So i wanted a new rom for the awesome features so after i had rooted and installed twrp custom recovery i downloaded cm12 then created a nandroid. I put my phone into recovery wiped everything except internal storage and installed cm12 and gapps. This is where my problems started, as much as i liked the new rom it wasnt connecting to my cellular network so i thought ok ill just recover my nandroid so i wiped everything except the internal storage and then started the recovery when it finished i rebooted and it goes to the warning bootloader unlocked screen and sits for about 15 seconds the goes black and repeats. My phone is a motorola moto x 2014 victara, any help is much appreciated.
Please give us more details:
1) can you access recovery? Try holding the "power" button for like 20 seconds and trying to reboot into recovery when the phone boots.
2) can you access fastboot mode on the phone? maybe you lost your custom recovery but can access the bootloader and that makes things easier.
3) what is your device number? (xt1097, xt1095, xt1092, etc)
You are going to want to factory reset. Most times coming from a customer rom to another or even back to stock you will need to do a factory reset in order to wipe out anything that may have been left over that could cause issues.
Related
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
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...!!!
well, i did not think something like this was possible...
I was on stock modded, and i wanted give to the AOSP rom a second chance, i flashed a wrong moto camera .zip (by mistake) from here http://forum.xda-developers.com/android/apps-games/app-motorola-camera-5-0-7-1-material-t3007246 instead of one i have been using... and I did'nt note that was for 4.4 rom (i had it for my brother's phone) and then after been on the bootanimation for like 5 minutes the phone turned off and only booted to bootloader and recovery, i was not able to wipe/format data and cache (the phone rebooted everytime) so i had to do a factory reset and then flashed via fastboot the stock 5.1 again, then started to boot only to recovery, hit the factory button at the bootloader and booted but i left it for 30 mins and nothing happend, it stays at the bootanimation... checked the data partition and its at 0mb, same cache.. tryed CM, AOSP, Stock and nothing is working plz help
Sorry for my bad english
EDIT: i solved it... flahed stock twice and wait for like 5 minutes and booted, then rebooted twice and everything is normal now
plz delete the post.. thx
Hello all. First of all, the issue I have is not major, just an annoyance that I want to get rid of.
So, I decided to flash 6.0 stock zip/update through the stock recovery but at some point it got stuck. At that moment, I was in a hurry so I had to unplug the phone and quickly flashed TWRP. I did a 5.1.1 AOSP nandroid backup before so I was all safe. But I noticed that, after successfully restoring the backup, it would boot me back into recovery whenever I tried to boot directly into system.
So basically, the only ways I found out I can boot into Android is through the bootloader and choosing Normal Powerup or doing fast reboots. And, based on what I think, everything that uses the "reboot" command, like in terminal, will kick me directly into the recovery (holding the power button and rebooting normally, doing a hard reboot, rebooting through apps or terminal, booting when phone is off or starting to charge from a depleted battery).
How can I fix this problem? Did anybody else encounter this as well? Thanks in advance!
I am having a hard time recovering from my curiosity with my XT1060, Developer's Edition (unlocked bootloader and all)
I had factory 5.1 ROM, xposed and all tweaked. But it's been months, phone's getting slow, and I'm itchy for MM...
So last night, I made a TWRP/nandroid backup onto my USB-OTG stuck, and then, installed Resurrection-Remix-M.
Works fine, until I tried to make a call. I can't hang up. After 30 seconds, the phone rebooted.
I had another guy call me. The phone rings, but the screen is blank. I cannot pick up the call. WTF? I tried turning screen back on, screen's blank. After a couple attempts to swipe blindly, power button, the phone rebooted.
At this point, I'm like WTF, that's enough. So I tried to plug in the USB-OTG and tried to restore.
TWRP does NOT see my backup. At this point, I realized that perhaps TWRP can't see the item due to MM's security structure.
So I engaged the RR's CM explorer and copy the Nandroid backup onto the built-in 32 GB . THere should be enough room.
I looked back X minutes later, the phone had rebooted itself (?!!) and it's stuck at the bootloader logo (I had replaced it with generic "White Google" logo)
I cursed a bit more, did the VOL-DOWN / POWER to bring up the Fastboot menu, and boot into recovery. I got the Team Win logo, then nothing. I waited 5 minutes. It's stuck too.
At this time, I'm cursing a blue streak. My phone has been dead for HOURS now, no end in sight.
I went back into Fastboot, did Factory (which I assume is "Factory Reset?") no effect. Still freezes both normal boot and recovery boot.
I boot back into Fastboot mode, I already have Minimal ADB and Fastboot loaded on PC, so I use that to flash the a new recovery.IMG (downloaded fresh off TWRP.ME for ghost) and rebooted. STILL FROZEN at TWRP. WTF?!?!?!
(FWIW, Ghost TWRP is still 2.8.7.0, while TWRP main is already at 3.0.2)
At this time I'm at a loss as on what to do.... I tried extracting one of the factory ROM's boot.img and flashed that via fastboot, nothing.
I just RSDLite the 292-ghost_verizon_51.... ROM onto the phone (with servicefile option). It rebooted to the bootloader warning, so flash did work, but it doesn't seem continue to boot either, but I guess I was supposed to have waited like 10 minutes just to get past the bootloader? I flashed the TWRP on there. Still waiting for TWRP to load. After a couple minutes, I decided it wasn't working.
I'm now using RSDLite with the Flashfile option (wipe out all the data). Wonder if this will do it?
EDIT: Now I'm past the bootloader logo and now it's kinda stuck on the Verizon logo, but I guess that's to be expected. Still charging... and waiting.
EDIT2: Verizon logo took about 5 minutes to boot into setup. I just hit skip / skip / skip until I got to launcher. Shut down, reboot into fastboot, flashed recovery again, and booted TWRP recovery successfully this time. (sigh)
Lessons to take away from this diversion that took HOURS away from my life... For no appreciable gain.
* Keep a flashable nandroid backup on the phone. I know it takes up GB's of space. But you'll be thanking yourself (and maybe me) when there's a problem and you need to recover, especially if you're into MM or N.
* And keep that nandroid backup UPDATED! (nightly, if possible)
* ALWAYS keep a copy of the stock ROM on your regular PC, and keep Minimal ADB/Fastboot (or whichever flavor recommended for your device) and Gapps loaded. Do update every once in a while.
* ALWAYS refer to XDA