Database Develop

Radio update help..

...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!

which recovery image do you have installed

maruutah said:
...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!
Click to expand...
Click to collapse
If your using Cyanogen's recovery, try to physically press the alt-s, and home + back to reboot
I believe it works like that for flashing the IPL (radio) and SPL
where did you get the radio from?

Sorry I left out the recov info, I know my signature is misleading...didn't change it yet..!
I'm using JF 1.43 recov, I remember that (not sure if it was ever fixed, all I know is that flashing the SPL with CM recov caused 'error at line ___' when flashing new roms) that you cannot flash the new SPL with cyanogen recovery, so I'm using JF's until I get the radio and spl flashed correctly.
I got the radio from where I usually have in the past, as well as the new SPL
http://sapphire-port-dream.googlecode.com/files/
(Of course I will not flash the latest SPL until the newest radio is flashed first!)
I just want my happy CM 3.9.7 back..! With the ability to flash the new hero roms when I get curious..
****I am now attempting to flash the radio with cm recov 1.4, will update on this if it works.
****no luck with cm either, didn't think it would make a difference but thought I would give it a shot. I still have 1.22.12.29 for my radio :/ agh!

So...Still can't update the radio for whatever reason, just does not take, and I still can't find anything in the forums about this either... :/ Anyone have any ideas at all?

get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.

david1171 said:
get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.
Click to expand...
Click to collapse
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/

Nope, no matter where I download from and how many times I flash with different recoveries.. I still have the original radio 1.22.12.29 :/
This has always been so easy! I've never had issues with rooting, then updating the radio, then updating to the new SPL.. :/

maruutah said:
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/
Click to expand...
Click to collapse
If you can, try rerooting, it will only be a few more steps.

B-man007 said:
If you ca try rerooting, it will only be a few more steps.
Click to expand...
Click to collapse
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/

maruutah said:
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/
Click to expand...
Click to collapse
I don't know why its not updating your radio, but everything else works fine. You should update the radio before updating to cupcake builds. maybe that will help?

gave up for a while, finally re-rooted
Re-rooted and still cannot update my radio, I have tried updating it after the very first rooting steps, after updating to JF RC33 as well, I still can't get the latest radio to get onto my phone. I have tried with JF recovery, CM recovery, as well as the original recovery image, and nothing. Notta. Zip. No idea why my phone simply will not take the new radio image.. I have re-downloaded it a million times as well, going in circles..don't get why the phone will let me root, unroot, all that jazz, and simply will not let me update the radio... driving me nuts!! I can use CM roms just fine of course but any other roms I am stuck with not trying cause of this annoyance!! Anything anyone can recommend would be great

o man still can't get it to work?
try flashing the official 1.5 OTA update, which contains the updated radio. see if it gives you an error message. if it does, take it to tmobile and tell them to replace your phone.
if it flashes...see if it updated your radio. if it did, you can use the one click root to root your phone

Thanks again buddy, I will try it out ^^

So, I unrooted, and applied the OTA updates from 29 to 30, 30 to 33, 33 to cupcake..and I still don't have the latest radio, still at 1.22.12.29. I got the ota cupcake here:
https://android.clients.google.com/updates/partner/signed-kila-ota-150275.53dde318.zip
i'm going to try flashing the ota radio update without root if it will let me..grr..this is so weird, there is no reason why it shouldn't take a simple radio update..hrm
***attempted the ota radio update, guess you can't without root which is what I figured, but frick, this makes no sense.. >>

so, this is a bit odd, at http://developer.htc.com/adp.html, one of the spots to DL the latest radio, when you hover over the radio link for 1.5 and 1.6, it says "ota-radio-1_22_14_11.zip" rather than "ota-radio-2_22_19_26I.zip", weird, eh? Wonder if it's simply not the right radio, and labeled wrong, I have no idea, but this is getting super old.

I'm actually having the same problem, can't seem to update the radio with the radio image the htc site provides. It's still stuck at 1.22.12.29

Anyone had this before? Any help would be appreciated

I can't get around it, and it's really frustrating, since the only rom I can use is a CM build..aside from a couple others, but CM is the best as far as universal SPL use goes..

So what I've tried so far:
- Updated to HardSPL
- Tried multiple Radio updates, new ones, old ones, even some from the forums.
- Tried a few complete updates that include the radio image
- Tried flashing directly from fastboot, not sure what partition I need to flash though, the radio partition gives me an error that it does not exist.
Still no go. The weird thing is that I come from a stock 1.5 installation updated from 1.0 via t-mobile. And I'm still at the original 1.0 radio image.

