2.29.405.2 update bugfest - any way to roll back? - Desire General

Did the 2.29.405.2 update OTA initially and noticed problems. So reinstalled it from SD card but no help.
Bought sim free, unbranded/locked and never rooted:
Cannot dial out from phone lists or contacts. Going to phone and clicking on an entry in the call list does not launch phone call any more. Going to contacts, opening one and clicking on an available phone number does not launch phone any more.
The only way I can make a call is to punch it in on the keypad! Grrr.
Wifi connects to my home base after a reboot but, after an undetermined amount of time it drops the connection and cannot get it again. Going to Wifi settings shows it scans, connects and tries to obtain IP address. After a short time it gives up, turns wifi off and starts over. Again & again.
Cannot get it to connect again without another reboot.
This is a crippling loss of functionality for me. Can anyone suggest a way to roll back this update so my phone works as id did?
Many thanks all,
M1

First try a hard rest(you will lose all personal data on the phone,pictures and other stuff on the SD will be fine). If that does not work try either the 2.29.405.2 or 2.10.405.2 RUU.

More info - to my horror, around 15 minutes after I had tried and failed to make calls from contacts the phone started making them one after the other as if they were stuck in a spool or something! Ouch - any thoughts?

Backup everything you can and flash the same ruu from shipped roms.
Sent from my HTC Desire using XDA App

> flash the same ruu from shipped roms
where do I find this? - android noob!

http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
And if it works, keep it safe!
Sent from my HTC Desire using XDA App

Thanks to all for help on this. Decided worth a trouble shoot before a hard reset and culprit seems to have been an app - extended controls widget. Removed this and all seems well again.

Try this one. This definately works! i have used it.
http://forum.xda-developers.com/showthread.php?t=768256
I was stuck at 2.29 update.
Then i used this guide and windows tool.
So i did this process and it rolled my phone back to stock android 2.1 rom 1.X
The first version that the phone was bought with.
This tool will boot the phone into bootloader and load a stock 1.x rom ota off the sd card as the tool will extract it to sd card and then load it.
This will wipe all your data not sure about the sd card as i dont remember any of that because i formatted my sd card after i had used the tool.
Thats because i had rooted my phone and tried custom sense hd rom.
The only reason i had was of the battery usage as the consumption was very badly increased and that the 2.29 rom was unstable.
PS: I did first try the htc service in Denmark. They couldn't help me and said i was stuck with the 2.29 rom update. :/

After my phone got rolled/flashed back to stock android 2.1.
The next day in the morning i could upgrade again to android 2.2 rom ver. 2.10 OTA from htc servers.
Maybe this works for you as i did for me and others.

Turns out it wasn't the app.
After a couple of days playing ok my sim free stock htc desire is unstable again.
Cut me off mid call - went to phone and clicked on last call entry - absolutely nothing happened, repeated with same problem. Exited phone to home screen then opened contacts and tried to make call from there - same behavior, a complete hang.
No web access either so opened wifi manager to find it hanging on "obtaining IP address" from my home network and continually shutting down and restarting wifi automatically at this stage.
Noticed general UI lag and several apps failing to open too.
Left phone alone and again, around 10 minutes later all of the actions - including trying to make the phone calls started running one after the other. Like everything had been caught in a spool or something. After this all seemed OK until it happened all over again later.
Although the UI seemed OK and some apps worked as expected, the only way to get phone and wifi working whilst it was hung was a warm boot.
Dreading a hard reset as it's going to waste another day or two getting everything reconfigured just so (can't find a back up solution that does everything - multiple mail account settings etc) but looks like only option.
Will try going back to mikep99's suggested rom as soon as I have time and will not be responding to an HTC OTA auto update offer again.
Grrr.

I still suspect an app conflict.
Can anyone recommend a util that might give me a clue which app / sys process could be hogging system / radio resources?

just got another OTA update pushed to me. installed (nothing to loose) and Congratulations my phone has been updated to 2.29.405.5.
Not sure whats going on here as that was the update I got 2 days ago. This time round it was only 4.8mb download so I'm assuming it's an update update. Hope it fixes things .....

Related

