Artemis USPL v.01 upgrade error with 270 code, Please HEPL

[lenocs]

Hi Profs,

there are some problems with a Artemis Update SPL (USPL) v.01. I've found this problem is several topic but there was no solution for it.

#1:
http://forum.xda-developers.com/showpost.php?p=1739577&postcount=413

#2:
http://forum.xda-developers.com/show...44#post1745844

#3
http://forum.xda-developers.com/showpost.php?p=1713596&postcount=1

The problem:
use USPL to get rid of the CID....count goes up to 100% screen shows black with green text, then pops to white. I need to do a soft reset to get it running again.

Then i use ROM Update Utility to update my p3300....and it still keeps hanging on 3%....damn. i get mad...!! Have read almost all here online...no virusscanner, no firewall....I use win XP.

i even tried without memory card and phone card....and nothing seems to work.......

ipl 1.14.0001
spl 1.14.0000
gsm 02.07.90
os 1.14.0.0

Who has any clue...?

With other words:
I've just got back my P3300 from repair, they changed the main board. With the previous main board I was able to upgrade the device and I was using the B&B versions.
But with this new board I'm not able to upgade the SPL. When I try to upgade the device after and start the start_uspl .exe the 10...20... ....100 my device become an interresting "blue screen" status and only the reset help to get out from this status. If I start the RomUpdateUtility.exe after the upgrade I got the error message #270

IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
ExtROM version: 3.12.405.102

This is not the solution for the problem. I've tried it:
Plug in USB cable. Hold voice recorder button and press reset button. Bootloader will appear (Three color stripes). Then you may flash up ROM. (This works only for RUU installation types, not for PDAmobiz modified installator) Original english HTC P3300 ROM you may download form here: http://wiki.xda-developers.com/index...temis_Upgrades ....


Please help us to solve this problem....

[lenocs]

This should be the same:

Hello POF,

I was directed to this link by Rudegar because I want to change the french ROM to English ROM.

The relevant data of my PDA is:

The version of the ROM: 1.14.406.1 FRE
Date of ROM: 9/27/06
Radio version: 02.67.90
Protocol version: 4.1.13.28
ROM extension version: 1.14.406.101


I tried exactly the way you described in the USPL_manual and everything went well till I got to a stage where I was asked to click the update button which I did. After then there was a window which showed "updating from current version to version 9.99". I was confused at this point but clicked "continue" and after this stage I got an error message and there was no longer a connection bw my PDA and my computer.

Thanks,

Jonat
Reply With Quote


http://forum.xda-developers.com/showpost.php?p=1784337&postcount=430

[lenocs]

Problem "lost connection PDA-PC"

Hi,
first I would like to thank you for goooood job to many people here !
Back to my problem. I have HTC Artemis (T-Mobile MDA Compact III), OS WM6 T-Mobile Czech version.
I ran start_uspl.exe on my computer. The part in DOS based screen seems to finish everytime OK, but finally the connection with PC is lost. Therefore when the PDA Phone ROM Update Utility starts cheking version the error "lost connection with PC" appears . PDA stay in "black screen" mode and only hard reset start it again as usual.
Does anybody have the same problem? Any idea, how to solve it ?
Thanks

http://forum.xda-developers.com/showpost.php?p=1773030&postcount=426

[Anthony2oo5]

When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me ;)

[lenocs]

Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....

[Anthony2oo5]

then pops to white. I need to do a soft reset to get it running again.

What im saying is when it pops to white, dont soft reset it, just start the upgrade.

[jahrami]

When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me ;)

that what i also do When the screen goes white, don't restart. Just start your RUU

[namco]

Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....

Same situation as above. Depending on the Artemis, the screen might go white or black. Just don't freak out and keep on flashing the USPL. It WILL work and then reboot. Then you can flash the actual ROM you want.

[merlot]

Hello from an absolut newbie trying his first upgrade,

And I have just experienced the same problem than lenocs.

I have run start_uspl.exe, but when the screen is suposed to become white or dark, it becomes dark and the artemis is in fact totally off and connection is lost.

Anyway I supossed that it was because the scrren got black and I tried to run the update utility, but I´ve got an error (the terminal is disconnected or similar) and nothing happens.

I have had to soft reset the terminal and fortunatelly it seems that I still have my previous ROM and it seems that it works. But, do you know if there could be some "side effect" because the first step of start_uspl script?

Anyway I would like to move to WM6, so, any suggestion would be really appreciated.

Thank's a lot

[SpiggyTopes]

When you restart, what is the USPL number?

[merlot]

Ooopppssss!

I didn't pay attention.

As I've said, I'm a newbie, so I was just woried because I thought I had "bricked" my new atemis.

How can I know now the USPL number?

