Related
I have tried many times to upgrade the Rom Image on my HTC Tytn (Cingular 8525) with no success. I am getting a 260 error with the program located at this link...
http://forum.xda-developers.com/showthread.php?t=293665
I did first run the unlocking application to unlock both SIM and CID before running the upgrade.
I followed all the steps exactly and have had no success...
The following might be effecting my attempt:
I am running my pc on Vista
I am syncing with Windows Mobile Device Center
I have tried to solve this problem for about two weeks. Can anyone help me?
Mrvanx has a guide on how to prepare Vista for flashing, you can find it here.
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Same problem
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Same problem here trying to change the radio version after changing the bootloader........
Connection alwayse lost just as said above.
Any help will be appreciuated
justx24
Use the RUU wrapper with the NBH file you want to upgrade.
I still have the same issue, even when using the RUU Wrapper and any nhb.
don't use vista
Ok, got one step furthur
I reached the point where the ROM Begins to update, which is VERY good...
The ROM update Reaches 1%, then waits for 20 minutes...
Then I get a 262 error and have to go through recovery, try again, with the same result.
i have same problem plz help thnx in advance
compwiz2008 said:
This information still did not work. I get a 260 error even after updating the driver, which I did not do until now.
After investigating furthur I have realized what the error is:
As soon as the RUU says "Verifying Information on your PDA Phone..." the second time and forces the device to enter bootloader, the usb connection is lost between the device and the pc. Investigating furthur, the connection to my tytn is lost every time I enter bootloader, whether it is by Power+OK+SoftReset or forced by RUU. Does anyone know how to fix this bootloader connection problem?
Click to expand...
Click to collapse
Have you tried removing or adding a checkmark to the USB to PC in CONNECTIONS on your device? I remember having a similar problem when I installed Radio Rom 1.38 that my USB connection was lost with the pc . I am using XP when flashing so if you have no luck then do this on a XP machine.
Forgot to ask! What ROM are you trying to flash??
@compwiz2008 and ahmerpar
I read somewhere that running windows update will update WMDC........maybe give that a shot?
Maybe you can try to upgrade your ROM from your SD card.
Nope
Let me try that...
Still did not work
I'm probably going to just take my phone to a computer repair shop and pay them to deal with it, since I'm evedently doing something wrong.
I was trying to upgrade to radio v1.43 in the hope that battery life was improved over 1.41 however when it got to 8% it stopped and gave me an error i can't remember After atempting to recover, it got off the three colour screen now the 3100 stalls on the blackshadow version4 screen (bootloader screen?) and goes no further. I tried reflashing but got a 260 and using mtty, only getting 2 com port options, didn't offer any help.
I'm really sorry to have not been able to sort this with reading through the relevant post but I haven't found a solution. What else can I try?
Hi,
Could you pls advise what is your device made, model, SPL version ... etc.
Also did you try to do Hard reset?
I'm using now black MAJIK (and few days ago black shadow) with radio 1.43 with no problem.
its the SPV m3100 When I decided to go Black shadow I read up on mr vanx and made sure I had all the things I needed. If I remember right, when I came to upgrade to Majik the auto detect found the second option down
SPL-1.04/1.10 - 1.09 Bootloader. I've realized since I had a spaz and ran the RUU from the archive this time. From what I've since read thats not too cleaver.
I have tried a hard reset and took the battery out instead of pressing space.
I dont know if this information on the starter screen is of use
M 05
S 04
B 05 D 3lak
I'm not sure, but hard reset doesnt mean you take the batery out.
Please check that link:
http://wiki.xda-developers.com/index.php?pagename=Hermes_For_Beginners#hardreset
I was in your position (hanged on booting) few days ago, and when i did hard reset, it changes every thing to basic normal condition.
i meant when i did a hard reset when it asked me to press space to reboot I took the battery out. I tried again this time pressing space to reboot but I still get stuck on the loading screen. I can't connect by USB to the PC I'm guessing the drivers on the phone haven't loaded and I'm stuck as to what to do.
Does anyone have any ideas?
try look at it http://forum.xda-developers.com/showthread.php?t=286755
ok I've tried everything I can think of to connect the 3100 to the computer so I can reflash it but mtty gives only com 1 and com2 but no USB and neither those two work, active sync wont connect so I disabled it as suggested and running the radio ruu and wrapper wont querry the device. I am now at a loss as to what to do next someone must know what I should do. Please?
what is your SPL?
try this http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
sl is 1.09 i'd updated it on the previously successful black shadow flash
msn [email protected]
icq 150277111
AIM TazmanFH9
Yahoo bigfathairyboggart
I have tried changing KITL trasport but I am unable to select or chose either option. I have also tried the rversion command in the tri colour screen but nothing happens. I hope I'm missing something nice and simple but I get the feeling I'm not going to be that lucky. Please help
tcSPVm3100 said:
sl is 1.09 i'd updated it on the previously successful black shadow flash
Click to expand...
Click to collapse
I suggest you check again, press and hold the side OK button and the power button...then put the stylus into the hole in the bottom of the unit.
yeah I've done that it's "SPL-1.09"
I had this exact problem yesterday, with the same bootloader too. The phone would not pass the splash and IT refused to upgrade. I ended up downgrading to a shipped wm5 rom (in my case the cingular 1.30.502.1_1.11.00.00) which to my surprise actually worked as no rom radio or spl upgrade moved at al on my phone. Then upgraded back to black majik. I hope this helps.
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
tcSPVm3100 said:
Thanks. I downloaded the trial of wm5 from the windows website and it asked me to install .NET framework version 1 so I got that but it turns out to be 2.0 not 1.1 It would say it had repaired but it would say this with or without the phone connected.
Click to expand...
Click to collapse
Just download a WM5 ROM from the wiki page!
ok tried this too no luck.
Trying to use the one from orange (linked to through wikki) I get an 294 invalid vendor error however active sync cannot connect yet of course so is this to be expected?
I have however gotten a connection with mtty which is a step forward dunno what to do with it yet though except trying the password 0000000000000000 command but it not disabling the password. This then lead me to read for a further hour how to change it and I've got to be honest; it beat me. I have No idea what the hell its talking about. My head hurt with so much reading.
I get a no gsm pop up v briefly on loader. I so want my phone back
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
tcSPVm3100 said:
I have since tried CID unlocker just so i get something installed onto this brick but I either get a connection error or it telling me it can't install for some other reason. I can not set the password in mtty to 0000000000000000 so how do I do that and is this the first step to getting things sorted? "just running a rom install" is not happening I can get a USB connection in mtty and that is it. Is the fact i'm running SPL 1.09 a problem? I'm getting precious little help guys If i'm posting in the wrong place or something please let me know. I need thing thing back now. Hours are drifting by with me trying to get some head knowledge but I still need some guidance please
Click to expand...
Click to collapse
can u flashing HARD V7?,i think better u have IPL 1.04 SPL 2.10olipro first ,then try to flashing radio?
and did u try SD card.
In bootloader can anyone here connect with active sync? I can't so updating rom and radio flashes in the usual way isn't possible. Trying the hard spl again it tells me to make sure active sync is connected and as it isn't it throws back a 262 update error. 0% on the hermes and that's currently as far as I can get. I have no means with which to access the memory card.
The reason you get an invalid vendor ID is because your CID doesnt match....download a ROM which is for your device (an orange one?)...then try.
You need to read the wiki alot more before trying anything else since you are not aware of the vendor ID error...nor the fact you MUST use HardSPL.
I linked to the orange ROM from wikki and tried installing it. it was while installing THIS ROM SPV_M3100_ROMUpdate_0407.exe I got invalid vendor error.
Installing a recent DL on HARD spl v7 I get a 240 open file error that's one I haven't had before.
With all other attempts they all say they want an active sync connection.
I can not connect to the phone through active sync
so all attempts by me to flash anything to the phone using an RUU fails.
Hi Folks,
I'm stuck in the tri-color screen for bootloader 1.06.
I have DCD 3.2.0 w/3.42.02 radio on the XV6800 and was trying to upgrade to radio 3.42.30. My system is Vista 32-bit.
I ran the Titan Relocker and it put SPL-1.06.0000 back onto the device and was planning on then putting 1.2 onto it.
Running titan_exitbl.exe says "Cannot open USB port. Please make sure, that USB connection in ActiveSync is disabled."
Unfortunately it is now stuck and even after ending the Sync Center service I can't get titan_exitbl.exe to pull it out of the Boot Loader.
Ideas? Thank you!
I could fire up an old XP laptop and try it from there.
Loaded ActiveSync 4.5 on an XP laptop, disabled USB connections, ran titan-exebl.exe and the device is booting now.
I'll continue on and see what else I can screw up.
Loaded SPL 1.20
Loaded 3.42.30
Loaded SPL 2.40
Device is back to working! Off to see if GPS is back after being lost with 3.42.02.
titan-exebl.exe
Where can I find titan-exebl.exe? Google doesn't turn up any results other than here?
titan_exitbl.exe
Never mind... just located it on my own hard drive!
Cheers!
Stuck on Bootloader
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Try changing your spl back to 2.40.
Throwing it back into the tri color screen again and flash the sprint stock 3.35
But put it on the root of a fat32 formatted micro sd card in the flavor of under 2gb.
Just run the exe from your computer it will extract the files from the exe to some location on your computer, normally the ruu update folder.
There will be a ruu_sighned.nbh file locate it and copy it to the fat32 formatted card rename it TITAIMG.nbh
Let the phone boot into the bootloader and it should detect the file on the sd and update the rom for you, by stating loading ......
Then will prompt you to update press power key.
Sense you are not on sprint don't let the first time custimizations run ... pull battery once you get to your mobile today screen on first boot...
Use active sync or the sd method to update your rom to whatever you wanted originally.
Most full updates from carriers the ones that flash both the radio and rom will run regardless of the boot loader thats on the device.
Happy flashing
Just thought I'd toss in here that GPS does work, but I have to use GPS Viewer to get a lock on the satellites first.
softwind said:
OK... I've tried titan_exitbl.exe, and it still doesn't work.
Here's my problem in chronological order:
1. I've been having a few problems (bugs) in my current custom ROM (PPC Kitchen 3.49 version), so I decided to re-flash to a stock ROM, see if the problems were fixed, and then try to flash back to a custom ROM.
2. I tried flashing to the Sprint 3.35 ROM. The RUU showed the progress bar on both my PC and the phone. But at 0%, I got a message saying "an error has occured" - or something to that effect.
3. I decided that the error was because I was running a custom ROM, and Sprint didn't like that. So I ran the Titan Relocker utility, thinking this would cure the problem.
4. I followed the steps on the screen and then got a message saying the relocker utility had completed successfully. The phone rebooted and went into the tri-color bootloader mode.
5. I retried the Sprint 3.35 ROM update, but got the same connection error, and the progress slider would never move from 0%.
6. I decided the phone had locked up and performed a reset with the stylus. The phone rebooted and went back into bootloader mode. The screen shows "TITA100 SPL-1.06.0000"
7. And that's as far as I've gotten. I've tried several hard resets using the buttons and the stylus together. I've tried removing the battery and reinstalliong... but the phone just goes back into bootloader mode.
I've tried both titan_exitbl.exe and UNI_Exitbootloader.exe, and neither utility seems to help. I get a message saying that "All data was sent... the phone will reboot now... please check your screen". The phone's screen blinks for a moment, and then returns to bootloader. Nothing can get it anywhere else.
I've tried different USB cables and ports. Activesync won't detect it, but the utility update software does.
When I run the Sprint 3.35 ROM update utility, I get an error at 11% saying "invalid vendor ID" and the update refuses to run. I tried to run the Titan Re-locker utility again, but it requires an ActiveSync connection. I've tried both enabling and disabling the USB connection in ActiveSync, but that seems to make no difference. The utility simply says no USB connection is available. The ROM update utilities will detect the device via USB - they just refuse to work with them.
I also tried running a DCD Tital 2.1.0 Bell ROM. The progress slider freezes at 0%, and then I get a message saying the RUU has encountered communication errors during the update. I've been through the recovery process the utiity suggests about a dozen times... it sill returns the phone to the bootloader screen.
So I'm getting pretty frustrated... does anyone have any ideas?
Click to expand...
Click to collapse
please i have this problem how to fix this?
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
drewcam888 said:
Please state your exact problem and what you did to cause it. Including all versions of rom and radio and bootloader.
Click to expand...
Click to collapse
Thanks!!! Ok, i cant remember eactly what is the v radio but i think 3.35 or 3.42 i cant remember exactly it's one of these. the SPL 1.06 Locked i cant unlocked i cant use titan_exitbl.... the SD update doesnt work stuck on loading.., i cant update from pc stuck 0% then Recovery Error help me. I My phone is bricked? Sorry for my english....
Did you try to install 2.4 unlocker?
drewcam888 said:
Did you try to install 2.4 unlocker?
Click to expand...
Click to collapse
Yes, i try from SD and nothing stuck on loading... from windows with RUU nothing 0% stuck and then UPDATE ERROR[262] now i don't know to do
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
drewcam888 said:
2.4 doesnt use sd and it is run from a .exe. Make sure you aren't trying 2.47. Are you sure you tried this?
Click to expand...
Click to collapse
Ok, but how run from windows? If i cant connect via activesyncs the phone is on SPL mode i cant out of that and the msdos windows say "No device conected" when press enter from windows i cant unlock. Any idea? I'll try 2.47 but how run from windows with the phone en SPL Mode?
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
drewcam888 said:
Please read. I said run 2.4 not 2.47. Put the phone in bootloader and it should say usb at the bottom. Then run 2.4 .exe unlocker. I think it should run without using activesync. And by spl mode do you mean the phone is in the bootloader.
Click to expand...
Click to collapse
Look i cant run Hard-SPL-MFG (Olipro 2.40 Unlocker) because when i run the Bat Or MSDOS Windows say "No device connect" question me if i want retray copy the file.
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
drewcam888 said:
Ok so i guess it needs activesync. About your only option is to install a pregps rom so the phone will boot and then you can reflash the custom rom. Below is a pregps Verizon rom and radio that will work for 1.06 bootloader. Called rom 2.09.
http://forum.ppcgeeks.com/showpost.php?p=834294&postcount=4
Click to expand...
Click to collapse
No luck, method A SD Card Loading.. then cheking... then show a number corner 00028002 and say down Not allowed.
Method B, via PC and RUU then ERROR INVALID VENDOR ID.
Any idea? Thanks bro.
I think my phone is bricked... noway load the rom... i've tried load bootloader unlocked via SD last option and nothing!! damn this is so
Edit: Update: OS is working fine but unable to flash radio. Getting stuck at 0% when attempting via USB. SD card method not working - no error messages at all, in bootloader mode. However, SD card is detected fine in the OS and works properly.
Hey all.
It all started off when I tried flashing an OS ROM on my i-mate JASJAM, but it wouldn't work. Kept getting the infamous Error 260. I'm on Vista 32, so I downgraded the drivers as mentioned in the wiki/forums but it still wouldn't work. So I tried flashing it in VMware with XP SP3 but still kept getting the error. Changed the cables and ports too. Tried with about 3 different ROMS (AT&T stripped, official i-mate, other ROMs on forum). Finally, I used a newer RUU as included in the latest HardSPL and it started to flash - but failed after 1% !
I tried re-flashing an OS ROM but I'm just not able to connect due to Error 260. So I resorted to the SD card method, but the process doesn't even start. It's a brand new 1Gig card, tried formating both as FAT16 and 32 and followed all instructions, but it's like the card isn't even being detected.
So, any ideas guys? I would really appreciate if you could help me, as this is my only phone. ( I was mugged a few days ago - had to surrender my old phone )
Current stats are:
IPL-1.04
SPL-2.10.Olipro
PS: The first thing I did was flash to SPL-2.10.Olipro and after many tries, it finally worked. I was even able to boot the OS and everything worked fine.
The error 260 came up on a thread a few weeks ago here : http://forum.xda-developers.com/showthread.php?t=520226 the person with the problem in the end managed to fix it and flashed a new rom, it might be a good idea to read over this thread and see if you can find any other ideas to help you.
Good luck
Thanks for the quick reply!
I'm not sure though how he managed to fix the problem - it looks like he managed to flash the HardSPL and was able to upgrade the OS ROM after it. I'm already at that stage, only thing is, I still get the Error 260 and the SD card method not working.
Um, for some reason I simply tried the AT&T RUU via USB and it started flashing! The RUU wasn't able to query my OS version, and I chose the force Safe SSPL option. It's now flashing!
Still no idea why the SD card didn't work
Edit: Flashing successful! OS is loading now! Thanks a lot Scotty93
Now to try updating the radio.. *fingers crossed*
im glad to see that youve managed to get it to work, if you can get the sd card method to work it is best as it can stop your hermes from bricking which is a problem if a radio flash goes wrong.
Good luck
Well, it happened. Bricked again. I *had* to flash the radio because I was getting a "No GSM" message on the screen. (Was getting it earlier too)
Tried updating via USB (SD card method not working again).
The progress screen showed up on the phone, but it was stuck at 0%. After 5 mins I got an Error 262 message from the RUU. It had a built-in recovery feature, but it didn't work (gets stuck again at 0% and same thing repeats).
Tried these radios so far:
1.56.70.11
1.48.00.10
1.46.00.11
So, any ideas guys?
Update: Tried flashing the i-mate SHIP rom. Process starts, but gets stuck at 13%. Error 262 in the RUU.
I've just checked this thread and my situation is quite similar to that. I however, haven't attempted to downgrade my SPL yet, to access the rtask command. Is that necessary?
I'm able to use the info 7 command in mtty (VMware), but it throws up nothing new.
At the moment I've switched back to the AT&T OS and it's booting fine, but still no gsm.
Is it worth trying any other ship/radio ROMs? Or can I do something via mtty?
What size sd card you using, It has to be 2Gb or less. Also must be formatted FAT32.
If the radio rom has been corrupted, and it looks like it might be, there is no real way to fix. Some people get lucky by reflashing their SHIPPED STOCK ROM or their SHIPPED RADIO ROM. Most other fixes I've heard of don't work, or if they do, not for long....
Good Luck...
Cheers...
It's a brand new 1GB card, formatted as FAT32, 512kb block size. The WM OS is reading it properly.
I'll try and flash a shipped radio one of these days. Thanks for your input.
Disregard...
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Your phone's cdma. This is a gsm forum. I'm assuming that you're trying to brick your phone with the gsm hard spl and not trying to flash the proper hard spl. Stop doing that, your phone is getting pissed at you. Go to ppcgeeks or the cdma (Herman, not Raphael) forum here.
haha leave it to me to find the wrong way to do something. I appreciate your heads up Ted!
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Try here: CDMA Herman
same issue on GSM phone
Hi I have the same problem on a GSM phone.
I get the updating bar on my phone- it stays stuck at 0%.
then a communications error
Thanks in Advance
What is the problem with the RUU update?
I have searched for a solution to the RUU update/upgrade problem; none so far. Apparently, it is a major issue. I am interested in upgrading my Windows CE on my Xperia 6.1 to 6.5. I must have tried over a dozen times. The update process stops at 0% and Error [262] is reported. What can we do to resolve this? Is it compatibility or scalability issue? is it a problem with the software? The fact that it is working for some . . . and not for others is a source of concern about the stability of the software and this has potential implications; or it may well have to do with the hardware limitations of the PDA. Any ideas of a workaround?
You might try the Experia forum. You also might want to try Experia Roms.
I used to experience this issue as well. I simply go into communications and hit the USB to PC connection. Then remove the advanced functionality check. This has resolved many of the communication errors when playing with ROMS. This has been true with both GSM and CDMA devices.
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Dunno if i can link to another forum. If not, appolgize and Admins remove the link than please.
For the 262 error, look here:
http://www.4winmobile.com/forums/windows-mobile-faq/13329-ruu-errors.html
player911 said:
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Click to expand...
Click to collapse
Yes they are coming with a new bootloader. I just got my phone replaced from ATT and the new one came with 1.95 version while originals were 1.90. There is no HARD-SPL out for 1.95.
The way to do it now is to flash an old original AT&T rom with the 1.90 bootloader (since it's original, it won't require HardSPL). Then go ahead and everything should work as described in this forum/wiki.
Interseting. Sounds like a winner. Next time he comes around I'll try this.
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
smicale said:
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
Click to expand...
Click to collapse
You should probably go to your ATT store and tell them you'd like to get the official Hard SPL update.
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
smicale said:
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
Click to expand...
Click to collapse
If u want to use not the official rom made for ur provider and phone, hardspl is the only way. Any custom rom needs hardspl. Otherwise ur phone will not accept the rom.
But look here http://forum.xda-developers.com/showthread.php?t=410150
and flash the stock 1.90 SPL first, then u are ready for hardspl.
Description how to do stock spl is in this thread. Its normally meant for going back to stock for repair, but it should also solve ur issue.
NOT SHURE BECAUSE IN THE CDMA SECTION, IS UR PHONE CDMA OR GSM. MY SOLUTIUON IS FOR GSM !!!!!!
U SHOULD CHANGE THE POSTING SECTION IF ITS GSM !!!!!
Try doing the HardSPL in a Windows XP machine (needs .NET Framework 2.0 and ActiveSync). Goodluck.
i had the same problem as you and i maybe have a solution for you
go to your usb settings and look if you have a check box saying something about advanced networking. if it is indeed checked uncheck it and your problem will be gone hopefully
i did it on my telus touch pro and i am now able to upgrade my phone to winmo 6.5