Database Develop

newbie killed XDA III

This is a story from my friend - he does not speak english at all, so he totally killed his XDA III.
He tried to flash VPA III German from Vodafone to English language.
Here is Device Data.
PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00
Then he downloaded Qtek WWE update and began to flash after preparing with following bat file.
xda3nbftool -x ms_.nbf ms_.nba 0x20040522
xda3nbftool -x nk.nbf nk.nba 0x20040521
xda3nbftool -x radio_.nbf radio_.nba 0x20040523
xda3nbftool -sd PH20B2 -sl GER -so VODAP102 ms_.nba
xda3nbftool -sd PH20B2 -sl GER -so VODAP102 nk.nba
xda3nbftool -sd PH20B2 -sl GER -so VODAP102 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
But the update hang on 10 percent of radio and did not continue. All his ideas to restart and continue had no success.
So he decided to delete radio file from update folder and restart the update process, because VPA simply hand in bootloader mode.
After update the device ran crazy, because he showed WWE version during the load but all error messages ran out in German.
Radio Worked!!! He tried to make a telephone call.
Then he decided to restart the whole update, but radio update began and stopped at 10 percent again.
So he flashed the device again without radio and then put in the folder a radio file from german T-Mob update. This time he flashed the device successfully, but during the load it shows NO GSM and D 1.22.00 WWE
Now we are in total sh... because GSM not working and still no effect in flashing.
The bootloader version is 2.07 and we only have working Qtek with 2.06 version, so SD backup will not help. Please help! Please!

Can you get the Device data TXT
PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00
From an original Russian phone.

It was not original Russian Phone. It was VPA III form Vodaphone, but without Sim-lock

Then you have the info you should need.
Read :
http://wiki.xda-developers.com/index.php?pagename=BA_GettingStarted
Just REMEMBER to be aware that if you get any warnings in the DOS window When running the xda3nbftool you must delete that ROM and try on a new copy. Running the xda3nbftool twice on the same ROM can produce errors without warnings!!
When you understand the consept descriped on that page, move on to getting the newest rom avalible that also works with the xda3nbftool
http://wiki.xda-developers.com/index.php?pagename=BA_RomKitchen

Thinking about extended ROM is not very actual now. I'll try to read all materials on Wiki, but the problem is that during this updates device data could change and I can not get the new version of this file now.

One of the headlines say "Based on I-Mate 1.22.162 WWE and I-Mate Arabic 1.31.112 WWE"
I werent thinking Ext. Rom. you have no need for that right now

I wanna say that I really appreciate your help.
Now I can describe situation in following points.
1. Device is after strange flashing of widely discussed Qtek ROM
2. I can't get devicedata.txt, because now I have strange mix of English and German langeages in system. (Something like German version with English interface - it is even hard to explain).
3. No GSM during booting.
I really have no ideas except trying to guess the combination of model, country code and operator.

Do you have the DeviceData.txt from befor you starting messing with it?
Otherwise try looking looking at this page http://wiki.xda-developers.com/index.php?pagename=BA_Versions

Well, I have such file before all upgrades. It is listed in the first post. But now I have kind of WWE Rom installed (I think so, because it is showed in red during the boot).

Ok, so if you try to make a new DeviceData.txt, what does it say ?
I suppose this is the original deviceDate :
PH20B2 B 2 GER R VODAP102 1.22.01 0 1 1.22.163 1.06.00 06.00
Correct?

I can not put GetDevicedata.exe to device, because I can not connect via ActiveSync, can not access File Explorer or Storage card because of this awful mix of languages. The only think I can do - launch applications from Today screen. They launch in German though.

You really ****ed this one up. Well i can only hope that the device data on it is still the same.
Now i'm absolutly no expert on this ROM switching, just did it once for kicks, but hang on a sek. and ill try and look at the 131.Base version to se if we can get that installed on your device.

In my humble opinion it was changed... I can suppose this, because fix.bat listed does not work now. And I can not even imagine the "radio" section of such file because of "NO GSM" presented.
p.s. Are there some "Flashers" devices in maintanance centers? Maybe they can help me... Of course it will not be easy to find such centers in Russia, so I hope that we can manage this situation at home.

