Can't update ROM in my O2 XDA anyways... - MDA, XDA, 1010 Software Upgrading

Several days earlier, i want to update flash ROM image in my O2 XDA. I want to update my WM2003 (ROM v4.01.16 ENG) to WM2003SE (v3.04.00 ENG - downloaded from xda-developers FTP). But any attempts to do this ended unsuccessful. When i try to update my O2 XDA through SD Flash Card, with the XDAtools, as it is written here: http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD , Wallaby boot loader don't boot from SD, and don't displays any messages, look like SD card is not inserted.
When i try to update through USB or serial cable, with ActiveSync, the Programme A display this error message:
============================================
ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR
============================================
Cannot execute the remote communication program.
Please make sure that the USB/Serial cable is properly connected.
============================================
However, Radio stake update (with Programme B) is working, and updating through USB.
What my actions is wrong? Or my device is broken? Please, help me!

As mentioned 1000 times here in the forum:
Update from this ROM Version via EXE-File is not possible You have to downgrade first via SD-Card to another ROM Version (e.g. 3.17.03)
Stefan

LumpiStefan said:
As mentioned 1000 times here in the forum:
Update from this ROM Version via EXE-File is not possible You have to downgrade first via SD-Card to another ROM Version (e.g. 3.17.03)
Stefan
Click to expand...
Click to collapse
Thanks a lot!!!! I try this tomorrow!

Unsuccessful downgrading... Wallaby boot loader don't boot from SD again! What wrong?!

What for SD-Card Writer are you using?
Many internal versions are causing problems.....
You could try enter the bootloader, make a backup of your current ROM. Than reenter your bootloader and check if now the option for downloading the ROM from SD-Card is displayed....
Stefan

LumpiStefan said:
What for SD-Card Writer are you using?
Many internal versions are causing problems.....
You could try enter the bootloader, make a backup of your current ROM. Than reenter your bootloader and check if now the option for downloading the ROM from SD-Card is displayed....
Stefan
Click to expand...
Click to collapse
All right! I understood how to do this. Just reading this forum. I make update ROM through SD card! Forget any cables! SD flashing is cool! Trouble was in bootloader v5.17, with the wallaby_patch_tool, and XDArit, and description for bootloader update, i done this!!! Now i want setup special edition rom!

Related

Stuck in WM2003 4.00.10, cannot use phone app.

