Database Develop

k-jam, another brick in the wall (dead after rom update)

Hello folks,
Today I flashed with the ROM in thread 'T-Mobile USA 2.17 ROM (Custom)'. After it came up, I ran through the screen align and wizard. When it was all done installing extended rom etc it restarted on its own. After booting back up, everthing was really slow and there was no cell signal. The battery icon had an ! mark on it and when clicked, it says unknown battery. At this point everything keeps freezing and genrally not working including no activesync connection possible. I restarted into the bootloader and tried to flash again. It completed, but now I just get the tmobile boot screen, and eventually it restarts again, never completing the boot. This is when I notice that it doesnt seem to have a radio rom (GSM) version listed, but rather a gap where it should be. I ended up pulling the battery out and trying to get back into the boot loader again, and now I cant get it to power on in any way.
I guess that is enough said. The only other thing to note is that everything was working fine prior to the attempted update, I was merely hoping to get a performance boost, as I was using the original rom.
Any thoughts?
Thanks!
B. Ramsey

Fixed!
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.

No dice
After installing the 2.17 ROM, no more GSM, and same problems. I reflashed back to the previous and it works again..

Re: Fixed!
pterodyne said:
No other ROM would install, but in reading back through threads, I found a link to RUU_Prodigy_1081002_108_10910_TMO_US.exe. After installing this, I had my GSM rom back. Then everything worked. I think the not powering on issue had to do with the fact that it sat in the bootloader screen for several hours at one point. Since there was no standby, the battery was wasted. I am attempting to reflash it now to 2.17, we'll see.
Click to expand...
Click to collapse
THANK YOU SO MUCH for posting this! I also had a brick because of the same setup - trying to use the custom TMOBILE ROM. I had the same symptoms you did - basically non-responsive and no radio stack and no USB connection. I was not getting anywhere with any other ROM. Now, at least I have a working device.
Still no AKU2 though
Let me know if you manage to get an AKU2 ROM on your device!

That's worrisome. Do you know if the CID unlock was successful? (I think it's scripted into that custom upgrader)
If you're feeling adventurous, you could try intalling the custom 2.17 Cingular upgrader I made (it's on the FTP server). If that's successful, then the problem is with the T-MO upgrader. Based on all the folks having success with that T-MO upgrader though, I imagine the only issue might be a corrupt download. If the Cingular upgrader results in the same behavior, then the problem is either with the CID lock or some odd hardware problem.
I'm truly perplexed by the issue you're having..sure wish I knew how to help ya.

Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
My device is a QTEK 9100. I was upgrading from the ROM on my device when I got it:
ROM 1.1.7.5 9/22/2005
Radio: 01.01.10
Protocol: 4.0.13.16
ExtROM: 1.1.7.105
My carrier is TMobile, so I figured the TMobile custom rom that was built off of the latest QTEK would be a good bet for me - but instead I ended up with no Radio.
I have the IMATE ROM you refer to - maybe I'll try to go to that as an interim step to get to the QTEK ROM I really want, since you had success with that method.
What I don't understand is why the Vanilla QTEK 2.17 (which is what I tried after the TMO Custom 2.17) gave me problems. I don't recall the exact error message, but basically it said it couldn't use that ROM on my device.

pterodyne said:
Thanks for the replies. My phone was already unlocked as it was purchased that way. I actually did get custom 2.17 tmo Rom to work, I just hadnt posted here yet. After flashing to the older rom, I flashed to the 2.16 Rom on clubimate.com. Then I had a working 2.16 with GSM. I figured what the hey and went ahead and tried the custom 2.17 Rom again. All is great, and FAST. I wish I could remember what custom Rom I was using before I think it must be the culprit. I cant remember, but it did have the extended rom free and open, total commander, and an unlocker.
Thanks
Click to expand...
Click to collapse
When you say it was already unlocked, don't you mean SIM unlocked? It would be unusual to buy a phone that is already CID unlocked.

I bought the unbranded k-jam from Simoncells.com. All I did was put my tmobile sim card in it and it worked. I guess I dont know the difference between SIM and CID unlocking.

