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?
Related
OP Junior MemberThanks: 0
2 posts Joined: Sep 2014
I have a Motog 1040 tx.
I have unlocked the boot loader through Motorola's website
I have SuperSU installed. I have verified using an app the phone is rooted.
This my problem installing clockword mod...
When I go through the commands in terminal manager. It says recovery. IMG not found.
I've downloaded clockwordmod recovery peregrine for my phone model and renamed
it recovery.IMG and placed it in the sdcard memory card root.
I've tried placing flash image in my sdcard root as well and used that method as well.
Anyone know what I'm doing wrong? The sd card is listed as sdcard1 on my device. I've also noticed that there is an emulated sdcard listed.
You can flash recovery in fastboot mode by using the command fastboot flash recovery nameoffile.img
How do I go about doing that?
Make sure the phone is not connected to a USB cable. Press and hold both volume buttons, press and hold power for a few seconds, release all buttons and you should be in fastboot mode.
What do I do once in fastboot mode? Where do I enter the command and where do I place the recovery.img
Have a look here: http://forum.xda-developers.com/showthread.php?t=2577043
I need confirmation that you've placed adb and fastboot in the platform tools folder?
Fastboot doesn't work in command prompt. Is this due to windows 8.1 64 bit...?
Fastboot and mfastboot should work in Win7 by installing drivers.
Win8 is a little trickier: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81-10/
OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?
Very good
deltadiesel said:
OK... So I got fastboot working. I flashed clockwordmod recovery peregrine....I flashed clockwordmod mod recovery no touch.... I've flashed twrp...... Successfully.....they're the right version for my phone. Even though I've sucesssfully flashed .... My recovery is still stock. What am I doing wrong if it is saying I've successfully flashed the recovery IMG though it doesn't change?
Click to expand...
Click to collapse
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.
audit13 said:
After it flashes successfully, disconnect the USB cable, and boot into recovery using the volume buttons.
Click to expand...
Click to collapse
Awesome it worked. Here's my other issue now though. Because I edited a file and inputted a string incorrectly in the root folder I had to install my stock ROM. Since reinstalling the stock ROM I have next to no memory left on my device. When I used mfastboot I did not clearvuser data so I wouldn't loose everything on my phone. What can I do about this. Will installing the custom ROM for my device clear this up?
I don't think a custom ROM is going to help you get back your memory.
Install Titanium backup. Backup your apps and data, do a full wipe of data, cache, and Dalvik and check memory usage. If that doesn't help, do a full wipe of everything, install the ROM, and restore from your Titanium backup. Just make sure to save your titanium backup folder to your PC before doing the full system wipe.
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..)
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
I am creating this post to help p2 community who is stuck on blue led after magisk update on custom rom
I have encountered this issue twice on my phone after a magisk update.
This happens when you patch the update directly from magisk manager.
The first time I was stuck with this issue on custom pie rom, I searched on other threads and got to know that device needs to reset to stock rom by flashing fast boot stock files on download mode, just search it, you will get link with details
However, this was a very complex task , also I lost my data in the process after flashing the data partition. From there , I went on to flash custom rom ,then installed apps , the process took the whole day
The second time when I again stuck with blue led , I was on another pie rom, This time I recovered my device without having to go over flashing all things again.
Please find the detailed step below , as I think it may help someone in such critical issues
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
Please like the post if you had same issue and are able to recover it from mentioned steps
I got into this trouble too, when direct installing magisk from v19.2 to v19.3. The magisk manager shows that it's finished installing v19.3 and reboot. Then the phone shows the white Lenovo screen, then turns dark, and vibrate for a few seconds with blue led lighting up, and finally just freeze. No bootloop, just a dark screen with blue notification led.
What I did was going to twrp (the one recommended in LOS 16.0 thread) by pressing vol up + down + power button until the white Lenovo screen come up, then release. I just reflash my current ROM (RR-P-v7.0.2-20190604-kuntao-Official.zip) using adb sideload. It finished flashing, click reboot, and finally managed to boot into system. No data loss, magisk v19.3 worked, and no magisk uninstaller required.
During the flashing process, I noticed that Magisk v19.3 was being auto flashed, so the magisk manager direct install probably somehow mess up with the boot.img after installing v19.3.
I was not able to go in twrp by any means , so I mentioned steps via download mode
Regarding your way to sideload and dirty flash whole rom , it didnt worked with me previously, so I cannot say about that, it was going back to blue led after reflashing
Regarding magisk installing and removing steps, anyone can ignore this steps and try if it works for them.
Just uninstall the magisk and reinstall it.
I have also faced same error previously and reinstalled magisk and it worked.
Someone please make a video of this and post it here
Rakxx said:
1) Go to download mode, flash treble supported twrp for treble supported pie roms, by using command - fastboot flash recovery name.img
2) Temporary boot into same twrp , command is -
fastboot boot name.img
3) Once in twrp, go to reboot, reboot to recovery
4) Once in recovery , copy following files into internal storage - magisk.zip, magiskunistaller.zip, twrprecovery.img ( one used in step 1 ), boot.img ( extract it from existing rom package.zip)
5) Flash magisk uninstaller first
6) Go to install, install image
flash boot.img by selecting boot partition
if it get stuck , again go in twrp using step 3 and try again, it will work
flash twrprecovery.img by selecting recovery partition
7) Flash magisk zip now
8) If all goes well , you phone will boot into existing rom
I have this issue but I don't know how to do these steps please make a YouTube video and post a link here (I'm new to this)
Click to expand...
Click to collapse
i don't know how else to describe this, i was flashing a custom ROM, then flashed magisk and now my phone is stuck in bootloop unable to go to recovery or system, the phone boots then black screen, etc etc, the same goes for recovery except it is faster (i reflashed recovery and it still happens) unable to do basically anything other than stay in fastboot mode.
what should i do?
edit 1: i can reboot to recovery and only be able to access shell.
Enter fastboot and flash recovery again. Brigudav's TWRP is the most used one. Gringo80's TWRP is new but seems to be working as others have written. (Both are unofficial and a take or leave, we don't have their source code, unfortunately.)
Right after flashing reboot to RECOVERY (not system). Can do with fastboot command or by holding button as usual. Alternative: reboot to recovery image file itself.
Once in recovery, format data (the option that has to type "yes" ). Reboot to RECOVERY again. Wipe cache, dalvik.
Reboot to system. Probably will work if your custom ROM was flashed properly.
Otherwise you can do everything again and also reflash ROM.
EDIT: I missed the Magisk part. So, while in recovery, dirty flash same custom ROM again. Or alternative: rename the Magisk file to uninstall.zip and flash it....this will restore your original boot and completely clean Magisk.
After you properly booting to system, then you can again try install Magisk.
why does flashing TWRP and booting to it directly work? i don't know! but it worked!
it seems that the custom ROM i installed is probably corrupt and flashed anyway ( i reflashed dirty/clean to make sure ) thanks for your help.