Before someone comes and flames me for creating a new thread (*hide from DaveShaw*) let me explain:
I have created a Wiki page for users who are stuck at the SPL (a.k.a Bootloader, Tri-Colour screen etc.):
Kaiser_stuck_at_bootloader
This has helped out a number of users who have become stuck at the SPL but every day I see more and more users getting stuck and creating new thread, or going off topic in other threads.
What to do if you get stuck:
Read the Wiki Page and follow the advice: Kaiser_stuck_at_bootloader
If you have tried all the steps in the wiki and still have a problem, read the feedback from other users in this thread and any advice I give out in this thread.
If you are still having problems please post all the details you can about what you have done and what version ROM / Radio / SPL you are running in this thread.
Credits:
Everyone I credited in the Wiki page.
mrdo who followed my advice and donated.
P1Tater for stickying this thread.
cmonex who seems to teach me something each day.
Thanks
Dave
Nice thread. Worth a sticky since it seems to be happening quite frequently lately
P1Tater said:
Nice thread. Worth a sticky since it seems to be happening quite frequently lately
Click to expand...
Click to collapse
Thanks to much I have learned from Master Jocky_W, I am currently working on hacking o a couple of Jockey's new HardSPL's into MFG variations. This will allow for the checking, formatting & fixing of OS flash memory blocks.
I am just about done I think, & then off to Jock it will go for his comments & keen eye.
GSLEON3 said:
Thanks to much I have learned from Master Jocky_W, I am currently working on hacking o a couple of Jockey's new HardSPL's into MFG variations. This will allow for the checking, formatting & fixing of OS flash memory blocks.
I am just about done I think, & then off to Jock it will go for his comments & keen eye.
Click to expand...
Click to collapse
Nice one, I was thinking MFG 3.* HardSPL would be good, but I assumed there was a good reason for them not to exist. Little did I know that's where you were hiding
Great work.
Dave
Good idea with this thread, congratulations.
Just to add something useful for the thread, here is my tip: (for n00bs, or a "newbie-n00bs" since I consider myself a n00b too )
No matter what, DON'T PANIC.
If your phone boots at least partially (the bootloader starts and shows R/G/D versions) maybe its not that bad
I've flashed few times "bad ROMs" and my phone stucked on bootloader. Luckily none of them was that bad that I couldn't recover from it.
What I do first:
disconnect the phone from anything you had it connected to,
and go into bootloader mode (camera button + reset with stylus).
It will show the tricolor+white screen, SPL version on the top and "Serial" at the bottom.
Plug in your USB cable.
If the "Serial" will change into "USB" at the bottom, you are most likely ready to fix the problem
- so flash your phone with new clean ROM now (I would go with clean stock ROM including radio as well)
oh, and don't worry about the ActiveSync info that may be displayed by the RUU app, because you are already in bootloader mode (RUU or KaiserCustomRUU etc, at first disconnects AS in order to set your phone in bootloader mode, thats why the warnings about AS being "green" etc)
HTH
this one isn't covered!
I go right to bootlader and see RUUNBH upper right!
my SPL is 3.56.hard
CPLD-8
I would flash my stock rom BUT i cant get a usb connection to work at all!
mtty doen't work at all!
hmm?!?!?!??
HELP, please!
OrrinS1189 said:
I go right to bootlader and see RUUNBH upper right!
my SPL is 3.56.hard
CPLD-8
I would flash my stock rom BUT i cant get a usb connection to work at all!
mtty doen't work at all!
hmm?!?!?!??
HELP, please!
Click to expand...
Click to collapse
Does "USB" show in the bootloader when you connect the USB plug or not?
Dave
yep
yes, those words DO change. But nothing can be done on my PC.
OrrinS1189 said:
yes, those words DO change. But nothing can be done on my PC.
Click to expand...
Click to collapse
Have you done the following to get MTTY to work?
* Download mtty.exe
* Disable activesync (connection settings -> uncheck "allow usb connections")
* Connect your Kaiser to PC using USB cable.
* Open mtty, select USB port and click OK.
* Hit ENTER twice, you should see the "Cmd>" prompt.
* Type the command "boot".
Are you using Vista or XP?
Dave
yes again!
i have disabled usb connections through active synch and killed ALL the mobile processes through task mngr. Still, usb port cannot be opened through mtty!
it's crazy! =[
also, when i plug in my tilt, i get a beep beep beep from my PC saying failure to cconnect to hardware. =[
VISTA!!!
OrrinS1189 said:
i have disabled usb connections through active synch and killed ALL the mobile processes through task mngr. Still, usb port cannot be opened through mtty!
it's crazy! =[
also, when i plug in my tilt, i get a beep beep beep from my PC saying failure to cconnect to hardware. =[
VISTA!!!
Click to expand...
Click to collapse
I'm leaving work now, but can you trying flashing your carrier ROM from the SD card, that might do it.
Also, try the attached MTTY.
If that don't work, can you find a Windows XP Machince and try the normal MTTY method.
Dave
No Luck
Since I can't establish a usb connection I have no way of getting ANYTHING to my tilt.
I can't access my SD card.
MTTY says command error when I say boot.
I don't think MTTY is connecting.
Does my SPL need to be changed?
If so, how do I change it if I can't get a connection to my tilt at all?
I GOT IT!
i TOOK your advice to flash from my SD my naming a rom KAISIMG.nbh and using my PC to put on card. then i just entered bootlader. I flashed a random new rom (not at&t) and it worked in restoring my phone.
I didn't use a stock rom cause my spl didn't match. thanks for all your help man.
OrrinS1189 said:
i TOOK your advice to flash from my SD my naming a rom KAISIMG.nbh and using my PC to put on card. then i just entered bootlader. I flashed a random new rom (not at&t) and it worked in restoring my phone.
I didn't use a stock rom cause my spl didn't match. thanks for all your help man.
Click to expand...
Click to collapse
Glad you got it working.
Dave
good thread
BTW, if you do not have the RUUNBH on the screen, but can't get OS to boot and you didn't flash my patched SPL's for prevention, I now have a solution for those too in my thread (also sticky, so easy to find).
cmonex said:
good thread
BTW, if you do not have the RUUNBH on the screen, but can't get OS to boot and you didn't flash my patched SPL's for prevention, I now have a solution for those too in my thread (also sticky, so easy to find).
Click to expand...
Click to collapse
Thanks for this.
I have added this to the Wiki Page. Which I may re-write later to be a little more clear.
Dave
I have re-written most of the Wiki Page to be more than a collection of random Links. It took over an hour, to get right, so please read it.
Now there's really no reason to get stuck.
Thanks
Dave
DaveShaw said:
I have re-written most of the Wiki Page to be more than a collection of random Links. It took over an hour, to get right, so please read it.
Now there's really no reason to get stuck.
Thanks
Dave
Click to expand...
Click to collapse
nice update! really useful to all kaiser owners.
btw, you wrote:
"This method will not work if RUUNBH is showing and cannot get the OS to boot even once"
I removed second part if you don't mind, the method doesn't need that as a requirement. (and it will actually unset RUUNBH flag too if the loading of the special SSPL and the flash is successful, but for RUUNBH issue this solution is overkill, because for that "set 16 0" is fine.)
cmonex said:
nice update! really useful to all kaiser owners.
btw, you wrote:
"This method will not work if RUUNBH is showing and cannot get the OS to boot even once"
I removed second part if you don't mind, the method doesn't need that as a requirement. (and it will actually unset RUUNBH flag too if the loading of the special SSPL and the flash is successful, but for RUUNBH issue this solution is overkill, because for that "set 16 0" is fine.)
Click to expand...
Click to collapse
Thanks cmonex, I don't even know what that senence means, I wrote it after midnight last night, and I really can't recall what I was thinking.
Cheers
Dave
First, I’m using the ROM L26KDV12. I used the tweaking program that comes with the ROM and I hit done, the phone said to restart the device to get effective or cancel to restart later but I choose to restart the device. So, the Phone restarted and I stuck in bootloader mode.
I tried to re-flash my ROM L26KDV12 and I got the 100% result in the screen but when I restarted the device it was stuck again in bootloader mode. I tried to update the Radio but got no luck also.
So I decided to update the ROM via MicroSD(Dutty’s Diamond V1.9) and I got 100%(complete result on the screen again) but when I did the last instruction of updating the ROM via MicroSD(to restart the device), my phone goes off and I can’t open anymore..
Please I need help..
Related
Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?
I ran the Hard-SPL on my HTC and it worked as it should. I'd say give that a shot, THEN try flashing the ROM of your choice.
-Mc
Problem is, when I run hard spl it expects activesync to be running, but in bootloader mode AS doesnt connect so Hardspl wont load =/
- Disable activesync usb connections
- Connect to bootloader with mtty and type the following commands to know your CID and Model ID:
Code:
Cmd>task 32
Cmd>info 2
Cmd>getdevinfo
Paste the output here, and also tell me which SPL version you have on your device.
Also, does the tri-color shows "RUURUN" or similar in the screen?
You should flash a ROM matching your CID to fix it.
Cmd>task 32
No card inserted
Level = FF
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1*00CS_0HTCE
Cmd>
Device screen says
RUUNBH
KAIS1*0
SPL-1.56.0000
CPLD-8
Flash this ROM, should bring it back to life.
I'm leeching it now, 40% done, also FYI, I've posted on the Official ROM forum new links to most utilities and ROMs hosted on my servers off the rapidshare, to share free of charge.
Ahh, life saver =) Thanks, I'll be sure to add that rom to my list of full Kraiser roms on my web server, now to correctly flash it back with the HTC rom.
Thanks!
Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!
I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?
It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Lukstra said:
Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!
Click to expand...
Click to collapse
ludovich said:
I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?
Click to expand...
Click to collapse
Run the Hard-SPL utility on your PC, and follow the instructions (sticky on this forum)
It will allow you to flash any ROM after that, I've flashed the AT&T Rom, the HTC rom and back and forth, pulling cabs out of the AT&T rom for the items I like (IM utility etc)
Palmore said:
Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?
Click to expand...
Click to collapse
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......
andydempsey said:
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......
Click to expand...
Click to collapse
LIFE SAFVER
nispen said:
It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Click to expand...
Click to collapse
Hi Wouter,
I bought a new Kaiser today (yes now I have two of them ).
I will see if I can dump the Dutch ROM myself and see what happens next.
Thanks for your help anywhy!
- Lucas
Bricked
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.
Vista Problem.
First off, i had the same problem as you so i just found an XP box to use.
Second, even with XP i still managed to **** up because i did not read the directions all the way through. This device is totally different so make sure you read all the directions.
If you have no access to an XP machine then u can just "obtain" a copy of XP and dual boot just for flashing your device.
If you have no idea what I am saying then read some more. the hermes forums have some great information when it comes to flashing via Vista.
For all you guys that just saved between $300.00-$500.00. How about sending POF like %5 or %10 of what he just saved you...
I'm just sayin'
Later, Lew
Have you installed the XP activesync drivers under Vista? The Hermes Wiki mentions somewhere how to do that.
Jabbs19 said:
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.
Click to expand...
Click to collapse
Best Forum Ever
I
I got it working. I had to pull the battery out of the phone to get it out of bootloadr, it was just plain stuck. Then, in Vista, I needed to F8, disable driver enforcement, I replaced the wceusbh.inf in device manager, and relaunched HardSPL and there she was! Now for the BigStorage.
Thanks to all that helped, I will be donating pof for sure
First of all, I wish to say thanks to jockyw2001 for coming up with a solution for all those 1.56/1.57 Tilts. You guys all got a Merry Christmas... you lucky SOBs. Haha
However, there are newer versions of the Kaiser/Tilt coming out with 1.82.00 display versions and the current fix for 1.56/1.57 do not work. They get to the WSOD and stall.
I may be one of the first to have a 1.82.00 phone - I understand that it is the latest version put out by HTC, but I won't be the last. So I am hoping that jockyw2001 reads this thread and will continue to work on finding solutions for these newer versions of the Kaiser.
@jockyw2001
I've got a bounty for you if you can figure this one out... I need to switch from Traiditonal Chinese (which my phone came with) to the WWE ROM to be able to use this phone. Thanks a bunch beforehand!
Michael
Mike some questions:
1. did you try 1.93 (i posted in the original thread)?
2. do you see tri-color with any of the versions you tried?
3. do you see "USB" on the display after a few seconds? If yes with which version?
4. do you see "unrecognized device" after unplug and replug usb cable? or do you see MS sync device in device manager?
5. do you have MTTY up and running?
Note that you should always run the SSPL with USB cable connected!!
Answer to your questions...
jockyw2001 said:
Mike some questions:
1. did you try 1.93 (i posted in the original thread)?
2. do you see tri-color with any of the versions you tried?
3. do you see "USB" on the display after a few seconds? If yes with which version?
4. do you see "unrecognized device" after unplug and replug usb cable? or do you see MS sync device in device manager?
5. do you have MTTY up and running?
Note that you should always run the SSPL with USB cable connected!!
Click to expand...
Click to collapse
A1. I did try 1.93 and I still got WSOD, I lost USB connectivity at that point
A2. No tri-color screen with 1.56, 1.93 or the original HardSPL v1
A3. I do not see "USB" anywhere, the connection goes dead at WSOD
A4. No and no.
A5. I got MTTY 1.42 and tried it, but I'm not sure I'm using it correctly. I'll have to re-read some posts for that.
Thanks for the followup. I'll try and figure out MTTY and get back to you on this.
Michael
good luck to ya..
i am sure it ll just be a matter of time before u get a solution, he is pro and before u know it u will be part of the flashing world here on xda..
the team here on xda rocks..!!
a in yul said:
i am sure it ll just be a matter of time before u get a solution, he is pro and before u know it u will be part of the flashing world here on xda..
the team here on xda rocks..!!
Click to expand...
Click to collapse
Thanks for the well wishes... I have faith in these guys based on the body of work that is available here. Almost every HTC phone ever made has been hacked so I know it's a matter of time before they get this one sorted out.
Michael
Hi dear,
I have the same problem.
During the installation of Hardspl on my new Tilt, the PDA doesn't go in Bootloader mode (3 colors screen) but stop it in a white screen......and I can only make a soft reset to continue to use it.
I have read something about these new version of Kaiser but I need to reflash my Tilt.
Is there someone who know the way to resolve this problem?
I'll post my Boot version shortly....
Thanks and regards
Daniele
I have a 1.57 (from the ROM version in Device Information, right?) Tilt that's new (stock at&t ROM without the customizations). I get the WSOD using both the methods of doing the HardSPL. I was hoping to start fooling around with my new toy!
I'll re-read the forum, but my experience seems consistent with the people in this thread.
TTFN
If I have some time left today I will post another patched SPL.
Oh yeah it *does* cost time ya know ...
You wouldn't happen to be able to pull your existing Traditional Chinese ROM off of that their badboy would you?
I'd really like getting my hands on a chinese ROM for the IME.
Please try the attached file. Follow the instructions exactly!!
The only thing I'd like to know is if display is tri-color and if "USB" appears.
Don't do anything else with it!
- download the attached file
- REMOVE SIM and SD CARDS !!
- connect usb cable
- copy sspl-1.16-test-on-kaiser.exe to your device and run it (leave usb cable connected!)
- screen should be tri-color and after a few seconds "USB" should appear on the display
display is tri-color and "USB" appears
Orange Tytn II French version HSPL 1.81
The test is ok ...
Patrick27 said:
Orange Tytn II French version HSPL 1.81
The test is ok ...
Click to expand...
Click to collapse
Thx, will wait for feedback from the original poster.
Do you actually have trouble running pof's SSPL and my SSPL 1.56 ??
re 1.81
it is ok with 1.56
Chinese ROM
ouminan said:
You wouldn't happen to be able to pull your existing Traditional Chinese ROM off of that their badboy would you?
I'd really like getting my hands on a chinese ROM for the IME.
Click to expand...
Click to collapse
I guess I'll have to go check some threads about how to dump the ROM on the Kaiser. I thought I saw an HTC traditional chinese ROM on one of the links for the Kaiser though. I'll have a look. If not, I'll do my best to dump this bad boy for you.
Michael
Hi there,
I just tried your new test file on my 1.57 Tilt and followed your instructions exactly. It worked. I get the tri-color screen and it says USB on it. It also says:
KAIS1*0
SPL-1.16.Jump
CPLD-0
Thank you for your efforts... no more WSOD!
So, is that it or is there another step? I'm not sure.
TTFN
greggerca said:
Hi there,
I just tried your new test file on my 1.57 Tilt and followed your instructions exactly. It worked. I get the tri-color screen and it says USB on it. It also says:
KAIS1*0
SPL-1.16.Jump
CPLD-0
Thank you for your efforts... no more WSOD!
So, is that it or is there another step? I'm not sure.
TTFN
Click to expand...
Click to collapse
Yes sounds like progress
With this 1.16 do you see "unrecognized device" after unplug and replug usb cable? or do you see MS sync device in device manager?
Can you also try with 1.93 from this post please.
@MikeLim: did u try?
1.16 Did not work...
jockyw2001 said:
Please try the attached file. Follow the instructions exactly!!
The only thing I'd like to know is if display is tri-color and if "USB" appears.
Don't do anything else with it!
- download the attached file
- REMOVE SIM and SD CARDS !!
- connect usb cable
- copy sspl-1.16-test-on-kaiser.exe to your device and run it (leave usb cable connected!)
- screen should be tri-color and after a few seconds "USB" should appear on the display
Click to expand...
Click to collapse
jockyw2001,
I followed your instructions to the letter but still ended up on WSOD. After about 15 seconds the USB connection times out and dies. Back to the drawing board
Michael
Just for info, I noticed this thread whilst looking for a solution to my WSOD, my Kaiser is 1.88.00.00 - (UK Orange) I used the JumpSPL1.56-kais on mine, and it worked fine, Tri-Color - USB, then installed
Also, I can tell you that so far, I have been unable to SIM-unlock via IMEI-Unlock.
MikeLim said:
jockyw2001,
I followed your instructions to the letter but still ended up on WSOD. After about 15 seconds the USB connection times out and dies. Back to the drawing board
Michael
Click to expand...
Click to collapse
After unplug and replug of the usb cable, please check if there is a microsoft usb sync device in device manager
Have you ever tried a hard reset and then run a SSPL?
jockyw2001 said:
Yes sounds like progress
With this 1.16 do you see "unrecognized device" after unplug and replug usb cable? or do you see MS sync device in device manager?
Can you also try with 1.93 from this post please.
@MikeLim: did u try?
Click to expand...
Click to collapse
Let's see... when I unplugged the USB cable and re-plugged it, Vista detected a new device and started installing a USB Sync driver. I think it finished. Actually Windows Update decided there was a new HTC Sync driver available for me, but it didn't successfully install. I'll try the next step.
TTFN
Hi. There is something wrong with my phone. When i tried make phone call. It stopped responding. After reset it goes to four color screen with serial word on the bottom. I never flashed this mobile. Now when I try connect to vista it shows massage Usb device Not recognized, same on xp, but serial changes to usb. Please Help
first of all, i'm not an expert
but there are some threads in this forum about it. the only thing i can explain is:
that you're stuck in the bootloader,
the usb vs serial thingie, is that vista makes any usb device like a serial one..
try checking the spl threads and 'stuck' keywords
sorry can't be of more assitance...
anduh, keep calm and relax.. there's a lot of knowledge here.
so keep breathing and don't go paranoid..
gl
you might want to provide us with some more info,
rom version?, if it sais anything more in the RGB screen
and 1 more thing.. tried removing the battery for at least 1 minute.. / removing sd / simcard
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
podhal said:
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
Click to expand...
Click to collapse
hi podhal,
1) go to settings of activesync and uncheck 'allow USB connections'
2) or just to make sure, go to task manager and kill the process 'rapimgr.exe' and 'wcescomm.exe'
3) download mtty from here: http://forum.xda-developers.com/attachment.php?attachmentid=71806&d=1203597568
4) connect your cable to your kaiser-- it should say 'USB' and not 'Serial' at the bottom
5) choose 'USB' in the drop down list of ports and click 'OK'
6) on the mtty screen press enter key and you should get a cmd>
7) type in 'boot' (without the quotes) and press enter. If it doesn't boot up, paste the output here. DO NOT EXPERIMENT WITH MTTY AND TYPE ANY OTHER THING AS THIS CAN MAKE YOUR PROBLEMS WORSE.
EDIT: do this on you xp machine and not on vista!
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
podhal said:
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
Click to expand...
Click to collapse
good for you now read and go inside the wonderful world of flashing ROMs, heheh
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
StealthNet said:
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
Click to expand...
Click to collapse
Try the frankenkaiser then It's pretty *safe* if you know what you're doing-- did it 3-4 times because I was trying to wipe out bad blocks. Make sure you have the right radio though and an old hardspl before you use it jocky patched the new spls to ignore task 2a command.
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
StealthNet said:
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
Click to expand...
Click to collapse
well I had 3 bad blocks before, but the problem that I had is my ROM area is writing to that blocks and what's unlucky is the critical parts of the ROM is written there (bad blocks are common, but of all the places.. sheesh) that makes my kaiser just reboot indefinitely. So-- what I did was task 2a and it removed only one, but it was enough to get me flashing flawlessly to any ROM
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
StealthNet said:
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
there is in step 3 task 2a which completely *bricks* the phone. But as it said, you would go through oemsbl which is the radio bootloader and not the spl (os bootloader) anymore since it's wiped out already. Read the whole thread before doing it, it's not for the faint-hearted
StealthNet said:
Nice to know!
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
spot on but you need to make sure the drivers are there. After task 2a it would detect your kaiser as new hardware etc., so you need to still install the qualcomm drivers from that thread.
Thanks for the help! I have a XP machine set up just to do that
Ok, let´s do it.
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
sorry mate, just saw your reply.
Maybe you're replugging it too fast, I had that problem also. It kinda takes time before you get it but you're right on track if you ran step 6 with the output
EDIT: I think I know what you did wrong.. I remember that problem before. Are you running the frankenkaiser unbricker radio from hell? if you don't have the radio 1.65.17.10 that won't work. You should ask jocky for the right frankenkaiser unbricker for your radio.
check you later StealthNet, it's 2am and I got to go work in 6 hours. Ta!
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
if it's not recognized, try installing active sync again "to load usb drivers", and try again
You incorrectly installed the drivers most likely.
But before you use Franken, you need to be sure you are using one compatible with your OEMSBL & Vboot version.
What was your last radio & rom version?
GSLEON,
I PMed Jocky and, unfortunately, I did it wrong. When I read the procedure to use Frankenkaiser, I mistakenly assumed that, since task 2a wipes out the phone, the radio version wouldn't matter.
In fact, Jocky explained to me that it really does, and that Frankenkaiser is tailored to be used with radio from hell only.
My last ROM and Radio version were the ones based on the latest Dutty's (radio 1.65.16.25).
My attempt to "task 2a" my phone was my last attempt trying to solve my colored brick (booting into bootloader everytime I turn on the phone). I think this is being caused by bad blocks into bootloader or radio area.
Hopefully, I'll be able to get out of the hard brick (task 2a) and it will solve my colored brick problem
In fact, if it does work, I think it will be usefull for lots of kaiser users (last time I accounted at least 4 ppl with the same problem).
Thanks for the help!
Hello,
Today i bought the kaiser and wanted to rom flash it to 6.1
My plan is to flash it to L26KDTLB6 (http://forum.xda-developers.com/showthread.php?p=2574491&posted=1#post2574491) i've followed the instructions here : http://forum.xda-developers.com/showpost.php?p=2261226&postcount=2
and the flash was in progress but cancelled after 14% due to communication problems (????)... now when i resettred my kaiser i see this weird red green blue and white screen.
I am terribly worried i might have ruined my kaiser even before really using it.
I am begging you for help.. i would appreciate any kind of help from you guys.
Thank you so much
MIke.
Wow! Sounds like you are in deep doodoo. I had almost an identical problem last night trying to flash ROMeOS 4.7. I went and read the stickies at the top of this forum and was back up running in no time.
loserp3 said:
Hello,
Today i bought the kaiser and wanted to rom flash it to 6.1
My plan is to flash it to L26KDTLB6 (http://forum.xda-developers.com/showthread.php?p=2574491&posted=1#post2574491) i've followed the instructions here : http://forum.xda-developers.com/showpost.php?p=2261226&postcount=2
and the flash was in progress but cancelled after 14% due to communication problems (????)... now when i resettred my kaiser i see this weird red green blue and white screen.
I am terribly worried i might have ruined my kaiser even before really using it.
I am begging you for help.. i would appreciate any kind of help from you guys.
Thank you so much
MIke.
Click to expand...
Click to collapse
Sounds like you did not HardSPL. The tri color screen you are seeing is called bootloader. It's not as scary as it might seem at first. When you connect yoru device to your computer does it still show the letters "USB" at the bottom? If so, try flashing the stock rom for your device and see if that will fix your problem. After that be sure to make sure you've properly hardspl'd your device before flashing anything else.
loserp3 said:
... i see this weird red green blue and white screen...
MIke.
Click to expand...
Click to collapse
HOW COME YOU KNOW HOW TO WRITE BUT YOU CAN'T READ?
geez...
I had the same problem once. I remember I solved it that I first flashed it back to the OEM that came with it, and then flashed it again. It worked. Hard SPL and CID unlocker helped being that the phone was locked.
If you dont have OEM OS you can always find one here, just use the Search button.
Secondly, you have to follow the steps exactly as instructed because those are the only way to successful flashing. Are you sure that you didnt overlook one of the steps?
Pay special attentiton to the 2nd Q&A and also other Q&A being that there are all the answers.
Happy flashing mate.
Hello all,
I was able to revert back to hTC'S 6.1 rom...So everything was back to normal.
The thing is, i really want to make the kaiser look good with the d3d driver and the touchflo 3d, I'll give the http://forum.xda-developers.com/show...=1#post2574491 rom one more shot this time ill use
SSPL-KAIS.exe (is that ok ?? will that prep my device for rom flashing ??? )
is there another cooked rom that has the touch flo 3d and the d3d drivers ???
appreciate your help
MIke.
loserp3 said:
Hello all,
I was able to revert back to hTC'S 6.1 rom...So everything was back to normal.
The thing is, i really want to make the kaiser look good with the d3d driver and the touchflo 3d, I'll give the http://forum.xda-developers.com/show...=1#post2574491 rom one more shot this time ill use
SSPL-KAIS.exe (is that ok ?? will that prep my device for rom flashing ??? )
is there another cooked rom that has the touch flo 3d and the d3d drivers ???
appreciate your help
MIke.
Click to expand...
Click to collapse
Do NOT flash another rom until you have hard spl'd your device. Make sure you check out the thread at the top of this forum, which you already sited once. You should also consider sim/security unlocking your device as well. You can ONLY use jumpspl to put hardspl on your device. Absolutely do not start flashing roms until you can enter bootloader and next to spl: see "hard spl" somewhere in the title.
Hi
Ok, here's what i've done to prepare the device
1) i ran kaiser-HardSPL.exe and loaded the nbh that came with it
2) I copied SSPL-KAIS.exe to the kaiser and ran it
thats it... i didn't however see hard spl in the title.. i did see JUMPspl though
loserp3 said:
Hi
Ok, here's what i've done to prepare the device
1) i ran kaiser-HardSPL.exe and loaded the nbh that came with it
2) I copied SSPL-KAIS.exe to the kaiser and ran it
thats it... i didn't however see hard spl in the title.. i did see JUMPspl though
Click to expand...
Click to collapse
you are so making this too hard on yourself. Follow these directions to the letter and you'll be fine:
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
If you have problems with the above process, try this:
1a. download the attached files
1b. pull out the battery and reinsert it (this step *is* important)
1c. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
Notes:
With the JumpSPL you should *not* flash radio roms, OS roms or full roms. The JumpSPL is only needed to flash a HardSPL (or SPL)
the link to the thread in which this came from is here:
http://forum.xda-developers.com/showthread.php?t=396922
Having just redone this this morning to revert back to 3.29, I can confirm that it works.
In the future, please don't start a thread for this type of porblem. We all starte out by reading. I've been a part of this forum for 3 years and learned all I have from just reading and asking questions that could not otherwise be answered.
loserp3 said:
Hi
Ok, here's what i've done to prepare the device
1) i ran kaiser-HardSPL.exe and loaded the nbh that came with it
2) I copied SSPL-KAIS.exe to the kaiser and ran it
thats it... i didn't however see hard spl in the title.. i did see JUMPspl though
Click to expand...
Click to collapse
you did not read the instructions correctly. Try reading them again.
It says:
How to Install 3.2x.Hard SPL:
1. Plug the device into your PC
2. Copy Jump/Soft to your device. use JumpSPL If you have the "White Screen" issue, if you don't, you can use SSPL-KAIS.exe.
3. Take out your SD card & SIM Card.
4. Run Jump/Soft SPL on your device
5. Wait for the bootloader screen to appear and "USB" to show.
6. Right-click activesync, go into connection settings and ensure Allow USB Connections is unchecked
7. Unplug your device from the USB port, wait 5 - 20 seconds, plug it back in.
8. Run KaiserCustomRUU.exe and flash the SPL
You are stopping at step 5. Perform steps 6, 7, & 8. After that time you can soft reset the device while holding down the camera button (that will take you to the tri colored bootloader screen) and it will say "hardspl" if you have done it correctly.
If you don't read more closely you WILL break your phone and nobody here will be able to help you. These procedures are easy enough to follow if you take your time and read. I only say this to save you a great deal of frustration when your phone dies later.
Also, remember in the future that all the information you are seeking is readily available if you look for it. Dont' expect someone to GIVE you the answer, and please please please....post your questions in a thread that is already around rather than starting a new one!
@ Scothua
like the way you think . . .
scotchua,
Thank you for your assistance. i've finally upgraded my rom.
thank you all.
Hi ! I have a problem with my Kaiser ! The screen is black, the device doesn't turn on ! But when i hold the power key & soft reset hole at the same time,
green light comes on, but the screen stays black ! Is there a way to make my kaiser working ? (Sorry for my english)
Remove battery and then press power button 30 seconds or more.
Worked for me.
Assface said:
Remove battery and then press power button 30 seconds or more.
Worked for me.
Click to expand...
Click to collapse
it doesnt work ! I think there is a problem with spl , because this problem appears after unsuccessful hard spl installing ! I don know how to fix this
IP13 said:
Hi ! I have a problem with my Kaiser ! The screen is blank, the device doesn't turn on ! But when i hold the power key & soft reset hole at the same time,
green light comes on, but the screen stays blank ! Is there a way to make my kaiser working ? (Sorry for my english)
Click to expand...
Click to collapse
Not trying to oversimplify things, but is the device fully charged? Did you have any problems during the flash? Which SPL did you flash? Have you tried a hard reset? Can you get to the bootloader screen to verify the version of SPL installed vs. the version you tried to install?
Just a few questions to help us try to figure out what is going on. Take care!
krouth said:
Not trying to oversimplify things, but is the device fully charged? Did you have any problems during the flash? Which SPL did you flash? Have you tried a hard reset? Can you get to the bootloader screen to verify the version of SPL installed vs. the version you tried to install?
Just a few questions to help us try to figure out what is going on. Take care!
Click to expand...
Click to collapse
The device is fully charged ! The problem was when I tried to install hard spl ...the screen stuck and I made a reset ,after this the phone ca not be turned on and all I see is green light.
I can not get to bootloader screen , when i try to turn on the device the screen i black (blank) but the green light is on
IP13 said:
The device is fully charged ! The problem was when I tried to install hard spl ...the screen stuck and I made a reset ,after this the phone ca not be turned on and all I see is green light.
I can not get to bootloader screen , when i try to turn on the device the screen i black (blank) but the green light is on
Click to expand...
Click to collapse
How are you trying to get to the bootloader screen? Have you fully read through this thread:
http://forum.xda-developers.com/showthread.php?t=533976
Finally, I would recommend downloading the original ROM and installing it. The ROM for the Tilt is here:
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
That is straight from HTC's website, and you might look to see if your specific phone is there. You should be able to download it, connect your phone with the USB cable and run the downloaded file from your computer to bring your phone back to it's original state.
If that works, I would then re-read the link above thoroughly and give it another shot. Hope this helps!
krouth said:
How are you trying to get to the bootloader screen? Have you fully read through this thread:
http://forum.xda-developers.com/showthread.php?t=533976
Finally, I would recommend downloading the original ROM and installing it. The ROM for the Tilt is here:
http://www.htc.com/us/SupportDownload.aspx?p_id=67&cat=2&dl_id=94
That is straight from HTC's website, and you might look to see if your specific phone is there. You should be able to download it, connect your phone with the USB cable and run the downloaded file from your computer to bring your phone back to it's original state.
If that works, I would then re-read the link above thoroughly and give it another shot. Hope this helps!
Click to expand...
Click to collapse
Active sync doesnt recognize my Kaiser!
IP13 said:
Active sync doesnt recognize my Kaiser!
Click to expand...
Click to collapse
When you try to run the original HTC ROM installation program (from my previous post) with your phone connected - does it recognize your Kaiser?
krouth said:
When you try to run the original HTC ROM installation program (from my previous post) with your phone connected - does it recognize your Kaiser?
Click to expand...
Click to collapse
no,it doesnt recongnize my kaiser ! when I connect my kaiser via USB Windows says that i have conected a "ZTE USB Modem 6000 CDMA 1x"
IP13 said:
no,it doesnt recongnize my kaiser ! when I connect my kaiser via USB Windows says that i have conected a "ZTE USB Modem 6000 CDMA 1x"
Click to expand...
Click to collapse
I am not asking what Windows thinks you have connected, or whether or not ActiveSync sees the device. What I am asking is: When you run the original HTC ROM installation program:
"RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe"
downloaded from HTC's website, is that program able to see your phone and go through the installation process?
IP13 said:
no,it doesnt recongnize my kaiser ! when I connect my kaiser via USB Windows says that i have conected a "ZTE USB Modem 6000 CDMA 1x"
Click to expand...
Click to collapse
Uninstall Ur Active synce And Install Again .
Then Put Ur Phone In Bootloader Mode I Hope Work Fine
CHK And Post Result
krouth said:
I am not asking what Windows thinks you have connected, or whether or not ActiveSync sees the device. What I am asking is: When you run the original HTC ROM installation program:
"RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe"
downloaded from HTC's website, is that program able to see your phone and go through the installation process?
Click to expand...
Click to collapse
I cant install this rom because it shows me an error : "ERROR [260] CONNECTION
The Update Utillity cannot connect your PDA Phone . Please check that your USB cradle/cable is connected properly between the PC and your PDA phone .
Chech the following :
1.The PDA Phone is connected to the USB cradle/cable.
2.The USB cradle/cable is connected to the PC "
I have allready checked the cable (it works with my other PDA)
delower10 said:
Uninstall Ur Active synce And Install Again .
Then Put Ur Phone In Bootloader Mode I Hope Work Fine
CHK And Post Result
Click to expand...
Click to collapse
I cannot acces bootloader mode , when I am pressing keys to acces bootloader mode the phone screen is still black /blank .
IP13 said:
I cannot acces bootloader mode , when I am pressing keys to acces bootloader mode the phone screen is still black /blank .
Click to expand...
Click to collapse
To access bootloader, you should hold down the camera button (on right side of phone) and the use the stylus to press the reset button (on bottom of phone.) When the phone goes blank, release the camera button.
When you do this, do you still get the blank/black screen?
Also, did you follow EACH step in the following thread:
http://forum.xda-developers.com/showthread.php?t=433835
krouth said:
To access bootloader, you should hold down the camera button (on right side of phone) and the use the stylus to press the reset button (on bottom of phone.) When the phone goes blank, release the camera button.
When you do this, do you still get the blank/black screen?
Also, did you follow EACH step in the following thread:
http://forum.xda-developers.com/showthread.php?t=433835
Click to expand...
Click to collapse
Yes ! I also get the blank screen after following all this steps !
IP13 said:
Yes ! I also get the blank screen after following all this steps !
Click to expand...
Click to collapse
I am not sure.... I have done some searching and ran across this thread:
http://forum.xda-developers.com/showthread.php?t=423486
It has numerous posts about problems people have experienced flashing - maybe you might get some insight there - or at least post your question there where more people might be monitoring the thread. Good luck!
Please take your issue to the right place, better than open a new thread, I sugest
http://forum.xda-developers.com/showthread.php?t=433835
Your situation should be taken by the right guys, not just gessing if this or that might solve the situation, male a post there
Also have a look at the sticky on the top, try to get Dave Shaw help
THx I will try to ask there ....
Fanning the flames.
Okay if you can't access the boot loader then you need to go higher up. I think the chain is Radio Rom, then SPL, then OS. Basically your SPL is gone, that is why your screen is black and you can't get into the boot loader --- cause its gone. So no duh, it can't load the OS. So, your only hope is that your radio rom is working so you can access the phone via cmd interface programmed within it.I really don't know what i'm talking about, but I've bricked my phone too and with some guidance (er explicit instructions in chat) I was (er she was) able to fix it [my situation was far more complicated with a "security locked" device, and a "radio from hell"]. Your key words are frankenkaiser. which you can find here:
http://forum.xda-developers.com/showthread.php?t=394584
Good luck, if you can get into the oemsbl I'm sure your in business. If your feeling nervous bust out the paypal and head to irc.freenode.org #xda-devs {albeit someone will likely help you without the donation but for real your going to hold someone up for an hour or two you should throw them atleast 20$ to save u 200$ }
tyler51773 said:
Okay if you can't access the boot loader then you need to go higher up. I think the chain is Radio Rom, then SPL, then OS. Basically your SPL is gone, that is why your screen is black and you can't get into the boot loader --- cause its gone. So no duh, it can't load the OS. So, your only hope is that your radio rom is working so you can access the phone via cmd interface programmed within it.I really don't know what i'm talking about, but I've bricked my phone too and with some guidance (er explicit instructions in chat) I was (er she was) able to fix it [my situation was far more complicated with a "security locked" device, and a "radio from hell"]. Your key words are frankenkaiser. which you can find here:
http://forum.xda-developers.com/showthread.php?t=394584
Good luck, if you can get into the oemsbl I'm sure your in business. If your feeling nervous bust out the paypal and head to irc.freenode.org #xda-devs {albeit someone will likely help you without the donation but for real your going to hold someone up for an hour or two you should throw them atleast 20$ to save u 200$ }
Click to expand...
Click to collapse
Thx man , appreciate this !!