Well theb that's where you went wrong, sim unlock refers to ur phone being able to use any world sim card...cid unlock refers to country Identification...if ur fone is not cid unlocked then wen u install foreign roms it will bugg up ur fone...dats wat happened to u and that other fellow pterodyne...I sim and cid unlocked my fone. ran the tmo 2.17 custom rom without a problem....plz do ur research on upgrading roms b4 u bash them...most factory fones don't come cid unlocked so I'd b surprised if urs did (tho it prolly came sim unlocked)...

8125 ROM Upgrade Problems

I recently attempted to update the ROM in my Cingular 8125. The process stopped at 95% and I received an "Internal Error". Now, when I turn on the phone, it gets as far as the color RUU screen, and nothing else.
How can I find out if I can repair this situation myself or if I need to take it back to Cingular.

Hopefully you'll give Cingular a little more info regarding this than you gave us.
My psychic advisor is STILL on vacation so I can be of very little help to you, sorry!

What ROM were you running before and what ROM were you trying to flash it with? Did you CID unlock before you flashed?

Sorry - When I posted the 1st message, I was in a hurry...
I am not sure what ROM version was on the device before I attempted to update (I know, I should have paid attention, but I was not). The phone was new from Cingular and I had not done anything else to it besides load a couple of apps (Skype & Agile).
I attempted to run the file RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe that I downloaded from the HTC site. The update go to 95% and I received the error "ERROR [326]: INVALID COMMAND" - This NBF file cannot be used for your PDA Phone. Please check your NBF file." (I have attached a screenshot of the error to this post).
I am not sure what to do at this point.
Thanks,
Chris

Some folks at the Cingular forum are having the same issue with no solution offered.
I'd suggest putting the device into bootloader mode (Holding Record and Camera buttons while soft reseting) and then reflashing. Make sure not to launch any programs while flashing. I also don't touch the device at all as I've noticed the USB connection might slightly disconnect.
Good luck and let us know what happens.

I just tried reloading from the bootloader screen - no luck. Exact same error at 95%. Would it work to try to reload an original earlier ROM? If so, how would I go about trying that?
Chris

I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.

I had this same problem.....I went to the cingular site after having the problem. Before installing I stopped all applications then soft reset.
THen after it boots up install the file from cingular. It worked from their site. Not sure what changed but I am not having any problems now with the new ROM.

I have re-downloaded the ROM file from the Cingular site (actually it just redirects to the HTC site). Same problem. I cannot get to the point to even shut down any programs because the phone OS does not even load at this point. When I do a soft reset, I get the following (sorry for the blurry image - as you can see my good phone with the good camera is dead...)

I had a similar problem. I posted the fix on another thread and ppl said i was wrong, this wasnt it...but heres what worked for me.
Are you using a usb port on the front of the computer? if so, try pluggin into the ports on the back of your computer. I tried flashing the official rom from cingular a few times using front port and it stopped at the exact same % each time. got the same thing as you, colored bars.
Someone had mentioned to me that front usb ports don't work as well as back ones. give it a try. good luck

from the picture, it looks you have the G4 chip(u can see 2.25 0001)

