Database Info

connection problems while flashing SPL

Hello,
I'm realy going insane at the moment.
I try to degrade the SPL from SPL-1.0.OliPof (KAIS130 MFG, CPLD-8 <- whatever that means) back to the orginal one.
What I'm doing is:
1. connect the kaiser without sd card and sim card via active sync to my XP PC.
2. start the bootloader via button and stylus.
3. unplug the usb cable and replug
4. starting the KaiserCustomRUU tool.
the problem is that I always get an error 260 which means that there is no connection between pc and pda. by the way I already tried every possible solution mentioned in this forum.
What i figured out is that after I repluged the usb cable the computer detects the pda but is not able to install a suitable driver. So I have an unrecognized usb device in the device manager. I guess this is the issue but does anybody know how to solve it. I mean which driver is needed in this state?
can anybody help?
greetings,
macx

I must be misreading your post... you don't mention running JumpSPL/SSPL. If you're not doing that, then there's you freebie for the year, and also the solution to your problem.

sorry, my fault.
Point 2 is running SSPL of course. Version 1 leads to a white screen and the other two versions bring up the bootloader.
In the meanwhile I tried so many things that I was a bit confused when I wrote this post.
nevertheless I don't know what to do anymore to make it work.

dead kaiser after flash

probably, i dowgrade my kaiser with lower version...(everything passed(unlock,flash)without problem and error...
after flash phone dead... nothing happen when try to power on,reset,boot,anything...try,almost 4 hour, everything what can find here, but still no luck...
no power, no bootloader, even i can't do anything with mtty couse i run Vista, and have prob to stop activesync working... everything what i got is
ZTE diagnosstics interface 6000 cdma 1x(com5)
zte nmea device cdma 1x (com6)
in my control panel/device manager,
that talking maybe phone is not totaly damage...
anyone help, any idea...this will be long long night...

I'm not sure what you mean exactly but I also had a dead Kaiser. It did not happen after flashing but my phone suddenly turned off and could never be turned on again. I first thought it was a battery issue but no.
Finally I returned it to HTC and they replaced the motherboard under warranty.

yes but my kaiser is not in warranty, customer buy it in Italy... and I kill him, sad but true...

well i might not be correct, bu it looks like you wiped the nand on the phone... i think if you look up the steps in the frankenkaiser thread it should help you out

but i can't go in bootloader mode....

if you look you dont have to enter bootloader mode..: http://forum.xda-developers.com/showthread.php?t=394584

ok, first , from now i'm on XP...
but always same... when attach in any button combination to the pc, it was always see the same, look on the pic
and in MTTY, i have the port from 1 to 10 &usb. on usb cannot connect, with the error "usb port can not open"
btw forgot to write, device is brand new, no hw damage

i make connection between kaiser and MTTY, over diagnostics port, but when try to type command(or Enter) nothing happens. how to use MTTY

as i see my kaiser stuck in download mode... (see in QPST & QMAT)... how to flash it or to restore it to normal mode(phone no power on, no going to boot mode)... i read emi&sbi, if it can help some...

if you look here from step 3 down i think this should walk you thru the process... http://forum.xda-developers.com/showthread.php?t=393337
if you look at the part right below step 2 it says to lower your com port for the diagnostic interface below 10, i think i saw that yours is set to 53...

i try on 3 differnet pc. try all comm port. mtty is my problem(one of them). when run mmty(choose connection base on diagnostic port), i can type anything, any command, enter,etc... nothing on screen, nothing happen after enter...

can someone explane how to flash kaiser via jtag...
someone who allready do it...
or send me to pm

Sorry no idea!
Hi mobilend,
i just saw your message... no idea about that!
Don't know if anybody already traced the testpoints.
You also would need some software tools to access the MSM chip.
Maybe i'm wrong but i read some threads about this kind of brick and maybe your able to recover without JTAG.
Perhaps the kaiser cracks could help you out
Regards,
scholbert

i do nothing since today...
if somebody have idea how to unbrick kaiser with jtag, write here or i may send device to him...

Problem
Hi excuse you have succeeded there?
I have yours same problem.

This is my fear, for this reason I have not had the courage to update my ROM.
I do not understand, the videos appear to be so simple, but at the same time, to read topics like these, I am in panic ...
Will I still be aware and courageous enough to update my ROM?

jonastamborin said:
This is my fear, for this reason I have not had the courage to update my ROM.
I do not understand, the videos appear to be so simple, but at the same time, to read topics like these, I am in panic ...
Will I still be aware and courageous enough to update my ROM?
Click to expand...
Click to collapse
Most of the problems come from not reading the information...
If you look at the number of users on here that have managed to upgrade their phone you will see that it way outways the number of people who have truly bricked thier phone. (A lot of the people who have upgraded thier phone have little knowledge about what unlocking means as well, so don't worry if it's a bit overwelming).
If you want to get started click "KAIS: Getting started" in my sig for a step by step guide by mskip. mskip, myself and some other members will help out with any questions you post in that thread. Also check out the info on the HTC Kaiser wiki page on the xda-developers wiki page.
Ta
Dave

O2 XDA Exec Won't Power On after Unccessfull ROM Upgrade

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

USB not working after flashing Damage Control

So let me start by saying I have been researching these forums for the last 8 hours trying to following instructions on getting my phone to connect to my computer and with no luck, hoping someone out there can please help me step by step in correcting my problem.
1)I flashed DC's Rom, then flashed the most current radio, then flashed the most current Wimax.
2)I noticed that when I connect my phone to the computer, it says device is not recognizable. The phone charges but does cannot be seen by the computer as a disk drive (I'm trying to RUU to stock but the comp. will not see my phone and I've already tried running RUU but it also is having probs seeing the phone).
3)I've read Calculin's instructions in fixing the SD Card and USB as close as possible but also no luck. I've downloaded Android-SDK Tools and ran CMD with the Instructions saying type in "fastboot oem boot", from there, thats where I get stuck, it just says "waiting on device". Not sure where I go from there, I'm in Reboot mode where it has Fastboot on my evo screen.
Any help would be much appreciated, I'm just so frustrated and I'm trying to get back to square one.

