Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Ok, so my phone is now dead. I don't know what to do..
Carrier O2 UK
Phone Model HTC HD7
Updating from nodo to mango
Problem Description: I didn't get an error code. It froze on the update at step 8 or 9 (restarting the phone) and now will not boot. It vibrates 7 times and stays on the HTC logo screen.
Please help me
It was updating for over 3 hours.
---------- Post added at 12:30 AM ---------- Previous post was at 12:00 AM ----------
Please someone help me?
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Carrier ORANGE CARAIBES
Phone Model HTC HD7
Updating from NODO TO MANGO
Error Code
Problem Description: Can't boot anymore. I don't even can turn on the phone :/ My first problem on windows phone!
Chasseur d'étoiles said:
Carrier: Rogers (Canada)
Phone Model: Samsung Focus
Updating from 7390 (I guess, the one after NODO)
Error Code : none, stuck at step 8 "Restarting your phone"
Problem Description: Phone is frozen at the Samsung logo and nothing happens from there (been there for about 30 mins).
Mango update is quite meh for me here -_-
Click to expand...
Click to collapse
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
derausgewanderte said:
just wanted to remind everybody that those of use who went from NoDo to RTM had varied times for the updates, some people reported more than an hour at the boot logo until it continued. After two hours I'd say something is wrong.
A hard reset might bring it to back (loosing all info of course). That in fact worked for me in the first update state going from NoDo to 7661 beta. I thought I bricked my phone, but it came back after a cold boot/hard reset.
Click to expand...
Click to collapse
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
mdjmurray said:
My phone was updating for collectively updating for three hours. At least two of those it was stuck on the boot screen. I've tried resetting it (holding both volume keys when turning it on) and nothing works. Microsoft's support page said to disconnect if it freezes..
Click to expand...
Click to collapse
a hard reset on mine worked by pushing down power button, camera button and both vol plus and minus at the same time while the phone booted. I unplugged the battery, plugged it back in and then get the timing right to push the buttons down. Good luck.
Dead HTC Surround..
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all. Hard reset won't work. Acts like the battery is completely dead and USB port doesn't work. No lights, no beeps.. dead. Ugh.
Never installed any hacks, ROMs etc. I was 100% normal updates. Very frustrating...
This was actually my third attempt to install the updates. Previous times it had froze I was able to do a hard reset and restore the backup.
Anyone have suggestions? I've pulled the battery and it hasn't made any difference.
bbrian said:
In the same boat as others. Phone stuck between steps 8 & 9, no phone won't turn on at all.
Click to expand...
Click to collapse
This happened to my Omnia 7 while doing the final restart. It got stuck on the 'Samsung Omnia 7' logo for about 15 minutes. I just hit the home button and it finished booting.....problem solved.
Ok. Did you guys forced the update or waited for the official notification?
i got a message on my cell about it so i upgraded i i got a sdamsun focus v1.4
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
VoodooKing said:
Ok, here's a thread where those who are having difficulty upgrading to Mango should post so as to stay clear from the other "I have Mango" thread.
The format should be
Carrier
Phone Model
Updating from NODO/7004/7008
Force update(disconnect trick) or Official Zune notice?
Error Code
Problem Description: Eg, Phone hangs for 30 minutes at booting screen.
Click to expand...
Click to collapse
tamcdonald said:
Carrier: AT&T
Phone Model: Samsung Focus
Updating from NODO
Force update(disconnect trick)
Error Code C1010009
Problem Description: It got through the friends and family update, then when it tries to update to Mango I get error C1010009 each time. I've tried this on multiple PCs with the same exact outcome. I went through the suggested MS troubleshooting steps and tried the Fix It thing to no avail, Fix It says nothing is wrong. Any suggestions?
Click to expand...
Click to collapse
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully installed it.
I believe that nobody is meant to do the disconnect trick and its best to just wait for the official update notice.
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
VoodooKing said:
Ok you may want to try to wait for the official notice to pop up. There is a reason why but I used to get that error when I changed my carrier code. A while back there was a Samsung firmware update being pushed down to some carriers that my carrier hadn't released yet. So I changed my carrier code to force the update. The update downloaded but did not manage to install and giving me that error code. I reverted to my original carrier code and a week later, My phone notified me of the same update and successfully it.
I believe that nobody is meant to do the disconnect trick and just wait for the official update notice.
Click to expand...
Click to collapse
tamcdonald said:
It almost seems like some kind of driver issue. After Zune updated it detected a new device and Windows said it installed it ok, the phone works fine in every other way as far as syncing with Zune etc. Device manager says the device is working properly, but when specifically trying to transfer the Mango update it refuses. Weird.
Edit: I fixed it. After reading your post about carrier codes, I starting poking around and rebranded my phone to ATT-US. After that Mango installed no problem.
Click to expand...
Click to collapse
That's good to know. Now we know one of the causes for the error message. Mine is unbranded 000-88.
bricked focus
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
depdereck said:
Carrier AT&T
Phone:: Samsung Focus v1.3
Updating from 7390
Force Update Disconnecting trick
Error cod:e none froze during step 8 or 9 phone restart phase of 7392 update
Problem: My phone will not move past the AT&T orange world phone screen. I have hard reset the phone numerous times both without SD card and with. Have followed all the steps to what i have seen posted do far. Not really sure what to do now. I have entered it into the download mode twice the first time for over 30 minutes the second time around 20 or so. What would be next step if there is one?
Click to expand...
Click to collapse
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
aggelosss5 said:
Hi i have i an unuseal problem my phone is htc 7 mozart and in about it says hardware revision NA radio hardware version 0.0.0.0 and when i boot to bootloader mode in the red colour it says something like chinese.Now i am in mango.Why it says that???
{sorry for my english i am from greece}
Click to expand...
Click to collapse
Is your phone still working after the update? What are the version numbers? You can check in Settings > About
VoodooKing said:
How long did it get stuck at the operator screen? I have seen reports of 15mins before the phone boots again.
Click to expand...
Click to collapse
It gets stuck there for a long time longest i let it sit there before trying another reset was about 45 minutes or so. I got Zune to recognize my phone and start a restore but it stopped again at the phone restart and sat there for about 30 minutes. I had to exit out to leave work and head home. I also tried to recover the phone with the Windows Phone Support Tool but that timed out at the restart as well and gave me an error code of 800004005.
Related
Hello,
I know booting issues are possible when opening the bootloader and messing with kernels and rom flashing but that's not my case and I couldn't find a post that helped me so I hope someone can help me out on this.
I am a member of the HTC User Trial program and I'm currently testing the 3.09.401.100 Jelly Bean ROM, all stock, not rooted, never opened the bootloader or flashed any firmware besides official HTC RUU when OTA came out late (UK device, always last to get official OTA )
Last night I left my phone on before I went to sleep and it had low battery. This morning I tried to turn it on and it didn't work so I thought that the battery went out. Naturally, I plugged my phone to the charger and the red led didn't light red to indicate charging for a 30sec-1minute period, than it flashed red a few times and afterwards it lighted up red as if the phone was charging. I've left the phone turned off to charge for about 3.5 hours (even after the led turned green, just to get it really fully charged).
Now, when I try to turn the phone on, it get's stuck in the "HTC ONE" bootscreen with the beats audio logo at the bottom.
Long press on the power button reboots the phone but the issue repeats and the phone does not boot past the boot screen with the logo.
Couldn't attach my HBOOT photo so here's a link: https://www.dropbox.com/s/oxk8yz19ew0gi6s/hboot.jpg
Same
I'm having the same problem with an unlocked bootloader
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Bram89 said:
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Click to expand...
Click to collapse
Contacted HTC with this issue and they are not familiar with it as well. They have asked me to send a bugreport using ADB and told me that a factory reset may be required.
I will update if anything new pops up.
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Vcek said:
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Click to expand...
Click to collapse
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
IdanK said:
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
Click to expand...
Click to collapse
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Vcek said:
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Click to expand...
Click to collapse
I got the update directly from HTC as I'm a member on the User Trial program, no flashing what so ever, just plain OTA download & install.
I was chosen to participate in the User Trial program because I'm also a member on HTC Elevate and they asked users to join the program for testing One X software update.
Hi All,
First of all I'm not a native english speaker and I'm a noob in this stuff o rom's .
I recently bought a phone and on update it to JB 4.1.1 with Sense 4+ . Everything went ok and the phone apparently was working ok.
The next day I just noticed that the bluetooth was not 100% because I had some cuts in the sound when connected to a bluetooth headset. Because of this I looked for another OTA update and it found one that said somethink like "General System Improvement" or something like that.
I've installed it but this update didn't went till the end since I get stucked on the "red sign" indicating some fail. I try to reboot the phone but apparently he was dead.
After a lots of tries and key combinations I was able to enter the boot mode and choose to restore to factory mode, but apparently it was not successful. Then I tried and option to check for CRC of img files I think (not sure because don't remeber). It check for 3 images files showing the CRC code, then I think the phone get stucked on one because I still have the waiting message but nothing else happens.
I pressed power button again trying to reboot the phone but since then then phone died completly. The only sign of life is when I connect to the PC windows emits the sound of detecting something but gives an error related to the drives.
Sometimes I get a message saying that a ARX device was found but not anymore.
Tried almost everything that I could read on this forum but nothing seems to work...I think the phone is looping on the boot or doesn't have any battery...not sure.
I've tried some RRU but they fail to find the phone saying not connected or not detected.
Any help will be greatly appreciated, Thanks
Johny
Sent it back for warranty repair as soon as you can this is a known fault as it happened to me recently.
Similar problems: http://forum.xda-developers.com/showthread.php?t=2075862
Getting out of APX mode
Your bootloader isn't locked right? Or were you ever rooted? If the answer is no, just send it to HTC and your warranty will do the rest.
Sent from my HTC One X using xda app-developers app
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
chylos said:
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
Click to expand...
Click to collapse
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
Click to expand...
Click to collapse
yepp exactly the same.
In short, don't update
Sent from my Nexus 7 using XDA Premium 4 mobile app
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Sent from my Nexus 7
datallboy said:
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Click to expand...
Click to collapse
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
Click to expand...
Click to collapse
Damn that sounds awful, and I was nagging for not getting the update, that's way worse. So you can't access bootloader mode at all? Did you try to use fastboot commands or adb when plugged to the pc?
Worth a shot if not already tried:
http://forum.xda-developers.com/showthread.php?t=2404297
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
Click to expand...
Click to collapse
I've actually gotten the QHSUSB_DLOAD before when trying to get into bootloader but pressing the wrong buttons.
I was eventually able to get out of it going through various button sequences.
I believe holding down the power for a long time worked in the end, but I forget now.
nope nothing helped me. it's still bricked. i tried every button combination up to 3 minutes. No sign of power.İt was 32 gb. i think google ****ed up this time.
ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP
Goofygirl0928 said:
ok long story short...i was playing on my tablet and i got a notification saying that i needed to update to the new lollipop so in the middle of the install it says there is an error and shuts off. i try to turn it on and it doesnt go past the google logo. i read online and someone said try pushing the volume down button and the power button until a screen pops up...i did that and it doesnt matter which option i choose it takes me back to the google screen. ive called everyone including google to see if a tech support person could help me and there has been no luck with out having to pay for it....the google guy said what probably happened is that ive wiped the OS off the tablet. and i was wondering if there is a way to fix this. ive downloaded the root tool kit but am pretty much lost when it comes to something that percise. the tablet is fully charged but its almost like my computer wont reconize it when i plug it in to do anything with it.. HELP
Click to expand...
Click to collapse
If you'd searched a bit, you'd have found out that it means your motherboard is screwed, and the only solution is to replace it. But if you have to pay for it, don't let Asus cash in on their deliberate scam - knowingly putting out a buggy update that potentially bricks their device, then turn around and solicit repairs at ridiculous prices. They break it, they should fix it. The point is that they don't even know what or why and thus choose to dodge responsibility by insinuating it's your fault.
Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.
losmolinos1098 said:
Similar thing here. I was sending a text late at night. Sent it and put it down. Next morning tablet was stuck on Google logo and nothing seems to fix it. Tried adb commands to restore. WugFresh Toolkit failed. Disappointed with both Google and Asus.
Click to expand...
Click to collapse
I have the same problem.
I updated from Kit Kat to Stock Lollipop and the device worked fine then today when I turned it on it would not boot past Google Splash. Will not boot into recovery. I can get into Fastboot mode but my attempts to flash a stock 5.0.2 from google have failed. I have a Nexus 7 2013 wifi Model "Razor" and flashing it in fast boot is not resolving the issue. Just boots to "Google" and stays. From what I have found this is very common on a 5.0.2 update and needs a RMA? is that correct?
FASTBOOT MODE
PRODUCT NAME - flo
VARIANT - flo 16G
HW Version - rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - None
SERIAL NUMBER - XXXXXXX(Filtered out)
SIGNING - yes
SECURE BOOT - enabled
LOCK STAT - unlocked
Thanks,
Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.
My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!