Related
is there anyway to do that?? thanks!!
I need to know the answer too.
My O2XDA has a boot loader version v5.17 which does not be flahsed using wallabyrom151.exe.
I have the following accessaries:
1. USB cable
2. 32Mb MMC card
How can I downgrade the boot loader from 5.17 to 5.15? Thanks!
Go to the rom image tools setction of this web site for more details.
You need 2 SD card to flash the new bootrom on your machine.
1 card is for writing the wallaby patch tool to boot up the XDA, other is to write the rom image.
Moreover, you need someone send you a 5.15 rom. By the way, the 5.22 bootrom come with some version (4.00.01?) do not have the protect at all. You can use that version.
I have had no joy with the wallaby patch on my O2 XDA with bootloader 5.17 the file loads to the SD card no problem but when I start up the bootloader the patching process described does not take place. I note in one of the other forums that a new XDArit version is due out soon. Can one of the developers kindly look at the patch tool at the same time please as I have inadvertantly (Read careless) produced a Rom with MKRom to large for my XDA which has renedered the device inoperable and my only chance of recovering it is if I can overcome the security inbuilt into the bootloader. Developers may be interested to know that the USB flash mode can be comunicated with via HTC's Multiport/USB TTY utility but the only commands I can get to work (Theres no help on this one) is the load command which looks back to the SD card and same problem.
Richard
Richjn : Did you chose a correct header when you write the patch tool?
Hi
Have tried both 1k and 3.5k header no joy with either I'm afraid.
Richard
killercheung said:
Moreover, you need someone send you a 5.15 rom. By the way, the 5.22 bootrom come with some version (4.00.01?) do not have the protect at all. You can use that version.
Click to expand...
Click to collapse
I have another device with bootloader 5.15, can I just dump it out?
Where can I get the 5.22 bootrom?[/quote]
Richjn said:
Hi
Have tried both 1k and 3.5k header no joy with either I'm afraid.
Richard
Click to expand...
Click to collapse
Same here, i've tried to write the wallaby patch using 1k header, xdarit return "successfully write 2 blokcs of data", but in fact, nothing is written to the SD card (from the hex dump of xdarit).
chiuhing said:
killercheung said:
Moreover, you need someone send you a 5.15 rom. By the way, the 5.22 bootrom come with some version (4.00.01?) do not have the protect at all. You can use that version.
Click to expand...
Click to collapse
I have another device with bootloader 5.15, can I just dump it out?
Where can I get the 5.22 bootrom?
Click to expand...
Click to collapse
[/quote]
chiu heng, can i have the 5.15 bootloader please?? I need it..its much user friendly then 5.17, that what i think
are you sure you have a wallaby patch loader image?
you can find the latest version here
http://www.xs4all.nl/~itsme/download/wallabypatch-sd.nb2
chiuhing said:
killercheung said:
Moreover, you need someone send you a 5.15 rom. By the way, the 5.22 bootrom come with some version (4.00.01?) do not have the protect at all. You can use that version.
Click to expand...
Click to collapse
I have another device with bootloader 5.15, can I just dump it out?
Where can I get the 5.22 bootrom?
Click to expand...
Click to collapse
[/quote]
You can. See the "Wallaby Bootloader" of this site for more information.
As I know the original 4.00.01 WM 2003 rom come with the 5.22 bootloader.
XDA developer Itsme said:
are you sure you have a wallaby patch loader image?
you can find the latest version here
http://www.xs4all.nl/~itsme/download/wallabypatch-sd.nb2
Click to expand...
Click to collapse
It can be written on the SD either. Do I need to include the bootloader image when preparing the diagnotisic SD card?
chiuhing said:
XDA developer Itsme said:
are you sure you have a wallaby patch loader image?
you can find the latest version here
http://www.xs4all.nl/~itsme/download/wallabypatch-sd.nb2
Click to expand...
Click to collapse
It can be written on the SD either. Do I need to include the bootloader image when preparing the diagnotisic SD card?
Click to expand...
Click to collapse
sorry... typo... I mean it can't be written to the SD card.
How to change o2's language?
Dear Sir
I managed to make pach diagnostic card, I do have Chinese rom card ready made from a O2 unit. But no luck on flashing English O2 with 5.17 os.
Thanks!
How to change o2's language?
Dear Sir
I managed to make pach diagnostic card, I do have Chinese rom card ready made from a O2 unit. But no luck on flashing English O2 with 5.17 os.
Thanks!
How to flash English O2 into Chinese O2?
Dear Sirs
I do have both machines and I managed to make the pach diagnostic card, I do have Chinese rom card ready made from a Chinese O2 unit. But no luck on flashing English O2 with 5.17 os. It simply returns to the choices screen after I hit action key to start flashing.
Thanks!
It simply returns to the choices screen after I hit action key to start flashing
Click to expand...
Click to collapse
That means you have not written the ROM image to the SD card correctly. Check the header size...
I used XDATools to downgrade my bootloader from 6.22 to 5.15...
http://xda-developers.com/XDAtools/
If you install the tool, there will be 2 programs: "Fix broken bootloader" and "OSImageTool"
Use the first one to downgrade your bootloader. It can downgrade from any version, you name it... 5.17, 6.22, etc
good luck
ebswift said:
It simply returns to the choices screen after I hit action key to start flashing
Click to expand...
Click to collapse
That means you have not written the ROM image to the SD card correctly. Check the header size...
Click to expand...
Click to collapse
1.How to check header size in plain English? I do not know how to jude the size.
2.Same card backed up from Chinese O2 can flash Chinese O2 but not the English O2. So writing has been done, just not sutable for language change.
I am having the same problem here and I tried again and again using the same steps as ebswift (thnaks a lot by the way) but I can't get anything else than the diagnostics screen.
If anyone knows of another method to write on SD cards other than using xdarit and the wallaby patch, I will be extremely grateful.
Bob.
My USB connection dropped out while doing loaiding a new ROM. Problem is I now have a XDA hanging in the % Restore screen.
I have bootloader 5.17 so I understand I need to do create an SD image with the Wallaby Patch Tool.
I am using the latest XDA RomImage tool to try and create an aimage
I understand I need to build a ROM from Jeffs Kitchen all my other are .exe's Problem is RomKitchen is down at present. Anyone know where I can get a *.nb1 image from???
I am also unable to burn the Wallaby Patch tool to the SD. Everytime I try it says. I am told cant open physical device. Any guesses. What can I do/
Use the full version 1.39MB of XDArit.exe you fool
Yes use the full version 1.39mb version not the 180k version if u are unanble to copy to the SD and are getting the can't copy to physicaldrive//./diskX.
Now just to get a nb file not exe
Can get Wallaby Patch Diagnostic to work but!
I can burn the Wallaby Patch tool and get the Diagnostic screen with the restore option to appear but restore does not work. I burn this to my 8mb SD
Screen Looks like the following
Wallaby Patch
Tool 1.2/51.17
-----------------
Boot -> SD
CE -> SD
Boot+CE -> SD
Restore SD
About
Exit
Any 1 got any ideas. I have downloaded a NK.nb1 file and burn to my other SD 128mb but when I hit return it goes back to main window again. What am I not doing right.
Confirming you're selecting "Restore SD"?
Also what ROM version are you looking for/need?
All is now cool
Qman - Everything now working. 1 very happy man I am. I was selecting restore but it was just going back to the main menu - Rom issue. I also upgraded to Wallaby Patch Tool 1.4 but I don't think it made any difference.
Jeffs Kitchen was down yesterday so I got an nb1 file from somewhere off of this site. Something wrong the ROM but I had no choice
Today I downloaded JeffsKitchen Roms and everything now works.
Started at 3.00.17 now onto 4.00.11. All is good
1 thing I tried today is burning the rom header with the 3.5k radio button checked. This works. I believe things don't work if you select the 1k radio button.
Many posts I have read to get to this point and about a day of fiddling around. I have learned heaps in getting my machine operating again. To anyone who reads this post and has problems with their machine, keep reading its all out there.
Hi,,
Where can I get the full version ?
I have the same problem for 2 years :l
Grtzzz Alex
Digital Cameras question: Can you recover images from a sd card when it says
unrecognized file format? Yes it is possible, so don't delete the images just
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.
Hi,
I have a problem with an installed ROM but I can't use activesync to update the ROM image.
I have tried using the OSImage tool to transfer the rom to the SD card in the XDA but nothing appears to be there when I reboot. I get the Wallaby boot screen and GSM OK, but no option to lead the image. What can I do.
When I try to read the card after copying the image there appears to be nothing on it.
Thanks in advance,
Dale.
if you did it right
the sd card reader should not even be able to read the card
at all
When you are in the Bootloader. Which version is shown in there?
You can try making a backup of the current ROM on the SD Card and retry entering bootloader. Than there should be the screen if you want to download the new ROM on the card. This will show if flashing in generally will work....
Stefan
LumpiStefan said:
When you are in the Bootloader. Which version is shown in there?
You can try making a backup of the current ROM on the SD Card and retry entering bootloader. Than there should be the screen if you want to download the new ROM on the card. This will show if flashing in generally will work....
Stefan
Click to expand...
Click to collapse
Version is 5.17.
From the Wallaby bootloader I am unable to save the ROM to the card. It keeps giving me the error "CARD Key Invalid"
Where do I go from here?
Dale.
You have to change your Bootloader....
Take a look here:
http://forum.xda-developers.com/viewtopic.php?t=29476&highlight=bootloader+5+17+patch
Stefan
LumpiStefan said:
You have to change your Bootloader....
Take a look here:
http://forum.xda-developers.com/viewtopic.php?t=29476&highlight=bootloader+5+17+patch
Stefan
Click to expand...
Click to collapse
Thanks for that.
Unfortunately I get the following error when i try to downgrade the bootloader.
C:\XDATools>pnewbootloader bootloader_v5_15.nb0
ERROR: Unable to open target/WinCE file - Returned by WSARecv or WSARecvFr
indicate the remote party has initiated a graceful shutdown sequence.
ERROR: ITReadProcessMemory - Returned by WSARecv or WSARecvFrom to indicat
remote party has initiated a graceful shutdown sequence.
Unable to find flash info offset, cannot disable bootloader writeprotect
I get a simmilar error when i try to upgrade or downgrade the ROM via activesync Program A.
What can I do about this?
Dale.
After a bit of fiddling I no longer get the first part of the error, but still get the following:
"Unable to find flash info offset, cannot disable bootloader writeprotect"
So, what can I do to overcome this problem?
Dale.
Just bricked my phone, i need the original shipped rom... It's a Dutch one, 1.8.404.1.nld.. Or could someone make a dump?? thnx!!
The Dutchman said:
Just bricked my phone, i need the original shipped rom... It's a Dutch one, 1.8.404.1.nld.. Or could someone make a dump?? thnx!!
Click to expand...
Click to collapse
A dump wouldn´t work with the RUU - so you need an official RUU update. Sorry.
Thinking of it.. I tried to upgrade the OS with awizard, but accidentally opened Upgrade_extrom.bat, but i did not perform these steps: (because I did not know I accidentally opened the extrom upgrade stuff):
4. Start !pdocread-L.bat.
-will be generated pdocread-l.txt
-find a line of type xxxxxxxx 9.99M (0x9fd800), where xxxxxxxx ExtRom.
5. Start !Upgrade_ExtRom.bat xxxxxxxx
So I guess I need to Upgrade the extrom to my previous extrom.. I've read that i could update the the OS with the nbh file on SD card, but can I update the ExtRom with a file on my SD card in bootloader mode (since my device is stuck on splash screen, i'm only able to get into bootloader mode)
Really need some help on this.. thnx!
The Dutchman said:
Thinking of it.. I tried to upgrade the OS with awizard, but accidentally opened Upgrade_extrom.bat, but i did not perform these steps: (because I did not know I accidentally opened the extrom upgrade stuff):
4. Start !pdocread-L.bat.
-will be generated pdocread-l.txt
-find a line of type xxxxxxxx 9.99M (0x9fd800), where xxxxxxxx ExtRom.
5. Start !Upgrade_ExtRom.bat xxxxxxxx
So I guess I need to Upgrade the extrom to my previous extrom.. I've read that i could update the the OS with the nbh file on SD card, but can I update the ExtRom with a file on my SD card in bootloader mode (since my device is stuck on splash screen, i'm only able to get into bootloader mode)
Really need some help on this.. thnx!
Click to expand...
Click to collapse
NO - you cannot flash OS.nbh by SDcard. It might be a possibility but i din´t get it managed