So... I rooted my A300FU (5.0.2) with CF-Auto-Root, and eh... all went fine, and root access works now, but when I press "Restart" now, it goes to recovery instead... Same goes if I shut it down, and start it again, it goes to the recovery. I can of course choose reboot from the recovery, in which I case it boots normally. Did I mess something up?
Eh... never mind... I guess... I turned it off and booted into recovery, and then went "shut down" from it, and then turned it back on, and everything was fine. So... am I supposed to delete the thread now?
King-V said:
So... I rooted my A300FU (5.0.2) with CF-Auto-Root, and eh... all went fine, and root access works now, but when I press "Restart" now, it goes to recovery instead... Same goes if I shut it down, and start it again, it goes to the recovery. I can of course choose reboot from the recovery, in which I case it boots normally. Did I mess something up?
Eh... never mind... I guess... I turned it off and booted into recovery, and then went "shut down" from it, and then turned it back on, and everything was fine. So... am I supposed to delete the thread now?
Click to expand...
Click to collapse
Boot device into download mode,than flash stock rom,flash again cf-auto-root,and before you reboot your device after rooting ,flash with flashify boot.img from your stock rom and then you can normally reboot your rooted device
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
I everyone, i just aquired this awesome phone.
I rooted it with towel root and everything goes fine.
Then i installed autorec and chose to reboot in recovery.
All goes well and then in twrp i chose to reboot system.
Now after the LG logo i have a black screen with the notification led activated.
i can't go back to recovery neither
Looks like ur in a boot loop. If you cant go to recovery, I suggest you go to download mode and restore to stock rom via the KDZ method.
sai777 said:
Looks like ur in a boot loop. If you cant go to recovery, I suggest you go to download mode and restore to stock rom via the KDZ method.
Click to expand...
Click to collapse
Can only vouch this post. Absolutely solid advice.
Keep pressing the power button till it powers completely off, then press the volume up and plug the phone into the computer. Then follow get back to stock guide.
Hey guys and gals, I decided to take my new PH-1 and root it after getting the latest OTA (this is an unlocked Sprint variant). I flashed the twrp for my build and there was an error, tried it again and the same error so I rebooted back into fastboot and it flashed but I didn't reboot into recovery. Flashed it again and booted into recovery but it was just a black screen as if the phone wasn't turned on. The closest I've gotten to recovery was the android laying down and it said "no command" but I forced a reboot at that point (I think I could have pressed up on the volume and pressed the power button to get to it from there but I haven't been able to get back to it).
I ended up flashing a modded boot image for root with Magisk 14.3 and that worked but I can't reboot my phone, it just goes to the blank screen like it isn't on and I can start it up again by holding the power button down for 15 sec. and it seems to function fine but I can't flash the OTA file to go back to complete stock or to go to the Oreo beta.
If anyone could give me some insight into this problem or a way of fixing it I would grateful, thank you.
When I go to put the official twrp on it doesn't stick after reboot. before reboot I can't flash anything either like magisk. Nothing shows inside the folders and after I reboot and go back to twrp it shows no command
Me too. I've flashed twrp-sanders and also twrp-potter. The phone will never boot into twrp recovery on its own. Also, when I fastboot boot recovery from PC, either version of TWRP loads splash screen but is frozen and requires a hard reset.
The phone is unlocked as it indicates this on boot up.
Only once after the first attempt of flashing twrp-sanders recovery did the phone boot into twrp recovery and I flashed Magisk from there. Since then, no dice
Any ideas or direction would be greatly appreciated. Thank you
Got it to finally work. I started over by flashing "twrp-sanders-r2.img".
Make sure the first thing you do after flashing the recovery is to push volume button until you see the recovery option. Then press power button to select it. It will take several seconds before you can interact with the program.
I made sure I had the magisk.zip ready to flash first thing I did.
If you don't go to recovery immediately after flashing the twrp, you'll have to start over.
I hope this helps
I've had a Galaxy SM-T510 for about 18 months. I installed a custom ROM and it worked fine. When it booted up I received a message "Bootloader is unlocked and security cannot be guaranteed, press power button" and when you pressed the power button it booted up fine. Recently, I installed TWRP and when I rebooted it goes to the some "Bootloader is unlocked, etc" error message, but when you press the power key it restarts and loops to the same point. Holding the power key, with volume up, volume down or both makes no difference. I installed Fonepaw which appears to only work in Download mode which I can't access. If I run Odin or Kies it doesn't recognise that there is a phone attached. Any suggestions?
I've solved the problem. Holding down both volume up & volume down at the same time, and plugging it in puts the device into download mode.
Actually, I haven't solved the problem. I can now install an OS thru either Odin or TWRP, but all the OS I have tried go into a bootloop and the device never finishes booting up.
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
BillSchutt said:
I'm disappointed no one has any suggestions. I decided to replace TWRP with Orange Fox and installed Lineage, the device of course went into a bootloop. I then booted it into recovery and it went into TWRP. So I installed Orange Fox and wiped everything, I reebooted and this time it went into Orange Fox. I reinstalled Lineage -> another bootloop, tried to get back into recovery and it was TWRP.
Click to expand...
Click to collapse
You aren't getting help because you are posting in the wrong place. And, if you are coming from an old custom ROM, you have to first flash the right stock ROM. I no longer have a 510 so I'm not sure which stock ROM you need but if you check the first post for the custom ROM you want in the ROMs, kernels and recovery thread, it should tell which one it is based on.