Thanks to everyone for their input. From the suggestions above, I have tried various USB ports on my laptop and I always get to the same point. I have also called HTC tech support and they are pretty sure I have bricked my phone. I talked to Cingular and they have agreed to replace it. I have also researched the G4 chip issues (looked at the post: http://forum.xda-developers.com/viewtopic.php?t=56408).
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris

xtreme23 said:
from the picture, it looks you have the G4 chip(u can see 2.25 0001)
Click to expand...
Click to collapse
I second this observation! :shock:
This makes a major difference on wether or not you can even upgrade.
Search for G4 issues.
The .0001 in the IPS/SPL number will tell you which one you have.
The way I understand it is:
2.25 - G3
2.25.0001 - G4
I think this is the proper way to identify it.

slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Chris, LokiwizMSL ( http://forum.xda-developers.com/viewtopic.php?t=50768 ) can SIM Unlock your device. Be sure to read the instructions.

Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?

slapper said:
Well - Now I have a new problem. So far, Cingular is refusing to replace my phone - saying that the ROM upgrade voided the warantee. I am still fighting that, but just in case I loose, is there any way to get my phone fixed once it has been "bricked"?
Click to expand...
Click to collapse
If you installed an unofficial ROM then they are correct. You should never admit that you used a ROM that was not provided by HTC.
There are warnings all over this site about VOIDing your warranty.
Since you used the Official Update they are wrong.

Same problem with official Cingular 8125 ROM
I tried to flash the official Cingular ROM from the HTC site here:
http://www.htcamerica.net/docs/RUU_Wizard_225111_22511102_022511_CWS_WWE_Ship.exe
I got the same error at 95%:
"Error [326]: INVALID COMMAND This NBF file cannot be used for your PDA Phone. Please check your NBF file."
When I reset the phone I get the RGB bootloader screen and nothing else.
My phone is a G4 and was running ROM version 2.25.11.1 WWE before. The reason I tried to apply this ROM is because there was apparently no Extended ROM. None of the customization cabs executed on a hard reset. Also, in Device Information, there was no "ExtROM" listed.
This is the second phone that this has happened on. I thought the first time was just a fluke thing and I had a bad phone. But now I think there is an issue with this ROM.
Anyone have any idea what is going on here with this ROM? Does the fact that there was no Extended ROM have anything to do with this ROM not flashing properly?
Is there anything else to try or do I need to try to return the phone (AGAIN)?

how to fix the problem
read this thread carefully. The upgrade problem seems to be occuring on G4 chipped Wizards with the most current IPL/SPL.
http://forum.xda-developers.com/viewtopic.php?t=56088
take the official update. run it, when it finishes extracting look for the extracted NBF file in your
C:\Documents and Settings\yourusernamehere\Local Settings\Temp\the newest directory just made
find the NK.NBF file
extract it using the tutorial in the post above you will be flashing with the official cingular components sans IPL/SPL.
flash it and your are back up and running
I would have posted this earlier but i had to make sure it worked and was repeatable.
I think the problem with the new update is the new IPL/SPL version checking. It seems that if the patcher sees the same version already running it will give you that error at 95%. I've seen it on 3 phones already and I have been able to fix them by doing what i've told you above. You are already in bootloader mode and your phone is ready to accept a new rom anyways. My solution may not be the best for your phone and take no responsibilites but you are already desperate and need a fix. Good Luck!

Thanks for the reply, evilito. Since I hadn't gotten any replies for a few days, I decided to go ahead and try to exchange the phone at the Cingular store. They were baffled that this was the second phone I had returned for the exact same problem, but gave me a new phone anyway. I wish now that I had waited so that I could try evilito's solution to see if it works. As it is now, I am too scared to try any flashing on this new phone after my results with the first two. I would really hate to have to try to return a third phone
Can anyone else verify that there is a problem with the latest Cingular ROM when flashing a G4? Or did I really have two bad phones?

slapper said:
Now I have the following question - When I get my new phone (which I will assume will have the G4 chip as well), the Cingular rep told me that it will already have the latest 2.25.0001 ROM on it. What are my options at that point to SIM unlock my phone. Will I be able to? From the post I referenced above, it sounds like I may not be able to with the G4 chip.
Chris
Click to expand...
Click to collapse
Thats good to know, I thought that when we unlocked it and updated the ROM we lost Warentee Support. Where can you get the official Cingular 2.25 ROM. I am still on 2.17.

Big Time Panic!!! Help please!!

I am not sure what I have done. I have a cingular 8125 G4. Downloaded the Risidioro g4 rom upgrade and my phone was not probably CID unlocked. Thought that did not matter cause I was able to install Mr Clean ROM couple of months back. I read some users in the forum who successfully upgraded from Mr Clean.
Everything went nice and smooth, the upgrade completed 100% and when it finished and rebooted it stopped at the blue, red screen and got stuck there. I did soft reset, hard reset but every time that blue, red screen comes up and gets stuck.
Has my phone become a "nice but dead piece of furniture" ? Oh! man..that would devastating!
Please help!
BigMonty

All right, no response yet but it is only a hour since I posted but for me it seems eternity already. I did something further reading and got some hope. My phone might not be dead yet. Somebody said, if I can get to the bootloader mode, I still have some hope.
I did some trick on hard resetting found here
http://forum.xda-developers.com/showthread.php?t=268836&highlight=dead
but to no avail.
Any other idea?? Cry!! Cry!! Cry!!!

Got another guy who successfully got out of the jail by having a SD image. Do you think it would work for me too? If it works where can I find it? I already e-mailed the guy, seems like a nice guy, let's see if he replies.
http://forum.xda-developers.com/showthread.php?t=274471&highlight=dead

Do you see a USB connection if you connect it to Active sync, normally it is showing in the lower left or right corner, I'm not sure.
If so, you should be able to re-flash again, best would be to do this with your previous installed ROM.

Btw,
Spl 2.25.0001
Ipl 2.25.0001
Can somebody suggest what would be most suitable ROM to go for once I am in the bootloader screen?

Vilem said:
Do you see a USB connection if you connect it to Active sync, normally it is showing in the lower left or right corner, I'm not sure.
If so, you should be able to re-flash again, best would be to do this with your previous installed ROM.
Click to expand...
Click to collapse
Thanks a lot Vilem for your reply. Yes I see a USB connection..but I guess we can't get to activesync because the OS did not load yet. I had the Mr Clean ROM installed and I tried to go for it but failed. What should I do now? Go for the original shipped Cingular ROM?Anybody knows which version it was and where can I find it?

bigmonty said:
I see a USB connection..
Click to expand...
Click to collapse
Means connected, try it. Mine crashed a couple of times like that and managed to get it going again.

You mean I should run the Mr Clean update utility which is the last successful ROM update or the orginial Cingular shipped ROM?

bigmonty said:
You mean I should run the Mr Clean update utility which is the last successful ROM update or the orginial Cingular shipped ROM?
Click to expand...
Click to collapse
try the last succesful.

bigmonty said:
All right, no response yet but it is only a hour since I posted but for me it seems eternity already. I did something further reading and got some hope. My phone might not be dead yet. Somebody said, if I can get to the bootloader mode, I still have some hope.
I did some trick on hard resetting found here
http://forum.xda-developers.com/showthread.php?t=268836&highlight=dead
but to no avail.
Any other idea?? Cry!! Cry!! Cry!!!
Click to expand...
Click to collapse
Bigmonty - after getting into allsorts of issues after trying to upgrade my G4 to various 3.2 based ROMS, i also got to the bootloader screen with the USB indicator in the righthand corner.
This worked for me - take the battery out for an hour or so, put back in and soft reset. make sure you have a good charge. reboot the PC and plug in the device.
Now the only ROM i can recover a working device from isto use the latest ROM from the phone supplier. in my case from the club i-mate site (my device is SIM unlocked).
hope it helps

Thanks AirWol. I was able to go back to Mr Clean successfully, which was a great relief. What I was doing wrong was, I was using the wrong update utility of Mr Clean. I should have used the one which was modified according to Risidioro guide for use in g4 chips. But I was using the original Mr Clean instead.
BTW, anybody knows whether it is possible to update g4 phones to the latest Risidioro or Cingular 2.26 ROMS? That is, can I modify according to Rididioro guide for use in g4? Anybody?
Probably I haven't learned enough lessons yet!

help quick! thinking of upgrading my radio rom!!

can anyone explain which one is the best one for 8125 g4 locked
and how im am to go about it thanks alot sorry for the noob question

Just depends on your operator, so you need to try yourself and find out which is the best one.

i have at&t and running on wm 5

Basically, like starkwong said, it's pretty much trial and error. You have to try out all of the different Radio ROMs to find out which one works best for you in your area. Nobody here can really tell you for sure which one will work the best for you, unless maybe they live just down the street from you or something.

i know that im just asking is it safe and not brick my phone because its not unlocked in anyway

Normally Radio ROM can be updated directly with the Update Software (RUU) regardless unlock state of CID.

OH NO!
I have a Cingular 8125 G3 unlocked and have TNT's Touchflo rom on it. I tried updating my radio using Faria's 2.69.11 updater, but now my phone won't work, usb won't work, and when I reboot, it reads the IPL/SPL is still 1.xx and the OS is 6.00.0.0 but there is NO GSM line at all! Seeing how I can't the usb to work, I can't flash it with the T-Mobile rom or anything, however I can transfer things onto the phone via IR. So is there something out there I can use to fix at least the usb so I can reflash my phone. Thanks in advance!

Got it!
Nevermind, I got it working. I was able to transfer the bootloader.exe file over to my phone, ran it, and then was able to reflash my phone. Whew, I was so scared. Anyhow, thanks for all the info on this page, I love this site!

Scared to post but I am stuck must take your wrath

Aloha everyone,
I have tried to not post for about 3 weeks but I just can't move forward. I have read and tried to follow everything on the site but I am just confused. I know this is a developers site and I am very intimiated to be castigated by you guys but...it's the internet so what the hell.
I have found numberous instruction threads pertaining to updating ROMS on the Wizard. It seems that up until recently there was only one way to do things but now there are many. As I try to answer questions I come into conflict over which way I shoudl be heading.
I currently have a working WIZ100 that boots with IPL 2.21.0001 SPL 2.21.0lip with GSM 2.25.11 and OS 2.25.11.1. I somehow got to this point, I think by following the instructions to get hardSPL on my device and booting on startup. I did not know if I next needed to find a ROM and if so then how to get that ROM activated on my device or what programs to do this with. I know that the threads spell it out but the threads pertain only to direct assumptions; the assumption that my head is not in my ass.
I wanted to attempt to put a new rom on here, for fun and to play around with something new. Perhaps increase reliability or to get WM6 going. I am stuck now though. Part of me wants to turn back and load the original ROM from the HTC site and the other part of me wants to try a new ROM as I already have this thing booting to the 0lip SPL.
Is anyone out there willing to help me either via this thread, personal message or IM?

Since you have already installed Hard SPL you should be safe to go ahead and pick virtually any ROM you choose on there. I don't have a lot of experience with Hard SPL yet, except for installing it on my kaiser, but the one thing I would guess that you should make sure that the ROM you want to flash doesn't have would be an IPL/SPL update included. As far as I know, I don't think any of the public ones that you find on here have them but make sure you read the chef of the ROM's entire post to make sure. And, if you magically happen to find my ROM somewhere, which you shouldn't since I only gave it to 2 people to try, don't flash it because mine does include an IPL/SPL update.

From my best understanding you have already loaded HardSPL and now are CID unlocked. If this is the case then I would recommend going forward and flashing a new rom to your device. Just go to the Wizard Mobile 6 thread and find one you like, and flash it.
Simple as that.

I appreciate your replies.
1) I am clarified like butter! What program do I download and use to flash the ROM to the Wiz, this has been a source of confusion for me.
2) If I download and install the HTC Cingular ROM from HTC, will that overwrite the HardSPL and return my phone to Factory Default, including the radio areas? In other words do I rid myself of 2.21.0lip?
Thanks for not beating my head in...very polite you devs are...

