Database Users

Radio update problem...

Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?

I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.

speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition

That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.

AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer

You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.

yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..

bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!

Turn your phone off, hold the camera button down, and power on your phone.
What do you see?

each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.

speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer

speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer

I've got HBOOT 1.46

Hey, all.
I have been silently following the Eris section of XDA for months now, mostly checking out all of the features with ROMs. I really started looking into rooting my phone a few weeks back, and I'm *pretty* sure I'm going to run Ivan's with Zanfur and gr0gmint's JIT.
In any case, I sent a PM over to jcase tonight because, with the new root methods available, I didn't know which to use when I finally decided to root.
Turns out, he'd never seen someone having hboot 1.46 before, but I do.
Here's my info from Power On + Vol Down:
PB00100 XC SHIP S-ON
HBOOT-1.46.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
Oct 5 2009, 19:21:56
HBOOT
<SEND> FastBoot Mode
<VOL UP> Recovery
Click to expand...
Click to collapse
In addition, wanted to throw out that I've never had problems with the Silent Bug or 50% Time Without Signal. However, my phone does lag like everyone else (even though I'm using SMS Cleanup, Not Call Log, Call Log Trimmer, etc.).
Didn't realize 1.46 was rare . . . my girl's asleep but tomorrow I'll ask to borrow her digital cam and I'll toss up a video of my Power On + Vol Down to YouTube to confirm.
For those interested, I got my phone mid-January at the Verizon Wireless at 342 Madison Avenue in New York City.

Original phones shipped with 1.46. The 1.47 bootloader was in the RUU for the maintenance release that followed. So in theory, any phone that left the factory before the first maintenance release had 1.46 on it, and most phones after that had 1.47.

thenestor said:
Original phones shipped with 1.46. The 1.47 bootloader was in the RUU for the maintenance release that followed. So in theory, any phone that left the factory before the first maintenance release had 1.46 on it, and most phones after that had 1.47.
Click to expand...
Click to collapse
That would make sense because the first day I had my phone, I got an OTA Update that came a few hours after my initial setup. It's my understanding that Verizon OTA's do not alter your bootloader and I'm assuming my first OTA was that MR.
Anyone think that I should replace 1.46 with the Engineering version? It doesn't seem like there's any benefit.

I had 1.46 too. I was able too root just fine using the "From stock 1.5 to rooted 2.1" walk-through in the sticky. I did run into a hiccup while installing the recovery image though. I just had to install it with a fastboot command instead.

[poll] got hardware ver 0003? Got root?

I recently upgraded to the Evo from the Hero. Over the last few days, it seems like a trend has been developing. Folks with hw version 0003 and sw per 3.39 have had a very hard time gaining root. Vote in my pole and tell me how it went for you. If you HAVE had success, let us know what worked for you. Again, this pole is for folks w/ hardware version 0003 who purchased the phone with 3.30 installed, and hboot 2.02 s-on

Those of you that managed to get rooted and flashing, what method did you use??

I followed this guide. Make sure you have adb working and you have the files in the right folders.
http://forum.xda-developers.com/showthread.php?t=829045

tejasrichard said:
Those of you that managed to get rooted and flashing, what method did you use??
Click to expand...
Click to collapse
twin001 said:
I followed this guide. Make sure you have adb working and you have the files in the right folders.
http://forum.xda-developers.com/showthread.php?t=829045
Click to expand...
Click to collapse
pins and needles man.. did you get it rooted?

Followed same guide, I have hardware 0003, got it done. Rooted. Unrevoked forever
Sent from my PC36100 using Tapatalk

ver 003 also. rooted with warm 2.2 rls3 with netarchy
used unrevoked in the rooting for dummies thread at androidforums
Sent from my PC36100 using XDA App

nebenezer said:
pins and needles man.. did you get it rooted?
Click to expand...
Click to collapse
Not yet. It goes great up to the point where I flash PC36IMG.zip, but when that is flashing, it throws an error during the radio v2 update (fail-pu) and instead of skipping bootloader, like it says in the guide, it tries to update and throws an error there, too (fail-ic). After this, it finishes the flash. I can get to recovery, I can even flash a custom recovery, but when I try to boot, it just hangs at the white HTC splash. To get it to boot, I hafta run the ruu. S-off sticks, so unrevoked is working, but I don't have root, and I can't flash custom roms. I have checked my md5sum, adb communicates correctly. Something about the pc36img file just doesn't work with my phone. I will say, the pc36img in Dan's thread doesn't throw the errors, but I still couldn't boot afterwards. Think I'm gonna step away from rooting for a day or two and just enjoy my new phone. I'll come back at this when I'm fresh, not so frustrated.

I can confirm tejasrichard's findings. Used the same method above. It threw me the radio error when flashing PC36IMG.zip. adb could not perform the rename in step 15 after this, but did accept the recovery command. Step 16 worked (no step 17), but in Step 18, the recovery failed and froze on the white HTC splash. Manually put the Amon RA and radio updates onto the SD card and flashed that sucesfully, but still froze on the HTC Splash. Had to flash back into 3.30 ruu.
I did go back and try unrevoked3 and the process said it completed, however hboot gave an error on the last step when going into the clockwork recovery and looking for the unrevoked-forever.zip files. I did reboot it and it completed a boot into something similar to 3.30 ruu with a different background. Superuser app is present.
Confirmed no root, but still have S-OFF.
4-day old phone
Hardware: 003
Android version: 2.2
Baseband version: 2.15.00.09.01
Kernel version: 2.6.32.15-g0f673ed / [email protected]#10
Build number: 3.30.651.2 CL271968 release-keys
Software number: 3.30.651.2
PRI version: 1.77_003

