I can't get to my recovery at all. When I try to reboot to recovery my phone just gets the motorola logo and it turns on normally. I've tried flashing different recoveries on rom manager and alternative one but nothing works. I tried installing sp recovery using termunal emulator and it just keeps saying failed. No memory. Has anyone had this problem before? How can I fix it?
try pressing "x"(hold) on the keypad and the power button (hold), an let go of the power button once u see the motorola logo
First off, rooted? If you aren't sure you probably aren't or you can go into Terminal Emulator and type su and hit enter. If the symbol changes from a $ to a # you're indeed rooted. If not, unstableapps.com and get easyroot. If you are, try flashing SP and then back to Clockwork. Then keep reflashing Clockwork until it flashes very quickly. Sometimes I have to keep flashing and flashing to get it to stick.
I am rooted. I've been flashing roms for a long time. I even tried flashing that custom recovery that's been floating around but it just says theirs no memory to flash the recovery. Ill give that a try. Thanks
Related
Ok so I have an unlocked Nexus One that I rooted when I first got the phone 6 months ago. I've been running CM6 no problems at all, everything has been great.
Heres where my problem starts I decided to flash the stock frf91 image onto the phone and did not check superuser permissions or whatever option they gave me before i did it. I was doing this because I thought I was selling my phone. Now I'm not and want to go back to CM6.
The problem is I cant get into recovery at all I get the error with the ! in a triangle with android standing next to it. I've searched everywhere and tried everything. Fastboot and ADB gives me errors like waiting for device (even though my drivers are up to date and it recognizes the phone?) or status failed too many links.
I tried doing a backup from my nandroid information through my nandroid backups on my computer (aka pulling system.img etc) I tried going through the terminal but Im getting denied superuser permissions.
Im just not sure where to go from here ive looked through so many articles and threads and posts and im very confused.
After I flashed the stock image I thought i would still be able to boot into recovery but i guess i dont have recovery? I try to flash the recovery but with no avail.
Anyone have any advice or even just somewhere to start I would really appreciate it. Thanks
When u flashed the stock rom it wasnt a rooted version so u have the stock recovery search for how to root the stock Rom once rooted u can put a custom recovery on there hope this helps
The procedures for the different handsets kind of blur together in my memory, so just want to check.
When you booted into recovery and got the "!" screen with the android did you try holding either the volume up, or volume down key <along with the power button> to bring up the menu?
The ! With the Android is the stock recovery image if I remember correctly if u press the power button the menu should pop up
Hi Folks,
I had a CyanogenMod-6.1 for Nexus One :: V6.1.0-RC1 (10/28/2010) installed on my Nexus 1.
Prior to that i was using CM6.0 RC1 stable release. Did an upgrade (with full void and nandroid backup) to try out the new features.
However this afternoon, out of nowhere, my volume buttons and trackball started to malfunction.
i.e to say : I cannot adjust volumes in any part of the apps/phone and i can't select/click stuffs with the Trackball.
Hence, I thought of removing CM6.1. Here's the problem started.
#1. I can't boot into recovery. The phone itself will be stuck at the big "X" screen. After 5mins, it will boot into CM6.1
- Using ROM Manager i tried to reflash Clockwork Mod 2.5.1.0 for a couple of times but i still cannot get into Recovery.
Be it powering up with trackball held down, booting into recovery up via Rom Manager. Surprisingly, volume down was working together with power down was able to go into Bootloader
for me to select "Recovery", however, i still can't access Recovery.
#2. I tried using ./fastboot-mac flash recovery updatedclockwork.img also can't.
#3. I tried using Amon-RA. ./fastboot-mac flash recovery Amon-RA.img also to no avail.
#4. i used ./fastboot-mac update to load a StockFRF91 Froyo also can't get into recovery.
As of now, my phone is stuck continuously in bootloop, cannot access Recovery. I've tried almost 30+ fixes on XDA and other Android Forums but i still can't fix it.
Is there anyway, i can wipe everything inclusive of the "Corrupted Recovery" files and restore back my Nexus One?
Thank you all please save my phone! :'(
Dude I feel your pain. I have the exact same problem. I wonder if it is a CM6 issue?
Has anyone not been able to boot into recovery mode on their phone. When I go into ROM manager and try to change ROMS or something it just turns off?
are you with S-on or S-off?
Probly S-off. I'm rooted with Fresh ROM 2.4.0 by Flipz.
First of all, you aren't bricked just because you can't get to recovery and/or change ROMs. If your phone shows signs of life, which from the sounds of it you can boot it up, you're not bricked.
Second, If you answer "probably" to the question "are you S-OFF?" you aren't. You would know if you were because you actually have to DO it. It doesn't happen by rooting or flashing a ROM. It's a whole separate thing.
Can you get into recovery by holding down "home" and "power" on boot? I press home right before I press power. If that doesn't get you into recovery, use ROM manager to reflash the recovery then try again.
Ok thanks for the tips. I'm going to instal the SDK and see what I can do then. I guess it's not totaly bricked just has some errors with the ROM or something because when I go into ROM manager and try to flash recovery mode it just turns off and then doesn't come back on. I can't go into Hboot or recovery mode from just turning it on because my on button is broke and, I don't want to take it back to the Sprint store to get it fixed until I get the custom ROM off of it so they can work on it.
HTC_HERO!!! said:
Ok thanks for the tips. I'm going to instal the SDK and see what I can do then. I guess it's not totaly bricked just has some errors with the ROM or something because when I go into ROM manager and try to flash recovery mode it just turns off and then doesn't come back on. I can't go into Hboot or recovery mode from just turning it on because my on button is broke and, I don't want to take it back to the Sprint store to get it fixed until I get the custom ROM off of it so they can work on it.
Click to expand...
Click to collapse
Why not just forget using Rom Manager and turn off phone and restart holding volume key down? Rom Manager isn't the only way to get into recovery. Once you are at h-boot screen, push home button and you are in recovery - you can flash a new zip or restore a nandroid back up (I hope you backed up something) .
Sent from my HTC Hero CDMA using XDA App
I backed up nothing. My on button is broken so I cant go into recovery that way...
I need to take it to the Sprint store but I don't want to have it rooted.
Once you get the sdk running, you could try "adb reboot recovery" and see if you have one, if not, you can flash a recovery with "adb shell flash_image recovery /sdcard/nameofyourrecovery.img" assuming you have a recovery image on the base of your sd, and where it says nameofyourrecovery you put in, well, the name of your recovery.
On a side note, you don't really want recovery from the sounds of it, you want the htc drivers installed on your comp, and the latest RUU.exe, which will unroot your phone and return it to stock.
Hey I figured it out I went to SDK and enterned some commands to flash a new ROM but it was saying that I didn't have enough space on my phone, so I found out that some how I had deleted the recovery image binary. SO I downloaded that and installed it and everything was all good.
Thanks people for all the info.
Sent from my HERO200 using XDA Premium App
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.
Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode
Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
usafmunk said:
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
Click to expand...
Click to collapse
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
mjones73 said:
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
Click to expand...
Click to collapse
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
usafmunk said:
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
Click to expand...
Click to collapse
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
usafmunk said:
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
Click to expand...
Click to collapse
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
TheOriginalKyle said:
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
Click to expand...
Click to collapse
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
usafmunk said:
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
Click to expand...
Click to collapse
Well new update: I was able to fix it! The problem was my own ignorance. I was following some Googl'd instructions to get the device into download mode that were incorrect. Once I saw the correct ones, I was able to get into Download Mode and revert to stock from there.