Related
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
stunno said:
It might be very simple to all you educated guys, but I am sure there are a few more like me that are a bit baffled by some of the threads on here.
What would be REALLY nice would be a 'simple' step-by-step guide to installing wm6 on our devices, and what we need to download to achieve it, eg "you need this for MDACIII, and this for O2 Orbit"
Obviously anyone trying it runs the risk of buggering up their phone, but that's their own fault.
Any volunteers?
Click to expand...
Click to collapse
having asked the same question myself here goes.
Download USPL and follow the instructions. they are very clear.
Download
extract
connect phone with minimum 50% battery
soft reset and once started up fully run the app by clicking on Rom Update utility
follow the process through once finished your device will restart.
once restarted you then can flash the rom of your choice
I used Black and Blue again ran the update utility and bingo.
dont forget that all data on your device will be lost so make sure you have back up of contacts etc in outlook on pc.
Finaly make sure you have Activesync 4.5
enjoy
AS STATED ALTHOUGH THIS WORKS YOU ALL DO IT AT YOUR OWN RISK
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
joey jojo said:
Id just like to know really is that how many people have done it without unlocking the device for o2 orbit uk. i have one and am not really willing to try it unless i know there are people out there that have tried it and it worked.
as there is no rom install file from o2 for this, there is no way bacj and bricked phone is the only way forward. id like not to brick my phone as i need it daily.
so, has anyone with a locked o2 device upgraded to WM6 successfully and which rom did you use if it worked.?
Click to expand...
Click to collapse
i have o2 uk orbit and all is well
pof said:
I created update package for this ROM in NBH format, so no risk of bricking when flashing it, just unzip & run RomUpgradeUtility.exe
Download here:
ARTE_WWE_WM6.zip
NOTE: Before flashing you need to have Artemis USPL on your device.
Click to expand...
Click to collapse
Taken from Bepe's thread about the modified o2 German update. Basically you need to use the Artemis USPL program and then use the first link to install which I did successfully on a CID locked phone.
Thanks guys, but, unfortunately, the uspl thing does not work on my pc
Along with a few others I get the 'black screen' on my mdac3 then activesync disconnects and the rom loader throws up an error
Luckily my mdac3 survives through a soft reset
I think the idiots guide is not quite there yet
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
crushuk said:
hi..
i have O2 uk orbit.. which is still locked, i fully charged the battery, completed a hard reset of the phone used the pof Artemis Update SPL (USPL) v.01 upgrade (wow what a brain box he is!) just in case it failed, so i could you use any NBH file to get you orbit to work again if i failed. Then used Bepe's WM6 os.nb file renamed it to windows.nb downloaded ATRE.zip unzipped the ARTE.zip file placed the windows.nb into the same directory, don't forget to edit UpgradeRom.bat file 0x3900000 to 0x3500000 with in the ATRE directory and copied and installed EnableRapi.cab to the phone. Reset it the phone and then started the UpgradeRom.bat! 12 mins later upgrade complete. Hard restart the phone.. Chewing nails by now... all went well did a soft reset of the phone before the O2 ExtROM autorun starts..
sorted, and did half way though a night shift at 3 am.. not bad at all!
Click to expand...
Click to collapse
Confused... is it really necessary to take all these steps? I thought that the only thing required is to run Pof's tool USPL, and after that run Romupdateutility.exe from the package in .nbh format (the link is just a few messages above yours). Please correct me when I'm wrong.
step by step guide
stunno said:
Any volunteers?
Click to expand...
Click to collapse
OK, I volunteered... This is a detailed list of steps how I installed a new ROM on my MDA Compact III (CID locked, at least I think so). It worked without any errors or problems. I used PDAVIET Black&Blue v2.0. It was my first flash on my Artemis, so I more than understand your need for step-by-step guide
1. download the file Artemis_USPL.zip
2. unpack into the folder c:\USPL
3. download the file ARTEMIS_Black_Blue_v2.zip
4. unpack into the folder c:\ROM
5. soft reset your phone and have it charged over 50% (I have it fully charged)
6. wait until the system starts on your Artemis
7. turn on flight mode (probably not necessary, but I wanted to minimize any risks)
8. connect your Artemis to PC with a USB cable
9. wait until ActiveSync icon in your tray (lower right corner of your windows desktop) turns from gray to green. If you connect your Artemis for the first time to PC, you do not need to set up synchronization, just click "cancel" on the first screen of "Synchronization Setup Wizard"
10. while ActiveSync icon is green, run c:\USPL\start_uspl.exe
11. a DOS screen will pop up with the text "Initializing: 0.." in the bottom indicating probably seconds from the start (it stopped around 70 in my case after about 1.5 min)
12. DOS screen disappears and PDA Phone ROM update utility pops up
13. at the same time, your Artemis turns blank (orange/green LED turns off as well)
14. tick the check box next to " I understand..." and then click Next
15. tick the check box next to " I completed..." and then click Next
16. a box saying "Verifying information on your PDA..." pops up
17. on the next screen click Update button
18. next screen says "Upgrade to ... image version 9.99" - click Next
19. Next screen says "You are now ready to update..." - click Next, a window with a blue progress bar appears with a text "Updating ROM image..", it quickly runs to 100%
20. next screen says "Congratulations! ..." - click Finish
21. your phone turns on and boots into your old system, however it should be CID unlocked now
22. your Active Sync should reestablish and icon turns green again
23. do not touch anything (phone or USB cable) and run C:\ROM\ROMUpdateUtility.exe (make sure activesync icon is green)
24. PDA Phone ROM Update utility window appears, tick the check box next to " I understand..." and then click Next
25. tick the check box next to " I completed..." and then click Next
26. a box saying "Verifying information on your PDA..." pops up
27. on next screen click Update button (says "Current information...")
28. next screen says "Upgrade to ... image version BnB2.0" - click Next
29. Next screen says "You are now ready to update..." - click Next
30. a window with a blue progress bar appears with a text "Updating ROM image..", your Artemis will have light gray screen with blue progress bar showing the progress of flashing - do not touch anything and wait (it took 2-3 minutes on my 3 years old PC)
31. next screen says "Congratulations! ..." - click Finish
32. your Artemis turns on and starts booting, you can disconnect it from PC now
33. the boot screen remains the same (T-Mobile in my case), so do not panic!! it is normal
34. wait until calibrate the screen appears, calibrate, choose time zone and you are ready to use your new OS
35. let me know if this manual was clear enough, whether it helped you and please suggest potential changes for improvement
Take care,
Dzim
i've just succesfully flashed my dutch CID-LOCKED MDA Compact 3 with this method, so i'd say it's reasonably fool-proof
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Cheers Dzim!
Your instructions worked perfectly.
One very happy complete idiot here!
Furbious said:
A couple of questions before i take the plunge - if my t-mobile cmda iii is already CID unlocked, can i just go straight to the update rom part.
Also, is there any way of dumping my standard t-mobile rom first off? I'm having trouble trying to use itsutils due to the app lock.
Click to expand...
Click to collapse
There is a TMobile rom on here somewhere already, I just cant find it at the moment
My Compact 3 it’s death now. After pres voice commander button MDA start only to the boot loader. Can’t run complete system.
Pleas tell me. How can I write the new rom with WM5 or WM6 ?
OOPS! Working well apart from the "cant save word documents" bug!!
Just an update - to use the v1 or v2 black and blue, even though it is unlocked, you still need to use the supercid util.
Otherwise you get the rom update getting to 3% before crashing out to say the rom is corrupted.
I've now converted 2 other tmobile compact mda IIIs successfully, wm6 is much quicker
Yes, with my Compact was exactly as You say. Now is death. What I can do now to repair it.
big thanks to Dzim, used the idiots guide and now on wm6 =D
cheers!
PS: first post
Hi! Nemesis, try to connect your HTC to your pc in bootloader mode.
Lauch start_uspl.exe in USPL folder. Follow instruction on post N°9 by DZIM.
After USPL your HTC should reboot (maybe in bootloader mode only).
Launch the ROMUpdateUtility.exe in Black&Blue ROM v2 and follow instruction.
Thanks gguyaz
Pleas tell me.
Could I doing this upgrade with Windows Vista on my PC?
this is a question for a friend. He said he got these problems when he was upgrading to the official htc wm6 rom:
I've tried to ugrade my Orange SPV M3100 with this RUU, but with no success.
First issue: when i have connected the phone to the PC, established active sync connection and i run the RUU, my phone disconnect and show a screen with RGB stripes during the first "Verifying the information on your PC, please wait" screen. ActiveSync connection is disconnected so i can't continue the update process, and i must soft reset my PPC...
So i've tried to connect the phone after this step of instalation and:
Second issue: After i press Next button on the screen "You are now ready to update your ROM image", the progress bar shows up and the phone disconnect from the PC and turn off. After a while the RUU says "no connection"...
What am i doing wrong? I have image version 1.23.78.3 on my PPC. Please help. Thx...
Please can someone help him out?
Appreciated.
the 3 coloured screen popping up is normal with this RUU, I have upgraded two devices in the same way without problems ... did you leave the upgrade program running through during the "Verifying device / PC" phase or did you abort? It takes about a minute or so until the next window pops up on the PC ...
a question for a friend
mms6 said:
this is a question for a friend. He said he got these problems when he was upgrading to the official htc wm6 rom:
I've tried to ugrade my Orange SPV M3100 with this RUU, but with no success.
Click to expand...
Click to collapse
Im not expert and never purport that. I thing u need 2 tell us a little bit more.
Your currently ROM, SPL, if your device is Super CID or Hard-SPL etc. some one can help u
God luck
thank you to all of you. I will try to get some info on CID, SPL etc.
I will come back with some more info in a little while
have him download the ROM that MrV posted so his/your device does not need to be SuperCID and it should run just fine put the phone into boot loader before the update begins and should be fine
thank you very much
mms6 said:
this is a question for a friend. He said he got these problems when he was upgrading to the official htc wm6 rom:
I've tried to ugrade my Orange SPV M3100 with this RUU, but with no success.
First issue: when i have connected the phone to the PC, established active sync connection and i run the RUU, my phone disconnect and show a screen with RGB stripes during the first "Verifying the information on your PC, please wait" screen. ActiveSync connection is disconnected so i can't continue the update process, and i must soft reset my PPC...
So i've tried to connect the phone after this step of instalation and:
Second issue: After i press Next button on the screen "You are now ready to update your ROM image", the progress bar shows up and the phone disconnect from the PC and turn off. After a while the RUU says "no connection"...
What am i doing wrong? I have image version 1.23.78.3 on my PPC. Please help. Thx...
Please can someone help him out?
Appreciated.
Click to expand...
Click to collapse
This kicked my A$$ for about an hour as well. You'll never want to actually stop the installation to startup activesync. That's where things get jacked up! Just make sure that activesync can see the phone before you run the RUU_Hermes.......Ship.exe file.
1. Make certain that Activesync works before you start (I had to upgrade to 4.5) and synchronize the phone on the WM5.
2. Launch the RUU_Hermes......Ship.exe update and Click the "I Understand..." box and then Click Next. You're phone will display the Red, Green, Blue, White bars and show USB as the connection.
!!!!DO NOT REMOVE THE USB CABLE UNTIL THE ENTIRE UPDATE HAS COMPLETED!!!!! This is where you're making a mistake just like I did.
3. The Next Screen shows the Follow the instructions below.........etc. and it asks you to 1. Connect the PDA to the USB 2.Establish an Activesync connection..... 3. Disable the standby...... 4 Make sure Main Battery..... and it has a check box at the bottom.
!!!!! DO NOT TOUCH THE PHONE OR THE USB CABLE !!!!!! YOU SHOULD STILL SEE THE COLOR BARS ON YOUR PHONE!!!!
Just click the checkbox that says "I completed the steps as indicated above"
and then click NEXT.
4. It will say Verifying the information on your PDA Phone... Please wait..
5. You'll get the Update the current ROM version UPDATE box to click, do so.
6. You'll get the Verify that you want to update the ROM version screen, Click NEXT
7. It will go to the You are now ready to Update your ROM image screen. click NEXT
AND MIRACLE OF MIRACLES....You'll FINALLY see the Gas Gauge percentage screen update on your phone and the PC. Wait about 12 minutes, say a prayer for our troops, and get ready to enjoy WM6!
Hope this helps!
Schwazche
Firstly I would like to say thanks to this site and the trinityguides.info site for the great work people have being doing and making available to everybody, it is great being able to use my trinity with wm6, keep the good work going!
Now the issue I seem to be hitting the same "error [260] connection" every time I attempt to update anything on my Trinity. I have followed the advice on the trinityguides site regarding being stuck in bootloader mode to no avail, and I can't seem to find anything in the posts on the xda site which will rectify the issue.
Previously I have been able to update to AX3L v2.8.01 version without any problems, but I decided to update to sammy's ultra light, it initially kicks into des' crashproof sspl, but then it can't connect to the pc. even when I manually enter olipro's hard-spl it does the same. I have tried to re-install hard-spl, but can't. Disconnecting the usb option in the activesync settings doesn't do anything either. Does anybody have any suggestions for me please?
I am not even too sure if my trinity should have both Des' crashproof and hard-spl on it at the same time? Could someone advise me on whether this is alright please?
the tech details:
Trinity
AX3L_OS_v2.0.8.2
radio - 1.46.30 (even though it doesn't say this in the device info, or boot screen after soft reset)
Home PC - XP (just in case)
Did you also try flashing it again, the ROM I mean. I have this error also but as soon as I execute the ROM flash again it finds the device and starts flashing:
http://forum.xda-developers.com/showpost.php?p=1449597&postcount=2
I am assuming you mean flash with the new ROM, sammy's in my case?
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
No, I am in the same situation. The first attempt puts the device in 'ipl-sspl by des' bootloader mode then after about 10 seconds or so the error[260] is displayed on the pc. If I exit the ruu app and attempt again, nothing new happens on the trinity (i.e. it is still in Des bootloader) and the message is displayed again.
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
What operating system en activesync are you using?
On the PC I am using XP and Activesync 4.5
Check your connection settings to accept USB connections. Also, try using Hard-SPL 1.30 before flashing the ROM again.
deejacker said:
the thing is that when it first goes into des bootloader mode, the white strip doesn't have any text in it. If I pull the usb cable out then put it back in, 'serial' is then displayed in the white bar, but I am still in the same situation as before.
Click to expand...
Click to collapse
In your PC, try another USB connection.
BLOODY HELL!!! It is the simplest things which we often forget to try. Thanks Jotam for pointing out an obvious point, it must have needed a re-plug of the usb cable into another port for the pc to pick up the device again. I will remember that for future updates so I don't make a dumb ass of myself again. Thanks guys/gals.
Vista
Using Vista? if so which version?
Hi I asked this question yesterday, I am a noob :-[ but the only difference is I'm using Vista Ultimate.
Just for others who have the problem.
When you replug into another USB port (Luckly I've got two on my laptop..)
I used the Vista drivers from TrintyGuides and bingo !
now I try and flash a WM6.....English or Italian...maybe French.
Thanks for the help I keep you posted.
Richard
It works
Now to discover the joys of WM6 after only having WM5 for two weeks....
/i am getting the same only rom update 3.14.4.1 now sees the phone..
has the device name changed???
evene exploit no longer sees the phone
sorry, can you be a little more clear.. what ROM are you flashing, and what exactly is happening?
by the way... i thought error 246 was the connection error... am i mixed up? which is 260?
This seems to be on any rom bar the Dopod roms
and it says 260 connection error
Error 260 connection error - the phone is not going in to bootloader mode - and the RUU cannot seem to initiate communication with the phone.
I'm getting this a lot recently trying to flash.
However, Hold the power and camera buttons while resetting with the stylus (keep them buttons held down).
When you get to the bootloader - plug the phone in - wait till you see the USB at the bottom of the bootloader screen - then run the RUU again - it WILL work - every time.
I used to get this error message alot. sometimes the programs you install don't allow you to update even if you force the phone into bootloader mode so you have to hardreset the device and then upgrade.....hope this helps
htc diamond stuck
T-Rob said:
yes, as described in the link I posted before. As soon as the error occurs, do not touch the phone, leave it, just start the ROM flash procedure again. (execute ROMUpdateUtility.exe)
Click to expand...
Click to collapse
hi ,
my htc diamond stack, no respond on the screen i try to do hard reset with tree buttons but its not working, nothing happaned, screen stay home screen with the time and not responding touching the screen at all
please emergensy help
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Will this work?
I saw this on said thread, but I presume it applies for a Herald phone, will it work?
The tricolor mode is "bootloader mode"?
Isn't there some sort of restart that can fix it?
Can someone elaborate on this? I'm really a super-noob!!!
"Try a SD card flash to unbrick your device
This is how:
MAKE SURE THE HERALD IS FULLY CHARGED BEFORE STARTING THE PROCES
#01 Download your original RUU
#02 Download (if not yet installed) WinRar and install
#03 Copy your full sd micro card to your harddisk and format your card with FAT 32
#04 Rightclick the downloaded exe file with your original RUU, click Unpack here
#05 In the map the will be created you will find a file (or similar) called RUU_signed.nbh. Copy this file to your formated sd microcard.
#06 Rename the file to Heraimg.nbh
#07 Get your Herald into bootloader modus by pressing the comm manager button and the camera button and pressing the reset button at the same time. Do not release both buttons until your in bootloader.
#08 Once in bootloader pop in your sd micro card.
#09 As soon as your card is popped in the screen will say something like "Reading SD card". Wait it out till it says "Push button to start" and slide the indicated volume slider down.
#10 The Herald will start the flashing proces. Wait it out till it says "Press any button" and hit the send button.
#11 Perform a hard reset
#12 Voila! Your back in business"
velascoperroni said:
I'm the newbiest of them all, I think I bricked my brand new Excalibur!!!
Sorry if I'm posting in the wrong place, but I need heeeelp!
O.K., here it is:
I just downloaded kavana's 080314 WM6.1 installer for the HTC Excalibur, I ran the exe and followed instructions, afterwards, the ROM app opened and started upgrading the phone but it got stuck at 1%, it made be go thru the recovery process several times (unplug, turn off, disconnect battery, turn on) but it always started on tricolor mode and always got stuck on 1%, after a third recovery process the ROM app just quit and left me hanging on tricolor mode!!!
Activesync won't connect now, I try to run kavana's exe again but it doesn't recognize the phone either, the phone is on, conected (windows makes the usb sound for connection) but it is not recongized, it's as if it's not plugged.
It is stuck on tricolor mode and I don't know what to do!
Please help me!!!
Click to expand...
Click to collapse
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
timothyjok said:
I believe you didn't application unlock it first. I had same issues. I finally got it to load. I don't think you bricked it. Remove battery wait a few seconds and restart phone
Click to expand...
Click to collapse
Already did that... still on "brick" mode...
Question: is my warranty still valid? I bought it 3 days ago.
you can solve simply to launch original upgrade to wm6 rom
glenbo said:
Try the dicussion thread "Bricked my T Mobile phone" there are plenty of answers there.
Click to expand...
Click to collapse
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Yes, You Are Correct!
pfunkside said:
Do try these procedures first. I'm just throwing it out there but if you try again it is probably a better choice to flash to WM6 first. Then try flashing to the 6.1.
I'm sure you can return it but come up with a believable excuse.
Click to expand...
Click to collapse
Yes, that is the correct path for him to take, install a 6.0 ROM first, before installing a 6.1 ROM. I suggest he install the T-Mo official wm6, just to get things started in the right direction again.
(1) If the device is still in the tri color mode (bootloader mode), that's a very good sign, it's not bricked. Connect the device to your PC via active sync in the tri color mode, you may think that the device is not connected to Your PC but it is, it may not look like it's connected, run the official T-Mo wm6 ROM RUU WWE, it will install on your device as long as your device is in the tri color mode.
(2)Once you get the wm6 ROM installed on your device, you must first SDA_ApplicationUnlock your device, next you want to Certificate AppUnlock and SurrealApplication Unlock your phone. Now, the reason you are doing all these unlocks are because you coming off the T-Mo wm6 ROM.
(3)After all this have been done, it now ok to try to install the 6.1 ROM on your device.......!
Great support!!! But now comes the obvious question from the n00b of the n00bs!!!
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
T-Mo Wm6
velascoperroni said:
Got it, now the big question is: how to flash to WM6?
Is it done by the steps I posted early? (formatting SD, etc.)
Also, where do I get the T-mobile RUU?
Finally, there are a few things you should know, my phone was bought in Mexico, under the cellphone company Movistar (Spain's Telefonica and I've heard U.S. AT&T), it had WM5 before I "bricked" it (hehehe).
When I turn it now, a few miliseconds before the tricolor screen I can read in the phone a "waiting for SD card" message when the tricolor screen comes on, I get this version of RUU 1.15.000.
I appreciate all your help, as a contribution to this amazing community, when I get thru this, I hereby commit myself to write a fully understandable guide for noobs with the same problem (not too long).
Click to expand...
Click to collapse
Is your mobile device still in the tri color mode, if so just connect it back to your PC via active sync, It will accept the download! OK you can get the T-Mo wm6 at T-Mo's website, if not I will send you a link with the T-Mo wm6 RUU. Don't panic, you are still in the game.......!
Update!! Phone unbricked but still on WM5!
Ok... I used this ROM: HTC_S620_WWE_1.27.405.1_4.1.13.44_02.94.90_Ship.exe
It went thru the upgrading process but got stuck at 3%, anyway, it finished with a message like "this ROM cannot be used for your phone" or something and restored WM5.
Now I will follow instructions on the thread: "The Full Guide To Upgrading From Windows Mobile 5 to 6" and I'll be posting my acomplishments on this thread.
Question: The reasons for me not being still able to upgrade may be:
1. I haven't unlocked phone,
2. My phone is for Mexico and cellphone co. "Movistar", or
3. I'm running Windows XP as a virtual machine (via parallels) on an intel Macintosh and somehow there's a problem with the USB drivers.
I'm rooting for option 1 (but kavana's upgrade was supposed to already unlocked it). Option 3 maybe but then, why do I get Activesync to run? Option 2 would be a bummer!
T-Mobile WM6 RUU WWE ROM
Get the T-Mobile official Wm6 RUU WWE Rom here http://www.mediafire.com/?0vtw32zmuz3 ......!Oh! I throught you had a Excalibur.....!
Just can't seem to upgrade WM5 to WM6!
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Your Answer Is In jockyw2001 Thread
velascoperroni said:
Iv'e tried the T-Mobile ROM and the HTC ROM and I get an: "invalid vendor id"
I tried every step on the aforementioned thread, even de CIS unlock, and still no luck... again, my vendor is movistar/telefonica/cingular.
Any thoughts?
Click to expand...
Click to collapse
A easy frix, but read the instructions very carefully, jockyw2001 thread is located in the sticky section. What you are looking for will be in post #1.........!
New Instructions
Run the Excalibur Uspl-CID ByPass.zip, extraxt on your PC and open it there, you will see several file folders. Open the one that say (uspl) MS-Dos batch File, follow on screen instructions by pressing any key. This time when you see the white screen on your device do not panic! Run the HTC WM 6 ROM, this is done while the screen is still white on your device. Just follow the on screen instructions on your PC.............!
Now I definitively bricked it!
I ran the CID unbloker, screen went blank, ran the ROM, it got to 16% and made me do a recovery, after the recovery it gave me the same "invalid vendor id" message and it automatically restarted the phone, but...
The restart stopped at the HTC intro screen!! I've restarted it several times and it just stops on the first HTC logo screen... even a hard reset won't fix it!!!
HEEEEEEEEEEEEEEEEEELP!!!
Here is a visual aid.
You are not reading into detail. Use the Tmobile rom instead of the HTC Rom.
http://forum.xda-developers.com/showthread.php?t=368998&highlight=Jamerican
Still Bricked!!!
Yeah!!! superb visual aid!!!
I just wish I had seen it before I bricked it!!!!
This is the current state of my phone: I press power, I see a white screen with the HTC logo in the middle, the phone vibrates, still the same HTC logo... and it is stuck that way! I can't turn it off, I have to take out the battery!!
I've tried a hard reset, same thing happens! It stays stuck on the HTC logo screen and I'm forced to pull the battery out for the phone to shut down.
It is obviously not recognized in any way when I plug it to the PC's USB.
What made this happen? HTC Generic ROM got stuck on 16% before telling me "invalid vendor id", restarted the phone and voila: brick!!
Boy, I wish I was back in the tricolor mode!!!
IS THERE NOTHING I CAN DO?
I'm seriously thinking about going back to the vendor on monday and saying: It was like this when I woke up (I just bought it three days ago!!!)
If it gets that far, it doesnt seem totally bricked, ima PC man, so this may be off, but it seems like some kinda bootloader error on the phone itself....IE, the HTC screen is all that the bootloader tells the phone to load. Have you tried forcing the phone into bootloader mode?
I Looooooove Google!!!
OK... I found a turnaround for the problem... got it to go to bootloader mode!!!
Whenever something like these happens to you this is the hard way to put your excalibur/dash in bootloader mode:
1. Take out battery and sd card;
2. Plug your USB cable to your PC (not yet to the phone)
3. Press and keep holding the SIMB. key (the one with the camera next to the space bar)
4. Plug your USB cable to your phone (while still pressing the SIMB. key)
5. Voila: You are in bootloader mode!!
This was gotten for a 15 min. search in google!!
Now... I'll keep going with my WM5 to WM6 upgrade...
Hi!
I was using Newplow's WM6 038 ROM with my N560.
Yesterday I tried to write another ROM(WM6 038 with 8MB pagepool) but during update got an error.. It said it just failed.
Now my N560 is stuck on booting screen(people climbing mountain..)
I tried Warm, Cold, Hard reset but with no luck.
Even the power button doesn't work so I had to remove battery. When I insert battery it powers on by itself.
I can enter bootloader screen by pushing power+record button so I tried to copy rom image file to SD card but it doesn't work.
I tried two ROMs(OS_213U.nbf from Original WM5 ROM and Newplow's) and 3 SD Cards(2GB SD, 1GB MicroSD with Adopter, 16GB SDHC)
Is there any recovery tutorial in bootloader mode?
Help me please!
Sorry for my English.
Have you tried flashing a ROM through the computer rather than the memory card? Try going into bootloader and flashing that way rather than the card.
The pagepool ROM is meant for N560s that have been upgraded to 128Mb RAM... have you upgraded the internal RAM to 128Mb? If you have not, then this may have caused your problem.
I had this problem when flashing to 038 normal RAM (from 035). A hard reset reset to the normal start screen, but nothing worked. However, trying a new burn with the Loox flash tool restarted the process and it worked. I found the cure was to make sure you hard reset the N560 before doing a burn. It appears to be that you have to do this to release enough RAM for the burn program to reside and for "working" storage. You may not have done this.
I suggest you try simply re-running the flashtool with SD/SDHC cards removed, battery in place, on the cradle via your PC, even though it appears stuck. The signals coming from the USB link may wake up the bootloader routine in the N560?
Solved the problem! Thanks for your comments!
I asked same question in Newplow's guestbook and the person who made pagepool rom answered. I used MTTY to revive my pda.
What I did is in below post. need translation
http://4pda.ru/forum/index.php?showtopic=55274
Hi all,
I have the same problem. N560 is stick on the himalaya picture. I tried to falsh from WM5 to new rom for Wm6 and after installation the pda stuked. So I did a warm reset and now only the start picture is apperaing. Problem is that battery is down now.
Can someone give more info on the process followed to revive the PDA ? I just cannont read russian (may be Jinsu77 ?)
Many thanks for support in advance
same problem here please please please someone help us
the only thing i can do is the l c:\os_213u.nbf on mtty program and nothing else happend to the machine
sorry for my english
read, and pay attention here:
[email protected]@p://a.mod-site.net/gb/u/newplow-1.html
POST 203.
It was me asking on Newplow's guestbook.
In case you're using Vista, you need some trick to be able to rom update. Read below.
http://www.modaco.com/content/windo...u-on-vista-it-can-be-done-the-ultimate-guide/
And then you need to download MTTY (I used version 1.42, got it by googling) and follow below steps.
(used google translation from 4pda.ru)
------------------------------------------------------------
For rom update without ActiveSync.
1) take this set of extract, copy it to the folder with the firmware.
2) copy the file os_213u.nbf example in C: \
3) You press the button Recorder + food and poke in the hole reset (Recorder button and hold until you eat dolphins)
4) plug the device to a PC, the Task Manager, shooting process - wcescomm.exe
5) Run mtty, choose Port: USB, connect.
6) If mtty caused an error and shut down, simply restart mtty, if not typed commands, then repeat the procedure with paragraph 3.
7) in mtty command, enter: (first letter in kommande - a little l l от слова from the word L L oad)
> l l c:\os_213u.nbf c: \ os_213u.nbf
Since the end of the process will be an inscription about the error, remove the device from the PC.
9) Run rom update, zhmete "next", until you see dolphins.
10), plug the device to a PC and program.
---------------------------------------------------------------
Hope this helps you all
in advance sorry for my english
I am doing all the instructions carefully and the mtty show this
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,1A0F023Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
the pda shos the dolphins and the full blue bar
after without change anything i run the PocketLOOX5xxFlashTool that i have in the same folder with the :
EnterBootLoader.exe
OS_213U.nbf (originally rom)
RUUServer.dll
RUU.dll
and the only thing i can see is that the PocketLOOX5xxFlashTool is trying to find the pda without any luck
also the pda is stucked in the same screen with the dolphins and the blue bar
do you see any mistake in this procedure
Helppp!!! please
tuluba said:
Helppp!!! please
Click to expand...
Click to collapse
have you closed EVERY process of activesync before proceding with mtty?
I close the wcescomm.exe and the rapimgr.exe is there anything else?
The pocket LOOX 5xx FlashTool cant connect with the N560 and at the and says that Error"The language in this Flash Image update (ENGLISH) differs from that on your device()!" and i have always english rom exept maybe from the last rom "the killer" with the 128MB rom that i dont know if it is an english or something else because the device never opens to see
After flashing in MTTY(don't care about error messages), you need to unplug your n560 from PC. And then proceed romupdate until you see the dolphin picture. Now you plug n560 to PC and cilck next and wait for a while.. Hope it works!
I change the language of the rom and it works
thank very much all of you
At all they have Probs with flash from SD Card: only use a Card with 512MB! I think a Card greater then can't read by the Bootloader....
hey.
i am compeletly new here. I have the same with my n560. I tried to upgrade to 128mb but after restart I see only climbing. I tried everything here but on dolphins afterr line is blue it is finished. that I am unpluging device. starting looxflastool for 560 and first is trying to connect by active sync and that when no connection made I see dolphins on left screen of flash tool window. than I am pluging again and after couple secs I see that: Error"The language in this Flash Image update (ENGLISH) differs from that on your device. I tried to change rom on every language but not working as well. PLEASE HELP
if that helps than i will add than on top when delfins i see on 560 is two lines. first is typed 2.14.G4 on second directly below is 2.15.
and when mtty 1.42 finishing flashing i see following:
Image Download Finish
OEMFlashWrite(A0000000h,8C200000h,0224002Ah)
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????
ChrisDo said:
Need help!!! Please!!!
I bricked my N560. I tried to downgrade from WM6 to WM5 and now I see only delfins and in the first line "2.14.G4" and in the second line "2.15"
What can I do?? How can I flash WM6 or WM5 ROM when there is no connection to the PDA????
Click to expand...
Click to collapse
You can usually get back to the boot loader if you do a hard reset. I am sure you know how, if not you will find it in the FSC CDROM manual that came with the device. Let us know if this works? I have got stuck at this point too, so I know it works..... hopefully!