Hello...
I made a mistake and flashed my recovery with out renaming my recovery.sh file.... I am rooted and unlocked status code 3. I am also updated on stock ROM. I need to back up and switch ROM's. I original flashed recovery with ROM Manager and got no results. Then I used a flash tool but failed to read the instructions on the thread before flashing. I have since then flashed several TWRP and CWM versions, as well as stock to no avail. When I select recovery from the boot menu I see the red Motorola emblem for a few minutes then it reboots normally. Does any one have a fix and or the recovery.sh file. Thanks.
Download the latest TWRP and place in your fastboot folder. Disconnect your phone from the computer, boot into fastboot, and then plug your phone in. Wait for the phone to connect. After it's connected type "fastboot flash recovery recovery.img." Recovery.img will be the name of whatever file you downloaded. After flash is complete, unplug phone and power off. Immediately boot back into recovery. Do not boot into OS.
With this method, you don't need to rename recovery.sh. Rebooting directly into recovery allows the updater script to complete, so the stock recovery doesn't take over. If you boot right back into OS, stock recovery will override.
If you can't do fastboot, download Flashify and use that app to flash the TWRP you downloaded. TWRP for this phone is not official, so it won't show up in ROM or TWRP Manager. You'll have to DL off here.
Sent from my HTC6525LVW using Tapatalk
Thank you for your detailed reply, I will try this tonight and let you know how it goes, I suspect it will work.
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app
You're welcome, hopefully one of methods will work for you.
Sent from my HTC6525LVW using Tapatalk
Thank you! Worked like a charm. Renaming the file Recovery.IMG, disconnecting my USB cable, powering down and rebooting directly into recovery is what I did not do. Doing that has solved the problem!
Sent from my Barnes & Noble Nook Tablet using XDA Free mobile app
Custom recovery unrooted my stock updated ROM.. Be careful!
Custom recovery has an option to root or you can flash SuperSU in recovery.
Well I kinda bricked it any way lol, but I fixed it with HouseOfMoto I think. At least I see the boot screen now...
Yep seems to have booted this time I will flash TWRP instead of CWM.
Related
Hi
I installed Cyanogenmod 7 and with it i added and Nscollab and I decided to change it.
Now the problem is that everytime i try to get into recovery from phone and from rom manager it displays the startup google logo and it stucks there.
iv'e heard that you can flash rom from computer. if anyone knows about program or any solution Please help me
Try to flash newest recovery form ROM manager. Sometimes it will not stay there after first flash, so try couple of times. If not, there IS the way to flash *img files from fastboot via PC. Google fastboot with other keywords, and there should be plenty of guides to do that ...
But first method should work just fine ...
Fastboot flash recovery
Sent from my Nexus S 4G using xda premium
yessir, if rom manager doesnt work then go:
fastboot flash recovery iLikePie.img
IN FASTBOOT MODE
and you should be good!
i tried that, i said by phone(via fastboot) and it just leads me nowhere, it comes back to same menu only and reboot and power-off works :\
What exactly did u try? Go here and try to flash it...
i cant get into the recovery. via the fastboot and via rom manager
when i tried to flash with the fastboot, i pressed on the recovery button and it shows the google startup logo, returns to the menu and it leads me nowhere.
when i tried to flash with rom manager, it reboots, and leads me to the startup google logo and stuck there. what im trying to say is that i dont have access to recovery menu (the backup, install from zip file etc).
Noahsoskha said:
i cant get into the recovery. via the fastboot and via rom manager
when i tried to flash with the fastboot, i pressed on the recovery button and it shows the google startup logo, returns to the menu and it leads me nowhere.
when i tried to flash with rom manager, it reboots, and leads me to the startup google logo and stuck there. what im trying to say is that i dont have access to recovery menu (the backup, install from zip file etc).
Click to expand...
Click to collapse
Try reflashing recovery from rom manager. It takes a few try for it to stick. When rom manager says it flashed. Reboot recovery from within rom manager. And keep trying till it sticks. Shouldn't take more than 3times
Sent from my MIUI powered Nexus S 4g using XDA Premium App
So you tried to flash recovery.img from fastboot and everything went smooth? After that you still can't go into recovery? Strange, that should work :S
it worked! the only button i didnt try it was the reboot into recovery,
thank you very much and all of you who helped me
Noahsoskha said:
it worked! the only button i didnt try it was the reboot into recovery,
thank you very much and all of you who helped me
Click to expand...
Click to collapse
Glad it worked for u
Sent from my MIUI powered Nexus S 4g using XDA Premium App
First off I am sorry for posting this, however I DID use the search tool. I recently got a USA spec Wifi only Xoom. It came with 4.1.1 preinstalled. I have sucessfully unlocked the bootloader.
My problem is this. I cannot gain root or even get CWM installed. I have tried oneclick, i have tried cmd prompt. I have followed every guide I can find to a "T". Is there something missing, is it an issue with Jellybean being preinstalled?
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
airesch said:
Use http://forum.xda-developers.com/showthread.php?t=1468298 to get CWM installed (and when you reboot from fastboot flashing the recovery image, and this is very important, DO NOT LET IT FULLY REBOOT INTO THE OS. You have to get into recovery in the next boot or the OS will just overwrite it with the stock recovery and you will just have to go back into fastboot and flash the recovery again.
http://forum.xda-developers.com/showpost.php?p=30464067&postcount=408 has the root once you get CWM installed.
Click to expand...
Click to collapse
Thanks for the reply, however this is one of the utilities I have tried,..
Here is a bit more info.
I am running windows 7 64bit if it makes a difference. Whenever I get the device into fastboot and try to flash anything, it just hangs at the original fastboot screen. I have let it sit there from 3 hours and eventually I have to reboot it. The Lord AIO Tool you linked just gives me and error message that the device is not a 2.2/2.3 device. If I were at home I would take a screenshot.
Could my bootloader be corrupt? The device still boots up and runs jellybean fine, but I am not loving the stock experience thus far...
Thanks again for the links!
Actually sounds like your drivers aren't right. I will look them up and link them when I get home
Try installing the driver from http://developer.motorola.com/tools/usb_drivers/, rebooting your pc, and try fastboot again. If that still doesn't work, then there may be something wrong with your pc setup OR your Xoom, not sure at that point.
Sent from my SPH-D710 using xda premium
Thanks a million, I am going to try it fresh on my pc at work. Thanks!
That did the trick THANKS A BUNCH!!!!!
Hi,
I finally managed to update my Moto G to 4.4.2 by flashing stock rom. However, before I did that, my phone was rooted and I used Titanium Backup to back up some files. I then copied that folder to my PC. Now, I have tried to root the phone again using superboot, but my screen goes purple literally 2 seconds after I load superboot and then I have to switch it off and back on again. It hasn't installed SuperSU so I'm assuming my phone isn't rooted any more. I am a total noob in these matters and I really do appreciate all the help given on this site.
I would greatly appreciate if you can help me by getting my files from Titanium backup back up again, and how to re-root my phone. I have searched the forum but I didnt find anything too similar to my situation and I don't understand a lot of the terminology. It took me a really long time to even learn how to flash the stock rom!
So I would appreciate any help. Thank you
Root option 2 doesn't work either. It just says "waiting for device" at the first stage. When I click on recovery, it says no command. USB debugging has been enabled. Im confused!
Put latest superSU zip on /sdcard on phone. Copy across to phone using USB or use airdroid app. Search internet for superSU zip by chainfire developer.
Flash custom recovery CWM (search forum for it). Be sure to get the one for 4.4.2 bootloader.
Boot into CWM recovery (boot to bootloader and choose recovery option using UP volume button) and choose to flash a zip file and then pick the superSU zip.
You are now rooted and have a custom recovery.
For titanium backup, either copy to phone using USB or use airdroid app.
If you still have probs then let me know and I can give more detailed instructions tomorrow when I am at my laptop along with links to files needed.
scott_doyland said:
Put latest superSU zip on /sdcard on phone. Copy across to phone using USB or use airdroid app. Search internet for superSU zip by chainfire developer.
Flash custom recovery CWM (search forum for it). Be sure to get the one for 4.4.2 bootloader.
Boot into CWM recovery (boot to bootloader and choose recovery option using UP volume button) and choose to flash a zip file and then pick the superSU zip.
You are now rooted and have a custom recovery.
For titanium backup, either copy to phone using USB or use airdroid app.
If you still have probs then let me know and I can give more detailed instructions tomorrow when I am at my laptop along with links to files needed.
Click to expand...
Click to collapse
Thank you very much for your help. Just a few questions if you dont mind. How do I put the SuperSU zip on the /sdcard part of the phone? When I access my phone via the pc, i cant find that folder.
Also, how do I go about flashing the custom recovery CWM. I don't know how to do this. The rest I should be OK with.
Thanks again pal
Go to android development section and follow the cwm 6.0.4.6 guide you can get the latest supersu from chainfire website just DL the zip plug your phone in and open your device and place the zip there. Then when you flash cwm don't reboot just move on to updating SD card and flash the super Su zip
Sent from my XT1034 using xda app-developers app
tiger123uk said:
Thank you very much for your help. Just a few questions if you dont mind. How do I put the SuperSU zip on the /sdcard part of the phone? When I access my phone via the pc, i cant find that folder.
Also, how do I go about flashing the custom recovery CWM. I don't know how to do this. The rest I should be OK with.
Thanks again pal
Click to expand...
Click to collapse
When you access phone via PC do you see a list of directories, eg data, documents, pictures. If so that is the sdcard. Just put the superSU zip in any folder, or just copy it across so its not even in an actual folder. As long as its on there its fine.
If you don't see the folders then maybe you don't have the right drivers for the phone. In this case may be easiest to use airdroid app.
You may need drivers for fastboot below though anyway - not sure on windows as I use Linux. Bit of reading on forums should help with that.
CWM - have you used fastboot before? Basically fastboot is a program you put on your PC to allow you to flash images to your phone. You will enter a command like
fastboot flash recovery cwm.img
Where cwm.img is the CWM recovery file. You need to be in the bootloader to allow the phone to accept fastboot commands. The cwm.img is then flashed to the phones recovery partition.
Check the forums for a link to a fastboot program, that's the easiest way to get it.
Honestly, thank you so much for your help guys, a special thanks to you scott. I kinda understand now!
Now, I did all that, but I got a problem. When I try to flash CWM by using "fastboot flash recovery recovery.img"
On my phone, it says mismatched partition size (recovery). Also, a bit off topic but when I try to restore factory settings, the phone doesn't do it properly. The android logo comes up....then it disappears, then appears again and disappears and so on.
Have I messed something up?
The partition mismatch is fine try factory reset on the phone setting not by recovery and see if that works
Sent from my XT1034 using xda app-developers app
Thank you so much guys. Got it sorted now. God bless
Sent from my XT1032 using XDA Premium 4 mobile app
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy
The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4
New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)
I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to
New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)
Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk
Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.
It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk
reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.
So, I got my moto g a few days ago, and today I decided to unlock the bootloader.
The process went fine, but when it booted up to the startup screen, everything was forceclosing (systemui, etc)
I force shut it down. After that, it would show the boot animation, going to the rippling motorola logo, and then go to a black screen. I am currently flashing to stock using fastboot, I can use fastboot to flash an alternate recovery, but that seemed to do nothing. Stock recovery does not work.
I really hope there's a simple, idiot proof way to fix this.
Anyone know what it could be?
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
bobcat913 said:
Go into bootloader, flash custom recovery and then flash a custom ROM
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
I flashed TWRP, twrp works fine, but I need to transfer a ROM to the phone, using TWRP's sideload feature doesn't work, as my phone does not show up as a device, once in adb. In device manager, it shows up as "Android" and has no drivers, when trying to use the adb sideload feature in recovery.
I ended up fixing it after all, installing the easy universal adb/fastboot drivers, and then adb pushing the rom, and gapps