Error 202 connection error when trying to install Hardspl - Dash 3G, Snap ROM Development

Hi
i'm trying to update to Hardspl, however the moment that my mobile turns black, the usb connection seems to disconnect, and the application gives me a 202 error, connection failed.
i am using the 1.19 maple version, since that't he rom version i currently have.
any ideas?

dzoku said:
Hi
i'm trying to update to Hardspl, however the moment that my mobile turns black, the usb connection seems to disconnect, and the application gives me a 202 error, connection failed.
i am using the 1.19 maple version, since that't he rom version i currently have.
any ideas?
Click to expand...
Click to collapse
just fyi, make sure your active sync connection is readable and full synchronisation is enabled. =)
-> 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.
even after running the RUU and it blacks out, u should boot in bootloader (hold volume up + power button) to check your spl version. if its 1.19.hard, then congrats. =)

thanks, however i checked the activesynch connection and all is correct, but i still get an error ... this time it's error 260 ..

Related

help in changing rom after duttys v4rtm

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

Problem with JumpSPL1.56-KAIS?

So, I used JumpSPL1.56-KAIS (because I was getting the white screen of death with HardSPL) prior to installing Dutty's WM6.1 and it worked great. Now, I'm trying to use it again to install a radio (1.58.26.20) and I get this error message on my Tilt:
"The file 'JumpSPL1.56-KAIS' cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. If the problem persists, try reinstalling or restoring this file."
I've tried to remove, redownload, retransfer, and reinstall the file, but keep getting the same error.
Has anyone had this problem and/or know what I'm doing wrong?
Thanks...
You must hard reset your device and then try again.
OK, I did a hard reset and tried again. This time it worked, but stopped at 99%. I recovered the connection and tried again. It stopped at 0%. I recovered again, but couldn't get out of the loop to try something else, so I soft resetted.
Now, I have the tri-color screen with the following
RUUNBH
KAIS1*0
SPL-1.56.000
CPLD-8
From reading some posts, it sounds like I'm stuck in the ROM update mode and I need to use MTTY to get back to the last known good state, but I'm not sure how to set up MTTY. When I try to run it with the port set to USB and everything else at it's defaulted settings, I get "USB port can not open."
I'm trying to do everything right based on what I've read on these forums, but can't seem to get on the right path. Any help is much appreciated.
- Uncheck "Allow USB Connections" in Activesync.
- Connect with MTTY
- Enter "boot"
- In case it again ends up in bootloader enter "boot" again
- If it boots in windows mobile flash "HardSPL" and nothing else !! (after running JumpSPL)
- If it doesn't boot in windows mobile, find the original rom and flash it (w/o JumpSPL)
How do I get MTTY to connect? It says "USB port can not open" when I try to connect. Do I need to change any of the default settings in MTTY?
afgoody said:
How do I get MTTY to connect? It says "USB port can not open" when I try to connect. Do I need to change any of the default settings in MTTY?
Click to expand...
Click to collapse
Uncheck "allow usb connections" in activesync (if that is what you use ..). Then put the phone in bootloader mode (tri-color display) and connect usb cable. Then start MTTY and enter boot.
Don't for get jock, you also need to select the RTS/CTS connection type!!
If you would like some one to walk you thru it, PM me. I can help thru MSN IM with file share. I've gotten good at this lately.
Thanks in a big way to Jocky of coure
jockyw2001,
Thank you so much for your patience. I am on a Windows Vista PC with Windows Mobile Device Center and have unchecked the "Allow USB Connections."
I think that a screen shot of how MTTY 1.42 pops up on my screen would help to explain my lack of knowledge with setting this program up correctly.
The Port dropdown has no USB selection available (only Com 1,2,3 & 7). How can I get MTTY to connect through USB?
Thank you
Sorry, I'm staying far from Windows Vista.
This guide will explain how to change your drivers to the xp.
GSLEON3: good work mate

stuck updating to wm6. activesync can nolonger see my device.

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.

TYTNII Flashing problem

Hi guys,
Yesterday I upgraded from my Vox (running Gonzo WM6.1) to a Kaiser and started reading up on how to flash a custom ROM. Much more info and ROMS than for the Vox!!!
Firstly, before I even checked here, I upgraded to the latest WM6.1 HTC Rom.
Since that, no luck. I've read several pages, wikis and what have you, but I can't get the phone flashed with any HardSPL. Tried several versions of JumpSPL and there after only connection errors when doing HardSPL. On using JumpSPL1.93 the words USB doesn't come up on the bootloader screen - only on 1.56 and the 3.28 on the phone itself.
On that - most posts says on the bootloader it would show "...Jocky..." or "...pof..." SPL version, but mine everytime just says the standard "CPLD-8". The leads me to think that somehow it doesn't want to run the custom SPL version. I tried the SDA unlocker tool too, but it says "The device can not be unlocked"
After trying 2 hours I'm ready to throw in the rope....
the word usb will not appear on screen!
you need to unplug and replug your usb cable, to shift from serial to usb
or use force usb versions of hardspl
stoutseun said:
Hi guys,
Yesterday I upgraded from my Vox (running Gonzo WM6.1) to a Kaiser and started reading up on how to flash a custom ROM. Much more info and ROMS than for the Vox!!!
Firstly, before I even checked here, I upgraded to the latest WM6.1 HTC Rom.
Since that, no luck. I've read several pages, wikis and what have you, but I can't get the phone flashed with any HardSPL. Tried several versions of JumpSPL and there after only connection errors when doing HardSPL. On using JumpSPL1.93 the words USB doesn't come up on the bootloader screen - only on 1.56 and the 3.28 on the phone itself.
On that - most posts says on the bootloader it would show "...Jocky..." or "...pof..." SPL version, but mine everytime just says the standard "CPLD-8". The leads me to think that somehow it doesn't want to run the custom SPL version. I tried the SDA unlocker tool too, but it says "The device can not be unlocked"
After trying 2 hours I'm ready to throw in the rope....
Click to expand...
Click to collapse
jahrami said:
the word usb will not appear on screen!
Click to expand...
Click to collapse
Yes it will, or it will not work. My Tilt has the exact issue. If I use JumpSPL 1.93, I will not get USB onscreen, and it will not communicate. If I use JumpSPL 1.56, I do get USB, and am able to communicate and flash.
stoutseun said:
...the words USB doesn't come up on the bootloader screen - only on 1.56 and the 3.28 on the phone itself...
Click to expand...
Click to collapse
If you load JumpSPL 1.56, and see USB onscreen, then follow the flashing instructions from that point (I don't bother with unchecking Allow USB Connections in ActiveSync), and HardSPL will flash successfully. If you get a communication error, switch USB ports; preferably to a different USB controller (i.e from front USB to back USB).
Thanks guys - I tried that all. Get to the stage where it shows the percentage bar and stays on 0% until the errors stops it all.
stoutseun said:
Thanks guys - I tried that all. Get to the stage where it shows the percentage bar and stays on 0% until the errors stops it all.
Click to expand...
Click to collapse
What error message? Each error number means something different.
Connection error. Tried various methods now and on two different pcs, but no luck. I think it's something to do with the phone being locked.
Is the SDA_Unlocker utility generic or is there a specific version for the Kaiser? I get an error saying "Phone is not unlockable"

[Q] Connection Error

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

Categories

Resources