I've flashed "Hammerhead-lrx21o-factory-01315e08" via ADB five times now. Unlocked, stock, unrooted, no recovery. Factory reset following install. After an hour or so, the phone freezes up and becomes useless. After rebooting, the same thing happens within minutes. Tried re-downloading lrx21o and switching computers; exactly the same outcome.
This is the stock image from the Google website. Each time, the install goes perfectly with no error messages. Each time I factory reset following installation.
I don't like to proliferate threads, but I have to vent my exasperation over this fundamentally broken release.
Who else has had Lollipop turn their N5 into a paperweight?
Related
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Last night I decided to switch to ART from Dalvick runtime. Ever since, when android finishes loading, I get the error message "Unfortunately, Android System has Stopped." I've tried returning to stock (I'm rooted) and neither of my windows computers can see my phone which is weird because I unrooted my LG G3 recently with no problems. I've performed a hard (factory) reset numerous times. Sometimes the android system loads up OK but as soon as I reboot or power down I have the error message again. I'm at my wit's end. I can't return the phone because it's still rooted and I can't get it to work. When it boots, the LG screen appears normally. The At&t screen appears normally. Please help! I'm desperate.
If you're okay with losing info, give this a shot. I'm not sure exactly why it's doing this unless you had xposed framework before. Anyway, follow the steps and it should fix it. I'm not sure if you've tried going into the boot loader yet and doing a factory reset through there. So you can try whatever you like
http://forum.xda-developers.com/showthread.php?t=2785089
I can't get a computer to recognize the phone. I have tried a hard reset and I still get the error message. Any other ideas?
I had the same issue after I tinkered with something I shouldn't have tinkered with. I think I installed GravityBox, didn't like what it did, tried to factory reset, and started getting the Android System error consistently.
That link mcnick posted will serve you well. I would however use this thread since it's tailor made for the AT&T variant.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
nikulogical said:
- A few days ago my phone freezes while I am using it, and its stuck on the google screen. at this point, it's on 5.0.1 unrooted, unlocked bootloader.
- I try going into recovery and wiping cache and doing factory reset. I keep getting errors but eventually the wipes work. Still doesn't boot though. So I do this a few times. I got it to boot twice but both times it froze within 5 mins and back to the same thing.
- I fastboot 5.0.1 factory image, goes through. but still no dice - stuck on google boot screen.
- I research and find out about the infamous power button problem. it doesn't seem like thats the issue with mine because the buttons seem to work fine. whatever, i take it to a local repair shop (phone is out of warranty) and the next day they inform me that there is no physical issue and that their software reset worked. they used the LG factory firmware way of resetting the device.
- Got the device back, used it for a while. It was fine for the time being but it was on 4.4.3 and I got the 4.4.4 update. I go and unlock bootloader, flash 5.0.1 factory image and push TWRP+root.
- Doesn't boot again, stuck on google logo
- I tried a whole bunch of stuff and nothing worked. I ended up with flashing 4.4.3 factory image in fastboot and relocking the bootloader so I could take it back to the shop the next day. At this point the phone wasn't even turning on.
- The next day (today), I tried turning it on, nothing. I put it in the charger for a while, then turned it on.... and it booted! used it for a while, it's fine.
- Did 4.4.4 system update, it's fine.
- Unlocked bootloader, it's fine.
- Tried to flash 5.0.1 factory image and again same issue - stuck on google screen.
- Been dicking around the last few hours trying to fix it ended with flashing 4.4.3 again but same issue, I then put the phone into download mode and connect to the computer but I got a green screen something about DemiGod Watchdog HW reset. I did the reset.
- Phone booted up again! Did the 4.4.4 system update and then it started freezing and rebooting withing few seconds of use. Now it's back to being stuck on google screen.
- I am obvious gonna bring it back to the shop now but any idea as to what is happening here?
Click to expand...
Click to collapse
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
gamer.11 said:
1.I presume the "DemiGod Watchdog HW reset" green screen came up after you gave the phone for HW servicing? If so then they could have knocked around the parts a bit to cause a hardware issue(not sure what causes it)
2.Check the MD5 of the 5.0.1 factory image.
3.Instead of factory image use the OTA zip file and flash in stock recovery.
Click to expand...
Click to collapse
So I used the LG tool myself to flash the firmware (4.4.3 is the only one available) and it worked fine. Updated to 4.4.4. Fine.
I then adb sideload the 4.4.4 - 5.0.1, and stuck on google logo again .................im pulling my hair out this is so weird.
1) yes this was after.
2)i tried adb sideload.. ill try that good idea.
can't flash ota.zip in recovery. only adb and that didn't work.
think i'm just gonna hang on to 4.4.4 then for now. tried everything.
Just an update. I was running 4.4.4 just fine but the phone froze and went back to the Google screen again.
bump
Might as well rma
Hello fellow xda-ers,
I have a OnePlus One, but i cannot seem to update the phone.
What is the exact problem?
- there is a system update ready, so i download the update and it asks me to install and then it tries to reboot
- the phone shuts down and doesn't reboot, i have to manually turn the phone off which makes the update sequence stop.
- the phone tells me again theres a update, but it doesnt reboot after it shuts down.
- even just giving the phone the command to reboot, just shuts the phone off and the phone doesn't reboot.
What did i try?
- via oneplus toolkit (mac) i flashed it to stock default, but still the problem persists.
- i flashed a 5.1.1. firmware straight from cyanogen mod, but still the problem persists.
- i flashed a custom recovery (while unchecking the update cm recovery), but the problem still persists.
I don't know what to do... Anybody have advice? It would be much appreciated.
I am pretty aware of what to do and not to do, i have been flashing phones since the iPhone 3gs. But this is just odd.
I was having similar problem. Except mine was booting into the bootloader. From there I tried to manually install the update. It kept failing so I gave up. Then about a week later (today) I let it try to install and it seemed to be working, except when it finally booted back up, it had completely wiped my phone!!! Now I'm midway though reinstalling all my apps and it gives me the "There's an update available for you phone". So apparently it didn't even update in that process.
I've got the exact same problem here.
Cant flash Cyanogen, recovery faulty & weird crashes in stock on refurbished Nexus 5
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
napstr said:
Hey guys,
so I recently got a "refurbished" replacement for my Nexus 5 and I decided since im starting out fresh (can't access the data on the old one), I'll try out Cyanogen mod.
I can assure you that I followed all the instructions exactly. At some point I checked every download for his checksums and all were ok.
Each time I started the process by flashing a factory image (flash-all.bat), to have a clean start.
I also tried to wipe cache/dalvik cache/data afterwards, but not always. This didn't change the behavior.
These things happened to me while trying to accomplish the task, and working around the issues as they arised:
Flashing TWRP: High (3 of 4) chance that TWRP wouldn't even start up, the phone would hang and just flash the TWRP background picture on screen.
When I did get through to TWRP, applying the Cyanogenmod .zip got stuck at "patching system image unconditionally". Let it go on for hours.
I figured that TWRP was broken and tried Clockworkmod instead. CWM at least always started after flashing it. But same as TWRP, it failed in installing the Cyanogenmod .zip. I tried putting it onto the phone by going into the stock android and then through adb push command, but also through sideloading directly into CWM.
What I noticed when going into the stock ROM was, that a lot of Google processes were failing during the initial setup (where it wants to know ur WiFi, date, Google acc, etc), like Maps, Settings, Play Services, and some others. Sometimes they were failing so hard it was impossible to type in the WiFi passphrase because the notifications of different "xxx has stopped working" were coming to fast, sometimes not a single one was failing. I could not find any pattern to this. When they were failing so hard I couldn't get through the initial setup I would just flash the stock again, until I got only some of them failing, or none at all.
Back to CWM and installing the Cyanogenmod .zip:
It failed with different errors. I got status 0, status 1, I think I once got status 6 or 7, but half of the time it hanged exactly where TWRP was hanging. The errors were random. After getting status X, I would sideload it right again, to get other status Y, sideload again, to get the hang. Could not recognize a pattern.
During this I switched USB ports, and cables, and even tried using my laptop instead of the desktop. One of the cables was faulty, it didn't even allow a connection, but any other setup showed the same behaviour.
Is there anything else I can/should try? Is it my fault, or is the phone bad?
Assuming the phone is bad, I suppose I still could get a stock running without the crashes, so it would _feel_ like the phone is alright (which is what Google probably did before sending it out again as "refurbished"), but I think there would be errors in the future, also I don't want a phone with such an uncertainty. Would they swap it? Also, it is a LG-D820, which means it might have issues with european LTE, haven't gotten to trying that out since I don't use LTE right now, nor will I in the near future.
Best regards,
napster
Click to expand...
Click to collapse
Hi.
According to what you say, it seems an hardware problem of you phone. Don't know if it may help but you can try installing an older factory image (for example kitkat) and seeing if the "force closing" problems are still there. If your phone is ok it should be able to run a factory image at least.
Download the nexus root toolkit, create a nandroid backup, then when either in CWM or TWRP wipe everything off the phone then try to flash a ASOP rom like Cataclysm if nothing else works then I don't know how to help sorry-.-
So I tried to get the stock ROM up and running again, and it seems even that is not possible. Several processes keep crashing during various tasks, even when idling. After having a short chat with Google Support about the issues I got an RMA offered, so things are cool. I locked the phone again, set the tamper-bit to false and wiped everything.