I like beating people's heads in, and you are far too polite, that I am actually having a very slight guilty twinge! Damn you. I have a G3 myself so I cannot help much, however, I found this sticky which may help.
http://forum.xda-developers.com/showthread.php?t=332320
I do know that once you choose your rom, you open the folder and run the item marked as ruu.
Now if you only had a G3, then I could fry you like the noob you are.
I suppose at some point, I should make a point of reading/learning about G4's. I know they are a far different animal from my G3.

That's the reason I said not to flash a ROM that contained an IPL/SPL upgrade since there is the possibility that it may overwrite Hard SPL, although I'm not positive of that, but better safe than sorry especially if it it's not an official ROM that carries the correct IPL/SPL format for a G4. If it doesn't contain the correct format for a G4 it could ruin your phone. If you flash an official ROM though and it overwrites it you can always just reinstall Hard SPL again and keep flashing. I hope this makes sense.
As for the files you need to flash a new ROM, they're usually included with the ROM. If they're not then just let me know and I'll upload them for you.

Good that you asked before damaging your (expensive) device...
Every Flash version comes with a RUU (Rom Update Utility) you just run that proggy and it does the rest.
To make it easier, look for a rom that states it's G4 safe (no IPL/SPL included), so you don't have to mess around with the inner files. If you want to, begin your tests with the TNT series, the latest build, stated in my sig is G4 safe, after that you'll be able to know the initial procedure.
Good Luck.

