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

Seeking advice rooting MyTouch 1.2 (HTC Magic 32a)

Hello all, thank you for this great resource and any insight you can provide.
I need some of your wisdom, as I've been banging my head against a brick wall for about two weeks now, trying to root my T-Mobile MyTouch 1.2 (HTC Magic) with the 3.5" jack.
I did a couple hours of homework and began the process, but currently am stuck at the HTC Magic splash screen on normal boot up. I cannot boot into recovery; I have tried flashing both the Amon Ra versions, H and G. I can, however, boot into hboot and fastboot menu options, so it my understanding that my phone is salvageable with the right tools and process. Unfortunately, I was given bad advice—or incorrectly followed good advice—and now all the instructions I find to restore functionality to my phone don't go smoothly.
I've spent countless hours trying proposed found threads here (mostly) and other resources, but while the solutions sound like the apply to my hardware, they fail to complete successfully.
I have created two goldcards, both appear to work, as I have been able to flash a sappimg.zip image initially, but currently trying to flash again to remedy problems hangs and requires me to pull the battery. It usually hangs at the initial unzipping or at updating radio_v2. Via fastboot, I have been able to flash the stock hboot.nbo and reflash different versions. I was able to flash to the stock radio once, but have had problems trying to reflash images, trying to correct the issue.
These details have read different things at different stages in trying proposed solutions, but currently the info on fastboot menu reads:
SAPPHIRE UNKNOWN 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP31000)
CPLD-13
RADIO-6.35.10.18
At this moment, I've stopped trying to find answers on the forum because I've spent countless hours failing and more importantly, fear that if I continue applying incorrect solutions, I will irreversibly damage my phone. I hope that someone can provide some advice tailored to my situation.
Thank you for reading and for your reply. I understand that any advice I receive is at my own risk to follow.

Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Option two: flash the sappimg to revert back to stock then stsrt all over again
Option three: flash the stock sappimg and stay at stock thanking jesus you didnt **** anything up.
Sent from my HTC Magic using XDA App

You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.

