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

Think I've bricked my Kaiser - Can anyone help?

Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?

Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though

If your at the tri-color screen, just reflash a new rom

Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try

japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.

hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?

japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.

Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously

Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE

New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910

Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?

Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver

You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?

japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.

jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash

No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.

Did you try installing HardSPL and then reflashing?

the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.

URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.

austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!

Flash without hardspl

I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK

Did you try going to tri-color first then flashing a stock tilt rom?

Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.

both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!

I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK

Simple Step-By-Step Installation of 3.28 Hard SPL

Credit goes to the creator of the HardSPL files V3.28/3.29; JockyW
Simple Step-By-Step Installation of 3.28 Hard SPL:
I have decided to expand on what has already been posted for those noobeees that are having hard time understanding the HardSPL procedures and are hesitant to flash new cooked ROMs fearing the process was not really explained in details.
You only need two files; SSPL-KAIS.zip and Kaiser-HardSPL-3.28.zip. Save both files on your PC in their own folder for easy access later. Follow these steps to the tee, Do this only if you have your device CID unlocked already ( OliPoff method ):
1. Save then unzip SSPL-KAIS.zip inside a folder on your PC, then copy the unzipped “SSPL-KAIS.exe” onto your device. To do this, connect your device to ActiveSync, After Syncing, Click on Tools from the ActiveSync window, and then click on Explore Pocket PC. “Mobile Device” window appears, Copy SSPL-KAIS.exe by dragging it inside the “Mobile Device” window.
2. Unzip “Kaiser-HardSPL-3.28.zip” in its own folder on your desk top. It will unzip into two files; KaiserCustomRUU.exe and Kaiser-HardSPL-3.28.nbh.
3. Remove your SIM card and your SD card from device. Your device will power off when your SIM card is removed. Power up your device. You are still connected to your PC via USB at this point. Your phone will sync again since it is still connected.
4. On your device, go to “File Explorer” and locate SSPL-KAIS.exe that you copied earlier on your device main memory and click it.
5. Wait for the Bootloader Tri-Color screen to appear and "USB" to show.
6. On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
7. Unplug your device from the USB port, wait 5 seconds, plug it back in.
8. Go to the folder on your PC that has “KaiserCustomRUU.exe” and click it. This will flash the HardSPL on your device.
9. When done flashing, do a soft reset, and you should be good to go.
10. You can use the above steps to flash Kaiser-HardSPL-3.29 if you so desire.
Good luck

Tilt will not receive ROM
I tried flashing the below upgraded Kaiser Rom on my ATT Tilt but now I have the tri-color screen:
KAISI*0
SPL-1.93.000
CPLD-8
The first time it stopped loading at 15%, recovered and now I am getting vendor ID error (294 invalid vendor ID).
I tried others ROMs (including this one) but it just does nothing 0%, errors out, recovery and repeat (update error 262).
After removing battery the tri-color screen says "serial", once I plug in the USB it says USB, but no firmware can be loaded on it.
Does someone have basic firmware that will load when an ATT Tilt gets in this state?
Any help is really appreciated. I just got this thing too. Below was the update I tried that kill my Tilt.
'RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe' that you can find

did u hardspl?

Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).

TiltedHTC said:
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
Click to expand...
Click to collapse
Sounds like your phone is still CID LOCKED. Unlock it using the software posted somewhere else on XDA but NOT in this thread, and try to upgrade the SPL after unlocking.
One way to find out if your device locked or unlocked is that you can try to revert back to the AT&T OEM ROM and flash it. You would then be certain that the CID is locked if your device accepts the OEM ROM.
I wish you posted your troubles in the ROM post where you downloaded the ROM where it belongs; My instructions have nothing to do with your device ROM issues.

I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.

TiltedHTC said:
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
Click to expand...
Click to collapse
The following link is to Pof's full and clear post on unlocking your device CID. Use it carefully.
http://forum.xda-developers.com/showthread.php?t=334679
Search the forum for RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom, download and then flash. you will be set.

Cingular/AT&T OEM ROM
Download the AT&T OEM ROM from the following link:
http://rapidshare.com/files/55298724...GULAR_WWE_.exe
This is just because I feel good today... Otherwise I would ask you to take the time and do the search yourself. Noobee Spoon-feeding Time...

I found this link to put OEM ROM back:
http://forum.xda-developers.com/showthread.php?t=335568
but the RUU ROM for the AT&T link would not load on my tilt (step 2 of idiots guide). I also did a search for the RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom but no hits.
At least I know what went wrong, now I need to recover the original Rom.
update:
This newbee still won't eat. I got the file (your link is to the same file) but I am getting the same 294 invalid vendor error (after 1%).
I rebooted computer and tried it again with same 294 error.

did you just use jumpspl and used that to load a rom?? why oh why.......

Tilted newbie, did not read enough. Any solutions?