Anyway I tried the star_uspl again (I'm a crazy newbie) and it failed. The artemis went off almost inmediately.

Thank you very much for your help



When you restart, what is the USPL number?

[libor.pavlik]

I think the problem is in SPL version 3.13 (or maybe anyone newer than 1.11).

Try different Artemis USPL - for me worked version from this page:
http://wiki.xda-developers.com/index.php?pagename=Artemis_DumpedRoms

It's very confusional, because file sizes and also dates are the same as in unfunctional version, but this one worked.

Hope it'll help you as it helped to me.

[Rocheau]

I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.

Just try.

[jahrami]

I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.

Just try.

do u have ur card in the phone while updating:confused:
you are suppose to remove the card :eek:

[PKS]

Hi,

i had the same problem error 270, 3% and lost connection with Activesync.

IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07

any way to upgrade was wrong ->> error 270

My good way was:
1. Downgrade to WM5 - original shipped ROM 1.12.405.1(link found on Wiki pages)
2. Under WM5 run USPL to unlock CID (now without any errors)
3. Final STEP - Upgrade to new ROM Artemis Touch 3.01 (without any errors by upgrade)

:-)))

Now my Artemis seems to be OK.

[TryOG]

I ran USPL with storage card inside the device...

no problem :)

[m-h-l]

Hi,

for me USPL did not work with my SDHC 8GB card but then I switched back to my previous 2GB SD card and then it works.
Perhaps the SDHC driver blocks USPL in some way.

Cheers,
Markus

[tetrapond]