NetrixTardis said:
You did not read the mytouch 1.2 rooting guide correctly. This phone can only run stock spl and radio. Read the guide at the unlockr. After using the goldcard you should have flashed stock spl and radio using fastboot.
Click to expand...
Click to collapse
I tried the files and process indicated on Unlockr several times. The files and process located here: theunlockr.com/2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/
Attempting again, just now, I run into the same roadblock as reported in my initial post: Immediately after clicking the action button to execute the update, the process hangs at 'Unzipping' on step [1] SYSTEM, where the progress bar never moves, and pulling the battery is the only thing that works (unfortunately, since I'm warned not to power off the device!).

knny1491 said:
Option one: flash the .nbo file for te engineerings 1.33.2010 spl and thz flash the g recovery.
Click to expand...
Click to collapse
Thank you so much for your response.
Attempting option 1, I get the following messaging in the terminal while trying to flash the hboot.img (not nb0, is this wrong?) downloaded from the 'Magic SPL HBOOT collection' thread located here: forum.xda-developers.com/showthread.php?t=529019
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
In the previous reply to another helpful commenter I describe another error I get while attempting to update the sappimg provided by Unlockr.
Further insight is very much appreciated.

so this is the second time I'm seeing this exact problem... this is keeping me from rooting this mytouch. but last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
but in the mean time you can try unrooting it until the problem is solved?
http://forum.xda-developers.com/showthread.php?t=665814

lbsk8addict said:
last time i saw this problem I believe it was solved.. i can't remember where i saw it though! I'll look and look until i find it then i'll post it here!
Click to expand...
Click to collapse
Thank you! I hope that you do.
lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
I've visited that thread before in my days of lurking, but didn't attempt it (I don't think—I've tried so many things, it's hard to remember fully at this point).
I think all I have right now are goldcards. I hope a stock SD card isn't needed, or I'll have to figure out how to restore a Kingston microSD or buy another.
Thanks again for all of your input.

lbsk8addict said:
but in the mean time you can try unrooting it until the problem is solved?
forum.xda-developers.com/showthread.php?t=665814
Click to expand...
Click to collapse
Follow up, attempting to update to MT3G 1.2 Sappimg (BUILD# 2.10.531.4) downloaded via that link, I encounter the second error documented in my initial post, the update process hangs at updating step [2] RADIO_V2. The red progress bar stops at about 95%. Pulling the battery out is the only way to escape.
I think, and this is just a gut-level guess, that my problem stems from a corrupt radio version. Any one have an opinion or advice about that?
After pulling the battery and booting back into fastboot, my versioning reads as follows:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO 6.35.10.18

You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that. What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Sent from my HTC Magic using XDA App

knny1491 said:
You have a 32a radio with a 32b spl, during the root process you are supposed to be able to revert that.
Click to expand...
Click to collapse
Thank you so much for the follow up. I wish the news were better!
How can you tell that I have a 32b SPL? By the errors I'm experiencing? The SAPP310000? Just guesses here. I don't see that on my phone so, I'm curious to learn.
knny1491 said:
What we need to do is get you onto an eng spl so you can fastboot erase radio, fastboot flash radio, then flash the correct hboot aka the stock one. Right now you cant fastboot or anything aka you are semi bricked. Only thing i can say is let it sit o the charger for as long as possible for the sappimg update and pray lots n lots.
Click to expand...
Click to collapse
Are you advising my to sit on my hands, keeping my phone charged, until, hopefully, the development community comes up with a new sappimg solution? Or are you saying to preform the 1.33.2010 engineering SPL update until success or my phone dies?

I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work. Quick question though did you try flashing te spl and radio BEFORE the recovery?
Sent from my HTC Magic using XDA App

knny1491 said:
I was stating to do the update where it freezes or hangs on the radio and let it sit for a crazy amount of time with praers, the spl version is defing by the numbers i the 1.33.0013 etc area, 32a users have 1.76.xxxx sp numbers while 32b users have 1.33.xxxx and after looking i see you are on the stouch 1.2 spl which is why fastbooting anything will not work.
Click to expand...
Click to collapse
Thank you for the reply. Good to know, as I was under the impression that all T-Mobile MyTouch 1.2 phones were 32A, and 1.33.0013 was the desired and appropriate version for 32A.
knny1491 said:
Quick question though did you try flashing te spl and radio BEFORE the recovery
Click to expand...
Click to collapse
I initially tried followed the procedure here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Fender/1.2
Where, I updated the SAPPIMG via goldcard, then through fastboot, I flashed the radio, hboot, and recovery. But, I wasn't able to boot to recovery after that process, for whatever reason, so I began trying other procedures from other sources, which in all likelihood took me further away from the solution instead of closer.
If the current attempt of updating radio_v2 until success or power battery dies (which has been hung for about 30 minutes so far) does not end successfully, should I try flashing a different hboot or radio? Or any other suggestions?
Thanks again for your continued help. I'm going to try to get some more attention to this thread to hopefully get more possible solutions.

If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Sent from my HTC Magic using XDA App

knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
Okay, thanks so much for the continued insight.
I think, I flashed the radio down to original, but encountered some problem, misdiagnosed it, and flashed it back up again. Now it's been about 3 weeks of messing with this phone for a couple hours a day, so, unfortunately, it's hard to remember all that I've tried. If what you're saying is true, then yes, I must have accidentally flashed the SPL before the radio. Is there a remedy for this? I've been pouring over this forum searching for "can't flash radio" (forum.xda-developers.com/search.php?searchid=39519193&pp=25&page=1) and so far I've read people claiming to have had successfully deleting their radios completely and reinstalling. Is this an option? Any other suggestions?
I will PayPal $30 to you, anyone who can give me a solution to where this phone is working and rooted. Alternatively, I live in Los Angeles, if anyone can recommend a good, knowledgeable, phone repair shop.

it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
3) let it reboot - should boot up to the "htc magic" logo -- for me it never loaded back up to stock 1.6, I had to pull the battery.
4) boot to fastboot using back + power
5) connect phone to PC and verified it was recognized using "fastboot devices"
6) make sure you have stock radio and spl in your Android SDK's \tools
7) performed the following:
fastboot flash radio radio.img (or whatever the filename you have for the stock radio)
fastboot flash hboot hboot.nb0 (or whatever the filename you have for the stock hboot)
fastboot flash recovery recovery.img (or whatever the filename you have for amon_ra or clockwork or cm recovery)
fastboot reboot-bootloader (to make sure that stock radio and SPL are loaded again)
8) reboot to recovery using home+power
*from this point on, you no longer need to use your goldcard
9) have new ROM .zip on root of your SD card, option flash from zip
10) ???
11) profit

