Related
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!
Hi everybody,
I made up a new version of pof's USPL for ELFIN based on SPL 2.20.0000. You should be able to flash SPL in the third step now.
Why a new version? Because USPL v1 is only for ELF (64/128MB), but not for ELFIN (128/256MB). Flashing the old ELF SPL in step three on a new ELFIN used to brick your device.
EDIT:
You can find the working release in the following thread:
http://forum.xda-developers.com/showthread.php?p=1964159#post1964159
Thanks to everybody who was willing to test this!
Tempting, tempting.
I still haven't reproduced that weird blue screen i once had on my ELF.
But like i just wrote i got's me an ELF.
Good luck finding resourcefull Gamblers.
If there's no luck just start a Donation round for a Bricked Device Garantee
djvw said:
insane people
Click to expand...
Click to collapse
We have a lot of those in this forum. People trying to flash first and then start reading .
Thanks for trying to get USPL working for the XL users!
ummmmm i just used to use the old uspl v1 and exit after step 3 than flash my rom, if you guys are really keen on testing this my new elfin will be here today or on monday and i will try it with my old one just to piss of rogers
shael said:
ummmmm i just used to use the old uspl v1 and exit after step 3 than flash my rom, if you guys are really keen on testing this my new elfin will be here today or on monday and i will try it with my old one just to piss of rogers
Click to expand...
Click to collapse
This is the kind of brave people we need ;-) Please test it and tell us if it's working as soon as you can. Thank you in advance!
Uploaded new version, please redownload in first post.
Nobody has tested this yet?
I think that a Elfin dopod owner can test this without problems, because if don't work he can flash the complete (and signed) dopod rom from bootloader to restore the original SPL...
http://www.dopodasia.com/download/R...7.1B_4.1.13.51_03.07.90_BLUE_Ship_Reduced.exe
i have a elfin locked on bootloader screen....can change my spl with this??
what ??? the UPSL 1.0 is for Elf only and not Elfin ??? what i dont understand is what do you guys mean quit at step 3 ??? I flashed my Elfin with UPSL 1.0 with all steps for more than 6 times so far and nothing has happen so far ... my SPL is the 2.20.2000 one ...
@jamezco:
that´s wrong.
You flashed those roms containing the USPL (start.bat). They automaticly quit the 3rd step and go directly to the Rom Utility to flash the new ROM.
If you use POF´s USPL v1 and you don´t quit after step 3, the patched Bootloader will be flashed from your devices RAM to the ROM, and this wil brick your ELFin. If you have done this, your actual IPL or SPL would be 1.11.xxx...
Sorry: could someone explain me whether it is strictly needed to use the USPL unlock (the one are treated in this post) to flash the PDA?
I mean: the bootloader in the rom package is not able to do that?
we need some thing to unloack direct from boot loader and no need to active sync
as far as i know this is not possible, cause you can´t access bootloader files...in bootloader mode.
same on pc, you can´t delete or replace files, which are open/inuse by another program...
STRAFALCIONE said:
Sorry: could someone explain me whether it is strictly needed to use the USPL unlock (the one are treated in this post) to flash the PDA?
I mean: the bootloader in the rom package is not able to do that?
Click to expand...
Click to collapse
The Rom Packages u can get here don´t contain a bootloader...and even if they would, the bootloader or the rom would have to match your model ID for flashing it to your device....so yes, it´s stricktly needed to CID unlock to flash Custom ROMs or ROMs with other vendor IDs.
Could someone help me? The USPL is needed for the flashing of ROM, or is it enough the bootloader of the ROM?
Sorry, I missed the answer of the post before
My eyes are crossing after 12 hours in front of the pc
Anyone tested already???
Come on guys,
somebody who can get official Roms from his provider should give this a try...
Hi all, not that i think myself insane but i have tried the USPL for my Elfin 128/256 Touch a few days ago . I have followed the steps and the screen turned white as mentioned by the installer after that it booted up fine again.
Everything seems to be working fine!
However, i have not seen any change to the device..
mb286 said:
Hi all, not that i think myself insane but i have tried the USPL for my Elfin 128/256 Touch a few days ago . I have followed the steps and the screen turned white as mentioned by the installer after that it booted up fine again.
Everything seems to be working fine!
However, i have not seen any change to the device..
Click to expand...
Click to collapse
You don't see any change in the device.... but if USPL works you can flash ANY rom from bootloader directly executing RomUpdateUyility, you don`t need to boot windows, activesync and white screen (temporary SuperCID) to flash, try.....
Go to RUU directory and execute RomUpdateUtlity instead of RUN.bat and see if you can flash any rom without 3% (corrupted) error....
I have been followingthe in structions on how to to this i just want to run l26 diamond with the correct spl so it dosent freeze i get to the sspl-kaiser part and it goes to bootloader but my pc dosent find it when i run the custom ruu??says it fails to find usb or somthing. do i have the wong original att rom im trying to use
RUU_Kaiser_CINGULAR_WWE_ with the new att spl supplied inthe reverting thread??? HELPPP please link to the other rom if i do havethe wrong one for this thanks.
jefem24 said:
I have been followingthe in structions on how to to this i just want to run l26 diamond with the correct spl so it dosent freeze i get to the sspl-kaiser part and it goes to bootloader but my pc dosent find it when i run the custom ruu??says it fails to find usb or somthing. do i have the wong original att rom im trying to use
RUU_Kaiser_CINGULAR_WWE_ with the new att spl supplied inthe reverting thread??? HELPPP please link to the other rom if i do havethe wrong one for this thanks.
Click to expand...
Click to collapse
Once you run sspl and it goes to bootloader it should show USB on the bottom. Once it says that you need to unplug and then replug your device's usb connection. Then continue to the flashing part.
jefem24 said:
I have been followingthe in structions on how to to this i just want to run l26 diamond with the correct spl so it dosent freeze i get to the sspl-kaiser part and it goes to bootloader but my pc dosent find it when i run the custom ruu??says it fails to find usb or somthing. do i have the wong original att rom im trying to use
RUU_Kaiser_CINGULAR_WWE_ with the new att spl supplied inthe reverting thread??? HELPPP please link to the other rom if i do havethe wrong one for this thanks.
Click to expand...
Click to collapse
okay if i understand correctly, u already have hardspl?
spl's r not rom specific. ur phone comes with an spl and flashing roms over ur carriers spl can and will lead to u bricking ur phone.
now if u r trying to flash hardspl than follow instructions to the "t" and post back.
lol
that one vital step got me un plugging and replugging the phone lmao
ok im at 1.93 thats the newest??? thought i read somthing about a 3.25 but it was german
is 1.93 good fro l26 diamond?
jefem24 said:
that one vital step got me un plugging and replugging the phone lmao
ok im at 1.93 thats the newest??? thought i read somthing about a 3.25 but it was german
is 1.93 good fro l26 diamond?
Click to expand...
Click to collapse
okay i will repeat that is a version of jumpspl; it has nothing to do with the rom. ROMS ARE NOT spl dependent. As long as you get hardspl onto your device (doesn't matter if you use jumpspl 1.93 or 1.5x, whichever one works) you can flash leos, dutty's, shogunmark's, kyphurs, _alex_'s anyones rom you want.
but the freezing issue is the reason i was doing all this im so confused now do i need to re hard spl my phone again to flash other roms what would be the purpose of soing what ive done then??? or are people just guessing at the stalling issue still?????
thesire said:
okay i will repeat that is a version of jumpspl; it has nothing to do with the rom. ROMS ARE NOT spl dependent. As long as you get hardspl onto your device (doesn't matter if you use jumpspl 1.93 or 1.5x, whichever one works) you can flash leos, dutty's, shogunmark's, kyphurs, _alex_'s anyones rom you want.
Click to expand...
Click to collapse
1.93 is actually a valid AT&T SPL it is the updated (although not the latest) one. So he might not be referring to jumpSPL even though there is also a version 1.93 of that (most probably based off the AT&T SPL).
jefem24 said:
but the freezing issue is the reason i was doing all this im so confused now do i need to re hard spl my phone again to flash other roms what would be the purpose of soing what ive done then??? or are people just guessing at the stalling issue still?????
Click to expand...
Click to collapse
I don't want to blow you off, but you should really go back and read the threads dealing with this to get a better understanding.. There are a few and they answer all the questions. If you are read them and still have questions or problems, post in those threads since continuing this thread is just more of the same.
jefem24 said:
but the freezing issue is the reason i was doing all this im so confused now do i need to re hard spl my phone again to flash other roms what would be the purpose of soing what ive done then??? or are people just guessing at the stalling issue still?????
Click to expand...
Click to collapse
when u mentioned 1.93 i thought u were referring to jump spl (thanks for clarrifying bengalih).
yes apparently going back to the att spl does fix freezes (can't confirm as i haven't tried) and if u need help with that post under relevant thread as bengalih suggested.
yes if u r going to flash a cooked rom u will need to reflash hardspl first.
The screen remains black, blank, and does not light up, even though activesync knows the device has booted because the icon becomes green. I can't navigate any controls, though the keys do light up when I slide it, or press buttons. Screen remains blank/black.
Here is what I did to get to this state:
1) I first hard reset my Kaiser, to reset all user preferences. This I accouplished by pressing both soft keys while pressing power (if I recall correctly), then hitting the green call button. It then installed Windows Mobile fresh.
2) I then followed the HardSPL instructions, here:
http://forum.xda-developers.com/showthread.php?t=361236
Everything went fine.
3) I then followed the Kaiser Sim Unlocker instructions here:
http://forum.xda-developers.com/showthread.php?t=361039
After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stays that way.
What should I do? Did I miss something? Is this recoverable?
It also does not have any sound. Does this mean I can't unlock?
How do I flash back to the original rom?
Ok, looks like have version 1.27.12.11 rom, during boot.... according to this page it isn't ok for my AT&T Tilt device.
http://forum.xda-developers.com/showthread.php?t=393182
So does this mean I have to pay to unlock? Or is there some way to do it still? Thanks.
NetTechie said:
Ok, looks like have version 1.27.12.11 rom, during boot.... according to this page it isn't ok for my AT&T Tilt device.
http://forum.xda-developers.com/showthread.php?t=393182
So does this mean I have to pay to unlock? Or is there some way to do it still? Thanks.
Click to expand...
Click to collapse
Try flashing this radio.
http://www.4shared.com/file/36681926/36b4832d/KAIS_Radio_Only_1271211_CustomRUU.html
I guess you didn't read step 10
I have a problem... it wont go green now, I can't get activesync to go green. I wont be able to load the rom... what can I do?
[ EDIT ]
A reboot fixed this *sigh of releif*. Goes green now.
AllTheWay said:
Try flashing this radio.
http://www.4shared.com/file/36681926/36b4832d/KAIS_Radio_Only_1271211_CustomRUU.html
I guess you didn't read step 10
Click to expand...
Click to collapse
Ok, question: Will I use the file in Step 3 to put that on the phone? It is saying there is a file open...? I can't disable USB on the device, as the screen is blank.
[EDIT] Looks like everything I needed was in the download. I put the other ROM back on. However, I'm having a problem with activesync... When I click on Connection Settings active sync freezes up. Any ideas what to do to fix ActiveSync so I can turn off USB, without crashing ActiveSync?
Okay, I got the screen with the unlock code... only it gave me this readout:
Your Unlockcode = ........
just like that, with dots.
Is there any way to unlock a phone, if the screen goes black? I can go back to the old firmware, but this special firmware is needed I think to do the unlock, and this special firmware makes the screen go black on my model.
EDIT: On page 33 of the Kaiser unlocker topic, I found what looks like my answer. I need the AT&T 1.57 ROM, as it is compatible with this patched radio so the display will work. Unfortunately, I haven't been able to find it on this forum yet. EDIT 2: Found it, loading it on now: http://www.4shared.com/file/3857459...ULAR_WWE_157_-_Originaly_Shipped_ATT_ROM.html
Unlock worked, once I had the AT&T 1.57 version of the ROM on there. ActiveSync still freezes, but I uninstalled it for the section where I was supposed to disable USB. Installed the 1.27.12.11 radio after completing the unlock, replacing the patched radio. All finished.
Mine still showsup Blank screen
Hi,
I followed the same steps as yours :
Firstly I reset my Kaiser & then followed the HardSPL instructions, here:
http://forum.xda-developers.com/showthread.php?t=361236
Everything went fine.
I then followed the Kaiser Sim Unlocker instructions here:
http://forum.xda-developers.com/showthread.php?t=361039
After completing step 5, the device rebooted, the AT&T icon displayed, then the screen goes blank and stays that way
Now I tried flashing
http://www.4shared.com/file/36681926...CustomRUU.html
But it didnot help (
Can you please tell me what I should be doing next..
vrramakanth said:
But it didnot help (
Can you please tell me what I should be doing next..
Click to expand...
Click to collapse
what do you mean when you say it "didn't help"?
I still get the blank screen..I am now downloading the AT&T 1.57 version .. I am hoping if I install this I will get the display and I can proceed to step 8a, 8b,..
Sorry to be short,
But did you even bother reading through the other threads with the exact same problem as you?
the problem you have is that you flashed an incompatible radio with the ROM that you are runing on the phone. You need to reflash the ROM with a rom that is compatible with the radio or reflash the radio rom to what came with the phone rom that you are running.
You should have upgraded to a 6.1 cooked rom prior to doing the SIM/CID unlock.
Flash your phone with a cooked 6.1 rom that INCLUDES the radio, and then try the CID/SIM unlocker.
my two bit.
I am trying with http://www.4shared.com/file/38574592...d_ATT_ROM.html, which is the ROM that comes with this phone. Do u think this helps? Do u want me to flash 6.1 ROM instead of this?
No,
Unless you know the stock ROM comes with a compatible radio, it will not work. The problem you are having is because you loaded a radio that is not compatible with the stock rom.
If you already have hardspl loaded, then load a cooked 6.1 ROM that includes a compatible radio (for example L26 v9 rom or Sleuth 3.0 rom).
ok..am a BIG novice here..may be a bad question..I have Windows 6.0 on the mobile..so the Cooked 6.1 ROM L26 that I found http://forum.ppcgeeks.com/showthread.php?t=26925 fits into this? Do I need to upgrade to 6.1 before this? sorry if its a wrong question ..
vrramakanth said:
ok..am a BIG novice here..may be a bad question..I have Windows 6.0 on the mobile..so the Cooked 6.1 ROM L26 that I found http://forum.ppcgeeks.com/showthread.php?t=26925 fits into this? Do I need to upgrade to 6.1 before this? sorry if its a wrong question ..
Click to expand...
Click to collapse
It's not a wrong question
1. Yes, that fits in
2. No, you do not need to upgrade to 6.1 before this, flashing the ROM will take care of it
hope this helps
Thanks mbarvian!!
So I am Installing the upgrade to 6.1 ROM, but do I still need to install the correct AT&T ROM that you gave me in the other thread http://forum.xda-developers.com/showthread.php?p=2452022#post2452022?
Thanks!!
Alibaba0101 said:
No,
Unless you know the stock ROM comes with a compatible radio, it will not work. The problem you are having is because you loaded a radio that is not compatible with the stock rom.
If you already have hardspl loaded, then load a cooked 6.1 ROM that includes a compatible radio (for example L26 v9 rom or Sleuth 3.0 rom).
Click to expand...
Click to collapse
I now installed a 6.1 ROM..now do I need to downgrade to be able to do SIM unlock?
From http://forum.xda-developers.com/showthread.php?t=361039 it says :
Note for WM6.1 users
================
Do not try this on 6.1! You will need to downgrade to 6.0
Click to expand...
Click to collapse
vrramakanth said:
I now installed a 6.1 ROM..now do I need to downgrade to be able to do SIM unlock?
From http://forum.xda-developers.com/showthread.php?t=361039 it says :
Click to expand...
Click to collapse
Yes, now you would want to download and flash the ROM I gave you in the other thread
here's the link:
http://rapidshare.com/files/55298724/RUU_Kaiser_CINGULAR_WWE_.exe
I am trying with http://www.4shared.com/file/38574592...d_ATT_ROM.html is this fine??
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