i have been trying for 3 months :(

once i have upgraded my artemis to wm 6.0 everything seemed to be OK for two days... then the screen started to go black when i restart... şi downgraded to 5.0 but nothing changed... when i remove battery for a while, my arte works... when i try to do anything with it, the screen slowly goes black as if it is broken... please DO HELP ME! i am going to go mad... i have a new iphone, ihave i kaiser as well... but i miss my artemis very much...

[fsimal71]

Hello:
I have the same problem and realized hundereds have too. I have been checking in all forums and no asolution to it

The issue that happens to me is that I used USPL for upgrading to WM6 and worked, but now for the Touchflo it does not. Tried with all USB ports, tried with different computers and no good news.

The USPL msdos screen indicates that there is no connection at all in all percentage levels, then it bocomes dark and the 260 error whne installing the rom.

please help us soon !!!

we are in trouble!!

[mnemoth]

Anybody can help us on this point ?

The only way to solve it is to remove the batterie during 30 min., then put it back and pray...

Then, for no reason, the screen shut down, a few minutes or days after :(:(:(

I've upgrade from WM5 to WM6 with the original Rom of HTC, it seems a little more stable but it shut down every 2 days when i'm lucky

[romac]

Hello:
I have the same problem and realized hundereds have too. I have been checking in all forums and no asolution to it

The issue that happens to me is that I used USPL for upgrading to WM6 and worked, but now for the Touchflo it does not. Tried with all USB ports, tried with different computers and no good news.

The USPL msdos screen indicates that there is no connection at all in all percentage levels, then it bocomes dark and the 260 error whne installing the rom.

please help us soon !!!

we are in trouble!!

I too have experienced this problem. I still have found no reason for it, but I reset my device, ran USPL about 3 times and it eventually worked. Still do not know the cause.

[HarryRag]

i only get this error when i try to uspl with my 8Gig sdhc card in the p3300

when i put the 1gig card back in uspl works like it always did

[pelops]

Hi all,

I'm one of YOU, the troubled lot with the error messages. I have tried all possible combinations, I think, with my XDA Orbit (O2 UK) and have had no joy this far. Just to let you know I also have the problem of lost ActiveSync connection once USPL is used. Tried to press on with the ROM update but the Orbit and PC are having none of it; tried waiting for ActiveSync to hook up again and then proceed with ROM update but no luck; tried soft reseting after USPL but SPL version is back to 3.14.0000; also tried various PCs etc but to no avail; tried all possible combos with SIM and MicroSD card (in phone/out of phone) but again no luck.

I have been told to try flashing WM5 O2 ROM to the Orbit (even though it has a WM6 version on from O2) before I go to the home cooked ROMs. I am however, unable to access the ftp server here fro the file and had no luck finding it elsewhere. If anyone can help I'd be grateful.

[sapg]

I have an O2 XDA Orbit that already has WM6 on it but I would like to upgrade to the ROM with touchflo. I have tried using start_uspl.exe but it complains about not being able to spawn cmd.exe. I have tried copying cmd.exe to the same folder as start_uspl.exe but that makes no difference.

Does anyone know what I'm doing wrong?

Thanks.

[slk-A4]

Hi,
I also seem to have this problem of losing the connection while upgrading.

(Artemis Touch 4.02 WM61. WWE Rom):

When I try to update e.g. the Radio Rom, I get this message:

Error 260 (Update Error):
The Update Utility cannot connect to your PDA Phone......


The utility starts the red-green-blue screen (IPL 3.15.0001) and SPL 1.11.0000 and that's it, then this message pops up.

Does anybody know what to do????

This happens already when when I run USPL and , as I said, also when I try to upgrade the radio, or even when I try to

This is what I tried:
-remove the 8GB storage card: no effect
-put in the original 2GB storage card: no effect
-downloaded another version of the USPL tool: no effect
-used another usb port: no effect
-softresetted the device a few times: no effect

The usb keeps losing the connection while upgrading the USPL.

I think it has to do with my 8GB storage card. All upgrades I did before I had this card installed, went fine.

Does anyone know a solution??

Thanx

[galfar]

This problem is in windows vista. Download new modem driver for htc or flash in windows xp.

[icek]

I don't think problem is in vista, for me taking out the sdcard has resolved my "error 260" connection errors.:)

[davelond]

[Note: At this point it is possible for the process to return an 'Error 270', as noted in http://www.xdasite.com/index.php/topic,1695.0.html. This can be circumvented by a soft reset followed by hard reset followed by re-commencing USPL.]


Am going to give this a try

[davelond]

nooooo... unfortunatly no joy

[SuperEd]

Hi all, managed to get it work 3rd time lucky.

Basically, getting errors like you guys in that it'll just hang on the blank screen, hanged on the pengium screen, error messages....

My fix..
- Ran Cert_SPCS.cab first on MDAC3 and installed..
- Ran EnableRapi.cab and installed...
- Then ran start_uspl.exe

didn't have high hopes as was expecting a blank screen and another error, but this time, when the screen went blank, active sync disconnected and connected whilst running rom update utility. The flash was quick on the progress bar and actually worked. The trick I think is that when the MDA is at a blank screen is to get active sync to connect before running rom update.

Hope this helps some of you with issues like me.

[incredulous]

This is a totally uneducated guess, but I believe your problem lies with your current IPL version.... Although I have just got back from the pub so I could just be talking out of my arse :)

[incredulous]

I don't think problem is in vista, for me taking out the sdcard has resolved my "error 260" connection errors.:)

It IS vista, trust me.

I had similar problems with the USPL, downloaded the old AS drivers for WMDC and now its all fine, hunky dorey :)

[davelond]

I've just tried Artemis Update SPL (USPL) v.01 - Another way to flash *ANY* rom to your device! from http://forum.xda-developers.com/showthread.php?t=311403 but i'm still getting this damn 270 error.

does anyone knw if there is actually a solution for this?

[gertjan813]

This is very irritating, same problem here!! would be great if one of the cell nerds finaly come with a solution.

Problem: Starting USPL, before I installend enebleRapi and Cert_CPCS and also not installed before. Readed and tried lots of forem's. Still the 270 error!

Im running now the latest update of T-Mobile NL

Greetings,

Gertjan

[ranaonline]

This is very irritating, same problem here!! would be great if one of the cell nerds finaly come with a solution.

Problem: Starting USPL, before I installend enebleRapi and Cert_CPCS and also not installed before. Readed and tried lots of forem's. Still the 270 error!

Im running now the latest update of T-Mobile NL

Greetings,

Gertjan

I had the same problem with my HTC P3300. When I started the process, the start_uspl.exe would go straight from 70-100%. I was reading everywhere that this is one of the symptoms. Then the phone would get disconnected from the PC and the ROM Updater utility started. The ROM Updater utility specifically states that the phone should be connected to the PC via ActiveSync. I tried on 3 PCs and it was the same everywhere.
I use Vista Ultimate and Windows XP Pro SP2.
SOLUTION (worked for me on Windows XP)
1. After much trying, i did a soft reset, followed by a hard reset.
2. Connected the phone to the PC using ActiveSync 4.5
3. Disabled firewall, Antivirus
4. Copied Cert_SPCS.cab, EnableRapi.cab to the phone and installed them in device memory
5. Soft reset the device
6. Connect the phone to the PC again
7. Start start_uspl.exe
8. When the phone screen gets blank (mine was black) and the phone light may also be off, DO NOT WORRY. Continue with the ROM Updater utility. It will automatically wait for the connection and update your phone.

I was not sure if the ROM Updater will be able to work as the phone's light was off. I was able to get done with the process cos I had learnt about it here at XDA-Dev! I am only sharing my learning.

[dmro]

You have to downgrade the active sync driver AND flash the rom WITHOUT the mem card. Otherwise you will get the white screen wich (in my case) doesn't let you continue the upgrade!

[Falkenbat]

ok,guys,without any problems before i now got "error 200 Pls get newer update utility" everytime with all roms...
fixed it after a few hours by using the original o2 rom and the computer of my friend...
now i ve this nice original o2 rom...but i dont want it,so i tried to get artemis touch 4.02...i run uspl...and after 100% my artemis made a reboot with this nice o2rom started(but without any black or withe screens) and the update utility brought me this fucking "error 270 Image file is corrupted"...
now found this thread but didnt really see a solution for my problem...
oh,yes, i have my artemis now almost one year, in this year i changed my rom many many times without any problems... I ve and had Win XP with Active Sync all the time...sometimes i made it without ac, but with the bootloader and normal usb connection...
pls help me,i want to have the touch 4.02 back on my phone...

[USRFobiwan]

Ok i have successfully upgraded 4 phones using VISTA. 2 native HTC phones and 2 T-Mobile mdaII's.

Some misunderstandings out of the way first:
- Use a USB port directly on the pc (back or front. NOT via a USB hub or monitor usb Hub etc.
- If a USB port on the front or back of the pc does not connect during the USPL update, try switching ports and try again. Most modern PC's have two or more build in hardware usb hubs, mostly different brandings also.
- White (blank) or black screen has nothing to do with a sd/sim card inside the P3300. Its just the process of the USPL CID unlocking procedure.
- Better save then sorry and remove both sd and sim card from the phone. (the screen can be white or black without them)
- Also temporary disable the phone lock (numpad key code) because this can prevent active sync or non active sync lose connection.

- If you run Vista download the special 32 or 64 bit HTC USB driver.
- Once the USPL is successfully in unlocking your device, it should read SPL 1.11.0000. There is no need to run USPL again if you see this SPL when installing roms. if you see ANY OTHER version then you need to run USPL again BEFORE you do a new rom flash (be it Toms rom or whatever)


I have shared the important files for you all, you can find them here:
Vista 32Bit HTC USB driver (http://www.rcunderground.nl/bestanden/63_Vista%2032Bit%20mobile%20device%20driver.zip)
Vista 64Bit HTC USB driver (http://www.rcunderground.nl/bestanden/64_Vista%2064Bit%20mobile%20device%20driver.zip)

Artemis (P3300) USPL CID unlocker (http://www.rcunderground.nl/bestanden/65_Artemis_USPL.zip)


How do you install the Vista USB drivers:
- First thing to do, open the "mobile device center" and un-check the "enable USB connection" in the connection settings.
- Then connect your P3300 to the usb and go into boatloader mode (hold the voice recorder button and press reset, let go of the voice recorder when you see the red,green,blue screen appear on the P3300.
- Vista should recognize a device and install drivers for it. Let him...
- Open up devicemanager (hold Windows key and press Pause-break on your keyboard) and select Device manger from the left menu.
- You should see a "Mobile Devices" option in the list of devices. Open it and then you should see a "PocketPC USB Sync" device.
- right click on this device and select properties.
- Go to the driver tab and check the Date if the driver. (note it down)
- Select the update driver button.
- Select the lower option, "search on PC..."
- Select "I want to choose from list..."
- Select Browse for drivers and select the folder where one of the above drivers are unpacked (WceRndis for vista 32 and wceusvshx64 64bit for vista 64)
- There should be one device driver called "PocketPC USB Sync". Select this one and isntall the driver.
- Once installed right click the PocketPC USB sync device and go to properties, click the drivers tab and see if the driver date is different then the original date (for vista 32 version it is: 6-10-2004)

If you have done the above successfully , you can disconnect the USB cable and reset your P3300 and let it boot normal. Enable the "allow USB connection" in the windows mobile device center.



Next step Installing USPL:
- Remove the simcard and sd card from the P3300.
- Connect your P3300 to the pc again. Using normal active sync oprations.
- Make sure the device is connected in windows mobile device center.

- If you already have it, run "Start_uspl.exe" or download it from above.
- A dos box will open en it will start going from 0 to 100%
- Once complete the screen of your P3300 will go white or black. Mostly white. This is normal so don't panic!
- The update screen appears from the rom update utility But...
- Active sync will have a disabled connection. Do not worry!

- Check the device manger (hold windows key and press pause-break key on keyboard) select device manager from menu on left.
- If everything is correct you should see a "Mobile devices" option in the list of devices. If you see this you device is still connected but not using active sync.

- Now go to the update options of the rom update utility. Let it do his work.
- Finish!


Troubleshooting:
- If you reset the device if the screen goes black or white (out of panic or whatever) and you still go along with the rom utility update on the screen the update will error out with a 270.
- if the screen is white or black and you update and the rom utility cant connect, or runs into a 270 error, then the device is not showing in the device manager list. Reset the device and try again. Use different USBport if necessary.
- Be patient, READ this 40 times if you have to, just to make sure you doing things right. 90% of the troubles comes from not following the right steps...


Good luck!