Related
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.
I am currently trying to fix a friend's Xperia Play r800a. It seems to be having a few different problems and together they are making it all difficult to get it going again. First off I have no real knowledge of toying with an Android phone. I browsed some threads on here, used Google and tried to use Flashtool to get the original operating system on it but all were a no go. I'll try and describe the problems to the best of my abilities and maybe someone can offer some help.
This is what I know from what he remembers he did to the phone. He said that the phone started t only boot to the Sony logo and then it would hang until the battery died or the phone was reset. If plugged in with a wall charger then it would allow him to get to the screen where he would enter his password but the touch screen wouldn't work. He then flashed it using Flashtool and at that point it would boot to a black screen and that's it.
-It hangs on a black screen, no logo or anything is present and it happens regardless of whether it is plugged into a wall charger or not.
-It is not found when plugged into the USB port (Windows 7 PC) and shows up as an unknown device. After a few minutes it is found by the PC but sometimes will randomly go back to an unknown device.
-I sometimes get a red light which blinks three times when I press the power button on the phone. I am currently charging it to see if it was a matter of being a dead battery or something worse (I heard it could be a hardware failure).
Any suggestions would be appreciated.
My Xperia Play has done This I asked a Mate (Jinx13) He said Il do a hardcore Testpoint process. After I have done this My Phone will Vibrate and Nothing I was Playing Rayman today and it Locks and Hardware Keys Do Not respond.
Then Touchscreen Stopped Working. Indeed This is a Hardware Failure I have got this and Re-Flashing with Blinking SETOOL2 and Resseting it Wouldn't work. I Then Re-Locked By fastboot SIM and Bootloader (Maintained DRM) and Now Dowloading R800i O2-UK From SETOOL Support and 3-UK one and I will Upload them for US people for Warranty they Become indeed handy . I now Am Going to O2 shop I was Running 2.3.4 .42 GENERIC.But I am Not allowed to Give you the FW's Only by Re-Uploading I Can. Anyway My Brave Soldier Died (Hardware Failure) Its the Screen Components.Im Not Rooted anymore and Re-locked with S1-Tool.
If this happens to you My advice is Dont Flash Alpha ROM's They can make Your device Coo Coo. And OC can Damage.
Basically I boot My phone with a 3600MAH Mugen Battery 89% Battery From the Last time It was on. Im afraid your friends Phone is Dead Maybe a Hardware Failure Most Likly and I am now Officialy Out of the Game.
But O2 Gave me 3 Year warranty!!!!! For £100 When I Purchased it. So I am Going to O2 in Stevenage and Say this What actually happend:
"I Purchased My Xperia Play on August 17th Through Online Store ; I have never had a Problem With My device Untill This week : I have had these Issues:
*Touchscreen Wont respond Cleaned Several Times.
*Random Reboots
*Red Light when Phone had 50%+ Battery
*Would Take 6 Battery Pulls to Turn on (Would Only turn on Earlier during the week)
*Lagged In games.
*Running O2 Branded Software
*No Screen Brightness or Signs of Working Screen.
*Would Not charge Unless turned On
*Camera Would Not work Unless Wifi Was not on I dont know why?
So Basically This Phone had a A fault since Day one I always had Camera Fails.
bluetoon said:
I am currently trying to fix a friend's Xperia Play r800a. It seems to be having a few different problems and together they are making it all difficult to get it going again. First off I have no real knowledge of toying with an Android phone. I browsed some threads on here, used Google and tried to use Flashtool to get the original operating system on it but all were a no go. I'll try and describe the problems to the best of my abilities and maybe someone can offer some help.
This is what I know from what he remembers he did to the phone. He said that the phone started t only boot to the Sony logo and then it would hang until the battery died or the phone was reset. If plugged in with a wall charger then it would allow him to get to the screen where he would enter his password but the touch screen wouldn't work. He then flashed it using Flashtool and at that point it would boot to a black screen and that's it.
-It hangs on a black screen, no logo or anything is present and it happens regardless of whether it is plugged into a wall charger or not.
-It is not found when plugged into the USB port (Windows 7 PC) and shows up as an unknown device. After a few minutes it is found by the PC but sometimes will randomly go back to an unknown device.
-I sometimes get a red light which blinks three times when I press the power button on the phone. I am currently charging it to see if it was a matter of being a dead battery or something worse (I heard it could be a hardware failure).
Any suggestions would be appreciated.
Click to expand...
Click to collapse
okay lol i don't know if that second post helped but is the phone unlocked? by any chance if it is, you can never really brick your xperia, from experience i kept flashing re flashing cusom kernal all day i get the same loops etc, but always fixable, also flash tool should fix your phone if that is you got the right ftf file for the brand like i have verizon and it have a verizon.ftf file, other than that i need more info about the phone not how it bricked, like what was it running at first etc. Try sony software reflashing repairing if that doesn't work use flashtool and see if you get an error with that
I cant enter fastboot or recovery lol
Xperia4life said:
I cant enter fastboot or recovery lol
Click to expand...
Click to collapse
lol xD oh danm only possible way i think is to try flash tool and downloading the ftf file for your phone and let me know if you get any errors
biggyhead said:
lol xD oh danm only possible way i think is to try flash tool and downloading the ftf file for your phone and let me know if you get any errors
Click to expand...
Click to collapse
my phone is having the exact same problem, it wont recover through pc companion and flashtool wont even work cause I cant get my phone into flashmode.
are there any other tricks that might get my beast running again?
NevErSn0w said:
my phone is having the exact same problem, it wont recover through pc companion and flashtool wont even work cause I cant get my phone into flashmode.
are there any other tricks that might get my beast running again?
Click to expand...
Click to collapse
How are you trying to get into Flashmode?
Sent from my Slider SL101
I updated my phone (Xperia PLAY) from Android 2.3.3 to Android 2.3.4, 4.0.2.A.0.42 on my phone, when there was notification for updates. It downloaded updates and turn the screen on with some kind of package. It loaded in little time. And when I tried turn on phone there is only vibration and green flash on power button. What can I do? Plz help me, I have lost the warrant and I dont know is there any guarantee for my phone!
P.S: I've tried that repair thing in PC Companion and it says The phone contains modified software that cannot be updated.
Locked bootloader.
davidbar93 said:
I updated my phone (Xperia PLAY) from Android 2.3.3 to Android 2.3.4, 4.0.2.A.0.42 on my phone, when there was notification for updates. It downloaded updates and turn the screen on with some kind of package. It loaded in little time. And when I tried turn on phone there is only vibration and green flash on power button. What can I do? Plz help me, I have lost the warrant and I dont know is there any guarantee for my phone!
P.S: I've tried that repair thing in PC Companion and it says The phone contains modified software that cannot be updated.
Locked bootloader.
Click to expand...
Click to collapse
Have you tried flashing another firmware using FlashTool?
Yes.
Somehow ,after 10 minutes of charging the phone turned on
Everything works now ,but all my data has been deleted :\ I managed to do a backup 1 week ago ,I really have lucky!
sorry for my English
On Wednesday, I was helping a friend move on a nice, hot day. I was sweating like a filthy pig and my phone was in my pocket and within a few hours it would not turn on when I tried to do so. That night I really didn't know what was wrong and the next morning I tried to turn it on and the red LED would flash 3 times in succession. I looked this up and they said "dead battery." Sure enough, I charged it and it took a minute for the LED to turn on, and as it charged it was red, then orange, then green. But even once fully charged, when I tried to turn it on it would only vibrate, but no screen action whatsoever. Note: the battery was at around 60% when the phone quit responding. The next morning it was dead. I have had the phone for a year now and the battery will last me at least 2 days if I don't play games and such.
The next morning, when using the flashtool it would go into blue LED'd fastboot and green LED'd flash mode. I thought I had backed up everything, but somehow those files were nowhere to be found. So I flashed the original 2.3.3 firmware, and still nothing. I used PC Companion and it said "Problem: The phone/tablet contains modified software that cannot be updated. Details: Sony Update Engine failure (error 2003)." I contacted Sony and I am still awaiting a response. So, on friday I'm ready to take this turd into the Verizon shop and I turn it on and wait about 30 seconds and I get the SE logo. It loads just fine. I set it up and try to update, but it won't allow me. I'm thinking, great, I'm stuck with 2.3.3... until I turn the screen off and try to turn it back on. And again, nothing. No response. So I'm thinking I will bring it in Saturday. I re-lock the bootloader in some attempt to hide that I rooted the phone, and flashed the 2.3.3 again. Note: I rooted my phone in December and have had no problems. I didn't flash any ROMs or Kernels. I am a simple man.
Saturday morning, after my phone has been off for 10 hours, it turns back on again. Same thing happens. Also, I spent a while on Thursday, Friday, and today trying to research and solve this problem. My brain hurts. But alas, I only had it off for 3 hours and it turned back on, and it did the same damned thing when it turned off. It simply doesn't turn back on. I don't know if it's the screen, or if there is moisture under there, and I haven't researched taking it apart yet. Any advice?
Hum...
Did you try with the software : Flashtool v0.9.11.0?
and flash one of those FTF file?
> Sony Ericsson Xperia Play > Xperia Play Android Development > [FIRMWARE][FTF] Collection of Xperia Play R800a/i/at/x firmware
or
> Sony Ericsson Xperia Play > Xperia Play Android Development > Xperia Play Index - ROM'S, FIRMWARE, KERNEL'S, GUIDE'S, THEMES, MOD'S
or
> Sony Ericsson Xperia Play > Xperia Play Android Development > [FIRMWARE] Working Xperia Play FTF Collection (AndroidFileHost)
I downloaded the newest version of flashtool, (9.11), and I downloaded the "Poo-Tang/Xperia Gamer" R800x Verizon 2.3.3 (CDMA) a few days ago, and flashed it already. Other information: When I attach the phone to the computer, it makes the docking and undocking sound, but the normal menu for accessing the phone does not show up, even when the phone actually came on recently. That is abnormal. Also, flashtool states that my phone is still Rooted, although I supposedly re-locked the bootloader. These last two comments may be pointless, but I figure the more information I give, the better. Any other ideas, kind sir?
Not that much...
It looks like you can connect into fastboot mode (search button - blue led) so you can use this command:
fastboot.exe -i 0x0fce getvar version
or recovery mode (back button - green led). And you can flash...
When you turn on it vibrate,means the kernel start. But you can't enable debuging. Can't use adb.
And the SD card doesn't show-up in windows, means the system doesn't finish to load.
Correct?
So just flash the good Ftf and send back to Verizon shop if it's under waranty.
Sprint_ST_1050 said:
So just flash the good Ftf and send back to Verizon shop if it's under waranty.
Click to expand...
Click to collapse
Thanks, that's pretty much what I ended up doing. Luckily, it's under warranty. But thank you for sending me those other links with the ROMs and Kernels, I will be using them with the new phone, as well as properly backing everything up.
Streiff353 said:
Thanks, that's pretty much what I ended up doing. Luckily, it's under warranty. But thank you for sending me those other links with the ROMs and Kernels, I will be using them with the new phone, as well as properly backing everything up.
Click to expand...
Click to collapse
One last thing, try the software s1tool.
Connect the device in recovery and clic the button RESTORE.
I just bought a what is called new z1 compact smartphone from ebay, and as soon as i turned it on it kept retsrating over and over and over, I did every thing that I found and read even finaly got it updated to android 4.4.4 but I still have the same problem. any one can help?
what should I do?
i
imanmoftah said:
I just bought a what is called new z1 compact smartphone from ebay, and as soon as i turned it on it kept retsrating over and over and over, I did every thing that I found and read even finaly got it updated to android 4.4.4 but I still have the same problem. any one can help?
what should I do?
Click to expand...
Click to collapse
its not good
i recommend to ask for replacement if it has warranty
If not Download PC Companion app connect ur phone and click to check for update if there is no update then select repair firmware option
after this if problem remains u should take to service cause it can be hardware issue
:good:
My phone also keeps restarting can't get into recovery. . .
----
lg P920