I have a TP2 supplied from the local agents which is not locked to any network so consequently I have not run the SIM unlocker.
Twice now, while trying to upgrade my radio from the official HTC website, the process hung after about 12% and would not recover.
The tri-colour boot loader screen would appear but with a lot of corrupted writing on it. Hard reset would not work and HTC eventually replaced the phone.
This was before HSPL.
Then I loaded HSPL. I also upgraded to the HTC stock WWE WM6.5 with it's included radio. I then tried to change the radio and same problem as above.
I eventually ran the HSPL re-lock program which then restored the boot loader and I was able to do a hard reset back to WM6.5. I then reloaded the stock WM6.1 because I did not like the WM6.5 UI or the radio it came with.
I did frequent updates on my Kaiser with no problems at all. Now I am scared to do anything with my TP2 in case it bricks again.
Any suggestions?
Related
Hi,
First, I ran some tests on my kjam. The kjam came default with the kjam rom on it, naturally. I wanted to CID unlock this phone, so I downgraded the rom to button's "beer glass" splash screen rom. Then I was able to run aWizard successfully to CID unlock the phone. I then upgraded back to the original kjam rom. Both the downgrade and the upgrade went smoothly.
I then found out I wanted to customize my splash, so I downgraded again. I customized the main splash (not the HTC one) using aWizard. Worked like a charm. I also ran some extra itsme tools to read and write from rom in some locations I needed access to.
Everything was working great at that point. But the downgrade ROM didn't properly respond to some of the printed keys on the kjam keyboard, so I thought I should upgrade again. However, this time, I decided I want to keep my splash etc., so I tried to upgrade only my radio and OS rom, as backed up by aWizard previously, from the original kjam ROM. I used aWizard to restore the selected areas of ROM, rather than the RUU tool.
I upgraded the radio ROM, didn't reboot the device to keep the radio and OS in sync, upgraded the OS ROM, just as that was happening, the phone received a phone call (or text message, do not know which), and hung. While the aWizard eventually completed the upgrade, the phone did not reboot or "un-hang" itself after aWizard displayed success (there was no error on the console window).
So I soft rebooted the phone. The splash screen came, but without a GSM version on it. I was like, "shoot!", something bad must have happened, lets just put the full kjam rom on this, and get it over with - never mind the custom splashes. So I went into bootloader and applied the kjam rom.
Now it displayed the GSM version as well on the splash screen, but again, it never left the splash screen. I was like, again, "shoot!", lets just go back to that old downgrade ROM with the funny keyboard, then we can figure this out again. So I went into the bootloader and applied the downgrade ROM.
Alas, the beer glass splash screen remained hung as well! And actually, since then, I've downloaded and installed ALL ROMs I've been able to find - ALL of them have hung.
My bootloader is still working fine and dandy...any idea why this might be happening? Was the problem in the phone call I received? In using aWizard without rebooting? In using aWizard at all? In trying to manually edit the machine ROM using itsme tools (mind you, those edits worked fine until I started updating the GSM/OS ROM)?
And oh, after hanging for a while on the splash screen, the phone screen starts flickering real bad (whilst still on the splash); in case that provides any help.
To clarify the bootloader situation a little more:
I've got FULL bootloader capability. I can mtty into it, I can write commands, I can install full new ROMs from the bootloader, etc. So this would seem to indicate my phone may not be a brick yet...its a brick that can display changeable wallpapers I even figured out how to draw progress bars and write text to the bootloader screen using MTTY commands. Fun, actually! Its a $700 etch-a-sketch pad
Please leave. We believe here in HELPING people without charging them.
Hmm.
A $700 etch-a-sketch?? I bet someone would buy that on eBay if you called it that.
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.
Hey guys,
I have two WINgs and I Hard SPLed one already and I Flash it regularly
the other one was at the T-mobile Rom and stable till it starting restarting at every call.
So i treid to Unlock it also like the other one
So I backed up all my contacts and Messeges with PimBackup
and after i Installed the three files
security removal, Aserg and cannonyang
when I try to Hard SPL through RUU with USB so it tells me no connection although its connected in Activsync
I searched the forums and Bypassed the Connection issue by entering the Boot loader through the phone and it got to 2 percent and told me i need a newer RUU although it is the Same as the other Wing for the versions and I have done the other one Fine
when I tried to do it again and still bypassed into the boot loader through the phone it now tells me that There is no Connection to the device. Although the USB sign is available in the bottom.
Now I have Also searched the forums and found Aserg suggesting that we install the Native T-mobile Rom
It connected fine and went into
1% of updating Image and then it gave me a communication Error
Now I noticed two things:
1. it Goes into Bootloader and CHills there
2. It Changed the IPL number from 4.26.0000 to 4.10.0000
but SPL remained 4.26.0002
Does any one have a Solution for this Problem Guys?
Is it bricked now and I just can't see it?
Please help because all my contacts are are on it and i am working with crappy nokia instead of it that has none of them.
you can import your contacts from PIM backup onto your other device if it has PIM also, you know that right?
Now some questions
Did you install the cabs that papamopps said to?
Can you still flash the RUU? It seems you have the newer Wing SPL but the older IPL.
I just flashed my Diamond with the: RUU_Diamond_HTC_NOR_2.03.409.1_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe
I'm an norwegian that's in the US studying, so they only gave me the norwegian version. Anyways, everything worked fine until flash, but now my phone refuses to register on the network (AT&T)!
Took the sim-card back to the at&t nokia phone, worked the first time...
I really wants to use my Diamond instead of the crappy nokia, but it would be a shame to downgrade to 1.93 (which worked just fine...).
Someone, please have a solution for me?
simply install a new radio....try 1.00.25.07 that seems to be the only quadband radio..
(you have to flash an hspl before)
It's stuck on 0% and won't continue... Tried several roms :-/
no service?????
is there a soution to this no network problem
THERE IS A CROSS IN THE RECEPTION BAR AND WHEN YOU DIAL OUT IT SAYS "OPERATION FAILED"
any replies appreciated
Quite bad if the official RUU more or less bricks the device, at least turns into just a little computer
It screwed up my Diamond aswell The gprs is completely dead, been up all night trying to fix it, several hard resets etc, nothing helps... if it was a cooked rom I could tolerate it but official roms screwing up our phones this easily pisses me off.
Mine worked again, with the old 1.93 rom!!
What the hell did they do to 2.03? I suppose the radio rom is different at least... But I couldn't change to the old radio when I had 2.03, tried using the HardSpl...
Is it possible to flash _once_ with everything from 2.03, but the 1.00.25.05 radio (which is the one from 1.93)? Doing it sequentually doesn't work.
So what I did, as the final solution:
Flash with stock 2.03 rom
HardSPL
Flash with 1.05.25 radio
Works perfect!
Hmm i did the other way round with my o2 XDA Diamond (1.93 Stock)
1. Hard SPL
2. New Radio Rom (1.09.25.23)
3. 2.03 official Ger HTC Rom (without vendor lock)
works great as well
I've seen this issue a couple of times too. With 1.93 as well as with 2.03. Did not figure out what was the cause but never had a chance to bring the device back to life with some uninstallation or radio flash. I always went back to the SPB Backup from the night before it stopped working propperly.
i Download the HTC Fuze ROM Update- Version 5.11.502.2 WWE
after i flashed it and booted it, initial setup was taking place... it said it was setting up touchFLO. everything looked good.
until...
it just rebooted!
and it keeps cycling that way. it never gets to load windows.
i have read that other people have been having trouble with touchflo after the update... but now i cant even get windows to load.
ive been trying to find solution all day. about 15 hours. i cant even flash another rom into it. i cannot hard spl. anyone?
Did you install Hard Spl 1.40 before you flash the device ??