Related
Hi All,
Out of the blue my HTC Vox stopped booting. I mean, it would load to the windows mobile screen and then stay there till eternity. Removing my memory card and SIM also did not help! I then tried the hard reset option.
Even after hard reset it sometimes boots(1 out of 15 times) and when it does...it hangs after 10 to 12 minutes. Still have not put my sim n memory card into the phone.
I tries flashing the ROM using the ARA 1.27 ROM. After it rebooted to the bootloader, the flash utility gave a connection error! It did not connect to ActiveSync and stayed at the bootloader screen.
I still do not know how to flash it successfully.
If anybody can help me out, I'll be extremely grateful!
Thanks
Prateek
take the battery out, put it back.
connect your Vox (USB).
Hold the camera button and turn on your Vox.
you should see a red, blue and green screen (if my memory works as it should) and the computer should recognize the device, though you won't be able to explore it with activesync.
Run the SDA_ApplicationUnlock thingy (if you need to)
now try flashing the device.
If it flashes but after 3% restart, you need to do a CID unlock right before flashing.
hope that helps.
Invalid Vendor ID
Hi MoRkusReX,
Its giving me Invalid Vendor ID. How do I CID unlock it?
Thanks,
Prateek
http://forum.xda-developers.com/showthread.php?t=330909
first post , download the last file:
Vox USPL- CID BYPASS.zip
There a Readme file in there, you should read it.
post back where you're done.
No Luck!
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
Only once I have been able to boot into my OS and followed the instructions given in the link. The phone comes to the Linux black screen and then switchers off. Then the ROM Update Utility with which i'm trying to update the ROM gives an error that "cannot connect to the phone".
So, now I need to flash my ROM from the bootloader itself. Have managed to get mtty and connect to the phone. But even trying ResetDevice command, the phone does not boot.
Can you tell me the exact steps to flash a new ROM from the bootloader itself including CID unlocking? Can it be done??
Thanks,
Prateek
prateekswarup said:
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
...
including CID unlocking? Can it be done??
Thanks,
Prateek
Click to expand...
Click to collapse
yes it can be done.
you don't need to boot to OS, I couldn't either. after the steps from my first post here, run the uspl_116_jockyw.bat file. follow instructions.
that will unlock the CID.
Now the VOXs' screen should be white or so... then you run the ROM update thingy.
Hi..
I connected with the usb and got the bootloader screen.
tried running the SDA unlock program...the button to unlock the phone is grayed out. Cant click on it.
Next tried running uspl_116_jockyw.bat file
..cannot connect to phone and hence copy of haret.exe did not occur and neither did pmemtest run successfully...
What am I doing wrong??
ok..
first steps again..
battery out, back in.
connect USB
CAMERA button + Turn on.
now.. does windows do that USB sound? you know.. "tu du" ?
No sound....using win 2k Nt server edition...
but has detected my phone once on that USB and then allows me to talk to the phone using mtty....as in commands like ResetDevice work on the phone using mtty..
also, cannot get into bootlaoder mode with USB plugged in...
Steps and their results:
Disabled USB connections in activesync
Booted to the bootloader (red and green and Blue screen)
Connected the USB
"USB" displays on the left hand side corner
Now tried unlocking using Apllication unlock...grayed out button...
Tried running USPL bat but stops and says phone not connected when copying haret.exe
Using windows NT server 2003
if the SDA Application unlock button is grayed, of course the USPL won't work.
why "Disabled USB connections in activesync"?
And.. I doubt this is the problem but you should check on an winXP pc, I did it on XP.
No Luck!
Tried the same with USB enabled...same result
basically the thing we need to figure out is why your computer doesn't recognize the device.
the rest is obvious.
when I go to bootloader on my device windows pops up with a message says windows found device "and it's ready to use". like when you cannot every other USB item.
have you tried doing that on an XP system?
Going to do that now....lets hope it works....
Does ur activesync turn green when u connect at bootloader?
Also, I have removed my sim and memory card...thats okay right?
yeah, I removed both of them.
and no, activesync didn't turn green, but Windows recognized the device when I turned it on. turn on the speakers and wait for that winxp "USB connected" sound.
Still No Luck!
Tried doing the same on win xp...
no luck...
it connects to win xp ans says new device found...and ur USB device is now
ready to use...
after that i try application unlock it still gives me grayed out button....
ne suggestions???
Finally....
Finally got it done...
Thanks for all the help....
I managed to cold boot into the system for one time ans then SDA unlocked it and then ran UPSL .... it ran and then balnked out...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
then i flashed it with the ARA rom...
Seems to be working okay now..will test for a day and see...
thanks a lot
prateek
prateekswarup said:
Finally got it done...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
prateek
Click to expand...
Click to collapse
I'm not sure this step was necessary but as long as it worked.. good times.
btw, how did you boot into the system?
kept trying hard reset and repeated booting...( it was booting 1 in 15 times type...)..and one lucky time it didnt hang..so used that window to slip in the SDA unlock and USPL..
thanks ...
you're welcome.
All,
Somehow my bootloader got trashed while swapping memory cards and I'd like to easiest fix to get it going again. (At Tri-Color screen) If I plug it in and run RUU_Kaiser_Cingular_WWE.exe (I'm running nonbloat Tilt rom) it'll start the upgrade, stop at about 1%, but the phone will boot and everything is there. So I'm just looking for a quick way to make it stick so I don't have to do that anymore..
I'll play with cooked ROMs soon, everything is working GREAT for the time being and I don't wanna reinstall!
Thanks all!
-RT
Doesn't sound like you have HardSPL installed but this should fix your problem (at least your issue sounds very similar) ... after you get it fixed you should consider installing HardSPL.
Credit to pof for the instructions below which were part of his now dead SSPL thread for Kaiser:
For those of you had the phone stuck in bootloader mode after flash with SSPL stopping at 16%, follow these instructions to unbrick your phone:
1. Download mtty.exe
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Connect your Kaiser to PC using USB cable.
4. Open mtty, select USB port and click OK.
5. Hit ENTER twice, you should see the "Cmd>" prompt.
6. Type the command "boot", you should see something like this:
Code:
Cmd> boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
After that device should boot WM6 again, you can now re-enable USB connections in activesync and flash HardSPL
Click to expand...
Click to collapse
Good Luck
Ahhh!
I didn't find it in the Kaiser forum, but in the Hermes wiki!
Seems that I just had to connect via mtty (to USB, not a COM port! ) then just issue a: set 14 0
Then did a soft reset and all was well!
Back in business!
Now, maybe I'll start playing with some ROMS!
Thanks again!
-RT
hello i have the same problem after i tried to sim unlock my mda vario iii i tried to do what you proposed but didn't work this is what i get when i tried to boot from mtty
Fill RSVD information for block 288 to 309
TAG NOT FOUND !!! NOT CLEAR STORAGE !!!
No card inserted
OEMIPLInit clear 10MB ext RAM
OEMGetUpdateMode
FMD_ReadSector+, bad block no=0x15440, status:0x0
FMD_ReadSector+, bad block no=0x15440, status:0x0
FMD_ReadSector+, bad block no=0x15440, status:0x0
IPLMSG:0x2:ERROR: Failed to open storage partition.
i would apreciate if you can help me
Stuck in Bootloader
Hi everyone,
I tried using MTTY.exe on a XP machine. The option for USB shows up but when i type the command "boot" i get command error. Please help!
KAIS130
SPL-1.93.0000
CPLD-8
on the right top corner the tri-color screen displays RUUNBH
I tried HARD-SPL / gets stuck on 0% and the RUU goes into recovery mode later. Tried stock ROM (Invalid ID).
eddiesantiago said:
Hi everyone,
I tried using MTTY.exe on a XP machine. The option for USB shows up but when i type the command "boot" i get command error. Please help!
KAIS130
SPL-1.93.0000
CPLD-8
on the right top corner the tri-color screen displays RUUNBH
I tried HARD-SPL / gets stuck on 0% and the RUU goes into recovery mode later. Tried stock ROM (Invalid ID).
Click to expand...
Click to collapse
should've read further. You'd of seen my post on Different SPL's & their different command capabilities.
For 1.93 SPL you can issue cmd>task 8
You need to install hardSPL once you get it going, because you DON'T have it know.
GSLEON3 said:
should've read further. You'd of seen my post on Different SPL's & their different command capabilities.
For 1.93 SPL you can issue cmd>task 8
You need to install hardSPL once you get it going, because you DON'T have it know.
Click to expand...
Click to collapse
Thanks for your response GSLEON3
I followed your instructions and used the Task 8 command for the 1.93 SPL
The device turn off and comes back to the same Tri - color screen with RUUNBH on top right. Tried flashing Hard-SPL stuck on 0%. Please help
Anything you found eddiesantiago ?
Hi eddiesantiago,
did you find any solution to your problem, i have a similar issue.
My Tilt Shows :
KAIS1*0
SPL-1.93.0000
CPLD-8
on the right top corner the tri-color screen displays RUUNBH
Please reply if you got it fixed.
TIA,
Dhaval.
same issue
My tilt shows the same info here, is this normal? I need to verify this before I send my TILT back to ATT...
Thanks
I have flashed dutty's v4 rom and i want to change it
the problem is that when i try to do so i run
KaiserCustomRUU
my device goes into the 4 stripes screen it says usb
but then the program in the pc says error 260 and doesn't load the new rom
my phone still works as dutty's rom is still in but what can i do to change it?
Thank you and i have searched a lot but could not find a solution
thimiost said:
I have flashed dutty's v4 rom and i want to change it
the problem is that when i try to do so i run
KaiserCustomRUU
my device goes into the 4 stripes screen it says usb
but then the program in the pc says error 260 and doesn't load the new rom
my phone still works as dutty's rom is still in but what can i do to change it?
Thank you and i have searched a lot but could not find a solution
Click to expand...
Click to collapse
OK lets start at the basics...... In bootloader mode (tricolour screen) what text does it say at top of the screen?
Have you DEFINITELY Sim Unlocked and CID unlocked?
it says these things
kais130 mfg
spl-10.0.Olipof
cpld-8
Ok that confirms you have the capability to flash. I have seen in the past some people have managed to flash one time only using jumpspl but then their device reverts back to original bootloader...I was one of those people
Next question then...Can you boot the phone normally and gain an activsync connection to it?
yes
i can use my phone normally
only i cannot put a new image in
Are you using Xp or vista? If using vista it may be worth trying a reboot... sometimes it goes doolally with its usb ports. If you cannot see the phone through WMDC or activsync after a reboot it is worth going to SYSTEM (on your PC) viewing non present devices through device manager,( Drop to Command prompt and type... Devmgmt.msc set DEVMGR_SHOW_NONPRESENT_DEVICES=1 ) removing the relevant phone connection and then re attaching it so that windows re detects it.
If you can get a connection via actvisync (win XP) or WMDC (vista) to your phone then all should be ok. Uncheck the activesync/ WMDC "allow USB connections" and try again.
If this still doesn't work then search around here for MTTY. That will allow you to specify the usb connection to the device...amongst other things.
thank you for your time
i have win xp and activesync works nice
the problem is when bootloader starts
When you attempt flashing, do you do it from the device already booted into windows mobile or direct from bootloader?
Which ever way you have tried it, try ther other way.
Not teaching you to suck eggs but just in case you dont know.... To get direct to bootloader hold camera button and soft reset with stylus whilst holding camera button down and the tri colour screen should appear.
With device at the bootloader screen, Can you confirm that you hear the windows "noise" when you unplug and re plug the USB cable just as you would when plugging and unplugging the device normally. This will determine if the device has connection at the bootlaoder stage.
why not just flash using the microsd card. its much easier that way
yes it has connection
the thing is that i have already flashed as i told before with dutty's v4
now i can't
Usually Error 260's are related to the USB port functionality ( Port can't be opened etc).
The SD card method or MTTY should sort you out.
thx again
hope it works
at least the sd trick worked!!!!
now running on winmob 6.1
Glad to hear you sorted it.
almost
i cannot use my sd card cause i have to have it formated in order to put a new rom in
thimiost said:
i cannot use my sd card cause i have to have it formated in order to put a new rom in
Click to expand...
Click to collapse
disable USB connections in ActiveSync and flash.
This Link gives a list of eror codes for Hermes, and probably the same for Kaiser.
It's likely that you have a USB port error - maybe try changing the USB port you use or a different sync cable - or just stick to SD card flashing in the future - I keep an old 1gig card for this.
this IS the problem...i cannot flash...
it stays in the bootloader with the message i wrote
thimiost said:
it stays in the bootloader with the message i wrote
Click to expand...
Click to collapse
It happen to me before hardspl again fix it, not sure why
you mean use the sd method to do hardspl again?
OHHH lord dutty we need your new rom
Dear all,
got a problem with flashing my TyTN II which might? be related to the
"brand new" version?
here is what happened so far:
we bought several German TyTN II pro and
some of them need to be convert to english rom
Version:
Radio: 1.27.12.32
HardSPL did not install (White Screen) so I went for JumpSPL. Software installed with no problem, "USB" appeared on screen, unplugged and replugged the cable
The TyTN Display is three-colored,
USB connected direct to PC,
AvtiveSync stopped
starting flash-hardSPL\KaiserCustomRUU.exe
starts up,
some "caution" messages read and understood,
TyTN connected,
battery charged,
Software says:
"Verifying the information on your PDA Phone... please wait..."
"Current information about your PDA Phone:
Image Version: [* this part is empty *]
Select from below:
[Update] Update the current ROM version.
KLICK on Update:
From: Image Version [* again no information *]
To: Image Version: HardSPL-kaiser
klick 'Next' to proceed
*Warning message*
KLICK on Next:
Updating the ROM image on your PDA Phone
Please do not remove the USB connection from the PDA Phone or launch
any program during the update process:
PDA Screen goes blank, with progress indicator frozen to "0%"
*STUCK at 0%
PC says: ERROR [262]: Update error, The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the errors .....
After recover, I once again end up with my three-colored-screen
KAIS130
SPL-1.93.0000
CPLD-8
I am able to connect via mtty.exe,
info 0 shows
Model ID: KAIS13000
HW Board ID:31,PVT1
info 2 shows
HTCSHTC__102Ã;¿HTCE
Having read most of the threads here i continued using mtty with
Cmd> boot
Command error!!!
Cmd> task 8
The pda boots again to my beloved three-colored-screen
Any escape from this? Or am I damned stupid ....
Cheers,
Martin
The
Try once more the boot command in MTTY and, if it again enters bootloader, once more. Usually it must be done two times.
no way, as "boot" only says "Command error" a million times ...
Exactly the same thing happened to me Everyone here shouts about flashing HardSPL first (and then it's "impossible to brick your phone"). Unfortunately, people rarely mention that the phone can be bricked whilst trying to flash HardSPL!
With mine, I did initially receive an error when using the 'boot' command, however when I did the following, it worked:
- uncheck 'allow usb connections' in activesync
- get the phone into the tri-color screen and plug the usb cable in
- start mtty, select usb
- issue the 'boot' command (without ANY other commands being issued before it)
Does the tri-color screen say RUUNBH in the top corner? Apparently, some have recovered their phones by flashing a ROM from their original vendor (e.g. if you got yours from HTC, try the base HTC ROM). This never worked for me, I just got the 'stuck at 0%, then error 262' behaviour you describe above.
still stuck... what i did:
- use mtty to issue the boot command : Command error
- use different Shipped ROM Images : wrong version whilst updating
-
still stuck... what i did:
- use mtty to issue the boot command : Command error
- use different Shipped ROM Images : wrong version whilst updating
anyone got a german 1.56.407.3, radio 1.27.12.32 shipping version?
- try to install rom image using SD: stuck with blank screen and "Loading...." comment
So I am running out of ideas. If I got everything right, the ONLY chance
to re-animate it is to get the one and only original rom setup version?
any way to install HardSPL via SD-Card?
Martin
e-men said:
still stuck... what i did:
- use mtty to issue the boot command : Command error
- use different Shipped ROM Images : wrong version whilst updating
anyone got a german 1.56.407.3, radio 1.27.12.32 shipping version?
- try to install rom image using SD: stuck with blank screen and "Loading...." comment
So I am running out of ideas. If I got everything right, the ONLY chance
to re-animate it is to get the one and only original rom setup version?
any way to install HardSPL via SD-Card?
Martin
Click to expand...
Click to collapse
Try flashing to this ROM
ftp://xda:[email protected]_Radio_22.45.88.07_1.27.12.17_Ship.rar
e-men said:
So I am running out of ideas. If I got everything right, the ONLY chance
to re-animate it is to get the one and only original rom setup version?
any way to install HardSPL via SD-Card?
Click to expand...
Click to collapse
It's very unfortunate your SPL doesn't support the "boot" command
Find a rom with CID = HTC__102 and ModelID = KAIS13000
You can find these values with a hexeditor in the RUUsigned.nbh (extract it from an original rom update)
You can rename RUUsigned.nbh to KAISIMG.nbh and put it on SD card. Just enter the bootloader and flashing will start. But it also checks if CID and ModelID match with your device.
Thanks alot, but:
Error [262]: Update Error
and its a KaiserCustomRUU which I thought only works o.k. if
HardSPL was applied correctly ?
Martin
jockyw2001 said:
It's very unfortunate your SPL doesn't support the "boot" command
Find a rom with CID = HTC__102 and ModelID = KAIS13000
You can find these values with a hexeditor in the RUUsigned.nbh (extract it from an original rom update)
You can rename RUUsigned.nbh to KAISIMG.nbh and put it on SD card. Just enter the bootloader and flashing will start. But it also checks if CID and ModelID match with your device.
Click to expand...
Click to collapse
I´ve got a second, working, perfect TyTN with the matching rom image. any chance to read out the ROM and use that one to boot?
I followed the thread about ROM extraction, but it says I need HardSPL to unlock, otherwise it will not be able to update ?
Same problem!!!!
e-men said:
Thanks alot, but:
Error [262]: Update Error
and its a KaiserCustomRUU which I thought only works o.k. if
HardSPL was applied correctly ?
Martin
Click to expand...
Click to collapse
Same problem here with my brand new TyTN II... Please help! i got it just one day
I am looking for an answer too. It seems that from 1.82.00.00, there is another layer of protection against JumpSpl. My experience is you need the original Rom to flash back, which works for me. Although you do not have the rom you desire but at least you unbrick you phone.
japher said:
Exactly the same thing happened to me Everyone here shouts about flashing HardSPL first (and then it's "impossible to brick your phone"). Unfortunately, people rarely mention that the phone can be bricked whilst trying to flash HardSPL!
With mine, I did initially receive an error when using the 'boot' command, however when I did the following, it worked:
- uncheck 'allow usb connections' in activesync
- get the phone into the tri-color screen and plug the usb cable in
- start mtty, select usb
- issue the 'boot' command (without ANY other commands being issued
before it).
Have a look at this; http://forum.xda-developers.com/showthread.php?t=369567
just might help
King
Click to expand...
Click to collapse
i got the same problem... when i haved installed hardspl it froze to 99% and give me back 262 error. now i'm retrying but don't work..
what can i do?
solved using mtty.exe
ffffffff said:
japher said:
Exactly the same thing happened to me Everyone here shouts about flashing HardSPL first (and then it's "impossible to brick your phone"). Unfortunately, people rarely mention that the phone can be bricked whilst trying to flash HardSPL!
With mine, I did initially receive an error when using the 'boot' command, however when I did the following, it worked:
- uncheck 'allow usb connections' in activesync
- get the phone into the tri-color screen and plug the usb cable in
- start mtty, select usb
- issue the 'boot' command (without ANY other commands being issued
before it).
Have a look at this; http://forum.xda-developers.com/showthread.php?t=369567
just might help
King
Click to expand...
Click to collapse
Hi there!
Which version numbers does your TyTN have? Mine does not respond
to boot command (says "Command Error:")
Click to expand...
Click to collapse
i've the same problem. i can't install nothing because lost connection at 0%
mtty is a solution for my problem ?
How do I use it?
e-men said:
ffffffff said:
Hi there!
Which version numbers does your TyTN have? Mine does not respond
to boot command (says "Command Error:")
Click to expand...
Click to collapse
You might want to try leave a gap between > and Boot when using mitty, it works for me.
Click to expand...
Click to collapse
>i've the same problem. i can't install nothing because lost connection at 0%
I have tha same proble but with touch dual!!!!
ffffffff said:
e-men said:
You might want to try leave a gap between > and Boot when using mitty, it works for me.
Click to expand...
Click to collapse
nope.. does not work.
restarting mtty - does not work
reset (hard,soft) TyTN - does not work
type "boot" before the prompt comes up - does not work
type " boot" - does not work
type "BOOT" - does not work
all different types of "boot" "restart" whatever - does not work
any more ideas? any check within my spl possible for a set of commands?
Click to expand...
Click to collapse
hello everyone.. sorry to bother you but I need an urgent help. I was flashing a new rom to Kaiser, everything was fine, but on 16% of flashin it gave an connection error.. so I did the connection recovery and everythin is ok... but when I want to continue flashing nothing happens.. I´m stuck on the boot screen and cant get enywhere from here... I can´t restore backup ´cause i cant connect the device with activesync.... can you pls help me??
did you hardspl your device first?
yes i did the hardspl, I haven´t been flash rom for the first time, but for the first time it gave me this error and i got stuck on bootloader screen..
try reflashing with an original shipped rom,
If you are still stuck PM me with a MSN messenger address & I'll walk you thru the recovery process. Or find me at [email protected] on live/msn messenger.
or try to use this tool: http://wiki.xda-developers.com/uploads/mtty.exe
disable active sync, select usb from mtty.exe then digit cmd
when it prompt cmd> digit boot
If you give advice, make sure it's correct.
Icchan said:
or try to use this tool: http://wiki.xda-developers.com/uploads/mtty.exe
disable active sync, select usb from mtty.exe then digit cmd
when it prompt cmd> digit boot
Click to expand...
Click to collapse
& then when you CAN'T connect, let me know, because that's just wrong.
What you do is disable USB connections in A/S connection settings. Then launch MTTY. Then select USB as the port. THEN YOU MUST SELECT RTS/CTS AS THE FLOW CONTROL TYPE.
Then hit the enter key twice. At the cmd> prompt you want to then use the "Boot" command. Let it reboot & take notice of what mttry reports. THe repeat the mtty "Boot" command again until MTTY reports that all is good instead of the sector errors you'll get the first time or two.