Related
Hi,
I tried to upgrade my MDAc with the rom from TMobile.
During the upgrade my computer asked for this file "wceusbsh.sys".
At that point the upgrade stopped.
No i only see "USB" and "v1.00" on my screen.
The charger led is red.
When trying to upgrade again, i get ether this message:
Error 120, country id error
or
err no device
I located the file "wceusbsh.sys" but still.
After "checking the information on your device" i get the error.
"Error 120, country id error"
How can i solve this problem.
Greg
You're stuck in bootloader. Did you try to upgrade to an other language?
You can try to hard-reset your device 'power & soft-reset' at the same time to boot your magician.
If it doesn't boot, kick it back in bootloader 'camera & power & soft-reset' at the same time for several seconds, till screen turns black & read 'serial v1.00'. When connected to usb it reads 'usb v1.00'
Now get maupgradeut_noid.exe from the ftp. Unzip your shipped-rom file you downloaded from TMO. Put the maupgradeut_noid.exe in the same folder as the unzipped files like maupgradeut.exe, enterbl.exe etc. Then execute maupgradeut_noid.exe instead of maupgradeut.exe this will give the error 120 once more. Just exit & execute it again, now it should proceed upgrading.
Cheers, M
=(
Same problem! Trying to use no id upgrade . I hope it will solve my problem.
P.S. DO NOT upgrade ROM when batt is lo =)
I upgraded my 85' with the "official" wm6 rom and now I cannot go to other roms. The process was solid, meaning I was fully charged, no power loss, and it was synced. I've tried every version of rom available and get the same results. I went through the "brick" thread and I'm affraid I don't quite fit into any category. I can get phone calls and everything works, I just happen to like all of the great ROM's everybody is cooking and want to try them to see which one I favor. I tried using the Hard-SPL and all of the other bootloaders out there and I always get that ERROR [206]. I've tried to restart the machine, and hard reset the 85'. Any good idea's.... Maybe I need to search more? I'll try that.
==============================================================================
UPDATE:
What I should really do is rent a gun, and buy a bullet...
I'm not saying I'm some sort of season veteran of flashing... but I've never had to touch anything after I accept all terms. For some reason, when it came down to the last "Next" form, my phone flashes "Accept" super fast. So what to do?... I push "Yes" soft key fast as I can and it runs like grease lightening... I had to choose SS for the boot loader because it couldn't figure it out... Maybe next time around.
Have you tried to flash a coocked ROM using the microSD card?
Hi,
did you try get your phone in the tri color bootloader screen and then running the Hard SPL program again?
I did not try to do flash it woth the MicroSD card... I just found out that I could flash it with the MicroSD card about 2 seconds ago. And I wanted to Hard-SPL at the tri-color as a last result in fear of bricking but everything is okay now. As I said before, I've never had to touch my 85' while flashing the rom, it just did it on it's own, but that "official" rom was not about being neglected. And then when I saw it flash something and say "yes", I pushed it and never looked back. It's alllllllllllllllllll good.
I do have one question, is the SSPL preferred over the other choices? Or is there one that is recommended?
Hi joshkrajnak,
How did you solve this problem exactly cos I dont understand what your saying:
http://forum.xda-developers.com/showthread.php?t=298640
boz said:
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Click to expand...
Click to collapse
To Clarify: Whenever I went to upgrade my 85' to a different ROM, it wouldn't recognize my bootloader, and then after selecting any of the options, it would give the "ERROR [206]" message and fail miserably with any rom.
What I did to correct it was this: On the "official release" whenever I went to upgrade the ROM, the 85' would show a message at the bottom, the same as any "Notification" would giving me the option to either "confirm" or "dismiss". I did not notice the messages up until it caught my attention out of the corner of my eye on the very last attempt. The messages would quickly appear and disappear, so when the time came and it stated:
Current Rom: 3.25.###.###
Upgrade: 1.##.###
I had to press a confirm notification to continue on or I would get the "206" error message. The quote posted by Binyo is correct, but it does not apply in my situation.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
Although that may be true that some applications may interfere with the upgrade process, I had turned off all applications and killed any services during this process.
I have a ASUS P535 that had working wm5 and I was going to upgrade it to PDAMobiz wm6.1.
I tried to install "PDAMobiz_P535_WM6.1_Build19716_1.1" but got message Update Fail at 80%,
because I had bootloader 06xxxxx.
So I searched at the forums at the web and found someone that gave me help, as following.
"You need to flash the sorg ROM, just choose the base version (appx 30MB),
install that first then you will find that your boot version had been change to 07xxxxx.
If there is any update fail during flashing the sorg ROM just ignore it. Then you flash the vivi ROM.
Link to P525.WM6.1.v0.11.Base.by.Sorg. Just run the rom flash... it'll take care of whats needed"
I installed P525.WM6.1.v0.11.Base.by.Sorg hoping that it will upgrade the bootloader but...
After this I cannot get past the bootloader "galaxy .nb0" not found, and second flash message insert sd card.
Screen is dark and i can barely see all the text in the bootloader.
I have the PDAMobiz galaxyII.NB0 in the SDcard but it doesn’t recognize it. If I put a galaxy.NB0 from Sorg
it starts to install but gives at the end Checksum ok! Update fail.
How to install so that it can recognize PDAMobiz galaxyII.NB0?
Make sure you have formated your memory card first and leave only galaxyII.nbo file in memory card <no folder or any other files>
Then try again. Get the rom from www.asusp535.com. It works for me.
that didnt help me.
i got almost the same problem
i got a P535 with no WM on it. (found it)
i've tried to put a WM6 on it, but it says Update FAIL !
if i copy any GALAXYII.NBO on my miniSD card, it says GALAXY .NBO not found. thats when i rename the GALAXYII.NBO to GALAXY.NBO, but then it says Update FAIL !
i dont know what to do with it
PLEASE HELP!
It worked for me too but I had WM6 official one from Asus before flashing to PDA Mobiz WM6.1
Is your SD Card formatted correctly and is of the right size?
i got a 2GB miniSD card.
i've formated it once in FAT (full format), then before i put a GalaxyII.nb0 i format it quick
do i need to format it full before i put a GalaxyII.nb0 on it?
p.s. can i change the bootloader too? maybe the bootloader is broke
exemple using: PDAViet_WM6.1_19900
when i put a GALAXYII.NBO on my card it says:
2007/05/18 18:03:59
CPU Version: PXA27x
Force Mode!
USB Cable PlugIn.
GALAXY .NBO not found /MicroSD card Inserted
Waiting...
when i rename the GALAXYII.NBO to GALAXY.NBO it says:
2007/05/18 18:03:59
CPU Version: PXA27x
Force Mode!
USB Cable PlugIn.
MicroSD card Inserted
GALAXY.NBO found
Checksum ok!
Update fail!
Reading...
well, i've tried wm5, wm6, wm6.1, wm6.5... non of them worked , i guess the phones bricked
any suggestions?
no one?
please
Try this
You could try this:
Go here http://forum.xda-developers.com/showthread.php?t=423148&highlight=p535+rom and update your bootloader to ver.070518180359 according to the instructions(copy BootGalaxy.NB0 to the root of your Storage Card, connect adapter and push Record+Reset ),then try to flash the ORIGINAL asus ROM.Once you got that,run the asus unlocklang utility from the phone.
After that you should be able to flash any ROM on your device.
A lesson learned from failed flash attempts and bricked devices:
Whatever should happen NEVER UNDER ANY CIRCUMSTANCES-NO MATTER WHAT,don't interfere in any way with the phone during the update of the bootloader.NO MATTER HOW LONG IT TAKES.Better charge your battery to 100% AND also have the phone connected to its charger.
A failed ROM flashing can be corrected,a failed bootloader flashing will kill your device for good.
P.S. whatever you do you do it on your own responsibility,i take no blame for a bricked device.
ํYou do it wrong step.
This rom is worked.
You should be flash WM 6 before.
WM5-->WM6-->WM6.1
It still does not work. I had mine at service (not asus service),just a regular mobile-phone shop which had also service. They could not repair or find any solution for how to fix the p535. So i am stuck with a phone that just wont work. Maybe Asus service could be able to fix it or not.
My phone screen is very dark and only text that is displayed follows:
2007/05/18 18:03:59
CPU Version : PXA27x
USB Cable PlugIn.
Galaxy .NB0 not found (flashing text in RED and with other text in black) MiniSD card inserted
...and at bottom of screen is:
Waiting ...
My conclusion is that i will probably buy new phone to replace this bricked one. A HTC HD2.
Your phone is fine... Just use the USBLoader.exe method... That happened to me a couple of times lately too, dunno if it's an SD Card problem or what...
Basicly, boot into the bootloader, connect it to your Windows PC, and update the rom from the PC...
The comand should be Usbloader.exe GalaxyII.nb0.
I'm sure it works, just hope you can give it a try, and preferably using XP since with vista you'll have to use the HTC old drivers so he can recognize the phone...
I'll leave the USBLoader so you don't have to search it... Atention this is not a Zip file, i just renamed the extension, so just rename it to USBLoader.exe
I wouldn't mind to get a Diamond2 either But i hope this helps getting your P535 to work again...
I would like to try if it works, but how to exactly do the Usbloader.exe method? Which buttons to press on the p535?
I tried and got this message in cmd:
C:\p535>Usbloader.exe GalaxyII.nb0
#####################################################################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
#####################################################################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
try to open \\.\wceusbsh004
try to open \\.\wceusbsh005
USB pipe opening error
Anyone know what it means? I have XP not Vista.
I have now tried on 2 laptops with XP and with same result.
My phone screen is displaying:
2007/05/18 18:03:59
CPU Version : PXA27x
Force Mode !
USB Cable PlugIn.
...and at bottom of screen is:
Waiting ...
Is it possible to maybe fix it? Is there any hope, maybe it is just half bricked.
That's exactly how it should be, you just need to either stop Activesync or install the HTC AS 4.0 drivers... Then the device will be recognized in that first usb port...
And no your device isn't bricked, the it's just the rom messed up if you can into the bootloader it's almost guaranted you can recover it
Please, can anyone post a link to where i can find the "HTC AS 4.0 drivers".
I will post couple of pictures. First is the error message from cmd. Second is with ASUS P535 and the message that it display.
This is pictures when i try to use the boot loader method. Nothing happens.
Yesterday i tried again to put galaxyII.nb0 on the card and flash it from there but message was:
2007/05/18 18:03:59
CPU Version: PXA27x
Force Mode!
USB Cable PlugIn.
GALAXY .NBO not found /MicroSD card Inserted
Waiting...
when i rename the GALAXYII.NBO to GALAXY.NBO it says:
2007/05/18 18:03:59
CPU Version: PXA27x
Force Mode!
USB Cable PlugIn.
MicroSD card Inserted
GALAXY.NBO found
Checksum ok!
Update fail!
It is frustrating not to fix this. And when i use usb i get:
C:\Usbloader.exe GalaxyII.nb0
################################################## ###################
# USB image transfer tool for Intel PXA27X USB Development Board #
# Version: 1220'04 Author: O.C #
################################################## ###################
try to open \\.\wceusbsh001
try to open \\.\wceusbsh002
try to open \\.\wceusbsh003
try to open \\.\wceusbsh004
try to open \\.\wceusbsh005
USB pipe opening error
Can anyone help me with my P535? I have tried everything but maybe i have missed something. Searching the google and various forums in different languages and still nothing.
My last resort soon will be to send this forum thread with questions to asus support and hope for some answers. What to do, how to do it, which files do i need...
And if you people that try to help me need some more information or pictures of my mobile just tell me. This is the best smartphone i ever had and it is shame to waste it.
kill Activesync from task manager first
Doesn't work.
Sorry to ask but why did you flashed P525 rom to P535 device? and why didn`t you upgrade to WM6.0 official Asus rom first then to WM6.1 custom rom?
Sorry I have no fix for your device.
Hi,
I'm using Artemis with one of Tom's ROM. The device was working well. But today suddenly the device won't start up - it is locked at the startup screen showing the SPL, IPL etc. I can enter the bootloader.
Can anybody tell me how to flash the ROM at this stage?
Flash from bootloader
Hi!
Please download an official rom and keep pressed the Power and Record buttons. You will see a screen with 3 colors (red green blue). Connect the USB cable and wait for Activesync. After this start the original rom flasher and follow the instructions. If you can start the Windows, you should flash the USPL again and you can flash cooked roms. If you flashed a new one, i think you should also upgrade the radio rom.
Sorry for my English
well i'll give it a try.
BTW will activesync work if the phone is not booting up?
sure it will, but make sure you have the only phone pluged in, nothing else, and disable all firewalls and antivriuses.
Good luck
i flashed with htc official rom and it worked first. after soft resetting a few time (due to program installation) the phone again back to earlier state.
it is showing:
ipl 3.13.0001
spl 3.13.0000
gsm 2.94.90
os 3.13.0.0
and stuck at this screen.
i tried to update the phone again with the same rom - but i'm getting error 270.
do i need to unlock cid before flashing?
but i can't use the uspl tool as i can't connect to activesync.
pls help.
make sure the battery is fully charged again.
Restart your PC, isbale ll antivirus and firewalls
Better if flashing in XP PC
put PPC in Boating status
Flash Shipped ROM
Specify which software caused you the trouble and do not install it again
CID unlock PPC
Flash any cooked ROM.
once i flashed the phone with the shipped rom successfully. The phone was CID unlocked then. But now when I try to flash the shipped again i'm getting an error message (error 292 or something - stating-invalid vendor id)
archat68 said:
once i flashed the phone with the shipped rom successfully. The phone was CID unlocked then. But now when I try to flash the shipped again i'm getting an error message (error 292 or something - stating-invalid vendor id)
Click to expand...
Click to collapse
you must unlock phone again.
I tried flashing the device with factory shipped ROM. but i'm getting Error 294-invalid vendor id message.
please suggest what to do?
chance are you have stuffed your bootloader...
start from scratch again by running uspl:
http://forum.xda-developers.com/showthread.php?t=311403
than flash your favorite rom again, ideally via sd-card-flashing:
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
greetz
thormdac said:
chance are you have stuffed your bootloader...
start from scratch again by running uspl:
http://forum.xda-developers.com/showthread.php?t=311403
than flash your favorite rom again, ideally via sd-card-flashing:
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
greetz
Click to expand...
Click to collapse
USPL needs activesync running. Can you tell me how to run USPL when I can't boot into windows?
well,
its been some time, but i am pretty sure uspl puts your device into bootloader and operates from there...
have you tried setting it into bootloader, connecting via usb and simply starting uspl?
running a normal setup-routine, there is no need to start it from wm either-simply put it into bootloader and start setup!
greetz
Well i tried that. But it seems that USPL doesn't work without activesync.
i've also tried flashing with SD card, but after a brief "Checking SD card content" message the phone goes back to bootloader.
Someone helpppp pls.
are u sure your sd card is correctly configured, according to the wiki entry- especially part "if above fails" ...?
if all steps fail, assumed you performed them correctly, you might try taking out battery and leave the device fully without power overnight...and restart it the next morning
I've used a 512MB SD card - formatted it- and copied the OS file as ARTEIMG.nbh - put the sd card in the phone and started the phone in bootloader mode.
I think there is nothing more to do.
I can enter the bootloader, connect the phone to PC in USB mode. So, I hope that my phone is not bricked.
But how to revive it?
if you are in bootloader, i dont see why you shouldnt be able to flash!!!
try another sd-card, use another xp computer, exchange the usb cable...
yust to be certain: have you left out battery over-night?
...and what are the details stated on boot-loader screen (numbers)?
oh, and I get the feeling you are not working exactly as told:
in your PC right-click on Computer, then select Manage
Select Disk Manager and then delete existing partition
create a new partition with max size 256MB
format this partition in FAT32
thormdac said:
(i)...and what are the details stated on boot-loader screen (numbers)?
(ii) oh, and I get the feeling you are not working exactly as told:
in your PC right-click on Computer, then select Manage
Select Disk Manager and then delete existing partition
create a new partition with max size 256MB
format this partition in FAT32
Click to expand...
Click to collapse
(i) See post no 5 for the details
(ii) You can not do this with a removable disk (SD card inserted through a card reader). Only works when you can get WM5Storage to work.
archat68 said:
(ii) You can not do this with a removable disk (SD card inserted through a card reader). Only works when you can get WM5Storage to work.
Click to expand...
Click to collapse
...i dont have my micro-sd-card-adapter at hand atm., but there sure will be possibilities formatting your sd card accordingly...try administrative tools/computermanagement/storage/diskmanagement under xp, boot your pc with a diskpartitioner like acronis disk director...
i can only advise you to keep trying...but as long as you can not say for sure sd-card-flashing is working correctly, i wouldnt give up...
and as far as flshing bootloader via usb/activesync goes, i can only say i once screwed my device due to insufficiant battery power during sd-card-flashing and thought it was bricked just at the point you are stuck now!!! - totally resetting it with the power-oiut-method, i.e. battery out overnight, revived it!!!
than agin i sure as hell did everything the way it was ment o be done...and nothing worked until i switched to another pc/ usb-cable!!!
so, to sum it up, DONT GIVE UP!!! bootloader is showing...so there must be a way to get this to work...
greetz
archat68 said:
I tried flashing the device with factory shipped ROM. but i'm getting Error 294-invalid vendor id message.
please suggest what to do?
Click to expand...
Click to collapse
Somebody please help me to revive my phone.
how can we help you, if you dont provide us any results of the steps suggested to you...ideally in a way so we can see what you actually did or didnt do, precisely as told ?!?
greetz
I can't post in developer forum yet....
u ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
u ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
u ERROR [206] : MEMORY ALLOCATION
u ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
u ERROR [208] : FILE OPEN
u ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
u ERROR [212] : FILE CREATE
u ERROR [214] : FILE WRITE
u ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
u ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
u ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
u ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
u ERROR [242] : INVALID LANGUAGE
u ERROR [244] : INVALID MODEL ID
u ERROR [294] : INVALID VENDER ID
u ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
u ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
u ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
u ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
u ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
well,thanks man for the sharing
valuable information may be usefull just in case
I always end up with 270 error.