ahh crap... phone wont flash anymore - Touch HD Windows Mobile ROM Development

im having a huge issue here....
i updated my phone to "RUU_BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship.exe", that went well.
since the phone is provided with orange UK 'tweaks' i had to use USPL to get around the locks.
ok - so, USPL booted, i then ran the above official update.
sucessful flash - or so i thought.
phone reboots, hard reset, and then allow phone to boot. setup wm6.1 as normal and get to the GPS stage - the hardware com port refuses to stay on the com port i select, and just goes back to 'unselected'.
thus, tomtom will not find any gps devices.
so i try to go back and find another rom that will work correctly - i now cant get ANYTHING to flash - i boot to SPL, attempt to flash rom, and phone/flash utility both get as far as 0%. after a short while, the utility comes back to say no comms with the phone. i cant boot to USPL, flash with another rom or anything.
how do i fix this?

Can you get your HD into bootloader mode ?

Each time a new ROM update
you must perform the procedure again with USPL unlock

Now that makes sense i didnt read the post properly lol

Related

Updating radio - Disconnects From ActiveSync During SPL Mode

I have been trying to update my ROM lately with a new Radio and have been having one issue. Whenever I run the update utility, the screen will enter SPL Mode (all white) like it should, but when it enters SPL mode the activesync connection is lost, every time. I cannot get it connected again until I reboot the phone back into wm6, and then it connects to activesync just fine.
How can I get it to stay connected long enough for me to flash?
So to begin, when I want to update the radio, I should be able to update it in the same way I install a new ROM, correct? I use a SoftSPL file I found here and simply copy main file into that folder and then run start-SPL.
Anyone else experience this? It just seems to always disconnect and cause errors right before it updates the ROM.
The only thing that I can think of that could be causing it is the phone fell in some water for a couple seconds about a week ago. It's been drying out and seems to run ok again as of today. I was able to flash the ROM a couple times, so I know it's possible to flash. It took a couple of tries, but eventually did flash. However, I've tried about 10 times for the radio only (2.71.11) and it won't work.
Any ideas, other than it cannot be fixed due to water damage?
Note: I was just able to flash back to the cingular stock ROM (was using Jaguar 4.0). The stock ROM always seems to flash easily without difficulties - can unofficial ROMs not be flashed in the same manner? Just an .exe file that takes care of everything and never has activesync issues? It's flashing the stock ROM as I type, and it does not show the activesync connection is active. It was at first, but was lost (or appears so, anyways) as the flash began. The stock ROM is much easier to flash in my opinion and hasn't given me difficulties thus far, although other ROMs used to flash easily as well - not so much now.
Superman859 said:
I have been trying to update my ROM lately with a new Radio and have been having one issue. Whenever I run the update utility, the screen will enter SPL Mode (all white) like it should, but when it enters SPL mode the activesync connection is lost, every time. I cannot get it connected again until I reboot the phone back into wm6, and then it connects to activesync just fine.
How can I get it to stay connected long enough for me to flash?
So to begin, when I want to update the radio, I should be able to update it in the same way I install a new ROM, correct? I use a SoftSPL file I found here and simply copy main file into that folder and then run start-SPL.
Anyone else experience this? It just seems to always disconnect and cause errors right before it updates the ROM.
The only thing that I can think of that could be causing it is the phone fell in some water for a couple seconds about a week ago. It's been drying out and seems to run ok again as of today. I was able to flash the ROM a couple times, so I know it's possible to flash. It took a couple of tries, but eventually did flash. However, I've tried about 10 times for the radio only (2.71.11) and it won't work.
Any ideas, other than it cannot be fixed due to water damage?
Note: I was just able to flash back to the cingular stock ROM (was using Jaguar 4.0). The stock ROM always seems to flash easily without difficulties - can unofficial ROMs not be flashed in the same manner? Just an .exe file that takes care of everything and never has activesync issues? It's flashing the stock ROM as I type, and it does not show the activesync connection is active. It was at first, but was lost (or appears so, anyways) as the flash began. The stock ROM is much easier to flash in my opinion and hasn't given me difficulties thus far, although other ROMs used to flash easily as well - not so much now.
Click to expand...
Click to collapse
First,You don't have to flash Radio Rom using 'SoftSPL',its an EXE file,it'll flash straight like an official stock rom,as it doesn't contain any IPL/SPL in it,it won't effect the bootloaders and the phone,its safe to flash to any device,G3 or G4,just connect your phone with pc via usb cable and run the Ruu included in the Radio Rom,it'll start to upgrade.
Secondly,YES! official stock Roms are easy to flash,cuz it contains official G3/G4 IPL/SPL included in them,it doesn't require CID unlocking the phone,whereas,custom build wm6 Roms require the phone to be CID unlocked and doesn't include IPL/SPL in it,so a G4 device cannot be CID unlocked,therefore,using 'SoftSPL' or 'HardSPL',its tricked into temporarily CID unlocked status,but actually its not CID unlocked.Hope its clear now
zabardast_1 said:
First...
Secondly...
Click to expand...
Click to collapse
Man.. it is clear enough, but dude, you didn't tell how am I able to proceed with the ROM upgrade when the activesync issue occurs everytime I try to upgrade.
I am a total newbie on this and I am having the saame problem in here.

