Hey Guys,
I followed the instructions to the letter on my Verizon 6800 using the 2.4 Bootloader, then the latest Sprint Radio Rom of 3.35.651 and it was hanging at the 11% mark every time.
So I used an older radio ROM and it completed, then the phone reset itself and will NOT POWER ON.
The battery is fully charged, and doing the power+camera+soft reset does not do anything. Nor does hard-reset steps, or removing battery.
The device will not power on, go to bootloader, nothing.
I guess i have to return to Verizon, any suggestions on final steps to take before I give them a device with some stuff on it? Thanks!!!
Related
Hi folks,
this is what it says when I turn on the phone
1.08
1.08
1.09.11
1.8.11.1 (do you think i need to upgrade)
I am currently using 1.8.1.1 Rom on my OS(thats what it says when i open it)
How can i upgrade it to 2.17(like most of you guys)
if the official version is available i would appreciate it.
I unlocked the phone with [email protected] when i got it.
And one more question
will it help my battery life(upgrading to 2.17 rom)
i just need a good battery life actually.
thanks for the masters who will help me to pass the noobing on my new device
i think you should try doing it again, just make sure your phone and the cid is unlocked first, then run the new rom
I was there about 3 weeks ago.
First if you are only running Summiter's ROM upgrade tool and after it executes you are still seeing the 1.08 numbers then the ROM upgrade did not take. This happened to me.
Goto the Lokiwiz post and use Lokiwiz 0.2b and select option C superCID unlock. READ the directions!!!! They are very clear, follow them exactly and your phone will be CID unlocked.
Then re-run Summiter's 2.17 rom updater and when it finishes you should see the 2.17 numbers when it reboots...
Then go a re-install all your software again....
PS if anything ever goes haywire on the ROM upgrade you can always get back to the bootloader screen on your device by performing a soft reset and HOLD the camera button in until the multi color screen appears. Then plug in the USB cable it will say USB on your device screen and then you get start the ROM upgrade again. I know I had to do this several times just because I DID not READ the directions closely!!!!
any suggestions for battery life?
mine lasts for a day with regular use I'd be very happy if it stays for 1.5 2 days.
Was in the process of upgrading from WM5 to WM6 on my Qtek 8310 when I did Step 5 on the guide - run Patched_RUU. It reached 100% and said it completed then the phone switched off and I can't turn it back on.
Is it now a paperweight?
Bricket Typhoon
A Qtek 8310 is not a Tyhoon but a Tornado. So I'm afraid you updated with the wrong rom. Don't know the consequences for sure....
Cat5 said:
Was in the process of upgrading from WM5 to WM6 on my Qtek 8310 when I did Step 5 on the guide - run Patched_RUU. It reached 100% and said it completed then the phone switched off and I can't turn it back on.
Is it now a paperweight?
Click to expand...
Click to collapse
Try removing the battery, hit the power on to dissipate any latent energy, put the battery back in and try to power up. If that fails, read the WIKI for the 8310 and try to start in bootloader mode. If you can start in bootloader mode, then there is a (slim) chance you can write the correct ROM to your phone from there.
SPL's (bootloaders) are very device specific, but if your phone was not yet fully or properly unlocked, it may have prevented the patched RUU from installiing. Try these steps and report back what you find. Be sure to look carefully at your screen because ofter the backlight will not turn on but there is still function on the screen. Good luck
Doh! What an idiot I am!
Yes you're right it is a Tornado - that's what happens when you try flashing your handset first thing Sunday morning!
Thanks for the suggestion raskell but I can't seem to get any response from it whatsoever.
Need help!
I have been messing with this phone for afew days now can't seem to get it to work. When I power the phone on all I see on the screen is green screen that says "IU BUILD! Test Only" this ws the result of a hard reset. The device is sim unlocked but I don't believe it's super cid unlocked. I'm unable to do anything except for hard resets and bootloader screen. I was going to try to reflash the original rom but can't seem to find any, I only have access to the sp3 roms which I can't use since it's not super cid unlocked. Any help would be great!!!
iMate OEM ROM
http://rapidshare.com/files/61129896/SP3_WWE_2.4.33.11.zip
Here is a link to an iMate OEM ROM. Start in bootloader and execute this to see if you can recover your device. You haven't shared much about what you phone is or how it ended up like it is. You are correct that it needs an OEM ROM, then application unlocked then Super CID unlocker before flashing a custom ROM. Good Luck and report back you results.
The phone is a Krome IQ700. In bootloader mode it shows IPL 0.27 SPL 1.01.0109 Typhoon UI. Another problem is active sync does NOT see the phone. When attempting to load any rom I get error 264. I think I might have to load rom with SD the only proble is I've never had to do this before so any help would be great. I could honestly live w/o the phone but I think this would be a great learning expirence. Thanks in advance.
after attempting your reply my phone is now dead and will not power on ...
nwdrifter said:
after attempting your reply my phone is now dead and will not power on ...
Click to expand...
Click to collapse
Remove the battery and memory card, wait 30 minutes then re-insert the battery. Hold in the camera button and then plug in the USB. If it is still alive, it will open in bootloader (Red, Green, Blue) mode.
still dead... what do you think happened?
nwdrifter said:
still dead... what do you think happened?
Click to expand...
Click to collapse
I had this once when my oem battery died. I was able to jumpstart it and get it to recharge using a 9v battery to kick it up from nearly 0V.
If you have a battery meter, you can test the contacts, looking for 4v across the battery terminals (remove battery from phon to test). If you get < 2v then you battery does not have enouge juice to power up.
Once you get power back, do you have the ROM from your OEM? You should be searching for it in the mean time. If I find anything on it, I will let you know as well.
Everything I see on your phone specs appears that it should respond and behave like all of the other Typhoons/Sp3's. As long as you followed the unlocking steps from Karhoe's post (second sticky on typhoon main page), your device should not be a brick. If you recover power, you may want to first flash an WM5 ROM from one of the posts then try to flash WM6 as this is the prescribed method starting from WM2003.
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've been using Android NAND for a while with no problems but the other day I struggled getting into bootloader. Eventually (for no obvious reason) it went in and I flashed the shipped rom. I tried bootloader again but no dice. Then I made the fatal error of flashing HSPL again only to get stuck on the O2 screen. I can't get any further.
I can't connect to the pc because it doesn't see anything and I can't get it onto bootloader to flash anything else. I've tried everything I can think of bar JTAG (which is out of my league) and I'm supposed to be sending it back to HTC tomorrow for a repair.
Question is, will HTC see HSPL installed without access to the bootloader and, if they do, will they tell me where to shove it?
..tried searching everywhere before starting a new thread...
jetsetwilly said:
I've been using Android NAND for a while with no problems but the other day I struggled getting into bootloader. Eventually (for no obvious reason) it went in and I flashed the shipped rom. I tried bootloader again but no dice. Then I made the fatal error of flashing HSPL again only to get stuck on the O2 screen. I can't get any further.
I can't connect to the pc because it doesn't see anything and I can't get it onto bootloader to flash anything else. I've tried everything I can think of bar JTAG (which is out of my league) and I'm supposed to be sending it back to HTC tomorrow for a repair.
Question is, will HTC see HSPL installed without access to the bootloader and, if they do, will they tell me where to shove it?
..tried searching everywhere before starting a new thread...
Click to expand...
Click to collapse
How did you flash shipped if you couldn't get into bootloader?
You're doing vol-down and power on right? If you get a splash you should be able to get into bootloader, because SOMETHING is telling your splash to show up.
Try putting the correct shipped on your SD and power up with vol down.
I think they will be able to tell that you modified it.
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
jetsetwilly said:
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
Click to expand...
Click to collapse
Well, I've seen lots of warnings about having your battery greater than 50% while flashing, which (obviously) means that if your device has run out of juice while flashing could lead to unrepairable (by end-user) issues .
Try orangekid's advice and report back.
jetsetwilly said:
Thanks for the quick response. I'll try it again with the sd card. The only thing I can think is that the battery died on me almost as soon as I tried the sd card shipped rom. I saw the bootloader for a second and then the phone went off. When I charged it back up, no bootloader...
The problem is I've tried so many things, I'm struggling remembering the exact order of my screw up. I have a feeling after the battery died and I couldn't get it into bootloader, HSPL was working and I flashed the stock rom using USB flash.
Click to expand...
Click to collapse
when flashing from SD, SPL and radio are the first 2 things it flashes afaik, so power out right when you started flashing could be a serious issue.
Hopefully what I said above works though, if your SPL is completely fubar I have no idea what HTC will say, what I would tell them if you try to RMA is you had problems with random reboots and did a hard-reset, then when it started flashing it just turned off for no reason and now it's weird or something like that so they think it was a regular stock hard reset thing and not a "oh **** I have to restore to factory cuz I have HSPL on here" thing.
Ok, so I tried about 10 more times with no joy - at least it's consistently broken now.
Thanks guys, just hoping for an 11th hour rescue. I'll send it off tomorrow and report back the outcome with HTC. I appreciate your help. I knew the lack of charge and flashing via bootloader was going to trip me up one day.
Was HTC able to bring the phone back to its original state or were you able to do something to get the issue fixed? I have the same problem. All I did was to load prj Clean Desire v0.3.2 ROM (this ROM is the same as Cotulla's but with few fixes). This was the first time I ever attempted loading an Android ROM on to my HD2. All looked well initially. The phone was rebooted after ROM was installed. I did intial setup like facebook acct, email, wi-fi, gprs, etc. Then after few hours, the menu button (windows button in HD2) and back button quit working. Even the power button when pressed for few seconds wouldn't bring up the power off and other options. I thought a soft reset would fix it and then I pulled the battery off and restarted. All I now get is the first boot screen with "123456...go.go.go..." and then a white screen with HTC on it. Nothing more. It is stuck there. I tried getting in to bootloader, but I couldn't. Holding down the volume-down and then pressing the power button just restarts the phone as mentioned above and takes me to the HTC screen. Not sure how can I get to the bootloader. Desperately looking for help....