I am one of the lucky souls who was able to update their RAZR Maxx HD and keep root, but the radios failed to flash. I'm unlocked too.
I looked up flashing radios through fastboot thinking the radio image was pretty obvious in the Blur_Version.9.16.6.XT926.Verizon.en.US.zip file. In the modem directory there are a series of files, but not an obvious radio image.
I've seen commands such as "fastboot flash radio radio.img" and "fastboot flash radio_cdma radio_cdma.img" on my old phone, galaxy nexus. It doesn't seem the same here for Motorla. Can someone give me a an idea of what we really have for a radio image inside of the update? I'm probably not understanding something that's real simple here, I apologize in advance.
Thanks,
Lenny
Related
So I have my hboot.img in the same folder as fastboot. I CD to that directory. I "fastboot devices" to see that my phones attached. I type:
fastboot flash hboot hboot.img
and I get the following error:
sending 'hboot' <512KB>.... OKAY
writing 'hboot' ... FAILED <remote: partition doesnt exist>
Any suggestions? I assume it's something silly I'm just missing (I hope)...
I started on the rogers dream where everyone installed the danger spl as the rooting process.. so I'm a bit less than used to other spls.
However can you tell us the version of your current spl (and radio in case we can't solve fastboot)
Thanks.
SPL is EngBootloader_v2
Radio is U_2.22.23.02
I could flash it via recovery no problem, but in light of recent revelations about the boot modes and bricking (and "borking") I don't want to break my g1 before I can afford my Nexus
Any advice would be GREATLY appreciated.
EDIT: BTW, I can issue all the commands I tried (reboot, reboot-fastboot, etc) successfully, just not finding the hboot partition. Saw that I'm not the only one with this issue over on forum.cyanogenmod.com/index.php?/topic/2734-partition-does-not-exist/
Anybody think maybe the problem is with the Engineering SPL? More specifically HBOOT-0.95.3000? That is the SPL that I have and I'm experiencing the same error. Maybe we need the HardSPL to fastboot a SPL? Just thinking out loud...
Meh...I just said eff it and flashed it via Amon recovery. It ain't bricked...so thats good.
Jaylen said:
Anybody think maybe the problem is with the Engineering SPL? More specifically HBOOT-0.95.3000? That is the SPL that I have and I'm experiencing the same error. Maybe we need the HardSPL to fastboot a SPL? Just thinking out loud...
Click to expand...
Click to collapse
No .. well in theory anyway hardspl is the eng spl..
The EngBootloader_v2 SPL is not nearly as nice to developers as any of the sapphire ones.. We have no hboot/spl flash that I can find.. It also dosn't appear to be S-OFF.. a problem if we wish to run an unsigned nbh (maybe hard spl can do that)
I think the best option is for me to return to defanging a sapphire SPL to prevent "boot mode 3" thus hopefully allow you to recover if you flash something out of order..
noCOMPLY said:
Meh...I just said eff it and flashed it via Amon recovery. It ain't bricked...so thats good.
Click to expand...
Click to collapse
yes for now that is the way.. just make sure you see a 2x radio in the fastboot screen before going to recovery and flashing..
(ie. if you have a 1x radio.. flash the 2x radio.. reboot to fastboot verify *in* fastboot it is now 2x.. and then and only then think about flashing the danger spl)
Guess thats what I'll probably do too. What about fastbooting an update.zip file with the spl file in it? I'm pretty sure you can do that.
Hi. I'm trying to find out how to fix this for the last few days, but so far without success. After flashing Android Revolution HD 6.0.3 from this thread http://forum.xda-developers.com/show...42&postcount=4, my hboot became locked. I didn't think it would be much of a problem, because I read that I can still flash ROMs, but then I saw this message:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio
--- Don't flash RADIO from ClockworkMod recovery! Extract downloaded file and read the guide inside! ---"
I downloaded the file, read the instructions, but it's not letting me flash the radio since it's locked.
So how can I unlock the bootloader again, without messing sth else up?
I'm sorry if somebody answered similar question already.
Thanks in advance.
tx3m said:
Hi. I'm trying to find out how to fix this for the last few days, but so far without success. After flashing Android Revolution HD 6.0.3 from this thread http://forum.xda-developers.com/show...42&postcount=4, my hboot became locked. I didn't think it would be much of a problem, because I read that I can still flash ROMs, but then I saw this message:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio
--- Don't flash RADIO from ClockworkMod recovery! Extract downloaded file and read the guide inside! ---"
I downloaded the file, read the instructions, but it's not letting me flash the radio since it's locked.
So how can I unlock the bootloader again, without messing sth else up?
I'm sorry if somebody answered similar question already.
Thanks in advance.
Click to expand...
Click to collapse
You are probably on HBOOT 1.23?
If you're using fastboot, it wont work (nothing should be locked as long as your phone still says S-OFF)
Copy the PG58IMG.ZIP to your sd card root, and reboot into bootloader, and simply follow the instructions.
Make sure you delete the file asap or it will keep trying to reinstall .
mrew42 said:
You are probably on HBOOT 1.23?
If you're using fastboot, it wont work (nothing should be locked as long as your phone still says S-OFF)
Copy the PG58IMG.ZIP to your sd card root, and reboot into bootloader, and simply follow the instructions.
Make sure you delete the file asap or it will keep trying to reinstall .
Click to expand...
Click to collapse
Yep I am on hboot 1.23. When you download the recommended radio, it's in an archive named Radio_11.65.3504.00U_11.19.3504.29_2.rar . It contains instruction, adb files, and a file named radio.img . So do I just create an archive named PG58IMG.ZIP, containing only the radio.img file, or there is something else?
And the other thing is that it will be best if I can unlock the bootloader again, because I just found out that I'm not able to flash new splash screen too. I guess that there will be many more things that wont work.
tx3m said:
Yep I am on hboot 1.23. When you download the recommended radio, it's in an archive named Radio_11.65.3504.00U_11.19.3504.29_2.rar . It contains instruction, adb files, and a file named radio.img . So do I just create an archive named PG58IMG.ZIP, containing only the radio.img file, or there is something else?
And the other thing is that it will be best if I can unlock the bootloader again, because I just found out that I'm not able to flash new splash screen too. I guess that there will be many more things that wont work.
Click to expand...
Click to collapse
The bootloader will ignore the extraneous stuff so you could just rename as PG58IMG.RAR and that should work.
Also, even though your Bootloader screen says *** LOCKED ***, as long as you have S-OFF, all you have lost is some of the fastboot commands.
Job done
mrew42 said:
The bootloader will ignore the extraneous stuff so you could just rename as PG58IMG.RAR and that should work.
Also, even though your Bootloader screen says *** LOCKED ***, as long as you have S-OFF, all you have lost is some of the fastboot commands.
Job done
Click to expand...
Click to collapse
I just tried what you said, but I got a message saying: "No image or wrong image found", or something similar to that.
Other ways to flash the radio?
Get your desired radio image from http://forum.xda-developers.com/showthread.php?t=1178143, it's already in the appropriate zip file.
Sent from my HTC Sensation XE with Beats Audio using XDA App
tx3m said:
"With 6.0.x ROMs I strongly recommend flashing 11.65.3504.00U_11.19.3504.29_2 radio"
Click to expand...
Click to collapse
I suppose you flashed the 3.12 firmware. That firmware has the 11.65 radio included
Sent from my Kindle Fire using Tapatalk
ar4l said:
I suppose you flashed the 3.12 firmware. That firmware has the 11.65 radio included
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Well, not really. At least not in my case. My radio version is 11.21....(that's what it shows in the bootloader menu). So I need to find a way to flash the radio. I hope that this could prolong my battery life, because right now with light/medium use, I'm able to use the phone for about 8-10 hours, before the battery is dead, which I find absolutely unsatisfactory.
So if anybody knows how I can unlock the hboot 1.23, or flash the radio I need, that would be awesome )
Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster
sunster00 said:
Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster
Click to expand...
Click to collapse
Typically we can't flash new radios without S-Off. There was a sort of loophole found that allowed us to do it before but I believe it has been fixed with the new hboot.
sunster00 said:
Question for the experts here:
I am on the new hboot 1.14.0002 after taking the OTA update on my 1.88 Asian stock rom (I chose to bite the bullet and go down this route) and now I'm getting "Failed (remote: signature verify fail)" when trying to flash radio.imgfastboot.
I have supercid and am rooted, htcdev unlocked. I also flashed custom recovery (TWRP) and recently a custom rom (KingCobra1x). Interestingly I flashed the boot.img in fastboot without any problem, but not the radio. This is the bit I don't understand.
Am I missing something here? I've read posts that say radio flashing in fastboot still works after upgrading, but that may not be for hboot 1.14.
Thanks in advance,
Sunster
Click to expand...
Click to collapse
If you are rooted you can try just dd'ing it right from android, assuming there's not WP on that partition.
beaups said:
If you are rooted you can try just dd'ing it right from android, assuming there's not WP on that partition.
Click to expand...
Click to collapse
Thanks guys for the replies. I tried dd'ing but no there's WP on partition mmcblk0p17 so that's a no go...
I just thought I would throw in my 2c, I'm on HBOOT 1.11 and am unable to flash radio via fastboot due to the same error. I am able to install the radios in this thread,
http://forum.xda-developers.com/showthread.php?t=1694012&highlight=radios
by just flashing the zip though? Is this expected behaviour?
EDIT:
Scrap that, here is everything I did in order, I can't make any 'sense' out of it...
1) running CM10-20121006 with HTC TELSTRA 1.89(0.18c.32.09.01_10.93a.32.20L) baseband
2) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio via fastboot
fastboot flash radio ~/Downloads/radio/radio.img
FAILED (remote: signature verify fail)
3) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio from zip
SUCCESS!!!
4) dirty flash CM10-20121008, radio has changed to ATT 1.85 (0.17.32.09.12_10.86.32.08L)? WTF?
5) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio from zip
no error but no change in reported baseband
6) attempted to flash HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L) radio using dd
no error but no change in reported baseband
7) dirty flash back to CM10-20121006, radio has reverted to HTC TELSTRA 2.40 (0.20os.32.09.15_10.113.32.28L)? WTF?
I received my phone with version 1.73 and immediately rooted and flashed cm10. Is there any benefits to updating to 2.20? If so what are they?
Between 1.73 and 2.20 there are a significant amount of bug fixes and performance enhancements. Best thing to do is download the 2.20 ruu, extract the rom.zip. in there you will have all the .img files, just flash them all individually in boot loader, making sure not to flash the hboot.nb0. That will update you to 2.20 and keep you on the older boot so you don't need to worry about flashing kernals seperatly from roms.
18th.abn said:
Between 1.73 and 2.20 there are a significant amount of bug fixes and performance enhancements. Best thing to do is download the 2.20 ruu, extract the rom.zip. in there you will have all the .img files, just flash them all individually in boot loader, making sure not to flash the hboot.nb0. That will update you to 2.20 and keep you on the older boot so you don't need to worry about flashing kernals seperatly from roms.
Click to expand...
Click to collapse
Downloading file - ok
Unzipping - ok
"Flashing individual img files" - Hrm.. How does one do that? I can't seem to find a guide for that..
Also, will that remove root access if one has already rooted, or will it still be there?
Will it prevent the phone from updating to the 2.20 OTA?
you will basically have the same thing as 2.20 ota minus the nasty new hboot.
Flash them in twrp?
Flash them in bootloader. Fastboot flash
I am sorry for being noobish when it comes to this. So I put all the image files in the same directory As adb except the h boot. So my phone should be in bootloader mode which is power and volume down when I flash the files. Thanks for all your help
Sent from my One X using xda app-developers app
18th.abn said:
Flash them in bootloader. Fastboot flash
Click to expand...
Click to collapse
Ok, I haven't been able to find a guide or howto on HOW to actually accomplish that (using only the phone and a linux PC)
What are the actual steps to this?
Does one have to have an "unlocked bootloader" to do this?
I'll keep looking, but if anyone can point me in the right direction that would be really cool.
disregard.... I think you would have too dd them individually in adb shell and I don't think there is any sort of tutorial on that method. But go to the stickies and eraste made a good thread on updating safely.
Is it possible for a custom ROM to disable a radio?? I was under the impression (after much Google-ing) that a S-ON phone can NOT modify the radio via IMG file (or any other method).
I have been trying several ROMs on my Desire S and finally found one I really like. Problem is, I no longer get any radio signal (no bars, no service). My Desire is rooted/unlocked, running Cyanogen Mod 9, HBOOT 2.00.0002, S-ON, radio 3822.10.08.04_M, service provider is AT&T US.
Any thoughts HTC gurus? THANK you in advance for any helpful info
-Mike
***Pls no flaming just cause I LIKE a smaller form factor phone. If I could buy a NEW phone with 3.7"-4" screen I would. They just don't make em.
flash the boot.img via fastboot commands straight after u flash the rom. boot.img is in the rom zip. u must do that everytime u flash a rom coz ur s-on.
P88IMG.zip is key, not boot.img.. correct?
I have always completed a boot.img flash after loading any new ROM (otherwise they don't work). I don't think that's the problem because the boot.img has nothing to do with the radio. As far as I know, the P88IMG.zip file is the one that (when flashed) determines the radio version AND it can NOT be flashed on a S-ON phone (like mine).
for some reason i had wifi in my head :what: yh the rom shouldnt do anything to the radio at all, try flashing a different rom (sense) see if the problem is still there then ul know if its hardware