Ok so I trashed my ppc doing the radio update. Since I did the exact thing that Freshster did here is a cut and paste of my problem
" So, I tried running this TMO 4.00.10 upgrade in order to upgrade the radio stack to 6.24.00. While it was doing the radio stack upgrade, it failed at 13% complete. The error told me to "reset the device normally, wait for the radio stack to repair itself, reset the device again normally, then try to run the upgrade again."
After I did the normal reset that it told me to do, my screen got stuck on the ROM Kitchen boot screen and only showed a G, R, and 4.00.05 at the bottom corner, without showing a radio version or protocol version number. The led would not light up anymore. It did not flash green to show that it had signal, and it would not even show orange when it was connected to a charger. "
At this point Im SOL until tomorrow b/c I dont have a SD reader, my question is, can I upgrade the radio via the SD and hopefully get things going again? Or do I just attempt to reload a whole new rom and rsu via the SD card tomorrow. Thanks in advance for your help.
This is just a suggestion, I don't know if it will work.
1. Bootup in the Wallaby Boot Loader (hold power button while soft reset)
2. Press Calender button to bring up radio stack selections
3. Select turn off GSM
4. Reset and see if it will boot up when it doesn't have radio turned on
5. If it will, then set in active sync in guest mode
6. copy the RSUpgrade files to your window directory on the device using the explorer option in active sync
7. copy the two monitor files monitor_ul_bs.map and .m0 to the windows directory
8. reomove the device from the active sync
9. using the explorer on the device find the RSUpgrade executable in the windows directory and double click
10. this should start the radio upgrade going again
GOOD LUCK!
Thanks for the suggestion, I tried it but now luck. The pda stays stuck on the rom kitchen boot up screen. Thanks again.
OK, I had the exact same problem. You have to be patient, when you reset the device you'll get the R blank / G blank because the existing radio stack has now been trashed. eventually the PPC OS will boot. At this point reset again, wait for CE to boot & then reset again, The point is keep resetting the PPC every time you get the R Blank & G blank screen and wait for CE to boot. ON each reset the radio stack upgrade is working in the back ground. After 4 or 5 resets mine came up with R 6.24. at this point I connected the PPC back to Activesync & reran the upgrade & it went through just fine & installed the T-Mobile WM2003 ROM
Pdageek1 is right on the money! But I'll add one more step, remove your SIM card. HTH
I will try this on my way to work. I have another question, is the unit still charging when its on the base even though the charge light is not on? Thanks
I had same problem, if you flash with old t-mo rom it boots up everytime and will allow you to reflash radio stack.
http://www.t-mobile.com/pocketpcupgrade
hello pdageek and thanks for the suggestions. I have left my unit on at the splash screen with the blank g and r for about 5 2 minute sessions with no luck. Im hesitant to leave it on too long and have it eat up my battery. How long in total did it take your pda to boot up with the corrupt radio upgrade?
Sirseymore, the problem I have right now is that I cant even get it past the splash screen, since the OS is not booting up I cant see the unti via active sync.
You can't just it leave setting there with the blank screen you have to keep
doing the soft resets, until it boots!
Also to speed things up a bit during some of your soft resets try holding the volume control button, it similar to holding the hand of a sick person.
I know it sounds funny but hey what the hell, I did it! :wink:
One last note it also might help if you do a hard reset while holding the volume conrol buttom. I know that also sounds funny but hey I did that too! :wink:
HTH
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
bimmer10 said:
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
Click to expand...
Click to collapse
When you say Latest tmobile rom do you mean the 4.00.10 or the latest rom off of Tmobile's Website?
I got the same problem as you did blank g and r
Let me know Thanks, Allen
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
JoshB said:
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Reflect said:
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Click to expand...
Click to collapse
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
Click to expand...
Click to collapse
Well mine is working very good i havent came acoss any errors yet All i did was do the regular upgrade to 4.00.10 and got to 13% on Radio Stack Upgrade when it errored so i took it out did a few Soft Reset's no luck so i flashed the 4.00.10 Rom through the wallaby bootloader got it up waited patiently for CE to load... loaded after about 15 minutes at that time it was running terribly slow and when i got it up i had no service because i had no Radio Stack so i then loaded up this old radio stack well not so old but it was version 4.21 i then soft reset the device started the 4.00.10 install it went through the Radio Stack then the Rom update with absolutley NO errors or conflicts so everything is working great..
Heres something to keep in mind DONT Upgrade To Tmobile Rom 4.00.10 With the radio stack version A.20.10 Or you will be doing what i had to do!
i want to say thanks to all the great people out there posting
Thanks, Allen
JoshB said:
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
My suggestion is this when you're in deep dodo, try it all! :wink:
Because as your seeing what works for some doesn't always
work for others.
Reflect, sorry I wasnt able to answer the specifics of the rom earlier, I was talking about th 4.00.10 version. Im glad you were able to fix the problem. :wink:
After waiting the 15 minutes to recover from the blank G/R screen, and successfully upgrading the Radio Stack to 6.24 and the ROM to 4.00.10, I've been using it for a day or so now, and I am pleased with the new ROM and radio stack.
Biggest plus for me is that GPRS now stays "always-on", even when the unit is turned off/suspended. I also like the fact that AIM 2.0, and PDF/PowerPoint viewers are included in the ROM.
As far as stability, I have had a couple of lockups (cleared by soft resets), and one spontaneous soft reset, but these could have been caused by software that I have installed (SpB GPRS Monitor, StocksAndWeatherToday, Journal Bar, Battery Bar, PocketNav, AE Uptime, Fonix VoiceDial Premium, Resco Explorer 2003).
I have had a couple of instances where the GPRS connection stops transferring any data, but still shows as connected. Since there's no way to turn off GPRS (SpB GPRS Monitor has a Disconnect button, but it doesn't seem to work), I can clear this condition by turning the phone off (not the unit, but the phone/radio) then turning it back on and reconnecting GPRS.
Thanks to everyone on this forum for your help, support, and ideas! This is a great amateur developer community.
JoshB
P.S. - Reflect, sorry I didn't answer your IM. I was in bed...
OK, I am going to try this once more since I can't stand having a useless phone...lol
I *had* the 4.00.05 ROM and the newest at&t radio stack on my T-Mobile phone (with TM service).
Attempted to install the T-Mobile 4.00.10 rom and associated radio stack via the .exe method over that, and it failed.
After that, I tried reverting back to the old T-Mobile 3.14 rom, via the sd card method. That seems to have loaded, but the GSM is still screwed.
Currently, when I start up the phone, I get the Welcome to T-Mobile startup screen, with 3.14 in the bottom corner. After a minute the G with no number after it is there, and below that, instead of an R is a U? (Maybe because I don't have the sim card in?) With no number. Then I get the "bing" sound, and it goes to a blank screen.
Reading through the posts here, it sounds like I should write the 4.00.10 ROM to the unit with the SD card, then wait for it to start up?
Should I have the sim card in?
When should I try the soft-resetting?
Just as an update, so far so good. I wrote the 4.00.10 rom to the unit with the sd card. Did a hard reset like it told me to. Now starts up with the T-Mobile Test only Not for sale screen. Shows 4.00.10, G with nothing after it, and R with nothing after it. It now stays at this screen though, instead of going to the blank screen. I guess this is a good sign, I am in a position others have been in. Yay! Waiting on it now to do something...anything, and I will attempt the radio fix.
Related
If I have overlooked the thread that covered this situation, please just point me to it as I have made several searches and read several threads but no luck.
I was happily running a custom 2003 ROM with the original AT&T stack. As I was quite happy with the way my 2003 OS was configured and operating, I decided to just try the NEW AT&T radio stack as I wanted to see if it helped with some reception issues I have expereinced. I copied the four radio stack files to the Windows directory on the PPC. I had the PPC in its cradle for power. I then executed the RSUupgrade and at 10% it locked down completely. No hard key had any effect and in fact, not even the soft boot buttom worked. I then attempted a cold reboot and that resulted in a hung machine again.
So, I decided to take the safe route and do an SD flash burn back to the original AT&T ROM (which I had copied way back when). Using XDA Tools I burned it to my SD card. Did the soft/on button routine, and proceeded to flash the memory. If indicated that the checksum matched and was finished. After the cold reboot, I got the old splash screen, but it took forever for the today screen to appear and the START button as well as ALL the indicators at the TOP are missing. I am unable to get to file manager.
I then decided to see if I could connect via ActiveSync. I uninstalled AS3.7. and reinstalled the original 3.5. When I attempt to connect, AS does see that the PPC has been docked, but it is never able to connect.
So, I am unable to reinstall a radio stack of any kind. I am unable to get the OS to function normally.
BTW, Just for grins I also tried an SD card install of the newest AT&T ROM as well as my custom ROM and the results are all the same. I suspect the now corrupted radio stack, but HOW do I purge it and start over when I can't get the OS to boot sufficiently to reinstall the stack
ANY IDEA? HELP!!!
Come on, someone has to have an idea
I will start off with an update. After reading another thread, someone mentioned that initial boot was taking about 15 minutes when there was NO radio stack. I decided to see if that might be occurring to me and sure enough, after about 15 minutes, the PPC beeped and the OS came up. If was still a bit sluggish, but operational. I was able to successfully attach to my PC via ActiveSync.
Now for the downside. Still NO success with installing the radio stack. I have tried reflashing the OS back to the original AT&T PPC2002 OS but that made no difference. I have tried both the original radio stack and the new one, no difference. I have tried to install the stack with the SIM card (SIM not SD) in and out, no difference. It always sticks at 1%, tells me the upgrade failed and to press ok to reboot. I did read the thread that gave LOTS of help regarding this issue, but nothing seems to help. I can remove the lnk in the startup folder, delete the files, reboot, recopy via ActiveSync, start the upgrade (RSUpgrade.exe) and everytime it immediately goes to 1%, sets there a minute or so, the pops up the failure message.
Surely, someone has an idea. Could a corrupt SIM cause this? Is there a alternate way of installing the radio stack?
BTW, just for grins, I thought I would try doing a "normal" exe upgrade since AT&T posted such. I know that it is full of risk, but at this point, I had little to loose. I made sure that I was running ActiveSync 3.7.1 and was connected. I then launched the upgrade. It came up with a splash screen with some warnings and the typical stuff. I then selected the "next" button and nothing happened except that cursor (when pointing in the window) went into the "working" state where it remained until I finally killed it about 30 minutes later. There was NEVER any sign that progress was being made.
HELP!!!
david
I have the same exact problem.
The Start menu is missing. No Icons on the top bar.
What's funny is that the screen seems to be inverted.
When I tap close to the bottom of the screen, the clock setting screen appears.
Anybody have a solution?
I suspect there is an alignment problem
When I first boot up after ROM upgrade, I can get to the today screen with the volume button, but I can't get to the file explorer because the start menu is missing.
When I tap on the lower part of the screen, the upper part responds.
Could this be due to the alignment steps being bypassed?
What order do you have to tap the alignment crosshairs during startup?
This sounds like a different problem
As I mentioned, on my first reflash of the OS after the radio stack upgrade failure, I got the today screen without the start bar at the top (ie it was totally blank and tapping in that area did nothing). Everything else on the today page worked. On subsequent reflashes of the OS, the today page was totally normal, start button, everything in place and working. On those subsequent reflashes, I also got the normal initial screen alignment pages on the first boot after the reflash.
I will also post, that I finally gave up on getting the radio stack to install. I have sent my unit to the guys at PPCTechs. In talking to them, they have 2 other SX-56 units in for upgrades with the same radio stack issue. They feel that they will be able to force the reflash via alternate means using a serial cable. As I mentioned on the other thread where I have been posting, I will post back once I hear if they were successful.
David
in general people should not mess with radiostacks unless they have issues and the radiostack is recommended by the phonecompany one use
I just bought a t-mobile wallaby from here in india, And i decided there was a update available after 3.14 or something. so i ran it. But it stopped in the middle. Said 20 min but waited an hour. Then i took the xda of its cradle and did a hard reset... Now all it does is switches on and show t-mobile and the light stay on...nothing after that. I think i really messed it up. Gave it to a guy who said he could fix it but now 4 days later says he cant. Really need help on how to do it myself Please. Please help me, cant throw money away like that......can some show me step by step instructions as i am stupid with upgraded or reinstalling this device.
why have you decided that you could upgrade your device if you don't understand anything to upgrading and its consequences.
Upgrading is *dangerous* for dummies.
You are the weak link[/list]
mananmistry said:
I just bought a t-mobile wallaby from here in india, And i decided there was a update available after 3.14 or something. so i ran it. But it stopped in the middle. Said 20 min but waited an hour. Then i took the xda of its cradle and did a hard reset... Now all it does is switches on and show t-mobile and the light stay on...nothing after that. I think i really messed it up. Gave it to a guy who said he could fix it but now 4 days later says he cant. Really need help on how to do it myself Please. Please help me, cant throw money away like that......can some show me step by step instructions as i am stupid with upgraded or reinstalling this device.
Click to expand...
Click to collapse
:x Forget what this guest just said we are a community who help each other out :x
I am now using the XDAII but when i had the XDA1 i had a similar problem. Got stuck upgrading. Hang onto your horses dude your device isn't dead so breath a sigh of relief. If you have a SD/MMC Card reader then use it to burn the base Rom from
http://lumpistefan.dyndns.org and then install it through the boot loader(Hold the Power button and then press the soft reset button using the stylus(you will enter the boot loader mode and then follow the instructions on how to install the Rom.
------------------------------OR--------------------------------------------
Go to a shop or a friend who had similar device, make sure you have a SD/MMC card with you and then enter the bootloader mode as described above and then copy the ROM on the SD Card. Then insert the card in your device and again enter the Boot Loader mode and Copy the Rom from the SD Card to your device after you are done press the Hard reset button on your device to switch it off keep it off for atleast 60 sec before pressing the hard reset button again to switch it on. Your device will live again.
[/b]A WORD OF ADVICE
Don't touch the Radio Stack on either your device or the other one. Always select Rom only.
If you need further help with using the bootloader search these forums you'll come up with alot of info.
Let me know how it works out
one question
Thanks for the advice.....your must be the better part of the site.
what happens if i cannot get into the boot loader.
thanks again
Re: one question
mananmistry said:
Thanks for the advice.....your must be the better part of the site.
what happens if i cannot get into the boot loader.
thanks again
Click to expand...
Click to collapse
I believe there's a way to go-back! Do a flush by pressing on the power button+the hard reset+the navigation button pressed. All at once and that's how you go-back to the original ROM. Let me know if it works and if you dare to do it anyways.. 8)
guest said:
why have you decided that you could upgrade your device if you don't understand anything to upgrading and its consequences.
Upgrading is *dangerous* for dummies.
You are the weak link[/list]
Click to expand...
Click to collapse
Mr. Guest you are an idiot, many of us have been at this point one time our another. This is no way to respond to a forum member in need of help.
i'm no techie when it comes to these things but just out of curiousity WHAT causes the upgrade to stop? mananmistry said he was in the middle of upgrading already; is it the rom he used or is it the connection (power flux, cable, sync, etc)? just curious... :wink:
oh and its beers for the others and the loo for the guest
update
now the thing is i got the phone back. I have connected the usb but pc cannot find device and xdatools or the rom .exe files wont install. it says "xda not found via activesync", something like that. I went into the boot loader and it said GSM ERROR and stops. have to press calender key to get into sub-menus. what is the problem. does the rom kitchen .exe files need sactive sync to be present. please can some one tell me.
do i need a sd card reader. can i not just use someone phone to put my sd card and burn onto sd...??
You are now in serious trouble, the GSM error often proves fatal for the phone. You can still flash the rom though by following the previous instructions. After that is completed you will have to try flashing a radio stack. Please be prepared to be disappointed, I wish you the best of luck. The good news is that even if the phone doesnt work you should still have a working pda.
Where can i get a radio stack rom...???
Click to expand...
Click to collapse
where can i get a radio stack rom....will try...
If my gf has a pda with sd card can i use the unit to see the sd card and write the rom on it???
Re: update
mananmistry said:
now the thing is i got the phone back.
Click to expand...
Click to collapse
how did U get the phone back 2 work (bootloader)
thanks
:?:
get a radio stack from here
http://lumpistefan.dyndns.org/tools/
I've had my Qtek 9000 for a week. I've spent most of that week installing software, and getting it setup (using a lot of useful info from this site).
This afternoon it locked up, and wouldn't respond to any button presses (including the on/off button)
Soft resets result in it powering backon, but stopping at the boot screen, after displaying the ROM versions in red text.
Eventually, I tried a hard-reset. Same thing happens - process goes ok until it displays the ROM version, when it just sits there. I've tried removing the SD card and SIM card and hard-resetting. No Joy.
I had just installed OzVGA, and was testing it when this occurred, but that is probably just a coincidence (surely a hardreset should fix anything bad that happened there?)
I hadn't at any point played with the ROM.
What should I try next?
And, does anyone know if I'm going to be able to get support for this in the US from Qtek? (I bought it in the UK), new
Thanks in advance.
-Steve
RE
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Re: RE
FOSA said:
Have you try taking out the battery, leave it for a while, put back the battery and do a hard reset?
It may work
Click to expand...
Click to collapse
Unfortunately, no such luck
I'd tried that before, but the battery was only out for a short time. This time it was been out for at least 15 minutes.
Does anyone know if there's any kind of hardware or diagnostic test mode it can be booted into?
-Steve
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Jorgee said:
How about updating/upgrading thr ROM?
This might work. you'll have to reinstall everything again, though
Click to expand...
Click to collapse
Thanks - I may try that tomorrow. However, I'm a little concerned that updating it with a new ROM might invalidate the warranty (especially if it's not a QTEK ROM)
I was hoping that there was some kind of hidden 'diagnostic mode' I could try first, before taking that step. I've also been looking everywhere on the web, and I can't find anyone else that this has happened to. This makes me think it may be a hardware problem, though the way it just 'happened' seems more like s/ware.
Anyway, I'm out today so this will have to wait until tomorrow. My biggest concern at the moment is how I'm going to get any warranty support in the US. All I have at the moment is a very expensive brick!
-Steve
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
thefixer said:
Jorgee said:
Have you tried entering bootloader mode?
BACKLIGHT BUTTON + POWER BUTTON + RESET HOLE
Then the screen will go blank then show the words SERIAL but you have to look real good because the backlight will be off when the serial is displayed. If it does go there, try hard resetting from there:
__ + __ + RESET HOLE
Hope this helps. WHat's your ROM verison/language anyway?
Click to expand...
Click to collapse
Thanks - but no improvement. I do get the 'serial' screen (with v1.00 displayed at the bottom), but when I do _+_+reset from there, it just goes back to the 'normal' Qtek boot screen and sits there.
Unfortunately, not having access to the OS, I don't know exactly the ROM versions etc. However, the info displayed in red text on the Qtek boot screen (where it hangs) is as follows. How do you interpret this?
R 1.03.00
G 42.36.P8
D 1.13.64 WWE
Thanks for your help - I'm hoping I can get this resolved without having to find out how to get support from Qtek!
-Steve
Click to expand...
Click to collapse
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Jorgee said:
You have a WWE (English QTEK ROM) but since you cannot enter bootloader mode, I don't think you will be able to update. You might have to return your device to where you bought it
Click to expand...
Click to collapse
Jorgee,
I notice (in the HTC 'confidential' manual I just downloaded) that there is a diagnostic program. Apparently, I put it on an SD card, and do Power+Backlight+reset to invoke it.
Do you know if that diagnostic tool is available anywhere on here, or elsewhere on the web?
Also - I wqas trying to find exactly how to enter 'bootloader' mode (after I have the 'serial' screen). Should it boot differently from here when doing a hware reset (_+_+reset)?
Regards
Steve
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Jorgee said:
Actually, when you see SERIAL, that means you are already in bootloader mode. One question, what ROM do you wanna update to? QTEK, IMATE, MDA, O2?
Do the following once you get the SERIAL ON THE SCREEN:
1. Open active SYNC, then choose FILE>CONNECTION SETTINGS, then remove the check on the USB option.
2. Connect the phone to the computer with the sync cable. This should change the SERIAL on the device to say USB.
3. Run the ROM Upgrade (whichever it is you chose).
This shoulod update your device. If you are able to enter bootloader mode (SERIAL) this means that probably your ROM (OS) is damaged. Just update it even to the same verison then it should work.
If you get Country ID error while trying to update or any other error, just inform me, i'll walk you through the process.
Click to expand...
Click to collapse
Hi Jorgee,
I'd prefer to go for the QTEK Rom (I'm assuming, from the info I posted above that I currently have 1.13.64 WWE). I'd like to go for the same or later version of this, but looking on the ftp site here I can't see ay QTEK ROM upgraders.
I have checked that when I plug in the USB I get 'USB' appearing on the screen, so I'm hoping that a ROM upgrade will at least work, even if it doesn't fix my problem.
One other thing that concerns me. When I plug into USB (with either a PC or the AC charger) the LEDs aren't lighting to indicate it's charging. Obviously, when during the flash upgrade I should make sure I have a reasonably charged battery. However, I don't know if I do (or even if it's currently charging).
-Steve
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Jorgee said:
I guess leave it charged using the AC adapter for an hours, then here's the QTEK ROM.
ftp://xdaupload:[email protected]/Universal
Under Shipped ROM's you should see the QTEK.
If you cannot find it, tell me, ill send it to you. Trying to avoid this because it is almost 60MB in size
Click to expand...
Click to collapse
Thanks - I'd already found it on the devbuzz site, and am currently giving the unit an hour or two's charge before trying this. Wish me luck!!
-Steve
OK, here's what happened when I tried to update with the same Qtek firmware:
Initial dialog (that shows old and new (to be installed) firmware versions had blanks for all three firmware versions currently installed.
Started the upgrade, and left it running (couldn't bear the tension of watching!). Came back, and found the following error message displayed:
"Error 113: Extended ROM Update Error"
The update tool indicated that I should 'try again'. I'm currently re-charging the unit, and hoping (against hope) that this error was caused by insufficent battery charge.
-Steve
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Jorgee said:
Okay, but maybe it just didn't update the extended ROM but the OS rom has been updated properly. After this error, try the __ + __ + reset button and see if it does boot fine.
Click to expand...
Click to collapse
No luck.
I've also tried re-flashing a second time, but this time I watched it to see what happens
As the radio firmware is flashing, a message to that effect is shown on the Qtek screen. Once that is finished, the upgrade tool starts the extended ROM flash. At that time the Qtek's screen goes completely blank. The, after a minute or two, the upgrade tool reports that the extended ROM failed to upgrade.
I am assuming that normally, while flashing the extended ROM, there's a message on the phone's screen to say what's going on?
I'm also wondering whether to have a go at flashing the ROM in one of the other ways?
-Steve
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Jorgee said:
I heard sometimes just flashing the Radio only might work.... Then after that you can flash the rest. Just extract the contents of the ROM to a directory. Take note of the ff:
Radio : radio_.nbf
OS : nk_.nbf
Ext : ms_.nbf
I just rename/move/delete the MS and NK files then run the update
Click to expand...
Click to collapse
Thanks Jorgee. Still no real success, but I think I might be getting closer.
I've tried the above (using both the original romupdate_ut.exe and MaUpgradeUt_noID.exe - same results with both).
I've tried each of the three files individually (using the ones from the shipped ROM, as downloaded above)
radio_.nbf always seems to flash ok
ms_.nbf always fails right at the start, and nothing appears on the phone's screen
nk.nbf almost worked. It started, and got up to 87% (tried this 3 times), with the update showing on both the phone screen and PC. Then it failed with error 112, leaving the '87% complete' message on the phone's screen.
Soft or hard reboots still result in us just ending up 'hung' at the boot screen.
Once again, thanks for your help so far. However, I am beginning to give up hope!
-Steve
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
truongia said:
I have the same problem with my Dopod 900 at post http://forum.xda-developers.com/viewtopic.php?p=207524#207524
But mine is no problem with EXTRom Upgrade
Waiting for your advise!
Thanks
Click to expand...
Click to collapse
I wish I had a solution!!! I've spent about 20 hours trying to get this thing to boot!
One question though - how did you get the 'boot option' menu up (allowing you to clear the registry etc). I might try that on mine (I had assumed that a hard reset ALWAYS cleared the registry.
Given that I was playing around with ozvga before this happened, there's a small chance that might help (though I think not; as I can't see how that would also stop the flash update working)
-Steve
Hello-
I use this phone for my business and was having problems with it, nothing major just some software issues so I was going to bring the phone back to factory standards and decided to download and install the ROM from HTC’s website and the install went to around 95% and then I got an error message saying “this nbf file cannot be used for your pda phone, please check your nbf file” and then the install said to quit. My phone/pda was frozen so I had to remove the battery to get it to turn off. When I turn it on, I get a Red, Green, Blue and White screen that says IPL 2.25.001 and SPL 2.25.0001 and RUU on the top right hand corner. I have tried a hard reset, soft reset, and removing the battery but it won’t get past this point. I cannot afford to be without this phone as I use it for my business and until it’s fixed I am out of commission. The phone was bought brand new in December of 2006. Any help I can get would be appreciated.
Your IPL and SPL tell me (2.xx.001) that you have a G4 phone. Make sure that you have a G4 version of the ROM and try the flash again. I hope this helps ^_^
EDIT: By the way, questions like this should go in the upgrades forum.
There´s a fix dont panic!!
golfernutnflorida said:
Hello-
I use this phone for my business and was having problems with it, nothing major just some software issues so I was going to bring the phone back to factory standards and decided to download and install the ROM from HTC’s website and the install went to around 95% and then I got an error message saying “this nbf file cannot be used for your pda phone, please check your nbf file” and then the install said to quit. My phone/pda was frozen so I had to remove the battery to get it to turn off. When I turn it on, I get a Red, Green, Blue and White screen that says IPL 2.25.001 and SPL 2.25.0001 and RUU on the top right hand corner. I have tried a hard reset, soft reset, and removing the battery but it won’t get past this point. I cannot afford to be without this phone as I use it for my business and until it’s fixed I am out of commission. The phone was bought brand new in December of 2006. Any help I can get would be appreciated.
Click to expand...
Click to collapse
It happened to me last night and for a moment (actually several hours) I though I had a dead phone, then I tried another ROM and even when it went all the way up to 100% progress the tricolor screen didn´t dissapeared, then I tried a 3rd ROM and this one worked, it went all the way and the phone finally booted. Check the Wizard G4 forum on this subject.
Look here to see my story:
http://forum.xda-developers.com/showthread.php?t=289948
Look here the ROM that is suitable for you
http://forum.xda-developers.com/showthread.php?t=289469
I got it fixed by using the Wizard love rom. O had actually read your posts after I had gotten it fixed, what a nightmare! I was ready to box it up and sell as is on ebay!!!
Cingular 8125
Rom Version: 2.26.10.2 WWE
ROM Date: 6/7/06
Radio Version 02.25.11
Protocol version 4.1.13.12:
Hope I am all up to par with this phone, I got everything re-loaded and all is working great.
Thanks for the reply and sorry I posted it on the wrong forum, I am new here to post, I generally just read.
I don't know if the phone is bricked or what. Was in the store tonight, tried to text message my wife who I couldn't find and the phone was all locked up.
Soft reset, and only the date/time loaded, nothing would run. Soft reset again, and the phone didn't load past the bright splash screen. Tried soft reseting a bunch more times, nada. Did a hard reset, first one didn't work. I think it was the 3rd hard reset that took. Phone seemed like it was back to basic WM5, would be okay. Went home, put it on the charger.
Went to take it off the charger to reload data, and it won't turn on. Soft reset, freezes at bright splash screen. Hard reset, same thing.
Is my phone bricked? Anything that I can do to revive it? Or am I SOL?
Cingy/ATT 8525 w/WM5
(By "bright splash screen" I mean when the splash screen flashes brightly. It increases brightness, but just stays that way.)
Any help greatly appreciated.
I managed to load the official WM6 ROM (spl 2.03) via the built-in bootloader. I have radio, ROM, and GSM. It boots through the ATT animation, then freezes. It leaves a black screen with a blue and green static bar running horizontally across the screen about 1/4" thick.
I don't know how to get Hard-SPL loaded on the device because the only way I can see the device is when it's in the built-in bootloader mode.
will attempt PB/KITL I guess, though I can't at this point get the phone to display the KITL info.
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
viatorx said:
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
Click to expand...
Click to collapse
Not sure I fully grasp what's happening here, but if you want to stop the customisation then hard reset and when it goes to the loading cusimisation stage shove the stylus in the hole to do a soft reset and it will stop it loading.
Mike
Alright, thanks, will give that a try.
I managed to run the official ATT WM6 ROM and flash it without a hiccup (twice), and task 28 in bootloader says no bad blocks. So I am confused how I can flash an "official" ROM successfully and the device still won't work. Am starting to suspect hardware failure apart from memory.
Thanks a million mate, that worked. Phone boots now, already have SSPL installed. Need to update .net and activesync for Hard-SPL 7 to run I guess. Then I have more options.
Woot! I unbricked my phone
Once I was able to hard reset and cancel the "customization" I ran SSPL, then Hard-SPL 7, then I Super-CIDed the device.
I haven't tweaked the data settings yet, but I can send/receive phone calls. Which is a coup, because this is my main line.
It runs sluggishly. I don't know if that is the ROM or the device. It won't boot if it's plugged into USB, and after flashing Hard-SPL it isn't a recognized device by windows, won't connect to activesync.
I am treating the phone gingerly right now, will try and unload the ATT wap settings cab and restore my pim.
At least now I have the option to install another ROM if it bricks on me again.
I really should have flashed Hard-SPL the DAY, the MINUTE after the warranty was up. Lesson learned.
Or not.
ATT ROM locked up on me, decided to try Schaps 4.40. Won't load past WinMo "tap screen to setup" screen. Guess I'll try something else.
For a stable WM6 rom try TNT SE. It is REALLY stable but does come with some 3rd party apps. Thought you might like to get it working though first then try the other roms and in my experiance I haven't found many other roms that were THIS stable...
Hope you get it working...
For a disassembly guide try this site - http://michael-channon.spaces.live.com/PersonalSpace.aspx?_c02_owner=1
Its a bloody good place to go for all things to do with hardware and Mike is a true guru with hardware problems...
Cheers...