[Q] Help updating to 2.32.651.2

I rooted my wife's Hero with the z4 method, I couldn't get unrEVOked to work for us, and removed some bloat with Titanium Backup.
I only did it out of my own curiosity, no particular need. She's running 2.31.651.7 and now an OTA update for 2.32.651.2 is being pushed out. She's a "I just want my phone to work" type, so I'd like to get her this OTA installed for her peace of mind.
I restored the uninstalled apps and "unrooted" in z4, but when I tell the auto-updater to go ahead with the OTA it just dies 1/4 of the way into the install and pops the exclamation point graphic.
Any thoughts? Any other Hero owners have success with a (formerly) rooted 2.31.651.7 to 2.32.651.2 upgrade?
(I searched around, no one seemed to have any threads indicating they got this to work... only ones saying they were able to root 2.32.651.2)

You could install Htc sync on your comp. then d/l the .7 ruu then try to update from the phone.
skylar.sutton said:
I rooted my wife's Hero with the z4 method, I couldn't get unrEVOked to work for us, and removed some bloat with Titanium Backup.
I only did it out of my own curiosity, no particular need. She's running 2.31.651.7 and now an OTA update for 2.32.651.2 is being pushed out. She's a "I just want my phone to work" type, so I'd like to get her this OTA installed for her peace of mind.
I restored the uninstalled apps and "unrooted" in z4, but when I tell the auto-updater to go ahead with the OTA it just dies 1/4 of the way into the install and pops the exclamation point graphic.
Any thoughts? Any other Hero owners have success with a (formerly) rooted 2.31.651.7 to 2.32.651.2 upgrade?
(I searched around, no one seemed to have any threads indicating they got this to work... only ones saying they were able to root 2.32.651.2)
Click to expand...
Click to collapse
Sent from my HERO200 using XDA App

If you have a custom recovery on it you can flash NFX's .2 update rom

FdxRider said:
You could install Htc sync on your comp. then d/l the .7 ruu then try to update from the phone.
Click to expand...
Click to collapse
The only downloads available at htc.com are the latest version of HTC Sync and the 2.27.x.x Eclair release. The Eclair release would completely wipe and reset the device, which is a huge pain in the butt.
Any other thoughts?
Anyone know how to retrieve the log file from the update process? Maybe I can debug what is failing.

Skylar you have to install the .7 ruu (which takes about 10 mins.) Then once the .7 ruu is installed and phone is booted back up go to system updates and update ota. That should do it ,I agree with kyoko I would have flashed nfinite's .2 rom same thing as the .2 update from sprint
skylar.sutton said:
The only downloads available at htc.com are the latest version of HTC Sync and the 2.27.x.x Eclair release. The Eclair release would completely wipe and reset the device, which is a huge pain in the butt.
Any other thoughts?
Anyone know how to retrieve the log file from the update process? Maybe I can debug what is failing.
Click to expand...
Click to collapse
Sent From My Pedal-to-the-Metal Hero!

FdxRider said:
Skylar you have to install the .7 ruu (which takes about 10 mins.) Then once the .7 ruu is installed and phone is booted back up go to system updates and update ota. That should do it ,I agree with kyoko I would have flashed nfinite's .2 rom same thing as the .2 update from sprint
Click to expand...
Click to collapse
I think you're confused.
I'm on .7
I can't update to .2 (it fails)
There is no downloadable RUU .2 or .7 available from HTC
HTC does have a published file from the original Eclair rollout to the Hero... but it wipes EVERYTHING off the device, including apps and data.
I don't want to start over

[Q] S-OFF, Won't flash HERCIMG

I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!

I was just told today that some phones that flash the eng-spl won't flash hercimg. Perhaps your wife's is one of them. I'm also told that ruu-ing the phone will remove the eng-spl and you should be able to flash a hercimg through hboot without eng-spl.
Edit: I'll also say that this information is less than 24 hours old for me, I'm no expert.

Drummerboy527 said:
I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!
Click to expand...
Click to collapse
When you say you can't get it to flash, what stage is failing? Does the bootloader not recognize the HERCIMG? Will it not install the .img? A little more detail, pls.

I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.

Drummerboy527 said:
I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.
Click to expand...
Click to collapse
If you ruu'd you took away your ability to flash through the bootloader, unless you used regaw's method to gain s-off. Does your bootloader show s-off at the top?

Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.

