Related
:?:
Hi,
I have ordered a new QTEK9090, which the provider here will only supply me in French. I see conversions on this forum for German to English. However, is there one for Frnech to English?
Thanks
Not that i'm aware of, but the process is similar. You will just have to do a few extra steps, like putting Devicedata.exe on your device and retrieving the devicedata.txt file so you know the operator and "country" ID to use with xda3nbftool.exe.
No reason why it shouldn't work.
It should be the same conversion process. You'll need to dump the french ROM from your phone unlock it using the exact same commands, use a hex editor to see what the french ROM has for a carrier code (T-Mobile) and the designation to say that it is in French (i.e. WWE for english).
You will then modify the .bat file in the other posts that were listed for the German update.
********************8
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -so T-MOB101 -sl GER ms_.nba
xda3nbftool -so T-MOB101 -sl GER nk.nba
xda3nbftool -so T-MOB101 -sl GER radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
*****************
You'll want to modify the "T-MOB101" and "GER" settings to what you find in the first 128 bytes of the French ROM that you pull off the device to your SD card or PC. I have never dumped a ROM off of a device so you have to search this site for instructions, I know they have been posted multiple times. So to sum it up:
1. Dump the ROM from your French phone to your desktop
2. Use the command xda3nbftool -x nk.nbf nk.nba 0x20040521 to unlock the nk ROM
3. Use a hex editor to read the nk.nba file (XVI32.exe, search web)
4. Once you see what they have for the operator code and how they specify French (FRE???) you will then modify the above commands and save in a .bat
5. Run the .bat file you just saved
6. Run BaUpgradeUt.exe in you unzipped ROM directory.
Hope this helps.
I Just noticed that you’re a newbie. If you search the forum for "dumping ROMs to the SD card", "How do I get the ROM off my XDA/XDAII/MDAIII" , etc and forward me the links, I'll then do the processes on my end first so I know what I'm doing before I hold your hand. I can then walk you through the process to get the two unknown pieces of data, provider and the French 3 letter abbreviation. I'll do all the changes and upload a completed set of files for you to use to make it easy.
Deal? If so, start searching and PM with your results.
later,
Wnpublic,
Do you know how to dump from the device to the SD or desktop machine?
I don't know how to dump the "original" ROM. It appears to be possible, I just haven't explored.
BUT
dumping that rom to get country code and operator ID is unnecessary. All you need to do is put Devicedata.exe on your device and run it. That will create a small text file called Devicedata.txt. Open it and it shows the whole header - or at least enough of it to do the upgrade.
Devicedata.exe is part of the standard upgrade package. simply get the imate one, for instance, unzip it twice, and devicedata.exe will be there.
Thanks,
I had just realized this last night as I reading up on dumping the ROM. I had totally forgot about it, thanks for the reminder and making the complex simple!
I tried to upgrade my Tmobile MDA III with the ROM of O2 XDA IIs and it is now stuck in boot load. I was wanting to use the new rom to fix the bluetooth issues, But now I would just be happy if I can get it back to the factory defaults. This was the German flashed to English MDA III. If there is anyone who can help me Pleeeease! Thanks in advance to anyone who can reply or help.
Shaneframe
Mine is also stuck
Yeah this sucks ... i get error 101: connection error
Hi
RELEVANT TOOLS
XDAII USB Cradle
SD card with at least 32 MB memory (All data will be deleted during the process)
Multi-Port/USB TTY
PRE-PREPARATION
Backup all data on your device, because this process involves hard reset.
Kill ActiveSync (wcescomm.exe) by using task manager (Ctrl + Alt + Delete).
HERE WE GO
Go to bootloader mode (hold Power Button + Directional Pad + Reset Button)
Run Muti-Port/USB TTY (romupdate.exe)
bill gate u gave me my needed tip THANK A 100 no A 10000000 times
Billgate
Interesting I must say.
I was hoping that you might "please" spend so time and explain the Boot load for us all.
Unlike the extened rom were I have read enough about it and thus some what understand it, I have no understanding about the boot load on a PPC.
Would be nice of you, thanks
Reviving a dead MDAIII from Bootloader
I hear you brother! Thanks to XDADOM elsewhere on this website, I *finally* managed to revive my dead MDAIII tonight.
You will need this ROM PDA2k_WWE_12200_162_10600_SHIP.exe (lurking somewhere on this website), xda3nbftool.exe and I also had ActiveSync 3.8 which may help.
The process to update is described elsewhere on this website, but as it's easy to get lost, here's how I did it:
Double click on the EXE file. Just before the upgrade starts, hop into Windows Explorer and try to locate the file radio_.nbf which will be in a TEMP folder somewhere on your hard disk (usually c:\Documents and Settings\YOURNAME\Local Settings\Temp)
Copy/Move all of these files into somewhere safe and memorable.
Fire up Notepad and cut and paste the following text and SAVE IT AS A .BAT file (NOT a TXT!!). Then run the attached batch file.
-----------------------------------------------------------------------------
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 ms_.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 nk.nba
xda3nbftool -sd PH20B -sl WWE -so T-MOB005 radio_.nba
xda3nbftool -c -u NK.nba
xda3nbftool -c -u ms_.nba
xda3nbftool -c -u Radio_.nba
xda3nbftool -x ms_.nba ms_.nbf 0x20040522
xda3nbftool -x nk.nba nk.nbf 0x20040521
xda3nbftool -x radio_.nba radio_.nbf 0x20040523
del *.nba
---------------------------------------------------------------------------------
Now cancel out of the Update, then navigate back to where you just copied those files. Run the file BaUpgradeUt and hopefully your MDAIII should be back to factory settings as an "imate" after about 10-20 minutes.
Once again, THANK YOU to XDADOM for his time, patience and efforts in helping me out.
MB,
No problem buddie!
If anyone else has this problem with their Blue Angel device feel free to PM me and my "Team" (MDAIIIUser and I [and you too MB if you're up for it!]) will endevour to help you! (I think we need a name...like...the Blue Angels?!?!?)
We will also be starting a new thread with a full walkthrough to upgrading/restoring your device...this will hopefully include all the different country and languages codes for all the different types of Blue Angels....
Coming soon!
So, in the meantime, PM me and we'll see if we can help!
Dom
I have posted an Excel sheet on the ftp server describing the Byte Layout for the BlueAngel Extended ROM with a view to creating a file extractor / creator so that we can build our own ms_.nbf files.
Please note that in order to work on ANY of the ROM files for the BlueAngel you must first decode them using the following:
Code:
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
This results in producing three files with the same size and name but an nba extension. The ms_.nba file is the one we are concerned with at the moment, however if someone wishes to look at the nk.nba file it would be nice to be able to extract the base rom files directly as well.
The Excel sheet can be found here if you wish to have a play! There are some areas I am unsure of as yet and as such it is still a work in progress.
I have made a start at coding a fat file extractor but:
1) Have not been programming for some years now so it will probably take me until the XDA XVII comes out!
2) Hope that someone else has already written FAT16 file handling code and could help out!
Any help greatly appreciated.....
I have now created this as a Wiki Page which can be found here.
Dear all respected members of our forum,
Please anyone guide me the way to make the 48MB RAMDisk cab? :?:
Plus, please help me with the address to modify the RAMDisk size when editing the nk.nba. I tried to search but ant find it yet.
Thanks in advance for all your consideration!!!
Where are you guys, please anyone knows this help me?
i don't want to sound silly, but doesn't making a 48MB ramdisk lead to a zero paging pool... why would you want to have that?
raymonds said:
i don't want to sound silly, but doesn't making a 48MB ramdisk lead to a zero paging pool... why would you want to have that?
Click to expand...
Click to collapse
I think it wont lead to that bad thing. I just wanna make the RAMDisk storage larger by reducing the RAM available for running apps, not by taking away the pool paging part. I kinda think it would even improve the apps speed, rather than running apps from ROM.
This's the ideal configuration for me: 16MB Pool paging+ 64MB RAM(decrease from 80MB: says about 77.17 in device information) + 48MB RAMDisk. Am I right? Please help me if you know how to make the 48MB RAMDisk driver cab file, and the address to adjust the amount of RAM in the nk.nba file.
Thanks and sorry for my bad English!
Hiya,
Modify the following addresses in nk.nba :-
207C14: -> 95
207C15: -> 24
207C18: -> 50
And change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
thingonaspring said:
Hiya,
Modify the following addresses in nk.nba :-
207C14: -> 95
207C15: -> 24
207C18: -> 50
And change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
Click to expand...
Click to collapse
Thanks a lot for your help, I'll go try it right now.
BTW, Do the addresses differ from each BA WM5 ROM version? Just in case there's new AKU 3.4 based-ROM released.
thingonaspring said:
Hiya,
Modify the following addresses in nk.nba :-
207C14: -> 95
207C15: -> 24
207C18: -> 50
And change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
Click to expand...
Click to collapse
just wondering if u could tel lme how to include that registry setting direct into nk.nba?
thanks
thingonaspring said:
Hiya,
Modify the following addresses in nk.nba :-
207C14: -> 95
207C15: -> 24
207C18: -> 50
And change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
Click to expand...
Click to collapse
Dear friend similar nk.nba modification for Himalaya pleeeease?????
@nhtmax
Upgrading to a newer AKU version won't change those addresses.
>how to apply to nk.nba
Lots of ways to do this - in order of difficulty :-
Easy - Manually edit the two registry settings after you've got the device up and running.
Less easy - use the ROM Kitchen to build your own ROM with those settings.
Really fiddly - dump the nk.nba file out to a bunch of files, decode the registry, edit the registry, encode the registry, add registry back into the IMGFS filesystem, rebuild the rom, re-encrypt the rom.
@c_shekhar
I'm sorry dude I have no idea about Hima. No device to test on.
Buzzdev.net is by far the best place to look.
@thingonaspring
Thanks a lot for yor help mate, I've just edited my ROM to have 48MB RAMdisk, and feel the speed really really fast+ more space.
@c_shekhar
If you want to have your Hima WM5 ROM with 48M RAMDisk, just do these following steps:
1) Convert the nk.nbf into nk.nba using xda2nnbftool.exe, command line should be like this: xda2nbftool -x NK.nbf NK.nba 0x20040304
2) Use some hex editor, search for address :
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 08 ( if you have full 128MB RAM version: no RAMdisk)
-> change the value to:
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 06 --> 96 MB program memory: RAMdisk= 32MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 04 --> 64 MB program memory: RAMdisk= 64MB
-> save the edited nk.nba.
3) Now you have the ROM version with your like RAMdisk preserved. Next thing to do is dump the nk.nba using Hima ROM kitchen (read for more in our forum) edit the default.hv inside the dump folder.
Change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
Re-buid the dump folder to have the nk.nba. Then type these command lines:
xda2nbftool -c -u NK.nba
xda2nbftool -x NK.nba NK.nbf 0x20040304
Now you have your 48MB RAMdisk ROM version ready for upgrading.
Thanks bro for the help. I am already using the AKU 3.2 ROM cooking. In this case I think I have do as follows:--
1. Put the registry values you have metioned above in the \DEV\OEM\ROM_Himalaya_v1.50_3.00a.64\0ffd60e6-162d-4643-850c-58fcc4e34579.rgu
2. Edit the \DEV\ROM\NK.nba using hex editor for substituting the values you have mentioned.
If you think I have understood correctly kindly endorse this in your reply post. Thanks once again...
@c_shekhar
You're on the right track bro. Just adjust both the nk.nba addresses and registry to have wished space of RAMdisk. Just do those steps to make your ROM.
But, one thing, I'm really sorry for my mistake as here:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
The above values are ONLY for 48MB RAMdisk version.
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 08 ( if you have full 128MB RAM version: no RAMdisk)
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 06 --> 96 MB program memory: RAMdisk= 32MB
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 04 --> 64 MB program memory: RAMdisk= 64MB
To have 48MB RAMdisk, change above value in the nk.nba to:
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 05 --> 80MB program memory: RAMdisk= 48MB
and the registry to the mentioned values.
Thanks bro a lot.
one more question nht_max
With RAMDisk of 48MB how big shall be the page pool size in Himalaya?? I mean would it change automatically or shall I have to make some other changes in the NK.nbf for changing the page pool size????
c_shekhar said:
one more question nht_max
With RAMDisk of 48MB how big shall be the page pool size in Himalaya?? I mean would it change automatically or shall I have to make some other changes in the NK.nbf for changing the page pool size????
Click to expand...
Click to collapse
Of course you have to change it manually If you want to have page pool size. The change's easy, just like what I'd just done on my BA. :wink:
You just have to edit some addresses in the nk.nba(not nk.nbf). At the time I had Hima, there was nothing called page pool size revealed, so I dont know about this on Hima bro :?
If you really want to increase its size, try to look for those addresses in the Hima threads.
how to modify BA ramdisk
hi,
I found the beneath mentioned addresses, in the hex editor, but dont know where i should be entering the "95", "24" and "50". please advise.
Also, i already have a 32 mb pagepool. can i have a 32 mb ramdisk? what according to the experts out here is the best config, for storage, programs, ramdisk and pagepool?
Thanks and regards,
Francis.
thingonaspring said:
Hiya,
Modify the following addresses in nk.nba :-
207C14: -> 95
207C15: -> 24
207C18: -> 50
And change the following 2 registry entries :-
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RAMDisk]
"Size"=dword:3000000
"Address"=dword:95000000
Click to expand...
Click to collapse
can someone please tell me what's the practical use of a ramdisk in a mobile phone
and how do you utilize it?
because i find it unpractical to have, since it's already mobile and BA already is a volatile unit, which tends to reset from time to time.
Stolen from udk's Jade Dumping thread
First all, thanks to Pof, here his original thread and cmonex for her orginal post here.
Download itsme's utils: http://nah6.com/~itsme/itsutilsbin-20080923.zip
List NAND Partitions
Code:
pdocread.exe -l
210.38M (0xd260000) [COLOR="DarkOrchid"]FLASHDR[/COLOR]
| 3.12M ([COLOR=DarkRed][B]0x31f000[/B][/COLOR]) Part00
| 3.50M ([COLOR=DarkOrange][B]0x380000[/B][/COLOR]) Part01
| 69.38M ([COLOR=Olive][B]0x4560000[/B][/COLOR]) Part02
| 134.38M ([COLOR=Teal][B]0x8660000[/B][/COLOR]) Part03
STRG handles:
handle e7489c1a134.38M (0x8660000)
handle 474960e6 69.38M (0x4560000)
handle c74b0fda 3.50M (0x380000)
handle 074b0eee 3.12M (0x31f000)
disk e7489c1a
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 474960e6
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk c74b0fda
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074b0eee
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Dump Them!
Code:
pdocread -w -d [COLOR="DarkOrchid"]FLASHDR [/COLOR]-b 0x800 -p Part00 0 [COLOR=DarkRed][B]0x31f000[/B][/COLOR] Part00.raw
pdocread -w -d [COLOR="DarkOrchid"]FLASHDR [/COLOR]-b 0x800 -p Part01 0 [COLOR=DarkOrange][B]0x380000[/B][/COLOR] Part01.raw
pdocread -w -d [COLOR="DarkOrchid"]FLASHDR [/COLOR]-b 0x800 -p Part02 0 [COLOR=Olive][B]0x4560000[/B][/COLOR] Part02.raw
pdocread -w -d [COLOR="DarkOrchid"]FLASHDR [/COLOR]-b 0x800 -p Part03 0 [COLOR=Teal][B]0x8660000[/B][/COLOR] Part03.raw
The most important files are part01 (XIP) and part02 (ROM).
Dumping the SPL
Code:
pmemdump 0x9a000000 0x80000 spl.nb
As monx points out below you may need to "App Unlock" your device before pdocread will work.
Either follow his reg hack, or just use this CAB by Chainfire : http://forum.xda-developers.com/showthread.php?p=3973249#post3973249.
Have fun.
Thanks to d474rpr for testing SPL dumping
Dave
For those interested here is the extracted SPL from the Rhodium.
Rhodium SPL
enjoy!
Just an additional info. need to apply this reg :
[HKEY_LOCAL_MACHINE\Security\Policies\Policies]
"0000101a"=dword:1
"00001001"=dword:1
(Dumping with Vista SP2 x64 + WMDC6.1 with virgin Rhodium )
EDIT: Done. Will upload in case somebody want it.
Okay here is RHODIUM_WWE_ASIA_v1.19.707.1(51489)_051509_OEM_FULL
DaveShaw said:
Dump Them!
Code:
pdocread -w -d FLASHDR -b 0x800 -p Part00 0 [COLOR=DarkRed][B]0x31f000[/B][/COLOR] Part00.raw
pdocread -w -d FLASHDR -b 0x800 -p Part01 0 [COLOR=DarkOrange][B]0x380000[/B][/COLOR] Part01.raw
pdocread -w -d FLASHDR -b 0x800 -p Part02 0 [COLOR=Olive][B]0x4560000[/B][/COLOR] Part02.raw
pdocread -w -d FLASHDR -b 0x800 -p Part03 0 [COLOR=Teal][B]0x8660000[/B][/COLOR] Part03.raw
The most important files are part01 (XIP) and part02 (ROM).
Click to expand...
Click to collapse
I assume it's a stupid question - but I need to change the storage adresses according to the list of the NAND Partitions?
Thank you
CHfish
yes. follow the address shown in ur prompt windows.
monx® said:
yes. follow the address shown in ur prompt windows.
Click to expand...
Click to collapse
Thank you monx® - faster then all support hotlines
@monx:
I have a Hong Kong CHT version of the Rhodium that I would like to switch to WWE. Can I use the RHODIUM_WWE_ASIA_v1.19.707.1(51489)_051509_OEM_FULL dump you provided to do so? If so, how?
Or is there an RUU package that I can use?
Pardon my ignorance...this is my first WinMo device and I'm still learning...
@e60202
Hi friend, my dump is not a complete rom (it is just rom sources to share)
Yes, we can rebuild the rom becomes the complete one but it wont have the required signature required by stock device SPL. So, we cant flash it until our device is flashed with Rhodium HardSPL (not available yet)
To change your device rom language, it is possible. U need to create GoldCard using QMAT (if i'm not mistaken u hv to buy this for full function to create GoldCard) & Mtty. Then u can flash stock shipped (signed) WWE rom.
For more info, pls search for GoldCard or u can try ur luck to ask for cmonex further help
so i take it then... if i do a rom/spl backup of my phone and then bugger it up, i'm unable to flash the backup back to the phone ?
drawflex said:
so i take it then... if i do a rom/spl backup of my phone and then bugger it up, i'm unable to flash the backup back to the phone ?
Click to expand...
Click to collapse
If you bugger up your phone, just Hard Reset to get it back to how it was.
You dump your ROM so that after flashing custom ROMs you can go back the one your phone came with. But we need Hard SPL to flash custom ROMs as well as dumped ones.
Dave
is there actually no problem in warranty? flash new rom .. **** it up.. flash original rom.. send it in
-adrian- said:
is there actually no problem in warranty? flash new rom .. **** it up.. flash original rom.. send it in
Click to expand...
Click to collapse
Re-flash original SPL so they dunno u hv modified it
well .. never tried it before .. hope it will work with the tmobile GER branded phone
already ordered.
monx® said:
Re-flash original SPL so they dunno u hv modified it
Click to expand...
Click to collapse
Doesn't this only work though if you have a signed ROM installed. I didn't think that you could use HardSPL to install a dump and then push the OEM SPL back.
Okay here is RHODIUM_GER_v1.19.407.0(51489)_051609_OEM_FULL
the German Version
wootty2000 said:
Doesn't this only work though if you have a signed ROM installed. I didn't think that you could use HardSPL to install a dump and then push the OEM SPL back.
Click to expand...
Click to collapse
yes, you can use HardSPL to do this! (when it comes out )
cmonex said:
yes, you can use HardSPL to do this! (when it comes out )
Click to expand...
Click to collapse
I know that with HardSPL I can install a cooked ROM, but my understanding is that if I install HardSPL, then a cooked ROM and then push the OEM SPL back, the OEM SPL will fail to validate the cooked ROM and refuse to boot it
Or does the OEM SPL only do validation when flashing and not booting?
wootty2000 said:
I know that with HardSPL I can install a cooked ROM, but my understanding is that if I install HardSPL, then a cooked ROM and then push the OEM SPL back, the OEM SPL will fail to validate the cooked ROM and refuse to boot it
Or does the OEM SPL only do validation when flashing and not booting?
Click to expand...
Click to collapse
No, if you have a cooked ROM and a stock SPL it will still boot. The SPL checks signing, device id, model id, etc when attempting to flash a ROM, not booting.
Dave
I already dumped the ROM/SPL of my Rhodium according to DAVE's guide.
And I know from the guide the Part01.raw is XIP and the Part02.raw is ROM. However, what's the part00.raw and part03.raw?
And how can I put all of these raw files together to a NBH file? It's need to be NBH file before flash back, am I right?