I was wondering that we all need S-Off to our phone to upgrade radio image manually else it gets updated only with either official update or with official ruu update file.....
We all know that we can easily find rom.zip file from the installation process of an official RUU.... I was wondering that if in between the process when the installer check information on our phone, if open the installer and get the rom.zip to change the radio.img from radio.img of europe or any other latest ruu, would it update the device with the latest radio ????
I m going deep into this process cos I couldn't get my phone S-Off due to certain reasons and want to get the latest radio update but I m bootloader unlocked which won't let me update the radio using fastboot commands cos it could only be done using official installation process....
If this helps then all of us would be able to b on the latest radio from htc which has an advantage of higher signal receiving capacity............
nikhilkaushik said:
I was wondering that we all need S-Off to our phone to upgrade radio image manually else it gets updated only with either official update or with official ruu update file.....
We all know that we can easily find rom.zip file from the installation process of an official RUU.... I was wondering that if in between the process when the installer check information on our phone, if open the installer and get the rom.zip to change the radio.img from radio.img of europe or any other latest ruu, would it update the device with the latest radio ????
I m going deep into this process cos I couldn't get my phone S-Off due to certain reasons and want to get the latest radio update but I m bootloader unlocked which won't let me update the radio using fastboot commands cos it could only be done using official installation process....
If this helps then all of us would be able to b on the latest radio from htc which has an advantage of higher signal receiving capacity............
Click to expand...
Click to collapse
I *think* its possible to update the radio while s-on. But a downgrade would not be possible at all.
Sent from my HTC Sensation XE using xda premium
Found another way out !
heavy_metal_man said:
I *think* its possible to update the radio while s-on. But a downgrade would not be possible at all.
Well I m sure downgrading needs a way out but I have found a way to get radio and hboot updated while staying s-on and unlocked....
If we install an RUU directly on unlocked state it doesnt get installed and gives some error but if we manage to install correct region files from the RUU made for our own region and only, system.img, recovery.img and boot.img needs to be flashed through adb tools using fastboot commands and when its done, just be patient and let the installation complete and then when it starts, we get a fresh mobile with new NON-ROOTED phone.... Don't root it so far and check system for updates and let it update and voila ! It'd update radio and hboot....
I m not sure what my hboot version was before update but my radio version was 7.53 before update but after it turnt into 7.57............
Click to expand...
Click to collapse
Or you could take the radio from the ruu rename it to pg76img.nbh (I think) and boot to BootLoader
As long as it is an update it should work without an issue
Sent from my HTC Sensation XE using xda premium
What I did was:
1) Lock bootloader using 'fastboot OEM unlock'
2) Extract rom.zip from an ruu (NOT the latest!) and then separate it into system.img, boot.img, recovery.img, etc...
3) Using fastboot, flash system.img, boot.img and recovery.img.
4) Again, using fastboot, wipe the data and cache partitions.
5) Now boot into your stock android.
6) Download the latest ruu and run it, following the on screen instructions.
7) This ruu will update your entire phone (INCLUDING the radio) to the latest version.
8) Now, reunlock your hboot using htcdev.com.
9) Flash clockworkmod recovery using fastboot.
10) Install whatever custom rom you want, or keep the stock rom.
Simple!
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app
Well done man
Sent from my HTC Sensation XE using xda premium
Thanks, I don't have a clue about developing roms. But I'll give back to the xda community in any other way I can...
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app
I did the same !
artturnip said:
What I did was:
1) Lock bootloader using 'fastboot OEM unlock'
2) Extract rom.zip from an ruu (NOT the latest!) and then separate it into system.img, boot.img, recovery.img, etc...
3) Using fastboot, flash system.img, boot.img and recovery.img.
4) Again, using fastboot, wipe the data and cache partitions.
5) Now boot into your stock android.
6) Download the latest ruu and run it, following the on screen instructions.
7) This ruu will update your entire phone (INCLUDING the radio) to the latest version.
8) Now, reunlock your hboot using htcdev.com.
9) Flash clockworkmod recovery using fastboot.
10) Install whatever custom rom you want, or keep the stock rom.
Simple!
Sent from my HTC Wildfire S with Beats Audio using xda app-developers app
Click to expand...
Click to collapse
Well I did the same And now I m happy with my new radio
Won't work !
heavy_metal_man said:
Or you could take the radio from the ruu rename it to pg76img.nbh (I think) and boot to BootLoader
As long as it is an update it should work without an issue
Sent from my HTC Sensation XE using xda premium
Click to expand...
Click to collapse
This process won't work until the device is S-Off cos it doesn't get permission to write the radio until it is S-Off. Device unlocked won't help !
nikhilkaushik said:
This process won't work until the device is S-Off cos it doesn't get permission to write the radio until it is S-Off. Device unlocked won't help !
Click to expand...
Click to collapse
Hmm. I didnt think it would have an issue with an official update. Well that's proved me wrong
Sent from my HTC Sensation XE using xda premium
Related
is there any risks after flashing the radio ???
rom acesmod v35 sence 2.1+3.0 gb
Sent from my HTC Desire using XDA App
take latest radio zip - afaik: 32.56.00.32U_5.17.05.23.zip
flash zip via recovery, reboot
and then WAIT a moment!!
first time i thought my desire is dead - but wrong, radio update needs its time
you should not disturb the update process cause of bricking ;-)
normally no problem - but like always: no guarantee ^^
I'm not sure if it is good idea flashing radio through recovery if you are using custom hboot (if i'm not wrong acesmod has a CM7 hboot support). So if that's the case then you are certainly acquainted with fastboot (android SDK) so try flashing it through it, alternative options are fastboot commander or android flasher...
ser.clansman said:
I'm not sure if it is good idea flashing radio through recovery if you are using custom hboot (if i'm not wrong acesmod has a CM7 hboot support). So if that's the case then you are certainly acquainted with fastboot (android SDK) so try flashing it through it, alternative options are fastboot commander or android flasher...
Click to expand...
Click to collapse
If you're S-off, there are 2 reasons why NOT to use recovery so far as I can see
1) Your cache parrtition must be Over 25MB free to use recovery as this is where the zip unpacks the image
2) Remove an extra layer of software to flash something. Fastboot is much better and safer
thx all but acesmod have stock hboot and that iam using
i dont use custom hboot ever
but at all there is no downsides of flashing radios right?
and yes iam s-off
Sent from my HTC Desire using XDA App
conzul said:
take latest radio zip - afaik: 32.56.00.32U_5.17.05.23.zip
flash zip via recovery, reboot
and then WAIT a moment!!
first time i thought my desire is dead - but wrong, radio update needs its time
you should not disturb the update process cause of bricking ;-)
normally no problem - but like always: no guarantee ^^
Click to expand...
Click to collapse
I thought that Radio had to be flashed from the bootloader? at least that is the case on a desire Z
no from recovery
Sent from my HTC Desire using XDA App
conzul said:
take latest radio zip - afaik: 32.56.00.32U_5.17.05.23.zip
flash zip via recovery, reboot
and then WAIT a moment!!
first time i thought my desire is dead - but wrong, radio update needs its time
you should not disturb the update process cause of bricking ;-)
normally no problem - but like always: no guarantee ^^
Click to expand...
Click to collapse
i though i passed woring from bricking after root and s-off flashing several roms lol
Sent from my HTC Desire using XDA App
deleted
I stand corrected.
thx guys i flashed the new radios nothing work lol
no cell no sms no wireless no bluetooth no nothing
i think iam fu*ked
returned no stock
workes fine for me
So i somehow went hiroshima on my one x. I'll keep it short and simple. Had my BL unlocked but was running CWM recovery and the stock rom. Tried installing the cyanogenmod 9 and things went to hell after i flashed the boot.img. Now I am stuck at the white HTC screen. I read the disaster recovery but I am still having no luck. I relocked the bootloader and reflashed stock recovery then i tried using the ruu utility but it said that it didnt match and then rebooted with some developer text on the boot screen. I used the getvar command and it says:
version-main: 1.28.720.10
Before the blowup I had ran the OTA.I was on 1.26.720.10. This is the ruu i tried to reflash. I cant seem to find the 1.28.720.10. I also tried pulling the sys and boot img files from the temp directory and manually flashing, it gave an error.
as of right now i have the bootloader unlocked again and CWM recovery reinstalled so i can charge.
please help! $20 reward via paypal to the person that helps me get back to complete stock!
The worst part is i dont even want this damn phone...lol
Try this mate. If you can still get to bootloader and recovery it recoverable. I'd go back to stock so its as if you bought the phone, just to be safe. So...
Open cmd and CD to your fastboot file location. Plug phone in and...
First flash a stock boot.img from your stock.zip
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
Then relock your bootloader.
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
Then run the RUU.
But make sure you have the correct one. So that includes region. If you started on 1.26 and you haven't done any OTA updates then you need 1.26 but with your region code.
Good luck!
Sent from my HTC One X using xda premium
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
applejoos said:
i did do the ota to 1.28 before i blew it up. also, how do i find the right region code? WHen i searched google for the results of my getvar version-main i found a bunch of threads referring to that being the ota for india, so thats the ruu i downloaded from the fileshare. i was working off a hunch though.
Will I be able to use a 1.26 RUU if I updated to 1.28, seeeing as how my getvar says 1.28?
Click to expand...
Click to collapse
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
benjamin.j.goodwin said:
Yeah if you did the OTA you need to use the 1.28 RUU as your hboot will have updated along with either things so 1.26 won't work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
So since there is no RUU matching my version number I am screwed now right?
Use the 1.29 ruu?
backfromthestorm said:
Use the 1.29 ruu?
Click to expand...
Click to collapse
there is no 1.29 for my region code.
applejoos said:
So since there is no RUU matching my version number I am screwed now right?
Click to expand...
Click to collapse
Do you know how to push a ROM.zip on to your SD card via command prompt?
Try downloading a custom ROM and flash the boot.img then, clear cache, then boot to recovery and flash the ROM. Then reboot. Should work.
Sent from my HTC One X using xda premium
I'm trying to help a friend remotely fix his current brick of a HOX and would like some pro advice to ensure im telling him the right thing. Info I have:
Its S-On UK T Mobile CID T-MOB005.
He obtained a 1.39 firmware from somewhere that matched his CID
At some point in the process the firmware flash failed or partially flashed
His Custom Recovery is gone
His HBoot version has not increased (i think 1.12)
He has a security warning under the 'relocked' message in bootloader
Before he tried the firmware upgrade he flashed viper x 3.4.0 + boot.img so the phone wont boot up normally now
He has a nandroid backup from before the process.
Im going to recommend to him to download the 1.36 firmware from Mikes thread here http://forum.xda-developers.com/showthread.php?t=1957376 (i notice there is no 1.39 available for his CID so im suspicious this was a duff file he had for 1.39)
If he cant flash it because of low power then he should use the charging batch script first or re-unlock, flash CWM, restore nandroid and flash the boot.img from it so he can boot phone and charge it normally or from cwm.
I guess after that start to look at an RUU or a stock nandroid backup download to be able to do the firmware OTA ?
My own HOX is S-Off so im not as familiar with the process as i never worried about the correct firmware or had to flash boot.img separately from roms or nandroids.
Any tips appreciated.
Cheers
Re: Hboot upgrade attempt failed
Yeah that's about it.....only flashing the rom is not going to work because of the low hboot.
Just charge the battery and and unlock the bootloader, then reflash a custom recovery and charge the battery up in there.
With enough power he can relock the bootloader and flash the firmware
Fastboot oem lock
Fastboot rebootRUU (watch the capital letters)
Fastboot flash zip firmware.zip
Unlock the bootloader
Fastboot flash unlocktoken unlock_code.bin
Then flash the custom recovery again and install a new rom ! :thumbup:
Cheers, so out of interest what causes the Security Warning in the bootloader ? Is it because the phone knows there is a screwed up firmware flash or knows it cant boot\has low power ? It must have done something as his custom recovery was wiped even though the Hboot ver didnt change.
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Re: Hboot upgrade attempt failed
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
You have to relock the boot loader to flash an updated firmware which is the point you are at and why you are seeing the security warning.
The first time you flash the updated firmware it flashes everything else.
Stock recovery, boot.IMG and sometimes other partitions.
Then it tries to flash the hboot and fails.
All you usually have to do is tell it to flash a second time and then in succeeds in updating boot.
Obviously he stopped after the first attempt which is why only the recovery changed and not the hboot.
I doubt he has a bogus firmware as the phone will not attempt to flash anything that isn't signed and cid matched.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Great will check, just assumed he had tried it twice as all instructions I've seen state that you must but then again i dont know what instructions he followed - maybe he didnt ! Ive not seen this explanation of whats being flashed and in what order before - cheers.
Mr Hofs said:
how does the security warning look like exactly.....i know there is a warning because the bootloader is relocked. don't know if we are talking about the same picture now
Click to expand...
Click to collapse
Ive not seen it but i assume its something like this
*** RELOCKED ***
*** Security Warning ***
Then all the usual bootloader stuff
based on images ive seen before on web. can find them with a quick google of images.
Re: Hboot upgrade attempt failed
Yeah that's normal :thumbup:
Re: Hboot upgrade attempt failed
Ok it lives ! Was a combination of the firmware file and his battery being too low to flash so he put cwm back on, charged and then followed my instructions. Cheers for help
This is the what I sent him incase anyone else finds them useful. Assumes you know roughly what your doing and that you must get back to fastboot usb for the commands .
-----------------------------
So get phone into fastboot mode by power plus vol and choose it in bootloader., plug usb in so it says fastboot usb, then get command prompt in directory with fastboot in on pc.
1. Lock bootloader with: fastboot oem lock
2. Vol and power down to get into bootloader again
3.fastboot oem rebootRUU
4. Should now get phone with silver HTC in middle on black
5. fastboot flash zip firmware.zip where this is the new firmware for your cid.
6. Might fail first time. Do it again and it works
7. Should now see green bar completed under the htc
8. Power and vol to get to bootloader. The hboot should now be updated.
9. Now to unlock bootloader again
. fastboot flash unlocktoken unlockcode.bin (where unlockcode.bin is the file you got from htcdev)
10. Now on the phone select yes and it reboots.
11. Don't wait just use power and vol to get into bootloader.
12. Flash custom recovery again. fastboot flash recovery recovery.img where recovery.img is the cwm 5.8.4.0
13. You can now flash your chosen Rom boot.img. fastboot flash boot boot.img
14. fastboot erase cache
15. Now use recovery to flash the Rom.
16. Done
Sent from my HTC One X
Very good :thumbup:
CASE CLOSED !
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
ViktorN said:
I have to say that the OP did a great job at providing the needed information. I wish everyone would describe their problems as good as the OP of this thread, it would make helping people out hell of a lot easier.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So true !
Indeed. Not very often you can tell exactly where a problem is without having to ask for more info. In fact. A thanks to the op for providing a very detailed diagnosis without even having the device to hand
Sent from my HTC One X using xda app-developers app
Hi All
I tried the ace hack kit again to get s-off and really messed up
It went through the process until it said radio flashed please wait....
Phone rebooted and stuck on the white htc screen
Managed to recover with a pd98.img but this has wiped my root and 4ext and the phone boots into 2.33 sense 2.1
hboot has changed from 2.0xxxxxxx to 0.85.0024
Problem is when i do the htcdev procedure to unlock the bootloader i get an error when running fastboot oem get_identifier_token
It just says bootloader command error
Help!!
Stu
You'll need to update the firmware to the latest
hacktrix2006 said:
You'll need to update the firmware to the latest
Click to expand...
Click to collapse
How do i do that if i cant unlock the bootloader to install a custom recovery?
You download the lastest RUU you can find for your phone from
http://forum.xda-developers.com/showthread.php?t=2094087
hacktrix2006 said:
You download the lastest RUU you can find for your phone from
http://forum.xda-developers.com/showthread.php?t=2094087
Click to expand...
Click to collapse
Ok thanks
My DHD was originally branded Virgin from the UK the cid is VIRGI001
I can see some UK Orange on the site but cant see a virgin
Which one can I use?
Stu
Then you will need to make a Goldcard then download the WWE Version then run the .exe and get the rom.zip file copied some where then with goldcard inplace run fastboot with the following commands
fastboot oem rebootRUU
fastboot flash zip rom.zip
That will then flash it. make sure before running fastboot your in the same place as fastboot and the rom.zip file though
hacktrix2006 said:
Then you will need to make a Goldcard then download the WWE Version then run the .exe and get the rom.zip file copied some where then with goldcard inplace run fastboot with the following commands
fastboot oem rebootRUU
fastboot flash zip rom.zip
That will then flash it. make sure before running fastboot your in the same place as fastboot and the rom.zip file though
Click to expand...
Click to collapse
Ok made the goldcard (hopefully)
My image build is 2.50.405.2
There isnt a build higher than this on the list but there is a wwe build with the same number
RUU_Ace_Gingerbread_S_HTC_WWE_2.50.405.2_Radio_12.54.60.25_26.09.04.11_M2_release_199042_signed
All the other builds are lower
Will this work?
Stu
ps
On Windows 7 any idea where the rom zip is extracted to when the exe is run?
Rom.zip will be any one of the folders in temp just type %temp% in run box. As for the Rom if that's the latest then it's the latest.
Also 3.x.405 is latest
Sent from my HTC Desire HD using xda app-developers app
All looks like it worked
The fastboot sent a load of files to the phone
And it completed ok
But phone is still on the black htc screen with the green progress bar appx 95% across
What do i do now?
If fastboot says completed just type.fastboot reboot
Sent from my HTC Desire HD using xda app-developers app
Ok waited about 10 mins then did fastboot reboot
Nothing changed and i still cant get_identifier_token
See attached
Stu
Have you installed the HTC dev boot yet if not then do the same with that
As you did with the ruu via fast boot
Sent from my HTC Desire HD using xda app-developers app
Hi Hacktrix
You're being really helpful and I appreciate it.
Sorry for being a bit thick but what do you mean by installing the HTC dev boot?
Have i missed something?
I cant get the token still as it still says bootloader error
Flashing the rom.zip seems to go without error but nothing changes on the phone
Cheers
Stu
Not a problem. Right have you gone to the HTC dev site and registered
Sent from my HTC Desire HD using xda app-developers app
If so i can do everything for you including S-Off'ing your device if you want that done too.
Yes im reg on htcdev
I already htcdev unlocked this phone prior to me messing it up with the ace hack kit
yes id like it s-off as well
Just easier flashing roms as before had to flash rom and fast boot the boot.img
stu
Send me a PM and i will help you ok mate
pm sent with my email addy
Cheers
Hi. Is it possible to install official T-mobile G2 RUU software on HTC Desire Z?
So long as radio secure flags are removed (s-off) then yes, but I can't think of a great reason to do so
Sent from my Nexus 4 using XDA Premium 4 mobile app
I love AOSP. So I can download RUU eg. from here and simply run the installer?
Yes but that would leave with a shipped bootloader, stock recovery and a non rooted ROM. Maybe a worse radio too. Why not just flash a stock rooted ROM?
I can simply root it again by eg UnlockRoot program. but I want to have clear software, I dont like custom roms. And also I cant find newest 2.16.531.6 ziped rom. I prefer to install this RUU.
...but first I have to fix my phone. I dont know why, but I cant run anu RUU installer (even this for DZ). when I click "update" button, it is waiting for bootloader, and after this there is a comunicat that phone is unpluged. I wonder I have to do this with ADB
But thanks for your answer this is what I wanted to know
Sort of, if using some unlock program for root I have to imagine your not s-off and if you are its fake s-off which if you were to run the RUU you may brick your device. The only method you should use to root your phone is exploit via gfree.
As for custom ROMs, that's your choice but I will say there are ROMs that are more aosp than stock T-Mobile as all the g2 stock isn't pure aosp. Buy of course do as you will.
As for your RUU issues, it won't have anything to do with adb as they are to be flashed through fastboot, but again be careful as what you want to do is possible but if you don't meet the prerequisites you will have a brick
Sent from my Nexus 4 using XDA Premium 4 mobile app
Ok, you are right. I'll flash some another aosp.
But now, this RUU issue.
So, from the beginning:
I changed the hboot to g2 one with this PC10IMG. Just flash by bootloader. Then I flashed the PC10IMG_Vision_TMOUS_2.15.531.3_Radio_12.52.60.25U_26.08.04.30_M3.zip. also by bootloader. Then found out that I cannot use RUUs installer because the phone dont wont to reebot into bootloader. So i change hboot to dz one with this PC10IMG. Now my hboot version is 0.84.2000 (PC1011000).
I installed some custom rom (virtuous sense 2.0.0).
I am running RUU software (RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.3_Radio_12.56.60.25_26.10.04.03_M_release_224299_signed.exe).
returning to the bootloader - is ok, phone is reebooting. But next is 'waiting for bootloader' and the Error, that the phone is unplugged.
On the phone screen for a while was the Black screen with Gray HTC logo, but for the moment there is white screen (looks like bootloader) with hboot version, Radio version, etc,
and at the end is: RUU
I hope you understand me.
What shoud I do? mayby the hboot version is incorect?
edit
I also cannot install 1.34.405.5_PC10IMG.zip by bootloader now. The files are loading, and then.. is nothing. There is no quastion for Update( vol up) or No (vol down)
edit2
Uff, the problem is solved. I hadn't installed bootloader drivers and radio was very old, so I had to update it. Thanks for your help, demkantor
No problem, I would advice to look through this thread a bit as well
http://forum.xda-developers.com/showthread.php?t=2348266
You'll also find those asop ROMs there
Sent from my Nexus 4 using XDA Premium 4 mobile app