Hello.
Basically I accidentally wiped my system in twrp and then i encountered some errors while trying to flash a new ROM.
Now I can't access the bootloader anymore, and I can't recover with the "fastboot flash recovery recovery.img" anymore. The flash goes through fine, but when I try to boot into the bootloader i get the error "dtb not found". I've tried with different recovery.img's but none of them have worked. I have no idea what to do, please help me!
Tty downloading "first aid ' into your computer.,connect your phone through fast boot and run the batch file. It worked for me like a charm.
suchiqaz said:
Tty downloading "first aid ' into your computer.,connect your phone through fast boot and run the batch file. It worked for me like a charm.
Click to expand...
Click to collapse
That gets me into TWRP, but I can't press anything inside TWRP, the touch doesn't work and when trying to flash a newer version of TWRP, I get the error "dtb not found" again.
Recover using Qualcomm drivers method
Sent from my ONE A2005 using Tapatalk
Related
Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.
Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk
Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?
No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.
colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk
I'm afraid I ****ed something up.
My phone bootloops and the only way to reboot correctly is to do "fastboot boot boot.img" with the STOCK boot.img (which can be found here : https://drive.google.com/drive/u/0/folders/0B7F3ZXr565GkUU5iYjJtLXE2STQ)
Also I am not able to flash anything on the phone.
TWRP says "Error executing updater binary in zip...", and when I attempt to flash something through ADB Sideload, i get "Cannot read zip".
How can I fix everything? I guess I flashed something wrong trough fastboot but I'm not even sure what.
Also I found out that my bootloader was still locked.
But I can't unlock it since I am on Lollipop and the ASUS Unlock Tool is for Android M (I get error when i install the apk).
So I would flash Android M to unlock bootloader but hey, I can't flash anything....
I kinda fixed it, atleast I can now boot normally.
I followed this tutorial by @MiauLightouch : https://forum.xda-developers.com/showpost.php?p=66364620&postcount=8
And now I can boot without using fastboot.
Still unable to flash stuff using TWRP though.
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM
StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.
kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.
Hello everyone. Today, I was updating the edxposed magisk module, then rebooted the device and now I cannot use it because it asks for a password. I am on Lineage OS 17, using latest Predator Kernel with latest magisk. I have Orange Fox recovery installed, but the thing is that I cannot boot into recovery mode to format data. I powered off the device, pushed volume up and power button but it was booting in the os, again asking for a password. I tried booting an image of twrp from fastboot and it didn't work, the phone either booted into the os asking for password or just powered off. Now I am trying to flash stock miui latest global with miflash tool and when i click the refresh button a box appears saying "Invalid class". I have all the necessary drivers installed. This error does not make sense to me since I have flashed stock firmware in the past on lavender using miflash tool. I searched on the internet and found no solution and very little information about this error. I cannot believe it, all of that because of a freaking magisk module update, I regret so much the moment I tried to update that edxposed module!
Anyway, I really am desperate at this point, I don't have much experience and I have no idea what to do. If anybody knows of a way to fix these problems, please reply as soon as you can, as this is my main device! Any help will be greatly appreciated.
If you have a backup of the boot partition, you can simply install the image via fastboot using "fastboot flash boot boot.img" and that should fix it.
user0u said:
If you have a backup of the boot partition, you can simply install the image via fastboot using "fastboot flash boot boot.img" and that should fix it.
Click to expand...
Click to collapse
Hello, thanks for the reply. I tried flashing my boot image but it didn't work, it was still asking for password. I also tried "fastboot boot boot.img" and same result. What I want to do at this point is to make MiFlash tool work so that I can flash the stock rom. For some odd reason on my computer it showed that "Invalid class" error. But now I tried using MiFlash tool on my dad's old laptop, and everything seems to be working here, no errors. At the moment of writing this the stock rom is being flashed. Let's hope I will be able to boot into it.
Good luck
FilippPAOK said:
Hello, thanks for the reply. I tried flashing my boot image but it didn't work, it was still asking for password. I also tried "fastboot boot boot.img" and same result. What I want to do at this point is to make MiFlash tool work so that I can flash the stock rom. For some odd reason on my computer it showed that "Invalid class" error. But now I tried using MiFlash tool on my dad's old laptop, and everything seems to be working here, no errors. At the moment of writing this the stock rom is being flashed. Let's hope I will be able to boot into it.
Click to expand...
Click to collapse
FilippPAOK said:
Hi, did you solved the problem with invalid class? i have the same issue
Click to expand...
Click to collapse
Hello, I never found a solution to this weird error, but I didn't need to because I now use a different computer. I don't really know how to help you. I remember that back then it used to work fine but suddenly one day this error showed up out of nowhere. I don't know what caused it and there isn't much information about it on the internet. Maybe try putting the mi flash tool folder to different directories on your computer and see if that helps, try deleting it and redownloading it or check the log on the mi flash tool log folder. I remember that it didn't help me back then but maybe it helps you.
Elaborate a bit on the issue. What is your device? What did you do before the error started showing up? Try being a bit more specific and maybe someone else will help you.
If you have access to another computer, use that one as a temporary solution to flash your device.
Hi, thanks for the reply
I tried everything: Update windows, reinstall Net Framework, Reinstall MiFlash, use older or newer versions, Reinstall Drivers, use in different locations
I'm 99% sure the problem is not MiFlash but any component in Windows 10
Because I had other problems with other application with similar error
I have no idea, I don't want to format my computer...
My device is Dell E7240
DoMimik said:
Hi, thanks for the reply
I tried everything: Update windows, reinstall Net Framework, Reinstall MiFlash, use older or newer versions, Reinstall Drivers, use in different locations
I'm 99% sure the problem is not MiFlash but any component in Windows 10
Because I had other problems with other application with similar error
I have no idea, I don't want to format my computer...
My device is Dell E7240
Click to expand...
Click to collapse
Hello, sorry for the late reply. Unfortunately, I don't know how to help you. If you find a solution, please post it so that people who might have the same issue in the future know how to solve it.
Please, I also found this kind of problem on my desktop, invalid class when refreshing in the miflash tool. I am very sad
Hello and thanks for inteterest to help. (My phone Redmi 2 Prime)
So to the point, i have my phone installed custom ROM. And today when i try to reset factory, it stuck in the MI Logo (Show and then turned off). So i forgot to flashing the twrp again last time, so i left it without any recovery. The only way is repairing it with Fastboot and installing TWRP. So i start installing all driver and flashing. But, when i want to flash twrp to my phone, it keep showing me this
fastboot flash recovery recovery.img
flashing 'recovery.img'
FAILED (Data Transfer Failure(unknown error)
DONE! 5.8 sec
But it doesnt installing any recovery. I have installing MiFlash driver. Is there any driver that i should install again? Or anything that i can do? Also my PC doesnt read my phone storage at all, it doesnt show in the explorer, but can read "my phone" and my phone model. And I'm using USB 2.0. I also have try USB 3.0 but it doesnt work too.
Any help would be appreciated. Sorry for the long post, eh?
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
dabakale said:
Try to temporarily boot into recovery by this command
"fastboot boot recovery.img"
(If it boots to recovery then you can flash any zip)
Click to expand...
Click to collapse
Thank you for replying
So i've try it, but why its stuck at 'downloading boot.img' for 2 hours?
Can i download the boot.img manually? If yes, what should i download?
Can you share a photo of error.
Or you can try miflash to flash stock rom. Then you try to flash twrp. I suspect there would be something wrong with your recovery partition.(i also had similar problem while flashing different roms.)
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Egalito Rieans said:
Ok, so when i flash stock rom on miflash, at average 70%, it show me "fastboot.exe has stopped working" and show me error 0x80004005('Error flash system.img')
Why, godness? Is it because my laptop is only having 2GB Ram?
Or is there any ways to flash TWRP with fastboot without UBL?
Click to expand...
Click to collapse
Try this method
[No More Errors] [Fastboot Rom Flashing] [Direct Method]
Hi all, Yesterday i flashed miui LP on my Redmi 2 Prime. In the evening i tried to flash the miui KK with fastboot rom. But ended up with unspecified error ;). I tried many things but no luck. Then i followed direct method and that worked...
forum.xda-developers.com