Hi.
I have not posted much on this site, yet I have used it plenty of times. And first off I have to say "Thank you oh so very much" to everybody who frequent this site. Most of all I would like to thank the developers and rest of the crew that helps users on a daily basis.
I've had plenty of phones the last few years: 9090, 9100, Tytn and now Tytn II - all of which have been flashed - successfully I might add - with software and aid from you guys. (Ok, so my Tytn nearly ended up as a paperweight, but with some fancy maneuvers using the CE SDK from Microsoft I was able to use it as a PDA again)
Now, I am stuck. Really stuck. (Not saying I'm not to blame, but I am still stuck)
I've got a Tytn II (The P4550 HTC Kaiser 120 I believe). A few weeks back I flashed this with Alex's Home ROM (http://wiki.xda-developers.com/index.php?pagename=Alex's ROMs). At the time I was running Radio 1.27.12.11, and continued to use it after the Alex flash.
That worked perfectly.
But being interested in always trying new stuff I yesterday decided to flash Alex.v5.WM61.HTC.302.UltraClean.ROM.beta2. And it really went bad.
I studied up on many postings (obviously not enough) and started the process:
#1: Hooked up the pda to my computer
#2: HardSPL v1
#3: Tri-Color mode and activesync grey
#4: Started the upgrade with KaiserCustomRUU.exe
Everything went smoothly until it hit 99% - there it stuck and the program ended with a communication error. My computer runs Vista (yes, I know. I wont even consider flashing another phone using Vista), but it has worked flawlessly 25-30 times before.
Anyways, what happened when I tried to recover was that the phone went into tri-color mode. Needless to say it was unable to recover. After much back and forth I reinstalled an old laptop with XP (as mtty does not work on Vista) and was able to boot it back in to the OS using a walk trough from this site - cudos to Laurentius26 for the post)
Anyways - it came back. But since it failed the flash I tried it again to make sure it finished properly. What I did was flash back the Alex Home ROM I had in the first place - that worked. Then I flashed back the 1.27.12.11 Radio ROM - which failed - seriously.
It hung on 17% and when reset it would only boot to tri-color. And this is where I am now.
Every time the phone resets it boots to tri-color. I've done and redone the mtty (with and without the task 28), but it stops in tri-color mode. If I at that point hook it up to mtty and issue the boot command it will boot properly, but thats kinda annoying - having to carry with me a XP laptop for each time I have to reset the phone. (Ive also tried the set 14 0 when the phone is in this state, but it will still only boot to tri-color)
So - what now?
I've tried flashing the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship, but it stops with 294 - invalid vendor id. I've tried flashing the same ROM with HardSPL installed - no vender id error but it fails at 16%.
In desperation I've tried HTC_Kaiser_NL_ROM_1.56.404.6_Radio_22.45.88.07_1.27.12.17_Ship, but this also fails at 16%.
I've studied many a post on this site, but have so far been unable to recover from this error.
Is there any hope of regain the much needed functionality of normal booting?
Hopefully there is.
Thanks in advance.
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Most definetly.
These were also posted by e-men in another topic this morning so I am currently installing Windows XP on a computer at work to try this.
Will report back.
Laurentius26 said:
Can you try these?
http://forum.xda-developers.com/showthread.php?t=371154
New commands for MTTY.
Regards,
Leo
Click to expand...
Click to collapse
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?
Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
ulfthomas said:
Woohoo!!!
XDA wins again.
The proper commands for the mtty worked like a charm.
Thank you kindly Leo, this was much appreciated.
Now for a question if you have the time: Since I started this process yesterday I have not been able to flash a Radio rom properly. It stops on 17% or 99% and quits with communication error. Any ideas?
And can I trust that my phone now works?
Click to expand...
Click to collapse
WM6.0 and WM6.1 radio's are different, they are not compatible!
So be carefull which radio version you are flashing
Info about radio versions:
http://forum.xda-developers.com/showthread.php?t=349375
Cheers,
Laurentius26 said:
Cool...., thank you
Would you like to give this a try as well maybe?
http://forum.xda-developers.com/showthread.php?t=366014
I never tried to flash a seperate radio ROM, I'm a 'chief de cuisine' so I cook it in
Cheers,
Click to expand...
Click to collapse
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?
This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
ulfthomas said:
But of course - now that I know how to reset.
One comment: I absolutely love the Palm SMS program added by Alex in his rom. You know if this is manually installable?
Click to expand...
Click to collapse
Laurentius26 said:
This is threaded SMS isn't?
That's default in WM6.1.
But if it's a seperate program there must be a cab out there.
I will have a look if it's that good you say!
Cheers,
Leo
Click to expand...
Click to collapse
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
ulfthomas said:
Well, good is subjective ... but I love it.
As for the updating: halted on 16% - communication error.
*Looks around - "Where's my mtty"
How can I get pass these updating issues?
Click to expand...
Click to collapse
Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
And all good tips Leo.
OS: Windows XP SP2. Freshly installed. Only Activesync 4.5 added.
HTC: Is orignial. Patched a few times using HardSPL
Original rom: As mentioned above I've tried a couple of them, but both ending in invalid vender id.
And no usb hub present.
Another comment - the flashing done today and yesterday has been done from two different xp computers - but with same result.
Laurentius26 said:
Which OS do you have on your desktop?
Do you have an original branded HTC device?
Try to flash a factory (shipped, not cooked) rom first!
Don't use a usb hub between your device and the pc, but use a straight connection.
See if there are applications running on your desktop.
Disable your Firewall for example...
And please take your storage card out.
Some tips....
Click to expand...
Click to collapse
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.
I'm going to upload a shipped ROM for you, this one if you didn't try it yet?
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship
Another question... did you use Custom RUU with ROM update?
http://forum.xda-developers.com/showthread.php?t=334890
ulfthomas said:
hehe... really? Remove my beloved SD card? Of course - always do.
No need for firewall as there are no nic's. And also no applications.
Click to expand...
Click to collapse
Yup - that one has been tested - fails with invalid vender id.
Also tried flashing that rom with HardSPL - comm. error.
And no, I have not tried the Custom RUU. Will for sure try that now.
The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?
Yes... try with another shipped ROM please?
ulfthomas said:
The Custom RUU is the same file that is included with your 6.1 Rom isn't it? If so I have used it with your ROM.
Do you think I should try it with another?
Click to expand...
Click to collapse
Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.
Use one more time MTTY, clear all FATS and I've send you a PM.
ulfthomas said:
Tried custom ruu with Radio 1.27.12.17.
Same results as other flashes - halts at 95%.
Seems like OS flashing hangs at 17% and Radio at 95%.
Click to expand...
Click to collapse
If you're getting an invalid vendor id it sounds like your hardspl or superCID isn't working correctly. Before going any further it's probably best to go to your bootloader screen and check that hardspl is still installed.
After that, I'd try flashing from the SD card.
Good point ach2, but when launching HardSPL and starting the update it lists the correct data on the bootscreen (Jumpspl or something equivavlent to that)
Leo: Looking around xda I found an article about dumping the ROM from another device. In the same thread I found a link to dumped original ROM. I patched that and it worked like a charm.
My PDA came back to its original state.
After arriving home just now I thought I would give your ROM another go, but same result - stuck at 16% (With HardSPL and Custom RUU)
What can cause this?
Related
Hi there,
I have a MDA Vario (G4) from T-Mobile and after following this http://forum.xda-developers.com/showthread.php?t=297762 and this http://forum.xda-developers.com/showthread.php?t=293480
I was able to install Faria's ROM on my Wizard but now i'm having some problems:
1 - I still have to watch that ugly bootscreen
(by the way, are those version numbers "right"?)
2 - Every time i reboot it i get this error about sddaemon
Problem solved:
knwlsh said:
As far as the error - your item 2...
Use Total Commander to search for sddaemon and then delete the link that it finds - you don't need it
Click to expand...
Click to collapse
3 - I often get this error about TimeWizard.exe
4 - As you can see on the previous photo, the memory is running low and so I everytime i try to syncronize with ActiveSync 4.5 (Beta2) i get this
Can anyone help me on those?
Thx
(Forgot to say thank you to Faria and Mun_rus. So... Thanks a lot!)
Ok 1. Are you CID unlocked, cus if you are not then the rom may not take correctly. It would be better if you had IPL/SPL at 2.26
Download and downgrade to the USA T-Mobile 2.26 rom. (At work so no time to find this for you, if you have not got it by the imte i get home i will update with a link)
Then try upgrading again to the WM6 rom, you may find that will sort all your problems!
The rom you should be able to find
HTML:
http://www.t-mobileapps.com/downloadcenter/Software_List.cfm?selDevice=24
Did you flash with shell tool? I think that you have no extended rom flashed, only OS.
As far as the error - your item 2...
Use Total Commander to search for sddaemon and then delete the link that it finds - you don't need it
funman said:
Ok 1. Are you CID unlocked, cus if you are not then the rom may not take correctly. It would be better if you had IPL/SPL at 2.26
Download and downgrade to the USA T-Mobile 2.26 rom. (At work so no time to find this for you, if you have not got it by the imte i get home i will update with a link)
Then try upgrading again to the WM6 rom, you may find that will sort all your problems!
The rom you should be able to find
HTML:
http://www.t-mobileapps.com/downloadcenter/Software_List.cfm?selDevice=24
Click to expand...
Click to collapse
DON'T use the 2.26 rom.... u've got a G4 and can't update IPL/SPL!
I downloaded this ROM
http://www.t-mobileapps.com/downloadcenter/Software_Detail.cfm?ID=80
and tried to flash it but when it starts (the PPC screen turns red,green,blue) it gives me an error msg on the PC saying "ERROR [294]: INVALID VENDER ID"
(this PPC came from UK)
I tried to use the mun_rus How To with this ROM but apparently it stayed the same.
From the UK T-Mobile i can only find this http://www.tm-phonedownloads.com/download_manager_mda_vario.html
but i think this is what a I have now running.
Ideas???
-----------------------------------------------------------------------
As for the Extended Rom i followed this:
http://forum.xda-developers.com/showthread.php?p=1172768&highlight=extended+rom+g4#post1172768
but i will double check it the next time i flash my Wizard.
(deleted - the same as the above)
Problems Aswell
Sorry if this has been mentioned many atime before but my rom is like really slow sometimes and most of the time on the today screen only the time/date is shown and no other items. Also when turning on the device sometimes it doesnt get pass the boot screen (green one) and is resolved by taking the battery out which is annoying. Someone said by putting the orginal factory rom then installing farias rom then it will improve - tried that same thing. And outlook wont let me change email type from plain text to html.
Anybody Know???
seanmig said:
Tried this one:
http://www.t-mobileapps.com/downloadcenter/Software_Detail.cfm?ID=80
The PPC screen goes red, blue, green but then it gives me an error msg on the PC saying "WRONG ID VENDOR" or something similiar.
Click to expand...
Click to collapse
Missed my post or want a bricked device? You're CID-locked.... look here:
http://forum.xda-developers.com/showthread.php?t=298613
Actually I did miss you post.
Wizard still working
As for the link that you suggest it ends with de Mun_rus' HowTo and that was the one that i followed to flash Faria's Rom
--------------------------------------------------------------------------
knwlsh:
Sddaemon problem solved. At least it seams so...
Hey,
I just did the SAME upgrade you did and I am getting the same
timewizard.exe popup!
however, my rom upgrade went ok , about the only thing different is I restored a backup including my registry to get all my programs back.
I have EVERYTHING working on wm6 with faria except for the annoying
popup.
have you been able to get ride of it?
Jeff
jeffr said:
however, my rom upgrade went ok , about the only thing different is I restored a backup including my registry to get all my programs back.
Click to expand...
Click to collapse
Is that a WM5 backup you restored? WM6 has stuff in the registry in different places. You've probably added a bunch of keys that shouldn't be there, and in the wrong place.
Also, WM6 PIM database is different format. If you restored that, its likely thats been hosed too.
i JUST BOUGHT A NEW O2 EXEC, AND TRIED MY BEST TO UNLOCK cid AND SIM, O2 APPARENTLY SHIP THEM UNLOCKED, SO I TRIED AND IT WAS. TRIED TO cid UNLOCK BUT NO LUCK KEPT GIVING ERRORS. SO I BEGUN THE INSTALL CROSSBOW LATEST, AND IT THEN WAS STUCK ON O2 SPLASH SCREEN, TRIED TO REFLASH WITH THINGONASTRING, NOW ITS STUCK ON BOOTLOADER, SAYING V2.01 AT BOTTOM AND SERIAL OR USB (WHEN CONNECTED), I HAVE LOOKED AND TRIED ALL OPTIONS, I TRIED UNI_EXTBOOTLOADER, AND THE OTHER ONE WHEN I WAS STUCK IN SPLASH SCREEN. NOTHING IS WORKING, THEN I TRIED TO SEE IF I COULD INSTALL OFF CD WITH O2 EXEC, BUT CANNOT FIND RUU. THE ONLY WAY I CAN NOW GET INTO BOOTLOADER IS FIRAT ATTACHING THE USB CABLE THEN BOOTLOADING, I CANNOT DO IT WIHOUT USB CONNECTED, BUT IF I TOOK THE USB OUT AFTER I HAVE GOT IT INTO BOOTLOADER, IT STILL STAYS ON. WHEN I ALSO PRESS THE RESET WHILST USB CONNECTED, THE LIGHT ON O2 EXEC FLASHES RED EACH TIME PRESSED?
ANY HELP WOULD BE GRATEFULL.... COULD THIS BE VISTA??? AS THATS THE OS I USE.
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
vistar said:
Please help, this is supposed to be a christmas present... i just couldn't help myself!!!!
Click to expand...
Click to collapse
Hi vistar,
Hopefully, you will have it sorted out by Christmas!
Yes, it is Vista problem and you need to change the USB Vista driver in your PC to XP driver.
I don't mean changing the Windows Mobile Device Center to Active Sync 4.5!
But the USB drivers. Look here:
http://forum.xda-developers.com/showthread.php?t=313001
http://forum.xda-developers.com/showthread.php?t=291723
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader
I believe that the first post should solve your problem. If not try the others. Basically, in Device Manager of your PC, the USB driver should be the old XP driver dated 2004!
Any other year won't do you good!
Merry Christmas!
Happy New Year!
KOR!
It is highly recommended NOT to use Vista ... even with the proposed driver patch.
I have developed a Radio ROM issue because of this: http://forum.xda-developers.com/showthread.php?t=347375
If you are using Vista, it is highly recommended for you to use Virtualisation and install XP.
I have been using XP under VMware forever without problems as far as flashing my Qtek is concerned ... until my Vista mis-adventure that is. I know that VMWare is not free, but you may want to give http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx a try.
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
will try the threads above thanks, i have tried in vista, and also i use vmware too, with xp pro spâ. which seems to work better but get error ăđă, radio update error, i think i have wiped the radio??? as when the first screen comes up it says:
from,
Radio:
EXT Rom:
Bla bla:
to:
Radio: 2.?.??
EXT Rom: 2.2.??
Bla bla: 2.2.??
I cant remember what numbers came up, but it was blank at top and version numbers at bottom.
any help would be grateful
ok i got it to work , through vmware, i ran PsiDOC_WM5_20041_Taster, which worked think its WM̀ still but its back on, I want WM̉ though, i'll try again.. some advice wouldn't go a miss. thanks.
Note: If anyone has problems blame vista..... Good OS, Bad PDA Partner...
ok every rom i try fails with the following: Error 114, Radio Rom Upgrade error.
why is this??? i have looked through the wiki and forum, people have had this problem before, but no answers.
I have this when WM5 loads up,
1.09.00
42.42.p8
2.00.41 WWE
and bootloader v2.01 (G4)
just incase this info is needed.
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
vistar said:
thanks, i will leave it on WM5 till an answer is given, preferably before christmas...lol.
thanks guys for at least helping me.
Click to expand...
Click to collapse
If you have tried all the links I have given, you could have easily upgraded the ROM to Windows Mobile 6.
Read carefully, my above post #3.
Did you know that you could just flash the CE ROM (Main ROM), if the Radio is not flashing.
KOR!
KOR support center !!!
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
vistar said:
How do i Flash that alone? do i just remove the radio file from the WM6 folder and run RUU again??? just to confirm...
Thanks M8 much appreciated.
Click to expand...
Click to collapse
Read the four links, I have given you.
1. nk.nbf (CE ROM - Main ROM)
2. ms_.nbf (Extended ROM - Storage ROM)
3. radio_.nbf (Radio ROM)
If the ROM is in .exe format, than excute the ROM without hooking your universal to the PC. In the temporary folder, you will find all the files.
Read,
KOR!
sorry what i meant was how do i flash the files to the device??? i have all the files ready..
do i remove radio from folder then execute RRU? or do i use a different way?
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
vistar said:
Thanks for your support KOR!!!
the later worked perfectly on my G4 device, i ran the update without the device attached, put into bootloader, and found all files in temp directory, then removed the radio file. connected the bootloaded device, then ran the update, it worked straight away, only in xp/vmware though.
Thankyou..... I really mean that KOR..
Click to expand...
Click to collapse
Hi Vistar,
You are welcome. If you download the drivers from the first link in post #3, then you can use Vista without any problems to flash your device.
Just make sure that the driver is dated 2004 before flashing the device. Check the driver for the Portable Devices ->USB Disk in the Device Manager of your PC.
Best Regards,
KOR!
BTW, I did reply to your PM.
King of Rapture™ said:
I flash my two Universal at least once a day under Vista with no problems at all.
Flashing Radio, CE ROM and ExtROM with Vista hasn't created any problem for me.
Vista like XP automatically install latest update from Microsoft site, this update also includes drivers too.
Just before flashing make sure that your old 2004 driver is not changed to the latest 2006 or 2007 driver!
That's all folks,
KOR!
Click to expand...
Click to collapse
Perhaps that's because both your Unis are G3 - and mine is a G4.
So, I flashed Dutty's Windows Mobile 6.1 rom with no trouble. However, when I tried to install the radio, it only went to 95%. Additional tries resulted in it not even being able to start the process. It just stayed at 0%. (Is activesync suppose to be force-closed during the process?) I'm a total beginner, so any help is appreciated.
imzac said:
So, I flashed Dutty's Windows Mobile 6.1 rom with no trouble. However, when I tried to install the radio, it only went to 95%. Additional tries resulted in it not even being able to start the process. It just stayed at 0%. (Is activesync suppose to be force-closed during the process?) I'm a total beginner, so any help is appreciated.
Click to expand...
Click to collapse
Could you be more specified please:
Which ROM & Radio? There are quite a few radios as well as ROMS from Dutty.
People Read The Wiki Before Flashing It Tells You Everything!!!!
Radio: 1.27.14.09 Rom: Dutty's WM 6.1 5.2.19199 UC Compliant
imzac said:
Radio: 1.27.14.09 Rom: Dutty's WM 6.1 5.2.19199 UC Compliant
Click to expand...
Click to collapse
What radio version are you trying to flash? The 1.27.xx.xx listed above is a WM6 radio and it will not work with any 6.1 ROMs.
imzac said:
Radio: 1.27.14.09 Rom: Dutty's WM 6.1 5.2.19199 UC Compliant
Click to expand...
Click to collapse
Well, there is your first problem
No WM 6.1 ROM is compatible with a 1.27... radio.
In order for it to work, you MUST have a compatible 6.1 Radio.
That was the version I was trying to flash.
KAIS_Radinly_1.27.14.09_CustomRUU
So, I can fix it by finding the correct radio? I'm still having connection issues because of this forced ActiveSync close.
imzac said:
That was the version I was trying to flash.
KAIS_Radinly_1.27.14.09_CustomRUU
Click to expand...
Click to collapse
Will not work!
The Wiki will answer all your questions.
You will need a 1.58/1.64/1.65 radio.
kjb86 said:
Will not work!
The Wiki will answer all your questions.
You will need a 1.58/1.64/1.65 radio.
Click to expand...
Click to collapse
Thank for that answer. However, I see nothing concerning why phone isn't connecting correctly, which I think is the main problem.
imzac said:
Thank for that answer. However, I see nothing concerning why phone isn't connecting correctly, which I think is the main problem.
Click to expand...
Click to collapse
whats not connecting?
To my computer. Everytime it gets to the point where its "verifying information on your PDA phone" activesync closes out automatically. Then it says Error 264 and tells me to try again. Then activesync comes back. For any rom that I run. Now, because I'm the bootloader state, I can't connect to my computer initially like I did before. Does that matter?
Okay, a simple soft reset got it all the way to the percentage bar. However, it stays at zero and come up with that same connection message. Then, I have to go through the recovery process and nothing changes after that.
Sounds like you messed up. anyway dd you have hardspl installed should be question number 1 and if all else fails use jockys FrankenKaiser and totally reset your phone.
austinsnyc said:
Sounds like you messed up. anyway dd you have hardspl installed should be question number 1 and if all else fails use jockys FrankenKaiser and totally reset your phone.
Click to expand...
Click to collapse
it doesn't sound like he has hardspl installed if he is attempting to upgrade his radio and it is stuck at 95%.
What are my options then?
imzac said:
What are my options then?
Click to expand...
Click to collapse
Are you still stuck in bootloader mode?
Yes. Is my phone a paperweight now?
If you are stuck in bootloader then download the file I attached. Next, follow these steps:
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
After you follow these steps search for hardspl before you attempt to flash anything else you can brick your phone if you do not have hardspl installed. You're playing with fire right now messing with your device without reading. Hopefully this helps you.
here is hardspl for you. please read the attached instructions.
Actually use the kaiser-hardsplv1
I don't see WCEUSB001 in PORT. I stopped the sync processes.
Attached you find all you need to flash cooked ROMs on your Ozone (Cedar).
The sspl/hardspl are confirmed to work fine on the HTC Cedar platform (Ozone).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. For the Dash3G I have already developed a sspl/hardspl. Users of the S511 have to wait until I feel motivated ..
The packages contains a SSPL, HardSPL, patched ROM updater and the original Ozone SPL. The package is based on SPL v0.39
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Ozone HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
5. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Ozone cooked or original ROM.
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Awesome work JockyW.
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
Click to expand...
Click to collapse
Um... so most of this worked fine, and the screen is dark, and a generic htc driver got auto installed... and the Rom Utility popped up on my screen... But how do I get it to connect to activesync like this?
After my phone rebooted completely (following the ROM utility completing), I just re-enabled Allow USB connections and it seems to work fine.
No, so the rom update tool doesnt complete because ActiveSync doesnt work after the screen turns black...
Edit: and Im using XP (noticed ur not from the thumbnail...) idk if that matters or anything
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
forgot to remove my SIM card! Gonna try again, give me a few minutes
no, same problems. :sigh:
The bootloader is still locked in 0.39.0000, confirmed.
EDIT: I'm pretty sure all my problems are coming from x64 drivers. I'm going to try this again in Windows XP Mode. Congrads everyone who's succesfully flashed! Good work guys!
businesschild said:
forgot to remove my SIM card! Gonna try again, give me a few minutes
Click to expand...
Click to collapse
businesschild said:
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
Click to expand...
Click to collapse
businesschild said:
no, same problems. :sigh:
Click to expand...
Click to collapse
businesschild said:
The bootloader is still locked in 0.39.0000, confirmed.
Click to expand...
Click to collapse
Instead of replying to yourself, please use the edit button next time.
Anyways, if you run auto.bat, disable USB Connections after the screen turns black via ActiveSync. In your device manager (with the screen still black) look at your USB Devices. You should see a entry called HTC USB Sync. If you see that continue to flash. Seeing HTC USB Sync is a key step in this whole process.
Please read the testing/development thread for some good solid help. A bunch of us ran into the same issue you did. If you read all 4 pages you should be able to troubleshoot your problem: http://forum.xda-developers.com/showthread.php?t=550628
computerpro3 said:
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
Click to expand...
Click to collapse
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
ookba said:
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
Click to expand...
Click to collapse
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
computerpro3 said:
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
Click to expand...
Click to collapse
HERE HERE!
The stock ozone rom is crap, I would love to cook my own ROM!
BTW hardspl successfully flashed first try on my device. Totally painless. Excellent job.
Anyone with a Telus SNAP try this?
ariesq said:
Anyone with a Telus SNAP try this?
Click to expand...
Click to collapse
I think the Telus SNAP is a CEDAR as well. Uses the same CDMA network as Verizon. Dump your SPL and post it for JockyW to examine and give the tumbs up.
Also, dump your RAW files, upload and post in this thread if you can.
http://forum.xda-developers.com/showthread.php?t=540586
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
ookba said:
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
Click to expand...
Click to collapse
I agree. Just sent him a small donation. You're next ookba, but will have to wait until next paycheck.
Update: Small donation sent to you as well ookba. I'll just have to skip lunch tomorrow
P
How sure are you that Ozone is Cedar?
RUU_Chief_W_WM65_VERIZON_WWE_2.10.605.1T_Radio_612522_1.71.00WV_NV_MFG_VZW
looks like a chief to me, but I could be wrong, I would like to release a 6.5 kernal, but dont want to have wrong device.
Attached you find all you need to flash cooked ROMs on your HTC Snap 511 (Willow).
The sspl/hardspl are confirmed to work fine on the HTC Willow platform (HTC Snap 511).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC CEDAR platform (Ozone) is not supported. For the Dash3G and Ozone I have already developed a sspl/hardspl.
The packages contains a SSPL, HardSPL, patched ROM updater and the original Snap S511 SPL. The package is based on SPL v0.34
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Snap S511 HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.34.Hard")
5. to test the sspl and the hardspl you can flash a splash screen
Once the HardSPL is installed on your device you can flash any cooked or original ROM.
A donation for my work would be highly appreciated
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Donation
Donation has been sent. Thank you for this.
Good work!!!!
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
dougmwpsu said:
Thanks Jocky, sending you good vibes and tips!
Once we install the hardSLP on the sprint snap, which cooked roms can we use? Are we going to need one specially cooked for the snap 511?
Click to expand...
Click to collapse
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Black_V!per said:
Yes, ookba is waiting to get his own phone to get a ROM working... Donations really speed up that process
Should this be stickied like the last few? Maybe consolidate all into one?
Click to expand...
Click to collapse
Anyone care to donate their S511 to me for a week or so?
ookba said:
Anyone care to donate their S511 to me for a week or so?
Click to expand...
Click to collapse
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
dougmwpsu said:
Maybe the next week I'm on vacation... can the phone be service deactivated while you have it?
Click to expand...
Click to collapse
Sure it can. Where are you though?
ookba said:
Sure it can. Where are you though?
Click to expand...
Click to collapse
Raleigh, NC. My next vacation isn't till the week of Christmas though, so maybe someone else can step up in the meantime. I'll also be out of the office again for a week in the spring.
first off, thanks so much to Jocky and Ookba for all the work you guys do! but i'm having some issues. i've dont a lot of searching on here and i can't find a solution hopefully someone can help me. i can't get the hardspl to run successfully.
my bootloader screen shows this:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
i'm using windows 7 (through VMWare on my iMac), everything seems fine until the pop up on the phone, i click the button (the not really a trackball button) and the screen goes black, i lose all connectivity through WMDC and the Rom Utility gets error 266.
If i don't click when the pop up shows on the phone, the Rom Utility will show and then the phone will go into the bootloader with USB written in the white area then i get the error 266 again.
of course there's no sim because it's a Sprint s511, and the sd card is always removed.
what can i do? i'd really love to get 6.5 on there, but i'm at a loss.
The fact that your running on a MAC with VMWare makes me think the issue could be in the connection...
Im not even sure if Win7 works, i could be wrong however. You wouldnt happen to know of anyone that has a WinXP machine would you?
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
I applied the HardSPL to my snap using Windows 7 and everything went well
robconway said:
I did try in vmware with XP and Activesync, but it did the same things. I have a Dell that I was gonna make a hackintosh, but I'm gonna throw xp on it and try using that machine. I was thinking it was the vmware too, i guess i just wanted one of you guys (you know, the one's with a clue! LOL) to confirm.
Click to expand...
Click to collapse
Thats what it sounds like... Good to know it works on Win7 though SPIK3.
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
robconway said:
Thanks Black_V!per for responding and all. I did finally get it going! I set up the dell with XP and it actually didn't work at first. I had originally unRARed the package on the iMac and just copied the unarchived folder over to the XP machine, thinking it would save me a download, but it didn't work. So i just dl'd an RAR utility for windows and unpacked the RAR on the xp machine and it worked perfect. originally the Rom Updater said it couldn't find the nbh file. all's well! And i'm loving 6.5!!
Thanks again Jocky and Ookba!!!
Click to expand...
Click to collapse
Must have corrupted during the download... Havent seen that since my 56k-days.
Glad to hear that!
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Jaymoon said:
First off, I appreciate everyone's hard work throughout this whole process.
Unfortunately I am running into a problem. The auto.bat is able to copy the JumpSPL file and the .nb file to my phone just fine. However once the Rom Update Utility starts the flashing process, the phone shuts off.
I did a hard reset to my phone, and went through the process again. The JumpSPL notice popped up on the screen, but then crashed when I hit OK. I know it crashed because the Windows Error Reporting popped up (which apparently I had disabled before I did the hard reset, so I never was able to tell if it was still running).
So then I manually ran the JumpSPL file. This time the memory box popped up, so I hit OK with the Jump Address at the default 0x00000000. It then asked which SPL file I wanted to use. I chose the .nb that was copied over. Then the Windows Error Reporting screen showed up again.
I'm not sure what is going on, but hopefully the details I just provided will allow someone to figure something out. Thanks.
BTW: My phone is a Sprint HTC Snap S511, and my splash screen is the same as the one posted before:
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B
Click to expand...
Click to collapse
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
SPIK3 said:
Is your phone applications unlocked? When I did mine it gave me a bunch of errors because it wasn't applications unlocked. Also make sure you remove your memory stick.
Click to expand...
Click to collapse
How would I go about checking this?
I remember on my Samsung Ace, before the 6.1 update, I had to install an "application unlocker" that allowed unsigned programs to install. Is this the same thing with the Snap? Also this is the Sprint version, so I don't have a Sim card, or anyway to typically "unlock" this phone.
EDIT: Ah, now I know what you mean. I found the SDA Application Unlock here: http://forum.xda-developers.com/showthread.php?t=563761
The Rom Update Utility finished successfully! Now to move on to the next step... Thank you SPIK3
No problem, glad I can help.