Droid 4 recovery help - Motorola Droid 4

Lost the keyboard lights on my droid 4 running ics 4.1.2 so I decided to upgrade to kitkat, which should have and did fix the problem. Upgraded to liquidsmooth 3.1 and the 4.4.4 gapps. Got most everything vital configured but noticed the unit started having frequent lockups after the first day. 3 days later the screen is unresponsive most of the time. Rebooting boots up to safestrap, but screen is still unresponsive to get into recovery mode so it continues on and boots up the liquidsmooth rom 4.4.4. Rom slot 0 is stock and liquidsmooth is in rom slot 1. So decided to factory reset using power and vol up/vol down keys and I can get into the firmware menu but selecting recovery results in a toes up droid, then a reboot into 4.4.4. Is there any other way to do a factory reset other than within the OS, which I can't seem to get into? Is it possible to adb into the device w/o usb debugging enabled or to do a reset remotely? Thanks in advance for any help offered.

manfone said:
Lost the keyboard lights on my droid 4 running ics 4.1.2 so I decided to upgrade to kitkat, which should have and did fix the problem. Upgraded to liquidsmooth 3.1 and the 4.4.4 gapps. Got most everything vital configured but noticed the unit started having frequent lockups after the first day. 3 days later the screen is unresponsive most of the time. Rebooting boots up to safestrap, but screen is still unresponsive to get into recovery mode so it continues on and boots up the liquidsmooth rom 4.4.4. Rom slot 0 is stock and liquidsmooth is in rom slot 1. So decided to factory reset using power and vol up/vol down keys and I can get into the firmware menu but selecting recovery results in a toes up droid, then a reboot into 4.4.4. Is there any other way to do a factory reset other than within the OS, which I can't seem to get into? Is it possible to adb into the device w/o usb debugging enabled or to do a reset remotely? Thanks in advance for any help offered.
Click to expand...
Click to collapse
All factory reset does in stock recovery, is wipe user data, and reset defaults.
It will not restore changes made with root, nor will it reset rom slots other than stock.
Use factory reset options in safestrap or
If you want to restore factory setting, flash firmware/xml with rsd lite.
Sent from my XT862 using Tapatalk

Related

Phone suddenly acting up need some help

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.

Device is stuck on boot logo

Hello, I have a problem with my Galaxy Note and I don't know what to do.
A few hours ago I tried to start the device as I usually do after I turn it off, but the device does not turn on and only stays stuck on this screen: "Samsung galaxy note n7000".
I'm running this Rom: "[ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1".
I have the ability to log into CWM by the combination of the known keys
I hope you guys can help me, thanks in advance.
(Note: The battery is charged and i also tried to remove it and put it back in.)
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Had same problem by loosing power. The device wont boot anymore. Fix per, reinstall without wipe did not work. Switch rom
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
terminator_5505 said:
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Click to expand...
Click to collapse
How can i replace the kernel and reinstall the rom if I cannot see the device on my computer when it's connected?
nokiamodeln91 said:
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Click to expand...
Click to collapse
I've already tried both methods you have specified and none of them worked.
My attempt to make a Nandroid backup has failed and the CWM said something like "backup of /data failed".
alvinhaw said:
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ?press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
Click to expand...
Click to collapse
Hi, this is not the first time I try to boot the device after installing a new rom.
I'm with this rom for a few weeks now and the problem occurred only yesterday.
This is well known problem with xlsc rom. U have to wipe everything and to flash rom. There are some solutions with backup/restore but they didn't work for me.
So, complete WIPE, and than flash!!
Backup of data failed because of insufficient space. Make backup to internal if there is more space.
i have the same problem since i full wipe and flashed asylums 20130302 build. after doing a full wipe and clean install, i started downloading my regular apps from playstore and suddenly it turned off just like when you remove the battery.
i tried the following::
1. full wipe and installed the rom -- it boots up few minutes then shuts off and wont boot up without charger
2. restored from nandroid -- same as above
3. full wipe and installed previous builds -- same
4. full wipe + flashed latest build 20130303 + latest gaps for JB 4.2 -- same
5. check battery stat -- ok
whenever it shuts off, it wont turn back on unless without a charger. it just shuts off at random. this is the second day I'm experiencing it and its frustrating.
any help? thanks
edit:: btw it shuts off at boot animation
In the other thread where you asked this question too there are members who replaced their battery and solved it this way.
Maybe you should try this and replace the battery.
Good luck.
I got same issue and I'm for kill someone. Why these problems on a official rom?

