Develop Bugs

[Q] Help - OTA JB Update today broke my phone

Hi Guys,
I have CID__001 in the UK and received the JB update this morning - great, I've been waiting for it for months, that's why I didn't bother rooting my phone like i did with my desire.
So my phone boots up and EVERYTHING keeps crashing. com.android.phone, android.process.acore, gapps, htc sync etc. Constant error messages, so i can't get rid of them to do anything. The SIM card won't prepare, the home screens never load so I can't access my apps, the battery is draining like crazy, I can't sync my contacts because sync crashes, I called the phone from my landline, the landline phone rang, but the HOX didn't. I also can't access my files on the phone through the computer, the computer recognises it's there, but when i click on it it says 0 files. I don't have a backup, but if i have to lose them to get my phone working, so be it. It's completely messed up.
I have rebooted several times, also in safe mode, but it always happens. I also tried running the RUU because I now have HBOOT 1.36 but it told me it was the wrong RUU and wouldn't update.
I wanted to copy the update file onto the external storage and rename it update.zip so I could flash it from recovery, but i can't access the files through the phone or the computer so that was a bust.
I cleared the cache from the recovery menu, still no joy.
I haven't done a factory reset yet, because I don't want to lose everything and I don't think it would work if I get all the crashes in safe mode.
I need some help, I've got some experience rooting/flashing etc, I did it a lot on my desire, but I am stuck here. I'd like to be able to fix it myself, as all HTC will do is send me a refurbished phone, charge me for the pleasure and I'll lose my data anyway.
My bootloader is unlocked, but I never rooted or flashed anything on it, it was purely stock with an unlocked bootloader.
Any suggestions? I really don't know where to go from here. Typical that I didn't meddle with my phone so I could have the official update and it messes up my phone.

Have you got stock recovery or custom?
Sent from my HTC One X using xda premium

stock

Could be you need a factory reset which is what i would do.

Yep, its gonna have to be a factory reset, if it still don't work contact HTC clearly a fault of theirs, cant see how unlocked bootloader can play a part..

Are you 100% its stock coz you can't clear cache from stock recovery... You need custom recovery.
Sent from my HTC One X using xda premium

Factory reset worked
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!

cec24 said:
Yes, my recovery is definitely stock. There aren't many options, but erase cache is one of them.
Factory reset worked. I have lost everything, had to reset from the fastboot screen (not sure what it's called) because it would not work from the phone settings - whatever was necessary to factory reset my phone kept crashing. Resetting from there also formatted my external storage, all my photos and music and everything are gone.
Really annoyed at HTC right now. I waited patiently for months, could have easily rooted and flashed a custom JB ROM but I waited and their update has caused me to lose everything.
Does anyone know why this would have happened or have heard of it happening to other people?
On the up-side...Jelly Bean is now rolling out in the UK!
Click to expand...
Click to collapse
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.

cuzzo94 said:
probably there was a problem with some other apps on the phone, so maybie that wasn't htc fault. But wasn't mass storage working? If yes you could backup everything before doing factory reset.
Click to expand...
Click to collapse
My phone showed up under my computer, but when I tried to access it, it said 0 files...I tried. Failed, but tried.

[Q] Gnex restarts constantly, can't do factory reset, can't reflash

Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.

Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app

I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?

I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app

same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse

Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.

Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4

What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???

Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..

If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!

7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.

I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?

Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.

fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference

Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...

I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.

Same problem by 31th December...

Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.

Same for me at the beginning of december

This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it

Update boot lock

I gave up on my Note 4, purchased a Nexus 6P, and gave my Note 4 to my father. I had used the program Gates Junior wrote to block some bloat, including the auto updater, Knox, etc..
When I factory reset the phone to set it up for my father, it immediately (before the setup program could even get the google account logged in) launched the update and updated. Upon reboot it updated again. After the second update, I checked for an update, and a third was available so I launched it. It rebooted into recovery and began installing the update. About 20% into the update, it froze. I thought perhaps it was just a long update so I put the phone down and came back somewhere well over a half-hour later, probably closer to an hour. The progress bar had not moved.
With much trepidation, I pulled the battery and rebooted. It booted into recovery and began installing the update where it promptly froze after 15 seconds at the exact same spot, around 20% done.
Is there a stock image I can apply through Odin to fix this? I thought I was pissed before about a non-rootable phone but an update-caused boot lock is infuriating.
Any assistance will be most appreciated. Thank you.

No one has any idea where to find stock images for Odin?

http://forum.xda-developers.com/showthread.php?t=3178148

Thank you, Gcounts!! That was exactly what I needed and I got the phone updated and operating properly for my father!

Google Pixel XL keeps rebooting

Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked

edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.

Scott said:
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.
Click to expand...
Click to collapse
I had a pixel xl rebooting 2-3 times a day, did exactly this, reboots persisted... Was within 14 days and got the phone swapped out. New phone does not have any reboot issues.

Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.

I noticed my phone restarted and the date was set to Jan 1st 1970 while it was in my pocket. I did a adb bugreport but could not find anything. I did find this line though check_reboot_mode: restart_reason: 0x00000000. Does the phone ask for pin only when it restarts? I have fingerprint based authentication setup but it still asks for pin from time to time, now I am wondering if those were restarts.

318sugarhill said:
Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.
Click to expand...
Click to collapse
It's generally a good idea not to restore a backup from a previous major system iteration. Anytime a new generation is introduced, one should do a clean install, as you noted in your last sentence. There are potentially a lot of system changes that can cause conflicts.

edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Hello,
I had the same issue with the most recent Verizon update on my wife's Pixel. There seems to be a lot of people with Pixels having this issue as well. I needed to return it for a new one...Verizon is aware of the issue as they did not hesitate to replace the unit.
Cheers

Helpful tip, hopefully.
If you want to test the effect of installed apps, Pixels can boot into "safe mode," where installed apps are disabled temporarily. Press and hold power button to open a reboot menu, then press and hold "Power off" button. A menu will open to allow booting into "safe mode."
https://support.google.com/pixelphone/answer/2852139?hl=en

Do you have any apps under beta? I was using around 6-8 apps in beta, I unsubscribed out of the beta and reinstalled all the apps. My phone stopped rebooting.
P.S. My phone was rebooting even under safe mode!

Android 10 - Factory reset needed?

Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?

I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good

razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.

is it worth factory resetting device with this latest update?

Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.

Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.

bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit

animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.

For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.

jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.

v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.

bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now

animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.

v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?

animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.