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
Hi there,
i cant upgrade my phone. i get an error 264.
i even hardresetted the phone and tryed.
when i start the "hardspl.bat" my mobile wants to run a jumper file. but when i press yes the screen turns white the connection brakes and i cant upgrade too.
and when i dont press yes and do nothing the updater starts but its stock at 0% and after some time i get the error o0
what have i done wrong ?
greetings
sluppy
same thing happens here, my usb connection losts while whitescreen loaded, i will try with another computer tomorrow...
by the way bootloader way doenst work, i have tryed several times, several roms, it has just come back from service due to speaker problem...
G4
OS 2.20.7.34
Qtek s200
so i can get into the 3 colored screen if i dont press yes when i am asked if i want so start the jumperspl. if i dont press anything the screen gets into 3 colors. but i get an error on the PC and i can do anything. but it seems that the usb connection is still running.
sluppy said:
so i can get into the 3 colored screen if i dont press yes when i am asked if i want so start the jumperspl. if i dont press anything the screen gets into 3 colors. but i get an error on the PC and i can do anything. but it seems that the usb connection is still running.
Click to expand...
Click to collapse
Please read the thread in my signature...
be patient ~~~ only less than half an hour to complete flashing........
download all needed files first~~~~
What is yr PC oS
I have d same error in win XP and Vista.
Try use win 2000.
I solved my using win2000.
its just not working! i copied the jumperfiles, i plugged the phrophet i run the spl i plugged the propeht in again and when i run the update thing i get an error.
it is me again
it has done today, i hav triyed again with my old notebook at work today and it's succeded, it think my home computer's mainboard have a sumething like usb connection problem.
I will try later with rear USB ports
i tryed it on a nother maschine and its not working. same error. and i 100% did whats described in the threats! every available method
sluppy said:
i tryed it on a nother maschine and its not working. same error. and i 100% did whats described in the threats! every available method
Click to expand...
Click to collapse
not about PCs, read again my thread ... is that you have a G4 device?
go to my signature again. Many successful cases.....................
yes its a g4 and i read ure thread. and tryed it serveal times. but its just not working
sluppy said:
yes its a g4 and i read ure thread. and tryed it serveal times. but its just not working
Click to expand...
Click to collapse
read more
http://forum.xda-developers.com/showpost.php?p=1937273&postcount=103
okay i think i found the error ... i had windows runnin on my mac with a virtuall mashine and it wasnt able to connect virtual windows with the bootloader.
but i got an other error now. if i run hardspl, i everything seems to run find. but its still the old 2.15 hard spl on the prophet even if its supposed to be a 2.20.
do i have to crack some kind of romlock befor? (its a german o2 XDA)
oh okay do i have to unlock the CID? i searched the prophet forum but didnt find anything specific.
-> http://wiki.xda-developers.com/index.php?pagename=Prophet_CID_Unlock is G4 only :/
Hey guys,
i had the same error and i tried just the same one more time, so romupdateutility.exe and it worked!!
error codes and its definition
this might help to define those error codes... got it in one of the files i downloaded from this forum...
sometimes README helps )
Hey guys, I am trying to flash Dutty's newest rom, but im having some trouble...
When I double click the RUU.exe file, I put a check in the checkbox, hit continue. then put another check, hit continue, then I get an error saying:
"Error [200]: Invalid update tool"
"Please get newer update utility"
This is odd because I read on the Wikki that you get this error if you don't have HardSPL, but I do. In fact, I have flashed at least 4 or 5 different roms on this phone. Another thing is that my phone isnt in activesync mode, and for some reason when I try to install activesync (directly from microsoft's website and from the CD that came with my tilt) I get an error saying that it wont install... And another weird thing is that this never stopped it before, I have flashed a rom without it being in activesync with the computer...
When I tried to install Microsoft's activesync directly from their website, I double click the setup.msi file, and then it says :
"preparing installation..."
"The wizard was interrupted before Microsoft ActiveSync 4.5 could be completely installed.
Your system has not been modified. To complete installation at another time, please run setup again.
Click Finish to exit the wizard"
And this happens every time I try it... I have tried redownloading the file and I get the same issue... I even checked to see if maybe I downloaded the wrong version (like the vista version or something) but I downloaded the correct one.
Now, when I try to install activesync from the CD that came with my Tilt, I get an error saying that I need to update my Adobe Flash Player, So i click on the link that it gives me, and I updated it. Even though it is currently up to date, I STILL get this error every time I try, even after restarting my computer.
Any ideas?
put the phone in bootloader and tell me exactly what it says there.
jjb007 said:
Hey guys, I am trying to flash Dutty's newest rom, but im having some trouble...
When I double click the RUU.exe file, I put a check in the checkbox, hit continue. then put another check, hit continue, then I get an error saying:
"Error [200]: Invalid update tool"
"Please get newer update utility"
This is odd because I read on the Wikki that you get this error if you don't have HardSPL, but I do. In fact, I have flashed at least 4 or 5 different roms on this phone. Another thing is that my phone isnt in activesync mode, and for some reason when I try to install activesync (directly from microsoft's website and from the CD that came with my tilt) I get an error saying that it wont install... And another weird thing is that this never stopped it before, I have flashed a rom without it being in activesync with the computer...
When I tried to install Microsoft's activesync directly from their website, I double click the setup.msi file, and then it says :
"preparing installation..."
"The wizard was interrupted before Microsoft ActiveSync 4.5 could be completely installed.
Your system has not been modified. To complete installation at another time, please run setup again.
Click Finish to exit the wizard"
And this happens every time I try it... I have tried redownloading the file and I get the same issue... I even checked to see if maybe I downloaded the wrong version (like the vista version or something) but I downloaded the correct one.
Now, when I try to install activesync from the CD that came with my Tilt, I get an error saying that I need to update my Adobe Flash Player, So i click on the link that it gives me, and I updated it. Even though it is currently up to date, I STILL get this error every time I try, even after restarting my computer.
Any ideas?
Click to expand...
Click to collapse
I can't help with the active sync problem (you don't have vista, do you?) but as for flashing...flash from the sd card http://forum.xda-developers.com/showthread.php?t=336158
P1Tater said:
put the phone in bootloader and tell me exactly what it says there.
Click to expand...
Click to collapse
excuse my noobness , but im not sure what that means
jjb007 said:
excuse my noobness , but im not sure what that means
Click to expand...
Click to collapse
OK, with the phone powered on, press and hold the camera button and insert the stylus in the reset hole until the tri-colored screen comes up. This is bootloader. Tell me what it says there, exactly.
jjb007 said:
excuse my noobness , but im not sure what that means
Click to expand...
Click to collapse
After you put your phone in bootloader mode as P1 said, you will see something like this:
KAIS1*0
SPL-1.93.0000
CPLD-8
Once you make a record of what is displayed, reply back with it.
ok, this is what it says (in the top red box):
KAIS1* MFG
SPL-1.0.OliPof
CPLD-8
Then in the white box it says: "Serial"
jjb007 said:
ok, this is what it says (in the top red box):
KAIS1* MFG
SPL-1.0.OliPof
CPLD-8
Then in the white box it says: "Serial"
Click to expand...
Click to collapse
Since you already have it in the boot loader just keep it there and try to flash it, see if you get any errors that way.
What version of Windows is on your computer?
If your running vista you need the mobile device center, not activesync.
Im using windows XP, I will try flashing while it is in bootloader, I edit my post once I see if it is successful or not.
**It did not work when I tried flashing from the bootloader screen, I got the same error
which rom are you flashing your device with?
I am trying to flash Dutty's newest ROM, and right now Dutty's 3rd or 4th newest one is on my phone.
after you put your device in bootloader, and connected it to the pc, did the word "serial" change to "usb"? and were drivers loaded for the device? there should be a htc usb sync or microsoft usb sync in your device manager
XtreMe_G said:
after you put your device in bootloader, and connected it to the pc, did the word "serial" change to "usb"? and were drivers loaded for the device? there should be a htc usb sync or microsoft usb sync in your device manager
Click to expand...
Click to collapse
Yea, I dont see either of those in my device manager...
Sounds like you're missing the drivers. Need to roll 'em back to the XP drivers.
GSLEON3 said:
Sounds like you're missing the drivers. Need to roll 'em back to the XP drivers.
Click to expand...
Click to collapse
Alrighty... so how do I go about doing that?
jjb007 said:
Alrighty... so how do I go about doing that?
Click to expand...
Click to collapse
You use google or XDA search via google. Try ROM flashing with Vista, etc...
Remember, there is a lot of valid data in Hermes forum as well
jjb, I had the same problem the other night on my home computer with XP. Luckily, I did not have the same problem with my work computer, also with xp. Something happended on the home computer to fcuk up the drivers (i'm guessing, as GSLEON pointed out). I had the same install issues with Activestinc. I had these issues in the past (at least 6 months ago) and was able to finally get Activestinc installed after rebooting multiple times. This time I only tried once before I waited to go back to the office and flash. I'm not sure what to do to rebuild(?) the drivers, but you might try a different computer. Also, my google search (for the 200 error) the other night pulled up a different web site that listed a lot of error codes and what they mean. I'm gonna try and figure out my driver issues with activstinc this weekend and I will post if successful.
ptgptg said:
jjb, I had the same problem the other night on my home computer with XP. Luckily, I did not have the same problem with my work computer, also with xp. Something happended on the home computer to fcuk up the drivers (i'm guessing, as GSLEON pointed out). I had the same install issues with Activestinc. I had these issues in the past (at least 6 months ago) and was able to finally get Activestinc installed after rebooting multiple times. This time I only tried once before I waited to go back to the office and flash. I'm not sure what to do to rebuild(?) the drivers, but you might try a different computer. Also, my google search (for the 200 error) the other night pulled up a different web site that listed a lot of error codes and what they mean. I'm gonna try and figure out my driver issues with activstinc this weekend and I will post if successful.
Click to expand...
Click to collapse
Thanks for the input... im going to try re-installing windows when I get the chance and hopefully that will clear up this driver issue.
rather than going through all the trouble trying to solve this problem, i would just flash using the microsd card
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..
Hi...
I was trying to Upgrade my O2 XDA Exec Rom with Windows Mobile 6.5 by explode. The process went successfully till 99% and after that it ended up with Error. Then I unplugged my pda from the pc and tried to restart the device. I was surprised that the device did not respond to any of the following
Soft Reset
Hard Rest
Boot Loader mode Start (Bulb + Power + Reset)
It is totally blank screen whatever you do.
When I connected the device to the pc with usb cable, a Red Light is shown for 2 seconds and then goes off and a message comes up on the pc that "USB DEVICE NOT RECOGNIZED".
Then I tried to Remove battery from the device for a whole night and the next day morning i did all the above procedures again to get no results.
Kindly Help me out
Thanks
Dinesh Kumaar
I think you have been bricked your device...
dineshkumaar said:
Hi...
I was trying to Upgrade my O2 XDA Exec Rom with Windows Mobile 6.5 by explode. The process went successfully till 99% and after that it ended up with Error. Then I unplugged my pda from the pc and tried to restart the device. I was surprised that the device did not respond to any of the following
Soft Reset
Hard Rest
Boot Loader mode Start (Bulb + Power + Reset)
It is totally blank screen whatever you do.
When I connected the device to the pc with usb cable, a Red Light is shown for 2 seconds and then goes off and a message comes up on the pc that "USB DEVICE NOT RECOGNIZED".
Then I tried to Remove battery from the device for a whole night and the next day morning i did all the above procedures again to get no results.
Kindly Help me out
Thanks
Dinesh Kumaar
Click to expand...
Click to collapse
if it's not recognized, remove the SIM card, the SD card, and on the PC open activesync and disable usb connections. for more info open this link
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
what if the device is bricked
Thanks for your quick reply
Kindly let me know what could be done with the bricked device. Can it be repaired again.
Thanks again
Dinesh Kumaar
dineshkumaar said:
Thanks for your quick reply
Kindly let me know what could be done with the bricked device. Can it be repaired again.
Thanks again
Dinesh Kumaar
Click to expand...
Click to collapse
you have to find another rom and try to flash it to your PDA.
ARE YOU RUNNING windows XP on your PC?
Yes ! I have Windows XP SP2 and Active Sync Version 4.5.0 (Build 5096)
Thanks
dineshkumaar said:
Yes ! I have Windows XP SP2 and Active Sync Version 4.5.0 (Build 5096)
Thanks
Click to expand...
Click to collapse
have you tried to upgrade another ROM, and if you did, is your PDA now working?
I cannot update my rom as my pc cannot recognize my device. is there any other way to update rom?
dineshkumaar said:
I cannot update my rom as my pc cannot recognize my device. is there any other way to update rom?
Click to expand...
Click to collapse
Have you read here?
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader_Serial
Try to reflash with another ROM
Hope it helped
And don´t forget to vote!
I had already done those steps to get no results.
its my badluck.
If you cannot get into bootloader and you have done the steps above, then you cannot flash to another rom.......it would seem you now have a paperweight im afraid
I am still not able to revive my device. I know that it is just due to corrupt bootloader but don't know how to repair it.
If anybody ever has solution for this... kindly let me know.
Regards
Have you tested mtty?
I would recommend to PM a chef on Universal forum
Good luck,
Mtty is not detecting my device
it says can't open usb port
One More thing I have noted is that when I keep the device connected with the pc, at a certain interval of about 10-15 mintues my device's Led shows RED Light for few seconds and then turns off followed by the the "USB device not recognized" on my pc.
I hope this can be used as a hint towards reviving my device.
Regards
have you followed orbs advise above and pm a chef on that section, they maybe able to help. From my knowledge (limited on that device) i ddont think there is any recovery proceedure that you have not tried. Have u downloaded offical wm5 rom and tried it. I know and appreciate that it will probably not work due to corrupt bootloader, but what else is there to do??
To understand more, what did you do PRIOR to trying to flash to 6.5.
Did you hardspl correctly? Had you already flashed to another rom and just felt like flashing to another new rom?? Give us more detail.
Thanks for your reply
I dont know how to PM Chef.
I had used 3 other Rom versions of WM6.1 on my device. They ran very much fine on my device. But When i found WM6.5 xplode, I wished to try that too. But the rom update procedure went successfully till 99% and after that it showed an error that upgrade was not successfull. I pulled out the device and tried to restart if by all methods but I wasnt able to power on at all.
Thanks
Regards
ok, goto the thread that you got the rom off, click the chefs name and you will get a menu there to send pm, do it, he might have seen a similar problem or know how to correct bootloader.
good luck
noup really no...
Is bricked
my bro has bricked an Universal and the same led turns red no power off no bootloar no power it means the flash chip is dead!
Sorry to heard that.
He waits too long for the upgrade it tooks at least 40 minutes
then ERROR... but you know... the batt was died in middle process ( th batt was ****ed up, it say full charged but no! it was on 60 or 50%) then the stupid thing is make a hardreset.. i told him dont hR your device... justa simple reste and reinit the process... and huh! its bricked.
if you are interested on sell your parts
maybe my bro want some parts.
my advice(similar to other people):
1. Charge your batery somehow (in other device or anything else)
2. put your devce in bootloader mode and connect it to pc - it wll be detected like microsoft usb sync
3. use mtty try difrend versions becuse sometimes 1.42 does not detect it properly - read here for what to do with mtty
IMO this may be battery problem or nand chip problem - in both cases it is hardware fail