Sorry my mistake, I should have clarified that comment Yes, I used Regaw's method originally for S-OFF, which is still S-OFF even after the RUU as it should be.
This was originally how I ran into this problem as the HERCIMG was not flashing even as S-OFF 1.47.0000. So I flashed ENG-SPL to try something different with no change, then RUU-ed and tried again. Still nothing. Had to reroot and restore

Drummerboy527 said:
So I flashed ENG-SPL to try something different with no change . . .
Click to expand...
Click to collapse
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.

24601 said:
Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.
Click to expand...
Click to collapse
I used ruu 2.27.651.6. I actually saw this happening in another thread (still cannot find it) and so I tried that also. I have a HERCIMG with both a 2.27.xxx and a 2.31.xxx. Here is what I did with my phone:
Ruu-ed with 2.27.651.6, applied OTA update to 651.7, then applied the next update .2. Flashed the HERCIMG with a 2.27.xxx android-info.txt that was the latest CWM from jasonmaloney's thread (renamed as recovery.img). Worked like a charm!
My wife's phone:
Prior to Ruu (An RUU has actually never been done on this since we originally purchased it), I actually attempted to flash the latest CWM since the current version was 2.5.0.7 thru HERCIMG to test it out. No luck!
Thought that maybe ENG-SPL was causing the problem so I RUU-ed 651.6. Attempted to flash HERCIMG under S-OFF 147.0000 which the bootloader ignored.
I never updated beyond that as I couldn't get some of the newer methods of rooting to work so I rooted .6 and restored the nandroid while I continue the research.

24601 said:
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.
Click to expand...
Click to collapse
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.

Drummerboy527 said:
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.
Click to expand...
Click to collapse
The member you saw mention this issue is vayman, he has literally the exact same issue having followed the exact same steps a few days ago. I hope you can figure it out.
sent from a series of tubes.

Flashing Problems

I installed 2 mods last nigh on my vivid and it messed up phone. I am trying to go back to Stock Firmware but when i run the RUU for my phone it tells me the current firmware is GT-P7510-user an will not install the RUU. Any one have a idea how to fix it.I have tried other RUU's and the same thing.
Thanks

Can we say "Idiot" I had my tablet plugged in now it works

Lol that's awesome

Reboot loop

MOD: please feel free to move this to Q&A, my bad.
I've tried PACman, I've tried CM10, I've tried tried the Stock ish. CM10 and PACman get to the initial setup screen where I choose a language and when I hit start, or activate USB mass storage, it freezes for a moment then reboots. On the Stock ish one it gets to the Beats logo or AT&T and freezes, then reboots. I've tried the RUU executable and it errors out (but all it says is there's an error, try the correct one executable). Does anyone know what's likely the cause of my problems, and how to fix it so I can just get my phone working? I've been working on it for 18 hours straight, I haven't even eaten anything in nearly 24 hours, and it has been stuck and incapable of rebooting for nearly 12 hours.
Additional details: I was attempting to install PACman and I had some issues, then I used the RUU for Gingerbread (because I didn't realize it was Gingerbread) and got my phone working again. The Bootloader is JB, and it's S-OFF.

this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom

ZeRo2o9 said:
this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom
Click to expand...
Click to collapse
Neither the ICS nor the GB RUU will work. It just says there was an error, and to please try the right RUU.
EDIT: So I'm guessing that basically I need to get the GB RUU to work, then OTA update to ICS, then continue with everything. How do I get the GB RUU to work? How do I even troubleshoot the fact that it's not working?
EDIT 2: I was wrong, it's giving ERROR [156]: IMAGE ERROR.
EDIT 3: I think I found the problem. The RUU is blank when it says what image ROM it's going to update the device to. Anyone know how to fix that?
EDIT 4: the RUU says its current version is the same as the ICS RUU.

have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted

Zero's got the right idea!
yup...that's exactly what I'd do, even if it were a stock AT$T RUU rom...better than nothing...

ZeRo2o9 said:
have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted
Click to expand...
Click to collapse
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!

HopelesRomantc91 said:
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!
Click to expand...
Click to collapse
I had a sneaking suspicion your original RUU was corrupt...Glad it all turned out

just a heads up if you are using Chrome to download these files.. i personally have had TONS of issues downloading large files with Chrome and would recommend using FireFox to download files bigger than 200MB maybe even smaller.. and the RUU's if i remember correctly are around 400MB.. just for future reference since you've already fixed your issue..