Ok, so now I'm feeling bad. I gave the kit I built for my SX66 to upgrade to the 1.08.00 radio ROM, and he killed it. He tried to upgrade the ROM with the power line attached to the cradle, and the unit started the to flash the ROM, and shutdown (assume battery drain). Now his unit won't power back up, and doesn't respond to hard/soft reset. He is currently draining the backup battery in hopes of bringing the unit out of flash mode.
The kit ONLY included the ROM upgrade for the radio, so the ext and system rom should still be intact.
I told him to try to cradle the unit, and rerun the flash.
Anyone got any ideas??
Thanks, Chris.
Just take the battery of and drain the backup bat.
Now get the latest complete upgrade from your supplier ( ..........ship.exe)
Run it, if it fails, just drain it again and run the orig. upgrade again.
If you dont have an orig. upgrade, you might have a problem.
Go to Wiki and read, search the forum for a rom that fits your device and use what you learned on Wiki to flash that rom to your device
Bosjo,
Thanks, draining the backup battery did the trick. I really appericate your help.
-Chris
Great
I can recover from just about anything with my orig. upgrade.
Just pull the bat. for 3 minutes (It's not even drained) and run the upgrade.
Now dont think that this will work in any given situation, cause it wont.
Read the Wiki before doing anything with you BA
Related
Hello,
I believe I have a real 'tough' scenario:
My BA (WM2003) was running normally till yesterday where it simply 'froze'. I tried restarting it, (soft and hard) and it kept stalling on the (IMate) splash screen and didn't proceed to WM. I left it to battery drain completely.
I came to work this morning, and literally tried everything:
Standard Upgrade using the Imate original exe (PDA2k_WWE_14000_176_11200). doesn't recognize the phone anymore.
Tried the MaUpgradeUT_noID with the nbf files (radio, ms and nk). In all cases the upgrade starts and gets interrupted in the middle with a 'weird' error and the BA display fades as the signal led goes RED (constant, no blink). I have to take the battery out, back in.
Tried the mtty set 14 0 / task 28 sequence with no result. (The info commands return a garbled sequence which makes me assume that my bootloader got corrupted).
Any advice would be appreciated.
Thanks a lot.
W.
wzaatar
Read in another post that you got no reply on this one.
Well it seems like nobody can come up with anything that would make more sense than what you have done.
My wording is when everyting else falis go back to the original rom and start from fresh.
If you can't flash an original rom in the ship.exe or the extract form you need to send it in.
Does your device react to hard reset ?? at least you should get a boot screen.
Have you tried Bootloader mode?
I know that this is a really stupid idea.. but have you tried putting it in bootloader mode, and then trying to upgrade? Or maybe throw a WM5 rom on there, and downgrade again! Worth a try until you send it in!
Thanks for the replies guys, I really appreciate the help.
I figured out that I had two distinctive problems:
1. The constant red led light, after a lot of research, it turned out that the battery was defective. Changing it solved the problem.
2. Now, I am able to flash the ROM (Tried it a couple times so far) with the orginal or another one. It flashes correctly, but only if I use the NoID flash program, else it will return a MODEL ID error. And when I reboot it, it stays stuch on the 'Imate' or the bootscreen and I don't get the WM to load (As if it freezes)...
3. I don't think I can upgrade to WM5 as I need to shrink the EXTROM size? Can this be done through some 'task' or other command in mtty for example?
Thanks for your suggestions.
Cheers,
Wadih.
Firstly, let me say that I scoured the forums and the internet in general for information before starting a thread. Finally, I came to the conclusion that I needed to start a thread.
I bought a PDA2K from a friend who upgraded to a newer phone. It worked great, was MUCH better than my craptastic PPC4100 from Audiovox. Then it started crashing. Just freezing at random times. It got worse and worse.
Finally, someone suggested the ROM was corrupted and that a flash to the newest firmware, replacing the bad information, would solve the problem.
So, I downloaded the latest firmware (PDA2k_WWE_14000_176_11200), followed the instructions, and began the flash.
When analysing my device, there was a blank spot next to the extended ROM information, which confirmed the theory that the extended ROM was corrupted.
I initiated the flash, and it completed the first stage of the flash sucessfully. Then the problems began. The phone went blank. I left it alone, but nothing happened. So I killed the flash and pulled the battery. When I replaced the battery, the standard bootloader pulled up (Serial 2.07).
After reading for a bit, I decided that I wasn't SOL. So I docked it again, and got a 'USB Device not Recognized' error. I ran the flash anyways, but it never progressed past the 'analysing your device' screen. So, I disconnected it, hard reset it, and docked it again. This time, when I docked it, it switched to (USB 2.07), and windows recognized it as Microsoft USB Sync. I thought I was in luck.
Yea, right. Same thing, the flash program does not progress past 'analysing your device.'
So... am I SOL? What do I do?
I think I went to this problem before, I remember that I solved it by downloading the upgrade from wiki
http://wiki.xda-developers.com/index.php?pagename=BA_Upgrades
try downloading the rom from wiki and try upgrading again. if it doesn't work, upgrade without extended rom. once its done unlock extended rom by extended rom unlocker software and remove all contents in it and then run upgrade again.
I hope someone can help here or point me to a post with steps to fix this.
I decided to do a ROM update on 8125 like device (Does not say Cingular or HTC etc. on the cover) But when started said QTek.
I installed the T-Mobile ROM update MDA_software_update_226102_22610105_022511.exe
Now the device starts then shuts down and then strats again then shuts down again. Sometime it makes it all the way to the start menu but most of the time it restarts during booting.
When it does make it to the start menu. The device reboots with in 30 seconds of clicking here and there.
Thanks,
You may be using the update not for your ROM...
Try to hard reset your device by pressing CommManager+VoiceCommand+reset (Release reset while still holding the other two buttons), then press Call button when prompted.
I have tried that many times but no help.
Phone boots
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 2.26.10.2
Windows Mobile
Reboots
Phone seems to me stuck in loop.
If I take out the battery
Give it a little rest.
Then it boots like normal but as soon as you click here and there the phone auto reboots.
Thanks,
I think you better try if the phone still reboot if it is in bootloader mode (Camera + reset). If so, then it is a hardware fault and software repair should not make any change.
If it stays in bootloader mode without reboot, then maybe the updater placed a bad ROM dump in your flash. Visit the unlocking forum, view the unlocking sticky and follow the instruction to use Button's 1.05 ROM to unlock CID, then flash another ROM.
No phone is not in a boot mode.
I did install the boot 1.05
CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
Then install the
MDA_software_update_226102_22610105_022511.exe
But the phone just keeps rebooting.
Does anyone from where I can download and install the
early release of Cingular 8125.
Thanks,
CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe
This ROM is used for CID unlock only, it is NOT a Cingular stock ROM, and you should upgrade to other ROM for day-to-day use because the IPL and SPL is far too old.
Read the how to flash a rom sticky, then read all of the stickies you can find about how to flash a ROM. Read the wiki.
Read, read, read. All of the instructions are available - you just need to take some time and read them.
kegobeer said:
Read the how to flash a rom sticky, then read all of the stickies you can find about how to flash a ROM. Read the wiki.
Read, read, read. All of the instructions are available - you just need to take some time and read them.
Click to expand...
Click to collapse
This may help, the exact same thing happened to me with my touch pro, I thought it was corrupt rom or somthing, however after looking into every aspect of this and trying everything I found the fault. It was my left hand battery pin in the back of the phone, it was bent at a lower angle to its two other friends. I carfully levelled them all out and raised them slightly and the phone was instantly cured. Try it I hope it sorts you out.
I would also suspect a bad battery issue. If you have not recently messed with the pins, I would right off suspect the battery. You must be ultra careful when bending any pins. I would first replace the battery. I had a battery that was up to 100% then dropped right off to 0 as soon as I attempted to make a call. Also it is common for the chargers to go bad. I had a wall charger that actually seemed to drain the battery overnight. I replace it with the battery and problem solved. Try batteries plus it is a chain store and they will have your battery and charger. Good luck. And one last thing try and charge with a wall charger or usb most of the time. It is much better on your battery then a car charger.
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Hum... maybe when you reCID locked it, you put a CID that's not for that official ROM you're trying to flash. The misbehavior of the phone is due to the ROM you had, not the CID Unlock. If I'm not mistaken, you can hardSPL it again, from bootloader. Then you can try and flash any other ROM you wish. Give my ROM (WM5SE rev5 - if your phone can handle 240MHz - or rev4) a go, after you have CID Unlocked your phone.
My phone can take up to 273 but, all the roms i flashed were g4 safe.... because the ipl spl never changed and i checked them in shell tool . it gives me a update error 302 which wizard love documentation says that the "phone needs a new rom code" which implies that it needs to be taken to cingular, and i dont think i can lie that well. how would one "accidentally" put their phone into bootloader?
theblackhandx said:
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Click to expand...
Click to collapse
You have posted present IPL/SPL 2.25.001,is it 2.25.001 or .0001 ?
As you removed 'HardSPL',did you reflash the appropriate IPL/SPL regarding your phones official bootloader IPL/SPL...?
You shud do the 'HardSPL' again and either do the removal of HardSPL again correctly as instructed in the sticky ' How to remove HardSPL' or Flash any other Rom to recover.
Cheers!
no it was 2.25.001 just a typo. i think i will try these suggestions when i get home and i will post my findings.
Hi all,
I recently got a G4 T-Mobile MDA and flashed it with Molski's WM6 ROM http://forum.xda-developers.com/showthread.php?t=412845.
I did this by using the instructions at http://forum.xda-developers.com/showthread.php?t=394218
Everything went fine and my Wizard was happily upgraded and all was fine.
Unfortunately, I had an active syunc failure and had to soft-reset the Wizard. It would then boot up, tell me the IPL/SPL, etc. and then hang at the splash screen. I cannot hard-reset the phone, and I can enter the bootloader.
From what I can tell, I need to downgrade to the carrier ROM, and that should see me right. As I didn't unlock my phone with HardSPL (only SoftPSL, can I just:
Fully Charge Wizard
Reflash carrier ROM using the same instructions I used
Enter bootloader
Fully charge the Wizard
Follow the instructions (using softSPL and the update utility) I used origionally to flash the carrier ROM
I then should be back where I started and I can re-flash Molski's in.
Is this the correct proceedure?
As I SoftSPL flashed my Wizard, do I need to revert back to the carrier ROM or can I try to reflash Molski's to see if that corrects the problem?
I am sorry to be a pain and ask this, I have read alot and am pretty sure I need to do this. I have read in the forum a few times that if you aren't sure, ask. I hope this is OK.
Thinking of using the T-Mobile ROM in http://forum.xda-developers.com/showthread.php?t=342744
Thanks all!
Note:
IPL/SPL 2.21.0001
GSM 02.07.10
OS 11.0.0.1
Well,as you upgraded with SoftSPL,no patched IPL/SPL was flashed and the original official Bootloaders are booting the device,therefore,there's no need to flash the official rom using SoftSPL,it can be flashed directly without any problem.
Secondly,it won't charge in Bootloaders (IPL/SPL) and untill and unless there's a working OS on the phone,so try to charge the battery through other means,like with a friends phone or buy a cradle.
As you are already in Bootloaders,coz your phone boots up and stuck at Bootloaders,you can flash any rom in this mode,but you can always enter into Bootloaders by pressing Camera button and soft reset together simultaneously.
Yes! you can still reflash any custom rom using SoftSPL,even this Molski's WM6 ROM in this situation wiyhout any hassel.
Nopes,its not neccesary to first flash official carrier's rom and than flash any custom rom,you can still flash to any custom build through SoftSPL.
BTW!!! why don't you try a Hard Reset,it may clear the stuck up and load into working OS,you can Hard Reset by Comm Manager button + Voice Command button + Soft Reset with stylus,it'll hard reset and reboot,check if this works out,otherwise go as above.
Thanks zabardast_1.
I did try to hard-reset but it wouldn't work. However, something interesting happened. When the issue occured, I had about 30% batter power, I think. I left the phone on charge with the USB wall charger (light went orange up top so I knew it was charging) after trying everything I could think of knowing I needed to charge it to re-flash it.
I came back to the phone about an hour later and tried a hard-reset again, and it worked!! I know for sure I used the correct hard-reset method when I was attempting to fix it earlier - but... questioning myself now.
Does anyone know if you need to have a certain charge to allow a hard reset? Seems unlikely.
Thanks for the information anyway - I was wanting to clarify this in anyway, just incase I did have something more permanent go wrong.
Thanks
jason
Its a built in safety feature in the wizard to cut off all the operations if battery charge goes below 30%,it for protection of the lithium battery in the phones,otherwise it dies quickly.So always try to keep it charged above 50% and never let it to fully discharge itself.