This morning my phone said something about an Android update. It was fully charged so I chose to install the update and the update immediately put my phone in a bootloop. I watched some videos on how to get to recovery mode and I've done pretty much everything I can do in recovery mode (wipe cache partition, apply update from adb (can't do that), wipe data / factory reset, restore user data (can't do that), reboot system now, reboot to bootloader) and nothing works. I found a few guides on bootloops but because my phone doesn't stay on long enough to be recognized by my computer I can't follow any guide I've found so far, or do anything that uses my sdcard. What can I do to fix this?
Edit: I forgot to say what kind of phone I have. Sorry, it's a ZTE Obsidian. After taking the battery out for around 10 minutes it's starting normally but keeps saying "Android is starting... Optimizing app X of XXX" which each X a number. Is this normal?
After more research I see there is no solution for this "I'm not rooted but an android update broke my phone" situation. So I took it to the store I bought it from and the woman said I was "eligible for an upgrade" and "all" I had to do was pay $15 plus the price of a new phone (nope) or I could pay $15 and they'd send it out for repair. I thought they should fix it or replace it with the same phone for free, especially since I JUST paid my bill. But she refused so I cancelled my service. This sucks. Whoever makes these updates should have to replace people's phones when the update breaks em.
Related
Took an over teh air update while on a road trip this weekend and upon reboot, the screen is showing nothing but semi-random dithered pixels. Looks like the display is pointing at the wrong RAM or something.
Tried a hard reset. Nothing.
I would assume this was just a coincidental hardware failure and nothing to do with the update if I wasn't seeing other reports out there of exactly the same symptoms.
Spent 3 hours on live chat with Samsung (kept getting cut off and having to start all over again). They want me to send it back in - 4-5 days UPS ground there, 3-4 business days to fix, 4-5 days UPS ground back. So my one month old $500 product will be gone for 2 weeks getting fixed from the company's own SW update. (fun note - they do not appear to have actually updated any of their internal tools to support this device - I kept getting asked for a serial number then told what I provided was not correct -- even though it was the one printed on the box and the device).
Decided to see if maybe KIES could help (unlikely) and it can connect to the device and recognizes that it needs an update, but when I try to do the update, as soon as it goes to download the files, the device disconnects. Then when it reconnects, it does the same thing all over again - re-downloading the same files, losing connection, re-acquiring it, loop. loop. loop...
So basically, Samsung, epic FAIL. You really think this is how you go toe to toe with Apple?
Anyone have any advice on whether it might be possible to force the factory firmware back into this thing to see if it is indeed jsut teh firmware being horked instead of the video circuitry?
Do you have CWM recovery?
Most definately you can bring this back by flashing another kernel or ROM via Odin. If you already flashed CWM Recovery before, it's just a matter of clearing cache & dalvik cache. If not, flashing another ROM only takes 10-15 minutes if you are used to it. Or about an hour to read up and do your first flash (read the first post in the Android Development subforum. Come back here if it's not clear. Just make sure you pick the right kernel & ROM).
Mine did the same once with a previous update. It would start up eventually though (after several minutes). As mentioned in the previous post, if you can get into Recovery (hold Volume-Down and Power toghether until 2 icons appear), a wipe of the Cache and/or a factory reset will probably bring it back to life.
Samsung & software, it remains a troublesome combination .....
PS. If you have got it up and running, disable checking for new updates. Once an update has been downloaded, the Tab keeps bugging you with popups to install it, even though you tell it never to. 2 days ago, the update question popped right up on the spot i was to tab a link on a website, firing off the update instead. It immediately wrecked my Tab. Luckily i had CWM Recovery flashed earlier, so a clear cache & clear Dalvik cache solved it.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hi,
I've got Nexus 9 Stock, unrooted and bootloader locked, I got an OTA update, downloaded and installed it, when it rebooted the boot animation repeated endlessly.
It doesn't do part 2 of the boot animation it just repeats part 1, the four colored dots dancing around in circles..(is this a bootloop?)
I tried booting into safe mode without any success.
I tried wiping the cache partition but it didn't seem to do anything, it just stayed on 'formatting cache' for ages..
I rebooted, still endless boot animation. I rebooted back into fastboot and then recovery, when recovery loaded it had an error message 'cant mount cache partition'..
I tried wiping the cache partition again but got the same result, it stayed on 'formatting cache' for ages..
I rebooted back into recovery mode and tried 'formatting data/factory reset' and again it didn't seem to do anything, it just stayed on 'formatting data' for ages..
When I rebooted back into recovery it went straight back to where it left off: 'formatting data' without displaying the menu, and it stayed there for ages..
I figured, at the very least, recovery is buggered. So I tried flashing twrp via fastboot but I soon learned I can't do that while the bootloader is locked and I can't unlock the bootloader without enabling it in developer options which i can't get to because of the endless boot animation.
Help please, what should I do?
Wiping cache takes much longer on the N9 than any other device I've owned. Seriously, give it 30 minutes to one hour to complete wiping cache; don't power it off while it's doing that.
Once you're done wiping cache and rebooting you'll probably still be on 5.0.1. Your options are to wait for Google to release a new OTA, call HTC for an RMA, or flash the factory image (it can be done without overwriting user data).
I'm having the same problem. Actually, a bunch of us on the Nexus 9 product forums are having the problem too.
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!categories/nexus/nexus-9
Google seems to replacing some and referring other people to HTC. I spoke with HTC this morning and they're having me send it to them for repair.
It's probably a nand problem!!
I hope this isn't the beginning of a #nexus9bricked
Nexus 7 tabs have been having hand failures for months now. Just search twitter for #nexus7bricked
+1 to the update bricking their Nexus 9
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
ksutherland91 said:
Yep mine got bricked when I installed the OTA update on a stock locked Nexus 9 this evening. Factory reset didn't fix the issue and I can't flash 5.0.1 because of Google's asinine developer options in Lollipop.
You can't flash even a signed factory image without selecting a Developer Option allowing for ADB to unlock the boot loader. So if you can't boot into the OS, you can't use Recovery to flash an image. Every Android device I've ever owned has been near indestructible because you could always refresh from recovery. Not so in Lollipop anymore, even with a stock device, unless you have the foresight to preemptively select the Developer Option allowing the boot loader to be unlocked.
I called HTC and they knew my problem almost before I got on the call given the call volume they're getting. They said I had two options: wait for an impending Google update fixing the issue coming sometime this weekend/early next week or RMA it to the repair center. They expect the update this weekend, and if I RMA it, that will take 7-10 business days and the repair center will simply be waiting for this imminent update fix from Google.
The rep could not explain to me how Google is going to issue an update to fix a boot loop on a device that can't be flashed, so I'll believe it when I see it. Part of me thinks they've been totally sandbagged with calls on this tonight and know they can't possibly repair/replace this many devices in a timely manner.
Click to expand...
Click to collapse
I also believe they are pretty busy with this issue. After 4 calls over 12 hours, I finally have an RMA and have the privilege of sending them my device to get repaired. Now, I have to wait 2 days for them to send me the shipping labels (they are covering shipping) and then 7-10 days for the repair.
What a PITA for a "premium" device.
Yeah they suggested I call back tomorrow or Saturday for updates on when this Google fix is coming about. The Nexus support agent I chatted with at Google says he's unaware of any impending update to fix this issue.
Right now I'm afraid I'm going to call HTC in a day or two and find out I have to send it in, and then I'll start the whole process 2 days later than I could have.
HTC live chat: guy said, that they repair using fastboot only. Imho, service command for flash on locked bootloader is present and hidden under OEM section.
Phone shop couldn't reinstall firmware. I'll sent it back to HTC to fix.
Meanwhile, I solved my problems by buying a new tablet - Galaxy Tab S 10.5 !
Thanks for all the replies, best of luck to everyone else
Now I can get back to wasting time and energy playing clash of clans hehe.
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.
IDK if this is the correct area for this, but Imma try here anyways. My friend upgraded his old S8 to the S21 5G about 2-3 months ago and has been having problems since a Samsung firmware update said his device had an error that needed to be repaired and had pronmpted min to check for an update, which it apparently found, and he had attempted to download and install it while he slept. Well, he woke up to find that his phone was now on the Odin screen for some reason. He took it to a T-Mobile tech center and they were able to get past the Odin screen by doing a Soft-Reset (Power+Vol Down, then Power=Vol Up after the device shut off) and it had worked for about a month. Queue the current issue... He's right back where he started, supposed device error, update found, attempted download and install while he slept, and waking up to the Odin screen. Only this time, doing a Soft-Reset does nothing. We've tried multiple tech centers and they all say the only solution is a full firmware reinstall, or to send the device in to be serviced, either way, that's the cause of the next issue. He has never used a Cloud service of any kind to back up anything on his device, and in doing a reset or service, he'll lose everything on his device, which includes numbers of recent friends and co-workers, photos that had been transfered from his old S8 to the internal storage since the S21 doesnt have Sd/Tf support, and a ton of other important infot hat he can't just lose in the process. Is there anyway to figure out how to potentially install a firmware w/o losing all the internal storage or some off-device program that could remove them. I have tried many different programs that say they can do what we're trying to do, but none have worked or have been up-to-date enough to even support the S21. I'll attach a couple files to show what I recorded of the kernel and the boot screen issue from my phone of his phone.