Hi All,
I have been trying to unlock my T-Mobile MDA Vario 3, after repeated trials I managed to copy SSPL-KAIS.exe onto the Device, started it, then unpug and plug back the USB.
Then I followed the instructions and the flash update process started, this went up till 95% complete, then it failed with an update error.
Now when I reboot the device I get a tri colous display which says the following by the top left hand corner:
Kais 130
SPL-1.56.0000
CPLD-8
At the bottom it says Serial, then if a USB is connected, it sasys USB. If I try to run the flash again, this time around it is stuck at 0% and eventually returns an update error.
Any help will be much appreciated.
Thanks
Please ask in the thread discussing the unlock method you are using.
Related
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
Hello all. I have followed the instructions to get wm6 and got stuck on step 9 of Karhoe's guide. Activesync will no longer see my device. so i cannot move forward. my phone is stuck on bootloader screen. After 'resetting device' in terapro. i saw the splash screen on my device then it went immediately to the bootloader color bars. everything else showed exactly what was on Karhoe pics. i just need activesync to see my device so i can proceed. any suggestions please. Thank you very much.
Activesyn will not see your device as it has been wiped clean of windows. Since you will need to be in booloader screen to install wm6, it doesn't matter if your activesyn sees your phone or not.
I ran into the same issue, i had to actually disable the 'allow usb...' option in activesyn so the romupdater utility can see the phone. So try it both ways.
enable it as suggested and just run the next step of installing the wm6gsmupdate...if you get some message saying connection error, then disable it and try again.
no activesync. Error [264]: Connection
thanks for the reply flashhsalf. it has not worked out for me tho. i tried both ways several times. enable/disable usb. i get same ERROR [264]: Connection.
im going to try it with a different laptop.thanks again.
Once I have this error too. Just reboot my PC and format BINFS one more time and all became fine. Don't know that is the reason, but this trick was helpfull
Have You re-enabled "Allow USB connection" @ connection options in Your Activesync??
got it to work...!!!
thanks all. i tried what was suggested all day...then when i went home i tried again with no success. to the point where my battery just died. i thought it was a paper weight at that point. but i decided to plug into the charger and the bootloader came up again. this time without the USB indication in the lower left corner. after a 2hr charge i took it to the same laptop which i rebooted. enabled usb then it worked! strange but glad i got it to work. Thanks again folks!
i updated to 6.1 but im experiencing issues with internet. ERROR
the remote party has ended this connection. this is the case with MMS as well. anyone experience this?
xdabe said:
Hello all. I have followed the instructions to get wm6 and got stuck on step 9 of Karhoe's guide. Activesync will no longer see my device. so i cannot move forward. my phone is stuck on bootloader screen. After 'resetting device' in terapro. i saw the splash screen on my device then it went immediately to the bootloader color bars. everything else showed exactly what was on Karhoe pics. i just need activesync to see my device so i can proceed. any suggestions please. Thank you very much.
Click to expand...
Click to collapse
i am also stuck to the same point ..
please help me what to do , why does this happens ..
i am very nervous ...as i cant make it a paperweight...
please help ..
thanks
my device is IMATE SP5M
and i have correctly done steps upto 8...
and when i try to do step 9 i only get three color boot loader screen
my device is super CID
info 2
GetDeviceInfo=0x00000002
+ SD Controller init
- SD Controller init
+StorageInit
***** user area size = 0x7820000 Bytes
HTCSSuperCID ' HTCE
Xdabe if you actualise Radio ROM, before upgrading to WM6.1 you wouldn't notice that problem with an Internet.
Try upgrading Radio ROM for your device.
Gsmsikar once you are in bootloader, and have SuperCID, just start installing Radio ROM first, then OS.
Hi, Im totally new to smart phones, and only received my phone today.
I was having problems sending sms messages, every time i received a message saying "wait 15 Seconds", after researching the net, i found that by updating the rom, i could get over this problem, i tried to attempt this but am now completely stuck.
Every time i switch on my SPV M600, its goes to a red,green,blue screen.
the IPL is 2.10.0001 and the spl is the same.
I have active sync on my pc, but i cant make a connection now.
Really stuck, please help.
many thanks
(Im in the UK and its a UK handset on the Orange network(
What ROM where you attempting to upgrade to?
To get the device back, I would say "Read the wiki" but it's down!!!
Download this ROM.
In ActiveSync, disable "connect through USB" (File->Connection Settings).
Put the device into bootloader (the three coloured screen) and connect it to the computer using the USB cable.
Run the file you downloaded earlier. This should then install a new ROM.
From there, just wait for it to finish.
Now, it should work!
From there, you could re install the Orange WM5 ROM, or try upgrading to WM6. Make sure you read all the relevant guides first!
thxxxxxxxxxxxxxxxxxxx
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).
There are threads covering your situation already, search for them then read them. If you still are stuck then post in one of them.
dear all,
first at all: I´m completely new here, so hello.
I finished reading the Wiki twice, also the guide from 'mskip' (Flashing your First GSM Raphael Rom (For Noobs)). very good and sounds very easy.
now I downloaded this file: RaphaelHardSPL-Unsigned_190_1_3
when I´m trying to flash, it results in a "error 202: connection". could the windows mobile device manager be a reason, because here is just an explanation with activesync. as I use win7 64bit, activesync will not run.
I also checked lots of posts here, but did not get a right answer which could lead to a solution.
btw I have the "MDA Vario IV"-version.
greetings, tris
EDIT:
Update: Now I downloaded "TAEL ROM v6.28244 RC2".
Connected mobile to PC, waited until it is connected via 'windows mobile device manager'.
Proceeded with the update (my image is 1.69.111.6) until the screen turned black and a progress bar is shown (0%). now error 262 appeared. have to unplug USB cable, reinstall battery and restart. old system is still working. what am I doing wrong? btw, same error on my laptop with win7 32bit with fresh installed 'windows mobile device manager'.
EDIT2: okay, and same on my other laptop with winXP and activesync.
You need to flash hard spl before doing anything else. Try putting the phone into bootloader (hold volume down, then soft reset), then connect it to your PC once it's in the tricolor screen and run the hard spl exe.
After that, just flash roms off your sd card. Make sure it's FAT 32 format, rename the ruu_signed.nbh to RAPHIMG.nbh, put it on the sd card root, and then go into bootloader and follow the instructions.
volume down and reset done. phone switched to tricolor screen. then I started 'RaphaelHardSPL-Unsigned_190_1_3', phone switched to gey screen with progress bar. 30 seconds later after 0% progress: error 262 appeared
EDIT: also when trying to update via bootloader, my image (1.69.111.6) will be left blank, I can´t see the version number which is currently installed.
I just hope you have a GSM TP/RAPH...
RAPH300 -> "T-Mobile MDA Vario IV"
but why do you ask? do I have the wrong software?
Just hear of those bad incidents with CDMA phones and GSM ROMs is all...
What does it display on the bottom of the screen when you boot into the tricolor screen/bootloader before you connect it to your PC and then after?
first serial, later USB
oh my god! *facepalm* okay for all the noobs out there: look at your phone. if you use HardSPL for the first time, you have a short timeframe to confirm "unsigned access to bootloader" via touchscreen. if you don´t do so, you will result in connection error 202 / 262.
thank you all, it works