Thanks for the info.
Do I execute the ruu from Windows XP or from the SD card ont he device?
Why am I have a hard time searching for and finding TNT 5.2.1921 TouchFlo ROM?

The rom update utlity gives me an error when I try to update. Should I try to do all this from the sd card?

Well, I am plugging along. I rebooted after an error 300 came up on the rom utility. Any suggestions for me?

I found this thread, back in business, thanks for your help guys.
I guess my only unanswered question is...if I use the HTC ATT exe from htc.com will it kill the hardSPL and restore the computer back to normal?

If you have ROM on your desktop, Connect your phone to your computer via USB, open up Activesync, uncheck the check box in settings that allows USB connections. Make sure you have at least 50% battery, then put your phone into bootloader mode. (soft reset while holding down the camera button- keep holding the button for 5 sec.) a tri-color RGB screen should come up. This is boot loader mode. Then run the rom update utility program, and everything is automatic from there on. once it is done flashing the phone will restart itself.

Thresher said:
I found this thread, back in business, thanks for your help guys.
I guess my only unanswered question is...if I use the HTC ATT exe from htc.com will it kill the hardSPL and restore the computer back to normal?
Click to expand...
Click to collapse
Try it and find out. I'd kind of like to know the answer to that one too, although my phones a G3 and already CID unlocked anyway. You can always reinstall Hard SPL over again if it does.

