Hi. There is something wrong with my phone. When i tried make phone call. It stopped responding. After reset it goes to four color screen with serial word on the bottom. I never flashed this mobile. Now when I try connect to vista it shows massage Usb device Not recognized, same on xp, but serial changes to usb. Please Help
first of all, i'm not an expert
but there are some threads in this forum about it. the only thing i can explain is:
that you're stuck in the bootloader,
the usb vs serial thingie, is that vista makes any usb device like a serial one..
try checking the spl threads and 'stuck' keywords
sorry can't be of more assitance...
anduh, keep calm and relax.. there's a lot of knowledge here.
so keep breathing and don't go paranoid..
gl
you might want to provide us with some more info,
rom version?, if it sais anything more in the RGB screen
and 1 more thing.. tried removing the battery for at least 1 minute.. / removing sd / simcard
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
podhal said:
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
Click to expand...
Click to collapse
hi podhal,
1) go to settings of activesync and uncheck 'allow USB connections'
2) or just to make sure, go to task manager and kill the process 'rapimgr.exe' and 'wcescomm.exe'
3) download mtty from here: http://forum.xda-developers.com/attachment.php?attachmentid=71806&d=1203597568
4) connect your cable to your kaiser-- it should say 'USB' and not 'Serial' at the bottom
5) choose 'USB' in the drop down list of ports and click 'OK'
6) on the mtty screen press enter key and you should get a cmd>
7) type in 'boot' (without the quotes) and press enter. If it doesn't boot up, paste the output here. DO NOT EXPERIMENT WITH MTTY AND TYPE ANY OTHER THING AS THIS CAN MAKE YOUR PROBLEMS WORSE.
EDIT: do this on you xp machine and not on vista!
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
podhal said:
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
Click to expand...
Click to collapse
good for you now read and go inside the wonderful world of flashing ROMs, heheh
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
StealthNet said:
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
Click to expand...
Click to collapse
Try the frankenkaiser then It's pretty *safe* if you know what you're doing-- did it 3-4 times because I was trying to wipe out bad blocks. Make sure you have the right radio though and an old hardspl before you use it jocky patched the new spls to ignore task 2a command.
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
StealthNet said:
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
Click to expand...
Click to collapse
well I had 3 bad blocks before, but the problem that I had is my ROM area is writing to that blocks and what's unlucky is the critical parts of the ROM is written there (bad blocks are common, but of all the places.. sheesh) that makes my kaiser just reboot indefinitely. So-- what I did was task 2a and it removed only one, but it was enough to get me flashing flawlessly to any ROM
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
StealthNet said:
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
there is in step 3 task 2a which completely *bricks* the phone. But as it said, you would go through oemsbl which is the radio bootloader and not the spl (os bootloader) anymore since it's wiped out already. Read the whole thread before doing it, it's not for the faint-hearted
StealthNet said:
Nice to know!
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
spot on but you need to make sure the drivers are there. After task 2a it would detect your kaiser as new hardware etc., so you need to still install the qualcomm drivers from that thread.
Thanks for the help! I have a XP machine set up just to do that
Ok, let´s do it.
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
sorry mate, just saw your reply.
Maybe you're replugging it too fast, I had that problem also. It kinda takes time before you get it but you're right on track if you ran step 6 with the output
EDIT: I think I know what you did wrong.. I remember that problem before. Are you running the frankenkaiser unbricker radio from hell? if you don't have the radio 1.65.17.10 that won't work. You should ask jocky for the right frankenkaiser unbricker for your radio.
check you later StealthNet, it's 2am and I got to go work in 6 hours. Ta!
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
if it's not recognized, try installing active sync again "to load usb drivers", and try again
You incorrectly installed the drivers most likely.
But before you use Franken, you need to be sure you are using one compatible with your OEMSBL & Vboot version.
What was your last radio & rom version?
GSLEON,
I PMed Jocky and, unfortunately, I did it wrong. When I read the procedure to use Frankenkaiser, I mistakenly assumed that, since task 2a wipes out the phone, the radio version wouldn't matter.
In fact, Jocky explained to me that it really does, and that Frankenkaiser is tailored to be used with radio from hell only.
My last ROM and Radio version were the ones based on the latest Dutty's (radio 1.65.16.25).
My attempt to "task 2a" my phone was my last attempt trying to solve my colored brick (booting into bootloader everytime I turn on the phone). I think this is being caused by bad blocks into bootloader or radio area.
Hopefully, I'll be able to get out of the hard brick (task 2a) and it will solve my colored brick problem
In fact, if it does work, I think it will be usefull for lots of kaiser users (last time I accounted at least 4 ppl with the same problem).
Thanks for the help!
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
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.
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..
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
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