Hello,
Well to explain my problem. I had the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID flashed onto my O2 XDA Neo. No problems, but sometimes I couldn't go back to desktop because "programms" didn't want to close. So I went to look for a dutch firmware. I found one and tried it. It didn't work, but my XDA Neo was already at 1% and didn't go further. So I pulled the cable out of the telephone. Now it doens't pass the red, green, blue screen when starting the phone. Hard reset doens't help eather. Wenn I connect it to the computer, activesync says "not connected".
On the screen it says:
RUU
IPL 2.15.0001
SPL 2.15.0001
Please help me out, because I really don't know what to do anymore
Encountered your case before while trying to downgrade with no success.
I suggest you try to turn back to dopod wwe rom and install it again before further attempts to brick your device.
Active sync tells it's not connected, that's normal because you connect a device which has no rom now.
You should see "USB" at the bottom of the screen once connecting to PC. Then start the rom update.
It will try to discover what's in your pda and will report you "nothing", which is logic. Click update and go. It should proceed...
Good luck.
g3k said:
Encountered your case before while trying to downgrade with no success.
I suggest you try to turn back to dopod wwe rom and install it again before further attempts to brick your device.
Active sync tells it's not connected, that's normal because you connect a device which has no rom now.
You should see "USB" at the bottom of the screen once connecting to PC. Then start the rom update.
It will try to discover what's in your pda and will report you "nothing", which is logic. Click update and go. It should proceed...
Good luck.
Click to expand...
Click to collapse
Thank you so much! I reflashed my old rom, and the device works fine again. But is it not possible to run an older rom? I would like to have the dutch version.
If your device is Sim unlocked, you may try the famous specific rom availIable at:
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=437&PN=1&TPN=1
This rom is for downgrading in a first step and cid unlocking in the second step exclusively and not for continous use . Once these two task are done, you can install any ROM you want.
Reminder: You can not install other language without CID unlocking.
g3k said:
Reminder: You can not install other language without CID unlocking.
Click to expand...
Click to collapse
It is not true. You can install any language ROM using NoVendorID patched reflashing utility.
Yes and no!
If the ROM to write is never "patched rom update utility" will bypass the CID check step and continue to install.
But it the new rom is older (ie 2.09 to write over 2.13) problems start there and you get an error in most cases. In that case we need to downgrade.
I've faced and practiced both cases.
Thanks for details...
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....
Probably the same problem
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
Also the same
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
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
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....
lenocs said:
then pops to white. I need to do a soft reset to get it running again.
Click to expand...
Click to collapse
What im saying is when it pops to white, dont soft reset it, just start the upgrade.
Anthony2oo5 said:
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Click to expand...
Click to collapse
that what i also do When the screen goes white, don't restart. Just start your RUU
lenocs said:
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....
Click to expand...
Click to collapse
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.
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
When you restart, what is the USPL number?
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
SpiggyTopes said:
When you restart, what is the USPL number?
Click to expand...
Click to collapse
solved ... at least for me
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.
Maybe this can help you
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.
Rocheau said:
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.
Click to expand...
Click to collapse
do u have ur card in the phone while updating
you are suppose to remove the card
Problem solved (for me)
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.
I ran USPL with storage card inside the device...
no problem
switch SD card back to 2GB or smaller before USPL
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
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...
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!!
Same Problem : Screen shut down
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
Hi I have an AT&T 8525 that I have flashed with Schap's WM6 pro 4.31 lite rom. I am trying to flash back to AT&T wm6 rom but every time I run the RUU it goes to the bootloader then the next screen is a white screen that says "loading..." so I wait to see if it loads slowly but it times out and returns to the bootloader screen. I have tried flashing from the SD card but it does the same thing. I have tried to soft reset then I tried to hard reset but I still get the same message. The utility goes to an error screen saying connection error. Is there anything that I can do to get this to work?
take out your sd card and run the RUU
THANK YOU!!! The fix worked perfectly. Outstanding!!!!!!
Hi, had a problem flashing my bro in law's Titan.
I unlocked the titan with the titan unlocker by Olipro and flashed with the round 4 reloaded (loaded) rom (dcd 3.2.6)
unlocked fine, installed the rom to 100% rebooted phone and its stuck on the Bell screen. (its after the HTC screen and after the screen that shows versions, which it does show D. version 3.2.6) any ideas how to get it to where i can flash it again?
Does it have a compatible v3.x radio installed as well? I recommend 3.42.40 personally, but just about any v3.x radio will work.
BTC
Tzetsin said:
Hi, had a problem flashing my bro in law's Titan.
I unlocked the titan with the titan unlocker by Olipro and flashed with the round 4 reloaded (loaded) rom (dcd 3.2.6)
unlocked fine, installed the rom to 100% rebooted phone and its stuck on the Bell screen. (its after the HTC screen and after the screen that shows versions, which it does show D. version 3.2.6) any ideas how to get it to where i can flash it again?
Click to expand...
Click to collapse
Ok, solved the problem by pressing the power button, camera button and reset button all at the same time. This of course enabled the bootloader on the phone. installed another rom which gave me the same result, stuck at carrier screen. This is of course because i didnt know i had to upgrade the radio first. Got the phone running again by updating the rom with the one at the HTC website for my carrier.
Now i'm trying to update the radio. there isnt alot of instruction out there, but i did find this http://wiki.xda-developers.com/index.php?pagename=Radio only upgrade instructions Although after following the instructions, the universal rom upgrade tool never connects to my phone. I tried the vista fix here http://forum.xda-developers.com/showthread.php?t=313001 But being that its over 2 years old, i'm guessing its now useless as when i try to update with the files there my OS says my drivers are more current and wont allow me to install them.
So now i'm stuck at the "how to upgrade my titan's radio" stage. Anyone have better instructions? (or can tell me what i'm doing wrong?
what i've done
downloaded radio version 3.42.40 as BTC suggested
downloaded "universalRUU" and extracted it to its own folder
copied the radio's file "TITAIMG.nbh" into the UniversalRUU folder
reset my phone into the bootloader screen
ran the ROMUpgradeUt.exe from the UniversalRUU folder
pressed "next"
it says "checking information on your device" and hangs there forever.
if i press update anyway, it continues to the last screen where i can press "finish" and thats it. nothing happens. which part am i missing? the phone is DEFINATLY connected to windows at that point, so it should be able to detect it, but it doesnt seem like it even tries as there is no system pausing or stuttering like it might be trying to do something.
thanks for the help so far.
Solved the problem on my own, as well as the other couple problems i ran into.
Updated the Titan WIKI to reflect my solutions and clarify some key points.
Hello,
I Flashed my P3600 starting from WM 5 with Trinity_Rom_NiAl_Build_23504.
It worked but not at all (pine nuts) so I decided to upgrade again.
The second one, the upgrade stopped while he was runnung and I did the recovery procedure as suggested by the upgrade.
Now when I connect in bootloader mode to pc USB connection is activated.
But every rom version i try to flash I got the Message Error[270] Update Error
Ur Image file is corrupted.
The bar % run till 1% and the device swich off immediatly.
In >Bootloader<
TRIN100
IPL-0.50
Trin100
SPL-1.06.0000
Please Help me.
Thank You
msmbrt said:
Hello,
I Flashed my P3600 starting from WM 5 with Trinity_Rom_NiAl_Build_23504.
It worked but not at all (pine nuts) so I decided to upgrade again.
The second one, the upgrade stopped while he was runnung and I did the recovery procedure as suggested by the upgrade.
Now when I connect in bootloader mode to pc USB connection is activated.
But every rom version i try to flash I got the Message Error[270] Update Error
Ur Image file is corrupted.
The bar % run till 1% and the device swich off immediatly.
In >Bootloader<
TRIN100
IPL-0.50
Trin100
SPL-1.06.0000
Please Help me.
Thank You
Click to expand...
Click to collapse
Error may appear due to corrupt image ROM. download the entire RUU and try again.
In General for archive with firmware.
I've already tried with another RUU but it works the same; really it means not to recognize the ROM installed because if I run the utility and click update to read the ROM just installed and the ROM to update, the utility recognizes only the new but not the present ROM.
The first time I ran it, the utility recognized the installed ROM too and it finished well.
msmbrt said:
I've already tried with another RUU but it works the same; really it means not to recognize the ROM installed because if I run the utility and click update to read the ROM just installed and the ROM to update, the utility recognizes only the new but not the present ROM.
The first time I ran it, the utility recognized the installed ROM too and it finished well.
Click to expand...
Click to collapse
Well.
In an active sinc disconnect connection on USB
- Download splxploit_HTC_Trinity
- Unpack and start
- Then stitch...
Should work