(Was: Help me... Help me... Help me... Anyone help me !!!)
Hi all!
I stuck in WM2003PE v. 4.00.10. Since I have been updated to it, my XDA cannot use phone function. Cannot receive calls and while I make a call... appear a popup menu from signal: "The operation failed". I so sad, I don't know what to do now :x . Anyone help me ???
My XDA is:
Wallaby Bootloader: 5.17
ROM version: 4.00.10 (I feel a vindictive hatred for it :x :x :x )
Radio Stack: 4.21
I'm from ASIA
As you known I can not downgrade from this ROM version by exe file.
I can not downgrade from this ROM version by SD card because my Bootloader is 5.17
XDAtools is a new tool. Can I use it to downgrade my XDA? Tell me method by detail, please (sorry, I don't want to sad again).
Thank for all
You CAN downgrade to say, 3.17 (Thats my TMobile version) if you have the nk.nbf file and use the XDA Tools.
You have to do it via the Wallaby Boot loader method... by placing the ROM on an SD card (via XDA Tools). To do this, I think that you need an SD card reader, as XDA Tools does not seem to do it via the phone...
There are instructions on how to do this as well as
A BIG WARNING about 5.17 boot loader.
I did it on my TMobile phone, with Bootloader 5.15.
So, do NOT follow the instructions I have stated here, read on this site and in the forum about how to flash your rom via the SD CARD Method.
That should do it for you..
BTW, when you write the ROM to the SD CArd, it WILL erase the SDCard data, so save off your stuff before you do this.
J
Thank jta
But, How do I have to downgrade my Bootloader from 5.17 to 5.15?
I tried XDAtools but no success
Anyone idea?
Hi VHS,
My XDA had bootloader 5.17 like yours, and I was stuck with T-Mo 4.00.10 also. I was able to correct the situation though, by doing the following:
I changed the bootloader with XDAtools from Jeff (it has 5.15 included), by running the “Fix broken bootloader” part of the program.
Then, I used SDcard/bootloader method to go back to 4.00.05, and successful. I knew I could use XDAtools also for doing this, but I preferred the SDcard/bootloader’s way then. Mind you that, using SDcard/bootloader’s way was very easy after you downgrade from 5.17 to 5.15. Since then, I could flash whichever rom I want, but not 4.00.10.
If you want to do the same, please read as much for the detail from the various forum here and carefully.
I hope this helps.
Hi beeheij!
Can you tell me the way in order to downgrade my bootloader from 5.17 to 5.15 by detail? I tried a lot of time but no success. I don't know why. And you tell me go back v.4.00.05 by SD Card.
I'm grateful to you very much
Has it occured to you that
"Help me... Help me... Help me... Anyone help me !!!"
is a really, really, really bad subject line ? I changed it to something which may get many more people to take a look and possibly help you...
If you can still use ActiveSync, you could try to use Jeff's version of the XDAtools to downdgrade the bootloader to 5.15, and work your way out from there...

problems with rom upgrade and bootloader upgrade, pls help

I try to upgrade my XDA to the Special Edition Rom, but when I run the Special Edition Rom executable (program A) I get the following error message :
Error 007: no rom image file.
Cannot find the rom image to upgrade your Pocket PC. Please download and try again.
After I click OK on this pop-up window, the program ends and no changes are made. :?
(Besides this, the "release notes" window stays empty: no release notes are shown.)
As suggested by biso007, I also ran the "fix bootloader"program from the XDA tools to upgrade the bootloader to 5.15 and to get rid of the write protect, but I get the error message "Unable to find flash info offset. Cannot disable bootloader write protect."
Who has a suggestion what I should do next ? The SD card method ? How does this work ?
Thanks a lot, I am depending on you guys. XDA developers is the best !!!
Regards, Bapa
Most probably your boot loader version has a protection mechnism (higher than 5.17) ... try the XDAtools flashing which should update your boot loader to 5.15 ... otherwise you have to use the SD card method.
problem with "fix bootloader"
As suggested by biso007, I also ran the "fix bootloader"program from the XDA tools to upgrade the bootloader to 5.15 and to get rid of the write protect, but I get the error message "Unable to find flash info offset. Cannot disable bootloader write protect."
Who has a suggestion what I should do next ? The SD card method ? How does this work ?
Thanks a lot, I am depending on you guys. XDA developers is the best !!!
Regards, Bapa
Using SD method to downgrade your bootloader!

T-mobile WM2003 upgrade problems

Hi everyone, I'm using an Asian O2 XDA and was running the 3.20.06 OS. I messed around with the ROM from Yorch's kitchen - the T-Mobile WM2003 upgrade, version 4.00.21.
My current problem is that I am unable to flash back to my previous version of ROM, or any other versions. My O2's running the version 6.22 bootloader and I have been unable to get it to boot from the SD card despite many attempts. Anyone out there that has managed to solve this problem ??
Regards
Maybe...
I dont know but maybe u need to use fixboot from XDAtools ?
it should help but i dont really know cause i didnt have such problem...
Boot loader 6.22 doesn't detect ROMs on SD cards. Try the XDAtools with any cooked ROM from the kitchen here and it will update your boot loader to 5.15 which doesn't have this restriction.
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Try connecting your device to the PC and sync ... then from the XDAtools directory run this command:
pnewbootloader.exe bootloader_v5_15.nb0
oldwrym said:
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Click to expand...
Click to collapse
XDATools won't work for flashing under T-mobile 4.0.21
cgigate said:
oldwrym said:
I've tried flashing the ROM using XDATools but the it kept giving me a message that the connection was reset by the device.
Is there something that I'm doing wrong ??
Click to expand...
Click to collapse
XDATools won't work for flashing under T-mobile 4.0.21
Click to expand...
Click to collapse
Is there any chance to get the XDA back to flashing?

Stuck on v2.00.x bootloader

I've managed to get myself stuck up a dead end.
My device: Orange UK spv c500.
SPL: 2.00.0013
OS: None!
I upgraded to wm2005 but despite updating the reg keys posted by subliminal I couldn't install the certificate I use to ActiveSync with my Exchange Server; so I decided to downgrade.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
My next mistake was to try and re-flash the 'phone with the latest Orange UK ROM (v4.2.1.1). What I'd forgotten was that this updates the bootloader at the same time.
The flash appeared to go fine, but on restart I'm stuck in the bootloader. When I attempt to re-flash again the summary in the RUU says "Image Version:" ie no image version present.
If I was still on a v1 bootloader I'd be able to run IU_SPL+PatchedRUU again to give me an IU mode bootloader. With a v2 bootloader I can run this as many times as I want, but it won't put a lower version on.
Without an IU mode bootloader I can't "r2sd spl" to use itsme's dowload tools. Without a working OS I cant use TyphoonNBFTools to flash the SPL.
Can you think of any other solution?
If there was someway to "con" the rom update process into installing an older version of the SPL I'd be OK. Alternatively if it was possible to change the version of the SPL in SPVDEVS-SPL.nbf I could get it on.
Thanks for your help.
robhughadams said:
I've managed to get myself stuck up a dead end.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
.
Click to expand...
Click to collapse
did you tried this rom backup with your card writer i used this one with psd write and it worked download this one and try it ;-)
greets { ps let me know if this time you sucseeded ;-) }
http://rapidshare.de/files/2633600/backup.rar.rename.html

Bricked, all RUUs report ERROR[300].