NetrixTardis said:
it's really strange why that didn't work for you.
My steps were as follows:
**make sure phone is fully charged**
pre 1) create goldcard
1) place sappimg.zip on gold card
2) boot phone with goldcard to flash using Vold down + power
Click to expand...
Click to collapse
Thank you for your continued feedback!
I think you've listed the standard recipe for rooting this phone. I believe you. Unfortunately, something in my phone has gone askew (certainly my error) at this point and the "standard" just isn't working now. As is, and for the past 3 weeks, the process you describe dies at step 2. It hangs while updating RADIO_v2 (at whatever position in the list of updates it is for a given SAPPIMG file). Also, attempting to flash a stock radio.img via fastboot also hangs. Both updates send just fine, but hang at updating around 95%.
I've also been getting some advice from another member, knny1491. On this page, above, you'll see he hypothesises what my error is:
knny1491 said:
If the radio doesnt flash then we have to question why the recovery didnt load, the g version is the correct version given there is only one spl for us 1.2 users and it is a google spl. That is why you flash radio then spl then recovery in that order so nothing messes up. The thing is you have to flash a radio before spl, yet you hav the spl yet NOT THE RADIO which leaves me to believe you accidentalky did the spl first n not the radio first.
Click to expand...
Click to collapse
That sounds plausible that I did flash things in the wrong order. I'll accept that. I've been messing with it so much, I'm lucky it works at all. So now, and still, my question is where to go from here? Do you know anything about this radio/SPL relationship and how to remedy this current conflict, NetrixTardis?
Thanks again.

Possibly try to re download the sappimg from the mgic spl thread?

I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...

NetrixTardis said:
I was just thinking, if your goal at this point is to have the phone usable again regardless of root; why not try the RUU exe ? If i unserstand what it does, it should flash the phone back to stock (radio, spl, recovery,ROM etc). You'll have a phone as if you just unboxed it.
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
Thanks for the idea! I'll do some research on that. If anyone else can give any insight into if this may help restore my phone, please chime in!
I'd like root, but anything that gets the basic utility of the phone back would be great at this point (I've been using a old razr as a replacement while mine is hosed). I think an official 2.2 update is coming out from T-Mobile soon. I can wait for that.

NetrixTardis said:
Thats if i understand what the ROM Upgrade Utility (RUU) does correctly. Someone should be able to correct me...
Click to expand...
Click to collapse
If this is a good potential solution, could someone please direct me to which RUU to use? I've located the "[ROM] Official HTC Sapphire/Magic/MT3G RUU ROM Links" thread here: forum.xda-developers.com/showthread.php?t=659403
There really is a great abundance of options. I'm guessing I should go for the latest [MT3G 1.2] download which is:
36) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35
36) 2.10.531.4 1.33.0013G 2.22.23.02 N T-MOB010
I'll want a few hours or perhaps a day before attempting this process, in hopes that some helpful reader will provide his input if this is a good or bad thing to do as far as getting the phone working again.
Thanks!

[Q] Rogers Dream - am I bricked?

