HELP:Error 270 when upgrading!!! - P3600 Software Upgrading

I have tried all stickied CID unlocker/Hark-SPL over the last 10 hours today and all ended up with:
Error [270] : Update Error
The image file is corrupted. Please check your Update Utility. (PDA Phone Rom Update Utility 3.1.3.2)
Bootloader info:
TRIN100
IPL-1.00
Trin100
SPL-3.03.0000
I got AUS Versions of HTC - WM6 3.00.707.18
Somebody please help me!!!
Thanks a lot!

During my research on the forum:
1. tried disabling the USB > PC on HTC
2. also tried disabling the USB connection in Activesync
3. tried it via normal activesync connection method running RUU
4. also tried bootloader method running RUU
No matter what I do, I just keep on getting this stupid error 270!!!! Also had some error 260 on the way, saw lotsa post regarding that and got it fix! BUT just this error 270! I don't know what to do now!
HELPPPPPP!!!

jackkkkk said:
During my research on the forum:
1. tried disabling the USB > PC on HTC
2. also tried disabling the USB connection in Activesync
3. tried it via normal activesync connection method running RUU
4. also tried bootloader method running RUU
No matter what I do, I just keep on getting this stupid error 270!!!! Also had some error 260 on the way, saw lotsa post regarding that and got it fix! BUT just this error 270! I don't know what to do now!
HELPPPPPP!!!
Click to expand...
Click to collapse
Ran into that error myself but with s1rl4ncel0t's help managed to do it.
Try not putting your device in bootloader but launch the updater with your device set up normally, connected to/through ActiveSync. This was my mistake, I had the same error but tried updating with the device already in bootloader.

Try this
http://forum.xda-developers.com/showthread.php?t=296722
I have the same problem
it's run fine for me...

Related

cant install rom update code 260

hi im trying to update my rom with the new one that just came out that will enable my gps on my p3600 but i cant seem to be able to
i have folowed the instructions but when i get to the updating part that you have to wait 10 minutes my activesync turns off completly and gives me error code 260 check your connections, reset your computer, reset device and try again
i have done that many and plenty of times and it does the same over and over again i thought it was my activesync so i downloaded the 4.5 version but it still does the same any help please
can i update my rom with the one from htc some other way?
or im just out of luck?
After sendind this error don´t connet phone via cable.
Exit updating pragram.
Start update again and it´s all right.

Blocked on the bootloader screen : Connection error

