Back again with another question.
I managed to flash another working rom on my phone but,..... (there's always a but )
My phone worked great for a couple of hours and then i froze.
Rebooted the phone and 9 out of 10 times it freezes upon boot (t-mobile screen) So i figured re flash... but once i tried the following problem came up.
It even freezes in the bootloader. Most time when it starts and shows the bootloader screen you see a small short line of colors showing up at the top center of the screen.
So now my question is whether its possible that the bootloader itself is damaged/corrupt and if so is there a way to fix it?
Its prob a stupid question because i have read some treads about that on the forum but I could not find any specific to the Tm Wing / Herald.
And i wanna make sure before i can arrange a funeral for the phone
Thx
Phone info,
Device Name: HTC_p4350
Rom version: 4.12.405.1 WWE
Rom date: 04/09/07
Radio version: 02.83.90
Protocol: 4.1.13.37
ExtRom version: 4.12.405.101
Model No: HERA120
IPL 4.10.0002
SPL 4.10.0000
try to flash to a different rom
cookiemonster55 said:
try to flash to a different rom
Click to expand...
Click to collapse
Thx,
I tried but most rom's won't work in my case.
For some reason only the original t-mobile rom make my WLAN work.
RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship
And the other one that works is
HERALD.ASerg.12.WM61R.WWE but then my WLAN does not work for some reason.
Most other ROM I cannot get to work because it keep saying either image file corrupt or incorrect hardware ID
But even the bootloader keep crashing lots. So i was wondering if the bootloader is a separate piece of software from the ROM that you can flash and possibly also damage.
I have tried lots of solutions but 99% (of what i can find) has to be done with Active Sync working. Mine does not boot 9 out of 10 times so no Active Sync. When it does it crashes pretty fast. (most time when i slide the keyboard out or when i wanna flash it )
But i'm not ready to give up
Related
I have a T-Mobile Wing for about 1,5 years now and up until the other week it worked great. For some reason it only show the T-Mobile flash screen and does not boot anymore.
I tried to flash it with the latest RUU rom but every single rom i try to flash keeps saying that its not the correct model ID.
Since it hardly ever boots WM6 anymore i try to flash it from the bootloader. (turn on and hold cam key)
I booted good once and i managed to get the following info,
Device Name: HTC_p4350
Rom version: 4.12.405.1 WWE
Rom date: 04/09/07
Radio version: 02.83.90
Protocol: 4.1.13.37
ExtRom version: 4.12.405.101
Model No: HERA120
Platform: PocketPC
IPL: 4.10.0002
SPL: 4.10.0000
Can anybody tell me which rom i should try to use??
So far i have had no luck at all.
I tried the following ones without success,
TMo_Wing_RUU_Update_4.26.531.4
RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship
I messed up my phone yesterday and was able to recover it using the TMoblie update ROM.
Did you try it more than once? Mine worked the third try. Make sure you are in bootloader. It is weird, but once in a while flashing takes acouple times.
So before you try other things, try the TMoblie ROM again from here:
http://wiki.xda-developers.com/index.php?pagename=Herald_Upgrades
use 4.26.531.4
PuffyTacos said:
I messed up my phone yesterday and was able to recover it using the TMoblie update ROM.
Did you try it more than once? Mine worked the third try. Make sure you are in bootloader. It is weird, but once in a while flashing takes acouple times.
So before you try other things, try the TMoblie ROM again from here:
http://wiki.xda-developers.com/index.php?pagename=Herald_Upgrades
use 4.26.531.4
Click to expand...
Click to collapse
Thanks, I tried to do that all night but still the same old thing.
I don't understand. It is a T-Mobile Wing so why would the rom file keep saying its not the correct hardware??
Another weird thing now is starting to occur.
Now most time even the bootloader crashes or the splash screen freezes.
I am not sure but can it be that the bootloader itself somehow is gone bad?
emielfellinger said:
I have a T-Mobile Wing for about 1,5 years now and up until the other week it worked great. For some reason it only show the T-Mobile flash screen and does not boot anymore.
I tried to flash it with the latest RUU rom but every single rom i try to flash keeps saying that its not the correct model ID.
Since it hardly ever boots WM6 anymore i try to flash it from the bootloader. (turn on and hold cam key)
I booted good once and i managed to get the following info,
Device Name: HTC_p4350
Rom version: 4.12.405.1 WWE
Rom date: 04/09/07
Radio version: 02.83.90
Protocol: 4.1.13.37
ExtRom version: 4.12.405.101
Model No: HERA120
Platform: PocketPC
IPL: 4.10.0002
SPL: 4.10.0000
Can anybody tell me which rom i should try to use??
So far i have had no luck at all.
I tried the following ones without success,
TMo_Wing_RUU_Update_4.26.531.4
RUU_Herald_HTC_WWE_5.4.405.1_4.1.13.34_02.79.90_Ship
RUU_Atlas_TMO_US_4[1].10.531.3_4.1.13.37_02.83.90_Ship
Click to expand...
Click to collapse
1. How long does it stay on the screen ?
2. do you have it plugged up to pc when booting? - unplug the usb cord.
3. if you are flashing to another rom, try hardspl first - there is a thread with instructions on how to do it.
4. when flashing try using flashcenter.
robpet2 said:
1. How long does it stay on the screen ?
2. do you have it plugged up to pc when booting? - unplug the usb cord.
3. if you are flashing to another rom, try hardspl first - there is a thread with instructions on how to do it.
4. when flashing try using flashcenter.
Click to expand...
Click to collapse
*Quick note: Use FlashCenter if not HardSPL'd
Use ROM Update Utility (RUU) if HardSPL'd
robpet2 said:
1. How long does it stay on the screen ?
2. do you have it plugged up to pc when booting? - unplug the usb cord.
3. if you are flashing to another rom, try hardspl first - there is a thread with instructions on how to do it.
4. when flashing try using flashcenter.
Click to expand...
Click to collapse
Thanks,
1: The bootloader screen comes up and then the screen goes slowly white
This takes anywere from 3 to 10 second for it to happen. Other times the T-Mobile flash screen comes up and then it crashes or just stays in the flash screen until the bat dies.
2: plugged or unplugged to the computer for the crashing doesn't matter.
3: Thanks i'll look for that thread and use that
4: I'm gonna use flashcenter tonight.
I tripped over my usb cable while flashing an official orange rom + radio version a few months ago, and bricked my trinity. Left it on a shelf for ages & decided to try to revive it a few days ago.
The problem was that the thing kept hanging after the splash screen, all the backlights would go on and it would hang. I managed to splxploit it to get hardspl back on there (olipro 1.3) & successfully flashed a few OS roms from here but it still hung on the (now different) splash screen. Realised that the 'No GSM' thing was a killer, so tried reflashing a few radio versions, and that worked fine as far as the flash was concerned through USB / HSPL.
However, it still says 'No GSM' and hangs at boot. Any ideas? I've run all the tasks from mtty with spl-1.30lipro, the CID shows the HTC SuperCID(hex) etc successfuly, and it formats the OS portion successfuly. Task 2a, like with others, just returns a new prompt after a second or so.
I've got radio 1.56.70.11 on there apparently. It still says 'No GSM', although this goes away a lot quicker now, whereas before it would hang with that on the screen...
Help?? Should I throw it in the bin?
Thanks a lot, any help is much appreciated...
Nik
you've killed the radio BL in that case, bad timing on your part, sadly it's unrecoverable.
the only fix is desoldering the radio chip and soldering a new one in.
Have you tried whith the version 1.20? The version 1.30 gives some trouble flashing the radio
same problem...no way for me in this moment!
do you solve?
flash with hard-spl 1.20 ou crash'n'proof... then try again... it works with me
serbington said:
I tripped over my usb cable while flashing an official orange rom + radio version a few months ago, and bricked my trinity. Left it on a shelf for ages & decided to try to revive it a few days ago.
The problem was that the thing kept hanging after the splash screen, all the backlights would go on and it would hang. I managed to splxploit it to get hardspl back on there (olipro 1.3) & successfully flashed a few OS roms from here but it still hung on the (now different) splash screen. Realised that the 'No GSM' thing was a killer, so tried reflashing a few radio versions, and that worked fine as far as the flash was concerned through USB / HSPL.
However, it still says 'No GSM' and hangs at boot. Any ideas? I've run all the tasks from mtty with spl-1.30lipro, the CID shows the HTC SuperCID(hex) etc successfuly, and it formats the OS portion successfuly. Task 2a, like with others, just returns a new prompt after a second or so.
I've got radio 1.56.70.11 on there apparently. It still says 'No GSM', although this goes away a lot quicker now, whereas before it would hang with that on the screen...
Help?? Should I throw it in the bin?
Thanks a lot, any help is much appreciated...
Nik
Click to expand...
Click to collapse
Definately, don't throw it away. It's still worth $$$. A lot of people can use it for parts if you don't get it working. Offer it up for sale on here if that's the case.
Olipro said:
you've killed the radio BL in that case, bad timing on your part, sadly it's unrecoverable.
the only fix is desoldering the radio chip and soldering a new one in.
Click to expand...
Click to collapse
hi you know radio bl? any schematic to know.. im curios whats does it look like,?
Well. Last night I tried to unlock my Kaiser. Today something has broke bigtime
I followed the instructions for unlocking it from Olipro. However, I couldn't get it to go past the "SPL 1.93" on the screen or past the Tricolour. It wouldn't pass that stage and thus wouldn't go to Stage 2, and onwards. So ended up at another thread. It was the white screen one. I've managed to download and load JumpSPL1.56-KAIS and JumpSPL1.93-KAIS and once that was done return to the initial instructions and unlock the phone.
It reported all was OK but I've not got another sim to test it in. All was well today but this afternoon a call went to voicemail. When I tried to retreive it, I heard the voice then it made a buzzing noise and cut off.
A couple of soft resets later and turning the network off then on and I get part of the voicemail again, but most the time no sound at all when making/recieiving calls.
I would update to a newer rom but I don't know which one it is.
The following information I have.
Operator Version: 24.328.1.610
ROM Version: 3.28.61.0 WWE
ROM Date: 05/02/08
Radio Version: 1.70 OliNex
Protocol Version: 25.65.30.04H
Under the battery it states this is a Kais130
The options I have would be to contact the service provider and give these details to get a replacement. However, I'm worried that they will notice that the Radio Version is wrong and thus charge me lots of money. Or just complain more. If I can fix it myself I would like this option though because I do want it unlocked....
Soft resetting with the camera button in, gives me the following information:
Security Unlocked
Kais130 MFG
SPL-1.0.OliProf
CPLD-8
SERIAL (futher down).
Try flashing a new radio from here:
http://forum.xda-developers.com/showthread.php?t=393182
denco7 said:
Try flashing a new radio from here:
http://forum.xda-developers.com/showthread.php?t=393182
Click to expand...
Click to collapse
Yeah! But which one do I choose?
Oh, well, um, I'm trying for one now. Except it might take a while. I don't have a small microsd card, only the 4gb one, so I'm copying my data off before I format it to fix what I broke
Thanks for your help
Try 1.65.16.25 it is the one that originally came with your rom.
Hi guys,
I have a weird problem.
As of recently two days ago, my tilt won't take any flashes anymore. I believe with was caused by an action of mine which I tried flashing android from SD to NAND.
Here are the symptoms:
1) After a failed attempt at loading the Android Kernel, I installed the stock HTC ROM (Kaiser_HTC_ASIA_HK_WWE_3.34.721.2)
2) The stock rom flash worked, but any subsequent flash do not work
3) When trying to flash (either from Active Sync or SD Card) it gets stuck at 0%
Current state is as follows:
1) Phone boots up normally with stock rom
2) I can get into Bootloader mode no problem
3) When trying to flash it doesn't work
I have tried several steps in order to recover.
1) Tried to flash Stock rom again (Faillure)
2) Tried to flash HardSPL again (Faillure)
3) Tried MTTY 1.42 (Don't know if Success or Faillure) - I have attached the screenshot below
I have been successful in flashing multiple custom ROMs before, but idiot me wanted to try the android and now I messed my phone up. I guess it's true what they say: "If it ain't broke, don't fix it!"
Anyways...
So it seems to me, the connection is getting done but nothing wants to be pushed.
Here are my credentials:
PC:
XP Service Pack 2
Phone:
ROM Version: 3.34.721.2WWE
ROM Date: 09/30/08
Radio Version: 1.70.19.09
Protocol Version: 25.83.40.02H
HardSPL 3.34
So my question is, do you guys know how to get my Kaiser working again?
Do you recommend in attempting Android on Kaiser again or leave it be?
Any help is greatly appreciated in clarifying this out.
Dave.
Sorry for some reason I cannot post link to images. Does anyone know how to do this as well?
tsiftis21 said:
Sorry for some reason I cannot post link to images. Does anyone know how to do this as well?
Click to expand...
Click to collapse
You can just dont put http or wrap it in code and it's due to limitation on accounts to prohibit spam untill you reach a ceratain ammount of posts.
Screenshots
Thank you for the tip!
Code:
[IMG]http://a.imageshack.us/img806/7494/clipboard01ytn.jpg[/IMG]
[IMG]http://a.imageshack.us/img412/3866/clipboard02ml.jpg[/IMG]
[IMG]http://a.imageshack.us/img192/6405/clipboard03bx.jpg[/IMG]
[IMG]http://a.imageshack.us/img809/4079/clipboard04r.jpg[/IMG]
[IMG]http://a.imageshack.us/img835/3858/clipboard05nr.jpg[/IMG]
tsiftis21 said:
Thank you for the tip!
Code:
[IMG]http://a.imageshack.us/img806/7494/clipboard01ytn.jpg[/IMG]
[IMG]http://a.imageshack.us/img412/3866/clipboard02ml.jpg[/IMG]
[IMG]http://a.imageshack.us/img192/6405/clipboard03bx.jpg[/IMG]
[IMG]http://a.imageshack.us/img809/4079/clipboard04r.jpg[/IMG]
[IMG]http://a.imageshack.us/img835/3858/clipboard05nr.jpg[/IMG]
Click to expand...
Click to collapse
remember to take out your sim and sd card while flashing.
Mr. Clown said:
remember to take out your sim and sd card while flashing.
Click to expand...
Click to collapse
I had tried without the sd card, but I had forgotten to take out the sim card.
I tried without the SIM card and the same result is present. Won't go past 0%.
Any other ideas?
Does any one have any ideas how I can get my tilt up and running again? Any help would be greatly appreciated.
Thank you
I get the same issue...
Word for word, the same as this.
Operator 24.328.1.610
ROM Version 3.28.61.0 WWE
Date 05/02/08
Radio 1.55.16.25
Protocol 25.83.40.02
I've tried several PCs, ActiveSync doesn't work at all, Windows Mobile Device does.
SPL 3-27 is on the phone but I've tried running the others without success. I get up to 17% on any ROM if using JumpSPL1.93-KAIS.exe but that's about it.
This is a work phone which is on the Orange UK network (corporate contract), it's playing silly beggars (not ringing when someone phones, but helpfully telling me I've had a missed call).
According to Orange the only thing they'll do is swap it like for like... but I'm 99% certain the problem is down to the ANCIENT firmware on the phone and Orange have confirmed they've got no plans to update it.
tstaddon said:
Word for word, the same as this.
Operator 24.328.1.610
ROM Version 3.28.61.0 WWE
Date 05/02/08
Radio 1.55.16.25
Protocol 25.83.40.02
I've tried several PCs, ActiveSync doesn't work at all, Windows Mobile Device does.
SPL 3-27 is on the phone but I've tried running the others without success. I get up to 17% on any ROM if using JumpSPL1.93-KAIS.exe but that's about it.
This is a work phone which is on the Orange UK network (corporate contract), it's playing silly beggars (not ringing when someone phones, but helpfully telling me I've had a missed call).
According to Orange the only thing they'll do is swap it like for like... but I'm 99% certain the problem is down to the ANCIENT firmware on the phone and Orange have confirmed they've got no plans to update it.
Click to expand...
Click to collapse
I had this on my tp.
My usb was dying out, i ended up switching my tp with the one of my brother cuz my brother got a galaxy S.
Try if active sync works properly and keeps connected for 15 mins or more.
My connection kept getting lost untill eventually no pc would be able to reconize my phone.
So my problem is - I put android on my htc tytn II and it worked (well kinda) but anyway I decided to switch back to Windows Mobile...
I installed 1.27.x.x radio , found a Windows Mobile 6 ROM and put (Like in the instructions ) Kaisimg.nbh(renamed from ruu_signed.nbh) and Kaisdiag.nbh to my SD card and then started flashing... It flashed smth,rebooted automatically and started booting android again...
Then I hold again camera button + power+ reset and since then when I put EVERY .nbh file on my sd card and try to flash it it STUCK on "Loading.." If I try to flash it with USB It stays at 0%.
The only exeption is if I try to flash from USB the rom that I tried to flash before from my sd card.. then it starts 0%..1% and reboot the phone...
P.S: Please help me...I think my device is not Broken but I dont know what should I do to fix it...
To flash back to WM from android put your kaiser into bootloader (multi colored screen) Then connect to usb. Download any WM build that is recent (I suggest Phoenix 3 for this, you can flash whatever you want later). After you download it open and run the included RUU that came with it and it will flash it on there.
hmm, I also had experienced the similar problem on my 1st time flashing back to WinMo.
When you are trying to flash via USB cable and the process stopped at 1% I guess there is also a message about "Invalid vender ID" right?
and if the text in your bootloader (tricolor screen) doesn't mention anything about hard such as "3.29.0000" (not "3.29.hard")
then
you've lost your hard SPL that's why you cant flash any .nbh to your phone.
I had managed to solve this problem by flashing stock WM rom for kaiser. The rom also has to be suitable for your phone, I mean if your kaiser is originally from France, then use French kaiser stock rom. Or if you are using AT&T Tilt use kaiser cingular stock rom.
you can find the list of shipped roms for kaiser here :
http://shipped-roms.com/shipped/Kaiser/
If you still have the "invalid vender ID" error message, try another stock ROM.
Thanks man you're my hero! I though I lost my phone.. anyway i bought new one - Nokia 2730 Classic but Ill sell the kaiser...
Thanks Anyway ... you're god!
Have the same problem...
Firstly, I'd like to point that the reason for the hard SPL getting overwritten by an original SPL is NOT HAVING UPDATED HARDSPL to a newer version that prevents accidental overwrite. This is instructed in the previous steps before actually installing Android. That was my mistake (I had HardSPL 1.0 OliPof), and now I can't flash no rom to my Kaiser (which thankfully works quite well in Android).
What happens (please correct me if I'm wrong) is that "KAISDIAG.NBH" is a modified, standalone hardSPL that will flash to the phone the SPL that comes with the "KAISIMG.NBH" you put in your SD card with "KAISDIAG.NBH"). In my case, I used the WinMo 6.1 spanish version 3.29.412.0, which, resulted in my phone being flashed with the original SPL 3.29.
Now, it seems many users have fixed this locating the correct stock rom and flashing it in their Kaisers. But to others, like myself, nothing seems to work. I believe that this is because we not only need a stock rom for our specific Kaiser model, but also it has to be compatible with the SPL that accidentally got installed in the phone. The problem is what if such rom doesn't even exists?
I'm really thankfull for all I learned by reading the forums (and from my mistakes ) and I know I'm in no position to make requests, but here goes what I think could help the users like myself to fix this, if posible:
1) Guide to identify what model of Kaiser we have (maybe it's already there, I just couldn't find it)
2) Complete list (or lists) of stock roms (There are some around, those are easy to find I think, but it doesn't hurt to share different sources)
3) Something like a JumpSPL for Android would be more than awesome...
Thanks in advance to everybody, sorry for my own stupidity . Any idea or help would be much appreciated,
Daniel
hmm, I'm not sure if it has to be compatible with the SPL.
In my case, I was flashing a very old WWE stock rom which has original SPL 1.56.
I also had been very desperate because any stock rom I found seems doesn't work and I even didn't know where originally my kaiser came from because I get it from my uncle. So I tried to flash any WWE stock rom I could found but nothing works. I read from Wikipedia that based on my phone model (Kais100), this model was only sold as AT&T tilt for US. But the problem is my phone is HTC branded, not AT&T tilt. Well, based on this information I also tried to flash some cingular stock rom but the result was just the same.
After contacting HTC Customer care, I know more info about my phone. They told me that based on my phone product ID, my kaiser was originally shipped for US, but unfortunately they can't provide me stock rom for my phone model. So I searched myself but this time I had better objective : to search HTC branded rom but for US.
finally, after days of search. I've found the rom that is suitable for my phone. Its called HTC WWE Brightpoint US which has original SPL 3.29 at the bottom of the list on the website I told you on my previous post.
few weeks ago I also accidentally overwrite my HardSPL again, but this time I did it with the stock ROM which has original SPL 3.29. But this problem also solved by flashing the stock ROM I've found before via USB cable.
So, I guess it has nothing to do with spl version.
Keep tying don't give up.
Update: Step 1 completed! YAY
Using the serial number and some obscure google searching, I came to the conclusion my KAIS130 is australian. Cheers, mate!
I verified this by being able to download stock roms from the australian HTC site with my Kaiser serial number. But at the moment of writing this, have downloaded two roms and no luck yet. 5 minutes remaining for the third one... Wish me luck...
Daniel.
Well... Now what?
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
cuartetoraro said:
Tried all four rom-like thingies I could download on the HTC page, all of them returning error 294...
Now what? try to somehow extract the .nbhs from the exes and and use customRUU.exe? Try to flash from SD card?
Please help... Any ideas... I really want to get rid from that original SPL3.29.0000 It's evil!!! I think it won't never let me flash again.
Thanks,
Daniel
Click to expand...
Click to collapse
sorry to hear that..
well, extract the .nbh from exe and flash it via sd card is the method that made me overwrite my hard SPL in the first place.
hmm, did your phone comes with operator brand, such as three or something?
-Rif- said:
sorry to hear that..
hmm, did your phone comes with operator brand, such as three or something?
Click to expand...
Click to collapse
No, it's HTC unbranded. Now, something strange here: the label behind the battery has the serial number: HT830GB06075 and the P/N (guess it's part number) :99HCY194-00, but to the left of the camera, another label with the part number: 36H00563-00M and below says DATE:061107(TB02)/US.
I don't know if that's normal, but it caught my atention because my phone seems to have been dissasembled (little label over screw is teared). Maybe my Kaiser isn't Australian after all...