Related
Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?
I ran the Hard-SPL on my HTC and it worked as it should. I'd say give that a shot, THEN try flashing the ROM of your choice.
-Mc
Problem is, when I run hard spl it expects activesync to be running, but in bootloader mode AS doesnt connect so Hardspl wont load =/
- Disable activesync usb connections
- Connect to bootloader with mtty and type the following commands to know your CID and Model ID:
Code:
Cmd>task 32
Cmd>info 2
Cmd>getdevinfo
Paste the output here, and also tell me which SPL version you have on your device.
Also, does the tri-color shows "RUURUN" or similar in the screen?
You should flash a ROM matching your CID to fix it.
Cmd>task 32
No card inserted
Level = FF
Cmd>info 2
HTCSCWS__001Ùü¤HHTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1*00CS_0HTCE
Cmd>
Device screen says
RUUNBH
KAIS1*0
SPL-1.56.0000
CPLD-8
Flash this ROM, should bring it back to life.
I'm leeching it now, 40% done, also FYI, I've posted on the Official ROM forum new links to most utilities and ROMs hosted on my servers off the rapidshare, to share free of charge.
Ahh, life saver =) Thanks, I'll be sure to add that rom to my list of full Kraiser roms on my web server, now to correctly flash it back with the HTC rom.
Thanks!
Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!
I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?
It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Lukstra said:
Same problem as TS. Bigger problem ... does anyone have the Dutch ROM?
Tnx!
Click to expand...
Click to collapse
ludovich said:
I got the same problem as Palmore. After 16%, stuck, then bricked. I am downloading the ROM pointed by POF (thanks man!!) hopefully will unbrick it. Now, how do we get the HTC Kaiser ROM on this thing? Anyone?
Click to expand...
Click to collapse
Run the Hard-SPL utility on your PC, and follow the instructions (sticky on this forum)
It will allow you to flash any ROM after that, I've flashed the AT&T Rom, the HTC rom and back and forth, pulling cabs out of the AT&T rom for the items I like (IM utility etc)
Palmore said:
Possibly the fastest phone brick in history... I did everything wrong...
AT&T Tilt, Windows Vista host machine
I ran the SSPL, NOT the Hard-SPL...
16% thru it failed
Rebooted, tri color screen, but not the same extact screen I had seen after running the SSPL on my Tilt.
Hard Reset, said yes take me to factory settings, back to same tricolor screen
Plugged it into a XP box, drivers installed, plugged in USB (it shows USB connection on the screen) Activesync of course wont go green
Loaded both the Kraiser rom and the Cingular rom, both fail at 1% and reboot the device and same invalid device ID..
Any ideas, aside from I'm a r-tard?
Click to expand...
Click to collapse
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......
andydempsey said:
If you are a r-tard, it must be catching - same situation here at 16% and 1% now......
Click to expand...
Click to collapse
LIFE SAFVER
nispen said:
It's on my phone. Tell me how do dump it and I ll send it to you.
Wouter
Click to expand...
Click to collapse
Hi Wouter,
I bought a new Kaiser today (yes now I have two of them ).
I will see if I can dump the Dutch ROM myself and see what happens next.
Thanks for your help anywhy!
- Lucas
Bricked
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.
Vista Problem.
First off, i had the same problem as you so i just found an XP box to use.
Second, even with XP i still managed to **** up because i did not read the directions all the way through. This device is totally different so make sure you read all the directions.
If you have no access to an XP machine then u can just "obtain" a copy of XP and dual boot just for flashing your device.
If you have no idea what I am saying then read some more. the hermes forums have some great information when it comes to flashing via Vista.
For all you guys that just saved between $300.00-$500.00. How about sending POF like %5 or %10 of what he just saved you...
I'm just sayin'
Later, Lew
Have you installed the XP activesync drivers under Vista? The Hermes Wiki mentions somewhere how to do that.
Jabbs19 said:
Ok, so here is my situation. I have a Tilt and Vista.
I ran HardSPL and I am at the tri-color screen. I have:
KAIS1*0
SPL-1.JumpSPL
CPLD-8
USB (in the middle of the screen)
I tried disconnecting and reconnecting it several times. I cant get HardSPL to run again (it hangs at the first section looking for ActiveSync) I tried restarting Vista several times. I can NOT turn off my device, as holding down the power button does not appear to work.
I have tried just running a couple of .exe roms (AKU 0.7.0 ROMS) and I get the connection error [264]. I cant re-establish my ActiveSync connection. In device Manager I have Microsoft USB Sync for the mobile device, but I cant get ActiveSync (Mobility Center) to see it.
I have tried opening MTTY to run "boot" but it says USB Port Can NOT be opened.
I just need some direction here, as it seems like everything hinges on my ActiveSync connection. I have been up and down the Wikis for Hermes and all the similar ones, and I think I am SOL.
I WILL GLADLY DONATE if thats what it takes for someone to help me. Thanks guys, I cant wait for my HTC Rom to work.
Click to expand...
Click to collapse
Best Forum Ever
I
I got it working. I had to pull the battery out of the phone to get it out of bootloadr, it was just plain stuck. Then, in Vista, I needed to F8, disable driver enforcement, I replaced the wceusbh.inf in device manager, and relaunched HardSPL and there she was! Now for the BigStorage.
Thanks to all that helped, I will be donating pof for sure
Hi All,
Out of the blue my HTC Vox stopped booting. I mean, it would load to the windows mobile screen and then stay there till eternity. Removing my memory card and SIM also did not help! I then tried the hard reset option.
Even after hard reset it sometimes boots(1 out of 15 times) and when it does...it hangs after 10 to 12 minutes. Still have not put my sim n memory card into the phone.
I tries flashing the ROM using the ARA 1.27 ROM. After it rebooted to the bootloader, the flash utility gave a connection error! It did not connect to ActiveSync and stayed at the bootloader screen.
I still do not know how to flash it successfully.
If anybody can help me out, I'll be extremely grateful!
Thanks
Prateek
take the battery out, put it back.
connect your Vox (USB).
Hold the camera button and turn on your Vox.
you should see a red, blue and green screen (if my memory works as it should) and the computer should recognize the device, though you won't be able to explore it with activesync.
Run the SDA_ApplicationUnlock thingy (if you need to)
now try flashing the device.
If it flashes but after 3% restart, you need to do a CID unlock right before flashing.
hope that helps.
Invalid Vendor ID
Hi MoRkusReX,
Its giving me Invalid Vendor ID. How do I CID unlock it?
Thanks,
Prateek
http://forum.xda-developers.com/showthread.php?t=330909
first post , download the last file:
Vox USPL- CID BYPASS.zip
There a Readme file in there, you should read it.
post back where you're done.
No Luck!
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
Only once I have been able to boot into my OS and followed the instructions given in the link. The phone comes to the Linux black screen and then switchers off. Then the ROM Update Utility with which i'm trying to update the ROM gives an error that "cannot connect to the phone".
So, now I need to flash my ROM from the bootloader itself. Have managed to get mtty and connect to the phone. But even trying ResetDevice command, the phone does not boot.
Can you tell me the exact steps to flash a new ROM from the bootloader itself including CID unlocking? Can it be done??
Thanks,
Prateek
prateekswarup said:
Hi MoRkusReX,
Since my phone is not booting into the OS thus I cannot use the UPSL_CID provided in the link.
...
including CID unlocking? Can it be done??
Thanks,
Prateek
Click to expand...
Click to collapse
yes it can be done.
you don't need to boot to OS, I couldn't either. after the steps from my first post here, run the uspl_116_jockyw.bat file. follow instructions.
that will unlock the CID.
Now the VOXs' screen should be white or so... then you run the ROM update thingy.
Hi..
I connected with the usb and got the bootloader screen.
tried running the SDA unlock program...the button to unlock the phone is grayed out. Cant click on it.
Next tried running uspl_116_jockyw.bat file
..cannot connect to phone and hence copy of haret.exe did not occur and neither did pmemtest run successfully...
What am I doing wrong??
ok..
first steps again..
battery out, back in.
connect USB
CAMERA button + Turn on.
now.. does windows do that USB sound? you know.. "tu du" ?
No sound....using win 2k Nt server edition...
but has detected my phone once on that USB and then allows me to talk to the phone using mtty....as in commands like ResetDevice work on the phone using mtty..
also, cannot get into bootlaoder mode with USB plugged in...
Steps and their results:
Disabled USB connections in activesync
Booted to the bootloader (red and green and Blue screen)
Connected the USB
"USB" displays on the left hand side corner
Now tried unlocking using Apllication unlock...grayed out button...
Tried running USPL bat but stops and says phone not connected when copying haret.exe
Using windows NT server 2003
if the SDA Application unlock button is grayed, of course the USPL won't work.
why "Disabled USB connections in activesync"?
And.. I doubt this is the problem but you should check on an winXP pc, I did it on XP.
No Luck!
Tried the same with USB enabled...same result
basically the thing we need to figure out is why your computer doesn't recognize the device.
the rest is obvious.
when I go to bootloader on my device windows pops up with a message says windows found device "and it's ready to use". like when you cannot every other USB item.
have you tried doing that on an XP system?
Going to do that now....lets hope it works....
Does ur activesync turn green when u connect at bootloader?
Also, I have removed my sim and memory card...thats okay right?
yeah, I removed both of them.
and no, activesync didn't turn green, but Windows recognized the device when I turned it on. turn on the speakers and wait for that winxp "USB connected" sound.
Still No Luck!
Tried doing the same on win xp...
no luck...
it connects to win xp ans says new device found...and ur USB device is now
ready to use...
after that i try application unlock it still gives me grayed out button....
ne suggestions???
Finally....
Finally got it done...
Thanks for all the help....
I managed to cold boot into the system for one time ans then SDA unlocked it and then ran UPSL .... it ran and then balnked out...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
then i flashed it with the ARA rom...
Seems to be working okay now..will test for a day and see...
thanks a lot
prateek
prateekswarup said:
Finally got it done...
then i disconnected the usb before the ROM update utility and unchecked the USB option in active sync...
prateek
Click to expand...
Click to collapse
I'm not sure this step was necessary but as long as it worked.. good times.
btw, how did you boot into the system?
kept trying hard reset and repeated booting...( it was booting 1 in 15 times type...)..and one lucky time it didnt hang..so used that window to slip in the SDA unlock and USPL..
thanks ...
you're welcome.
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
My Dear Samaritans,
IMPORTANT:
- My SD/Memory card is removed
- My Sim card is removed
I was upgrading to Tomal v8.9 on a vista 64 system via a virtual machine XP SP2. Update failed and I got stuck in bootloader.
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
Tried using v8.71 still crashed without any luck.
Moved to a pure XP SP3 desktop...
When I connect the device to the computer(s) "Serial" changes to "USB" but XP sees it as an unrecognized device.
Tried flashing again but same error as on the virtual machine.
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck. Everyone's issue is resolved as soon as they remove their SD or SIM, but I have neither and am also using XP with activesync's USB disabled.
Tried UNI_ExitBootloader but that does not find/recognise the device either.
If it helps -- My device is/was an O2 XDA Exec (Stock) which I had previously flashed with Tomal's v8.5
I am ready to try anything, please help!
P.S: The error is Error 112
Did you install ActiveSync on xp pc?
If not, do it now and try again.
I had similar problem. Had corrupted DOC sector
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
tomal said:
Did you install ActiveSync on xp pc?
If not, do it now and try again.
Click to expand...
Click to collapse
Already have activesync 4.5 installed with USB connection disabled...
Thank you so much for the prompt response and helpful thought!
enigma1nz said:
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
Click to expand...
Click to collapse
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Don't worry
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
blingin said:
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Click to expand...
Click to collapse
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
330e said:
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
Click to expand...
Click to collapse
There was no SD card when I began the initial flash but it still got stuck. Been trying without the SD and SIM but to no avail...
Thank you for the manual, downloading it now, will keep everyone posted in case anyone else is suffering from the same thing...
enigma1nz said:
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
Click to expand...
Click to collapse
Still trying, will keep you posted and thank you for the responses!
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
330e said:
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
Click to expand...
Click to collapse
It's the thought that counts not the language, thank you so much for your help!
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
your need to format your SD after flashing.
330e said:
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
Click to expand...
Click to collapse
tomal said:
your need to format your SD after flashing.
Click to expand...
Click to collapse
Tried the SD image method with a 128MB SD but didn't work. Maybe because I have a G4 and the method is for G3
managed to get a connection finally and ran MTTY, after "task28 55a" it just hung for a long time so I disconnected.
Tried running UNI_ExitBootloader.exe and now can get in and out of Bootloader but still cannot flash or connect...
Any suggestions welcome...
Try this....
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
martinbrettphilo said:
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
Click to expand...
Click to collapse
Thank you...
Xda2 stuck in bootloader screen after failed flash in vista
blingin said:
My Dear Samaritans,
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
When I connect the device to the computer(s) "Serial" changes to "USB" stuck within the bootloader screen
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck.
I am ready to try anything, please help!
P.S: The error is Error 112
Click to expand...
Click to collapse
Hi i have had similar problems also i have an XDA 2 pda originaly had wm2003 on it (tried to flash it to wm2003se ) can someone help me also im realy at a loss =C many thanks in advance (i will give more detail if someone actualy) replys to me
Wrong forum
Welcome to the forum
Universal does not means all devices, actually is a model
Please enter into the right section of the forum
Goos luck,
Can you Help?
I have an XDA II was on O2 uk network. I used to flash it all the time and knew my way around. however recently i flashed it in vista without thinking.. and as i upgraded the rom from wm2003 to wm2003se about 25% of the way through vista disconnected the device then it was unrecognised usb.. then vista started installing new drivers that recognised the device... however this then crashed flashing the rom onto the pda..
It wont soft or hard reset, i took the battery out for 24 hours and tried again and nothing.. the only thing on screen is that it says serial on the top of the screen (which changes to usb when connected but get error 101 when trying to reflash/ no activesync connection and am confused my mtty as when it does connect i cant type into the text area only paste)
on the bottom of the screen is v1.06 (which before the flash crash was V1.0 something lower than v1.06)
basicaly is the device recoverable as long as i have this serial / usb recognition by the device????? (using mtty i cant connect through ports or usb but thats because i dont seem to understand how to use it)
the other question is is there any other way to get a rom back onto the device without mtty or activesynch..
I pray that ysomeone will respond .. i miss my pda dearly
a thousand thanks in advance
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