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.
Related
I got a GPE M7 which had a botched update to lollipop where there was an error and I have to restart the phone. Since then I was unable to make any voice calling as I could not hear anything and voice dialing can also make the phone lose its reception. To get the reception back I usually have to restart it several times.
After that, I lived with it for a while, the google support told me to wipe partition cache from the recovery screen but it did not help. The y say they are unable to help me anymore. I tried to unlock the bootloader so I could flash a new ROM. I went through all the steps to get my Unlock.bin until I send the command to unlock the phone at the fastboot screen, it won't go into the screen where the phone will ask you if you really want to unlock the bootloader. So the phone remained locked.
I tried to factory reset it but now it just get stuck in the bootup screen, where the swirling color bubbles are and it won't stop. The longest I have tried is to let it sit there overnight and it used up all the battery (fully charged) and rebooting it up is still in the swirling bubble screen.
I finally tried HTC support and they say I could try to flash their ROM on it. I went through all their steps to flash their ROM on it but it won't accept it. The ROM installer would reboot it from fastboot, with the HTC logo and when it tried to send the ROM over to the phone, it just crash (error 155) and went into recovery. Recovery said that if I can see the HTC logo, I should be able to flash the ROM again. So I did, and then this time it ssai I have less than 30% battery left (Error 120) and refuse to update it, even though I tried three times with fully charged battery (LED is green and plugged in for hours).
Now HTC support is just ignoring after they instruct me to factory reset it again and it just won't work. I don't know what else to do. I have been without a phone for two weeks and I can't really afford a new one right now.
My carrier is Tmobile.
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.
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?
I waited to write here, if the March 2020 patches solved the problem, but unfortunately it is not...
several nokia comunity users have the same problem and nokia is not responding about It.
having Nokia 8.1, I gave Nokia 7.1 to my girlfriend last year ... great smartphone, the Android 10 update work very well, but the February 2020 patch was a disaster!
Probably it didn't install well, and then the phone asked for a factory restart.
the problem is that the Factory reset did not come back to a pre-February patch state, but always brings it to the point of "restarting the phone to finish installing the February patch".
and immediately the restart is requested, which can be postponed, but not indefinitely, so after fifteen days the smartphone restarts by itself, and freezes again asking for a factory reset!
in an endless loop!
I think I have to do a system flash to bring the phone back to a previous stable state, right?
Can you help me on the procedure to follow?
I have never unlocked the bootloader and all the rest
thank you guys
My friend has the same issue.
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
thanks for the answer!
the guarantee is still active,
I think I will send it to nokia assistance, as soon as next week I will be able to see my girlfriend (for the emergency covid19 I haven't seen her for 60 days, but next week there is the unlock down).
meanwhile I took for her a Nokia 4.2 to be used as a replacement.
I hope Nokia's lab assistance will flash the system quickly and better than what I could do
PCIHD said:
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
Click to expand...
Click to collapse
Can you show me to a thread or video for option 2)?
Morning Folks.
3 Days ago (Saturday) I received my Pixel 6 (Vodafone UK), Sunday evening, the device turned itself off, only noticed in the morning when the alarm didn't go off.
I eventually received my E-Sim from Vodafone yesterday (Monday Morning), All was fine during the day until the evening. The device rebooted, after the reboot I entered my pin, and non of the apps would work, the device rebooted again. After this reboot then I would have 3-5 seconds before it would reboot again.
Went into Fastboot and WIpe/Formatted device... This did not make any difference, it would reboot at the welcome screen instead.
My questions.
Has anyone came across this before on the pixel 6?
The last phone I updated firmware was the Galaxy I5700, and I noticed ADB on the fastboot section, Is it possible to get a Vodafone UK Image for the pixel 6 and reflash it?
The only way this could happen is that you tried to boot a modified boot.img or the system UI was changed.
I do not think you are telling us the whole story here. Missing information.
Try booting in SAFE MODE.
vandyman said:
The only way this could happen is that you tried to boot a modified boot.img or the system UI was changed.
I do not think you are telling us the whole story here. Missing information.
Try booting in SAFE MODE.
Click to expand...
Click to collapse
Afternoon
Thanks for the reply. Nope literally the above happened as is, I've no interest in a new ROM, changing any file system, or changing UI... Actually one thing I did change was changing the Icons to Themed Icons(beta mode) or something, this was within Settings, but could not tell you exactly where. Wouldn't think this would affect anything else tho.
I am unable to boot into safe mode. I have wiped the device, and the next reboot takes me to the Welcome Screen (Get your Device Ready) then a few seconds later, it reboots. The reboot afterwards might not even take me to the welcome screen and just get stuck on the Google Logo.
Anyway I've nipped to Vodafone today and the guy at the desk checked it out, going back for a warranty job, he managed to get it to boot to the main screen, but the screen was doing things by its self, and again rebooting for him. See how this goes and maybe they will find the issue.