I have a W150 which was *very* slow and not working correctly. Try and open the Play store? Nope, returns to menu. Go to settings and factory reset? Returns to the menu. Try to get into recovery? Black screen. So I figured I'd nuke the storage and flash the original ROM over it.
Downloaded the factory ROM from XDA. Erased recovery, boot, cache, userdata, recovery and system. Flashed recovery, boot and system, then rebooted. It booted up into WearOS 1.5 just fine - connected to the phone and set it up. Downloaded the WearOS 2.0 OTA update, installed fine. Amazingly responsive again, just like when I first got it. Update said it was done with version 2.0.0.153815175 - no further updates available. I had 2.35 before.
I unlocked it, picked up the 2.35 OTA update from XDA and used adb to sideload it - this resulted in a constant ly animating Google logo screen. (It was running 2.35 before but picked it up OTA).
Back to fastboot, wipe, reinstall factory ROM. Boot up, set up, all good. Download the 2.0 OTA update, it reboots for the install and never comes back up. Flashes the LG logo, then black screen. Neither fastboot or adb see it.
I tried letting it charge up to 100% before attempting the install, and also tried the install while it was connected to power, but same result. If I boot it into fastboot, I can wipe and reinstall 1.5 and it works fine. I can also unlock and install TWRP which works fine. Trying to get into stock recovery results in a black screen, even with 1.5.
I suspected the battery but it's still good for two days of light use, and I was keeping it charged while doing all of this. (I have tried applying the update on battery power only, no luck).
Any help appreciated!
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.
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.
Rooted ok. I went to install a clockworkmod recovery so I could backup my current ROM before I try flashing something new. Oh, I need SDK, ok, installed. Oh, I need platform-tools, ok, installed.
So I run that and then the phone reboots to a screen saying AP fastboot flash mode. I am able to get the phone working with the 3 button method; phone runs fine, but reboot goes to fastboot screen.
I installed ROM Manager. I think I properly flashed CWM, but no change.
My bootloader was locked. So I worked around, motopacalypse; now bootloader is unlocked.
Currently my computer does not show the phone in Explorer (?!).
I flashed cwm again successfully. No change.
How can I clean up this fastboot problem?
Atrix HD android 4.0.4
System version: 77.12.22.MB886.att.en.us
Also the battery icon has a question mark.
Going with more trial and error; in ROM Manager, I chose reset permissions. A flurry of code goes by. Then it suggests I reboot. I go to shut down, but the phone will not. It now perpetually shows Shutting down spinning circle. What has happened?
Boot loop probably. Just hold all power button forever .after it shuts down,hold all three buttons to get to ap again. Then chose recovery.
Sent from my ATRIX HD using Tapatalk
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.
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