I voted without reading this part. "purchased the phone with 3.30 installed"
I have 003, and am a flashaholic. But I purchased mine two days after launch.

Similar experience
Adding to the thread here. Pretty new to all this. I banged my head against the wall for hours rooting my new EVO bought just a couple days ago. (hw version 003)
Managed to get S-off using Method 3 (which I think has been edited to be the only method as it's been the most reliable) from the thread...
'[TOOL][GUIDE] HBoot 2.02 S-OFF'
Once I had S-OFF I thought I was golden. However, I could not flash any roms through recovery. Tried Fresh, Myn, Ava...kept getting errors. Always, it was back to RUU. The only thing that has worked for me thus far was using the 'Sprint Lovers' rom at this thread:
'[ROM] 11/07/10 | SPRINT LOVERS | 2.2 | 3.30.651.2 | Radio/Wimax/PRI All-In-One'
Not sure what's different about this Rom but it loads as a PC36IMG.zip file from Bootloader and not through recovery. I'm then able to boot the phone normally. Superuser, Wifi hotspot, swype, 4g, camera works fine...nice. It's basically stock Sense with rooted goodness. I actually love it and have tweaked the phone beautifully.
HOWEVER, I'm almost certain that i'm not fully rooted. (Maybe partially Nand unlocked) I have no idea. I've had to reload the ROM 3 times because I decided to go into recovery for one reason or another and gotten stuck in boot loop hell always going back to recovery. ARG!! Not sure the reason for that. I tried so many things early on that I cannot account for everything. I'm just going to roll with this ROM for now until the dust settles.
I'm following this thread closely:
'[GUIDE] HBoot 2.02 S-OFF'
Supposed to downgrade your HBoot which I think may be the whole problem. We'll see. I don't have the energy to start from scratch again. I'm actually quite happy with Sprint Lovers.

Thanks for the info! I'll try that ROM soon as I can and see if it works for me.

[Q] New Evo complaints...

So just decided to get an evo. My wife has had hers since release day. This one Has the 2.20 and the 3.30.651.2 Build. The quality of the screen is horrible compared to hers (the color and brightness). Before even being able to root it I couldnt use QIK because it reboots the phone. Downloaded the latest one and I can open the software and its after my camera kicks on that it reboots now....
So i rooted it and got the s-off. Now I can take nand backups but its says they are corrupt. Cant flash a rom because it will hang on the Evo boot screen or it will drop to a boot loader loop with the HTC with 4 exclamations....
Is anyone else seeing this or is this guy flat out a lemon?
I have looked around the forums a little and found people having a hard time rooting and s-off which was easy after skimming the forums for a while. Thanks ahead of time for any input in this.

The screen problems im not sure how to fix
there is a new ota to fix your camera issues, yours is most likely the new hardware/camera 004 model.
for rooting the only method that works is toast's, unrevoked wont. Unless im behind on info. Have you tried toast's method?

Unrevoked works fine. Took me about five minutes to root useing that method when I got my replacement phone.
As far as your phone issues, take it back to the store and show them the problems. Get a replacement.

Oracle, go to your bootloader. What is the first line? Is it Supersonic EVT2-3 S-off? If so, I had the same problem. You have bad blocks. My recommendation is the that you flash sprintlovers ROM. It cones as a pc36img.zip, and you flash it through bootloader. I tried every method of rooting and none of them would let me flash through recovery.... I always either got errors while flashing or, even if it seemed to flash fine, it would never boot. Also, Sprintlovers will get your pri corrected. If this works for you, give me a shout, and I have an idea we can try.

RUU Cannot Find Bootloader

Goodmorning,
I did a good few searches and could not find an answer to my delima. I am pretty informed about rooting and flashing ROMs. What happened was I already had a phone rooted and mikroms 4.61 but needed to exchange it due to a bad camera. I recieved my new evo 4g (hardware v4...hboot 2.10) and rooted it with unrevoked. Everything went will and was rooted within minutes. I then went to downgrade the hboot (this is where the problem began). I followed the same instructions I did with my previous evo (I believe it was hardware v3) and did the update, did not reboot, installed the .zip file. I then went and wiped everything (Full Wipe). Dalvik and Cahche as well. I then went to install mikfroyo and everything seemed ok. I them went and rebooted and now I am stuck on the bootloader. The hboot is still 2.10 but it has s-off. I tried a RUU, the RUU finds the evo and reboots the phone. Then the RUU cannot get to the bootloader. It stays waiting for a good minute but can't seem to find the bootloader even though the phone is on the bootloader. All drivers are installed properly as I checked the Device Manager and no question marks come up. Any ideas would be fully appreciated. Thank you.
By the way...I cannot get into Recovery either. When I choose that option it just heads right back to the Bootloader screen.

Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?

HipKat said:
Why would you downgrade the hboot?
I know people have dome this to try and solve issues with their phone not booting at all, but to just do it?? Why?
Click to expand...
Click to collapse
For some reason I thought the evo would just function better with the previous hboot, doing nandroids and flashing ROMs. If I didn't need to do it I would not have even looked that way. Guess I am not as experienced as I thought. I just did that because it worked well with my previous evo. I hope I don't have to go to sprint and replace it again for my ignorance. There's other phones that have true issues that deserve to be exchanged next to mine.

Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes

snandlal said:
Your phone is bricked. Try fastboot devices, if you get 123456789012....your screwed. You now have bad blocks and partition info is mixed up. Sorry.
Your new phone has newer block sizes
Click to expand...
Click to collapse
That stinks. Well, I will go in ahead and have it sent in through Best Buy. Thanks a bunch, friend. Godbless