Database Users

CWM recovery reboot prompted for recovery disable & root - now stuck in boot loop

I was trying to unlock my Nexus 4. I've done this before on a Galaxy Nexus, successfully but something went wrong here.
Just got CWM Recovery on. I tried to reboot using the recovery and it provided me with two prompts:
1) Do you want to disable the stock recovery install? [ I hit NO ]
2) Do you want to root your device (I believe this is what it asked) [ I hit YES ]
Now my phone is stuck in a reboot loop. I can get into recovery with no problem (and it is still the CWM one). I've tried reloading the recovery to no avail. What are my options to try to fix this?
I have tried fastboot erase cache but it did not restore my phone.

Update your recovery or try to flash another recovery. Twrp is recommended here. Cwm also gave me some hard time with bootloop and stuff

CCody said:
Update your recovery or try to flash another recovery. Twrp is recommended here. Cwm also gave me some hard time with bootloop and stuff
Click to expand...
Click to collapse
I tried flashing TWRP, but I get the Can't mount /data, Can't mount internal storage, etc etc. I can't flash .zips at all and I feel like my only way out is to use fastboot to deal with things. Even now, I'm trying fastboot and it's stuck trying to send the factory Nexus 4 4.4.4 ROM over...
I have no idea how to safely fall back now. I just want my phone back ASAP.

Just tried flashing 5 out of the 6 imgs to my phone using fastboot (didn't flash recovery). and I'm STILL stuck on the loading screen (10 minutes). Which means I'm still having the problem...I have no idea what to do now.

limenuke said:
Just tried flashing 5 out of the 6 imgs to my phone using fastboot (didn't flash recovery). and I'm STILL stuck on the loading screen (10 minutes). Which means I'm still having the problem...I have no idea what to do now.
Click to expand...
Click to collapse
Flash recovery in fastboot. This'll put the stock recovery on. Do a factory rest in the stock recovery. Then flash the twrp image in fastboot and re-root
Sent from my Nexus 5 using XDA Free mobile app

limenuke said:
I was trying to unlock my Nexus 4. I've done this before on a Galaxy Nexus, successfully but something went wrong here.
Just got CWM Recovery on. I tried to reboot using the recovery and it provided me with two prompts:
1) Do you want to disable the stock recovery install? [ I hit NO ]
2) Do you want to root your device (I believe this is what it asked) [ I hit YES ]
Now my phone is stuck in a reboot loop. I can get into recovery with no problem (and it is still the CWM one). I've tried reloading the recovery to no avail. What are my options to try to fix this?
I have tried fastboot erase cache but it did not restore my phone.
Click to expand...
Click to collapse
Flash it again. Remember to clean out the cache and dalvik cache every time you flash a zip.
This is why most phones get stuck in a boot loop when flashing a new ROM.
As long as you have the custom recovery, you don't need to flash custom recovery
Hope this helps!

I would also recommend PhilZ's recovery. Best of both CWM and TWRP.
Sent from my Nexus 4 using XDA Free mobile app

[SOLVED] Recovery loop - Bricked? - Reboot Mode Flag: Recovery

Hello everyone,
I'm not new to flashing and ROMs, so I tried flashing the Android L AOSP build from here. I succeded and wanted to install gapps through TWRP. I don't exactly know what I did. Now when I power on my device, I always get stuck in recovery. I already reflashed the 4.4 factory image and the AOSP lollipop build serveral times, but my fastboot info still says "Reboot Mode Flag: Recovery".
Summary: Fastboot works, I can flash imgs. Every time I start/restart it reboots to recovery.
I also tried relocking and unlocking, but I had no luck.
I hope I get my Nexus 10 working again.

PetaByteBoy said:
Hello everyone,
I'm not new to flashing and ROMs, so I tried flashing the Android L AOSP build from here. I succeded and wanted to install gapps through TWRP. I don't exactly know what I did. Now when I power on my device, I always get stuck in recovery. I already reflashed the 4.4 factory image and the AOSP lollipop build serveral times, but my fastboot info still says "Reboot Mode Flag: Recovery".
Summary: Fastboot works, I can flash imgs. Every time I start/restart it reboots to recovery.
I also tried relocking and unlocking, but I had no luck.
I hope I get my Nexus 10 working again.
Click to expand...
Click to collapse
Boot into fastboot and try to wipe the /misc partition....
Code:
fastboot erase misc
Thx Josh

Thanks for your reply, but it didn't work. Still the same.

PetaByteBoy said:
Thanks for your reply, but it didn't work. Still the same.
Click to expand...
Click to collapse
How did you flash the android 5.0 zip ?
Thx Josh