So this worked out well for me overall. Installing HardSPL to my G4, and then using a correct bootloader with the right ROM (to review).
I am having one issue.
I have the OEM ROM, however the RUU gives me an error. Is there a documented way to restore the phone to an original status? Is it even necessary?
I ask due to problems since my upgrade to the TNT rom. I am noticing a lot of missed calls and people have complained. Is this an issue with the 8125 and the particular ROM?
I don't know what to ask, or how to search for this. Thanks for any input you can offer.
Otherwise the TNT rom is awesome. I do miss the voice dialing though. Thats another search.

Actually, that's usually an issue with your radio version. Try using either version 2.19 or farias 2.69 and see if that fixes your problem. You should be able to find both of them in the wiki and you may want to try both of them and see which one gives you the better reception because sometime one will work much better than the other for you depending on your location.
By the way, you don't have to be CID unlocked or have hardspl installed to update your radio so you shouldn't have an issue with the RUU giving you an error. If you do, let me know and I'll upload a different RUU for you to try.

xeno1 said:
Actually, that's usually an issue with your radio version. Try using either version 2.19 or farias 2.69 and see if that fixes your problem. You should be able to find both of them in the wiki and you may want to try both of them and see which one gives you the better reception because sometime one will work much better than the other for you depending on your location.
By the way, you don't have to be CID unlocked or have hardspl installed to update your radio so you shouldn't have an issue with the RUU giving you an error. If you do, let me know and I'll upload a different RUU for you to try.
Click to expand...
Click to collapse
So the Rom is broken up into major parts. Those parts must ineract with one another, so that would be why my radio version may be at cause?

Yep. The ROM can contain the IPL, SPL, OS, Splash Screens, GSM (the radio), and extended ROM, any of which can be changed or upgraded individually without affecting the other parts of the ROM (for all intents and purposes anyway). That means you can change your radio version without it deleting all of your settings or your installed apps in your OS, etc etc.
Since you still upgrade each individual part using a RUU that is able to update any of the parts you still get a warning when you run it that it will delete all of your files, but as long as the update that you're running doesn't include a new OS you can ignore those warnings.

I decided to back out of the entire upgrade and move back to WM5 Official Cingular HTC ROM. I am stoked that I now know the full process of taking a G4 through hardSPL, ROM updates and restoral.
I was too scared to try any radio updates or fixes. Maybe when I upgrade phones I will come back to playing with the 8125 but for now, I just need a good functioning phone for work.
Do these Cingular radio fix cabs apply to a standard phone or only to upgraded ones?