Database Info

Serious Help Needed Flashing Custom ROMS, Please Help!!

I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.

kjones2k1 said:
I am in dire need of some help when it comes to flashing custom ROMs. It appears that I can no longer flash custom ROMs. I can successfully flash the official 1.62 ROM from HTC website, the dumped TILT ROM, the Kaiser dumped ROM, and the WM6.1 WWE 3.03.405.0_radio_sign_25.70.40.02_1.64.06.04, but any other ROM I can’t. Let me explain my meaning of not being able to flash a ROM. Once it flashes 100% and reboots, when the “Tap the screen to begin to set up your windows-mobile device” is supposed to be displayed, all I get is a blank white screen. If I touch my stylus to the screen the text shows up, but none of the colored pictures that suppose to be in the back ground. Every section of the setup just displays the text no background images. Even my today screen won’t display any background images.
Does anyone have any information on this? I’ve abused this thread http://forum.xda-developers.com/showthread.php?t=314615 like a cheap dirty whore trying to find a solution, but no avail. Any help will be GREATLY appreciated.
Click to expand...
Click to collapse
are you using 6.1 radios or the 6.0 radios?

P1Tater said:
are you using 6.1 radios or the 6.0 radios?
Click to expand...
Click to collapse
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09

kjones2k1 said:
For each ROM, when ever I flashed, it changed my radio. For instance Alex's 1.62 rom, when I flashed his ROM, it already to changed my radio to the need radio to 1.27.14.09
Click to expand...
Click to collapse
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.

P1Tater said:
some come with radios, but most dont. You have to be sure if you need an AT$T specific radio or not.
Click to expand...
Click to collapse
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?

kjones2k1 said:
When I was running the WM6.1 3.03 ROM with radio 1.64.X.X, I flashed to Alex 1.62 ROM and my radio changed to 1.27.X.X. Didn't this flash change my radio?
Click to expand...
Click to collapse
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.

P1Tater said:
yes, if those are the only two flashes you have done, then it sounds like you might have had the unfortunate luck of having a bad flash. Reflash again and see what happens.
Edit:
Did you also do a hard reset at the "tap here to begin screen alingment" screen? If not, always do so.
Click to expand...
Click to collapse
I always hard reset when flashing new roms (learned alot in the kasier wiki). This is what I'm trying. Flashing to ATT 1.62 (Offical from HTC website) > manually flashing to 1.27.04.09 radio > Flashing to Alex's 1.62 ROM

Anyone else have any suggestions?

I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.

GSLEON3 said:
I have a few ideas that I think may help. PM me when you get a moment. It may Late saturday or sunday till I can get back to you, but I need to know a coupl of things. So, if you're still stuck, let me know.
Click to expand...
Click to collapse
PM sent

Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)

_Alex_ said:
Check out the ROM Upgrading section of the Kaiser wiki under 'Troubleshooting' to learn how to enter bootloader mode.
Assuming that you installed HardSPL the first time you flashed, once you've booted into this mode, reconnect your device to your USB cable and flash another ROM.
For those who haven't looked at the Kaiser wiki in a while, I've completely revamped it w/TOC pages to make it alot easier to use (shameless plug)
Click to expand...
Click to collapse
?? This is not my issue. I'm not a complete beginner when it comes to flashing. Ever since I flashed the WM6.1 3.03 ROM I haven't been able to flash a custom ROM without having an image problem. I can still flash OEM type ROMS without the image issue, but not custom ROMS. I have the problem with images once a custom ROM has been flashed. If more clarification of problem is needed, I am will to give it.

This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!

_Alex_ said:
This may be extreme and largely untested, but have you tried 'clear storage' on the WM6.1 ROMs and chosen 'delete NAND' (or something to that effect)?
That should wipe your ROM memory clean, although I'm not sure if that would help or hinder your cause, as I haven't heard anyone try it yet...
Hope this helps!
Click to expand...
Click to collapse
No, I haven't tried, but I guess I'll give it try when I get back in town on thursday.

Sorry I had to bug out....
Alex, his problem is a little different than a RUUBNH error that's commonly seen. I tried walking him through a CE reset using MTTY & he can't even communicate with his bootloader. MTTY wouldn't establish a USB connection. I agree that formating the Nand may help, but I think you really should also try & reflash hardspl as well. I suggest the new version with AT command support. I have seen a few funky hardspl flashes that inhibit communication, although rare.
I didn't forget you though Kjones, & I'm trying to duplicate your problem & find an answer.

Rom trouble

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.

Flash - What Went Wrong?

I've always fancied flashing my Kaiser (V1615) with a new ROM, but was always nervous because I wasn't sure of the process and didn't want to risk bricking the phone as well as all the effort needed to get everything back on it I needed. Well, a few days ago my old Kaiser met the floor and an untimely end. So I decided to take the risk and put a new ROM on it and decided on the latest Dutty WM6.1 ROM.
I read all about flashing on here and made as much sense of it as I could. Thing is, I'm very technical in general, but not very familiar with Windows Mobile or flashing. I found there was lots to read, but it was all written with an assumed level of knowledge and understanding of terminology. As a result I found it quite hard to understand. I took the plunge anyway and started, but things didn't work out as expected and I didn't understand why.
I'm not trying to be critical of all the work a lot of people have put into the documentation that is available online, it's just that when I originally approached this with zero flashing experience I found it difficult and confusing to understand. What I really needed was a concise and basic introduction to flashing. I've now been through the process and after re-reading the documentation it makes a lot more sense.
I worked out you need to run something called HardSPL before you could flash a new ROM. I'm still not sure what HardSPL does apart from CID unlock the device, but what does CID unlock mean?
I ran HardSPL v1 and it started ok, but then I ended up with a white screen. At this point I already wished I hadn't started, but no going back now. Is it known why some phones white screen? Turns out it's a common problem, so followed the instructions to recover. All was well again, but still with the original ROM.
I thought I'd be brave and stuck with it and this time tried JumpSPL1.56-KAIS instead of HardSPL as recommended on one of the tutorials. This went better and I ended up with the Tri-Color screen. I plugged my USB cable in and USB showed on screen.
Next step I thought was to flash a ROM onto the device. I ran the Dutty updater on my PC and all started ok, but when the update got to 18% I received a communication error. I tried to recover using the updater, but the same thing happened. At this point the phone wouldn't boot, so I was more than a little worried and wishing I hadn't started!
Found something that described several options for recovering from this problem. I decided to try and flash the device back to the original ROM from Vodafone. When I eventually found that ROM I ran JumpSPL again, got to the Tri-Color screen and ran the updater. This time the update completed successfully and the phone rebooted and was all working again.
I decided to leave the device as it was and started customising it myself. I'd still love to put a cooked ROM on there, especially if it helps with performance, but after the experience above I'm not very confident.
Can anyone tell me where or what went wrong? I'm going to get my old Kaiser repaired and want to try again on that phone.

