Related
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
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
JW 301 said:
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
Click to expand...
Click to collapse
You'll need to use this guide (http://villainrom.co.uk/viewtopic.php?f=46&t=375) to make a goldcard, and downgrade using the HEROIMG.zip method (google it)
it doesn't work... I took the rom.zip, renamed it HEROIMG.zip and put it on my sdcard.
hboot finds it, loads it and then says "Main Version is older! Update Fail! Do you want to reboot device?"
what can I do now?
Have you checked to see if your goldcard has definitely worked?
it definitively is a goldcard, as I used it to install generic ROM on T-Mob device... still doesn't work now... but the problem is not that I try to install a ROM that's not meant for my device (thats what I understood goldcard does), but the problem seems to bee the bootloader-version the 2.1 RUU brought.
what can I do now?
Same thing happened t me a while back, I just re-tried every step from scratch and it worked the third time...!
what exactly did you do then? I tried so many things, at least I want to know, which steps to repeat over and over again
Just going to have a look at it for you, I am going through the processes as we speak so if I find a solution I will post back.
@JW 301 post the info in settings > About Phone
- Model number
- Firmware version
- Baseband version
- Kernel version
- Build numbr
- Software version
- Model number: HTC Hero
- Firmware version: 2.1-update1
- Baseband version 63.18.55.06PU_6.35.15.11
- Kernel version: 2.6.29-063c4d24 [email protected] #1
- Build number: 3.32.405.1 CL191507 release-keys
- Software version: 3.32.405.1
I want to get back to 2.73.111.26 (that is a T-Mobile ROM) so I can apply official T-Mobile OTA updates (by the way, I managed to get to VillainROM 12.0 yesterday, but went back. I want to use official ROMs...)
See new post here;
http://forum.xda-developers.com/showthread.php?p=7600524#post7600524
Had the same problem, I mean, EXACTLY the same.
This is what sorted it for me:
http://forum.xda-developers.com/showthread.php?t=726118
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.
Hi All,
I have recieved a Streak (Unlocked from Tesco) came with 2.1 Android. I cant' remember the full baseband but it did end with 00-EU. I tried to update but said none available,so I dowloaded the 309..pkg 2.2 update and used that.
I sucessfully installed OS 2.2, installed all my apps. Z4Root - this allowed me to install Titanium and root explorer (and run them)
BUT I switched the phone off and when I switched on again, I am now stuck in the Dell boot loop. Trying to repeat the pkg update doesn't make any difference nor does the factory reset??
I take it that I have got to revert back to 2.1? It seems that I will have to fastboot recovery (Stock recovery (build 4399) then load onto the SD update.pkg Build 8023 (intended for O2 devices, can be applied to generic UK devices)
Is this correct or is there something else I need to do??
Many Thanks in advance
John
Update, did the fastboot recovery image, rebooted phone now back to Froyo 2.2 and working correctly?? z4root works and I can reboot. I don't know what I did but all OK now?
Just wanted to let people know how I rooted my EVO in case it can help others. Unrevoked 3.22 would not root my phone after I did an Ota update, and I was not confident enough in myself to not brick my phone using other methods. I have almost no computer skills, and this sequence worked for me. My specs looked the following.
Android Version 2.2
Baseband Version 2.15.00
Kernal Version 2.6.32.15-ge2f608
Build number 3.29.651.5
Software number 3.29.651.5
PRI version 1.77_003
Hardware version 0002
HBoot 0.97
Radio 2.15.00
I first put the app ROM Manager on my phone from the Market. I then put the app z4root on on my phone. z4root can provide a temporary root on the EVO. The I used ROM Manager to Flash ClockworkMod Recovery. I then used ROM Manager to Backup Current ROM. Next I put unrevoked forever on my SD card and flashed unrevoked forever. Unrevoked forever turned the S-off. I then rebooted and ran z4root to permanently root. My phone is now rooted and I have not had any problems.
cool
will try on my friends new evo
I followed all these steps and although the temp root works, confirmed by running Cachecleaner, when I try to boot into recovery to flash Unrevoked Forever I just get the phone with the red exclamation point instead of the actual recovery menu. I really wanted this to work because I do have the software fully up to date.
ins0dus said:
will try on my friends new evo
Click to expand...
Click to collapse
How brave of you