how to install hard spl without windows running in kaiser?
can i use some Mtty commands to make this possible?
this should probably be posted in the threads pertaining to HardSPL, and to answer your question i think not. you have to run the KaisSSPL/JumpSPL in order to temporarily overwrite the SPL on the device. and you cannot just overwrite it by flashing HardSPL as you would a rom or we would have done that from the get go and have it included on every rom.
my kaiser has some problems and can not load windows , thats why i need to change spl and try to use other soft to recover problem.
i have problem with processor communication via I2C with PM7500 chip.
may be i have to brick it firs deleting boot and going to serial connection with processor? (like command task 2a - but in my spl this command not working)
thank you
actualy there is no issue for you.
you can not change spl without WM6.
i've got the same probleme.
let me know if you find a solution.
i thought that my tytn ii was bricked. now is alive. Read "Radio Hell" threads... check in what status is your tytn ii... (obviously at your own risk)....
first try with "solved radio hell thread", but if you erased all by mistake this thread helped me too:
http://forum.xda-developers.com/showthread.php?t=394584&highlight=oemsbl
rumensat said:
how to install hard spl without windows running in kaiser?
can i use some Mtty commands to make this possible?
Click to expand...
Click to collapse
pressing green key not working in 1.93 spl
mtty commands for formating not working with this spl
mtty command don't work for me.
nicx said:
mtty command don't work for me.
Click to expand...
Click to collapse
MTTY should work, just make sure you have unchecked "allow usb connections" in activesync.
rumensat said:
may be i have to brick it firs deleting boot and going to serial connection with processor? (like command task 2a - but in my spl this command not working)
Click to expand...
Click to collapse
which spl version is installed? write down all information shown on tricolor bootloader screen
jockyw2001 said:
which spl version is installed? write down all information shown on tricolor bootloader screen
Click to expand...
Click to collapse
RUUNBH
KAIS130
SPL-3.28.0000
CPLD-8
Serial / USB
rumensat said:
pressing green key not working in 1.93 spl
mtty commands for formating not working with this spl
Click to expand...
Click to collapse
hi,
i had rom radio 1.64.06.04.
for me this command work fine:
Try this from MTTY:
set 16 0
task 8
maybe that's will work for you.
set 16 0 -this command doing nothing
task 8 - reboot unit
at all there is no chance to brick this **** at all
I LIKE TO BRICK THIS **** AND TO START WITH SERIAL DRIVERS
i take off battery in every second when load rom and no chans for me to destroy stupid boot
I remember loading the original HTC ROM when in deep sh*t trouble... no need to have it booted to OS, only to tricolor screen
then you will boot to OS, install SOFT-SPL, then HARD-SPL and your custom ROM, Radio, splash...
i can not boot to Os , i have never seen OS in this unit
rumensat said:
i can not boot to Os , i have never seen OS in this unit
Click to expand...
Click to collapse
when you turn on the device, what do you see? tricolor screen? or white screen? or
you cannot boot to OS even after flashing a stock official HTC rom?
when turn device it is start load windows, after first screen go melodi which i see in rom named LB (low battery), and phone sw off.
i can load any original rom with success, but same story.
i thing problem is in I2C communication between proc and PM7500 chip , register for batt value is nor readable.
thats why i like to remake soft and take off power controll from it, but can not flash hard spl
rumensat said:
when turn device it is start load windows, after first screen go melodi which i see in rom named LB (low battery), and phone sw off.
i can load any original rom with success, but same story.
i thing problem is in I2C communication between proc and PM7500 chip , register for batt value is nor readable.
thats why i like to remake soft and take off power controll from it, but can not flash hard spl
Click to expand...
Click to collapse
Isn't it easier to apply for a warranty replace then?
here in Bulgaria HTC dont have service
Anyway I have seen some note that jocky is going to make the SPL flashable via SD memory card... maybe worth waiting then
BTW have you tried different battery?
Related
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..... .....
May 24th, 2008
FrankenKaiser SPL Loader
This is a fast application image downloader which can download e.g. spl or android to the phone when the phone is in dload mode. This can for example be useful for developers to test a SPL from another device w/o the need to flash them
======================================================
DISCLAIMER: This method involves erasing SPL & OS and requires correct data entry by the user. I will not take any responsibility for any malfunctions and or damages caused by using this method and software.
======================================================
Prerequisites:
- a *security unlocked* HTC MSM7x00 device
- QC diag drivers installed (e.g. MotoQ)
This was tested with a Kaiser, Niki and Wings
Steps are:
1 power down
2 hold green send key and power on, the phone will enter radio bootloader (oemsbl)
3 connect with MTTY (COMn) and type "dload" to put phone in dload mode
4 close MTTY, reconnect USB, run my new downloader in a CMD box, e.g. "./FrankenKaiser-SPL-Loader.exe /dev/com4 SPL1.56-KAIS-unbricker.nb (substitute com4 by the com port of your qc diag driver)
5 hold send key and press soft reset with stylus (on phones like Nike this is not possible, in that case you must add "setboot 1" to step 3 before typing "dload" and in step 7 add "setboot 0" before typing "dload")
6 connect with MTTY (COMn) and type "mw 901708 1 e1a00000"
7 type "cego" (press and hold camera to enter tricolor bootloader mode)
Have fun!
may i be one of the first to say Thank you.
jumpspl, supercid and security unlocker, frankenkaiser .. man you are owesome.
A truly gifted individual and thank you for all your hardwork.
Thanks, Jockyw2000, your work really rocks, but...
OEMSPL did not work for me (HTC Wings)
Ive hold down the green button and tapped the PowerButton=>Boots normal.
Offtopic;
My Question is; Is it possible to "Switch" the GPIO 0x5c (Kaiser SimDoor) from 0 to 1 manually?
Because i want to "port" a KaiserRom over to my Wings, but ive getting trouble with this annoying "Sim Door Open, please close it.Phone shuts down in 10 seconds..." warning.
arpy said:
Thanks, Jockyw2000, your work really rocks, but...
OEMSPL did not work for me (HTC Wings)
Ive hold down the green button and tapped the PowerButton=>Boots normal.
Click to expand...
Click to collapse
Your Wings is not security unlocked, so you can't enter oemsbl that way.
Offtopic;
My Question is; Is it possible to "Switch" the GPIO 0x5c (Kaiser SimDoor) from 0 to 1 manually?
Because i want to "port" a KaiserRom over to my Wings, but ive getting trouble with this annoying "Sim Door Open, please close it.Phone shuts down in 10 seconds..." warning.
Click to expand...
Click to collapse
Afaik that's possible.
Security Unlocked?!?
Ähh...ok...isnt enought to flash your HardSPL?
...but youll give me some hope...now i digg deeper into this phantastic Forum...
Just a quick question Jocky....
How does this differ from using MTTY to upload SPL to our Kaiser?
kyphur said:
How does this differ from using MTTY to upload SPL to our Kaiser?
Click to expand...
Click to collapse
How do you use MTTY to upload a SPL then ?
jockyw2001 said:
How do you use MTTY to upload a SPL then ?
Click to expand...
Click to collapse
I'm asking with all due respect. I haven't done it. To be honest I haven't flashed anything with MTTY since I had my Hermes last year but I was under the impression that we could.
If we can't then you have answered my question as the difference is exactly that!
In the quest for knowledge we all sometimes ask apparently dumb questions...
So with this thing I can make my deviece look as a MSM7500. To boot up HaReT all the time???
kyphur said:
I'm asking with all due respect. I haven't done it. To be honest I haven't flashed anything with MTTY since I had my Hermes last year but I was under the impression that we could.
If we can't then you have answered my question as the difference is exactly that!
In the quest for knowledge we all sometimes ask apparently dumb questions...
Click to expand...
Click to collapse
obviously you can, the RUU uses mtty commands to download the images.
When I run FrankenKaiser-SPL-Loader.exe , WindowsXP closed DOS window with error.
What is wrong ?
WBR !
Sorry, duble.
"mw 901708 1 e1a00000"
what's at address 901708 and why change it to E1 A0?
ma kaiser dead or not please help will donate with paypal 50pounds if you can help
wait ....to resolve this .
gsmhackerns said:
I use hard spl and install radio to unlock my htc tytn bat after this i flash with this rom :RUU_Kaiser_HTC_WWE_1.25.405.0_22.39.82.00.b_1.27.04.15_Test
My phone complete all proces 100% bat after this can not boot or charge no ligh no bootloader as i can see now it have only radio bootloader (oemsbl) and i found and install driver and see in device menager com ports quacom diagnostic interface 6000 and qualcom nmea device...Can you help me to unbrick my kaiser with frankenkaiser spl loader i will donate with paypal you please...pm fuull instuction or can you create for me exe file with all .thanks.wait you.
Click to expand...
Click to collapse
Did you security unlock your device before this happened?
Ta
Dave
DaveShaw said:
Did you security unlock your device before this happened?
Ta
Dave
Click to expand...
Click to collapse
i install hard spl unlock device bat after flash complete 100% my phone always go in oemspl can not go in normal bootloader or power on.
Since it doesnt seem as though you unlocked the phone, just download an oem rom/radio combo for the phone from the operator it belongs on ( IE , if it is an ATT TILT, download from HTC the latest rom off their website JUST for the att tilt )
This should fix you up
DaveShaw said:
Did you security unlock your device before this happened?
Ta
Dave
Click to expand...
Click to collapse
Dave i have same prob...device allready unlocked before flash... no power on, no bootloader mode... on pc recognized like diagnostic.... what can i do?
Frankenkaiser error
I managed to brick my device real good. When I start the device, holding down green send, and run mtty to run the dload command, I get Invalid command : dload. Im in deeper than I bargained for. Whats next?
the0ne.john said:
I managed to brick my device real good. When I start the device, holding down green send, and run mtty to run the dload command, I get Invalid command : dload. Im in deeper than I bargained for. Whats next?
Click to expand...
Click to collapse
What did you do? task 2a?
Are you security unlocked? What SPL do you have?
Thanks
Dave
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!
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?