I tried to install the faria wm6 update with the shelltool. everything was going as per the directions, about 3 or 5 mins in the install process(which says takes 15 mins) it stopped and it gave me an error on the phone saying something about the reprog.exe or someting... anyways, the computer said done and to reboot... so I did and now it goes as far as the white TMOBILE screen with the following 4 lines of code
IPL 2.26.0001
SPL 2.26.0001
GSM 02.25.11
OS 2.18.0.0
and it freezes there... it wont turn off either.
Tries removing the battery and reinserting it. Well the same thing happens upon powering on the device. Tried hitting the little hard reset button on the side with the stylus... the screen flashes off and then it attempts to reboot again and the phone freezes at the same spot. Please help. I did everything according to the directions. PLEASE TELL ME I DIDNT BRICK MY PHONE. :'(
This was answered over in the WM6 forum.
But read this:
http://forum.xda-developers.com/showthread.php?t=298613
thanks.. the reboot with the camera button worked.. then I flashed the original rom back... now time to try again. thanks
Hi,
Sorry if this is the wrong place to post this but i could not find an answer for this in this section or general section -- The problem is this i upgraded to wm6 from wm2003 and everything was fine then it started it freeze ocationally so i thought i'd give it a hard reset as ther was no where in the tutorial that said that after flashing you could not hard reset now the phone is stuck on the O2 screen where the IPL & SPL are displayed
IPL=1.00 &
SPL=1.01.0109 &
GSM=0.3.28.60
I know the IPL/SPL were at 2.61 before that
Can anyone tell me how to get out of this or is the phone now bricked?
Yes, you cant hard reset because the htccoldboot.dll is not there, its not brick, you got the right SPL, just reflash again, refer to my guide on my siggy
Thanks
great that worked out fine gave me a scare - now it's all back up and runnung apart from the camera
For those stuck with this same problem, please re-flash starting from step 7 of karhoe's instructions to upgrade to WM6.
After installing a few applications and having to reboot, my SMT5600 would not connect via ActiveSync, nor show any network carrier and none of the menu keys worked (Start & Contacts). While troubleshooting I browsed to a forum suggesting I try a hard reset.
Never got a proper hard reset and ended up stuck at the initial screen showing the IPL / SPL / HIVE and Partition info.
Followed karhoe's step 7, with phone turned off, held camera button down and plugged in USB cable. Followed remaining instructions.
Note: the "type 'l c:/os.bin' " step is done in the mtty.exe screen that pops up (and not on your PC's command prompt ).
Thanks karhoe,
Good luck to everyone,
Jawad
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
I don't know if the phone is bricked or what. Was in the store tonight, tried to text message my wife who I couldn't find and the phone was all locked up.
Soft reset, and only the date/time loaded, nothing would run. Soft reset again, and the phone didn't load past the bright splash screen. Tried soft reseting a bunch more times, nada. Did a hard reset, first one didn't work. I think it was the 3rd hard reset that took. Phone seemed like it was back to basic WM5, would be okay. Went home, put it on the charger.
Went to take it off the charger to reload data, and it won't turn on. Soft reset, freezes at bright splash screen. Hard reset, same thing.
Is my phone bricked? Anything that I can do to revive it? Or am I SOL?
Cingy/ATT 8525 w/WM5
(By "bright splash screen" I mean when the splash screen flashes brightly. It increases brightness, but just stays that way.)
Any help greatly appreciated.
I managed to load the official WM6 ROM (spl 2.03) via the built-in bootloader. I have radio, ROM, and GSM. It boots through the ATT animation, then freezes. It leaves a black screen with a blue and green static bar running horizontally across the screen about 1/4" thick.
I don't know how to get Hard-SPL loaded on the device because the only way I can see the device is when it's in the built-in bootloader mode.
will attempt PB/KITL I guess, though I can't at this point get the phone to display the KITL info.
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
viatorx said:
No KITL in the ATT WM6 ROM.
Managed to get ATT WM6 ROM through the setup, after the "customization (bloatware)" it reset, and now it sticks on the bootup animation.
So close, I have SSPL and Hard SPL on the micro SD, if only I could get to the damn file manager. If I could somehow cancel out the customization process grrr.
On power charger, I seem to be able to get through the setup after a hard reset okay. It just won't boot after the reset.
Any ideas. I gotta get a few hours sleep. Sorry if this dialog to myself is in the wrong area, I didn't notice the "bricked hermes" thread was in the upgrades, etc area.
Click to expand...
Click to collapse
Not sure I fully grasp what's happening here, but if you want to stop the customisation then hard reset and when it goes to the loading cusimisation stage shove the stylus in the hole to do a soft reset and it will stop it loading.
Mike
Alright, thanks, will give that a try.
I managed to run the official ATT WM6 ROM and flash it without a hiccup (twice), and task 28 in bootloader says no bad blocks. So I am confused how I can flash an "official" ROM successfully and the device still won't work. Am starting to suspect hardware failure apart from memory.
Thanks a million mate, that worked. Phone boots now, already have SSPL installed. Need to update .net and activesync for Hard-SPL 7 to run I guess. Then I have more options.
Woot! I unbricked my phone
Once I was able to hard reset and cancel the "customization" I ran SSPL, then Hard-SPL 7, then I Super-CIDed the device.
I haven't tweaked the data settings yet, but I can send/receive phone calls. Which is a coup, because this is my main line.
It runs sluggishly. I don't know if that is the ROM or the device. It won't boot if it's plugged into USB, and after flashing Hard-SPL it isn't a recognized device by windows, won't connect to activesync.
I am treating the phone gingerly right now, will try and unload the ATT wap settings cab and restore my pim.
At least now I have the option to install another ROM if it bricks on me again.
I really should have flashed Hard-SPL the DAY, the MINUTE after the warranty was up. Lesson learned.
Or not.
ATT ROM locked up on me, decided to try Schaps 4.40. Won't load past WinMo "tap screen to setup" screen. Guess I'll try something else.
For a stable WM6 rom try TNT SE. It is REALLY stable but does come with some 3rd party apps. Thought you might like to get it working though first then try the other roms and in my experiance I haven't found many other roms that were THIS stable...
Hope you get it working...
For a disassembly guide try this site - http://michael-channon.spaces.live.com/PersonalSpace.aspx?_c02_owner=1
Its a bloody good place to go for all things to do with hardware and Mike is a true guru with hardware problems...
Cheers...