I was curious. I've noticed people said that if you put the 4.00.16 ROM on, the only way you can downgrade it, is if you reprogram the ROM from the SD card and not by the EXE method.
I was curious as to WHY? What does that .16 ROM do to the XDA to prevent you from doing an EXE rom reprogram?
So far, we lacked time to look into this one. Tell us, and we'll see if we can fix it.
Downgrade unseccesful using SD method from 4.00.16 ver
Sorry if this is OOT: I'm a non techie person so please somebody explain me how to use the SD card reflash metod to downgrade from 4.00.16 bact to 4.00.11 version. If write the new rom to sd using XDAtools it's done. after it I put it back the SD card back to the XDA. I enter the wallaby 5.17 screen by pressing power+ soft reset button. It said wait and then GSM ok after that freezze.
What I'm missing?
The why, I can't say as I have not investigated in detail, I just said to heck with it and bought a SD writer.
What happens after you load 4.00.05 and 4.00.16 is when you try to run and upgrade/downgrade/re-install from Prgramme-A or the newer programmer that came with the 4.00.x installs it fails saying it can't connect to the device, please check to make sure it's plugged in (even though there is a active connection with Activesync).
Using the SD card there is no issue with running the upgrade.
-rich
but what is it that .16 has that .11 doesn't that stops you from changing ROMs via the EXE method?
Also, after putting on .16 and you go back to say .11 via the SD boot method, are you able to use the EXE method to change ROMs after that?
Currently I use the AT&T A20 radio stack and was thinking about trying out the Tmobile 6.24 to see how it works out. Haven't decided yet.
Investigating the no reflash .EXE method
Ok I have found a roundabout method to resolve this only using the .EXE method.
I used the rom kitchen to generate me a 4.00.11 ENG WM2003. After flashing my phone and wanting to make sure i could revert I tried my origonal o2 provided flash upgrader "Radio_Unit_Upgrade_v31413.exe" and the latest downloaded one from the o2 website "Radio_Unit_Upgrade_v31703.exe" neither of which would let me flash them - i get the error "this rom is not for this device" (or some such).
I went back to the rom kitchen and built myself a 3.17.03 ENG O2-Euro rom image and flashed that onto the phone. this suceeded where the o2 stock .EXE failed and I was nearly back where I started.
Now that I had my rom kitchen 3.17.03 back on I tried to install the latest "Radio_Unit_Upgrade_v31703.exe" file again and was greeted with sucess once more!
The question this begs is the same as the origonal however, ok we can get the stock provider rom back on - but why will it let me flash the rom kitchen 3.17.03 back on and not my o2 downloaded rom? Hopefully the developers will be able to spot whats going on and sort it out in the kitchen (hopefully removing what ever right protection the new rom installs).
Hope this helps, shout if you want me to test with a specific rom version (for uk / europe phones) and ill give it a whirl for ya
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
cruisin-thru said:
I think the "official" rom checks for versions, whereas the roms from the kitchen use a modified bit of code called "adaptrom" to fool the software. I wish I had a tenth of the capabilities of the guys on here that work out all this stuff.
Click to expand...
Click to collapse
I'm not sure about this, but i will give you some hint, ok :?
The T-Mobile Rom has a protection to it that you can not upgrade any ROM except T-Mobile ROM's other than that if you have a version of rom that is not T-Mobile ROM you can use the adaptrom to normally update any kind of ROM because adaptrom ignores the Version like PW10A1:007, the explanation of this versioning is in this forum(some kind of country and GSM band 1800/900, 1900/900).
Now why we have to use SD card after we update T-mobile ROMs, if we want to change to another kind of ROM's, because if we use "exe" or sometimes we called it "Program A" it checks the version of the ROM's, since the adaptrom can ignore only the version of the ROM's it can ignore the Type of ROM's, if it is T-Mobile or other ROM's, now for SD card it doesn't check for any version or type, and it goes directly to updating the ROM's in the Bootloader way or we can call it forcely updating the ROM'
s.
Hop this help.
Hi Guys,
I need your help .
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata"
and then
"ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
Stupidly, I haven't got a SD card. :evil:
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Qman said:
Read the above post that starts like:
"Ok I have found a roundabout method to resolve this only using the .EXE method"
HTH
Click to expand...
Click to collapse
Hi Qman,
No matter which ROM I cook, when I try to install it using the .EXE it gives me the message I posted before.
Would you explain to me, idiots guide, how to flash not using a .EXE?
or, have you got any sugestions?
Related
Hi All,
After a LOT of reading and mucking about, I've been able to update my ROM, get full use of GPRS and revert back to the manufacturer's ROM. There are a number of instructions, some of which are pretty dangerous. The following forum topic is the invaluable guide you need to read if you wish to revert back from a T-Mobile installation :
http://xda-developers.com/forum/viewtopic.php?t=3274
The place to get your ROM's is http://www.yorch.net, from the ROM Kitchen. Use the XDA Tools from the above forum link to burn ROM's you download from Yorch's onto your beloved XDA (use the .nb1 format, NOT the .exe method and burn using XDA Tools through your USB cradle).
I happen to have the 5.17 Wallaby bootloader which means that it will not let you simply whack in an SD card with a new O/S and burn off a backup ROM, it won't happen. Don't try to upgrade your Wallaby bootloader. The safest method is to use the Wallaby bootloader patch which can be downloaded from a link at the top of the forum topic link I posted above. That allows you to do a simple O/S restore from your SD card, providing you have an SD reader which presents your SD card as a new drive on your computer. The instructions are simple, just use xdrit as per the instructions in the forum topic link above.
So, from my experience I backed up my original ROM using XDA Tools and stored it on my hard disk in .nb1 format. I then downloaded the .nb1 for 4.00.16 and installed it using XDA Tools without a hitch. Everything worked fine, but I wasn't comfortable until I knew I could revert back to my original ROM. So my next step was to write the Wallaby Patch tool onto my SD card using xdrit using the instructions as laid out in the forum topic link above (take note, use the 1K header option in xdrit). The SD card reader I used was an X-Drive that you normally use for digital camera style stuff. Once written, I put the SD card in the XDA and did the bootloader boot (hold the power button whilst pressing the reset button), and was then given the option to press the Action key to go into the diagnostic mode which is where the patch program resides.
I then took the SD card out, leaving the diagnostic screen still open, put the card back into the X-Drive, formatted it using default options in Windows XP, then wrote the ROM backup I had (you can use any ROM here) onto the SD using xdrit, selecting the 3.5K header option (because we are still using Wallaby 5.17 regardless of patching). The last major step was to place the SD card back into the XDA and select Restore SD and accepted the risk notices. The restore appeared to go fine, but at the end it said Incorrect CRC. That in itself is a worry, but I had at least restored to a point where I could burn whatever ROM I like using the simple XDA Tools method, which is exactly what I did after reviewing the connection info (once more), going to 4.00.05.
Before I originally went to 4.00.16 I recorded all my connection details, including proxy info. When I went to 4.00.16 and re-entered all the gprs info, I found that the internet worked, but MSN Messenger would not connect, stating that the proxy info was incorrect - even though the values were exactly as originally setup. That was one major reason for wanting to go to another ROM. However when I ultimately got 4.00.05 on, I kept getting exactly the same error message with MSN Messenger. The answer came from a hint in another forum topic where someone (with AT&T I think it was) said not to put anything in the proxy info. That did the trick. Un-ticking the proxy option allowed the internet and MSN Messenger to work perfectly.
For Telstra GPRS (I think this is universal) the access point name is : telstra.wap.mnc001.mcc505.gprs
GPRS Authentication method is PAP authentication.
Hopefully this info might help someone out there, because I spent close on 8 hours sweating over trying to get my original ROM back up and running.
Oh yeah, thanks to the XDA Developers, Yorch and the whole XDA community. ROM updating really is easy when you've got the right info, and I can tell you it's really worth upgrading to PPC 2003 (WM2003?), it seems so much more stable, my GPRS has never stayed on as long and it's fun! You can get creative in the ROM kitchens (such as http://www.yorch.net), adding the software you like.
Just a piece of advice, search the threads for problems with any ROM you want to try out first so that you know the traps before it's having a party on your XDA at your sanity's expense.
I have some more observations now that I'm getting more comfortable with doing ROM updates. There are some advantages in going from the 4.00.05 ROM to 4.00.21, such as button lockout while off.
When I initially did the 4.00.21 upgrade I happened to go into the "band" option in phone settings and left the options unselected. Unfortunately setting this to nothing defaults to USA which is totally incompatible with Australia. The result was the phone would not synchronize and I could no longer go into phone settings. The fix for this scenario can be found in this thread : http://xda-developers.com/phpBB/viewtopic.php?t=2893&sid=1e7be62705d2831332c7f0bd5a75e364. It's standard stuff to the die-hards, the scariest thing in the world for us newbies.
Once you set the band for Australia (same as Europe - 900/1800 I think it is) you then get a signal, can synchronize and start customizing your settings. You can get rid of most of the T-Mobile garbage, so far everything is working fine.
Thanks for that buddy, i'm about to do the same downgrade tonight (once Yorch's kitchen is back working properly). You saved me many many hours of pain!
Thanks to all who add to these wonderful forums.
Steve
Just to keep this info updated for the Aussies (and same applies for Asians, and Europe too I think), basically the same applies for 4.01.00 as I explained for 4.00.21 further back. 4.01.00 seems much the same as 4.00.21 at the moment.
Hi guys,
I have a similar set-up as yours, ie I am in Australia nd I upgraded my rom to a 4.00.16. I would like to downgrade it to the original O2 one as I have to return the phone to my company (I am being made redundant).
I tried the method you described but I failed. Basically, I can write the patch on the SD card and when I put it back into the device nothing changes...
Could you please be more specific as to what you did ? Typically, did you switch off the device then put the card then stop/soft-reset or else ?
As well, I only have the NBF version of the O2 rom that I got from the update on their site. Do you think it works or should I try to find a "pure" NB1 rom (I think there's one on Yorch's website).
Thanks a lot in advance for your help.
Bob.
Hi Bob,
Sorry to hear you have to give up your XDA, hope you have replacement work for your redundancy.
Once you have written the Wallaby Patch onto the SD card using XDRIT you reset the device using the stylus and hold down the power button at the same time (with the SD card with the patch in place). That will load into bootload mode, and you press the action button at that point to actually go into the patch.
Once the patch has loaded you leave the device on, and remove the SD card, write your ROM image onto it using XDRIT, and place the SD card back into the phone. On the patch screen select "Restore from SD" using the little directional arrows button below the phone screen. It will then ask you to confirm, then you will see the progress - it takes about 5-7 minutes.
The details on how to write the patch and write ROM's are further up in this thread. I think you can use the NBF file but I am not certain. If you don't want to risk using an NBF you can use the same method above, but revert to the 3.17 ROM from Yorch, then you should be able to use the ROM upgrade from O2 to get a clean install of the manufacturer's ROM.
Let us know if you have any problems.
Thanks Mate.
I have tried once again to patch my Wallaby 5.17 (funny name, isn't it...). It failed. Once I go into the bootloader and press the OK button, I get to the diagnostics screen and nothing else is happening.
Could you shed some light on this ?
Thx.
Bob.
Re-reading your posts...
Would it be possible for you to send me the wallaby patch tool you used ? I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key.
Basically, even though I get the following message : "Successfully copied image of 514 blocks", after having chosen the 1k header, as it's explained in the very detailed post you mention, I still get to the diagnostics screen instead of the patch one...
Thx again in advance for any help.
Bob.[/img]
I tried the one from here (http://xda-developers.com/XDArit/wallaby-patch-tool.nb2), as is and renamed to nb0, but it seems to be the key
Click to expand...
Click to collapse
Hmm, I had no problem at all with the bootloader... one thing though is that you don't rename the .nb2 to .nb0, you use the file as-is. In XDARIT you should be able to select the .nb2 file to write to SD.
It is a diagnostics screen that you get to, that is the purpose of the patch. In that diagnostics screen should be options such as backup ROM to SD and restore ROM from SD. If it still doesn't work for you then maybe I should send you the versions of the patch and XDARIT that worked for me.
Hi,
I am using the O2 3.20.06 ENG ROM and 4.21.00 Radio. Do you think I can upgrade to 4.00.21 ROM directly?
Should I just run the exe file from the Yorch.net? Is it that simple?
What about the radio? Do I have to install a new one or is the 4.00.21 ROM included the radio?
Also, why people need to upgrade bootloader to higher version? I am using bootloader 5.15.
Thanks very much in advanced.
Well, I wouldn't use an exe for upgrading, and I wouldn't try upgrading the radio unless it's an official one posted by your supplier.
Use a .nb1 ROM from yorch and use XDA-TOOLS to do the ROM upgrade. Remember that if you go to a T-Mobile ROM you will need to use the SD card method to change to a different ROM.
Don't try upgrading your bootloader, 5.15 is fine. It's the higher versions that can be problematic and require the patch.
Thanks very much for your reply.
I am about to upgrade my device.
Just a few more questions,
1. Is this 4.00.21 ROM worked okay with the 4.21 Radio in Asia?
2. Also, other encounter a problem with SD card with this new 4.00.21 ROM, have you find any? (every 48 hrs the device wipe out the data in the SD card!)
3. It seems to me when using SD card method to change ROM with bootloader 5.15, the procedure is the same as upgrading or downgrading, isn't it?
4. The file from Yorch.net "upgrade" is only nbf file. It's not nb1. Is it the same?
Cheers,
Hi Chris
1. Yes, 4.00.21 does work fine with the 4.21 radio. I've touched on moving from 900/1900 to 900/1800 band if you should strike that problem.
2. Funny thing that, but I just checked and my SD card is erased after some 3 weeks of no problems.
3. Yes.
4. I do know that if you make a ROM in Yorch's kitchen you can choose .nb1. If you download an 'upgrade' I'm not quite sure what you get.
Not successful with the upgrade
Thanks so much for your reply.
From Yorch.net "upgrade", I can only get the 4.00.21 nbf file which is not nb1.
I can't use xdarit to burn that rom to SD card, an error occurred. But when I use the new OSImagetool, I can burn the ROM to the SD card and I can even change the name to nb1 file.
For both cases (nbf or nb1 file), I put the SD card in my device and press to the bootloading mode, nothing happen!
The device can't detect there is a ROM upgrade there. How can I do that?
Chris,
You need to download the .nb1 from the Rom Kitchen link on Yorch, not from the upgrades link, if all you are getting is a .nbf. With .nb1 you can use the osimage tool or xdrit with the sd method.
The bootloader will not restore from sd unless you have a correctly written image. In Yorch's kitchen you will see that .nbf is tagged for advanced users, that's a strong hint that different methods need to be used to install those.
I see....
Thanks v much.
Sorry for the delay in reply but I had gone back to Europe for Christmas.
I would be happy to use your wallaby patch file as mine doesn't seem to work. You can mail it to me on [email protected].
Thanks in advance for your help,
Bob.
Ok Bob, I'll send it in a few days when I get back to a PC. But I can guarantee it's the same patch that I linked back to in this thread.
I am trying to upgrade my Siemens SX56 to ROM 3.17 from Yorch.net,
I did the following:
1. Backed up the current ROM using OSImageTool.exe
2. Downloaded ROM 3.17 from Yorch.net in a .exe file format
3. Clicked on the downloaded .exe and I get the following error message:
Cannot find the ROM image to upgrade your Pocket PC. Please download and try again.
Please help, I am a newbie!
1st mistake...DONT USE AN EXE to upgrade. Use the sd card method. Otherwise you will be screwed.
When I select zipped NK.nb1 (SD-card flashing) I get the following error:
./mkrom.sh: ../../kitchen.local/mkrom-inc.sh: No such file or directoryno files for configid 26220739Cannot fit files in given sectionsError splitting files
:shock:
From what you posted it appears theres a problem within the Kitchen,
try back later!
HTH
Where else can I get 3.17 , the only kitchen I found was Yorch.net
Now the log shows:
adding: NK.nb1zip I/O error: No space left on device
zip error: Output file write failure (write error on zip file)
Click to expand...
Click to collapse
I'm guessing that the kitchen needs to have old results purged occasionally (possibly manually?).
Strange I used it earlier to get stock ROMs and I did all of them with no problem. Hmmm
jgalindo said:
Where else can I get 3.17 , the only kitchen I found was Yorch.net
Click to expand...
Click to collapse
You can use the XDA developers Special Edition ROM v1.2 its based on the same ROM.
XDA developers Special Edition ROM v1.2 can be found at:
http://cuba.calyx.nl/~jsummers/XDA/XDA-developers-SER-v12.exe
HTH
Ignore my last post. I went back and was able to cook a 4.00.16 ROM, so it's not a server disk space issue (like the error message made me think).
And I just cooked a 3.17.03 ROM. Guess it might be back.
Thanks a lot guys, I'm still trying with no success. :x
I just realized Vallerhum has the setup I want, I also have a Siemens SX56 on ATT. Where did you get your ROM?
I got it from Jeff's kitchen before it went south. I am trying to get my own up for I have all of the ROMs to date.
Is your phone also unlocked?
How can I get your ROM? I am going to another country on Friday and need to unlock it before then so I can show off to my friends
No my phone is not unlocked. I am not planning on changing companies anytime soon but if you want to unlock it...just load the 3.17 rom or if you have ppc2002 just install the xda unlocker and then install the ppc2003 rom of your choice. However, always use the sd card method, dont use an .exe.
I was able to cook a ROM! This site is great: http://www.zensay.com/qtek/ceupgrade.html
Thanks all for your help!
Now, I'm playing around with other stuff and seeing If my unlock was successfull.
That site is not a kitchen. It is for teaching how to do an SD card ROM upgrade. Where did you cook (or download) your ROM? Cooking is the customization of ROMs with other softwares.
I just want to check that this is correct since I'm new at this. I cooked a rom on xda.weblink.net and selected the t-mobile 4.01.16 rom and all the options i want and selected the .exe option. Then when I run the .exe and im about to click upgrade it says I will be upgrading to rom 3.16 (attached screenshot). i thought i was upgrading to 4.01.16?
Do not worry!
ignore the info and go ahead, you will get 4.01.16
after all the problems i've heard about, i wonder if i shouldnt just use the SD card method. This is my only phone and without it I am screwed! Does the SD card method update the radio like this one does?
The sd card method is used with the ce part of the rom, if your radio stack is working ok I suggest you leave it alone. I think the reason the screen says it is installing a different version is because it is patching code so the rom is accepted rather than being rejected because of a mismatch of country/rom/version etc.
i've heard that the radio stack for this version will increase gprs speed
Dear All,
I've tried to create a Wallaby Patch.nb2 for my Wallaby Bootloader 5.17.
I tried XDArit but failed with "Failed to open device \\.\PhysicalDisk23"
Can I do it with other tools such as OSImageTool?
Thanks in advance.
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Doi.Doi. said:
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I couldn't get into the bootloader any more. Hence, I did everything you say above e.g getting XDARit 1.0 and instruction from Negatong, however, XDARIT could't run on my computer. Every time I run it, I get the message: "XDA ROM Image Tool has encountered a problem and needs to close. We are sorry for the inconvenience".
Do you come up with any different solution? Tks
Doi.Doi. said:
Thanks goldendel. You are my man. Now I've finally entered the so called diagnostic mode and playing around with different ROMs!
Rgds.
goldendel said:
Hi Doi Doi,
I've been having exactly the same problems as you over the past 24 hours. The only way I could get the wallaby bootloader created was via XDArit 1.0 NOT 1.02. You can get XDArit 1.0 at http://www.yorch.net/downloads/xdarit1.exe. Follow the instructions from Negatong at http://forum.xda-developers.com/viewtopic.php?p=97306 to get the OS on your XDA back up and running. I think the reason why the upgrade failed originally is the same as me. The reason is posted on the homepage where you got the ROM from:
"Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM...."
When I got the .nb1 file for 3.17.03 from Lumpistefan, it was all good from there.
Good luck,
Tim
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I couldn't get into the bootloader any more. Hence, I did everything you say above e.g getting XDARit 1.0 and instruction from Negatong, however, XDARIT could't run on my computer. Every time I run it, I get the message: "XDA ROM Image Tool has encountered a problem and needs to close. We are sorry for the inconvenience".
Do you come up with any different solution? Tks
Hi Nghiem,
I haven't had this problem before. There are several posts about people not being able to get into the bootloader any more. By the sound of it, most people manage to get in eventually by constant hard reseting. Alternatively, you could try the bootload fixer if it's definately stuffed. I haven't tried this, but again, there are guidelines in the forum.
Good luck.
Tim
http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/
Doi.Doi. said:
http://lumpistefan.dyndns.org/tools/wallaby-patch-tool.nb2
other useful things,
http://lumpistefan.dyndns.org/tools/
Click to expand...
Click to collapse
Or all here:
ftp://xda:[email protected]/Wallaby/Tools/
and
http://wiki.xda-developers.com/index.php?pagename=Wallaby
Stefan
I have a Dopod C858 that is from China. It currently has the Chinese version of Windows Mobile 5.0 and I am looking for an English upgrade to Windows Mobile 6.0. I tried using the RUU for the HTC P4350 but it came up as a Model ID Error and I couldn't continue. I tried doing a CID Unlock using IMEI check but they don't support the Dopod C858. Does anyone have any ideas? Oh and one more thing. Currently, the Comm Manager on my Dopod does not have the WiFi option. I noticed after I did a hard reset that when it was loading the .cab for Comm Manager, it displayed something like no_wifi.cab. Did Dopod Asia purposely disable Wifi?
EDIT: I contacted IMEI Check and they helped me out by enabling my IMEI. My device is now supposedly "CID Unlocked."
QQ group 33128089
Any luck with finding this via QQ? I have the same need...
Here is what I did: I CID Unlocked my phone using IMEI Check and downloaded the DOPOD Rom file located here. After that follow these directions and you should have an english rom:
Tools you need:
==============- HexWorkshop from here
- the ROM of your choice
- Winzip or Winrar
- a valid UNL file for YOUR phone
Preparation:
===========a) install HexWorkshop and Winzip or Winrar on your pc
b) in explorer on pc, RIGHT click on the ROM of your choice and use:
"Extract files to folder ..." from conext menu Now it will unpack all
the
files
c) in the new folder you will have ONE file like "HRUU_signed.NBH"
(*.NBH)
RIGHT click on the .NBH file and use: "Hex Edit with Hex Workshop" from
context menu
d) You'll see on the 5th row HERA10000
==!!! make it HERA***** (5 stars) and save the file
e) Now RIGHT click on ROMUpdateUtility.exe and use: "Hex Edit with Hex
Workshop" from conext menu
Search for text "BsaD5SeoA" (without quotes, case sensitive)
OVERWRITE "BsaD5SeoA" with "IMEICHECK" (without quotes) and save the
file
ROM-Update:
==========
1) take SIM card and SD card OUT of the phone
2) Connect the phone running windows ce to the pc (normal way).
3) Completely Unlock your phone using our unlocker **
4) After phone is unlocked run unlocker (again) BUT when the unlocker
ask
for UNL file, remove the USB cable from the phone THEN press "Cancel"
on the
unlocker select file window (unlocker will close on PC). NOTE: The
screen on
the device will not show something usefull when in this mode. Most
probably
it is complete WHITE. !!THIS IS NORMAL!! Don't touch phone, let it like
it
is!
5) After you closed the unlocker, attach usb cable again (phone has
still
white screen)
6) start (the modified) ROMUpdateUtility.exe
7) when update finished and device started you will get a message:
"Data Crashed, contact service provider" (-*!NO PANIC!*-)
==Simply fix this problem by running the unlocker again and this time
select the key file normal way (full unlock process again).
The only problem is that the ROM is WM5 and there is still no Wifi.
Credit goes out to the IMEI-Check Team who provided me with the instructions!
Great, thanks for the info.
One question -- can you use the steps outlined to upgrade to WM6?
I was able to install WM6 before, using "aserg way", but the radio didn't work b/c the radio rom was not updated as part of the flashing process.
The way I understand it, if I can unlock my device and use the process you listed, I should be able to use a RRU which has an updated radio rom. After that, I should be able to sucessfully update to wm6.
What do u think?
I tried flashing a couple of WM6 roms but both of them didn't work. One stopped at 2% (Invalid Model ID) and the other one gave me an "Invalid Command." I currently have radio version 2.71.90, do you think it will work with WM6? If so, can u provide me with instructions on how to flash to WM6 using the aserg method?
Last time I tried upgrading to WM6, I found a cooked rom posted on this forum, and used 'aserg's' method to update it w/o updating the radio rom.
The method basically involves using a tool called 'awizard' along with a few other small utilities. The instructions should be easy to find on the forum here, let me know if you can't find them.
But before you do that, verify your radio is up to date. There is a minimum radio version you need to have (a search for radio rom on the windows mobile 6 forum should turn it up) before you can fully use a wm6 rom. The only known way to update the radio rom is to install an RRU package (which it seems like you've been able to do).
Currently, I'm waiting for my purchase & id to be validated with IMEI check.
Once that's done, I'll start with the steps you listed and try to get my radio rom up to date. After that, I'll select a rom, and do whatever it takes to get the rom installed.
I'll record all the steps I take as I do it, and post my results.
Don't worry -- I won't waste any time here, I've been waiting to update my device for a long time.
i'll be waiting right here. good luck!
oh and another thing, i am currently using this rom (ROM ver. 1.8.405.1). it gives you radio version 2.71.90.
It appears we need to find an RRU which includes a radio rom of 2.79 or higher.
We both currently have radio roms at 2.71.90, which is not good good enough for WM6.
I'm guessing we could use one of the posted upgrades (look in list of available official shipped rom's) and upgrade, even if we can't find one in english.
Afterwards we should be able to upgrade to wm6 of the appropriate langauge.
i read somewhere that one of the german ones has an updated radio rom. would you be volunteering to try first?
Yah, I found a few RRU's which contain a 2.79 version of the radio. I still need to wait for IMEI to verify me before I can continue with the process though.
btw... what time zone are you in? (I also bought my device in China, I live in Shanghai right now)
i'm in shanghai right now too!
i'm wondering if you can answer this for me. i don't know why some roms work and others don't. I currently have ROM version 1.8.405.1 WWE. Before that I successfully installed ROM version 1.7.707.3. I tried to install 5.4.405.1 but that didn't work. Am I supposed to install the updates in order of their release?
The order shouldn't matter. But, now I'm concerned -- because 5.4.405.1..etc is precisely the way to upgrdade to wm6 (since it has the 2.79 radio rom).
How did that update fail? Did you try updating after first unlocking your phone, or did your failure happen before you unlocked?
it gives me this after i try to upgrade: ERROR [300] : INVALID UPDATE TOOL
I've tried the steps you outlined above against several different roms... I get "invalid command" at 2% every time.
How frustrating... I'm guessing the steps IMEIcheck provided to update the 'updater' don't work with roms newer than a certain version.
Can you ask your contact there if they can provide updated steps which work with newer roms?
Seriously... i just paid like 40 bucks to unlock my phone.
I was _already_ running an english rom after flashing using aserg's way (an older htc wwe release), so I'm failing to see any advantage to having cid unlocked my phone.
I don't want to give up... I've already spent contless hours trying to figure out how to get past every minor error...
i'm in the same boat as you dude. this rom worked for me, but again, its version 1.8.405.1. None of the newer ones work. I just emailed my contact and i guess we can only wait and see what he can come up with. Another thing, have you enabled wifi on your device? I have a wifi button on my Comm Manager but when I tap it it tries to launch but then nothing happens. I read about a registry edit to fix this but my registry was different.