My HTC3300 was dead, only can load into Three-color Mode with USB avaliable. I tried all kind of RUUs, including the Original ROMs(English, French, Deustch....)and the newest version , all report ERROR[300]invalid update tool. then the screen of phone stayed in 0% and RUU tool exit only...
IPL 1.27.0001
SPL 1.11.0000 (used the USPL to unlock CID before)
Before Bricked, I successfully updated many versions of ROM, and the last operation is WM6.1.
And I tried MTTY tool, when I tried the command 'DOCTEST', but failed...
Cmd>doctest
Binary partition read/write test, offset=0x0, length=0x400000
Test pattern =0xAA
Flash Binary partition failed.
DOC binary partition read/write test FAILED Cmd
Can anyone help me out? what's happened on my HTC3300?
Thanks!
i think SD card flashing might work not so sure abt it
just put the nbh ROM in root of sd card n enter bootloader
it might work
sheennick123456 said:
i think SD card flashing might work not so sure abt it
just put the nbh ROM in root of sd card n enter bootloader
it might work
Click to expand...
Click to collapse
yeah, I've tried many times the SD card flashing, the screen displayed 'Checking SD contents' , then loaded into the Three-color mode.
I've formated the sd to FAT32 already.
btw, thanks to you!
do u see the counter on the bottom left of the screen???
u hav to press volume slider before it comes to zero
if u wait it will return to tri colour screen
yeah, I'm sure there is no counter on the screen.....
tincomking said:
My HTC3300 was dead, only can load into Three-color Mode with USB avaliable. I tried all kind of RUUs, including the Original ROMs(English, French, Deustch....)and the newest version , all report ERROR[300]invalid update tool. then the screen of phone stayed in 0% and RUU tool exit only...
IPL 1.27.0001
SPL 1.11.0000 (used the USPL to unlock CID before)
Before Bricked, I successfully updated many versions of ROM, and the last operation is WM6.1.
And I tried MTTY tool, when I tried the command 'DOCTEST', but failed...
Cmd>doctest
Binary partition read/write test, offset=0x0, length=0x400000
Test pattern =0xAA
Flash Binary partition failed.
DOC binary partition read/write test FAILED Cmd
Can anyone help me out? what's happened on my HTC3300?
Thanks!
Click to expand...
Click to collapse
Brother, we are in the same boat :-(
My Artemis is also having the same problem.
Below is the output of doctest...
doctest
Binary partition read/write test, offset=0x0, length=0x400000
Test pattern =0xAA
Flash Binary partition failed.
DOC binary partition read/write test FAILED
By the way have you resolved it by now? Is there any way to flash the DOC area using mtty?
$50 Bounty for [Error 300] INVALID UPDATE TOOL, Fix
Mods, Developers, Seniors...
Anyone know how to get around with the Error 300 Invalid update Tool, problem?????
I think we can donate(maybe pay will be appropriate in this case ) to the developers who bring out a fix for it.
I'll put a $50 bounty for a fix to this issue!!!!
Any takers?
Tried renaming the RUU_Signed.nbh to ARTEIMG.nbh and copying it to a small FAT32 TransFlash card to SD-Flash it?
incredulous said:
Tried renaming the RUU_Signed.nbh to ARTEIMG.nbh and copying it to a small FAT32 TransFlash card to SD-Flash it?
Click to expand...
Click to collapse
Ofcourse, tried almost exerything, except hammering it.
But any way, sent the device to service center, let's see what they'll reply! I dont think it will be covered in the Warranty
POOR...
DID YOU REMOVE SD CARD
Jimmy19 said:
POOR...
DID YOU REMOVE SD CARD
Click to expand...
Click to collapse
Yes, tried SD Flashing, tried flashing using RUU in BootLoader mode, nothing worked. Also tried checking the device condition using mtty too! but I get a CMD55 Failed error!!!
Hi,
try to re-download everything using a different browser. My USPL and ROM downloads somehow got mungled with Firefox, once downloaded with IE they flashed fine.
Robert
rfka01 said:
Hi,
try to re-download everything using a different browser. My USPL and ROM downloads somehow got mungled with Firefox, once downloaded with IE they flashed fine.
Robert
Click to expand...
Click to collapse
Did that buddy!
I believe the CID area is corrupt, coz using mtty, I get CMD55 Failed! even a doctest is failing!
Hi!,
it happens to me just like.
I have proven all the possible ROM and nothing. Please, help.
kiko_murzia said:
Hi!,
it happens to me just like.
I have proven all the possible ROM and nothing. Please, help.
Click to expand...
Click to collapse
Brother, there is no fix for this! no one on this forum knows **** about this problem. Everyone tries to help but there is no one who realizes the actual problem and knows a fix to this.
I finally sent my device to HTC Service Center and they replaced the motherboard. Luckily, my handset was in warranty! I should be receiving my Artemis in a couple of days.
I suggest, even you do check out your nearest SC.
That is the only fix, I know of!!!

Categories

Resources