Database Users

T-Mo Wing RUU for USA!!

Here it is guys.
http://www.mediafire.com/?2nq9iu0a2nt
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.

xavier6303 said:
Here it is guys.
http://www.mediafire.com/?21rtyxwyuyj
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.
Click to expand...
Click to collapse
thanks mate... but unable to extract the file...

NNagendran said:
thanks mate... but unable to extract the file...
Click to expand...
Click to collapse
Try redownloading. It extracted fine for me.
xavier6303 said:
Here it is guys.
http://www.mediafire.com/?21rtyxwyuyj
To enter the wing into boot loader, turn the phone off. Turn the phone back on while holding the camera button AND the voice button.
Click to expand...
Click to collapse
What's the OS version on this? Anybody know?

tried redownloading a couple of times and still got an "unexpected end of archive" error when using WinRAR.
Can you repost the file somewhere else, please?

worked on my phone should work on yours

lucabraz23 said:
worked on my phone should work on yours
Click to expand...
Click to collapse
Do you have a wing, or an unbranded 4350? Also, can you do me a favor and check settings>about and give the version number on the OS?

delete delete

doesnt work for me i have an unbranded herald
i get error224 invalid model number

imawinnerbaby said:
doesnt work for me i have an unbranded herald
i get error224 invalid model number
Click to expand...
Click to collapse
The main benefit of this ATM is now wing users have the ability to flash from the bootloader.

will this rom get rid of the crazy memory leak?

Tried updating the ROM twice then checked under the device info:
ROM version still says: "4.10.531.2 WWE"
ROM date: 03/15/07
Radio Version: 02.83.90
Protocol version: 4.1.13.37
The ROM update utility says that the image is Version: "4.10.531.3" anyone know why this one was not loaded?

Guys, I know there are alot of questions pertaining to this RUU but it is the T-Mobile OEM Rom that comes on every T-Mobile Wing. This just helps if you brick it; you will be able to recover from a brick in most cases. I had a problem with my usb connection on my device after I reflashed it. For some reason I was getting "usb not found" errors. I cleared storage and it works fine now.

