Hi,
I have enabled OTA update from Eclair to Froyo. After download completed I confirmed install of the new firmware but during install it was stuck.
I have pushed “wait” several times when asked but finally done “forced close” since phone didn’t move anywhere for over an hour as long as I pushed “wait”.
Since then the phone is starting up trying to load, it reaches the default main screen and after 30 seconds it reboots and this is a continuous process.
The SD card as “gold card” and it is inserted but I noticed that it is not recognized and gets into mounted and ready phase.
Any idea how to revert back to Eclair since phone does not respond to any step due to its “reboot” process?
Any possibility to wipe the phone completely and reinstall stock Rom?
Thanks in advance.
double posting will not get you more answers! you will just get banned please close this thread.
this one was posted by mistake...you are right.
Related
I have an un-branded orange HTC Desire which is factory unlocked! I live in India, I got the OTA (froyo) a few days back, When installing phone restarts and then starts looping on its own with white htc screen and a percentage bar, this keeps happening and restarts on its own! No signal can be found! Im puzzled and its very frustrating that i couldnt get it worked after 2 attempts, I flashed back to the generic 2.1 HTC rom, but I would really like froyo on my phone!
I dint use a goldcard when downloading and installing the OTA, do i need to keep the goldcard in when installing? and also if someone can post or link me to the manual installation, I'd be grateful!
And has anyone come across and workaround for the above issue? I found that a lot of people have this issue!
Any answers on this would be majorly appreciated, thanks!
http://forum.xda-developers.com/showthread.php?t=696189
Everything you need to know
I still dont follow! I mean, isnt that a guide to rooting your phone? Im confused as to what exactly to do! :S
(apologies for the newbness)
Basically you need to flash it and start again, you should be able to get a ROM working to start with then after that a good idea is to try rooting it and flashing to a Cooked Froyo ROM from here
Where did your phone originate from, since in india it is not out yet. Because if you got it from an asian country you have to insert a goldcard when updating. See this thread: http://forum.xda-developers.com/showthread.php?t=741836
Thanks for all the help! finally managed to get it working!
fter the OTA Failed and I got the 1-100% count with errors and no radio. I did the following to fix:
*use at your own risk*
I think I already had the WWE_1.21.405.2 with 4.06 radio
so did not bother with the RUU a second time, just downloaded the manual 2.2 rom
renamed as update.zip copied onto gold card
put gold card in phone
rebooted holding back
selected bootloader then recovery
pressued up and power to get menu
selected Load update.zip
at end of update (when prompted) rebooted from menu.
waited while green update screen showed.
phone rebooted itself
came back up with no signal upon unlock it did the 1-100% count took a while but no errors this time.
eventually it displayed a sucsessful update message and all is hunky dory.
Big thanks - had the same issue myself.
Suspected I needed the goldcard in but didn't know if writing the update.zip file to SD card would overwrite the goldcard bit and leave the SD card corrupted, though.
You live and learn, I suppose.
Hi,
I have enabled OTA update from Eclair to Froyo. After download completed I confirmed install of the new firmware but during install it was stuck.
I have pushed “wait” several times when asked but finally done “forced close” since phone didn’t move anywhere for over an hour as long as I pushed “wait”.
Since then the phone is starting up trying to load, it reaches the default main screen and after 30 seconds it reboots and this is a continuous process.
The SD card as “gold card” and it is inserted but I noticed that it is not recognized and gets into mounted and ready phase.
Any idea how to revert back to Eclair since phone does not respond to any step due to its “reboot” process?
Any possibility to wipe the phone completely and reinstall stock Rom?
Thanks in advance.
If you look at the dev section there is a list of all the RUUs you can use to return your desire to stock.
yes i know about those RUU but the problem is that i can't get into that since phone is rebooting by itself in normal, recovery etc' status.
Oh right does the computer not recognise your phone at all?
Sent from my HTC Desire using XDA App
it is recognized by the PC but then it is disconnected due to reboot...any idea?
How about when using fastboot/hboot? Dies that work for you? Then you should be able to flash a ruu.
Try removing all the ZIP files from the root of your SDCard ...
I had the same problem - this seemed to help...
First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.
Hi All,
I have a VZW Htc One M8, and I have been playing with it when have gotten the chance recently. I have installed/flashed an RUU before to correct an issue I ran into (trying to take an OTA) and everything went smoothly. As I said I took the OTA, but kept the RUU from the previous time I used it (first mistake). I am s off so I am hoping that is going to save me here.... This brings me to my problem.
I was trying to flash Viper Rom, but at the end of the setup I kept getting a popup saying setup has stopped, and I was unable to see a homescreen, but the phone was working. I decided to revert back to stock using the old RUU (be gentle) and it loaded and I hit yes to begin. About 10 second in it stopped and wanted me to reboot... I was in the middle of doing something else when it happened so I rebooted back to the bootloader and my OS line was in red. I then went back to recovery and restored my very recently created backup of my stock rom, which worked. I then went back to the boot loader to look at what was in red more closely and it is now blank. It says OS but then nothing after.
I have since gotten the new RUU that I should have used, but it seem to hang on the last part of the loading (put in on my external sd card) and my phone works... but the boot take forever and the VZW logo doesn't come up anymore. It almost seem like the phone boots fine but the HTC ONE logo stays until the phone screen turns off and when I hit the power button to turn the screen back on the phone is booted. My question is... should I 1) try the old RUU again and then take the ota since I am s off I have seen that technically it should work. 2) let the phone sit at the loading of the newer RUU and see what happens (I haven't tried seeing if the old RUU will load yet) or 3) count my blessings and deal with a non completely broken phone?
I realize I made a few errors while doing this, but I am hoping that s off will allow me to correct the problem. Any help would be greatly appreciated.
Issue should be resolved
Sorry to everyone that read this... I didn't make it all the way through the thread where I found the new RUU, and the thread tells how to resolve the problem with not loading all the way. I am going to try the fix after work.
Edit 1: problem resolved... I am an idiot
So, I screwed up. I accidentally wiped my phone in TWRP and lost the backup I had.
After failing to get it to run for several hours (update via dload folder would abort after 5%, flash via fb would just crash on boot) I was able to at least have it run Android (8.0.0.330). However, the phone is now buggy and won't recognize my SIM, nor load my backup from Google, nor load system updates.
I'm not sure what else to try and I don't really want to trial & error my way through all other firmwares. Any ideas how to fix this?
edit: Fixed my problem. Apparently service ROM updates fail if the device isn't sufficiently charged. I charged it to 100%, then installed this ROM as usual:
- put dload folder on SDcard
- hold vol up AND down AND power
- wait for recovery
Hope this helps anyone who makes the same mistake.
cafemachiavelli said:
So, I screwed up. I accidentally wiped my phone in TWRP and lost the backup I had.
After failing to get it to run for several hours (update via dload folder would abort after 5%, flash via fb would just crash on boot) I was able to at least have it run Android (8.0.0.330). However, the phone is now buggy and won't recognize my SIM, nor load my backup from Google, nor load system updates.
I'm not sure what else to try and I don't really want to trial & error my way through all other firmwares. Any ideas how to fix this?
Click to expand...
Click to collapse
Use erecovery. When phone is on the unlocked bootloader screen, press and hold volume up. From the erecovery screen select download latest full package (similar message)
Recently there have several people claim that erecovery is finally working. (Previously there was no response from the server)
Unfortunately I was also getting no response from erecovery.
In good news, charging my phone overnight and dload-flashing the newest full OTA I could find (and checking that region is correct - it might've been russian the last time) fixed the connectivity issue. Didn't consider it the first time since I was >50% charged, but apparently there's some threshold under which system updates will be canceled. TIL.
Now I can't connect to Google's servers to get into Play Store, but I'll figure it out. Will update when fixed in case anyone else makes my silly mistake.
edit: I'm not sure what fixed it, but after flashing gapps got my phone stuck in a boot loop, I restored the system via dload again and now everything's working fine. Weird.