Related
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
It happened to me once. I pushed the power button for 60 seconds as it supposed to do a kind of battery pull, and it worked.
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Lordificated said:
same thing just happened to me... tried Factory Reset and TWRP ran an Open Recovery Script and boom... boot loop... TWRP screen pops up and then goes to loop...
tried pressing powerbutton but no use...
any workaround for this???
Click to expand...
Click to collapse
I've done this twice to my nexus now and I think I found a reliable way to restore to running condition. YMMV
1)Boot the nexus into fastboot (power and both volume keys) when you power up.
2)Attach your usb cable from the PC (or MAC I guess, dont have one to try)
3)start WUG Nexxus Root Toolkit. 'Launch' advanced utilities.
4)Test your fastboot with Quick tools. check the button at Fastboot-Bootloader and click 'List Devices' if the box that pops up is empty then fastboot isn't working (I can't help you there and it must be working to continue).
5)If fastboot shows a device then go to "Boot Temporary" and click 'Custom Recovery'.
6)I selected 'Touch TWRP' but CMW may work as well. This will reboot you into (temp)TWRP and from there you can force a reboot that will reset the 'Recovery' flag that has locked your bootloader.
7)Give it a few minutes (be patient for 5 minutes) and hopefully you reboot to where you were prior to this mess.
Long time lurker and couldn't fix my fails without everyone here.
Thanks to all.
Bill
HunterOrHunted said:
While using the PA Updater app to upgrade my rom, the app attempted to reboot into recovery to run an openrecovery script. While doing this, I believe it set my "reboot mode flag" to recovery.
The tablet boots with the Google screen and then shows the TWRP splash (I'm on version 2.6.0.0), then it reboots and starts again.
I am able to get to the bootloader, but even if I press start or recovery mode it reenters the boot loop trying to get into recovery. In the bootloader was where I saw the reboot mode flag set to recovery. Is there a way to use fastboot to remove that or am I just going to have to do a wipe with fastboot?
Click to expand...
Click to collapse
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
zeroedout420 said:
I had the same thing happen to me (though i updated from stock 4.4 to 4.4.2 [and i had twrp installed]). I tried reflashing to stock recovery and a few other things but same problem, it kept booting me into stock recovery. I know this is going to sound crazy, even stupid, but just letting it sit there for 5 minutes (at the stock recovery screen) let it work... I was searching for more things to try and it just started booting.... Checking the bootloader again showed the reboot mode flag set to none.
Click to expand...
Click to collapse
I guess mine worked because I was still on stock bootloader and adding TWRP was an important key but the 5 minutes seems to be the solution after all the rest.
recovery boot loop:- Is coz, one of your partitions would be facing problems while mounting.. So Wipe the Partition and Format it with Ext-2 file format. and reboot the Mobile. Then it'll stops rebooting.
Do you have a Samsung device?
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
carltasmania said:
Be warned - there is no such thing as fastboot mode for most Samsung Galaxy devices - you'll be wasting your time doing this and typing "fastboot devices" for many hours!
If you have problems with your recovery, it works to just reflash the CF-autoroot kit, which happens to flash the cache partition too. My problem was similar to the OP's - a bootloop with TWRP's obviously buggy OpenRecoveryScript, which was installing a ZIP file over and over again.
If you flash the CF-autoroot specific to your device, TWRP will be gone, but the phone will boot normally again - with all your data on it - hooray!
Then you install TWRP or CWM recovery as you did originally.
Stay away from OpenRecoveryScripts! I'll be installing a ZIP file in the traditional, manual way from now on, from an external SD card so I can remove the card if I get another TWRP boot loop.
Click to expand...
Click to collapse
How do you install cf-autoroot when stuck in a boot loop with samsung galaxy S device if there is no fastboot?
My phone is stuck in bootloop too. It shows Twrp at the starting and then restarts. What am i supposed to do? I need help ASAP please
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Skroutz said:
Hi,
I was on a rooted android 4.4.2 official, when i tried to install custom recovery using Flashify.
https://play.google.com/store/apps/details?id=com.cgollner.flashify
There was the Secure booting error and booted normaly.I found out that this was not possible so i quit.
Today a got an update from LG so i installed it. The phone rebooted giving the Secure booting error, and it stayed black screen.
Googling i found this tread
http://forum.xda-developers.com/showthread.php?t=2582142
I folowed it but i thought since my phone had problem with it's recovery, just flashing the recovery.img would be ok.
I restarted the phone bat it would not start. It desplays the lg logo restarts, lg logo restarts.
I can boot the recovery but it does not work. When i press recover it just restarts.
I cant boot download mode or anything else, i have been googling the hole day.
I would apricciate your help. It is a one month old phone.....
Thanks
Click to expand...
Click to collapse
are u stuck in cmw recovery??
Stock recovery.... :/
Sent from my GT-I9100 using XDA Free mobile app
Same Problem here! Exact Same
Also having this issue, stuck in the secure boot loop, can't get to download mode.
Im exactly the same - im stuck in TWRP and cant boot into Download mode at all - just get the LG Bootscreen then straight into TWRP Recovery no matter what i do
Did we all except some kind of update from LG........ i wonder if this the link here and is now a common problem?
Mine was this and i thought it was just an app update for the stock apps and now im stuck big time
Any luck guys or solutions then please post here so we can keep it together and help each other!
Yeah I got an OTA update for my D803-Bell model, upon restart entered the secure boot error loop.
Sounds like, via this thread that it's commonly happening to people who had TWRP or CWM (or even aborted / possibly never completed installs like me) got nailed.
As per that thread, and everything else, I've tried every option possible -- no download mode. Recovery mode doesn't restore anything, just resterts to lg logo -> secure boot error -> black screen. Shows as QSHSUSB_BULK in windows/linux, and I can see those 25 partitions in linux (but reflashing openrecoverytwrp__.img over the recovery partition didn't help. I'm waiting to find out how I can make my own copies of those various partitions listed, from another D803-Bell model I have access to. All the D803 .img files on those links in that thread, appear to not contain D803 Bell stuff, just Telus, Rogers, etc... so I'll likely have to source my own.
I just took a shot in the dark recommended by a friend -- and fixed my phone.
I zeroed out the 'fota' partition on the phone. As seen in this thread ; http://forum.xda-developers.com/showthread.php?t=2451696
Just did a dd if=/dev/zero overtop of the fota partition, which was 25 for me from my linux box. One quick power cycle later, and I'm fully functional again, and the OTA update that killed me is still showing as available again.
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
As I understand; If you're trying to boot it to recovery mode, it goes to fastboot mode, right?
If I understood right; you need just flash recovery to your device.
G2 has a different boot process from other devices. If bootloader failed to boot the thing you want to boot, it goes to fastboot mode. That's why it goes fastboot mode when you try to boot it to recovery.
Ah yeah, i just couldn't figure out how to get it out of Fastmode. I was a little confused about the difference between fastmode and recovery.
I seemed to have fixed the problem by AutoRec, for whatever that is worth. Now it boots into TWRP's recovery mode. Shouldn't be hard to get cyanogenmod now.
TheAmericannomad said:
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
Click to expand...
Click to collapse
if you want go back to stock and you can't enter in download mode you can try follow this but USE THE CORRECT FILES FOR YOUR DEVICE!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2477595
to extract laf.img from kdz.
http://forum.xda-developers.com/showthread.php?t=2600575
Give a thank to the OP of the threat.
Hi guys
I have a big problem with my note 3 hlte that i have never heard off... I run cyanogenmod 12 and i noticed when i flashed it that cwm recovery went back to stock recovery so i used app called Flashify and i "flashed" cwm that flashfy offerd me.
Afther that it offerd me to reboot into recovery witch i selected and now my phone is stuck in recovery boot loop....
It doesnt want to boot into recovery and i cant boot it normaly or download mode because its stuck in loop..
i tried removeing battery, draining power, leaving it for some time but every time when i return the battery and try to turn it on, its stuck..
very hard to explain, if you want i can record and upload it
(i would usualy flash a cwm via odin but i was to lazy to turn on my pc )
sorry for some gramatical mistakes
found solution
Volume down + home and pluging in usb automaticly boots into download mode
Find the correct cwn/twrp for your phone model & bootloader(4.3/4.4). Flash with odin.
The recovery corrupted, no big deal.
Sent from my SM-N9005
I successfully rooted the phone and installed magisk etc. but I want to further and wanna mess around a bit. So I need TWRP to back up my everything. However, whenever I flash TWRP to both slots phone deletes OS or TWRP claims so. Therefore I flash the OS and do all the things over again and the cycle continues. What can be the cause for TWRP deleting OS or saying so. Is it can be caused I flash the wrong TWRP? I used tool all in one to only boot to twrp but it just stucks me in the fastboot logo and nothing happens for long time. I know when flash it it boots in seconds.
And for FTM mode I try to enter the ftm mode but it stucks on boot logo and doesnt bring any chinese characthers again for long time. What can be the cause?
All the helps would be appreciated,
Thanks in advance.