I extracted the imgs from the zip and fastboot flashed them one by one. Then I flashed twrp (the stock recovery didn't work seither), rebooted to twrp and installed pa pico gapps with modified script. When I rebooted, that worked. I booted to recovery a few times to make the Google Now Launcher a system app. Since that it is only rebooting to recovery.

I doubt that it's bricked.
Have you tried flashing the factory image KTU84P exactly like instructed here? :
https://developers.google.com/android/nexus/images

Nope I already tried that..

once when i was upgrading from 4.3 to 4.4 i experienced something very similar. nothing worked.
the way i fixed it was to relock and then unlock the bootloader (even though it appeared unlocked, something was wrong.) I hope this helps.

I finally got it working. Thanks for the time you spent helping anyway.. So I flashed CWM through fastboot and restarted to recovery. CWM cleared the boot flag properly, which TWRP didn't. Now booting

PetaByteBoy said:
I finally got it working. Thanks for the time you spent helping anyway.. So I flashed CWM through fastboot and restarted to recovery. CWM cleared the boot flag properly, which TWRP didn't. Now booting
Click to expand...
Click to collapse
Great to see you got it taken care of....
Can you add 'SOLVED' to the tread tittle...
Thx Josh

Security error after recovery update

I have a d802 . I had cloudy1.3 and twrp 2.7 installed with autorec. I tried to update it using
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
(from twrp page, with the latest img file).
But I coudn't access recovery, some error about security. Then I shutdown my phone and then it booted fine into system. I retried to access recovery but nothing.
So I decided to return to autorec, I installed it, I clicked "Flash Recovery" and now my phone doesn't boot in any way.
It show "lg security error" and then shutdown.
I can access download mode. Is there a way to fix my phone without deleting everything?
I'm sure the problem is the recovery, I was messing with it, can I bring my phone back and don't delete my configuration, photos, apps?
Thanks

I'm so happy!
I did it!!!
I managed to boot into recovery with the usual combination of keys (with the method that ask you if you want to format, but then you press power and it boot into recovery).
From there I saved everything using adb pull (Just in case). Then I dirty flashed Cloudy 1.3 and my phone is back !
I hope my experience can help someone

System Partition not booting, after reboot its booting into recovery!

Hey, sorry for the ignorance!
I flashed this ZUI (Nougat) rom on top of CM 13 data, phone did boot with old apps. When i pressed factory reset from settings menu the phone went to recovery and since then its only booting into recovery and not into system! everytime i get into TWRP system is not checked. even after mounting system and flashing stock zip. The phone isn't booting into system but recovery only. Tried flashing system.img by Fastboot.
Solved by using QFIl

Flash stock recovery, then boot into recovery.
It will automatically do factory reset, after that your system partition will boot.
Then flash TWRP again.
And do remember, not use Factory reset option from OS while on custom recovery.

Had the same issue, went to fastboot and then flashed through adb. Worked as a charm.

Hi there,
I installed RR os nougat on my phone about a month ago
Since then it was working perfectly fine ,
But today when I tried to interchange my sims the disaster happened
Now my phone is not booting
1st after pressing power button it shows zuk logo and then boots in twrp recovery
And I tried wiping and installing the ROM again but still the problem is there ....
It is not booting in system partition
Please someone help ......

GOKU07 said:
Hi there,
I installed RR os nougat on my phone about a month ago
Since then it was working perfectly fine ,
But today when I tried to interchange my sims the disaster happened
Now my phone is not booting
1st after pressing power button it shows zuk logo and then boots in twrp recovery
And I tried wiping and installing the ROM again but still the problem is there ....
It is not booting in system partition
Please someone help ......
Click to expand...
Click to collapse
Try the above mentioned solutions as flashing stock recovery and then stock OS and then TWRP!
I used QPST method to flash Chinese ZUK ROM through QFIL , and then flashed CM 13 later on. :good:

I flashed stock firmware through fastboot and it booted and then flashed twrp and due ROM !! Now working perfectly fine !! Thanks for help

any idea where i can find stock firmware and recovery? the urls which i find via google are no longer online -_-

akshaybjp said:
Hey, sorry for the ignorance!
I flashed this ZUI (Nougat) rom on top of CM 13 data, phone did boot with old apps. When i pressed factory reset from settings menu the phone went to recovery and since then its only booting into recovery and not into system! everytime i get into TWRP system is not checked. even after mounting system and flashing stock zip. The phone isn't booting into system but recovery only. Tried flashing system.img by Fastboot.
Solved by using QFIl
Click to expand...
Click to collapse
I had the same issue. Solved?

SOLVED!
Go to : https://www.youtube.com/watch?v=vSWC5MAB5cE

For TWRP
If You have TWRP follow this thread https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
the terminal is in advanced menu.......

drtarga said:
any idea where i can find stock firmware and recovery? the urls which i find via google are no longer online -_-
Click to expand...
Click to collapse
Can be found here https://forum.xda-developers.com/showpost.php?p=71415281&postcount=6

How to switch off the phone stuck in zUK logo with no recovery installed. I tried long pressing the home button but it reboots to zuk logo ,is there any way to switch off the phone

This will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.

[SOLVED]"No Command" error in recovery mode after flashing TWRP via ADB

What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again

The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.

echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make

Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img

It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.

NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly: