[HELP] - OP5 Without SO - OnePlus 5 Questions & Answers

Hello people...
I was trying to install this ROM on my OP5 (OnePlus5Oxygen_23_OTA_040_all_1811051816_c6670cf) that previously had a modified ROM (xXx NoLimits).
Installing de stock ROM with TWRP 3.2.3-0 threw error 7, so I tried to Install the sotck recovery flashing from fastboot (https://oxygenos.oneplus.net.s3.amaz...m/recovery.img) and now can't acces de "Install from internal storage" from the stock recovery. ADB does not recognize the device when entering in fastboot mode. I tried drivers reinstallation, and installing with sideload with error.
The device has a Unlook Bootloader, and was rooted with Magisk.
Sorry about the english. ¿What can I do to install the SO or TWRP to restore the BackUp?
Thank you all.
FIXED: The problem was solved with this thread by djnim: https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
Remember, if NO operating system, unrecognized fastboot and NO functional bootloader, use the MsmDownladTool V4.0.

Related

[Q] nexus s verification failed,help

Hi people,i recently bought a nexus s and when i try to install any update via recovery, such as the official 2.3.5 uk rom(i am on 4.0.4) i get the verification failed error,i even tried to root using the Superuser-3.0.7-efghi-signed.zip file in recovery but still same error,using 4.0.4 with unlocked bootloader, any ideas how to fix this,i only use linux so hopefully not a windows only fix,Cheers.
Couple of possibilities:
-You're using stock recovery/old custom recovery version; flash the latest CWM or TWRP recovery via fastboot
-Your recovery is corrupt/not for your phone; flash the latest CWM or TWRP recovery via fastboot
-You've toggled an option in recovery to check for signed .zips; turn this off via recovery
@Harbb for some reason check for signatures was ticked, all good now, Cheers

Bricked Moto XT1562

Hi , newbie help needed here!
have tried to root my moto and installed twrp properly. everything stopped working fine after i tried to install supersu. i tried to reflash stock image however for some reason twrp stopped working and I cannot run cwm either. the errors from cwm read:
"unable to load kernel"
while on twrp the system kept looping while attempting to install - i got errors such as "cannot find e: data" or "cannot mount e:" etc.
Has anyone come across this situation? Thanks in advance.
How did you get cwm recovery when it's still not available for mxp?...
Download stock firmware and RSD lite and flash it. RSD lite only works on windows 7.. otherwise you have to flash firmware manually.
derheckler said:
Hi , newbie help needed here!
have tried to root my moto and installed twrp properly. everything stopped working fine after i tried to install supersu. i tried to reflash stock image however for some reason twrp stopped working and I cannot run cwm either. the errors from cwm read:
"unable to load kernel"
while on twrp the system kept looping while attempting to install - i got errors such as "cannot find e: data" or "cannot mount e:" etc.
Has anyone come across this situation? Thanks in advance.
Click to expand...
Click to collapse
Follow the instructions from here
http://forum.xda-developers.com/moto-x-play/general/how-to-flash-stock-marshmallow-firmware-t3277657
Download & install minimal adb and fastboot.Extract the firmware to that folder and then enter the fastboot commands
http://forum.xda-developers.com/showthread.php?t=2317790

Unable to install qualcomm driver for Lenovo a6000 plus

I was trying to install custom rom and my device got bricked, now its stuck in boot logo. I am trying to install a rom but tried with qfil/qspt but device is not getting detected. Once I was able to install qualcomm hs-qd loader 9008(com 3) but it was not working so I removed it and now I am unable to install it again.
I tried to enter the recovery mode by flashing TWRP recovery, My device was prerooted and already i had install TWRP but a device was brick I was unable to access it. After flashing TWRP, I got the Mount screen of teamwin but touch is not working.its saying unmodified system partition detected. but after that I am unable to got to next step to install a rom in my device as qualcomm hs-qd loader 9008 not getting installed. Please guide me, I am new in all this,need expert help. thank you
@amitpandey, have a look AT THIS.
Still not detecting by my pc. Also unable to disable driver signature as in my laptop no option of troubleshooting option available in advance startup menu.

Help!!! Error mode?! :(

Hello GUYS.. So I was on the latest nougat update and I wanted to try CM13 on my P9 Lite VNS-L31 but someone told me that I need to downgrade to 6.0 before I install CM13 So I downloaded oeminfo and 6.0 rom from update finder.. and first I wiped system, data, cache and dalvik cache..okay so now I have no os installed.. Then I tried to install oeminfo with TWRP.. But it can't mount product/vendor/version (invalid argument) And I was like wtf does this mean? so I flashed stock rom image with fastboot again.. it said it's installed but twrp says no os is installed.. ugh I just tried everything to fix that..I tried to extract vendor.img and product.img and flashed them from fastboot.. But it said command not allowed and still twrp gives me the same errors when i try to wipe data or install system.. I asked people on another site and they told me I should install stock boot and recovery images from twrp and install system with 3 buttons method.. So I did but it said failed.. And when I wanted to flash twrp again the bootloader was locked wtf? so then I tried to unlock it again it asked me if i really wanna unlock it and I choose yes..the phone rebooted and I got this
Error Mode
Attention
Please update system again
(Android Logo)
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
now I can't boot into recovery or fastboot it just stays in this screen
I tried to install system with the 3 button method but it just won't boot to anything.. I also tried to connect the cable and boot to fastboot..But it. just shows the huawei logo and then goes back to error mode.. please tell me what I should I do now?
hi, did you solve this issue?
You should've just downloaded the rollback package and stock mm rom. Flash the roll back package and then the mm rom in eRecovery. Btw if you are going for meticulus Cm13 rom then ot has been removed from his website and in the beanstalk rom of meticulus when you call someone or someone calls you then the UI restarts. Thats a major bug

I have bricked asus ZenFone max pro m1. Please help me unbrick it!!!

While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile

Categories

Resources