Attempting to update 1 week old 8525 to ATT WM6 - Probs...

Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
Are you following the directions at THIS GUIDE . What ROM are you trying to put on there? Did you CID unlock the device? Are you running Vista? Do you have .NET 2.0 or 3.0 version?
That should be enough questions to get us started.
Did you read my title? This is the stock ATT WM6 that came out yesterday. No need to unlock the phone, it is a 1 week old ATT 8525 with the stock ATT WM5 Rom on it.....
Windows XP SP2+ PC.
If it's the rom RUU_Hermes_CINGULAR_WWE_3.62.502.3_6275_1.54.07.00_108_UOOS_SVN05_Ship maybe it had some problems because if you go to the official release site http://www.htcamerica.net/support/8525/software-downloads.html they are still showing the WM5 rom for download.
There may have been a problem with the release and they pulled it back for some reason. Just a thought and not much help I'm afraid.
Yes thats it. When it ID's my current Rom and what it will upgrade to, it is correct. (it shows it's 3.62 vs my current 2.xx) Many peeps have had no problem upgrading to it. (most find it a very good Rom from the varios sites I read)
And this page at HTC still has it up:
http://www.america.htc.com/support/8525/software-downloads.html
JETninja said:
Ok, PC is fine, close any running programs. Hermes has stock WM5 with some programs added. Only reg tweaks are PTT and removed 3G animation at start.
Device syncs normally every day and both Work and Home.
When I follow all the directions, run the Updater - The PPC gets the Color Bars as the Updater is trying to read it....then AS (V4.5) disconnects and closes. (gone from taskbar) I can soft reset the device, reopen AS, they sync just fine. At this point I have the updater do the next, it pulls up the Current ROM info and says it will upgrade to the new one. I select next, and it starts.....and AS closes again. After a minute the upgrade app says it lost connection. (duh!)
Any ideas why?
I'm not a stranger to upgrading roms on PPC's, have several that have both been updated a number of times. No issues, though that several AS versions earlier.
I've given thought to Hard Reseting the device, but I'm wondering if its more AS's fault.
Any and all input much appreciated!
Thank You!
Click to expand...
Click to collapse
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
@brorex he can wait till christmas next year, if the updater cant communicate with the device , because it has closed AS then it will never update.
@JETninja
try doing what i said to this guy here,
http://forum.xda-developers.com/showthread.php?t=341282
yesterday he upgraded with the same rom and device and it worked
brorex said:
You just need to wait for a while AS shuts down that is normal be patient and it will start updating you will see a progress bar will take approx 10 min after that
Click to expand...
Click to collapse
I thought that too, but after the color bar test when it want to set you up to actually install the ROM, the Upgrader whats you to make sure there is an active connection with AS. Well, there isn't. It shut down and the PPC is still showing the color bars. I can reset it, then re-sync to AS. (after having to re-launch AS from the Program Files - it no longer resides in the Tray when it shuts down during the process) I then get it going again, it attempts to start the ROM upgrade, AS quits again.....about a min later I get the Communication Error message....
I'm downloading a 2nd copy right now, will try it as soon as it completes...
*Edit...think I have an idea what I'm doing wrong, I have it connected and synced too early, the first part of the ROM updater is just a PC test, I'm thinking the PPC should not have been connected at that time. Re-trying it now.....
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Going to give it a shot here at work on this PC. If no go still, will try the above mentioned methods. PC at home kept getting communication errors...
i had the same problem
make the connection at AS then start the update process.... the 8525 will go into 3 bar mode and when the update gets to the upgrading rom screen... the installed rom wont show up.... hit upgrade... and then continue and it will work.... i was stuck there for a while too because if i waited for the istallation to load then made the as connection the right image would show up in the installer but then it would stop working after that.....
I just put this rom on my 8525 and it worked well for me. My 8525 is unlocked with supercid so I had to extract the OS and update using the methods described for working with SPL-140 Olipro with IPL-1.01 or the "How not to Brick thread".
That won't help you much as you don't want to do that mod to your New 8525 and void the warranty, but thought you might like to know the stock OS seems pretty stable at this point and I have had no problems yet.
Thanks everyone! It finally worked here on my Work PC. At home I could get to the Bootloader, but it would lose connection for some reason. Here I lost it the first time, but tried it again and it managed to stay connected and apply the update. Got it up and running, applied owner info, just now re-doing the AS relationship. (a good 500+ contacts! LOL! It'll take a little while as usual!)
Then it's back to all the tweaks I like so far...and some new ones I've held up on since I've been waiting for WM6.
Out of my 3 PDA's (2 ipaqs and this puppy) this one has certainly been the trickiest ROM update, but it seems to be more my device since most don't have this much trouble.
Thanks again!
So far- So good, but just one problem- BATTERY!!!
After I installed upgrade, my battery drains in few hours... I reset phone, I reloded upgrade- nothing helps! Warranty still in affect, but phone worked well and I'm positive- hardware is OK. What else can i do to fix this problem?
I have the same problem
ai6908 said:
Try putting it in boot loader and upload...thats what i did when i updated my 8525...Very much like the new ROM...
Click to expand...
Click to collapse
I have the same problem exactly. As soon as I start the upgrade the device immediately sleeps and the connection is lost. 1 minute later I get a Connection error message.
I am new to all this. How do i put the machine in 'boot loader' mode?
Thanks
Just did this rom update again on a 8525 the installation went extracting files active sync shut down wait a few minutes nothing happens the the upgrade screen no ACTIVESYNC connection while update is happening as soon as device is in bootloader mode activesync closes out

Anyone got anys ideas on whats wrong with my TP2???

I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Shaolinstyle said:
I have been using the Energy Leo Rom’s since September updating whenever I new rom is released, everything has always been fine with them and I absolutely love them. Me and my fiancée both use them, but lately my phone has been restarting over and over and will not boot, it gets to you boot up splash screen and restarts. When this began to happen I wasn’t even using my phone it was recharging as I was updating my computer to Windows 7, anyway I am able to revert back to T-mo’s stock rom and everything works, but whenever I go back to any none stock rom, even earlier ones it keeps doing the reboot thing, our second TP2 is fine. I have done research and haven’t found much I have ran Mtty at least a dozen times, even upgraded my radio, and nothing works but the stock rom, I have cleared storage both the software route, and the power, talk and end button route. Any help would be greatly appreciated, I just can’t handle this stock rom.
Click to expand...
Click to collapse
Are you able to re-do the Hard spl?
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Shaolinstyle said:
Yes, I have redone it and nothing changed, it goes through the initial TP2 screen showing the radio and other info in red on the bottom, but as soon as it goes to set up the rom is when it restarts. Whats weird is it is never at the exact same time, sometimes will be a second, other up to five seconds.
Click to expand...
Click to collapse
I know this sounds obvious and dont take it the wrong way but are you sure that the rom you are trying to flash as been unzipped properly and is named correctly. Try re-downloading a fresh rom and unzip it and rename it Rhodimg.nbh and put it on the root of your Sd card and try flashing it from the card. Also is the battery charged?
I am certain that the roms that I have been using are unzipped and named properly, there was actually a flahed rom on this phone that was workig fine until it started resetting with the rom on it, I wasn't updating or anything when it started to act up. Plus I use the same roms on a second TP2 which are working fine. I did try now to flash from my SD card, Hard SPL said it installed correctly but when I rebooted phone its doing the restart thing over and over still. Battery has been at 100% or close to for all flashes.

Help! Phone crashes after booting OS!

Well, this sucks. Upgraded from the Hero to the Desire Z 1.5 weeks ago. Downgraded it, rooted it, tried out a few ROMs, settled on Virtuous Unity and all was happy.
I used the phone in the car this morning as a GPS, 3G data connection was working fine, etc. I had a couple of client meetings, after which I pulled out my phone to check for messages. I noticed there was no mobile signal at all. I figured it was building interference, so I went outside. Still nothing. Wifi was working fine, GPS was working fine. I enabled airplane mode, then disabled it again to see if that would kickstart things. Still no go.
I decided then to power cycle the phone to see if that would help. It went through the usual reboot cycle, displayed the lock screen, then the SIM unlock screen. Then no matter what I do or don't do, about 5 or 6 seconds later, the screen suddenly goes black and the phone reboots.
Now it just does the same thing over and over again. The phone boots up fine, displays the lock screen briefly, then the SIM unlock screen, then it crashes and reboots. Whether I unlock the SIM or not doesn't matter. Within 5 or 6 seconds, the phone will reboot. I can see notification icons popping up, so everything appears to be working fine otherwise.
I have not changed anything on the phone this morning: it was sitting in my pocket the entire time. Same ROM, same radio firmware. I restored last night's nandroid backup just in case, but it didn't help. I thought perhaps it was VU's built-in overclocking that wasn't agreeing with the phone, so I restored a MIUI-based backup. No go. I went all the way back to the stock (but rooted) Bell Desire Z image I took when I first got the phone. Still no go.
I've tried booting up without the SIM card, and without the SD card. Nothing works. I'm guessing the phone suddenly developed a hardware problem. It would be something that is triggered soon after the OS has successfully loaded. Maybe something to do with the 3G radio?
There are no obvious errors or kernel panic messages in logcat. Everything appears to be proceeding normally, until it just comes to a dead stop. Anyone have other suggestions I can try?
Search this forum for "boot loop" and you'll find some things to try.
Thanks, burtcom, but none of the threads I checked apply here. Other boot loop problems more often have to do with the phone rebooting while the boot animation is still playing. My phone successfully boots and is in the process of loading user apps when it crashes. Also, most reports come as a result of something attempting to root their phone and then installing a ROM. I've already made it past that stage. I am able to boot into CWM, do my nandroid backups and restores, etc. The ROMs have all been working fine up until some point this morning. The fact that several different ROMs now all have the same problem makes me suspect a hardware issue.
Moved my SIM and SD card back over to my Hero, and everything works fine there, so I strongly suspect some hardware just broke on the DZ this morning. I'll try flashing a new radio firmware, but I can't see how that would fix anything, since the old version was working just fine all along.
taob;15238893I'll try flashing a new radio firmware said:
Huh... so I flashed the latest Bell Canada 26.06.02.25_m2 radio.img, (up from my old 26.03.02.18_m3 firmware), and now the phone no longer crashes. I'm thinking maybe it isn't an issue with old vs new firmware, but that the old firmware was somehow corrupted during the course of the day. Re-flashing the original radio probably would have worked too, but now I have the latest one...
Hopefully this will help someone in the future with the same problem.
Click to expand...
Click to collapse
The phone no longer reboots, but I still had the problem of not picking up any signal whatsoever (voice or data), even though wifi and GPS work just fine. APN settings were verified to be correct. It turns out I had to go into Settings -> Wireless & networks -> Mobile networks -> Network operators -> Search network and manually re-register my phone on TELUS. Bizarre.
I had the same problem, update your radio and flash this zip on the Unity Thread
"For people experiencing random phone Freezes, this is due to overclocking, it's solved by lowering max speed.
Just flash this patch over: (link is on the thread)"
That's a different kind of problem, sengalang. My phone was working just fine overclocked to 1.2 GHz for over a weeks, so why would it suddenly start crashing like this? Problems due to overclocking tend to result in reboots at random times, and not at 100% predictable times like my problem. I did also boot with the MIUI and stock DZ ROMs, which do not overclock... same problem. Thus the root cause was not CPU speed.

Signal problems after update

Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.

[Q] Stuck on bootloader after changing screen density with Rom Toolbox

Hey guys. As the title suggests, I can't boot my Note 2 (sgh-i317). It is stuck on the AT&T logo and while it's stuck there it vibrates slightly every 5-6 seconds. I tried changing my screen density to 240 and it worked for a bit but annoed me. then I went to change it back and got this problem. I accidentally set it to 360 I think though, instead of 320. I have wiped the cache. I have wiped the data. I have installed roms countless times already with Odin. I'd imagine my reset counter is at over 10 just from today.
I've been searching on google and these forums for hours and have seen many suggestions, but none of them have worked. The farthest I have gotten was to get the phone to boot, but once I start going through all the setup stuff I begin getting error popups saying that Touchwiz home has stopped responding. As soon as I push OK the error immediately pops up again. I seriously can not do anything with my phone.
Is there any way to get a stock build.prop file somewhere for this phone, and if so, how would I install it if I can't even boot into the device?
Any help would greatly be appreciated. I have no idea where else to turn here. Thanks!
-Mark
Do you have a backup to restore from recovery ??
If not....then power down the device and remove the SD card and place it into a PC card adapter...
Then download or copy over a suitable rom...
Then place the SD into the phone and boot into recovery...
Fully wipe the device and flash the rom of choice...
Reboot....set....profit....g
Edit:
Are you certain that your power button is not stuck ?
If the method I suggested fails... and rebooting occurs with vibration...then your power button is suspect....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks. Well I got it to boot finally, however there's been a couple issues since. It's on 4.1.2 right now...
1. Whenever I try to officially update to 4.3 through the settings, it downloads, then when installing it ALWAYS fails at 25%.
2. This is a big issue. My data connectivity is gone. I have no 4g access period. If I'm not using a wifi network, I can't do anything online, period. I've reflashed numerous times, and can't get it to recognize the network. I can make calls just fine, just no data.
I've tried wiping data and going to factory reset, but this doesn't help in any way whatsoever. I've popped out the battery and sim card and reinserted after a few minutes, still to no avail.
The funny thing also, last night my friend, who has the same phone, updated to 4.3 and got the EXACT issues I've been dealing with. The ONLY thing in common is that we have both rooted our phones in the past. When I first got 4.3 it worked fine. It wasn't until I rooted that these issues began. My friend's phone was not rooted, however it had been in the past. I'm thinking that this 4.3 update has an issue with phones that are rooted or have been at some time. I don't know how it can tell, but that's all I can think of. his phone now is also a doorstop, like mine.
K, fixed data connectivity from another thread here. For some reason, even if I wipe my system, it seems to still keep settings intact. In this case, nothing set in APN. Seems the more I try to fix my phone, the more problems show up.
If you updated to official 4.3...then yes ...a whole new host of problems are yours until the devs figure out the locked bootloader and it's knox flag...
Backups won't restore....and so forth...
Read around ....you'll see...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Categories

Resources