I need some desperate help. Looked thru the threads but could not fix my issue.
Let me first explain how I get here.
My TMO MDA started to reboot intermittently ever since I upgraded to the WM6 roms. I went through several WM6 flavors thinking it was fix the reboot issue. The phone would reboot during calls and while accessing internet. It would sometimes hang during splash screen as well.
So...thinking WM6 is not stable I decided to d/l back to the carrier rom (file name: MDA_software_update_226102_22610105_022511).
When I started downgrade on one occasion, the phone rebooted towards the end of the process.
Ever since I've had no luck doing another rom update. I'm notices the phone would just turn on with the straight into the bootloader mode. It shows RUU on the right side and IPL/SPL 2.26. The bootloader screen would flash (rebooting?) causing the connection to drop.
Is my phone bricked?
Related
I have a Qtek S200, which is stuck in the boot sequence. what i beilieve is unique about my situation is that i am able to sucessfully flash updates roms, but even before i messed with anything the problem began. the strange thing about what is happening is on the boot scree where it should show all the rom versions, the 'GSM' line is missing. this seems to happen randomly, but most of the time, and the phone never goes beyond that screen, it just eventually goes all white, then reboots. i have flashed with older and newer radio roms, and have finally flashed with the newest dopod rom (2.15) with no change in the situation. does anyone have any suggestions?
Thanks, Mike
maybe you can try this one
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=444&PN=1
or downgrade to a v1 rom and see if you get to boot all the way
Now you issue could be something else but what you can do to make sure (to a certain level) that the GSM radio is the culprit is take out the SIM card and try to turn on the device. This way radio would not be initialized and if radio is the problem, this way device should boot up successfully.
I have had this problem with my older JAM and had to take it to service center (They said radio was sucking in too much power and making the device to reset itself.)
Hey folks,
I got the T-Mobile SDA and it's allready running WM5, so I skipped step 1-4 in the how to and wanted to flash the patched ruu from step 5.
But whenever I start the flash tool it starts fine, checks version and then boots into the bootloader mode (the one with the color bars). But after that it wount start flashing. After a while it aborts with a communication error. Also when it switches to the bootloader mode the activesync connection disappear, which I assume is correct, but from my mda2 which I flashed couple of times via the bootloader I remember that when it went into the bootloader some sort of device was discovered from windows. with the sda it's not the case.
Anyone got an idea what is going on here? I thought after I flashed wm5 on the damn thing getting wm6 on there would be a piece of cake...
thanks for your help!
4saken
_4saken_ said:
Hey folks,
I got the T-Mobile SDA and it's allready running WM5, so I skipped step 1-4 in the how to and wanted to flash the patched ruu from step 5.
But whenever I start the flash tool it starts fine, checks version and then boots into the bootloader mode (the one with the color bars). But after that it wount start flashing. After a while it aborts with a communication error. Also when it switches to the bootloader mode the activesync connection disappear, which I assume is correct, but from my mda2 which I flashed couple of times via the bootloader I remember that when it went into the bootloader some sort of device was discovered from windows. with the sda it's not the case.
Anyone got an idea what is going on here? I thought after I flashed wm5 on the damn thing getting wm6 on there would be a piece of cake...
thanks for your help!
4saken
Click to expand...
Click to collapse
by the sound for this you have allready got the bootloader the right one. if it says spl 1.01.0109 on the green part of you bootloader then you can flash wm5 or wm6 these no need to flash the patched ruu
lol, ok. it's flashing now! I didnt think I already had the right version. But you were right. it said 1.01.0109 in the green bar.
let's hope it goes trough without a glitch
I flashed some rom on here a while back. The wife has the wiz and I have the herald. Anyhow, she was having problems so I figured I'd flash the stock 2.26 tmo rom back on her mda. I ran through the update utility and it crashed at about 7x %. Now it is stuck in a bootloader reboot loop...Anyone have any suggestions?? I need to get her phone working again so any help is appreciated. By the way, its a G3 device.
Thanks
Kevin
Just reflash the t-mobile stock ROM again, as simple as that. Most of the time when you have a failed flash you get the bootloader every time you boot. Make sure you don't connect the sync cable until after you're in the bootloader and when you do connect it it says USB at the bottom and you should be good to flash from there.
Hello! First time poster here.
I have a Cingular 8125 (HTC Wizard G3) that was stuck at the bootloader screen (red green and blue bars).
I was able to get the Button ROM (IPL & SPL 1.05) loaded onto device and it was working. I was able to place calls, send messages, etc.
Well, I was following the guides here on this site for unlocking and ran through the unlocking procedure, at which point I attempted to load the T-Mobile ROM (2.60 is what hte IPL and SPL shows).
However, while loading the ROM it failed at 85% giving an Error 302. The device started to reboot over and over again, never getting past the bootloader screen.
I am able to get it to a stable bootloader screen by powering the device off and then connecting it to a wall charger for awhile (i have varied the times, usually I let it sit for more than 10 minutes). I will then connect it back to the PC and try to flash the rom back to the button rom, but it has started doing it on the button rom as well!
Does anyone have any ideas? I have been scouring the forums and haven't found anything yet. I do have the Multi-port/USB TTY program, but I can't seem to find any commands to help me out.
Any help would be greatly appreciated. Thanks!
Update:
I was able to access the device from the TTY (while it was at the bootloader).
I entered in the password (BsaD5SeoA) then entered in the command: ruurun 0 followed by ResetDevice.
The device rebooted at the Button Rom came up! However, it is currently stuck on a customization program....installing Signed_DiscoButton8.sa.CAB
Ok, at this point I'd try the following things. First, hard reset. On reboot, go thru the whole screen alignment. Don't worry about setting date/time, you won't need it. When the screen gets to where it says Customization In 3 Seconds IMMEDIATLY SOFT RESET. You don't want it to customise. Now, it should work normally. Try to flash tmo rom. It will hang at 85% for a while. If that doesn't work, flash from the bootloader screen. Just go into bootlader, (hold camera, stylus into reset hole), after plugging up usb make sure you theres a usb at bottm of screen, and flash your rom.
Thanks for the reply witch.
I tried what you suggested, and I'm still having problems. Whenever the device attempts to flash, the screen will go blank and start endlessly cycling through the bootloader.
I was able to repeat what i did earlier, and got it back to working w/ the button rom. At least I am assuming its button rom. The numbers aren't really matching what button rom was originally. Button was 1.05 IPL and SPL, but the device still shows 2.26.
I checked the version screen to get some numbers, just in case.
ROM Version: 2.26.10.2 WWE
ROM Date: 6/7/06
Radio Version: 02.25.11
Protocol Version: 4.1.13.12
Any thoughts on why it won't let me flash? I'm a little leary about attempting any ROM upgrades now that I have it a (hopefully) working state. I am going to let the battery charge overnight (was dead after trying everything) and try making some phone calls w/ it tomorrow and test other functionalities.
I have a cingular 8525 (Herm100) that I was running windows 6.5 on from Scotty 93.
This ROM the HTC Home version.
Recently it started hard resetting randomly and finally the last time it hard reset on its own, it became stuck in bootloader mode. Whenever I try to flash a Rom on it everything works fine and the progress bar comes up until the very end. As soon as the progress bar disappears, the Rom should boot but the bootloader just comes back up. I have HardSPL 2.10 from Olipro on it.
I looked at common bricked hermes cases and it didnt fit any of them. I have run out of ideas of what to do. Any help would be greatly appreciated.
Nevermind
wow. nevermind. I think I may have fixed it It seems like it has an internal battery or something because I had to remove the battery and let it sit for an extended period of time before it would start to boot up normally. Then when it did, I just flashed the old prerequisite ROM as soon as I could establish a connection with my computer. It seems to be working totally fine now.