Anybody ever hear anything on a fix for this? The RUU for "real" 2.2 ran and put 2.15 on, which now seems impossible to remove. I have downgraded the radio before to fix this problem, but the radio included in the RUU won't downgrade using any of the previous methods.
The only difference from previous upgrades is that the clockworkmod recovery has been upgraded from 2.5.0.1 to 2.5.0.5 before this install.
NEVERMIND! POSTED IN WRONG AREA... APOLOGIES
Moved you over to Q&A buddy.
Best of luck!
No known fix yet, other than going back to stock 2.1. VZW's only solution is to replace it, same with HTC. Apparently some devices don't like 2.2 enough to allow the speaker to work, so its either stay with 2.1 or get a new one. I had this issue with leaked OTA, RUU, and even the official, from VZW OTA update.
Sent from my ADR6300 using XDA App
I have the same problem with the official OTA. I accepted the update with everything stock (except for S-OFF) and then re-rooted via reinstalling clockworkmod. I have not been able to get the internal speaker working since then.
Am I SOL on returning this thing because I have S-OFF?
Related
Hello everyone. I really need some help here. I had rooted my friends Incredible a while ago. When the 2.2 OTA update came out, he manually upgraded to it. Now, hardly anything works. The phone is always force closing 'System' and it reboots every 5-10 minutes. I doesn't detect that it's plugged in via USB for I can't use ADB to downgrade.
Unfortunately, he didn't do a Nandroid backup, so I can't just revert back using that. Currently, HBOOT is at 0.79.0000 and the radio is at 1.00.03.04.06.
So, to clarify:
Root 2.1 --> OTA 2.2
Now the phone locks up and restarts and only the web browser seems to really work.
Can any of you help me or possibly provide a blank Nandroid recovery image? Any help would be much appreciated. Thanks,
your radio image suggests the 2.2 update wasn't installed correctly. somewhere in the forums is a .img file to downgrade back to stock 2.1, as in the day you opened the DINC out of the box. That should fix your problem. I actually think I have the file.
I've tried searching the forum and I can't find the img. Can you point me to where I can get it? Also, I tried running the HBOOT update with PB31IMG.zip in the root of my FAT32 SD card but it never asked me if I wanted to update.
So to clarify he's on 2.2 with a 1.X radio? If that's the case that's your problem right there. Upgrade your radio to 2.15 and see how things go for you then.
Sent from my ADR6300 using Tapatalk
I'll try that now.
Yodes said:
So to clarify he's on 2.2 with a 1.X radio? If that's the case that's your problem right there. Upgrade your radio to 2.15 and see how things go for you then.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
Yeah, 2.2 should have a radio Baseband of 2.15. But I would just back up to a fresh 2.1 stock and go from there.
Fresh 2.1 stock (will wipe phone):
forum xda-developers com/showthread.php?t=757927
Then install the small OTA update:
unrevoked com/incredible/ota.zip
Then you will be fully ready to install 2.2 with no problems. Sorry my links are funky, I'm a new user and it won't let me post links yet. Hope this helps!
That worked great. Thanks so much.
Hey guys, I should have posted this about a month (maybe even longer) ago, but I've been dealing with some health issues and couldn't be bothered. First off I have a rooted phone (with S-OFF) but I like keeping the stock sense build. I upgraded OTA to 2.2 some time ago, then there was an OTA update a few months after that (which I was able to install without any problems after I replaced a couple of files that had gotten modified), now this newer OTA update refuses to install.
It tells me it needs to reboot to start installing so I click the button to reboot and it counts down, but it never reboots. Is it somehow detecting that my phone is rooted? I would like to have the most up to date OTA update installed on my phone at all times so any help or ideas would be great (also I'm sorry if this has been covered before, I did search but I've been afk for a bit so I might have missed some things).
- DeeBG
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
RMarkwald said:
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
Click to expand...
Click to collapse
Blah I have to go back to 2.2 stock? Oh well, it's not the worse thing in the world (I already had to do it once) and those are great instructions (plus I've wanted to have the latest version of Clockworkmod installed for a while and using Unrevoked means I won't have to mess with the payload/su/etc files). Thanks!
I also thought of something (kind of late though). I was using a custom kernel, which might have been the issue too. But I went ahead and re-enabled S-On, however now for some reason my phone is checking for errors on my SD card (no idea how long it will take, or why it's doing that), but does anyone have a link for that 17.7mb file of the 3.26.605.1 update? I found the full RUU, but it's huge and I rather just upgrade than possibly wipe everything out (and I don't know when my phone will have the OTA ready again). Thanks for any help!
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
bigsapz said:
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
Click to expand...
Click to collapse
That seems to be what that linked thread says, but I don't believe that is correct (that's why I am looking for that 17.7mb OTA file). I was able to install the first 2.2 update (aka 2.2.1) without issue after I restored some files that were altered (either by rooting or installing the wireless tether app that's hosted on Google Code). However this OTA update (aka 2.2.2) isn't popping up again for me to install, so I am going to see if I can extract just the upgrade data from the official RUU. I have to wait until later tonight because I need my phone to be operational for another few hours but I'll post back with results (and files if need be =).
Yeah I tried the RUU update and as expected it did a total wipe... bringing back system via nandroid and will try something else.
Edit: http://forum.xda-developers.com/showthread.php?t=969973 <= using Jay's thread, which is much like the post that was first given to me in this thread. Not re-enabling S-ON seems to be the problem... lesson learned, don't try shortcuts unless you know what you are doing (and I've been afk from the "Dinc Scene" too long for that =p.
Edit 2: Up to date and 100% working!
Hi I would like to know if there would be a problem if I flash the official rue of an Asian desire z with a european version or vice versa?
I bought my phone second hand and I decided to flash the 1.34.707.1 version into my originally 1.72 desire z. Now my phone cannot find updates. It keeps telling me that there is no update even if check manually.
I know that I can flash a higher version by downloading a higher rue version but what I wanted to find out if I can no longer receive ota updates because of what I did.
Since when I was in 1.72 my phone did not notify me of the 1.82 update too...
I don't know what's wrong.. Please help. Thank you.
I think if you are SuperCID and S-Off, it would work. Otherwise, it won't let you flash the ROM from another region.
Also, if you flash an official ROM, you will lose root, and you can't get it back on any ROM version higher than 1.34. For this reason, if you downgraded to 1.34 for purposes of rooting, you don't want the OTA updates, anyway.
If you're rooted and S-Off, and you want a more updated ROM version, just flash the Virtuous custom ROM. Its mostly stock 1.85, but rooted, and with a few cool added features and some optimizations.
Hi, the thing is I'm not very knowledgeable when it comes to rooting. I read the posts here specifically in the wii section and I don't think I have the skills to pull it off and risk bricking my phone.
I think my phone is not rooted or it was before but not anymore, since as mentioned I flashed an official ruu.
So basically, I should still be able to receive OTA's from HTC right? I was wondering why my phone keeps telling me there's no update when the software number is 1.34 stock and not rooted. Shouldn't it notify me that there's an update at least regardless of whether I want to or not?
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
redpoint73 said:
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
Click to expand...
Click to collapse
@redpoint73
I bought the phone from a friend of mine. I noticed that it had eng hboot and had s-off.
I have zero knowledge about rooting. When the gingerbread test rom for the desire z came out, I flashed the pc10img.zip via the bootloader, however since it was very buggy and laggy, I decided to flash stock desire z rom.
Having no knowledge about rooting I read some of the threads in this forum and learned that flashing an official rom i.e. the RUU would be the easiest way to return back to stock.
It worked, I am using stock rom. I experimented and found out that I can flash any of the RUU, so I chose any of the WWE release. I decided to flash an older firmware version specifically, the 1.34.707.1.
Now the problem is my phone doesn't prompt me with an update, even after checking in about phone > check for update.
I still have s-off but eng hboot is gone. To clarify I was not the one who rooted the phone, so I have no idea what to do.
Is it possible that the previous owner tweaked something in the phone that would absolutely prevent it from receiving OTA?
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Please help and thank you again. I extremely as a NOOB!
qtlestat said:
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Click to expand...
Click to collapse
I wouldn't worry about getting the official Gingerbread ROM OTA. It will probably be posted here or at shipped-roms.com long before you would get it OTA.
My HTC desire was originally T-mobile UK Branded. After rooting and messing about with a few custom ROM's I returned it to Stock using:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
Downloaded from xda
It's now clean unrooted, unbranded, stock hBoot HTC Sense 2.2, nice and stable apart from a few problems with text messages.
Question.
Will this phone update to Gingerbread (if it ever does actually appear!!) in it's current state, or will I have to try and find the original T-mobile branded ROM? Which I don't have by the way; anyone got it???
johnroberts said:
My HTC desire was originally T-mobile UK Branded. After rooting and messing about with a few custom ROM's I returned it to Stock using:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
Downloaded from xda
It's now clean unrooted, unbranded, stock hBoot HTC Sense 2.2, nice and stable apart from a few problems with text messages.
Question.
Will this phone update to Gingerbread (if it ever does actually appear!!) in it's current state, or will I have to try and find the original T-mobile branded ROM? Which I don't have by the way; anyone got it???
Click to expand...
Click to collapse
Why did't you just say Rooted and use you best RoM, and wait for the XDA Devs to use official RoM? imo A leaked version will come out before OTA.
since you debranded it i see no reason to not recive OTA
so you should be ok
Does stock Desire have sense 2.1 or 2.2 ?
Sent from my HTC Desire using XDA App
Also wouldnt bother re-branding it as the unbranded version will be out MONTHS before the network versions - if they ever bother to bring one out that is !!
johnroberts said:
My HTC desire was originally T-mobile UK Branded. After rooting and messing about with a few custom ROM's I returned it to Stock using:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
Downloaded from xda
It's now clean unrooted, unbranded, stock hBoot HTC Sense 2.2, nice and stable apart from a few problems with text messages.
Question.
Will this phone update to Gingerbread (if it ever does actually appear!!) in it's current state, or will I have to try and find the original T-mobile branded ROM? Which I don't have by the way; anyone got it???
Click to expand...
Click to collapse
To get OTA updates from your carrier you will need the official rom, the t-mobile roms are listed with the other RRUs in the Dev forum here (look for the TMO RRUs) - http://forum.xda-developers.com/showthread.php?t=695667
a direct link to the latest t-moble RRU i beleave is this one here - http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_127570_signed.exe
hope this helps
OTA on debranded handsets (with a gold card) stopped working with the last OTA update - chances are you'll need to use an RUU (assuming it leaks) OR a custom ROM
I found RUU to make the phone more stable than an OTA to be honest.
When I had 2.1 -> 2.2 the bluetooth was all over the place, kept dropping out etc., and a few other minor niggles.
Flashed 2.2 RUU from scratch and it seemed to 'fix' some of the issues I was having.
Friend of mine tried same but had been factory resetting to try and fix things and I suggested running RUU and he said his phone seemed more stable after that too (rather than the factory reset option)
Not sure how much of the above is just a placebo effect - or the reinstall completely did fix some possibly dodgy files?
Lothaen said:
I found RUU to make the phone more stable than an OTA to be honest.
When I had 2.1 -> 2.2 the bluetooth was all over the place, kept dropping out etc., and a few other minor niggles.
Flashed 2.2 RUU from scratch and it seemed to 'fix' some of the issues I was having.
Friend of mine tried same but had been factory resetting to try and fix things and I suggested running RUU and he said his phone seemed more stable after that too (rather than the factory reset option)
Not sure how much of the above is just a placebo effect - or the reinstall completely did fix some possibly dodgy files?
Click to expand...
Click to collapse
Maybe the OTA update didn't clear cashe correctly when it installed to make a bug. At the end of the day RRUs contain all OTA updates up to a certen point, the reinstall would wipe cashe and data so it would fix the bug you had.
Sent from my HTC Desire using XDA Premium App
Hi, probably going to sound like a N00b question but I haven't yet found answer that fits.
If I have a HOX that is running v1.26 and I root and ROM to something using v1.29 or anything higher than 1.26 can I use the RUU for 1.26 that fits my CID to revert to stock?
Only reason I ask is that I have already had one HOX that I managed to well and truly kill that my provider has fortunately replaced for me (although they don't yet know it's been unlocked!).
The Mic died after a few days from root and ROM onto RD MIUI, but as I had performed a full wipe I had no stock backup to revert to when I then wanted to get it replaced, and so ended up trying all I could to find the RUU for v1.29 but there was only v1.26 available. So I've had to send back my faulty handset with a different ROM on it.
Just looking to avoid a repeat in the future.
Thanks
(Please try to keep your comments helpful rather than mocking)
It is the hboot you can't downgrade. As far as I can tell, it has been updated with every release of the OTA.
If you root and install a ROM with a newer base, the hboot won't be updated (unless it's a newer stock ROM updated by RUU or OTA) you can still go back to an RUU with the same or newer version you have now.