[Q] Can't factory reset Moto X

I wanted to perform a factory reset because I keep getting really high Android OS usage on my phone. However, when I went to settings -> backup and rest -> factory reset, it didn't reset my phone; it just rebooted again. Then I tried to reset it by booting into recovery, so I powered up the phone holding the volume down button, scrolled to the recovery section, pressed up to select it, and it just made my phone restart again. I don't know why my phone won't let me perform a factory reset, could someone help me out? It is rooted and has titanium backup and greenify installed, but that's about it.
PwnMyMoto hijacks stock recovery. You'll need to uninstall it to get the recovery back to factory reset.
fruitytoilet said:
I wanted to perform a factory reset because I keep getting really high Android OS usage on my phone. However, when I went to settings -> backup and rest -> factory reset, it didn't reset my phone; it just rebooted again. Then I tried to reset it by booting into recovery, so I powered up the phone holding the volume down button, scrolled to the recovery section, pressed up to select it, and it just made my phone restart again. I don't know why my phone won't let me perform a factory reset, could someone help me out? It is rooted and has titanium backup and greenify installed, but that's about it.
Click to expand...
Click to collapse
don't think you can uninstall pwnmymoto because it already uninstalled itself after it rooted your phone. You will have to flash stock frimware on the device using RSDlite. tutorial found here http://forum.xda-developers.com/showthread.php?t=2446515
for high android os usage it might be because of the wifi router you are connected to fyi. try running on no wifi for a day or a night or whatever and see if that doesn't change. There seems to be an issue with some routers that cause the usage to be extremely high. I'm having the problem currently because of my wifi router.
Hello
I am from europe......
Search my Moto x (rooted) Stock rom.....i want recovery, i want factory reset..
I install Morelocale2 set hungarian languane, and useless controll not working(((( uninstall program, set English Us languane, ...........not work....
message : sorry there seem to be data issues..............
( telefon Claro Puerto Rico network....Stock Firmware: 2 choice..Claro Chile and Columbia,,??????? true?? false????
help pls........:crying:
jayboyyyy said:
don't think you can uninstall pwnmymoto because it already uninstalled itself after it rooted your phone. You will have to flash stock frimware on the device using RSDlite. tutorial found here http://forum.xda-developers.com/showthread.php?t=2446515
for high android os usage it might be because of the wifi router you are connected to fyi. try running on no wifi for a day or a night or whatever and see if that doesn't change. There seems to be an issue with some routers that cause the usage to be extremely high. I'm having the problem currently because of my wifi router.
Click to expand...
Click to collapse
any update on this? I'm in a similar situation where I want to do a factory reset, but I can't flash any Rom because I am on republic wireless. is flashing the firmware the and as flashing a new Rom?
warrenis1234 said:
any update on this? I'm in a similar situation where I want to do a factory reset, but I can't flash any Rom because I am on republic wireless. is flashing the firmware the and as flashing a new Rom?
Click to expand...
Click to collapse
you can always flash the fw for your device onto your phone. you may not be able to flash an older version of a fw for your phone but you can always flash a current version. if you use rsdlite to do a full factory reset it will work. you just can't do a factory reset through the recovery mode in your phone because pwnmymoto hikacked it so its no longer there.
if you have a locked bootloader and you want to do a factory reset or flash a rom you need to install Safestrap
here is a link to the thread all about it
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/

Solved - Locked Boot Screen, Unable To Access Custom Recovery Image.

Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.

Phone in bootloop please help...

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.

Categories

Resources