Im have uploadet a file you should be able to use.
Unpack and run the BaUpgradeUt.exe file.
If your device data hassent change in your friends desperate attempt to update it, it should work.
There is no Radio incluced cause i keep getting Password errors on all those i find.
You can try and run the the upgrade i made, edit and delete the files you dont need in the ext. rom after installation, hard reset it, and you should be running, without radio that is.
Now i dont have all that much time, but look through the wiki and find a radio you can flash onto it. Same procces as everything else, just without the nk and ms files.
ftp://xda:[email protected]/emergency
As far as i know this is a WWE Rom, and all the Arabic customation is in the ext. rom.
Please note that you install this on your own request and risk, and that i take no responsobility on the outcoming result!

Thank you so much in advance. I'll try to flash it today.

I get the same country ID error.
No-No-45-45-N
It means that devicedata changed. But can yous guess the new data?
I think that new device ID shoud correspond to flashed ROM, because it was flashed twice. Maybe WWE language and BRIGH001 are the new country identificators. What about the model?
And I want to return to the idea of SD dump. Is it possible to do such trick?

Well, I tride to decode this files to following combinations
PH20B WWE BRIGH001 and PH20B2 WWE BRIGH001
Only country ID error

Tried all the combination of identificators
PH20B and PH20B2
VODAP102 and BRIGH001
WWE and GER
country id all the way.
I am beginning to loose my last hope. I feel even pain to look at it. It is alive, bootloader is alive and no way to save it...

It sounds like the first atempt succesfully wiped the DeviceData, and the second attempt wrote new DeviceData.
I heard someone in here have a similar senario, he just succeded installing the faulty DeviceData ROM.
Well first pull of the battery and look at at the silver sticker, in the upper left corner is the device Model/Number PH...... check that number against the number you gave me as the original number.
Which ROM was it he tried to install, The excact name as it's found on the ftp server.

Oh, and do remember to only use the xda3nbftool.exe once on the same ROM. If it dont work, erase that ROM and try on a new copy!!

Upgrade problem

Hi there,
I have prolem with upgrading my BA.
I upgraded my BA to WM 2005. But this version isn't suitable for my. I would like to return to my previous ROM, or change ROM to HEMI...
I downloaded HEMI ROM and I started upgrade utility..
First i used BaUpgradeUt.exe. Error 100: Error model ID appeared..
Second I used MaUpgradeUt_noID.exe. After several seconds appeared window with information about uprading, so I pressed UPGRADE button.
After that ActiveSync shutted down, and window with information "checking information on your device" appeared...
My XDA still working, there is no information about upgrading.
Is there any tricks with WM2005.
Some advices?

mcs1 said:
After that ActiveSync shutted down, and window with information "checking information on your device" appeared...
Click to expand...
Click to collapse
And your BA waits for bootmanager to talk to it from BA.
mcs1 said:
Some advices?
Click to expand...
Click to collapse
Yes: to read readme.
In every rom package, (even in case of HELMI's on) there is Readme.txt file, that explains the procedure (in case of helmi's one: in folder with nbf file).
In short words:
0. Unhide and delete EXTROM by repartitioning flash rom (info on Wiki)
1. Unzip and copy nbf to correct folder
2. SetOperator (in case of MDA3 from ERA GSM it was T-MOB009, but you HAVE to check it in your machine)
3. Prepare EXTROM on SD card
4. Put BA in Bootmanager mode (Serial/USB massage on the screen)
5. Go on with BaUpgradeUt
6. Make Hard Reset WM5 way (power with reset is not enough)
When you do this carefull according to the Wiki and Readme, you should be happy user of WM5.

Thx. It's working now.
jakubd said:
mcs1 said:
After that ActiveSync shutted down, and window with information "checking information on your device" appeared...
Click to expand...
Click to collapse
And your BA waits for bootmanager to talk to it from BA.
mcs1 said:
Some advices?
Click to expand...
Click to collapse
Yes: to read readme.
In every rom package, (even in case of HELMI's on) there is Readme.txt file, that explains the procedure (in case of helmi's one: in folder with nbf file).
In short words:
0. Unhide and delete EXTROM by repartitioning flash rom (info on Wiki)
1. Unzip and copy nbf to correct folder
2. SetOperator (in case of MDA3 from ERA GSM it was T-MOB009, but you HAVE to check it in your machine)
3. Prepare EXTROM on SD card
4. Put BA in Bootmanager mode (Serial/USB massage on the screen)
5. Go on with BaUpgradeUt
6. Make Hard Reset WM5 way (power with reset is not enough)
When you do this carefull according to the Wiki and Readme, you should be happy user of WM5.
Click to expand...
Click to collapse

