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.
Related
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
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..
i am really stuck here after i upgraded my o2 xda exec to ur rom. it took too much battery and took me ages to charge it. however, this is never the issue. what happened was that my phone went off battery and couldnt make it charge or even connected to the pc.
it actually charges when i plug but without the orange light which indecates that it is charging.
Plus whenever i try to connect it to pc it says uknown device. even when i switch to bootloader mode it still says unknown device. therfore i cant flash a new rom. the battery is new and the device is O2 Xda exec but is also as new.
pls pls anyone, sort me out.
Moe
Mo0oe said:
i am really stuck here after i upgraded my o2 xda exec to ur rom. it took too much battery and took me ages to charge it. however, this is never the issue. what happened was that my phone went off battery and couldnt make it charge or even connected to the pc.
it actually charges when i plug but without the orange light which indecates that it is charging.
Plus whenever i try to connect it to pc it says uknown device. even when i switch to bootloader mode it still says unknown device. therfore i cant flash a new rom. the battery is new and the device is O2 Xda exec but is also as new.
pls pls anyone, sort me out.
Moe
Click to expand...
Click to collapse
Welcome to the forum
I would recommend to follow this instructions on the Wiki: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Charge your battery at 100%
And don´t forget to vote!
Good luck,
I had similar experience with this ROM even after installing everything successful, and good use of ROM for about 7-10 days, not sure why and thought am the only one experienced this. The phone simply went off (i remember using it the previous day night to check mails). No display, it wont indicate wehther it charging, hard reset or softreset does not do anything etc etc
I have put the Uni in Bootloader mode, did a DOC format and flashed the ROM again, it worked and working so far.
Remove SIM and SD Card from Uni and it should recognise the Uni when connected to PC. Its better to use a XP machine as Vista need a separate proces which you can find in this forum by searching.
Please Read wiki and proceed as appropriate to your device condition. The detail on how to do DOC format is in there in wiki
All the best
stilll stuck with my uni!!!
rbalu72 said:
I had similar experience with this ROM even after installing everything successful, and good use of ROM for about 7-10 days, not sure why and thought am the only one experienced this. The phone simply went off (i remember using it the previous day night to check mails). No display, it wont indicate wehther it charging, hard reset or softreset does not do anything etc etc
I have put the Uni in Bootloader mode, did a DOC format and flashed the ROM again, it worked and working so far.
Remove SIM and SD Card from Uni and it should recognise the Uni when connected to PC. Its better to use a XP machine as Vista need a separate proces which you can find in this forum by searching.
Please Read wiki and proceed as appropriate to your device condition. The detail on how to do DOC format is in there in wiki
All the best
Click to expand...
Click to collapse
orb3000 said:
Welcome to the forum
I would recommend to follow this instructions on the Wiki: http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Charge your battery at 100%
And don´t forget to vote!
Good luck,
Click to expand...
Click to collapse
thanks to u both lads for replying but unfortunately i am still stuck. i tried all the ways u told me abt and tried wiki. Apparently, so many ppls have the same problem but no clear way for the solution yet. both of my computers cant recognise it!!!
i really need ur help stilll in this and u can help me step by step through msn messenger if this is convenient to any of u guys.
rbalu72 said:
I had similar experience with this ROM even after installing everything successful, and good use of ROM for about 7-10 days, not sure why and thought am the only one experienced this. The phone simply went off (i remember using it the previous day night to check mails). No display, it wont indicate wehther it charging, hard reset or softreset does not do anything etc etc
I have put the Uni in Bootloader mode, did a DOC format and flashed the ROM again, it worked and working so far.
Remove SIM and SD Card from Uni and it should recognise the Uni when connected to PC. Its better to use a XP machine as Vista need a separate proces which you can find in this forum by searching.
Please Read wiki and proceed as appropriate to your device condition. The detail on how to do DOC format is in there in wiki
All the best
Click to expand...
Click to collapse
how do i do the DOC format. i searched everywhere pretty much but couldnt figure out how to do it!!
pls let me know. cheers!!!
Mo0oe said:
how do i do the DOC format. i searched everywhere pretty much but couldnt figure out how to do it!!
pls let me know. cheers!!!
Click to expand...
Click to collapse
hi
1.) first you need to download mtty utility, here is the link http://forum.xda-developers.com/download.php?id=9864
2.) on PC go to activesync and uncheck "allow USB connections"
3.) Then go into bootloader mode (light button+power button and soft reset)
4.) On PC open mtty utility / software.
5.) On PC select USB from the "port" drop-down on the upper left corner of the dialog box and hit OK.
6.) On PC you see a blank white screen. Press enter to get "USB>"
7.) On PC type "set 14 0" and hit enter. You will see some gibberish on the mtty utility which will again be suffixed by "USB>"
8.)the type in "task 28 55aa" (try not to copy/paste this because mtty sometimes doesn't recognise it if it is pasted)
9.) you will se WAIT, so wait until it is finished
10.) unplug the usb cable, and re-plug it into the same port
now you are still in bootloader mode, now flash the new ROM, remove the
usb cable and do a hard reset
I hope i could help
damir-bosna said:
hi
1.) first you need to download mtty utility, here is the link http://forum.xda-developers.com/download.php?id=9864
2.) on PC go to activesync and uncheck "allow USB connections"
3.) Then go into bootloader mode (light button+power button and soft reset)
4.) On PC open mtty utility / software.
5.) On PC select USB from the "port" drop-down on the upper left corner of the dialog box and hit OK.
6.) On PC you see a blank white screen. Press enter to get "USB>"
7.) On PC type "set 14 0" and hit enter. You will see some gibberish on the mtty utility which will again be suffixed by "USB>"
8.)the type in "task 28 55aa" (try not to copy/paste this because mtty sometimes doesn't recognise it if it is pasted)
9.) you will se WAIT, so wait until it is finished
10.) unplug the usb cable, and re-plug it into the same port
now you are still in bootloader mode, now flash the new ROM, remove the
usb cable and do a hard reset
I hope i could help
Click to expand...
Click to collapse
hey,
thanks man. i got my uni back on track now. u r the best. thanks to everybody here. i am loving this forum.
thanks again,
moe
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?
I'm normally good with stuff like this ^_^
Not today though
I promise, I followed the instructions to the letter, trying to install WM 6.5 on my phone (S710). I did the USPL thing first, then basically did the exact same thing with the files I got from the WM6.5 "Official v1.0" thread. Is that the right version of WM 6.5?? I'm a bit lost. So I feel like I did the USPL stage twice.
Now here's where things get weird.
When I get to the RUU stage, ready to install - activesync stops recognizing the phone. Says it's not connected. The RUU however sees the phone, but shows blank for the current installation. I press 'update' and both the phone and the RUU go to 100% in about 2 seconds (so obviously it's not doing much).
I reboot the phone and it's like nothing ever happened. Back to my crappy version of windows (infested with my stinky network's own software).
Have I given enough info? What am I doing wrong? Should I start again from the beginning? If so which files should I have and like I said :'( what am I doing wrong?
Epic love and hugs to anybody that can help
x
i've had a problem similar with this. make sure the uspl is done properly. and you must run SDA_ApplicationUnlock.exe first. then uspl: uspl_116_jockyw.bat, after all done, phone will have black screen, run ROMUpdateUtility.exe from uspl folder. (the tutorial is in the archive of uspl). aftel all that install new rom. i have wm6.5 official v1.0 too, work fine.
oh, you may try to start flashing from bootloader(turn off phone, keep the camera button pushed, and insert usb cable)
fuggerboo said:
I'm normally good with stuff like this ^_^
Not today though
Click to expand...
Click to collapse
MS has added "exchanced ...." checkbox in USB to PC connection - just disable it (uncheck).
when checked - works only with synce on linux but not with activesync on XP
m32