I have a Rogers Dream 32B. Radio 3.x (this is EBI1, correct?).
I was following the instructions on the CM wiki to root my phone and install CM 5. I can't link outside as a new user, but the article titles on CM wiki are "Full Update Guide - Rogers Dream 911 Patched" and "Upgrading From CM 4.2 or other rooted ROMS to 5.0.x(Dream/Sapphire)"
I used fastboot to install Amon_Ra's recovery, which is the first note. But after that I'm not exactly sure what I did to brick my phone.
Stalls at the Rogers splash screen. I can access the bootloader with the 3 androids on skateboards by holding down Camera + Power. I can also issue fastboot commands. I can also boot into recovery by holding down Home + Power. I haven't tried doing anything in recovery other than having it power off the phone, but I can see it says I have Amon_Ra's recovery version. I can't issue adb commands to the phone, which is step 4 in the tutorial - copying the ROM and google apps files to the SD card.
If I do a reset in recovery, will that help me at all? Or is there something else I can try?

plasticjar said:
I have a Rogers Dream 32B. Radio 3.x (this is EBI1, correct?).
I was following the instructions on the CM wiki to root my phone and install CM 5. I can't link outside as a new user, but the article titles on CM wiki are "Full Update Guide - Rogers Dream 911 Patched" and "Upgrading From CM 4.2 or other rooted ROMS to 5.0.x(Dream/Sapphire)"
I used fastboot to install Amon_Ra's recovery, which is the first note. But after that I'm not exactly sure what I did to brick my phone.
Stalls at the Rogers splash screen. I can access the bootloader with the 3 androids on skateboards by holding down Camera + Power. I can also issue fastboot commands. I can also boot into recovery by holding down Home + Power. I haven't tried doing anything in recovery other than having it power off the phone, but I can see it says I have Amon_Ra's recovery version. I can't issue adb commands to the phone, which is step 4 in the tutorial - copying the ROM and google apps files to the SD card.
If I do a reset in recovery, will that help me at all? Or is there something else I can try?
Click to expand...
Click to collapse
You're not bricked.
Couple of options:
1) Go into fastboot and flash a COMPATIBLE recovery.img. You installed an EBI0 recovery image, you need an EBI1.
2) Go into fastboot and flash an EBI0 radio (version starts with a "2").
I suggest option 2, since it will improve your compatibility with custom ROMs. It is also MUCH SAFER to have a 2.x radio since it is compatible with ALL SPLs ("1.x" and "3.x" are each only compatible with *some* SPLs.)

lbcoder said:
You're not bricked.
Couple of options:
1) Go into fastboot and flash a COMPATIBLE recovery.img. You installed an EBI0 recovery image, you need an EBI1.
2) Go into fastboot and flash an EBI0 radio (version starts with a "2").
I suggest option 2, since it will improve your compatibility with custom ROMs. It is also MUCH SAFER to have a 2.x radio since it is compatible with ALL SPLs ("1.x" and "3.x" are each only compatible with *some* SPLs.)
Click to expand...
Click to collapse
Thanks for your help lbcoder.
EDIT: Actually, I installed the correct recovery image! I have RA-dream-v1.7.0R, which is the one for EBI1.
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.

plasticjar said:
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.
Click to expand...
Click to collapse
I use the same combination, Rogers Dream on AT&T. Started off with the EBI1 kernel and 3.x radio, but after a while went to EBI0 and tried both current 2.x radios. I found no noticeable difference in reception or speed with any combination.

plasticjar said:
Thanks for your help lbcoder.
EDIT: Actually, I installed the correct recovery image! I have RA-dream-v1.7.0R, which is the one for EBI1.
If I downgrade to EBI0, will this affect my connection to UMTS 850/1900? I am using the Dream on ATT and got the Rogers version so I can use 3G in the USA.
Click to expand...
Click to collapse
No, it won't affect your radio frequencies.
Your phone is basically TWO COMPUTERS. One is the "radio" computer, the other is the "application" computer. Each of these runs their own operating system. You'll just be running your radio computer on an operating system that is *more compatible* with the typical ROMs that you might find for similar hardware.

"Main Version is older" fix

