I realize this information is on the HTC website but I have seen alot of questions lately regarding these errors. I decided that maybe, just maybe it might help someone with an error when flashing a rom, radio or splash and they can't quite figure out what the error is referring to. I also figured that this might lighten the load that GSLEON3 has been seeing lately with all of the "HELP, I think I BRICKED my phone" threads that keep popping up. Maybe it will help and maybe it won't but I thought it might be worth a try. I'd like to say thanks to OLI, Jocky, all of the rom cookers, GSLEON3 and XDA. You people make this fun.
I hope this helps someone.
? ERROR [202, 204] : CONNECTION
? This error message will appear when the device is not connected to ActiveSync correctly. Make sure
you properly connect the device to the PC through ActiveSync before running RUU.
? ERROR [206] : MEMORY ALLOCATION
? ERROR [280] : UPDATE ERROR
? When you see any of these error messages, close other running programs on the computer and run RUU again.
? ERROR [208] : FILE OPEN
? ERROR [210] : FILE READ
? These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
? ERROR [212] : FILE CREATE
? ERROR [214] : FILE WRITE
? ERROR [222, 224] : DEVICE NOT RESPONDING
? These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
? ERROR [220] : MAIN BATTERY POWER
? This error message will appear when the device's battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery
when it is upgrading the radio).
? ERROR [238] : FILE READ
? This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
? ERROR [240] : FILE OPEN
? When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again. Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up. Thanks ConfusedSTU.
? ERROR [242] : INVALID LANGUAGE
? ERROR [244] : INVALID MODEL ID
? ERROR [294] : INVALID VENDER ID
? ERROR [296] : UPGRADE ONLY
? One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
? ERROR [246] : DEVICE NOT RESPONDING
? This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
? ERROR [260] : UPDATE ERROR
? This error occurs when there is an "open port error" before upgrading the CE ROM image. Solution: You can reset the device and run RUU again. If you still encounter an "OPEN PORT ERROR" again, reset your computer and try again.
? ERROR [262] : UPDATE ERROR
? This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
? ERROR [300] : INVALID UPDATE TOOL
? This error message will appear when you use the incorrect RUU version to upgrade.
? ERROR [330] : ROM IMAGE ERROR
? This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Nice one mate, at leat this will give people who flash some idea what to do when or if they get errors flashing.
great find thanks for posting this will be useful for everyone.
Obligatory "thank you" post.
haha ok ok mistake now i see the solutions xD!
edit...............
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Confused Stu said:
Thanks P1T.
Just to put one in laymans terms from real life experience:
ERROR 240
Check that the contents of the folder is a KaiserCustomRUU.exe file and an RUUSigned.nbh file. If you put the os-new.nb file in by mistake instead of the .nbh, this is the error that shows up!!
Click to expand...
Click to collapse
I'll add this to the post. Thanks Stu.
_Alex_ said:
I thought everyone knew that these error codes were included in the .doc files that come with shipped ROMs (and removed within custom_ruu.exe).
Guess not Great post P1tater!
Click to expand...
Click to collapse
I thought so to but I have had to answer a couple of these lately and was hoping that this might help to clear a few things up.
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
RPG0 said:
Bump (keeping it on the first page) & +1 for sticky
Oh, i would change the name to start with "Flash error codes" or at least include that in the title.
Click to expand...
Click to collapse
I can make that change.
Thanks for the info pal
helpful! thankx
Wiki
Ported to the Wiki
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Ta
Dave
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
iXiR said:
Thanks dude. Great work. You put a lot of effort in this kind of handy things.
Oh, by the way, do you have a social live?
Click to expand...
Click to collapse
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
DaveShaw said:
I Can't speak for P1, but nope, I work, go home, play with my Son and either relax in front of the Telly or play on my PC.
Everynow and again on a weekend I'm forced into meeting something called friends by my better half
Dave
Click to expand...
Click to collapse
That's similar to my own schedule. P1 got to have a secret in finding time for this kind of things
ERROR 200
I got this error 200 "get newer update utility" I am using windows vista 32 bit.
where can i get a newer update utility? thanks
I-mate JasJam upgrade error
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
rumjar86 said:
hey guys no matter what i do even if i do a reset on the phone and restart the computer i keep getting the 260 error when doing the rom upgrade. i am using windows 7 and have had no errors with anything ever with it.
Any ideas?
Josh
Click to expand...
Click to collapse
Try resetting the phone and the computer to make sure that no other processes are running. Then try putting phone into bootloader, and when sync'd try flashing from there.
Related
Made a huge error.....didnt go through forums and read instructions before trying to Flash a German T-Mobile MDA Compact to a English ROM....
The device is completely dead....
Followed all the steps required to get it back up...It is refusing to do so though....
Used this thread:
http://forum.xda-developers.com/viewtopic.php?t=19500
One thing to note is that I am not using the AC charger, am using the USB cable to charge the phone.
Can someone please helpme...
Haven't got past the bootloader mode...
If you followed the instructions from the other thread, it should have started flashing.
Some things to check on:
1) Did you do a full d2s before you attempted the upgrade? It's always good to have something to fall back on.
2) If you can get to a bootloader screen, all is definitely not lost.
3) Sometimes, it takes 4 or 5 minutes for the "Press to flash" comes up on the screen so be patient with that.
4) Make sure you did exactly a 416 byte copy from the original rom file in to the new flash file.
5) You can only write an nb1 file from the pc AFTER it has been created from the pocket pc. If the SD card has been pc formatted, the nb1 file will write to it but the pocket pc won't recognize it and will just sit there at the bootloader screen.
HTH
I think I fired the MDA
Well I did not create the nbf file from the ppc, downloaded it from the the forum FTP. I do not have the backup of the nbf file. As I mentioned I did not read the forums before trying the update.
I just downloaded the T-Mobile ROM update and tried installing it. Obivousioly it didn't work, Game the dreaded the 112 error in the 3rd step.
Am not even getting the bootlader screen now..
Any ideas on how I can get this device up and running.?...
ok, need some clarification here. "What" are you trying to load (nbf files or nb1 files) and how are you trying to load them (SD flash or the standard USB based upgrade)?
Easy enough to check to see if your device can still get to bootload mode....hold the camera and power switches in at the same time and hit soft reset with your stylus. After letting go of those and you see either "Serial" or "USB" at the top of the screen, you should still be able to recover from this.
Tried with the nb1 files not nbf (sorry abt teh error)..
The bootloader screen was showing up ...unitll I tried the T-Mobile MDAcompact_vers11201
After the 112 error while updating...the device now refusing to get to the bootloader mode.
Have I fried the device and made it unusable....?
hey just got back the bootloader screen...
Take the SD card out, disconnect the USB and tell me what happens when you hold the power and camera buttons in at the same time, then hit the soft reset.
Also, has the unit been charged recently?
Its showing Serial v1.00...after the reset.
Its been on the USB chatge all along.....
Great. If you get Serial at the top, this can be recovered.
If you want a good T-Mobile 1.12 rom file, go here and use this one:
ftp://ftp.xda-developers.com/Uploads/Magician/tmobile-uk_wwe_ROM_1.12.00(thereapermanl).rar
Unpack it and follow all the procedures about copying the 416 bytes, rewriting the file, etc. from the other thread. I have tested this rom file and it installs ok.
Thanks for the encouraging words...
Will it work even if I do not have a backup of the original ROM on my machine?....I only have the tmobile.nb1 file which I got from the XDA forums.
Lemme try using that and editing it.
Thanks a ton for your help.
You might be a little stuck for an nb1 flash if you don't have an original flash back up but don't fear. You can go here and get this WWE1.12 file and just do a USB type upgrade:
ftp://ftp.xda-developers.com/Magician/Shipped_ROMS/WWE_11200_128_11210_ship.exe
I know this one works too. It's ROM 1.12, Radio 1.12 and Ext_ROM 1.12. When you try to run the upgrade program though, it might give you a Country ID error. If so, use the attached upgrade program instead. If this one gives you a Country ID error again, close the program and just run it again. I've been down all these roads already.
Lemme get this right this time: I will be doing the following
1. Install the ROM as you have mentioned. With the country id hack if necessary
2. Hopefully by now the device would be alive. If so will take a backup of the ROM on the SD card
3. From then on follow the instruction given in the doc.
Hope I get it righ this time else Its going to be a long night for me.
Lemme know if I have to do anything else.
Either ROM will work fine for you. It just depends on whether or not you want I-Mate stuff on it or T-Mobile stuff on it.
Doing the USB upgrade will put the I-Mate ROM on but after that, it should be working and you can then do an SD backup, follow the SD flashing procedures and get the T-Mobile ROM on.
Good Luck!
The masupgrateut is throwing up a ruu.dll error?...you seen that one before?
What sort of error? Not found?
yup...
I extracted the ROM exe and found teh file...copied it to the windows folder..and ran the no id program...no error this time round but the update is still giving a COuntry ID error...
Been looking at various posts...specially this one...
http://forum.xda-developers.com/viewtopic.php?t=14973
Thinks thats gonna help?
ok...two things.....just run it again. The no ID program sometimes does that on the first time 'round so just run it again.
Second, stick this at the end of the RUU.conf file:
[CHECKCEID_TYPE]=1
ran the program multiple times...still getting the COuntry ID error...
Are you running this program? MaUpgradeUt_noID.exe
...with the change in the RUU.conf file?
I just noticed something....did you extract all the files to a single directory and just run it from there or did you just pull a few out?
ALL the files have to be in the same directory. This is also where you need to execute the installer program.
Error while loading ROM from CoreProKitchen... (not "HELP! I'M STUCK IN BOOTLOADER!")
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?
inneyeseakay said:
Okay, so I added my packages, etc and followed all the steps, everything worked up until the point where I flashed my phone. When it get's to 98% my computer pops up with the following error message:
-----------------------------------------
The instruction at "0x00405e9b" referenced memory at "0x0018a000". The memory could not be "written".
Click on OK to terminate the program
Click on CANCEL to debug the program
-----------------------------------------
I'm back up and running, but I would really like to use my rom. Any idea how to clear up this error and get this baby flashed?
Click to expand...
Click to collapse
Mabe you put too many files in the ROM ... how big is the nk.nbf ?
The nk.nbf is 60,161KB... that's smaller than some of the other nk.nbf's I have seen.
Anything else it could be? Redid the whole process, flashing again...
For an OS only nbf the file should be around 57/58MB - sounds to me like you over filled the ROM.
On XP if you put your mouse over the nk.nbf and it shows its bigger than 57.3meg then you will not be able to flash it as its too big (thats for a rom with OS, and splash screens. If you don't have splash screens I think its like 57.1). The other way to check is right click and choose properties on the nk.nbf. Look at the size (not the on disk size).
Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.
inneyeseakay said:
Thanks... I guess I overstuffed it... I didn't think it had all that much in it... oh well.
Click to expand...
Click to collapse
Try to optimise some big executables. That will surely give you couple of spare MB
Up and running now!
so I get the white screen of death when I try hardSPL v1, so I followed the alternate route found here: http://forum.xda-developers.com/showthread.php?t=354061
but...
I get ERROR [240]: FILE OPEN when I run kaisercustomruu.exe... I go through two 'next' buttons, and gives me the 'verifying information on my pda' dialogue and then gives me the error.... no progress bar or percentage or anything.....
any way to fix this? I really wanna get my radio rom going!
thanks
description of error 240 from hermes wiki here
ERROR 240 : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
huh. should work......
I extracted the flash-HardSPL.zip file and has these files in it:
KaiserCustomRUU.exe
kaiser_hardSPL_1.0.nbh
Use the "white screen" JumpSPL method. Only this time DON'T use the 1.93 version unless your device has the 1.93 MFG SPL version.
Close all other files on your PC, & change USB ports.
rx jr. said:
so I get the white screen of death when I try hardSPL v1, so I followed the alternate route found here: http://forum.xda-developers.com/showthread.php?t=354061
but...
I get ERROR [240]: FILE OPEN when I run kaisercustomruu.exe... I go through two 'next' buttons, and gives me the 'verifying information on my pda' dialogue and then gives me the error.... no progress bar or percentage or anything.....
any way to fix this? I really wanna get my radio rom going!
thanks
Click to expand...
Click to collapse
This is the second time you have created a new thread without reading...
WHERE IS THE IRON HAMMER (known as Kyphur)
AllTheWay said:
This is the second time you have created a new thread without reading...
WHERE IS THE IRON HAMMER (known as Kyphur)
Click to expand...
Click to collapse
i've no idea what you're talking about, chap
GSLEON3 said:
Use the "white screen" JumpSPL method. Only this time DON'T use the 1.93 version unless your device has the 1.93 MFG SPL version.
Close all other files on your PC, & change USB ports.
Click to expand...
Click to collapse
white screen JumpSPL... like in the link I provided in my first post?
Yep, just like that, only this time use the 1.56 version.
you mean JumpSPL1.56-KAIS.exe, right?
tried it already, no worky. tried 1.93 too, still no worky.
no solution available?
maybe i'm the only one having this issue
ok, update.....
it finally worked, for no reason! just out of the blues!
so now i did my HardSPL, but can't flash my radio rom using the customruu.exe file and the provided nbh file.
same 240 error.
Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls
wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Very nice....
task command does not work for me...
you may want to add "lnbs"
htctouchp said:
wow!!! another great thread brother .i really hope that some expert can guide us here.
u have not mentioned the 'task' command here. i was also sure that this command didnt exist for elf/elfins. but today i used snoopypro while flashing a ROM and what i saw was 'task 28' when the ruu was just about to finish. after seeing that, i'm confused a bit
PS: this might be useful a bit:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Click to expand...
Click to collapse
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?
ababrekar said:
what is that snoopypro? u can actually see what is being flashed on the device?
hey great going guys. these threads are gonna be rocking helpful for everyone. spl thnx to htctouchp for initiating this idea
is this (http://forum.xda-developers.com/showthread.php?t=379318) something similar?
Click to expand...
Click to collapse
snoopy pro is just a usb port sniffer, it will record everything that passes a port. u cant actually see the flashing data, but u can make a log file out of it and after the flashing is over, u can analyze that log file. that post which u've given as reference, does the same thing. it records the session (usblog data) using snoopypro which later on u can open in hex editor. just try it out while flashing a ROM, and analyze the log later on. may be u can also find something useful
Hey guys!
Has anyone used the ls command?
Is it used like:
Code:
>ls
or
Code:
>ls c:\dump.nb
or
>ls \"Storage Card"\dump.nb
I tried the first one and waited,waited,waited...but (1)I got bored and (2)nothing was really downloaded to my pc so aborted You can see what mtty shows right below:
Code:
Cmd>ls
clean up the image temp buffer at 0x8C100000 Length 0x03A00000
BOOTLOAD_PAGE_TABLE_BASE_C_VIRTUAL= 0x8C080000
Clear image temp buffer done .
MTTYDownloadImage
start download
*Edit1:I'm asking for this command because I think it's a way to dump your rom(IPL,SPL,OS,etc.)
*Edit2:I found this nice tool, but it seems it doesn't work for my phone!Could anyone give it a try too and confirm?
Reading through an SPL.nbh file with a hex editor yielded the following known commands (as listed in the first post here):
SetDsbDBGMSGT
ClearDBGMSG
ReadExtROM
WLANReset
SDSelect
emapiCountryID
emapiInit
emapiWlanMac
emapiPwrDwn
emapiRead
emapiTest
emapi
getdevinfo
ruustart
ruurun
progress
wdata
password
set
SetDebugMethod
checksum
ResetDevice
BTRouting
lnbs
ls
Attached is a text file with a copy/paste of the results from issueing these commands in MTTY.
From what I can figure out you can load an NB or NBH file using lnbs or ls, BUT only ony a Super-CID or CID-unlocked device otherwise you get an error
Code:
Not allow operation!
Error : DownloadImage return error (code = 0xFFFFFFFF)
So, bootloader commands issued through MTTY can be ery usefull for retrieving your Device ID and Model ID, and once CID unlocked you could load an image through MTTY instead of using RUUloader etc, but it looks tricky to figure out how to get things working for a CID-locked/bricked device.
Logic would indicate that somewhere in the NBH file would be a checksum relating to the Vendor-ID and/or Device-ID, having an NBH file where the ID and checksum don'y match would result in the 270 error - corrupt image (one could assume).
So, the big question in my mind at the moment is "How can one figure out where the checksum is in the NBH file". If we can figure out the address of where it resides, we could maybe use the checksum command to pull that info back? Then theoretically, to fix a bricked device all we would need to do would be hex-edit the NBH file to replace the vendor-ID and checksum with the correct one for the particular bricked device?
Thoughts/comments from any of our resident experts in USPL etc would be greatly appreciated!
Craig
good effort Craig
but how to revive an Elf(in) stuck in bootloader is still a mystery for most of us. lets hope for the best that someone out of us can unfold this mystery someday
Interesting!!!
Does anybody knows more comands Im searching for a hardreset via MTTY or a Cleaning DOC leaving behind the task 28 cuase in cmd> dont works... only in usb> i used it just once in a G3 HTCwizard then i cant do it anymore.
Maybe "format" command before the CMD>
kokotas said:
Do we know what commands does the bootloader accept through mtty?
If we find all of them and what each one does, couldn't we be able to revive a bricked device using mtty? <=The main idea belongs to htctouchp
Here is a list of possible commands(we will have to see which are real commands):
Code:
[SIZE="3"][B][U]Command[/U][/B] [B][U]"Usage"[/U][/B] [B][U]Parameters[/U][/B][/SIZE]
1.ESetDsbDBGMSGT
2.ClearDBGMSG
3.ReadExtROM
4.WLANReset
5.SDSelect
6.emapiCountryID
7.emapiINIT
8.emapiWlanMac
9.emapiPwrDwn
10.emapiRead
11.emapiTest
12.emapi
13.getdevinfo
14.ruustart
15.ruurun
16.progress
17.wdata
18.password
19.set
20.SetDebugMethod
21.checksum
22.ResetDevice
23.BTRouting
24.task "Unknown command"
25.lnbs
26.ls
Click to expand...
Click to collapse
Hi do you know a command for unlock the CID, because i tried to flash my phone P3300 an his broken, I can enter only in bootloader, every time when I try to intall a rom shows me error 300, so I think I didn't unlock the CID first time! Thank you and sorry for my english
Hi
You mention your device is P3300, this forum is about the Elf/in P3450 and P3452. No surprise it doesn't work ...
Use this link http://forum.xda-developers.com/forumdisplay.php?f=316
This is an alternative method for SuperCID the Tornado smartphone
Firs of all you need to download the uitils:
http://rapidshare.com/files/132988194/Unlock_SuperCID_Your_SPV_C500_550_600.rar.html
STEPS:
1.Extract files.
2.Now establish a connection between the phone and ActiveSync.
3.From the Decertificare folder copy the file Allow_decert.cab to the root directory of the phone.
4.Install Allow_decert.cab into the phone and reboot it.
5.Establish the connection between phone and ActiveSync then, from the same folder run Semi_decert.exe press Remove Lock button, if the phone was unlocked successfully a message box will appear and ask you to reboot again.
6.Establish the connection between phone and ActiveSync again, then from the Decertificare folder copy the file Full_Decert.cab to the root directory of the phone(Do not install it,just copy it).
7.Finally from the main folder run Lokiwis.bat you will see a msdos window with 4 options:
U-Unlock
L-Lock
C-CID Unlock(SuperCID)
Q-Quit
Select option C and press enter, after this the phone will reboot an your phone will be SuperCID.
To be more sure that your phone is SuperCID and using TeraTermPro util follow next steps:
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!!
I recomend you to perform a format BINFS before install any ROM
Hope this be useful for you all.
See ya from Mexico!
Hey thanks!
You're welcome! and I hope you'd got SuperCID your phone!!!
Great!!!!
Finally!! all these days without a solution to unlock these phones, then you came my friend and made my day.
Best regards from Colombia
Luis M
Data Crashes.
Followed the procedure precisely and at the end I got:
"Data crashes. Please contact your service provider."
I ran the TeraTerm to check what is the status of info 2:
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Right now I have device with bad CID block. I keep the original backup from lokiwiz, but I don't know how to write it back.
There is a thread for Wizard started and it looks like there is hope, just I need a tool to write the CID backup block back to the device.
Thanks.
SuperCID unsuccessful, 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.)
...
PLease, please help! Thank you so much!!!
/dan
TeraTermPro
Hi Bro, you now where i can find TeraTermPro???
if you can upload shotware, it´s better, thank you bro
Thanks !!
Brother thank you very much
to day i can unlock my first SPV C600 with your help
if you need anything from me, it´s done.
msn/email: [email protected]
pdt. afther you have SuperCid, and your phone reboot
run again lokiwis.bat and write U and Press Enter
afther you phone reboot, insert a simcard from
your company and enjoy it
download here teratermpro
unlockboxthis said:
Hi Bro, you now where i can find TeraTermPro???
if you can upload shotware, it´s better, thank you bro
Click to expand...
Click to collapse
Hey sorry for the delay but I've been kind of busy, TeraTermPro can be downloaded from here:
http://rapidshare.com/files/134350178/TeraTermPro.zip.html
hey I saw your post, sorry for the delay mhhh does your phone compatible?? I mean I tested with SDA (US) Tornado and I got success, I think you should try once again but now place files in different root.
to anewbie
anewbie said:
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.)
...
PLease, please help! Thank you so much!!!
/dan
Click to expand...
Click to collapse
hey I saw your post, sorry for the delay mhhh does your phone compatible?? I mean I tested with SDA (US) Tornado and I got success, I think you should try once again but now place files in different root.
Maybe
d1saster said:
Followed the procedure precisely and at the end I got:
"Data crashes. Please contact your service provider."
I ran the TeraTerm to check what is the status of info 2:
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Right now I have device with bad CID block. I keep the original backup from lokiwiz, but I don't know how to write it back.
There is a thread for Wizard started and it looks like there is hope, just I need a tool to write the CID backup block back to the device.
Thanks.
Click to expand...
Click to collapse
Hey bro why you dont try once again without the simcard??? or first with lokiwis try to unlock the phone and then try again, that may fix the problem
i also followed all the steps and when it reboots finally i get a message saying "data crashes contact oraanges services"
pls help
I vote for sticky!
Hi I have looked all over here and can't work out how to perform the format on the BINFS can someone help me here?
Please help
This tool broke my SP5m.
On startup im receiving a ''Data crash'' error that says ''go to service center''
I cant open my phone.
I reflashed offical i-mate_SP5m_WWE_2.6.331.2.exe rom and it comes again.
Please help.
tera term is showing this when i type ''info 2''
Code:
info 2
GetDeviceInfo=0x00000002
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Cmd>
How can i fix that ???
chaqueun said:
Hey bro why you dont try once again without the simcard??? or first with lokiwis try to unlock the phone and then try again, that may fix the problem
Click to expand...
Click to collapse
it dont works man.My phone is unusable with simcard now
Please help?
I tried unlock,cidunlock,lock but there is no difference ((
Hey bro why you dont try once again without the simcard??? or first with lokiwis try to unlock the phone and then try again, that may fix the problem
Click to expand...
Click to collapse
I tried few more times with and without a SIM card, no luck. If somebody doesn't know the lockwiz is designed for HTC Wizard, not for Tornado. Somebody said that ONLY CID unlock would work, but apparently not for all Tornados.
GetDeviceCID: Error - InitDecoder
HTCS ´í•6HTCE
Click to expand...
Click to collapse
Congrats, now you have basic PDA without Phone function. Remove the SIM card and you can use the device at least to back up all your contacts. The problem now is that you have bad COD block, which has the Certificate and the Radio information on it. I had backup of the CID block and tried to reflash it back to the device but the problem was still there. So I went to imei-check.co.uk, paid $40 and they fixed it with the provided software tool and unlock key file. It seems that Tornado has lack of developers, who can provide sophisticated tool which can backup and restore all memory blocks without the end user knowing the hex address of the particular memory block.
Successfully unlocked, thanks
(Qtek 8310)
This is a risky method for many tornados.Please use only spvservices.Dont use this wizard tool.And it can crash wizard too.
it can remove some keys from your sim block or write wrong keys and your phone gives data crashes error when your sim card is in.So you cant use your simcart.
Only the solution for tornado is buying a full unlock flash file that created specially for your imei.I bought it and my phone is working now
On wizard (not tornado) there is a project to rebuild keys without buying imi-check.com sim flash file:
http://forum.xda-developers.com/showthread.php?t=307558