My bro checked his UK, unbranded Desire for updates and noticed that he has an update of around 30MB and not Froyo.
He thinks that maybe he never installed this one and Froyo will show after he first installs this. He goes to install it, but after the green arrows, a red question mark appears in the middle of the screen with a phone. The phone just restarts as normal after this and the update is not applied.
What's causing this? I think it's the 1.21 update if I remember rightly.
His phone IS rooted but it's stock ROM.
No-one knows the answer?
Has he tried un-rooting?
apparently from what ive heard you cant get OTA updates if you've had your phone rooted
That must be it then.
I'll probably skip the official update then and get a decent custom ROM for him.
Related
I've used several custom roms like MIUI and RCMIX, but have always kept a backup of the phone's original software. Although these roms are great, they do have minor problems and the updates intended to fix them cause more minor problems...
anyway, Now that the official HTC DHD 2.3 update is live, I have gone back to the my backup of the original 2.2, and succesfully (by the look of it) downloaded the update. The phone reboots and only goes to a screen of the android logo with a yellow Exclaimation mark (!). I left it for half an hour til it was clear nothing was happening. Took battery out and it booted back into 2.2 without any problem.
I've tried undoing a lot of what was needed to get custom roms in the first place, but it hasn't been any good. (Unrooted, and used jkoljo's radio tool for an S-ON and Stock CID)
It's a generic DHD on T-mobile contract, but bought from Carphone Warehouse.
I've seen other posts about this, but I'm pretty sure they were in the wrong place and thus went ignored
Hi,
Have a look at this thread your not the only one having this problem - me too
http://forum.xda-developers.com/showthread.php?t=1081923&page=2
lendafender said:
I've used several custom roms like MIUI and RCMIX, but have always kept a backup of the phone's original software. Although these roms are great, they do have minor problems and the updates intended to fix them cause more minor problems...
anyway, Now that the official HTC DHD 2.3 update is live, I have gone back to the my backup of the original 2.2, and succesfully (by the look of it) downloaded the update. The phone reboots and only goes to a screen of the android logo with a yellow Exclaimation mark (!). I left it for half an hour til it was clear nothing was happening. Took battery out and it booted back into 2.2 without any problem.
I've tried undoing a lot of what was needed to get custom roms in the first place, but it hasn't been any good. (Unrooted, and used jkoljo's radio tool for an S-ON and Stock CID)
It's a generic DHD on T-mobile contract, but bought from Carphone Warehouse.
I've seen other posts about this, but I'm pretty sure they were in the wrong place and thus went ignored
Click to expand...
Click to collapse
+1 like @ericsson...also you can try this thread for solve it if you haven´t or loosed the recovery CWM...READ all posts
http://forum.xda-developers.com/showthread.php?t=1081595
So I had my phone rooted sometime around the point when the 4.1.2 OTA came out. I went back to stock recovery and a nandroid backup that I made before rooting. Now, about once a week, I get the notification that the update is available but it doesn't work. My phone reboots like its going to update, I get the android guy with the spinning graphic thing, then it reboots the same as it was before.
I tried searching but couldn't find a solution...if my searching skills suck just let me know
THANKS!
I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.
you haven't finished , actual OTA is 2.19.40.18
I haven't received that update yet. 2.18.40.12 was the older update and was the one I downloaded/installed.
I had rooted my phone and removed some of the bloatware (I wish I knew better at that time).
But anyway, I got the OTA notification. I unrooted my phone and applied the update.
Things seemed to work fine but when the phone rebooted, the dreaded "Error" dead bot appeared. But unlike many, I didn't get stuck in a boot loop as the phone started normally.
And it looks like the update was applied because the System Update build number shows "2.18.40.12" (earlier was 2.17.40.12)
Should I be worried? Should I flash the stock ROM? Or is there any other method of restoring the bloatware?
Thanks for your time.
EDIT: I flashed my phone just to be sure. I suppose this thread is irrelevant now.
Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
nbhadusia said:
Hi, minor issue but annoying. I sideloaded and uodated to the latest U firmware for Europe this morning. All went smoothly. Now I keep getting the android system update notification. Any way of fixing this?
Thanks in advance
Click to expand...
Click to collapse
Theres is L and X ota too, perhaps it wants one of those?
That would be odd? I'm in the UK running the H build originally. From what I understood, the U build was for Europe.
Good point though. Is there anyone in the UK on the EE network that has let the phone update via the network push. If so, what build got pushed? Cheers
A quick update. I let it install (expecting it to fail). And it worked? Even though I was rooted and running elemental x kernel. I've more ended up on the V build. It gets stranger. I checked the kernel and it was now stock. I panicked thinking they may have locked the bootloader, so I rebooted to check and thankfully still locked. What was strange through is that after the last reboot, I was back on elemental kernel and rooted again?? The build was still V. Everything working fine... I'm just confused
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
nbhadusia said:
Another update. I've rebooted a few times now to see if anything changes between different boots. Looks like I'm running stock V build evertime. Root and elemanntalx kernel lost which I'll flash later. I'm still surprised the OTA for the network push worked even though I was rooted running a custom kernal.
Click to expand...
Click to collapse
“Curiouser and curiouser!” Cried Google (they were so much surprised, that for the moment they quite forgot how to speak good Android).”