Database Info

Fatal downgrade...

Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....

Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)

illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine

Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!

I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !

Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)

it doesnt work

I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.

If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)

illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.

My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.

I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful

Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick

From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...

THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!

same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again

SPVServices.exe Tools showing blank screen.

Hi Guys,
Glad to see WM6 on the Tornado...
Pulled my Cingular 2125 out of the bin and trying to get it upto WM6.
The problem I'm having is that I need to SuperCID it but SPVServices isn't working.
I get the "ALL OK" RAPI init was Successful when I run SPVServices.
Then I click the "CID Tool (Alpha) Link" but it only displays a blank screen.
I have successfully App-Unlocked and installed the Certs.cab
Any help would be appreciated.

What OS no ur PC are you using? FYI, it must be done on XP

OS & IE Versions...
Sorry, forgot to mention...
Windows XP, IE 7. Thought there might be an issue with IE7 so I uninstalled it and tried again with IE 6. Same results.

Try it on other computer ?

Gonna try on my work PC tomorrow (or actually later today).
Just wondered if others had experienced this..

Odd, never heard of a blank screen issue, most errors are saying that it can't write the to the correct memory area or it just wont run at all under vista..
Phil
[EDIT: Good to see you about again kyphur ]

try to supercid with lokiwiz (wizard sim unlock and supercid tool). it works on tornados too
before this make sure that the phone is fully app-unlocked.
ps: skip the enablerapi.cab step

Ah yes, LokWiz my old friend... Wizard was my second HTC Device (Blue Angel being my first).
I used SDA_ApplicationUnlock.exe, is there a sure-fire way to confirm that my Tornado is App-Unlocked?

Success!!
Go figure, worked right off the bat on my work PC, that's just not fair!
Well, thanks you guys have really got your stuff together here.
We'll see how my 12 year old daughter likes WM6 SmartPhone Edition.

please help i beg you!!!

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.

Kaiser SIM/CID Unlocker & Changer

Hi Folks
Well, here it is, ported from what I did for the Polaris basically... I find it's a nice solution as it works by flashing your device with a patched radio and changing stuff properly, anyway...
download and run the EXE, follow the instructions.
bear in mind if you already have Hard-SPL on your device you can skip *straight* to Step 2.
and remember the golden rule:
YOUR DEVICE MUST BE IN CE AND SYNCED BEFORE RUNNING EACH STEP.
Download Here or Download Here
UPDATE: now version v2.0 - Model ID error fixed, it WORKS.
if and when you get success, POST!
PS: If you try to sell this, I will find you, kill you, and sell your ****ing testicles on eBay

Yes, apologies, my error, new version uploaded

So what is the status now?

I found this solution does not work on all of devices. But my solution is as follows.
Run KaiserUnlocker.exe
1. I started with the Step 1. The upper button of total 3.
2. Go through the menus and accept everything.
3. You get TRI-COLOR screen on your device and a few seconds later you get the USB label.
4. After some time you get a communication error Message. DON'T RESET YOUR MOBILE DEVICE. DON'T TOUCH IT.
5. Press Exit to quit KaiserUnlocker.exe on your Desktop machine.
6. Unplug and replug the USB cable.
7. Start the KaiserUnlocker.exe again and wait a little bit.
8. Your mobile device (AT&T Tilt) suddenly alive again. The progressbar shows up and you're from 0% to 100% in a few seconds. Wait a little bit and then you get the message the process is finished.
Now I don't know what to do with step 2 and 3. Should I perform them or not. Hmm?
What I would like to do is just to update from AT&T Tilt ROM to original HTC TyTN II ROM

AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one

Oh I see you changed the version now. At the time I downloaded it and wrote my first message it was just V1. There was no V2. But I can't test it now because I already have the ROM patched.
And I didn't get the ModelID error. It was a connection error 260.
I think it's just some guys of you are lucky to have a device that doesn't get the white screen when using hardspl and it doesn't stop on tri-colors or the progressbar at 0%.

