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
The issue is back, I recently bought a new device and I cannot HardSPL it. Many ppl are having this problem. Is it cause the device is new?? Can someone think of a way to fix it?
Related Links:
HardSPL will not install - WHITE SCREEN: SOLVED - http://forum.xda-developers.com/showthread.php?t=354061
HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free) - http://forum.xda-developers.com/showthread.php?t=334679
Someone?????????????
xmoo said:
The issue is back, I recently bought a new device and I cannot HardSPL it. Many ppl are having this problem. Is it cause the device is new?? Can someone think of a way to fix it?
Related Links:
HardSPL will not install - WHITE SCREEN: SOLVED - http://forum.xda-developers.com/showthread.php?t=354061
HTC Kaiser Hard-SPL v1 - CID Unlock & Flash any ROM to your device (4 free) - http://forum.xda-developers.com/showthread.php?t=334679
Click to expand...
Click to collapse
Are you saying the info at:m http://forum.xda-developers.com/showthread.php?t=354061 does NOT fix the problem?
A friend of mine in Los Angeles had the same problem with his boss' new Tilt but was able to get it fixed with that information. I think I read somewhere that Tilts made withina certain time frame and with certain serial numbers are subject to this phenomenom. Sorry, can't point you to the exact forum.
JPIndustrie said:
MikeLim/JockyW,
I think I have the same exact issue. I'm on my 3rd North American ATT OEM Tilt, and I have the same exact symptoms that MikeLim talked about.
Tried your fix (with the SIM/MicroSD removed) and all i get is the WSOD, with ActiveSync timing out, and "windows Mobile-based device #7" in Device manager (with the same exact ID's).
Any ideas?
Thanks
Click to expand...
Click to collapse
Wonder_Man said:
I am having the same problem, when using JumpSPL it simply hangs at the white screen, it never continues to the tri-color screen. From what I read, only JumpSPL needs to be on the phone, then loaded through the phone menu. I get a white screen, and disconnected on activesync. Is it possible to continue install (disconnect usb,reconnect usb, installing HardSPL) without seeing the tri-color screen? Or am I babbling like my mother on a long distance call?
Click to expand...
Click to collapse
I posted that in the old thread yesterday, I recently got my Tilt about 3 weeks ago. I too cannot get past the WSOD. I didn't want to start flashing until I was sure that you could still do it with the WSOD on screen.
Same problem here and mine is about 2 weeks old.
Anyone with a brand new tilt(less than a few weeks old) have success getting past the white screen?
SPL v1.5 ???
Same for me white screen ... 09/08/07 RB01/EU
The new device I have bought is diffrent than the one I bought 2 days after it's release.
The new one is a bit thinner, The keyboard keys are slighter (No click sounds). Video is working better (NOT FULLY). So think that is the issue, new device new spl needed.
Ok so we need wait the new SPL
darko91 said:
Ok so we need wait the new SPL
Click to expand...
Click to collapse
Think so, or we doing something wrong (Don't think so, i've SPl'd like 5 devices the same way, but this one is special).
I once posted SSPL 1.93 for testing here (no security bypass yet, only to see if it runs and if you can connect by mtty). Someone should try it.
When i use your i have the Tricolor stuff ...
and
KAIS130
SPL-1.93.0000
CPLD-8
But not the USB on the bottom
But i'm @ work i cant test mort now ...
That's at least something. And you didn't have tri-color screen with any of the other SSPLs (pof, my 1.56, etc) ?
No with the 1.56 i had the White screen ... Nice white anyway
Try the attached SSPL. It is again a test version, only to see if it shows tri-color and if there is USB connectivity. Don't try to flash HardSPL with it.
1. copy it to your device and run it
2. tri-color screen should be shown and after a moment the word "USB" should appear
3. unplug and replug USB cable and see if you can connect with MTTY or if that is a problem check in device manager if there is a USB Microsoft Sync device at the end of the devicelist
EDIT: I just fixed a small bug. The attached version works fine on my Kaiser.
why cant try flash the spl ? is it dengerous ? ...
darko91 said:
why cant try flash the spl ? is it dengerous ? ...
Click to expand...
Click to collapse
DON'T FLASH IT
Only test if this SSPL (aka JumpSPL) shows tri-color and offers a working USB.
Once that is confirmed I can add the security bypass patches so you can flash a HardSPL.
Im finely back to home ...
I try your SSPL ... but allways same thing ... stuck on Trycolor no USB on the bottom ...
darko91 said:
Im finely back to home ...
I try your SSPL ... but allways same thing ... stuck on Trycolor no USB on the bottom ...
Click to expand...
Click to collapse
What version is your installed SPL ?
If you start it, make sure that the USB cable is connected!
That work USB is ok !
I made a mystake i have start the program without the USB plug ...
Windows say to me after the replug new device found ex..... .....
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..
Attached you find all you need to flash cooked ROMs on your Dash3G (Maple).
The sspl/hardspl are confirmed to work fine on the HTC Maple platform (Dash3G, SNAP S520, SNAP S521). Any phone that says MAPL1XX under the battery should work just fine with the sspl and hardspl. This has been tested by oOkBa yesterday night. His cooked roms flash extremely fast and he noticed no problems except for the splash screens. Apparently HTC changed the format slightly. Should be easy to tackle and has nothing to do with the sspl/hardspl.
Now for the bad news ... It will not work on the HTC Cedar platform (GSM/CDMA, HTC Ozone XV6175, Verizon). Running the sspl on an Ozone will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. Please see this post for more info and how you can help.
There are 2 packages both contain a SSPL, HardSPL, patched ROM updater and the original Maple SPL. The first package is based on SPL 1.17 (tested by oOkBa) and the second is based on SPL 1.19 (tested by Gawain1986)
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Dash3G HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "1.17.hard")
5. if you have difficulties to install 1.17 then try 1.19
6. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Maple cooked or original ROM.
Have fun,
JockyW
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
ookba said:
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
Click to expand...
Click to collapse
couldnt of said it better myself..
oo..
my Snap 526 is MAPL110..
should i gib it a shot?
but i need a plan b in case something goes wrong.. any idea how to hard reset the snap with the scrollball?
I have the same mapple, ithink it's ok.
before running this file, do we have to dump the rom? and do we have to use the spl backup kit berfore?
(sorry for all these questions)
First of all, there's really no need to run this yet until there are custom ROMS to flash. If you want to simply test or prep, go for it. I can confirm it works in a MAPL100 so I don't see why any other device with MAPL1XX should be an issue. I will build some factory ROMS as well as some custom cooks in the next days for you guys to play with and test.
see i dont think alot of the new people understand the process.
the spl does nothing more than ENABLE ur device for a rom, thats it!
nothing fantastic, its not a completely diff o.s. on ur device..just preps it for whats to come.
what happend with my device today was a fluke!
i was testing and working at the same time..i could have missed a step, one of my work programs on my laptop could have set something off..i dunno.
Bricking usually isnt a part of getting a SPL for a device..just ALOT of testing. SO now is the another part of the process..the waiting process. Waiting for a rom cooker to successfully establish something, test it, and release it.
in this game..u need patience.
So I;ve been trying this and it seems something is going wrong...
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
It will then refuse to use any driver I try to add to the device.
Any thoughts?
PS. It's a SNAP S521 (MAPL110)
EDIT: Windows XP x64 has the same problem.
Gawain1986 said:
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
Click to expand...
Click to collapse
First, this has not yet been tested on Win7. Second, it should not be necessary to unplug and replug the cable. Try again and just wait a minute or so to allow Win7 to install the driver. Other thing you can do to make sure the driver is already installed is to put the phone in bootloader mode and connect it by usb cable.
ps: it is normal the display turns dark after running the sspl
ok, i understand there are 3 steps. but I would like to know how to do the first one:
dumping my rom.
First I entered the bootload by holding the volume down button and turning the device on...
It said:
Code:
MAPL110
SPL-1.19.0000
MicroP-Maple (LED) v6
ENGID 0x2
PCBID 0x80
PanelInfo 15-0x2
I connected it to the computer and it recognised the Qualcomm phone immediately and settled on the HTC USB Sync driver.
Then I restarted the phone and connected it again, ran auto.bat... it ran SSPL again and I waited.
So after I tried waiting for 5 minutes, WIndows 7 did not see a new device, it stayed with it's normal RNDIS driver.
So I took the plunge and ran the RUU, which told me it could not connect to the phone.
I unplugged the phone and replugged it and it said there was an error regarding the USB device.
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Enter bootloader. If you see "1.17.Hard" the HardSPL is succesfully installed and you can flash any cooked and official roms in the near future.
Fabtwone said:
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Click to expand...
Click to collapse
Gawain1986 said:
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Click to expand...
Click to collapse
Please first try it on WinXP before we draw wrong conclusions.
Good work jocky - nice to see you about again
Thread Stuck.
Dave
jockyw2001 said:
Please first try it on WinXP before we draw wrong conclusions.
Click to expand...
Click to collapse
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Gawain1986 said:
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Click to expand...
Click to collapse
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
To anyone who has problems, please look up your current SPL version.
(press volume down and power on).
Is there anyone who succesfully flashed the HardSPL where the old SPL version was 1.18.00 or higher?
jockyw2001 said:
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
Click to expand...
Click to collapse
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Gawain1986 said:
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Click to expand...
Click to collapse
Try the attached sspl which is based on your v1.19 SPL.
Run sspl.bat (preferrably in XP)
I'm sorry, but the new 1.19 SSPL is not working either. The phone stays in the black screen and both Windows XP x64 and Windows 7 x86 keep telling me the USB device is malfunctioning.
I have had some experience with unlocking my previous Tornado, VOX, Kaiser and X1 and I'm pretty sure I need to see a tri-color scren when invoking JumpSPL.
So maybe that's the problem?