My flashing routene (not ideal but it works for me)
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
2) after device reboots, hold camera button and restart to check SPL
3) Flash rom/radio of choice
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Sam

Wow, I need a cuppa now
I'll go through 1 at a time... (and Sam has answered some questions already)
-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave

Thanks for the advice, but this is what I normally encounter when I read something on here, which is advice which no doubt makes perfect sense to the author or others experienced in flashing, but usually raises more questions than it answers in my head.
For example;
1) run the first part of the Kaiser SIM/CID Unlocker & Changer
Click to expand...
Click to collapse
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
2) after device reboots, hold camera button and restart to check SPL
Click to expand...
Click to collapse
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
3) Flash rom/radio of choice
Click to expand...
Click to collapse
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
4) Follow HardSPL v3.07, v3.28, v3.29 and v3.56 by JockyW 's second guide "If you have problems with the above process, try this:" and flash my 3.XX SPL of choice.
Click to expand...
Click to collapse
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?

BTW, not trying to moan about everything, just posting my experiences to find out where I went wrong, but also highlight some issues hopefully other flashing newbies can relate to and authors of tutorials can draw some useful feedback from.

Only one question, do I need to CID Unlock before using Jump and HardSpl or, the Hardspl does the Supercid ?
I'm not referring about SIM since I don't care, for now
With WM6.1 - Oficiall HTC ROM
Thanks

Thanks for that one dave, on reflection i kinda missed the whole point of the thread, and as for the majority of the stuff you posted i didnt undertand that to begin with.
Also, DaveTME, if you are wanting to flash a custom rom to youre kaiser. from my experiance and from the number of times ive seen this happen. i advise against asking for reccomendations(sp?) (not saying you will but its worth saying) try a few roms out and decide from there.
Also another thing to note. if you flash to WM6.1 remember to use a 3.xx spl otherwise you'll encounter a few problems with youre device.
Sam
What do you mean by the "first part"? The thread you've linked to doesnt really explain what I'm downloading and doing.
Click to expand...
Click to collapse
download the Kaiser unlocker and run the first stage of it, the program is in the linked thread.
Ok. I get this assuming you mean the device will reboot automatically and I restart it to check the SPL version that gets shown on the boot screen, but why do I need to do this?
Click to expand...
Click to collapse
No, after the device reboots, youre given youre Rom, Protocol and Radio. if you hold the camera button and reset you'll get youre SPL displayed, youre looking for 1.01 olinex to be shown
So at this point I can simply plug my device into my PC and run the ROM updater I've downloaded. Working out what rom/radio version to download is a minefield in its own right.
Click to expand...
Click to collapse
1) Yes, just run the RUU with youre chosen rom and thats it
2) its not a minefield, just make a decision on what rom you like and flash it. theres nothing to stop you flashing another one.
I thought HardSPL needed to be run before I flashed? Also, why the different versions? Which one do I choose?
Reply With Quote
Click to expand...
Click to collapse
The 1.01 SPL will allow you to flash a cutom rom. following that you need a 3.xx SPL as they are designed for windows mobile 6.1. as for yure decision. i use 3.29, yet other users have had better sucess with 3.56. Most rom chefs will say which SPL they reccomend anyway with their rom.

-CID unlock means that when the phone is loading a new device into the ROM the Carrier ID check is removed, each Mobile phone carrier has a different CID in thier OS ROMs. Unlocked means you can flash a OS ROM from any carrier or a cooked OS ROM from this site.
Click to expand...
Click to collapse
Great. Thanks for that. Makes perfect sense now
-The Jump SPL should only be used for replacing the SPL. Do not flash anything other than SPL's when at the Jump SPL (or SSPL). OS and Radio ROMs should be flashed from either in Windows Or By Manually Entering the Bootloaders. More info on SPL's is here: http://wiki.xda-developers.com/index.php?pagename=SPL Questions?
Click to expand...
Click to collapse
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
-Have a look at flashing from SD Card to avoid communication problems, http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
-The most clear instructions can be found here: http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser#ROMx20.Upgrading
Hope this helps.
Dave
Click to expand...
Click to collapse
Thanks, will have a read

DaveTME said:
Ok. I think you mean that the SPL is a component on the device? What is the difference between HardSPL and JumpSPL?
Click to expand...
Click to collapse
Read the "SPL Questions" Wiki Page, it is all there and fairly clear.
Ta
Dave

Ozone Verizon (Cedar): SSPL, HardSPL and original SPL by JockyW

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.

HTC Snap 511 (Willow): SSPL, HardSPL and original SPL by JockyW

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.