What is this thread about?
There is a known issue where some N1 phones cannot be flashed via the PASSIMG method because their boot loader says "Main version is older!" and stops.
Why is this a problem anyway?
If your bootloader is locked, you cannot flash the stock ROM easily.
If your bootloader is unlocked, you still cannot flash all partitions via fastboot. (A lot of partitions are protected for writing).
What is the "Main Version"?
The Main Version is a string value read and used by the bootloader. It's stored either in the boot loader image itself, or in the misc partition.
You can see your phone's Main Version by bringing it in fastboot mode and executing the following command:
Code:
$ fastboot getvar mainver
mainver: 2.18.1700.1
$
And what is older than what?
Every PASSIMG.ZIP file contains a android-info.txt file that dictates to the bootloader, among other things, the main version that this PASSIMG will bring the phone to. For example, for the commonly used FRG33 PASSIMG file, the main version is 2.16.1700.1. So, the main version on the PASSIMG file is older than the main version of the bootloader on the phone.
So, the phone will be downgraded with that PASSIMG, what's the problem?
Ask HTC or Google that question. I give up on trying to understand why they do not allow downgrading on a dev phone that can officially be unlocked.
Why does this affect only a batch of N1 and not all of them?
I can only speculate on this. It certainly means different production batches with different bootloaders.
This could be due to SLCD vs AMOLED, or an other production differentiation that was never made public by HTC.
So, we need a PASSIMG file stating version 2.18.1700.1 or later, right?
Yes, that's correct. It also is your lucky day, I have digged up such a file online after a week of searching (yes, it was that hard to find it) and I have mirrored it.
Here you go:
PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed.zip
Happy flashing

I'll try it out, the main version is updated for all refurbished HTC Nexus One's from starting a couple of months ago, and I can confirm it.has nothing to do with AMOLED vs SLCD.
Sent from my Nexus One using XDA App

georgemv said:
[snip]
So, we need a PASSIMG file stating version 2.18.1700.1 or later, right?
Yes, that's correct. It also is your lucky day, I have digged up such a file online after a week of searching (yes, it was that hard to find it) and I have mirrored it.
Here you go:
PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed.zip
Happy flashing
Click to expand...
Click to collapse
Awesome find!!!!!
Sent from my Nexus One using XDA Premium App

Excellent news!!!

Great! Downloading it now.

FYI, I just checked my "Main Version" and it is 2.16.1700.1, which I guess is why I have never had an issue with my device recognizing the leaked FRG33 shipped ROM.

UPDATE
Didn't work for me for some reason. It completely skips over everything, like there was no PASSIMG.zip on the card on the first place...
I have the aforementioned MainVer (checked via fastboot) and I renamed it PASSIMG.zip
Tried it twice, downloaded it from the phone and from my computer.

If your phone skipping past, then it's likely that it's not seeing the file. Most common reason for this is because the file is named incorrectly (i.e. PASSIMG.zip.zip - because Windows may not display on of the zip extensions).

I know how extensions work
Will try again tomorrow, maybe from Ubuntu or different laptop. I simply rename the downloaded file PASSIMG as it is a ZIP file.
Sent from my Nexus One using XDA App

Great! Works for me!!!

saratry said:
Great! Works for me!!!
Click to expand...
Click to collapse
Were you having the Main Version problem before?

A simple question!
After installing this ROM FRG83, can I install FRG33 with a previous HBoot without problems?
Maybe I will have the same problem (about main version) when I try to install 2.2 (2.16.1700.1) over FRG83 (2.18.1700.1). Is it posible?

Thanks!! Works for me!!!
I had this problem with FRG83D version and it has been fixed

EDIT: I love you, I can't believe it actually worked!!!!!!
I guess I was using a bad file manager, this time I downloaded it from my phone and CUT AND PASTED (not copied) using ES File explorer and I renamed it using the same software. Worked like a charm!!!!!!!!!
How did you get a hold of this??? I want to find a Gingerbread version of this for safekeeping