A question.
On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
Do you have to do this ?
I never did that.In my settings USB connections is enabled and it seems to work
/Linus

thaaaanx
i must admit this is the best and clearest step by step guide i have come acrooss thanks a lot mate

just a quick thought..... maybe you should give some credit to jocky

Also,
It wouldn't hurt to mention the "white screen" issues people get when running SSPL.
In such a case they need to use Jump SPL 1.56 or 1.93.
Link Here
Ta
Dave

Thnks man for tutorial. I think it usefull and simple for newbies.

So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks

kpcz said:
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
Click to expand...
Click to collapse
Correct.
Hard SPL's allow you to flash custom ROM's no matter what version.
Ta
Dave

ok, thanks - will give it a try!

It appears there is no way to recover.
Any great excuse that should be used when I take it back for repairs?

Completely Unable to flash ROM

I cannot flash any rom. I've tried one of Dutty's and I tried the HyperDragon version. With each, I got to the step of running the KaiserCustomRUU, clicked through the screens and at about 18% complete, it freezes due to some communications error. Can someone help? I've seen these cool ROMS online and just can't get it to work. Here's what I did
1. Synched TILT with PC and moved JUMPSPL1.93-Kais.exe and JUMPSPL1.56-Kais.exe(I've tried both) to the sync folder.
2. Run the file from my TILT, following the unplugging steps mentioned in all the guides online.
3. Run the KaiserCustomRUU file from my sync folder on the pc...follow screenpops, then at 18% I get the error. I try the error recovery with no luck...
I'm completely stumped...I've been able to avoid a "brick" whatever that is, by downloading the ROM from the HTC site to save my phone, but unable to set up a new ROM....AHHHH!!!

So after running JUMPSPL1.93-Kais.exe, which hard SPL are you trying to install so you can flash a custom ROM? When you say you run the KaiserCustomRUU file on your PC, what else is in the "sync" folder?
I recommend you read the Wiki more thoroughly; make sure you know exactly what you're doing.

Completely Unable to Flash ROM
I downloaded a folder called Kaiser-HardSPL-3.29. In this folder I have KaiserCustomRUU.exe (which is what I ran). there is also a file called Kaiser-HardSPL-3.29.nbh. Only the .exe is the executable file so that's the only one I could click on.
I've tried navigating a few beginner guides on this website and they still seem designed for people who have somewhat of an idea of what they are doing. I don't

Read and follow the steps in the first post in the attached thread, it's the best one I've found yet.
http://forum.xda-developers.com/showthread.php?t=433835

kaisercustomruu
That thread definitely lays out the steps for me, but the problem I'm having is when I flash the hardspl3.29. That's when I get the pops ups on my pc, which I click through, and when the progress bar gets to 18%, It says I've had some sort of communications error. it did this both times I attempted it.

mrmack00 said:
That thread definitely lays out the steps for me, but the problem I'm having is when I flash the hardspl3.29. That's when I get the pops ups on my pc, which I click through, and when the progress bar gets to 18%, It says I've had some sort of communications error. it did this both times I attempted it.
Click to expand...
Click to collapse
Read the wiki and step by step instructions "how to install HardSPL".
READ IT.
Step.... by..... step.... its easy.

So you've installed HardSPL 3.29? Did the whole unplug/plug in thing? And THEN tried to install the ROM?

btstarcher said:
So you've installed HardSPL 3.29? Did the whole unplug/plug in thing? And THEN tried to install the ROM?
Click to expand...
Click to collapse
Do you have to do the unplug/plug thing?
I did it the first time when I flash to hardSPL 3.05... then when I hardSPL it to 3.29 again, I didn't have to do that. It just run by itself.

I'm not sure; I always did. I suppose not if you didn't and the procedure still worked.

mrmack00 said:
I cannot flash any rom. I've tried one of Dutty's and I tried the HyperDragon version. With each, I got to the step of running the KaiserCustomRUU, clicked through the screens and at about 18% complete, it freezes due to some communications error. Can someone help? I've seen these cool ROMS online and just can't get it to work. Here's what I did
1. Synched TILT with PC and moved JUMPSPL1.93-Kais.exe and JUMPSPL1.56-Kais.exe(I've tried both) to the sync folder.
2. Run the file from my TILT, following the unplugging steps mentioned in all the guides online.
3. Run the KaiserCustomRUU file from my sync folder on the pc...follow screenpops, then at 18% I get the error. I try the error recovery with no luck...
I'm completely stumped...I've been able to avoid a "brick" whatever that is, by downloading the ROM from the HTC site to save my phone, but unable to set up a new ROM....AHHHH!!!
Click to expand...
Click to collapse
Make sure you use,.
Win XP SP2 or higher
Active sync 4.5
and net framework installed on your pc
USB cable that came with kaiser box,.
Thats usually the main reason for cant upgrade ROM,.
SPL and CID thing is not related if you failed in upgrading process,.
Hope this help,.
BR