(post deleted)
(Apparently Mediafire doesn't like Firefox for some reason, but got the file downloading in IE.)

i'll try it
I've been after this file since about mid July and noone seems to have it. As a matter of fact, it seems like people have been waiting for this to release to show up. I've looked all over for this file. I'll give it a try tonight on my bricked Wing. I just don't know how you have this file and everyone else is scrambling for it.

transportguy said:
Tried updating the ROM twice then checked under the device info:
ROM version still says: "4.10.531.2 WWE"
ROM date: 03/15/07
Radio Version: 02.83.90
Protocol version: 4.1.13.37
The ROM update utility says that the image is Version: "4.10.531.3" anyone know why this one was not loaded?
Click to expand...
Click to collapse
transportguy,
My stock T-Mobile Wing reports it's ROM version as 4.10.531.3 WWE.

Okay, so apparently the Wing is supposed to reboot itself at around 1% and 30% in the update process. I thought the reboot was the RUU failing, so I disconnected my Wing and got a connection error message. Whoops. In other words, keep your Wing plugged in during the update process even if it reboots.
Just figured I'd post that in case anyone else runs into the same "problem" I did.

I have 2 Wings.
My bricked wing is 4.10.531.3 WWE
My unmodified, pristine Wing is 4.10.531.2 WWE
I've been waiting for this so that I can unbrick my 1st Wing and I can use that one as a testbed for ROMS, etc. I'm not sure if it'll work on my newer (x.2) Wing, but since there's no reason to try, I doubt I'm going to
Thank you for making this available to us!
EDIT:
Ok, so I decided to try, and it looks like the update is going to happen. This allowed me to upgrade 4.10.531.2 WWE to 4.10.531.3 WWE.

Is there a Dutch wing official ROM available?

applecarriage said:
transportguy,
My stock T-Mobile Wing reports it's ROM version as 4.10.531.3 WWE.
Click to expand...
Click to collapse
Thanks Applecarriage, after the second time I flashed the ROM it showed 3. I guess the first flash didnt take.

Has anyone noticed any difference from 4.10.531.2 WWE to 4.10.531.3 WWE ? I am wondering if its worth upgrading too.

ONLY - Technical Support - ONLY

Disclaimer: As in every case your choice to flash any memory on your phone is YOUR decision and you run the risk of making a expensive Paperweight. Research Flashing and read post about new Rom's or Builds to learn from others mistakes.. There are a lot of risk takers here on XDA that will be glad to bite the bullet to help the community with rom stability and issues. But ultimately you CHOOSE to flash your phone Not us.
I created this thread for new users unfamiliar with Flashing and modding their phone to get technical Support for any technical Issue that comes up regarding the phone. However Please Avoid Posting things such as "I am bricked how do I fix" or "Help my phone doesn't Start up" Because they will not allow the more experienced users to Help you.
Suggestions:
1. List the following in the reply
- What Model Is your Phone (Should Be HTC Dream AKA Tmobile G1)
- What SPL are you using (Boot Holding Power + Camera then first line)
- What Recovery Image are you using(Stock, Jesus Freakes 1.42, 1.43 or HK)
- What Rom is Currently Loaded (Booted up go to Settings-> About Phone)
- What Radio do you have currently (Settings -> About Phone)
2. What are you Trying to do (Ultimate Goal)
3. What steps has you taken (In Detail please)
4. Once you problem has been resolved please Edit your Original Post indicating that it was resolved.
Thanks In advance for Keeping this thread Neat.
Some Reading Material for you:
APN Info Thread
General Questions Thread
G1 Wiki Thread
G1 Tips and Tricks Thread

jf recovery 1.43
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.

build..?
I did my first fastboot recovery, even though I didn't need to. Pretty decent operation. Just wanted to get the feel of it. I think I'll be using nandroid and fastboot a whole lot in the near future
Goal: To either build myself, or at least play a part in the building of one sweetest ROM's. I guess i'll start small, with a theme.
(it's been a 12 pack of Mountain Dew and B movies kinda night.)

CC CEO said:
doesnt seem like i need it because ive flashed beta 3 using 1.42 but i want it cause it has to have some capability that 1.42 doesnt right? Only problem is I have no idea how to flash it. I tried renaming the 1 in "haykuros hero rom" post to update.zip and it still said 1.42 when i went back 2 recovery. I dont use fastboot or adb or anything because I am a capital "N" noob and nothing seems to ever say how to do any of this stuff using a mac so.... that being said...can you help?
1. tmobile g1
2. haykuros latest spl
3. 1.42
4. ion
5. latest radio
goal: 1.43 recovery
steps taken: saw a lot of people ask the same question. searched. went back to the rooting thread attempted to enter the commands by pressing alt+x in the recovery console the way they were listed and placed the recovery.img file i unzipped from the hero thread on my sdcard. no luck.
Click to expand...
Click to collapse
Installing JF Recovery 1.43 is just like any flash update for a rom...
You find and download the recovery file. Rename it to update.zip (Keep in mind that windows by default hides the.zip part so if you rename it to update.zip windows actually sees it as update.zip.zip.. This is a common problem.
Then Boot to SPL by powering off your phone and powering up with Home + Power Key.
Once loaded then hit Alt + L (If you don't have a modded Recovery already) and then If you have to wipe(which I usually do) Alt-W then you need to load the new firmware with Alt + S.
If all goes well it will load the new recover image and will reboot back into Recovery mode in which you just Home + Back to Exit and reboot.

I don't wanna step on anyones toes but I believe to load the new image after wipe it'll be alt + s....

Hero beta's
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?

mvanwyk83 said:
I've triend to install both Beta 2 & Beta 3 of the Hero build, but evertime it got to the setup screen it would force close. What can I do to get past this problem?
Click to expand...
Click to collapse
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.

Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem.
tia

Curunir said:
Just a quick question:
I'm currently running
the Android 1.5r2 based Cyanogen build v3.3.1
1.43 recovery img
Hardspl
The latest radio update (the one with the I as the last character)
I would like to update to Haykuro's new bootloader to get more space and to be ready for the upcoming haykuro build, but I'm a bit scared by all the reports of phones getting bricked.
So my question is, if I install it using the update.zip on sd-card method, is there any chance of a brick?
Let me point out that I don't have a microsd card reader available, so I wont be able to flash the build I'm currently using right after updating the SPL. So far it's not entirely clear to me whether this can be a problem. Tia
Click to expand...
Click to collapse
Before you consider flashing the new spl. Make sure you have a pvt revision board. Power + camera when turning on your phone. It will be at the top. If it says dvt don't flash.
You also need the 26I radio firmware.
If you do not have a memory card reader or a second memory card ten do not flash the new spl. Once you flash the spl, your phone will not boot until you flash a new Rom onto it
I believe this is correct. Anyone with experience care to confirm?

Actually now that I am rested and thinking straight.. Don't you load a recovery image by loading the recovery.img file on your sd card and booting to Bootloader?
Man I was sick and tired last night =)
Go to My Hero Thread and in the first post is the JF 1.43 Zip file you can use to Flash to JF 1.43 in update.zip format.

ubernicholi said:
With the beta 3 update update on your sdcard boot into recovery and wipe then flash then wipe again then reboot.
If you have a2sd already Use the adb recount Command and then adb shell to delete the system/sd/ folder.
Click to expand...
Click to collapse
Now is that process the same for Beta 4??

,
mvanwyk83 said:
Now is that process the same for Beta 4??
Click to expand...
Click to collapse
Should be. Can anyone confirm?

I put some music on beta 4. The album cover is in my pics but doesnt show where it should when playing music, do i need to somehow manually put it there?
Am I asking this in the right place even? thanks

1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)

cronin4392 said:
1.
Tmobile G1
SPL: DREA100 PVT 32B
Firmware version: 1.5
Baseband Version: 62.50S.20.17H_2.22.19.26I
Kernel Version: 2.627-00392-g8312baf [email protected]
Build Number: dream_devphone-userdebug 1.5 CRB21147201 test-keys
2. Upgrade to the Dudes Build (http://forum.xda-developers.com/showthread.php?t=507151) and backing up all my data and apps
3. Tried to update (by naming his build update.zip and updating) and also tried backing up data using the commands in his post (listed above)
Click to expand...
Click to collapse
What errors did you get or what problems are you having?

stuck on android screen
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated

rschuman90 said:
hey guys, this morning i got the OTA cupcake update, and my phones been running fine all day, however, i just restarted it and its stuck on the android logo screen, it shows the shine going through the logo like it is loading but after a few seconds it stops, then does it again, is my phone shot? please, any help will be greatly appreciated
Click to expand...
Click to collapse
Wipe your phone. Press and hold home+power. Continue to hold it till youe see a caution triangle. Press alt+l and then alt+w when its done select reboot from the top of the list. Good luck

Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.

Mast3rmatt said:
Quick Question
I am running the newest of everything, currently on Hero BUild 4
What actions should be taken to downgrade to the older SPL. I am getting extremely bad battery with this and can't handle it.
Click to expand...
Click to collapse
From what I know, its a bad idea to downgrade your spl. Check you screen brightness and your screen time out if you are running an overclock program, try setting it to 384 max 128 min. Double check to make sure your screen actually times out. See if your wifi is running, as well as your gps. If you use twidroid change the rate from 5 minutes to 1 hour

i have to wipe my entire phone and loose everything now!!?

BIG PROBLEM - my g1 isn't a phone anymore...

hi folks,
i got a really big problem: yesterday my SD card/partitions went corrupted. That wasn't really a big thing, i don't have any importend data on my sd. But all my programms (which where installed on the ext3 partition on the sd card) continued to work, so i thought it was just the fat32 partition which where damaged.
So, at the evening, i dropped my g1 from my desk. the sd card went out, and the g1 was stuck. no reaction to any touch input or keypress or something. so i took the battery out, restarted it and see that all apps where gone, and i don't get a signal strength any more. when i go to settings->wireless settings->mobile networks it instantly force closes...
i tried to wiped it a couple of times, but with the same result - the system works but without any phone services. it force closes when i trie to call a number or go to the settings and so on.
does this looks like a hardware issue or software issue? i don't know what to do next...
i am running CM build 4.2.3 with 1.4 recovery console.

Sounds like a hardware issue
Try a different ROM perhaps, but I doubt that'll help...
Do you have the latest radio and SPL?

Go back to stock RC29 by flashing the DREAIMG.nbh file to ensure it is not the software.

Deathwish238 said:
Sounds like a hardware issue
Try a different ROM perhaps, but I doubt that'll help...
Do you have the latest radio and SPL?
Click to expand...
Click to collapse
I have never flashed a radio or SPL... I went from my (european) stock image to CM builds since 4.04...
I really hope its just a software issue; i can't imagine that the antenna or something broke because it just fell down from my desk (and that wasn't the first time)...
I will try to install the htc recovery image and reflash the latest CM build; hope this works...

stonedraider said:
I have never flashed a radio or SPL... I went from my (european) stock image to CM builds since 4.04...
I really hope its just a software issue; i can't imagine that the antenna or something broke because it just fell down from my desk (and that wasn't the first time)...
I will try to install the htc recovery image and reflash the latest CM build; hope this works...
Click to expand...
Click to collapse
Can you check your radio version? Settings > About > Baseband Version, should end it 26i.

When i go to settings -> about -> baseband it says "unknown"... So my baseband ( = Radio/SPL?) is broken!?
thank you for your help!
Should i try to reflash the htc recovery image + cm build (i think those two roms flash the radio/spl theirself?)?
EDIT:
Ok, i tried to reflash the htc 1.6 recovery image and the newest cm build -> it worked (it took about 15min to reboot after flashing the two roms - i really thought i have bricked it)!
Big thanks to adrianK and everyone else for guiding me the right direction!
So, my phone IS a phone again...

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

[Q] Help with rooting

Hi i wonder if anyone can help.
Ive been reading about rooting my wildfire.
I have tried the unrevoked tool and done all the correct things eg installed the usb drivers, had debugging enabled, havnt got sync installed but when i connect my phone unrevoked doesn't recognize it, it just says the same thing 'waiting for device'. I have read all the stuff about the froyo 2.2 but I don't think it affects me because my software version is.
Firmware version
2.1-update1
Baseband
13.45.55.24H_3.35.15.31
Kernel
2.6.29-6fb59e13
Build num
1.26.771.1 CL231296
Soft num
1.26.771.1
Brow ver
WebKit 3.1
So I don't know whats going wroung , the only thing I'm thinking is that its something to do with 'other devices ABD' which appears in my device manager when the phones plugged in?
Anyway can anyone help thanks??

mclozors said:
Hi i wonder if anyone can help.
Ive been reading about rooting my wildfire.
I have tried the unrevoked tool and done all the correct things eg installed the usb drivers, had debugging enabled, havnt got sync installed but when i connect my phone unrevoked doesn't recognize it, it just says the same thing 'waiting for device'. I have read all the stuff about the froyo 2.2 but I don't think it affects me because my software version is.
Firmware version
2.1-update1
Baseband
13.45.55.24H_3.35.15.31
Kernel
2.6.29-6fb59e13
Build num
1.26.771.1 CL231296
Soft num
1.26.771.1
Brow ver
WebKit 3.1
So I don't know whats going wroung , the only thing I'm thinking is that its something to do with 'other devices ABD' which appears in my device manager when the phones plugged in?
Anyway can anyone help thanks??
Click to expand...
Click to collapse
You don't seem to have the HBoot Drivers, install them and then install HTC Sync and uninstall it again. You should then have everything you need

oo ok thanks, the hboot are installed because i get android phone in my device manager and I followed the driver installation process. I will download htc sync now then and see how I get on.