Hi,
I try since 3 days to update my rom with the file from HTC e-club (RUU_Trinity_HTC_FRA_1.23.406.2_103_6275_1.38.00.11_108_Ship.exe) but when I execute the file there is the bootloader (tricolor) screen with the SPL version 1.06 and nothing until there is an 'connextion error 260' on my PC screen.
I don't know how to do please help !
thanks
using vista or xp?
stevaz said:
Hi,
I try since 3 days to update my rom with the file from HTC e-club (RUU_Trinity_HTC_FRA_1.23.406.2_103_6275_1.38.00.11_108_Ship.exe) but when I execute the file there is the bootloader (tricolor) screen with the SPL version 1.06 and nothing until there is an 'connextion error 260' on my PC screen.
I don't know how to do please help !
thanks
Click to expand...
Click to collapse
try this: http://vimafeje.com/splxploit-windows.zip
I'm using XP !
racerx_ said:
using vista or xp?
Click to expand...
Click to collapse
vimafeje said:
try this: http://vimafeje.com/splxploit-windows.zip
Click to expand...
Click to collapse
I tried it but I have :
=== Trinity splxploit by pof - pof[at]eslack[.]org
=== Exploits stack overflow on HTC Trinity SPL
[] SPL file: TRIN_HardSPL.nb
\\.\\WCEUSBSH001: No such file or directory
cannot connect to \\.\\WCEUSBSH001
My ActivSync USB connection is disabled just like they ask!
hmmm... i'm not too sure about this one.. have you tried just flashing hard-spl or something while you're in bootloader screen?
also, sometimes it takes trying more than once to get splxploit to do its thing.. Is there a message with the 260 error? i can't remember which one the 260 is
I tried to install the HardSPL but still the same error : ERROR 260 : CONNECTION ERROR !!!
My usb cable is conected
racerx_ said:
hmmm... i'm not too sure about this one.. have you tried just flashing hard-spl or something while you're in bootloader screen?
also, sometimes it takes trying more than once to get splxploit to do its thing.. Is there a message with the 260 error? i can't remember which one the 260 is
Click to expand...
Click to collapse
stevaz said:
Hi,
I try since 3 days to update my rom with the file from HTC e-club (RUU_Trinity_HTC_FRA_1.23.406.2_103_6275_1.38.00.11_108_Ship.exe) but when I execute the file there is the bootloader (tricolor) screen with the SPL version 1.06 and nothing until there is an 'connextion error 260' on my PC screen.
I don't know how to do please help !
thanks
Click to expand...
Click to collapse
When there is the "connection error 260" close the upload application and try to relaunch the installing file without deconnecting your usb cable from your ppc.
Besides, in the bottom of the bootloader screen (the white part), it must be written "USB", not "Serial".
It's it was just my ActivSync driver ! I have update it and now it's working.
Thank you for your answers !
First off...what version of active sync did you update to? Second....what if the white part of my bootloader screen doesn't say "usb" or "serial"?
I have had the same issue and for some reason only Ro update issue 3.14.4.1 seems to be able to connect to my phone too...
Expolit no longer sees my phone after upgrading to Mary Rom 1.2,
Some one else on here may be able to assist with these details...
I am using vista but my xp machine is the same too
stevaz said:
I tried it but I have :
=== Trinity splxploit by pof - pof[at]eslack[.]org
=== Exploits stack overflow on HTC Trinity SPL
[] SPL file: TRIN_HardSPL.nb
\\.\\WCEUSBSH001: No such file or directory
cannot connect to \\.\\WCEUSBSH001
My ActivSync USB connection is disabled just like they ask!
Click to expand...
Click to collapse
There's a slight syntax error in the prog. Just edit the unbrick.bat file, and replace \\.\\WCEUSBSH001 at the end by \\.\WCEUSBSH001 (one less '\'). Did it today after experiencing exactly what you did, worked perfectly, now running just fine with new loader, new radio, new ROM
1) manually start in bootloader mode
2) disable USB in activeSync
3) check 'usb' appears at the bottom of the tricolor screen and that he device is recognized by XP. If not, try unplugging/repluging
4) run the corrected unbrick.bat
5) while still in (new) tricolor screen after loader update, upload a new ROM (might have to reactive USB in activesync, don't remember)
It worked just fine for me, after quite a scary day when I couldn't get anything from my device but 'connexion' errors or 'corrupted image' errors
Cheer up, everything's gonna be fine
M
christopaaron said:
First off...what version of active sync did you update to? Second....what if the white part of my bootloader screen doesn't say "usb" or "serial"?
Click to expand...
Click to collapse
Yes - no good asking the question - getting help and then not providing the final answer
Tell all - so that ALL can learn from your experience!
Hi.
I've got windows Vista, and i have the same problem. How can i solve my problem?
I already downloaded all the updated software...
Bootloader reads "Serial" and not "USB"
I am using Kamba_a 6.2 EN, and I can not flash at all my trinity. When it goes to the bootloader, reads "Serial" and then freezes. I've tried to flash the bootloader also, but always get at the end a "CONNECTION ERROR". What should I do?
rafaelegomezb said:
I am using Kamba_a 6.2 EN, and I can not flash at all my trinity. When it goes to the bootloader, reads "Serial" and then freezes. I've tried to flash the bootloader also, but always get at the end a "CONNECTION ERROR". What should I do?
Click to expand...
Click to collapse
If you have HardSPL (Olipro 1.20, Olipro 1.30 or Des' Crash Proof) installed, check this and this.
First of all, thanks for your attention. I've been going through all the related links starting from those you sent. The CID on my trinity is HTC__001, and I can't find any cooked ROM with such CID so I can flash from the miniSD. By the other hand, the white strip of my bootloader reads "Serial". Is there any way I can change that to "USB". Otherwise, all the other ROMs I'm trying are giving me the same 206 communication error.
To whom it might be useful: My bootloader was giving me only Serial connection, and I couldn't make any flash. It ended up being the USB Cable!!! The bad one let me sync, upload/download files, everything exept flashing.
rafaelegomezb said:
First of all, thanks for your attention. I've been going through all the related links starting from those you sent. The CID on my trinity is HTC__001, and I can't find any cooked ROM with such CID so I can flash from the miniSD. By the other hand, the white strip of my bootloader reads "Serial". Is there any way I can change that to "USB". Otherwise, all the other ROMs I'm trying are giving me the same 206 communication error.
Click to expand...
Click to collapse
rafaelegomezb said:
To whom it might be useful: My bootloader was giving me only Serial connection, and I couldn't make any flash. It ended up being the USB Cable!!! The bad one let me sync, upload/download files, everything exept flashing.
Click to expand...
Click to collapse
Every WWE ROM available here is HTC_001 CID. So you can flash any WWE ROM with the RUU or by SD.
As for the Serial issue, connect the Device to the PC with the USB cable an it will change to USB.
Be shure to read the Bible first!!!
htc not working
i tried to run splxploit-windows on windows vista, but there is a problem:
[]Spl file: TRIN_HardSPL.nb
\\.\WCEUSBSH001: no such file or directory
cannot connect to \\.\WCEUSBSH001
in my trinity in the red rectangle shows in white letters:
TRIN100
IPL-0.50
then in yellow letters:
Trin100
SPL-1.07.0000
The green and blue rectangles show nothing and the white shows USB.
how can i fix this
help plz...

[TUT] Dummies guide: recovering from RUU errors

Flashing roms doesn't always work out perfectly. So what do we do when we get an error during the Rom Update Utility (RUU) update process? Read this!
I have searched several times for explanations of error codes. I finally came across something quite useful. I couldn't find it anywhere in the Blackstone forums nor on the Wiki so I thought I would share it. This is a copy/paste from a thread I found by debonairone and modified slightly.
Here is a list of error codes and possible resolutions when attempting to flash a rom with the RUU:
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the phone is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDOR ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade. This can also be caused by a mismatch between the CID of the rom you trying to flash and your device.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [248~259] : UPDATE ERROR
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically only happens when you try to flash a new SPL to your device.
Solution: Use Soft-SPL before attempting the RUU again.
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [264, 274] : CONNECTION
ERROR [302~318] : UPDATE ERROR
ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Reserved for future use.
You know there's a wiki page for this
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Dave
DaveShaw said:
You know there's a wiki page for this
http://wiki.xda-developers.com/index.php?pagename=RUU_Errors
Dave
Click to expand...
Click to collapse
Damn it! I couldn't find it... LOL! Can you delete this thread then?
Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks
HDuser said:
Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks
Click to expand...
Click to collapse
If that was directed to me, sure I can compare them and make this thread a solid combination of both. But I cannot update the wiki, that I know of at least
cRaCKwHoRe said:
If that was directed to me, sure I can compare them and make this thread a solid combination of both. But I cannot update the wiki, that I know of at least
Click to expand...
Click to collapse
Anyone can change the wiki, just click the "Edit" button at the bottom of the page.
Dave
Wow I feel dumb. I'll take care of it then
Where is the problem ?
sorry wrong threat
HDuser said:
Would you be kind enough to check your and the wiki content and eidt wiki, i will then link it to our home page and trash this thread.
Thanks
Click to expand...
Click to collapse
I updated the wiki. You can trash this. Thanks!
Excellent addition mate to this site. Very informative
Crack can I ask a question? Finally took the plunge and had a go at flashing new rom. got stuck at the first hurdle, Got hit with an "error 262". Not sure if I follow the solution though as I took battery out as it suggested in the RUU and restarted. Same result, even tried the USB driver thingy but it gives me errors when I update the driver. Shows USB on the phone though.
marmin said:
Crack can I ask a question? Finally took the plunge and had a go at flashing new rom. got stuck at the first hurdle, Got hit with an "error 262". Not sure if I follow the solution though as I took battery out as it suggested in the RUU and restarted. Same result, even tried the USB driver thingy but it gives me errors when I update the driver. Shows USB on the phone though.
Click to expand...
Click to collapse
So did you have an issue flashing the actual ROM or the SPL? What SPL do you currently show in your bootloader? How were you trying to flash the ROM?
cRaCKwHoRe said:
I updated the wiki. You can trash this. Thanks!
Click to expand...
Click to collapse
Rmeoved sticky and will let this thread just move down the line.
Thanks for your Input (as always).
I got the same problem...
Error [262]
i just followed the recoffery of the RUU and after i pulled out batery and i whent back to my normaal device start-up it was recofered according to RUU.
but i still had the same error after i tryed updating again my ROM.
my SPL on my Bootlouder = 1.14.0000
i was flashing my ROM with ur Dummies guide and i whent for the HSPL flashing.
ive done the "Drivers updating HTC USB Sync " before with succes.
plz help me
i got the same problem error (262) when im trying to update my SPL to 1.54, that was started the 0% screen and just hold on that screen...
anyone can help me?
javahuan said:
i got the same problem error (262) when im trying to update my SPL to 1.54, that was started the 0% screen and just hold on that screen...
anyone can help me?
Click to expand...
Click to collapse
Used this tips,,, goodluck
Troubleshooting - manual SSPL
Boot up your phone.
Copy SSPL-Manual-TouchHD.exe to your phone. In a file browser on your phone browse to where you copied SSPL-Manual-TouchHD.exe and run it.
Your phone will reboot into its bootloader and should show SPL v 1.07.OliNex.
When it shows USB at the bottom then run HSPLWrapper_blackstone_156OilNex.exe from your computer again.
Go to step HSPL3 if successful.
Error message [270]
I'm getting this error message which says its a corrupt image, check utility and try again.. I can't find anything about this on the forum. Does anyone know anything about this?
markzladz said:
I'm getting this error message which says its a corrupt image, check utility and try again.. I can't find anything about this on the forum. Does anyone know anything about this?
Click to expand...
Click to collapse
ERROR 270 (Update Error - The image file is corrupted):
Your device is still CID locked while trying to flash a cooked/custom ROM. Flash the USPL or Hard SPL if you have not already done so! If you were using the temporary USPL (white screen) method when you encountered this, you have to wait for the screen to go completely white before flashing a ROM (reset and try again if the screen did not go white).
Click to expand...
Click to collapse
You need to first install hspl or uspl. Read the Dummies Guide to Flashing (link in my signature)
ClydeB1 said:
You need to first install hspl or uspl. Read the Dummies Guide to Flashing (link in my signature)
Click to expand...
Click to collapse
Thanks, will try that and see if it works. The problem at the moment is when I'm flashing the ROM after I've installed USPL it goes to about 100% before failing and giving me that error message.

Problems flashing Touch HD

Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell
I had same problem.
Change usb cable, change usb port you are using and make sure antiviruse turned off.
rgtuit said:
Hi all,
Im trying to flash my SPL by following the sticky guide in order to install the Windows Mobile 6.5 and Manilla 2.5 ROM by Miri. I connected the device to my laptop, got an ActiveSync connection, started in Bootloader, waited for the USB sign and ran the application but the loading bar gets stuck on 0% before giving an Error. I then went to troubleshooting and tried the manual SPL flash but when it restarts in the new bootloader, I don't get the USB text at the bottom. If I try running the program, I get Error 260: Connection. Sorry if this has already been covered in a previous post, I did try searching the forum but didn't really know where to look.
Russell
Click to expand...
Click to collapse
You're using sticky guide yet you created a new thread instead of posting in sticky....why? no need for this
Thread closed
p.s. for your info
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.
If this doesn't work, try resetting your device, put it in bootloader and then connect it to usb cable

Cannot get the spl changed!!! Help

I have followed all the instructions on this website!! I have microsoft Vista and I installed the appropriate drivers on my phone to change the USB and everytime I try run USPL GUI v 2.5 I get a message saying Error accessing device. The phone is in bootloader mode as well while I do this and I tried to do the SSPL MAnual Touch HD on my phone and got error messages as well.....what am I doing wrong! Im stumped
Surely this phone is out of Warranty
hd2person said:
I have followed all the instructions on this website!! I have microsoft Vista and I installed the appropriate drivers on my phone to change the USB and everytime I try run USPL GUI v 2.5 I get a message saying Error accessing device. The phone is in bootloader mode as well while I do this and I tried to do the SSPL MAnual Touch HD on my phone and got error messages as well.....what am I doing wrong! Im stumped
Click to expand...
Click to collapse
You're out of warranty right?
So why not just use HardSPL?
Regards,
Tigermoto.
Same problem with Vista and Seven, even with the drivers that should work.
My solution is using an old backup notebook with XP.
Please post further queries/responses regarding flashing, USPL & HSPL here. No need for another thread
Thread closed

Categories

Resources