Related
I realy don`t know what to do...
I have a Treo 750v, it was spanish version, I wanted the english version, so I did everything that I found here to do it right, but, wen i try to flash any WM6rom even the original from Palm.
I`m stuck in the bootloader, when flashing it just doesn`t pass the extrom(with sdcard), or blocks in the midle of OS, so I did it with the KaiserCustomRUU.exe and it blocks in 17% "ERROR [226]:FLASH WRITE".
i have the latest radio update, and the SPL-1.40.oliNex...
so what should I do...
please post any ideas...
it is recognised on my computer, but doesn`t sincronise with activsync...
try the palm recovery rom, available for dl from palm site
mb
thanks, but I`ve done it already...
It said it`s complete, but my treo stays stuck.
If you have any other ideas please post.
Have you tried to flash using the SD method?
Clear the temp directory. (to find out which one go Start\Run and type cmd. At the prompt type set and look in the list for the temp directory.)
Launch the installer. When you are presented with the program window go to the temp directory. This is where you will find the place where the installer created it's files; this is where you will find files named .NBH
Take the largest .nbh file maybe around 50-80mb and copy to a formated (fat32) sd card.
Rename the file to CHEEIMG.nbh.
After you put the card back in the phone, reset it and it will start the installation process.
Post back with any issues.
thanks, but yes...
it stuks in extrom, or if the CHEEIMG.nbh only does have the OS, it get stuck in the midle and an error is showed on screen...
superhiperclim said:
thanks, but yes...
it stuks in extrom, or if the CHEEIMG.nbh only does have the OS, it get stuck in the midle and an error is showed on screen...
Click to expand...
Click to collapse
almost sounds if your DOC has bad blocks (The flash rom). weird ****
superhiperclim said:
thanks, but I`ve done it already...
It said it`s complete, but my treo stays stuck.
If you have any other ideas please post.
Click to expand...
Click to collapse
can you get mtty to connect over USB?
after the load from SD, the screen shows:
" 00018003
CHEEIMG.nbh - FAIL
SPLASH1 - OK
BOOTLOADER - OK
GSM - OK
MicroP - OK
EXTROM - Fail
OS -
Update Terminate
UPDATE FAIL"
This with extracted CHEEIMG_FW.nbg, renamed to CHEEIMG.nbh from the treo750_2_23_ROW_en_desktopupdater.exe
any ideas left to solution?
thanks in advance
I`m sorry (for my ignorance) but i don`t know what "mtty" means...
but if you are asking if I can conect my treo over usb, the answer is, Yes i can
marleyb said:
can you get mtty to connect over USB?
Click to expand...
Click to collapse
after a quick search, I found mtty,
I don`t know what or how to do with mtty...
can you tell me what to do?
superhiperclim said:
I`m sorry (for my ignorance) but i don`t know what "mtty" means...
but if you are asking if I can conect my treo over usb, the answer is, Yes i can
Click to expand...
Click to collapse
try this;
1) disconnect usb cable
2) in activesync deselect usb connection (see pic as1.png)
3) connect usb cable
4) reset while holding left media button
5) start mtty (attached) and select USB (see pic as2.png)
6) select ok and press enter a couple of times, you should get a console prompt like pic as3.png)
does this work? do you get a console prompt? if so let me know then we can move on to the next and last step
mb
yes i get a console prompt...
superhiperclim said:
yes i get a console prompt...
Click to expand...
Click to collapse
kay type;
set 14 0 <enter>
task 28 <enter>
task 0 <enter>
device should reboot now, if not reset manual
if os loads now be happy, if not try to flash a full official firmware.
I fixed my older bricked S200 once this way, if your lucky it works for you too
let me know,
mb
ps. between set and 14 and 0 = 1 space
Cmd>task 28
Storage format start
Write Nand Success
and then nothing hapens, so I can`t put the "task 0"
any other ideas?
task 0 is just reboot, so you can reset now, see if you can succesfull flash a new rom now, can recommend the SD procedure
btw i added you in msn messenger
greetz
mb
did it, but once again... faild on the EXTROM... I am instaling with SD method the original Treo750_WM6...
ok, I will acept you on msn...
superhiperclim said:
did it, but once again... faild on the EXTROM... I am instaling with SD method the original Treo750_WM6...
ok, I will acept you on msn...
Click to expand...
Click to collapse
just checked task 28 should respond
Code:
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 407
Storage Total block: 537
Total Bad Block in CE: 0
NeedToEraseBlockStart: 420
NeedToEraseBlockEnd: 944
Storage format success
so I suspect your DOC (Disk on Chip)is defect
I will try it again, and leave it alone for some hours, to see what happens...
let`s see...
I still have some hope
nothing hapens, i used usb monitor, and in a certain point, there is no activity!
any more ideas?
superhiperclim said:
nothing hapens, i used usb monitor, and in a certain point, there is no activity!
any more ideas?
Click to expand...
Click to collapse
send it back to vodafone I guess
mb
Hi,
I didn't see any post about using MTTY on Kaiser.
If I did a bad ROM flash with my previous device (HTC Universal), I could always fix this by clearing the FAT table with MTTY.
Believe me... if you flash and it stops ad 85% you will be very happy if you can use this tool!
Reason I started this thread is to help out people who are having such a problem with there Kaiser!
This is the correct procedure to get you out of trouble
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
Incase of an emergency it could be very helpfull I think!
Thank you all for providing the input in this thread so I could make this small user manual!
Happy flashing!
Leo
Well... seems like nobody bricked his device yet!
That's cool....
I've read in many places about people using MTTY on thier Kaiser to get it to boot after a bad flash, but I can't remeber where. And I don't know where they got their info from.
I could attach MTTY here but I'm a bit scared if I do is that people going to blame me if they brick there device!
That's why I'm asking someone has experience with it.
It could be usefull for a lot of people.
DaveShaw said:
I've read in many places about people using MTTY on thier Kaiser to get it to boot after a bad flash, but I can't remeber where. And I don't know where they got their info from.
Click to expand...
Click to collapse
You supply a ROM that people can use to Brick thier devices (if they don't Hard SPL).
I suppose that's why they invented Big Red Font's and disclaimers.
If you do decide to post it, I'd get _Alex_ or Mike to add it to the Sticky.
P.S. I have yet to expirence it myself.
Hahaha... yes you are right
Ok I will attache MTTY.
Thanks,
DaveShaw said:
You supply a ROM that people can use to Brick thier devices (if they don't Hard SPL).
I suppose that's why they invented Big Red Font's and disclaimers.
If you do decide to post it, I'd get _Alex_ or Mike to add it to the Sticky.
P.S. I have yet to expirence it myself.
Click to expand...
Click to collapse
MTTY (How to fix a bad ROM flash?)
Is this thread can help you ?
http://forum.xda-developers.com/showthread.php?t=370169
I can't find the original post that talk about the procedure to unbrick kayser with
MTTY.
Hi !
I used it once.
The "info 2" works as designed ;-)
greetz
A clear procedure would be nice so you can unbrick your device easy using MTTY.
Thanks,
tyoine said:
Is this thread can help you ?
http://forum.xda-developers.com/showthread.php?t=370169
I can't find the original post that talk about the procedure to unbrick kayser with
MTTY.
Click to expand...
Click to collapse
Thanks for confirmation!
flushbeer said:
Hi !
I used it once.
The "info 2" works as designed ;-)
greetz
Click to expand...
Click to collapse
If you have a bad flash....that's no reason to worry.
I haven't had to use MTTY to recover.
In most cases, if there's no issues with the Rom itself...you can pop out the battery and re-flash the same ROM from BootLoader Mode. This will also work if for some reason your computer crashes or loses power & restart during the FLASH.
If the Rom has issues.....the flash will not complete and the device will be stuck in BootLoader Mode. At this point,you must FLASH a FACTORY ROM!!
Pop the battery off 1st, power up the device, device will power up in BootLoader Mode, connect to pc & FLASH your devices FACTORY ROM. This will restore your device back to it's original out the box settings.
The above only works if the device has been put through the Hard SPL or SuperCID process.
I personally have never tried to flash a cooked ROM without unlocking any of my devices. From what I've read what others have experienced...the flash would just fail and they're stuck in BootLoader Mode.
Myself ... I've experienced bad flashes, bad cooked roms that I've cooked, lost power to a pc & had my pc crash during a flash. Listed above is how I've recovered. There is life after Bootloader Mode.
The only time you have to worry is if your device does not power up at all
As a public chef...it's your responsibility to set the parameters of your ROM! Meaning, Radio, HardSPL, program conflicts, etc.
You are not ultimately responsible if someone bricks their phone but if they pushed the issue, you could be hit with some form of liabilty because you failed on providing a simple Disclaimer that sets the expectation.
I hope I've been helpful.....
That's clear
Thank you,
Leo
Okay, MTTY is a very useful tool & can help save your butt on many occasions.
A few of those occasions include:
1. Bad flash or installation of HardSPL
2. Bad Flash of a ROM.
There are several other problems that can arise & be mended with the use of MTTY. The most common use is for recovery of any flash process resulting in an RUUBNH error.
For most of these error you want to use MTTY to reboot the low level CE of your device to flush out any bad blocks.
Use of MTTY to recover from these errors is usually simple. The basic outline of how to use MTTY to resolve these errors is as follows:
1. Right click on the quicklaunch activesync icon on the lower left quadrant of your pc. (You can also just open up the A/S program)
2. Select Connection Settings.
3. Uncheck the box labeled "Allow USB Connections" & then Click "OK".
4. Open MTTY & select "USB from the Port options drop down menu.
5. Select RTS/CTS from the Flow Control Settings & click "OK"
6. Pay attention, because for a brief mmoment MTTY wil report whether or not it could establish a port connection to USB. If you are successful, a Command window will open.
7. Hit the "Enter" key on your PC twice. You should then see a command prompt that looks like this "cmd>".
8. At the command prompt (cmd>) you should enter the command "boot".
This will reboot the device & report back about any errors or bad or erased blocks.
9. If your device was just hung, it should be fine after the reboot. If it returns to Boot Loader however, it means there was a problem with bad blocks.
10. If errors were reported & you end up back at the Boot Loader screen, then repeat the "Boot" Comand at the (cmd>) prompt.
It can sometimes take two or three boots to fully recover from RUUNBH errors, so if at first you don't succeed keep trying & remember to keep notes about any errors reported in the MTTY info window.
Other Information: MTTY needs to have full access to the USB port. Some anti-spyware, anti-virus & firewall programs can prevent MTTY from gaining the port access it needs. McCaffee in particular should be temporarily disabled & some firewall programs may also need to be disabled.
don't work damn
this is my pda
RUUNBH
KAIS 130
SPL-1.93.0000
CPLD-8
USB
this is mtty
cmd
Command error !!!
Cmd>boot
Command error !!!
Cmd>
this rom RUU_Kaiser_ATT_WWE_1.51.502.0_Radio_sign_22.45.88.07_1.27.11.31_Internal.exe start, but at 1% kaiser reboot...
anyone know how much htc customer care ???
pedro_se_rooot said:
anyone know how much htc customer care ???
Click to expand...
Click to collapse
When I sent mine in to look at a problem with connecting via 3G, I was quoted:
a) I'm responsible for shipping to the centre in Texas, US. (Don't know if there might be one closer to you).
b) There would be a charge of USD$28 for diagnosing the problem and producing an estimate to fix. They would call me with the estimate.
c) If I agreed to the fix, the $28 charge would be waived and I would be charged the estimated amount.
d) If I decided against the repair, I would be charged the $28 fee.
e) They would also charge for shipping the unit back to me, typically, about USD$50 for North America.
In my particular case, however, they have repaired the phone and shipped it back -- apparently at no cost to me, other than getting it down there. I guess they figured it was a 'in warranty' problem.
/drt
Hi there,
Is your device dead or still responding?
Can you come into bootloader?
Did you follow this step before you connected your device and opened MTTY?
It's very important you do!
1) Kill activesync processes: Ctrl+Shift+Esc in Windows to bring up Task Manager. Kill wcescomm.exe and WCESMgr.exe (by selecting the task on the processes tab, and clicking the End Process button below)
Please tell me?
pedro_se_rooot said:
don't work damn
this is my pda
RUUNBH
KAIS 130
SPL-1.93.0000
CPLD-8
USB
this is mtty
cmd
Command error !!!
Cmd>boot
Command error !!!
Cmd>
Click to expand...
Click to collapse
the device iss not dead (i think) but with Mtty work only info and task 8.
i've follow all the step and killed active sync.
EUREKAAAAAAA
i've follow this guide
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into the cradle
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.
Hello,
I have flashed my O2 XDA IQ (HTC Tornado) with Tornado_WM6_Platinum_Edition_-_SP1, but after the 100% progress, the phone rebooted and stucked on Bootloader. I have tried to launch mtty, but there`s no open ports so mtty cannot start. Can you help me anyway?
Thanks
did you tryed to hard reset him?
I`ve tried, but after the "Press 0 to restore factory defaults..." screen, the Bootloader appears again.
I have the same problem with my spv c600.
krivul said:
Hello,
I have flashed my O2 XDA IQ (HTC Tornado) with Tornado_WM6_Platinum_Edition_-_SP1, but after the 100% progress, the phone rebooted and stucked on Bootloader. I have tried to launch mtty, but there`s no open ports so mtty cannot start. Can you help me anyway?
Thanks
Click to expand...
Click to collapse
first disable usb connections in active sync, then start mtty ans select usb as port.
but why not flash it again. just have the phone in the bootloader and the flash program should find it.
just read this and you should be fine:
http://forum.xda-developers.com/showthread.php?t=324557
walram said:
first disable usb connections in active sync, then start mtty ans select usb as port.
but why not flash it again. just have the phone in the bootloader and the flash program should find it.
just read this and you should be fine:
http://forum.xda-developers.com/showthread.php?t=324557
Click to expand...
Click to collapse
I cannot start SPV service and SDA app. unlock. "Please connect SDA". That`s why i cannot set SuperCID and install the ROM
try to flash your orangianl rom you know the one that comes with the phone
Unfortunateli i don`t have the original rom right now, and i can`t find anything at the O2 website.
have you try killing activesync then open matty.exe typing info 2 then press enter then typing format BINFS then press enter again then flash one of the roms form this forum
When i type it appears this:
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSO2__0501 ‘©öIHTCE
Cmd>format BINFS
Not allow operation!
krivul said:
When i type it appears this:
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
CMD55 failed
HTCSO2__0501 ‘©öIHTCE
Cmd>format BINFS
Not allow operation!
Click to expand...
Click to collapse
did you cid unlock your phone?
No, because when i start SDA_ApplicationUnlock.exe it tells me that the SDA is not connected.
krivul said:
No, because when i start SDA_ApplicationUnlock.exe it tells me that the SDA is not connected.
Click to expand...
Click to collapse
see thing is you were ment to cid and unlock your phone before you flashed your phone.
Is there any way to restore the original rom?
i found this o2 rom for you:
ftp://xda:[email protected]_Complete_Updates/O2/xda-phone-update.exe
i guess it is an o2 rom because it is in the o2 dir. put your device in the bootloader and try to flash it. good luck!
walram said:
i found this o2 rom for you:
ftp://xda:[email protected]_Complete_Updates/O2/xda-phone-update.exe
i guess it is an o2 rom because it is in the o2 dir. put your device in the bootloader and try to flash it. good luck!
Click to expand...
Click to collapse
Thank you, i`ll try
I have tried to launch the .exe, but "RAPI.dll is missing"
Please ignore last post There was my mistake. I`ve tried that rom, but it is not for my device.
Thanks anyway I will keep fighting
you will need to try to flash it from a backup made on a sd card that should work i think
If the phone is legitimately stuck in boot loader, open AS and make sure you disable "Enable USB connections". If the ROM is intact, connect to boot loader using MTTY over USB and issue 'ruurun 0' and then 'ResetDevice'. Let us know what happens.
Today I'll try to flash another rom that I have but when I run SPV-Services It doesnt found a page in the internet!!- connection to the internet is normal
check your firewall, turn it off if you can
I doesn't use it!
Open Microsoft Active Sync, click File -> Connection Settings -> where it says this computer is conected to: usaully is automatic change to internet
I make so ,and I downloaded new one from karhoe's website but the same problem!! Can you try to run SPV-services?? or can your send me your one by the ICQ??? I make SuperCID when I flash previous rom but now I can't!
Oh....when I try http://www.spv-developers.com it also doesn't work!! Maybe trouble in this?
If I SuperCID my phone when I flash the previous rom, can I skip this step for the next roms?
spv-developers is not always online...
Hey recently happened to me the same with svp however If you SuperCID your phone before you'll be able to skip this step but to be sure that your phone have SuperCID check it with TeraTermPro, I guess you know the steps if not they are:
1.Disable usb connection of the ActiveSync(Uncheck allow usb connections).
2.Unplug usb cable.
3.Turn your phone off.
4.Press the camera button and plug the usb cable(You'll see thw white screen and seconds later the three color screen.
5.Run TeraTermPro.
6.Select Serial and in port: USB then ok
7.Type: info 2
and if in the end of the list you see supercid htc or something like that it's done!!
Close TeraTermPro and just run any ROM you want and voilaa!!
Hope this be useful for you.
However if you don't see your phone superCID tell me and I'll tell you how to do it without svp services. By the way if you dont see you supercid your phone to get back to the phone OS just remove the battery and turn it on.
See ya from Mexico!
Hey check my post http://forum.xda-developers.com/showthread.php?t=412139 Hope you reach SuperCID your phone!!
See ya from Mexico
Tera Term says:GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x3B880000 Bytes
HTCSSuperCID ' HTCE
as I know it means that device already SuperCIDed!?
Please help!
First SPVServices cannot connect to the remote site.
Then, I tried the alternative using Unlock_SuperCID_Your_SPV_C500_550_600.rar. Followed every step exactly. When I run Lokiwiz.bat, here is the output from the MSDOS window:
....
--------------------
U. Unlock
L. Lock
C. CID Unlock (SuperCID)
Q. Quit
--------------------
Type the letter and press Enter: C
CID unlocking mobile... DO NOT DISCONNECT UNTIL THE PHONE REBOOTS!
ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom
to indicate the remote party has initiated a graceful shutdown sequence.
opening: lock_backup.bin: No such file or directory
This exe file was created with the evaluation version of Perl2Exe.
For more information visit http://www.indigostar.com
(The full version does not display this message with a 2 second delay.)
...
Then, I just try invoking pdocread manually, regardless of what command line argument I put, or no argument at all, the response is always the same " ERROR: Unable to open WinCE file '\windows' - Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence."
From ActiveSync, I do see \windows, but as a directory, not a file. Anyone got any inside or suggestions?
PLease, please help! Thank you so much!!!
/dan
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).