Hi there, Ive just been trying to get root on the phone. I flashed CWM 3.0.2.4 onto my NS (2.3.4) and now it only boots into CWM, wont boot into android. How do I get it to boot to android! No idea what to do, Ive googled the **** out of this and just get loads of conflicting stuff, none of which works!
Thanks for the help!
What is the command you used to flash CWM onto your phone?
hi i have the same problem. i have i9023 and i made:
oem unlock command and the flash recovery command.
everything was ok.
then i used superroot-user-install.bat or something like that (which was mistake on 9023 i think)
after this i can start phone with volume up+power and can go into recovery.
but if i want to reboot into system i had just google logo and litlle logo of lock down on the screen and thats all.
Stupid question: did you try yanking the battery?
I have the same problem! I'm stuck in the ClockworkMod Recovery. Rebooted the phone multiple times, no change :S
EDIT: Panic is over, fixed it
I got that problem too when i tried to root my NS, then I downloaded the stock image > extract to get the original bootimage > flash it > reboot CWM recovery > problem solved.
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
Well, while trying to flash a custom rom on my phone I ended up here and tried many different methods.
First after I installed TWRP on the phone I tried to install the rom and it told me it failed. So then I wiped my phone and tried again, still failed. Then I got stuck in a bootloop. I did a factory reset and was able to get into TWRP. So I wiped everything and it asked me if I wanted to root my phone. I said yes and now the boot screen stays forever and the notification led never turns off. So I did factory reset and tried to run a command on terminal "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" it still did not boot up.
I have tried flashes the stock and I can't get oceanhost.eu and storagecow.eu to load up.
Please I would appreciate any help, is my phone dead? I can always boot to TWRP as long as I factory reset.
The Need said:
Well, while trying to flash a custom rom on my phone I ended up here and tried many different methods.
First after I installed TWRP on the phone I tried to install the rom and it told me it failed. So then I wiped my phone and tried again, still failed. Then I got stuck in a bootloop. I did a factory reset and was able to get into TWRP. So I wiped everything and it asked me if I wanted to root my phone. I said yes and now the boot screen stays forever and the notification led never turns off. So I did factory reset and tried to run a command on terminal "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota" it still did not boot up.
I have tried flashes the stock and I can't get oceanhost.eu and storagecow.eu to load up.
Please I would appreciate any help, is my phone dead? I can always boot to TWRP as long as I factory reset.
Click to expand...
Click to collapse
Sorry that I didn't mention this but, I am runnning a LGG2 802 16gb
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
I would flash TWRP and try wiping all including internal. Sounds like one of the partions is corrupted. You could do it with fastboot in bootloader mode but not sure of the commands.
teunnk said:
I had my phone rooted on old Oreo version and wanted to reinstall the latest factory image. While I was doing this my laptop got a BSOD and the installation didn't fully finish. I redid the install but now my phone is in a bootloop. It will go past the Google logo but afterwards will loop on the dead Android guy with the ''No command'' message, same happens when I try to enter recovery mode. Is there something I can do?
Click to expand...
Click to collapse
You're probably not used to the stock recovery. The no command droid is normal. Watch this video, and see if you can get to recovery or bootloader.
I had already installed TWRP and decided to wipe the whole data from my phone, thinking that it's going to be the same as a factory reset because I want to reset my phone. Phone startup went well, no hiccups or anything. Then I decided to flash TWRP again. But I never managed to actually install it. I follow the manuals from here and here, but I somehow always can't boot into the recovery. I use the same ADB and fastboot I used to install TWRP from before. Flashed .img, reboot, can't enter the recovery, starts over again, and this goes on and on. Until now, whenever I want to boot normally, I keep getting stuck at the "Zenfone" logo screen. The only different thing that I could think of that caused this is when I decided to use Universal ADB Helper, because maybe it'll work there i thought, and I flash the twrp.img using the "Flash Recovery via fastboot" command. If there's anything that could help me, even if it meant resetting the phone again, I'd very much appreciate it.