[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
i have the same problem
jules.renz said:
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
Click to expand...
Click to collapse
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
majeida said:
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
Click to expand...
Click to collapse
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
sorry for the misunderstanding
jules.renz said:
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
Click to expand...
Click to collapse
sorry i have the same problem .
I'm using FML-AOSP-5.0-20141207-maguro and CWM V6.0.5.1 on a rooted Maguro.
Your personal data includes what?? Apps or photos and videos?
varadparulekarofficial said:
Your personal data includes what?? Apps or photos and videos?
Click to expand...
Click to collapse
yes
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
ashclepdia said:
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
Click to expand...
Click to collapse
I used this method
*I boot into costum temporary recovery "TWRP 2.8.3.0" Then I tried erasing and reflashing "bootloader", "radio", "boot" and new "system" through recovery All finished successfully according to TWRP but a reboot showed the system in the same state as before
Related
I recently bought an Oneplus 3 and wanted to root it, I succesfully unlocked my bootloader but when I try to flash TWRP and then load into the recovery mode the phone shows the oneplus logo for a few seconds and then turns itself off (even though ADB said it was succesfully flashed), when I reboot and go into recovery in brings me to the stock recovery.
Does anyone know how to fix this?
EDIT:
I previously had TWRP running on my Oneplus 3, at the first boot of TWRP I selected 'Read Only' because I saw that in a video, I couldn't flash a certain rom thats why I tought I had to update my TWRP, does this have something to do with it?
Anyone?
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Stock
krabman said:
Don't let it boot into system. Fastboot TWRP, unplug your phone, boot into recovery manually (power + volume down).
In TWRP, select reboot system and it will apply a fix before it reboots and it should stick then.
Click to expand...
Click to collapse
Can this be apply on other devices? Because I am having the same problem
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
This is universal: After flashing OEM ROM, don't boot into system. Boot into recovery, you will get into TWRP and from there boot into system. Or after flashing OEM ROM, flash Magisk and then boot into system.
kelvinchinedu said:
Can this be apply on other devices? Because I am having the same problem
Click to expand...
Click to collapse
Yeah, what he said. You can reboot recovery from TWRP and TWRP will patch it or you can flash magisk and it will do the work. What you can't do is flash TWRP and then boot directly to system because the stock recovery will be restored. Realistically do both, reboot recovery and then flash magisk for the win. I congratulate you on searching BTW, this thread is more than 2 years old. You may want to consider perusing the appropriate section for your other device. If it's a newer device with AB you will have some specific procedures to follow relating to that.
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Alcolawl said:
Hey guys and gals,
Silly question.
For a few months now, I've had TWRP 3.1.0 RC2 installed and no matter what I do, I absolutely cannot reboot into recovery. If I choose reboot to recovery while the phone is running, it results in a ramdump and eventually boots to system. If I reboot into the bootloader and choose to boot into recovery mode from there, it just boots to system. It's incredibly annoying. Literally the only time I can get into recovery is when I connect my phone to a computer and fastboot boot into a temporary TWRP Img and install TWRP again. Once I boot into system, I can never boot into recovery again. This is extremely inconvenient on the go, like right now, because I want to flash V4A before I start playing music from my Bluetooth speaker. Guess I'll just listen to low quality music :'(
What am I doing wrong? This is stupid.
Click to expand...
Click to collapse
I had the same problem, then I got a twrp boot loop, ended up having to boot into slot b and reflash stock img through adb, beware...
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
NYYFan325 said:
I was JUST about to post this! Exact same problem to the tee (except using RC1)! Hopefully someone smarter can chime in lol
Click to expand...
Click to collapse
I was on RC1 also
Anyone got some insight to this? Can't be that uncommon of a problem...
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
noidea24 said:
Try starting the process again.
Boot to bootloader
Fastboot boot 3.0.2 rc1
In twrp flash 3.1.0 r 2
Reboot recovery and check if it works
Click to expand...
Click to collapse
I never had TWRP stick unless I added another step to your instructions --boot completely into the rom once, go back into the bootloader, open temp TWRP and flash the TWRP zip again. If I didn't do this my recovery would always revert to stock but, strangely, even though I was running a custom rom the combination of the custom rom and stock recovery never bootlooped my phone and I was able to boot from the stock recovery to the custom rom with no problems. The only reason not being able to boot into TWRP was even an issue was that you can't flash any zips in recovery without it. Otherwise the phone ran so perfectly I didn't even realize at first that TWRP wasn't still the installed recovery.
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Also pointing out flashing rooms and certain zips here in the forums WILL revert you back to a stock recovery. Just my last bit of helpful information, hope someone gets it figured out, flashing is already a chore for those of us who like to experiment.
pcriz said:
Get the stock boot.img (this will remove root/kernel/twrp)
Boot into the bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (switch to the inactive slot)
Fastboot reboot bootloader
Fastboot flash boot boot.img
Fastboot --set-active=a or b (reload previous slot)
Fastboot reboot bootloader
Fastboot BOOT twrp.img
Flash TWRP in twrp..
If you can do that I would be interested in your results.
Click to expand...
Click to collapse
I was able to boot into recovery after doing this. Got a bootloop booting into system though, but flashing the ROM (and TWRP) fixed it.
Hello,
Try booting to TWRP 3.0.2 RC1 then flash TWRP 3.0.2 RC1 + SR1-SU v2.82SR1 + SU Pixel Fix (from Chains beta thread) one right after the other in the same TWRP session then reboot. Should fix your issue, give you recovery+root without ram dump.
Cheers
Everytime you flash a rom you need to flash twrp before rebooting or you'll lose twrp recovery.
Unfortunately I've had to get my Pixel XL replaced due to a defect and received a Verizon edition XL running 7.1.1. This is what I get for buying it from Best Buy Therefore I cannot unlock the bootloader and this problem no longer applies to me.
I'll keep this thread open for a bit in case it's useful for anyone else. I'll just sit here in all of my Stock-ness.
I couldn't get this to work. Tried flashing stock boot.img, then booting off of the TWRP images but I keep getting TWRP boot loop. Any suggestions? Tried flashing the entire stock image as well and no dice...
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.
Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
sbeaber4 said:
That's standard with a lot of OEM ROMS on many different phones. You can flash magisk or SuperSU to preserve your flashed twrp.
Click to expand...
Click to collapse
That won't work, the no-verity-opt zip is needed to preserve twrp or it will always revert back to the stock one.
Go here
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
And DL the TWRP & no-verity-opt-encrypt 1.6
follow the directions starting with
Open a command prompt and verify your device appears in fastboot
Then run
Code:
fastboot flash recovery C:\Twrp__chinese_Android8.img
Click to expand...
Click to collapse
Pitrino said:
Goodmorning, I've a strange problem with flashing recovery.
I used lastest fastboot
I've flashed the recovery (fastboot flash...) Then booted into it directly (fastboot boot recovery...) And obviously problems with mounting data.
The real problem is that when I reboot system , twrp is automatically erased and stock recovery is mounted.
I've tried everything, new recovery,new fastboot...
Please help me
Click to expand...
Click to collapse
- flash latest twrp https://twrp.me/xiaomi/xiaomimimix2.html
- reboot to recovery with hardware keys (volume-up + power) immediately after flashing
That solved the problem for me.
Hello, need your help guys.
So my Whyred bootlooping now. What I did previously was wiping System, Cache, Dalvik & Data before flashing custom ROM -- I know, this shouldn't be an issue. But since I can do fastboot, I tried to flashes recovery. I tried a few (TWRP, RedWolf & Batik), for each the steps were all the same: Via fastboot flash the dummy image to manipulate ARB check, then flash Recovery and finish with boot into recovery.
The phone booting into recovery, I can see the screen of recoveries for few second, then phone bootlooping again.
What should I do?
And for additional information, my phone was unlocked bootloader -- it still unlocked because I can see the Unlocked sign on bootloop screen. I also tried to flash official MIUI rom via fastboot (whyred_global_images_V10.0.6.0.OEIMIFH_20181127) but it was failed because anti roll back -- I also don't understand this because the ARB was supposed not allowing me to downgrade, but why is it also not allowing me to flash the latest ROM too?
I am now stucked in bootloop -- still can do fastbooting, but really have no idea how to flash any rom and get into the system. Really need help help help please
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Rush-er said:
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Click to expand...
Click to collapse
Yes, for redwolf it was the command -- I was short typing but thats the idea.