I have tryed to flash my HTC CRUISE its not letting me intresting am on windows 6.1 htc one i would like to upgrade to the http://forum.xda-developers.com/showthread.php?t=446378 still staying on 0% hope some body can help me its doing my head it.
Thanks
Fue
Have You, before, install the HardSPL?
You can try this:
Originally Posted by christonge
1. Stop ActiveSync
2. Open Task Manager (press Ctrl + Alt + Delete) on your PC and
stop these two processes rapimgr.exe and wcescomm.exe
3. Plug in your device via USB. Your computer should be asking install a driver. Install and continue.
4. Now Run mtty and choose USB in 'PORT'
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset.
5. type "task 8" to get your device formatted.
6. Now unplug your device and manually reset it.
i hope you will be happy after .. thanks
I am using Windows Vista Ultimate. Everytime I hook up my G-1 it shuts off my internet connect and it gives me an error message at the bottom right about it not reconigizing the device. It will allow me to charge it but I can't access the sd card or use my internet when connected. please help. P.S. I can take it to anyone elses computer and it works just find (XP & Vista).
cyanogen 4.2.3.1
Welcome to forums
Have a look here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
Hope it helps,
check out for the program 'USBdeview' and run it. It allows to correctly unistall any previous driver, then reboot, connect the g1 with the cable, choose 'manual install' and put on those, they will do the job fine
make sure USB Debugging is enabled (Useful for ADB Commands)
So depressed, this morning, when my phone is in syncing I answered a phone and the mobile synchronous interrupted, Ijoined it to my again, the pc shows"unknown device",
I tried to updated drivers, but no use
I reboot my Touch PRO,the PC also shows "unknown device",
I reflashed a new rom to my phone , the pc shows as the same""unknown device",
I connect my colleagues' HTC C720 and an imate PPC to my PC ,they could be activesynced with my pc. My touch pro also could be synced with their PC
who can help me.It makes me crazy.
Simple mistake. It's possible that everyone may have had this problem before.
It's a Device Partnership Error.
I'll help you with the easiest way to fix this(in my opnion).
1.) Unplug your Device from your PC
2.) Download & Install CCleaner HERE
3.) Uninstall Windows Mobile Device Center/Active Sync from your PC
4.) Run CCleaner (Run the Windows Cleanup & Registry Cleanup [FIX EVERYTHING])
5.) Restart your computer
6.) Download & Install Windows Mobile Device Center/Active Sync
7.) Soft-Reset your phone
8.) Plug in your Phone during its boot-up
Reply with results.
Agent Zach
I followed your instruction
but it's no useful
thanks all the same
During the upgrade of jasjar to wm6.5
After synchronization by activesynic and format the old version
Restart the machine work and entered the boot Loader system
Screen appears, written by usb from the top and bottom of v1.00
And a message from windows xp says usb device not recognised
And stop everything ....
I tried to install the driver of the usb from the cd but the pc does not accept
also tried more pc by xp, seven, vista
But the same thing ....
What is the solution
In this threat i gonna upload some patched frankenkaisers for different versions.
With "FrankenKaiser" you can unbrick "task 2a" bricks:
There is no SPL, Splash and OS present as "task 2a" formats the entire application area.
Before FrankenKaiser there was no method available to unbrick and therefore they were called "hard bricks"
With frankenkaiser you can also revive kaisers where you don't see anything on it but is detectable (after turning on your device) in windows as an other device:
you got stuck in the OEMSBL and you can only talk to your device with mtty.
Credits goes to Jocky Wilson who created the original frankenkaisers. (Paypal to [email protected])
I've only changed them to work with different versions.
These versions are created at forum user requests.
Method to dump your rom:
1. connect your bricked phone and power it on
2. connect with MTTY to diag port COM#: (look up # in device manager)
3. type "radata" followed by enter (you'll see a parameter error message)
4. type "GO2AMSS" followed by enter
5. your phone should now change to "QC download mode"
6. use "QPST Memory Debug" tool to dump smi.bin and ebi.bin
7. zip smi.bin and upload it to Rapidshare (or any fileshare service) and send me the link
oemsbl: V1.9309
Radio: V1.71.09.XX
Verified.
oemsbl: V1.9519
Radio: V1.70.19.XX
20110823: new version uploaded
oemsbl: V1.9529
Radio: V1.65.29.21
oemsbl: V1.9518
Radio: V1.70.18.xx
Frankenkaiser for other versions can be created in this thread
Excellent work massivekid, just what I needed to fix the 600+ bad blocks on my spare Kaiser! Thank you!
You da MAN!!!
Turns out I cannot use any of this because my laptop has NO COMM ports.
Unless I can find a USB to serial adapter and force a COMM port, I'm stuck.
You don't need a com port. If your phone is in OEMSBL then it will ask for a different driver. This driver will create a virtual com port on your computer thru USB.
First of all, thanks for creating frankenkaisers for different radio versions,
but I need some help, my radio is version V1.71.09.XX, I did all the steps to rescue the phone up to step 11, and when I connect the usb to computer, windows shows an error and wont recognize the usb connector, not allowing me to flash the hard spl through usb. would be absolutelly happy if you would help me solving this.
Do you see the tricolor screen?
Did you disconnect and reconnect the usb cable again and do you see USB on the tricolor screen?
if no usb is seen, redo steps 7-10 again (after pulling your battery) but this time in step 9 run FrankenKaiser with the other SPL "sspl-0.92-jumpspl-force-usb.nb".
this will force usb detection.
i redid steps 7-10 at least 10 times already, tri-color screen shows up with the first spl and gives problem when connecting the usb, when I try the 0.92 spl the screen stays black (I tried connecting the usb even with it staying black and the same error message showed up)
*During the whole step by step the only difference I saw between my results and the screenshots was the oesmbl version on screenshot 7, where instead of a "2" there was a "1"
And did you tried the "sspl-0.92-jumpspl-force-usb.nb" at step 9?
If you enter mtty and type ? or h what is the output of the command?
if you see a lot of commands, then your device is security unlocked.
the "sspl-0.92-jumpspl-force-usb.nb" file is to force USB connection so you can connect with usb.
If that doesn't work, try with the original spl and after cego, pull the usb cord quickly and if the tricolor appears, try to connect the usb again.
after typing "h"
Available monitor commands are:
? [command]
h [command]
mb [StartAddr [Count [Filler]]]
mh [StartAddr [Count [Filler]]]
mw [StartAddr [Count [Filler]]]
setboot [0/1/2/3]
setatcmd [0:SIO/1:UART/2:USB/3PRAM]
setsmdloop [0:disable/1:enable]
setmpatch [0x1: CPU Freq/0x2: acoustic/0x4: simdoor/0x8: RTC]
setiot [0isable/1:Enable]
eraseall [erase all setting flags]
setdiag [0:USB/1:UART/2PRAM/3:SIO]
partition
checksum
format
setinfo
readadc
cego
setgpio
getgpio
gpio
version
powerdown
platformid
radata
showexplog [n]
usbdppulldown [n]
usbdmpulldown [n]
usbdppullup [n]
usbdmpullup [n]
Headsetpullhigh [n]
rfid
wpmic [PM_VREG] [0/1]
the "sspl-0.92-jumpspl-force-usb.nb" gives only blackscreen on the phone, no tri-color.
I`ll try the first spl and take out the usb quickly.
Same result after pulling usb quickly after doing the command "cego"
Tried the same with sspl-0.92 and the blackscreen apears the same way, and the error message on windows is the same:
(translation might no be exact because my windows is in portuguese)
"One of the usb devices connected to this computer had a problem and windows can not recognize it. to get help click on this message.
After clicking it shows a windows with a root usb hub, 4 usb doors being one of them the one where the phone is connected with a red X before it.
Ps.: I`m not exactly sure, and I don`t know if this might influence on anything, but if I remember right, when first unlocking my phone, the JumpSPL1.56-KAIS.exe wasn`t effective, I needed using one of the other 2 jumpspl available on that thread.
With "sspl-0.92-jumpspl-force-usb.nb", you can also try after cego to press and hold camera to enter tricolor bootloader mode
Also you can try this spl: SPL3.56-patch-nostuckinSPL-FORCEUSB.nb at step 9?
Just unzip it in your folder and use it.
when using the sspl0.92 it wont go out of the blackscreen (even holding camera button), and the same error message is shown on usb
when using the new spl3.56 the usually blinking green led stay orange after the cego command and the screen stay black, tried holding the camera button, to no effect in either "spls".
Same usb error on three spls...
The error states that the device is halted and is not handling usb functions anymore. The one that has the tricolor screen, should work, but some devices are not detecting the usb correctly. Therefore the usb force spl are created.
I'll try to find out how we can overcome this...
thank for your attention and taking your time to help me, hope you can find a solution, surelly you will help many kaiser owners that got many "bad blocks" in memory...
(shouldn`t ever have tried to put android on nand...)
keep me informed on any kind of progress and let me help you on testing.
Ok, try this one:
Remove and reinsert battery, then hold the send button and power on. Connect with MTTY (COMn) and this time enter "dload" to put phone in dload mode Continue with step 9.
Try SPL1.56-KAIS-unbricker.nb then or sspl-0.92-jumpspl-force-usb.nb
tried it, no letters under the: "Just be patient while I'm working ..."
believe the phone hunged up, will try again.
(also tried using the send button whenever turning the phone on in the steps 7 through 10, nothing different happened, I believe the jumpspl can only be loaded while in setboot 1 I`m thinking about trying to use "cego" without typing setboot 0 before...)
Phone will absolutelly lock if I dont enter setboot 1 in the step before typing dload,
frankenkaiser isn`t able to access it (no letters under te message to wait) and it locks after the frankenkaiser attempt (wont accept mtty commands), removing battery returns to "normal" (as in dead kaiser).