Unplug your phone and restart it, then plug it back in. I had to do this 3 times before it started working again. Other than that, you might just need to download the new drivers.
And you posted in the wrong section.

Sorry about posting in the wrong section, what drivers should I install, are you talking about the new HTC Sync Files or something else? Can you point in the direction to get these files?

okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?

faquedado said:
okay, I think I'm getting close, I have a box thats popping up now thats trying to located the Device Driver the phone. It says "Failed" next to the line "MY HTC" Where can I download the necessary drivers for this phone?
Click to expand...
Click to collapse
You should be able to get the proper drivers from either Sprint or HTC's web site. There are links on both sites. Also, when you install / reinstall the sync drivers make sure anti-virus is disabled. If the situation continues and you've tried everything else other folks suggested look at program permissions in your anti-virus program. I was having something similar and CA anti-virus was not letting the program start-up. I had to toggle it to "allow".
Good Luck.

[Q] Oh my. SBF failed. Am I out of luck? !Resolved!

I have (er, HAD) a rooted stock droid 2 global. I read copious amounts of info to guarantee that my move from a blur-laden rom to a considerably-blur-LESS rom (Hexen) would go as pain free as possible. I printed out all the rsdlite info I could find, located all the appropriate files and drivers, found a good, md5 verified stock sbf, and prepared to make my phone better.
Step-by-step I re-read the instructions until I thought I had it right. I started, and waited for the final step "phone[0000]: phone is being rebooted."
It never came. I did everything right and it ended with rsdlite's status on the phone reading :"failed flashing process. phone [0000]: error switching phone to bp pass through mode (0x70bE); phone disconnected," and my pc giving me a "found new hardware: flash mdm6600" message. I am not able to find a driver for the mysterious new device that crops up as my phone is trying to reboot.
My phone sits unperturbed, still reading "SW Update in progress..." If I try to shut it off, it doesn't respond. And when I battery-pull and put the battery back in, it starts up immediately with a "Bootloader D0.11 Code corrupt..." message.
I cannot make it go into bootloader mode. All it does it what I've told you.
So, you tell me, please, am I screwed? Am I the proud owner of a 3-month old brick?
Dan

resolution
My phone is back.
Half the reason (okay 9/10ths) I posted was because I thought my phone was finished. I had searched thru here and the web many times during each SBF re-attempt, and I seriously think there were at least a dozens tries minimum.
No documentation was found for my issue: Bootloader D0.11
On my last search I found a set of Motorola USB drivers that were a newer version than what I had found every other time. They made the difference. The drivers that *worked* were V4.7.2.0. The previous drivers were 4.6.5.
I hope this helps...
Dan

What did you do to get out of the bootloader D0.11 screen?

Well, like I've said, all I did was use a different set of Motorola USB drivers. The drivers made the phone be recognized by the PC during the RSDlite process.
These are the drivers I used: Motorola_Driver_Installer_v4.7.2.0.msi.zip
All I did was RSD *again* exactly as I had been doing.
The only differences are that the whole process begins with the bootloader error message being displayed on the phone. RSDlite will recognize the phone when it gets to that part of the process. And when you get to the "switching the phone into BP mode" message and the simultaneous PC message "found new hardware: flash mdm6600" the pc message appears *very briefly* (presumably because *now* it has MDM6600 drivers) and the RSD process continues, exactly as it was supposed to.
I hope I've answered your question clearly. And I hope this helps you with your D0.11 error.
Just so that you know, I am *no* expert by any means when it comes to this stuff. I'm just like you: looking for answers.
Good luck,
Dan

Thanks for the help. After two hours last of searching and downloading last night, I finally got my wife's droid restored.