Hi,
I hope this question wasn't asked before, I couldn't find a solution to my problem yet.
I tried using the toolbox to flash Philz and later TWRP recovery. the phone booted normaly and not to the custom recovery.
When I tried to boot to custom recovery the stock recovery loaded instead.
I even tried the command prompt method.
Eventually I used the command m=prompt method and immediately manually booted to recovery and the custom recovery (Philz this time) loaded. I though I was done, but right after I set up the phone as I like it and wanted to make a backup of it, the stock recovery loaded instead of the custom recovery.
any ideas?
what as I doing wrong?
Thanks
Unlock bootloader amd ise the fastboot commands to flash tje recovery permanently. Guides in the general section.
I see I need to elaborate
I will tell you what I did step by step.
1. Using the toolbox (V6), I unlocked the bootloader, the phone booted as if it was just got out of the store (all my data was erased)
2. Entered the gmail account and basically went through the entire initial setup process.
3. Booted to fastboot again and flashed TWRP recovery (using the toolbox).
4. The phone automatically booted normally (not to custom recovery)
5. I tried booting to custom recovery and I got the stock recovery instead
6. Booted to fastboot again and flashed Philz recovery this time (using the toolbox).
7. The phone automatically booted normally (not to custom recovery)
8. I tried booting to custom recovery and I got the stock recovery instead
9. I opened command prompt and used the "fastboot flash recovery recovery.img" command, the recovery.img I got from the "philz_touch_6.59.2-bacon" zip file.
10. I immediately forced boot to recovery and got Philz
11. I set up my phone as I like it (app + settings)
12 tried booting to recovery again (from power off of course) and got the stock recovery again !!!!
Any ideas?
I tried again and partially succeeded
Hi,
I decided to do all using the command prompt.
This time I disabled the CM Recovery Protection (though I clearly remember doing so before but might have done it before unlocking the bootloader).
I tried flashing using "fastboot flash recovery" command TWRP recovery but when I tried booting to the recovery I got one vibration (the one supposed to be before the recovery loads) and after a few seconds (+1 logo on screen) I got another vibration and the system normally booted (not to recovery).
I did it again with Philz and it worked, I booted twice to recovery and it holds.
The only difference was that Philz recovery was named recovery.img and TWRP was named TWRP.img, I don;t think that matters.
I really wanted TWRP. don't know why it didn't work.
This question has been asked several times, see the FAQ thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Related
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
EDIT (FIXED)
WHAT WENT WRONG...
1. Was using CWM (When i was last active in android flashing, twrp was just another custom recovery, cwm was needed for cm)
2. When i did use TWRP, it was an older version, and did not work (did not even boot to recover, in fact)
3. When i did get twrp working, i used a bad cm.zip file (corrupted)
nishant_713 said:
what i did -->
1. Unlock bootloader
2. Flash cwm via "fastboot flash recovery recovery.zip"
3. Boot to recovery
4. Factory reset
5. Flash cm zip from sd card.
what i got -->
1. "E:Can't open /sdcard/cm.zip
(bad)
Installation aborted."
Then -->
1. Rebooted, copied again, booted to bootloader
2. selected recovery
Now -->
1. shows the android mascot with its lid open and "No command"
2. no cwm (where did it go ?!?!)
Everytime i flash recovery, it boots the first time (till the time I've not rebooted after flashing recovery) and still won't flash my zip file, and then the recovery won't show.
Click to expand...
Click to collapse
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
bloodhound42 said:
first mistake here is u used Flash cwm via "fastboot flash recovery recovery.zip" which is wrong u need to use .img after recovery but not zip so try once again and flash latest twrp as cwm support is ended
Click to expand...
Click to collapse
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
nishant_713 said:
Thanks for the promt reply mate. Actually it was recovery. IMG only, not zip, i typed it wrong here otherwise the recovery wouldn't have loaded at all, as mentioned earlier. Moreover, I did try flashing twrp, but using twrp, I can't even get recovery to boot once (which does happen on cwm 6.0.4.7)
P.S - can it anyhow be related to bootloader ? I am on stock Lollipop. And device is dual sim (xt1033)
Click to expand...
Click to collapse
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
bloodhound42 said:
If u r on stock lollipop then u boot loader is already upgraded and its good for twrp recovery can u try flashing twrp v 2.8.6.0 and check it out using adb if it is already rooted then try flashing by flashify and let me know
Click to expand...
Click to collapse
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Update -- Ok flashed 2.8.6.0 and now boots to revovery (even after a restart) but still can't flash cm. Something pops on screen for a fraction of screen and then recovery reboots. It says "no md5 file found". Any chance of zip being corrupt ?
Update 2 -- Now my internal memory has stopped working :/ can't even take a screenshot, nor a photo. says memory full. Doesn't even copy file to memory when connected to pc. Although in recovery mode (twrp) , with usb mounted, it does copy.
nishant_713 said:
Ok did that. When it booted to cwm (which is all i can manage to boot to, if at all) i selected root phone option. But it didn't root actually. Then i rooted successfully using cf auto root. Then used flashify to flash twrp image, and now when i select recovery from bootloader, it boots normally, not even showing the "no command" screen. (And yea, I'm pressing vol up to select, not power)
Click to expand...
Click to collapse
weird did u flash normal recovery or gpe recovery ? U have to flash normal recovery and one more thing are u sure that its going into cwm recovery ?
May be the ROM is corrupted buddy download again and flash or try other Roms
Haha. After a hell lot of effort, i did get TWRP installed, and after breaking my head on why cm nightly won't install, i downloaded another one, and it installed fine. Now rocking CM 12.1 (4th device which I'm using on CM, and yet never had so much trouble getting it running..)
I installed twrp and were accessible before nowadays I'm not able to boot twrp its just stuck loading screen of twrp(first blue page with written twrp) please help me to fix this issue , I'm tried to flash recovery again and again but still same problem persists ,
Two Solutions :
1) Make sure your fasrt boot is connected . USb debugging on . and you are flashing latest TWRP fro your device. Once you have flashed TWRP recovery do not reboot . Use volume buttons to select recovery and press power button to select it without restarting teh mobile . This shoudl fix the isuse , if it does well and good if not jump on second solution.
2) Flash Clockworld MOD recovery (CWN Rercovery) instead that should overwright old recovery
No it doesn't work , i tried all type of booting to twrp ya also just tried latest twrp still same problem stuck at boot, im able to enter if stock recovery, . and can we flash latest roms on cwm?
There is no cwm for moto g3
Start the phone in the bootloader, now fastboot boot twrp.img and go to the file manager and delete /sdcard/TWRP folder, then reboot into the bootloader. (this wipes all old TWRP configuration information, and any backups you have on the internal storage so make a copy before hand if necessary)
Now "fastboot flash recovery twrp.img" but replace twrp.img with the actual filename of your TWRP image. Once it completes, DO NOT REBOOT, but select Recovery on the phone and start it, TWRP should start.
You will prompted whether to allow write access to system or not, ALLOW write access to system, and TWRP will start.
Go to Reboot menu and select Recovery, the phone should reboot and TWRP should start again... if you are prompted to allow system write access, allow it and repeat this step, if you are not prompted to allow system write access again, you should be good to go, proceed as normal.
That's it... basically the stock ROM has a script that will over-write any recovery change that is not stock, so TWRP needs to be able to write to system and reboot for it's startup script to stop the replacement script in the OS.
So for the most part @chungomungo1 answer was correct.
---------- Post added at 03:57 PM ---------- Previous post was at 03:53 PM ----------
And yes, there is (or rather was) CWM Recovery for the Moto G 2015, both Osprey and Turbo, but it has been discontinued and is no longer available. LineageOS (that replaced CM) seems to have embrassed TWRP recovery, at least as of now. Actually, it seems to still be here: https://download.cyanogenmod.org/?device=osprey however actually trying to download it fails.
I cant get into recovery if fastboot boot twrp.img or fastboot flash recovery twrp.img I'm stuck at the first boot screen can't get in then how can i delete twrp folder from sdcard? Also i tried to delete twrp folder from file manager it restored automatically, there is no fix for my solution?
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
qqzzxxcc said:
Only thing is works for me is https://forum.xda-developers.com/xperia-l/orig-development/cwm-recovery-installer-t2589320
su into dd via adb, twrp app, recovery installer by corphish (https://forum.xda-developers.com/xp...-installer-t3187915/post62536810#post62536810)
Every "fotakernel"-style ways saying that it is finishes its jobs successfully, yet when I "adb reboot recovery" it always loads stock recovery.
Bootloader is unlocked, I've checked it via *#*#737...
I've spent over 8 hours trying everything I've found to flash img, but it just doesn't becomes custom recovery, it is always reverts to default.
What I'm doing wrong or what is wrong with my phone?
Click to expand...
Click to collapse
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Kungfu73 said:
IIt's not your fault, it's because stock ROM only supports and allows this recovery!
So if you don't have any problem, use only that one!
But if you want to install custom ROMs using latest TWRP, then you have two choices:
1- Install some Lollipop ROM from current recovery and then use its own recovery to update your recovery to latest one, and continue your works!
2- Use adb & fastboot to flash latest TWRP to BOOT partition (not fota or recovery partition!!!) by booting into fastboot mode and using this command:
Code:
fastboot flash boot [I]yourimagename[/I].img
So it directly boots into recovery( instead of ROM!) But be careful!!! You must install your new ROM right after recovery is opened to avoid any potential problems with missing boot!
I recommend using first method for your convenience and safety
Click to expand...
Click to collapse
Thanks, that helped me so much!
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
qqzzxxcc said:
Okay, just reporting how stuff worked for me
Flashed boot.img from cwm11 - flashed cm11 = 4.4.4
TWRP to FOTAKernel didn't worked - still old CWM
Installed CM12 from that CWM - 5.0 as you mentioned.
Tried TWRP to FOTAKernel using su+dd. Still old recovery (don't remember which one, probably same CWM).
Decided to go all-in, flashed TWRP img to boot using fastboot - Finally got TWRP, but obviously couldn't run anything else. Also had flickering\shaky screen left and right but it's functions seemed to working alright.
Flashed [7.1.1]LineageOS 14.1 || Beta 4 by corphish (I've tried to flash it before from that old TWRP (2.7.10) it would run once (all functions were working fine), after you reboot device it gets stuck in bootloop.) result = everything works, no bootloop after restart, and TWRP 3.0.2.0 either fixed it self or maybe it comes with ROM so that helped, dunno.
Thanks for mentioning "fastboot flash boot yourimagename.img" and that I can flash recovery into boot.
Click to expand...
Click to collapse
Glad that it worked for you and you finally could get latest one!
I forgot to mention that in first method, after installing LP ROM, install recovery installer app and flash TWRP v2.8.7.2 and use that to install latest one !!! and LoL very long way
I just wanted to say that it is possible!
Ok.... So i unlocked my bootloader on a verizon pixel and installed magisk with a patch boot image. no problem
I just tried to install TWRP (3.2.2). I booted the image first, the flashed the TWRP zip in the booted image. Then TWRP would boot, but only TWRP would boot. it would never progress to booting up the rom.
So i found a thread that suggested flashing the magisk patched boot image.... that just made it worse. It would only boot to recovery... and NO FASTBOOT. I was able to get to the menu and use adb to side load the latest OTA. Now i can boot into the ROM and use the phone as usual
However, I still don't have fastboot in recovery mode. I don't think its drivers. I must have mucked up recovery. It gotta be related to the TWRP snafu. I can boot into the stock boot loader and my PC beeps and recognizes the phone, when i use the arrows to go to recovery, my pc loses the device. My PC just can't see the pixel in recovery mode.
Not sure how to proceed
Can I side load the factory image after removing the wipe tag (-w)? Do i need to factory reset?
Am an idiot.... fastboot works in bootloader.... please delete