BA imate PDA2K upgraded to AKU3.2 and want to Ug Radio to 1.15 but having a problem

Operator version : AKU3.2
Rom V 5.04.06 WWE
Rom date 03/02/05
Radio v 1.12.00
Protacol v 1337.42
Ram size 96mb
Flash size 32mb
Storage size 43.26nb
Model PH20B
Pocket PC
IMEI 3530300008641
GetData: PH20B AT%CID?
5 . 0 4 . 0 6 . 1.3 1.12.00 % 4
1st problem: Downloaded the Radio 1.15
and unrared it, fixed country code. (That was the error when tried to run it)
The download (Radio 1.15)does not show the ms_.nbf or the nk.nbf
Shows: Getdevice, Enter BL, BAupgradeut, HTCRUU.dll, HTCRUU and the radio_ (just like that, no ext.)
downloaded MaUpgrade_noid.exe. when I ran this gave me: Unable to locate Component. (this application failed to start because RUU.dll was not found. Re-installing the application may fix this problem
Please help

primbcadman said:
Operator version : AKU3.2
Rom V 5.04.06 WWE
Rom date 03/02/05
Radio v 1.12.00
Protacol v 1337.42
Ram size 96mb
Flash size 32mb
Storage size 43.26nb
Model PH20B
Pocket PC
IMEI 3530300008641
GetData: PH20B AT%CID?
5 . 0 4 . 0 6 . 1.3 1.12.00 % 4
1st problem: Downloaded the Radio 1.15
and unrared it, fixed country code. (That was the error when tried to run it)
The download (Radio 1.15)does not show the ms_.nbf or the nk.nbf
Shows: Getdevice, Enter BL, BAupgradeut, HTCRUU.dll, HTCRUU and the radio_ (just like that, no ext.)
downloaded MaUpgrade_noid.exe. when I ran this gave me: Unable to locate Component. (this application failed to start because RUU.dll was not found. Re-installing the application may fix this problem
Please help
Click to expand...
Click to collapse
Just rename the HTCRUU.dll to RUU.dll and you're good to go

thanks for help now new problem
new when I try to download get error:101 connection error
and ends my connection to active sync
By the way this is a fantastic place great people here

can't format extRom..

hi people...
i tried to install a wm5 and a wm6 rom in a qtek 9090 but i can't format and merge ExtRom... i tried to use the rom unlocker found in the a77ila wm5 rom pack but i have a lot of error during unlock.. and when i try to format this error will show: FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed!
i tried with xda-developer unlocker but an unable to find exe file will show..
and repart_doc still not work...
anyone can help me?
my device:
qtek 9090
SO WM2003SE ver. 4.21.1088 (Build 15045.2.6.0)
ROM : 1.40.04ITA
Radio: 1.12.00
Prot Ver: 1337.42
ExtRom ver: 1.40.153 ITA
tnx in advance... and sorry for my bad english

1. You cannot reformat extROM without unhiding and unlocking it first. Follow the procedure step by step. (remeber aboutsoft reset
2. Correct links to both tools as well as the procedure you can find on Wiki (http://wiki.xda-developers.com/index.php?pagename=Helmi - Installation)
3. Report effects.
3b. Your english is OK

here i am...
followed tutorial step by step...
1. installed the unlocker
2. launched unhide
3. soft reset
4. launched unlock
5. system displays a windows named debug showin ERROR: press OK
6.another system window named debug showin FL_IOCTL_BDTL_HW_PROTECTION press ok
7. another window saying a peripheral connected to system in not working press ok
8. a debug window saying extrom unlocked
9. soft reset
10. launched repart_doc
11. error window saying "FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed" press ok
tried also without soft reset at point 9. same results..
i only see Ext_Rom in memory page of Setting but still remain full
------------------------------------------------------------------
Finally solved...
i don't know why but ita extrom can't be formatted...
so i used an escamotage... upgraded qtek9090 with this rom BA_TMNL_14200_119_11300_Ship
After used unlocker and repart_Doc and all goes on....
now go to upgrade to HELMI_BA_WM6_R0_Public

hiya
i cannot format my DOC too, i got the same error ,
i used TASK 28 under MTTY , but still i'm getting this error.
anyone can help with this problem ?

Hiya
I was searching XDA-DEVELOPERS website about 2 days to find a solution for this problem, I have an I-mate PDA2K, i used all EXTROM tools on this website like this:
1- Installed EXTROM_tools,
2- run UNHIDE ,
3- then run UNHIDE,
4- Soft Reset,
5- now i can see Extended_ROM on my file explorer, i can read it , and able to write on it ... copy paste ...
6- run REPART_DOC.exe on my device,
7- tried many sizes like 128kb, 1024, 2048, 512, 61000, .................
but on this step i always get the god damned FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed,
i finally used Task 28 under MTTY but nothing happened, still have this problem,
No Wayyyyyy ! No wayyyyyyyyyy to repart my DOC size, .... noooooooooooo wayyyyyyyyyyyyyyyy
anyone going to help me plzzzzzzzzzzz ?

try it in this order...
1. downgrade to 2003
2. in WM2003 unlock... unhide... softreset
3. then repart_doc...
4. then upgrade to WM5/WM6
PS:
@Borbor...
hmm... i cannot see any part on your post that you tried to UNLOCK the extrom.
mastermoon DID. you need to unlock it first in order to modify it.
unhiding it just simply makes it visible to filemanagers.

SilverSamurai said:
try it in this order...
1. downgrade to 2003
2. in WM2003 unlock... unhide... softreset
3. then repart_doc...
4. then upgrade to WM5/WM6
PS:
@Borbor...
hmm... i cannot see any part on your post that you tried to UNLOCK the extrom.
mastermoon DID. you need to unlock it first in order to modify it.
unhiding it just simply makes it visible to filemanagers.
Click to expand...
Click to collapse
Hiya
I'm not a braincracked one, I'm a computer software engineer and i write CNC machines programs, so i don't need to someone to teach me instructions !!!! i did all, but i got FL_IOCTL_FORMAT_PHYSICAL_DRIVE failed. !
find me a good solution plz !

and i thought landmark's the only one who is bossy...
if you dont need instructions then what are you looking for in here??? duh!!!
you're both at the same level of intelligence... are we downgrading humans now?
P.S.
look at the end of the third post... that is solved.

Everybody is allowed to name themself software engineers nowadays?

Please people start behaving like grown up's we are no longer in kindergarten.
Please:
- listen to each other
- be prepared to be wrong
- try explaining your problem in another way
- but most of all don't try to solve your listening problems by yelling and cussing to each other.
TIA, Flar

Upgrade to Windows Mobile 6.x

Dear XDA Members,
I have now read the official Wiki five times, and I still haven't understood how to upgrade my BA to a Windows Mobile 6.
The Wiki "HTC Blueangel WM6 Home" links to a Wizard Style Wiki for this, however that link only returns a 404 Error. I also haven't found any information about this in the FAQ or orther threads. Maybe it's just me?
Where can I find a WM6 image for the BA (T Mobile MDA III)?
What software do I need to flash it via USB to the BA?
Thank you in advance.
Chris

Please refer to http://forum.xda-developers.com/showthread.php?t=630416
The instructions are there in Posts 1-6. Good luck.
Sunny

hi and welcome to the forum
as stated by sunny, my tutorial thread should cover all aspects of the upgrade process, including links to most of the recent roms.
the blueangel wiki suffered from the transfer to the new mediawiki project, which is why it should not be used for tutorials anymore.

Thank you both for your fast and helpful support.
I am running a non-english Windows Mobile 2003SE (GER) and executed the steps from your Guide to downgrade it to a WWE version. On xplode.tk I downloaded the latest T-Mobile UK Version and extracted the files mentioned in step 1b from the Temp folder while executing the .exe file. I also copied the files into the RUU folder.
When I open the task manager in step 6 i can only find and kill "wcescomm.exe"; "WCSEMgr.exe" isn't there. I am running WinXP SP3, logged in as administrator.
When I start Maupgradeut_noid anyway, I doesn't show me the rom versions.
Where am I going wrong?
Edit: I forgot to mention I have read the thread "Cant' Downgrade from Win2003 SE GER to ENG", but renaming the folder and then trying it didn't work for me either.

if you can't see those processes, you are probably not running activesync. install the latest version (a link can also be found in that thread in the 2nd post) and create a temporary partnership. just connect the device in normal running mode and set it to sync something small, like notes or favorites, after syncing go to the connection settings and untick "allow usb connections" then you should be fine and you can continue with the next step, connect in bootloader mode, make sure the display changes from serial to usb. at that point, a new driver will be installed and then running the ruu should get the upgrade process working, meaning, then there will be numbers in the 2nd window. if not, please post the RUU.log found in C:\

I have already installed ActiveSync 4.5.0.
I created a temporary partnership syncing favourites and after that unticked USB syncing in ActiveSync.
Then I connected in bootloader mode, making sure the display changed to USB V2.07. No new driver was installed, but I guess that already happened in my earlier attempts.
The HTCRUU.log (no RUU.log there) i found on C:\ contained a "Image Radio Checksum Error", so I downloaded another image from another mirror, but got the same problem.
Here is the log from the 2nd attempt:
11:50:02:843 [msg] : Config Info : [000000],[0],[0].
11:50:02:875 [err] : Image Radio Checksum Error.
11:50:02:875 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [0]
____
I HAVE however been able to flash a WindowsMobile 6.5.3beta image to the device without formatting, so thank you for helping me with that!
I reverted back to Win2003SE, because I would still like to get the 60MB if possible.

ah, ok, apparently the radio rom is damaged and shows a crc error, since you are planning on downgrading and then upgrading, just delete the radio_.nbf from your update folder and try again.
no worries, obviously, you did nothing wrong, but there have been a lot of corrupted radio roms around lately, xplode's rom archive has them and so mine and d-two's have them as well.
in general, a first indicator for corrupted roms is the file size, a nk.nbf rom must always have 32,769kb (1kb more than 32mb) and a radio has 4,097kb (1kb more than 4mb)
you can ignore (delete) all radio roms in the process of upgrading, frankly, it has nothing to do with the operating system itself, it is just the bridge between the operating system and the hardware. if you are not running radio 1.15.00 yet, which is the latest and according to most users, the best version, you can upgrade it any time you want, so i'd suggest: try and upgrade to wm6.x first and then, when you got used to flashing, flash the radio, or, if you are satisfied with your phone's in-call sound quality, bluetooth and wi-fi performance, don't flash it at all.

Ah, ok.
I deleted the radio file and tried again. This time it showed me an ms_.nbf Checksum Error. I deleted that one as well and got this:
09:51:05:968 [msg] : Config Info : [000000],[0],[0].
09:51:05:968 [msg] : RadioFile Not Exist !
09:51:05:968 [msg] : MSystemFile Not Exist !
09:51:06:171 [err] : Image CE Checksum Error.
09:51:06:171 [msg] : Update Image. CE : [0], MSystem : [0], Radio : [0]
I also redownloaded the MaUpgradeUt_noID.exe right from your signature to ensure I didn't use an old one. Still the same problem.
My radio file DOES have 4,097kb; the nk.nbf has 32,769kb as well...I have to admit i'm still puzzled.
I also downloaded the two most recent radio files from your tutorial thread. Same problem: Checksum error. But I do not get a checksum error when I try to flash one of d-twos os-images.

i'm changing the radio roms, i will only provide radio 1.15.00 from now on, and i will post the entire package, as it came from htc (including the original RUU).

Thanks.
Where can I find them? Your tutorial thread seems untouched.

flash
hi WeissenbornC,
are you flashing with vista or win7??
if yes read please d-two´s tut for flashing with vista/win7.
http://forum.xda-developers.com/showthread.php?t=622768
hope it helps
cheers scudo

Hi scudo2709,
I am using Windows XP. Flashing a ROM is no problem, I have now had 5 different ROMs on my BA. However, I haven't been able to flash a shipped english rom (WM2003) in order to format the flash drive. I keep getting Checksum Errors with all of the ones I've been able to try so far.
Thank you for trying anyway.