Freeze on boot screen

Hello,
Today my vibrator goes mad, so I decided to send my phone back (I still have the warranty).
In order to proceed, I have to put back the official SFR ROM, and luckily I found this link on the wiki : ftp://xda:[email protected]/Uploads/Trinity/SFR_S300+_ROM_French_1.23.163.2_Only_OS.rar
So I did a little backup of all my data, I take off the memory card, and I started the installation.
But at 9%, it bugs. Hopefully, the ROMUpdateUtility display a message that I have to put off and put in the USB cable, and retry the installation. Its seems that works, because the transfer was complete and the phone reboot automatically .
But when the phone reboot, it display the classical boot screen SFR Bonjour, show some numbers (M 05 - B 05 - D 1.23 - R 1.50.08.11 - G 32.83.7020.20h) and when this numbers disappear the phone freeze.
I've try to wait half an hour, but the SFR boot screen stay, and the phone didn't respond to anything (I've try to put the power cable, and the LED set on only if the phone is off). I have to put off the battery to turn off the phone.
If somebody could help me, please!
And excuse me if I made any mistake, english is not my native language.
I have the same issue......
I have the same issue, my SPVM700 just sits on the initial splash screen after I tried to re-flash it to the original Orange ROM [as I too had to return it for a warranty repair]. I used Mozzer's Orange ROM [http://forum.xda-developers.com/showthread.php?t=309959] to restore it - the procedure looked the same as with other ROMs I had successfully loaded but it was only when I tried to restore the official MNO ROM that my Trinity bricked.
I can access the bootloader screen [TRIN100 IPL-0.50, SPL-9.99CP] and can flash the device, where the progress bar always reaches 100% on the PC and the PDA and then the PDA automatically reboots, however, it does not advance past the splash screen.
I have tried the Hard-SPL fix [ http://forum.xda-developers.com/showthread.php?t=299659 ] and then re-flashed the device with other ROMs that I had tried previously [Schaps, AX3L, HTC Official WM5 P3600 ROM etc..] but still get no joy - is there something that I should have done prior to re-loading the original ROM that I have missed and is my Trinity now forever a brick?
you've presumably tried a hard reset? but it's not written above so i thought i'd just check.. (pressing two soft reset buttons and pushing the stylus in the reset hole?)
Yes I did try a hard reset even though I didn't expect much from it as I had just replaced the ROM [effectively wiping the ROM and replacing it with a different ROM] and none seemed to boot. Once the device has started booting up, the only way to switch it off is to disconnect the battery [and the only way to switch it back on is to soft reset] so I am guessing there is a hardware issue caused by returning the device to the Original MNO build as this was the ROM upgrade that trashed the device - other ROMs tested prior to this had loaded successfully.
Sorry to bring this back but since the link is in Behemot's sig, it is not resolved yet. Have you guys loaded SSPL before flashing? If you haven't, the OEM Rom won't boot with HardSPL. Try flashing another custom Rom and use this method before flashing the Shipped Rom.
Good luck.
ask ilos for original SFR rom or search for extenue SFR rom. or contact me by personal message and give me your mail i have the SFR ROM without radio ROM (you can get the radio on this forum)...
Sorry, I've forget to update this thread...
So, for me the only solution was to bring back the device to an SFR store (it is still under warranty).
I believed they would reproach me that the RADIO was not the original one or something like that, but no. They didn't make any remark and send my device back with an official SFR ROM.
The only thing is that they take more than a month instead of the traditional two weeks to fix it.
So all is ok for me.
I hope you will solve your problem

Can't upgrade/downgrade ROM using anything...

I recently updated to stock spl 15.000 (from OliNex's spl) to combat the green, fuzzy, screen problem on the new official ROM but nothing will update; I've tried:
-Going back to official ROM's, which results in 'Error: Invalid Vendor ID'
-Going back to OliNex, it just sits at 0% before timing out and going to a recovery console (which is useless)
-Downgrading/Ugrading to official and Dutty's ROM's using USPL
Any help to get back to OliNex would be great.
Thanks
+The phone still works but I can't upgrade it.
Yes i got there too. Drove me nuts...
To install Duttys 2.7 Xtreme Follow points 3 & 4 in this post - works great
http://forum.xda-developers.com/showthread.php?t=503225
or... if you want to get back to OliNex - run USPL then run HSPL to restore back to OliNex
solution
try flashing with sd card loaded the original firmware.
Cheesy95 said:
1. - Going back to official ROM's, which results in 'Error: Invalid Vendor ID'
2. - Going back to OliNex, it just sits at 0% before timing out and going to a recovery console (which is useless)
Click to expand...
Click to collapse
1. - I've encountered the Invalid Vendor ID error too. To work around this, you have to flash the official stockrom in the language you purchased your HD in. That worked for me.
2. - Did you connect your device with Activesync (or WMDC) before you started the HardSPLWrapper? Also you dont need to put the phone into Bootloader mode. Just plug your USB cable in and let it sync. If not sure: follow the instructions in the HardSPL thread.
It has to work, it did with me.
Grtz... Jeat
Thanks everyone. It's working now, I was doing it in bootloader mode 'cos ActiveSync failed me. But now it's up and running again, everything is back to normal, and I can go back to trying new, more awesome, ROM's I installed the latest official ROM and now I'm half-way through flashing Dutty's EXTREME 2.7. I'd still be stuck with the crap official version without your help Thanks again!

HTC Tytn ii not booting

My htc which is still default from factory freezes on start up. i have been advised that it needs a firmware upgrade but as i am unable to boot the phone up i am unable to upgrade the firmware. i am lost here i have been searching for hours to find a solution and can;t seem to find one so i thought i would ask you guys. it freezes on the screen smart mobility and doesn;t move from there.
Have you tryed to hard-reset?
To flash the original stock ROM via bootloader? as doesn't need to fully load os to flash.
i have tried to hard reset it now and it wont turn on now.
i got it to boot again after the hard reset but it did the same thing just froze on the smart mobility screen again. i had sent it in to be fixed but they wanted to charge me quite a bit to update the software and since i have 4 months till my contract is up i don;t want to pay it is there anyway i can give it the update whilst it is freezing during boot up
Try flash stock ROM via bootloader.
Camera button hold in press in stylus, stock rom "from wiki" now flash via usb or sd.
would you be able to suggest the best rom for me to use i have wm 6.1 the info it givews me is kais130 spl-3.29.0000 cpld-8 i have never done this before i just want to be sure i get the right one
You will need your carrier ROM as when flash will vendor check since not hard-spl'd.
thankyou so much for the help i was able to locate the correct rom and now my phone is working again you have been a great help
Glad you sorted, happy to help

Back from Android to WM6 problems

Hello everyone!
I recently installed Android Froyo 2.2 (Incubus26Jc's Super FroYo RLS15 All Language), following mainly this thread http://forum.xda-developers.com/newthread.php?do=newthread&f=602, and also reading many others, about hardspl etc.
Everything went perfect! The phone workes just fine, full functioning!
My problem is that, after deciding to go back to windows mobile for selling my phone, I followed these steps :
"Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH.
Place the SD into your Kaiser and hold the Power button and camera button down, then take your stylus and hit the reset button. Follow the instructions on the screen to flash your Kaiser. When the flashing is done you should be back to running Windows Mobile."
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Also, when I press the power button+camera button, for a new update flash, after the three colors screen(KAIS130, SPL-3.07.0000, CPLD-8), the message "Loading..." appears and stucks.
I guess, my phone no longer has hardspl, and there is no way to put it back, neither put back the signed rom, if there is no WM os????
Any help/suggestions???
Thank you very much, in advance
I suggest you follow the tutorial switch back to Windows Mobile by Dukenukemx ~ http://forum.xda-developers.com/showpost.php?p=6461906&postcount=1
looks like a really lost hardspl. Maybe this will help you get back to windows http://forum.xda-developers.com/wiki/index.php?title=Kaiser_stuck_at_bootloader
aris0602 said:
I downloaded the shipped rom RUU_signed_WWE_1.56.405.5_22.45.88.07_1.27.12.17 but the update process stopped at about 1/3, and the phone rebooted with Android OS.
Click to expand...
Click to collapse
One question:
What version radio was on the phone BEFORE attempting a WinMoBlows flash?
It looks like the shipped rom had the 1.27.12.17 radio included in the bundle and, if so, this would explain the error in flashing.
One thing to check would be at the bottom of "Settings" page, touch "About Phone". Towards the bottom you will see "Baseband Version". The numbers at the end are your radio version and should be the original radio numbers. If it says "1.27.12.17", you've found one problem...
I would say follow dukenukem's post and try to reflash HardSPL again.
I haven't run into this problem yet since I will probably never sell either of my Kaisers... lol.
same problem at my place...
installed android, about 2 month ago, wanted to switch back to win and couldnt do it that simple as say "Switching back is very easy. All you gotta do is download your favorite WinMO rom, and rename RUU_Signed.nbh to KAISimg.nbh and place it on your SD card along with KAISDIAG.NBH. " in Dukenukemx's tutorial.
I have tried everything putting on sd card many ROM's Hardspl's, then i found this on my pc RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88. 07_1.27.12.11_Ship when i try to flash via usb (manually enter bootloader and connect usb cable) it get to 1% and reboots and ond rom update software says ERROR [294] : INVALID VENDER ID and above Exit button says: VER4-KBKV5867-HUEbc568-KBKV58670...
and when i try same rom to flash via sd card it says
Loading...
Checking...
0028002
Not Allow
with any other it stay's at 0% on phone and nothing is showed, then on RUU says ERROR [262] : UPDATE ERROR and down is button Recovery, tried a lot's of times nothing...
Then i saw that you PoXFreak said to check radio in baseband mine is 1.65.17.56
any sugestions please?
Another user with problems...
Tried a return from android to windows mobile because of the random locks that were happening in android (also some other weirdnessess...)
Now when it is put a microSD with kaisimg or kaisdiag it goes into white loading screen and stay there...
(tried flashing Kaiser_HTC_ASIA_HK_WWE_3.34.721.2, that seemed to be the one who came with my phone)
The baseband message somebody talked above shows only "HTC"
When in tricolor bootloader the following is showed:
security unlocked
KAIS***
SPL-3.28.0000
CPLD-8
(Still gonna try updating it connected to the computer, seems like usb and serial dettection are working, for it will dettect the charger connection and start showing USB in the lower part of the screen, battery got very low overnight, still needing to charge it to really do some test)
_____________
Update:
Flashed ok through USB, just entered tricolor bootloaded, connected usb and executed the original rom installer.
hello everyone
I used to have this kind of problem.. my hard spl broke when i tried to flash a stock wm rom from android.
In my opinion, each stock roms comes with specific SPL, radio version, etc. It means that when you are trying to flash stock rom, you also flashing new SPL. the problem is, the new SPL broke your hard SPL so you won't be able to flash anything to your kaiser except your original stock rom which comes with your kaiser.
you can find some stock roms for kaiser here : http://shipped-roms.com
Since I'm only sure that my kaiser originaly comes with WWE version I almost tried all the WWE stock roms there, but my search ended when I flashed RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe, this rom works for my phone and it seems that only this rom didn't give me "invalid vender ID" message.
so, keep trying to find your original stock rom
and after you managed to flash your stock rom, don't forget to flash hard-SPL again if you still want to mess around with your kaiser.
good luck
Another way to do it, albeit a little tougher, would be to use Oli's NBH tool and remove the SPL and radio from a stock rom. That way you get to keep the radio and SPL while flashing a stock rom.
Keep in mind that some WM roms only like certain radio versions, and you may end up having to flash an older (or newer) radio to find what works best.

Categories

Resources