actually, it's steps 2 and 3 that I care about, having a patched ROM is irrelevant.
step 2 and 3 allow you to sim/CID unlock

Mirror:
Kaiser Unlocker v2.0
FTP Problems!
Hi everybody,
Our provider has notified us of the fact that our ftp server has appeared in a list of compromised FTP servers which are known to host malware associated with attacks on banks and banking infrastructure. We have been requested to secure our systems. Since we realize it would cause serious problems to some if not most of our users if we we're to close it down immediately or change the password in the next 5 minutes we hope you can all live with the following arrangement:
We will close down the ftp server Monday the 9th of march on 09.00 CET. You have until then to download anything from our ftp server you (urgently) need, especially if you host software of which you don't have a back-up on our ftp it's important to download it asap. After closing down our server upcoming Monday we will remove all malware and start restructuring our server, implementing a new user structure, this does mean our server will be offline for a while and we cannot assure you no data will be lost.
If you have space available to host your own software please do so, if you have space available for those who do not have their own space please let it be known by posting a reply to this post. Our apologies for any inconvenience this will cause, but we hope to be able to serve you with a better ftp server as soon as possible.
Best regards,
Flar
Site admin.
Click to expand...
Click to collapse
Just to be safe!
Thanx Olipro

Sorry for asking, what do you mean by "your device must be in CE"?

Olipro said:
AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one
Click to expand...
Click to collapse
I did re-download after you said it didn't work. I must have downloaded it before it was fully uploaded. I did see the V2.0 NOw...this time no errors.
Thanks again Works perfect now. Thank again.

It Works!
This is awesome. I was trying with Jocky's unlocker for couple of hours. No luck.
Gave a try to this tool. Unlocked first time. Now, I got to check my phone with a different provider SIM.
Thank you so much!

Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?

Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?

Penske MB said:
Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?
Click to expand...
Click to collapse
it's 1.58.something, i forget the rest

FTP will close today.!!!!!!!!!!!!!!!!
I try to download and uploade to mediafire
Midget Edit: Mirror removed, new version.

doesn't matter, I'm updating the FTP link in a second or two with the new one

Active sysnc
Hi Olipro,
Thanks for all the hard work.
When I try to run the step 1, it keeps on disconneting the active sysnc. Am I doing something incorrectly?
Cheers
Shan

elmoono said:
Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?
Click to expand...
Click to collapse
These were my steps,
1. Identified my AT&T radio ROM & downloaded that from XDA website as a backup. Pick from here
2. Ran Pof's HardSPL Link
3. Ran Jocky's SuperCID & Security Unlocker Link
4. Installed Dutty's Official WM6.1.2.19199 Full Version Link
5. Installed Radio ROM 1.64.06.04 Download
6. Installed .NET Framework 2.0 on my Windows XP SP2 from Microsoft website.
7. Ran OliPro's Kaiser SIM/CID Unlocker. Followed just step 2 & 3 since I had already installed HardSPL.
8. Installed Radio ROM 1.64.06.04 to get my ringtone & HSDPA connection.
May be my steps 3 ~ 5 were over kill but that was just me. If you would like to skip 3 ~5 make sure you have WM 6.1 installed also remember to patch your original radio on step 8.
All the above steps does not need a strange SIM. I am yet to pop in a different carrier SIM to confirm about my Tilt Unlock Status. However, after the above steps, I found "Kaiser Unlock.exe" under my Tilt root folder. I ran that from phone, clicked on check SIM Status, came up as "You are already SIM Unlocked"
Hope this helps.

when you run step 3, just query what simlocks are active

Worked on my AT&T Tilt!
Not sure about step one already had SPL done with Whitescreen Fix
I will try it monday when my friend brings his tilt over to get it unlocked.
I did have to install a 6.1 ROM (I used Dutty's Official) between steps 2 and 3, had a blank screen, using the att rom -bloatware.

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.