might need some help here.
I did everything as said (downloaded, renamed and so on) after the loading the check. occurs but i dont get a message where i am asked if i want to flash the device. it just skipps to the hboot menu again.
anyone some ideas?

Does main version have anything to do with hboot?
My mainver is 2.15, but I'm still on the old hboot. I want to flash the new hboot but not if it's going to also change my main version.
Anyone know?

J.L.C. said:
Does main version have anything to do with hboot?
My mainver is 2.15, but I'm still on the old hboot. I want to flash the new hboot but not if it's going to also change my main version.
Anyone know?
Click to expand...
Click to collapse
I don't know, but I can tell you that I flashed the latest HBOOT, and I still had the earlier main version. Besides, why are you worried about main version. It's been shown in this thread that the FRG83 shipped ROM works even on the newer main version. And you can't run stock Gingerbread on the older HBOOT...

i just ran
Code:
fastboot getvar mainver
on my phone and it shows:
Code:
1.01.1700.1
is this good or bad?
C

good info!

cchhat01 said:
i just ran
Code:
fastboot getvar mainver
on my phone and it shows:
Code:
1.01.1700.1
is this good or bad?
C
Click to expand...
Click to collapse
Doesn't matter. It means you have device with older version of OS initailly, and you didn't use PASSIMG of higher version at all. (If you updated your OS with OTA or manual upgrade only, or flashed custom ROM, main version will remain as its initial value)

radio downgrading ?

i tried to make a thread in the Q&A section but it has not been appearing.. twice!
my question -
currently on 5.08 radio and want to experiement/try out 5.12 radio
if i do not like it and want to go back to 5.08 can i simply just fastboot flash the 5.08 radio back?
or is there additional steps i must take to downgrade the radio?
if i am unable to downgrade back to 5.08 i dont think i want to flash 5.12 tbh....
thanks in advance!

You can flash whichever radio you want. There is no "upgrade" or "downgrade", the system doesn't check versions.

Funny you mention that. I went from 5.12 back to 5.08 a few days ago. I had a small issue with wifi not reconnecting, and had to disable/enable wifi to reconnect each time.
This is on MIUI GB. Radio 5.08 doesn't experience this issue for me.
Interesting to hear if you experience this too on 5.12
Sent from my Nexus One using XDA

WiFi has nothing to do with radio, so whatever it was that you did in addition to flashing radio - like rebooting - more likely cured your phone.

Flashing an unsigned radio will brick your phone RIGHT?
I had been flashing ROMs, Recoveries, HBOOTs but haven't tried Radios
I want to experiment just don't want to have a BRICK

soloviyko said:
Flashing an unsigned radio will brick your phone RIGHT?
I had been flashing ROMs, Recoveries, HBOOTs but haven't tried Radios
I want to experiment just don't want to have a BRICK
Click to expand...
Click to collapse
That's why it's best to use fastboot to flash the radio.

baseballfanz is correct
do it thru fastboot, if you are not familiar with fastboot, become familiar before you do it
nandroid
get the radio images from the wiki
i never saw any diff btw .08 and .12
put the radio.img in your adb/fastboot folder on pc, usually tools or platform-tools
fastboot flash radio radio.img where radio.img is exact name of the image file
i check this by right clicking the on the radio.img i put in the tools folder and clicking on properties. it will show you the exact name and i copy/paste it into command window

Jack_R1 said:
WiFi has nothing to do with radio, so whatever it was that you did in addition to flashing radio - like rebooting - more likely cured your phone.
Click to expand...
Click to collapse
I had already tried multiple reboots, fix permissions etc to no avail. It was only when I changed radio that wifi reconnect worked.
Sent from my Nexus One using XDA

Anyone else have an opinion on .08 versus .12?
rugmankc said:
i never saw any diff btw .08 and .12
Click to expand...
Click to collapse

CrustyMcLovin said:
Anyone else have an opinion on .08 versus .12?
Click to expand...
Click to collapse
No differences IMO. I was on 5.12 for a long time but went with 5.08 as that's the "official" radio version that came out with GB. Performance wise no different.