i got 2 files from someone wich updates the rom of an xda2
this exe you can extract and then replace the rom file
gonne test it in a few hours and then post my results and the program
ok its only an extened rom updater..
it works
they have a beter error recorvery i must say,
i replaced the extened rom with a ppc2003 rom
and it updated
@ 99% it failed.
phone looked dead
said only serial 1.01 and i treid the normal extended rom again
and it was succes,
phone is back to normal
german though
Where did you get the files from Akira? I need to find English ROM, if I can find the right tools, I can have my friend copy his Imate rom and flash it back to mda II
Related
Hi,
I seem to have made my MDA compact II a brick. I was having problems hard reseting it (Format FAT failed) so I tried upgrading to a different firmware.
I now have the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID
firmware on it. This is not good as it is for the Prophet, although it says in the Wiki that this should work. Anyway I can now hard reset the phone, so all I need to do is flash the TmobileUK firmware back on it. The only problem is that it doesn;t let me do it. It says error:296 upgrade only.
Anyone any ideas?
cheers.
extract the contents of the t mobile package using win rar
download
ftp://xda:[email protected]/Prophet/Tools/ROMUpdateUtility-NoVendorID.zip
and put in the same directory and run.
It gets to 1% then says invalid command, not for this phone.
Latest T-Mobile ROM is at http://www.tm-phonedownloads.com/download_manager_mda_com2.html
very stable, much better than the original shipped ROM
Finally got it back.
If you have a T-mobile MDA II (Charmer), then Flash it with a Prophet ROM, the only way I could get it back was to use the following:
RUU_Charmer_100_100_049_CHS_Ship.rar
typho5 -x nk.nbf
Then created a new nk.nbf with the output using nb2nbf.
I then Flashed this with Wizard_RomUpgradeUtility_noID
And miracle it started. I quickly CID unlocked it and am now flashing with latest T-mobile.
My problem was that the Rom Update programs wouldn;t read version 2.xx ROMS.
Anyway it has just finished and looks fine. Thanks for everyones help, now I just have to get my SD wifi card working.
How do you do it
Hi I just got a MDA compact II from T Mobile UK I would like to upgade the ROM but its all very new to me since you know what you are doing can you post an idiots guide to the process.
Hope you can help
Hi, it depends what Rom you want to upgrade it to, the latest one from T-mobile is pretty good. There is an unbranded one (no T-mobile logos or suchlike) or there are Roms in different languages. It depends why you want to change the firmware and what to.
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
daveh1171 said:
I suppose I don't really know the problem is as I just got the thing did some searching and came across this site read your post and thought i want to do this maybe you have some suggestion. Also I tried the RUU mentioned in an earlier post but it I can't update when I get to the from/to screen it tells me I will go from 2.6.2.110 to 2.6.2.110 I was expecting to move up.
Click to expand...
Click to collapse
Sounds like you are running the latest version. Is there a problem with the phone? If the phone works fine, I would just unlock it using lokiwiz02b (So you can use any network card) and then EnableRapi (So you can run unsigned code) then CID unlock it using awizard (so you can use any Brand/Language of ROM).
If you have no problem with the firmware I would leave it alone.
Hi,
Yep, I'm in the same situation, why does the prophet firmware load onto the charmer without erroring? !!!
Anyway, I have a copy of RUU.rar but I'm having problems working out what I need to do to it between unpacking and flashing the phone (i.e. the typho5 bit and then the nb2nbf).
Can someone please help me out?
P.S. The phone just sits at a black screen that says 'Dopod' across the front at the moment
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Chirpy said:
Can anyone tell me how to 'force' a downgrade of firmware? I've got what appears to be the right firmware from FTP but it won't over write the incorrect version 2 installation as the uploader software thinks it's later therefore better.
There has got to be a better option from the command line surely?
HELP phone is dead
Click to expand...
Click to collapse
Progress, but now it works only from the charger so the shipped ROM upgrade won't work as it reports the battery as being at less than 50%.
Anyone know how to force a ROM upgrade or where I can find the right ROM files to use awizard to do this?
I tried to update to a mda compact 2 with the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID.zip
rom,
however when booting it getr stuck on the dopod screen, the IPL is 2.06.001 and the spl is 2.15.0001
I have tried flashing a few other roms to it including the o2 neo but this results in the same problem.
I have tried to revert to the tmobile version but as it is a lower version it will not let me.
What can I do?
Regards
Tim
anyone have a sd card dump of the t-mobile unit?
Tim
You can either try
Flashing it with t-mobile latest WWE ROM (refer to WiKi http://wiki.xda-developers.com/index.php?pagename=HTC_Charmer ) -
`T-mobile UK. RUU_Charmer_2060227_20602110_021921_T-MobileUK_Ship`
Or, flash it back with T-mobile shipped WWE ROM from the ftp server here and flash it with aWizard. I'm not sure about others, but `HTC_Charmer_Shipped_ROM_WWE_UK_TMobile.zip` is the one I uploaded and it should work with aWizard.
plink212 said:
I tried to update to a mda compact 2 with the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID.zip
rom,
however when booting it getr stuck on the dopod screen, the IPL is 2.06.001 and the spl is 2.15.0001
I have tried flashing a few other roms to it including the o2 neo but this results in the same problem.
I have tried to revert to the tmobile version but as it is a lower version it will not let me.
What can I do?
Regards
Tim
Click to expand...
Click to collapse
Do the updates actually run fully?
You could try to set the device in bootloader mode manually before trying to flash a new rom. That resolved the problem for me.
I flashed with the dopod no id rom.
Success!
Robin
I cannot do the awizard as I cannot get it to boot into windows mobile.
I cannot flash the tmobile software as it says that the nbf is incorrect for the handset.
The dopod rom is being flashed from the bootloader and complete sucessfully however it just gets stuck at the dopod screen and proceeds no further
Any other ideas?
Tim
What posessed you to try to flash a Charmer with a Prophet ROM?
2 things
1. I thought it was a prophet
2. it says in the wiki that it works
1. Easy mistake I suppose.
2. Wow! I wonder who wrote that. In any case I would not have risked it but then I'm a bit of a coward when it comes to this kind of thing, especially when I've read so many posts where people have bricked the devices.
anywho does anyone have an sd card image of the magician?
ok i have found someone who has a compact 2 i just need to know how to dump the rom to sd card any pointers?
I have an CHARMER PM200.
Its version was 2.xx.xxx.
Customer give that phone to some one to unlock.. and that person kill this phone..
Now its only SHOW three color screen and
IPL 2.06
SPL 2.15.0001
..
I tried to write ROM with T-Mobile RUU_Charmer_2060227_20602110_021921_T-MobileUK_Ship
But it give me error.
ERROR {296} : UPGRADE ONLY
This NBF file cannot be used for your PDA phone. please get new NBF file.
When I use JAFWM to flash above file its flash 100% but problem still same.
anyone know.. how I can revive this phone..
Br.
DrMobile
Also tried to flash ROM RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_Ship-NoVendorID
But at 80% I get error..
ERROR [326] : INVALID COMMAND
This file cannot be used for your PDA Phone. Please check your NBF file
plink212 said:
ok i have found someone who has a compact 2 i just need to know how to dump the rom to sd card any pointers?
Click to expand...
Click to collapse
Hi,
I am facing the exact same situation like yours.
Please tell me, what is your status now?
Did you find any success with SD Card Image. Please let us know.
T-Mobile MDA Compact II: Come back from the Prophet to the Charmer ROM
The Problem is: I have change the ROM of my german T-Mobile MDA Compact II from the "Charmer 2060228 GER" to the "RUU_Prophet_220734_2207114_024721_QtekWWE_Shi p" and how can i now overwrite this one with "RUU_Charmer_2060227_20602110_021921_T-MobileUK_Ship" (or any other Charmer series)? When i start to change the ROM, it is loading about 1% and the mistake is about "nk.nbf" file. Is there any body know, how to solve this problem?
lelik_yaa said:
The Problem is: I have change the ROM of my german T-Mobile MDA Compact II from the "Charmer 2060228 GER" to the "RUU_Prophet_220734_2207114_024721_QtekWWE_Shi p" and how can i now overwrite this one with "RUU_Charmer_2060227_20602110_021921_T-MobileUK_Ship" (or any other Charmer series)? When i start to change the ROM, it is loading about 1% and the mistake is about "nk.nbf" file. Is there any body know, how to solve this problem?
Click to expand...
Click to collapse
i flashed charmer with wizard..and now its totaly dead...it cant even enter boot...any suggestion....
Hi I made a very big mistake i flashed my cingular 8125 (g4) unlocked by IMEI-CHECK. I flashed it with molski aku 3.2 and when it reset the Cingular Extende Rom is the one that automaticaly gets lunched. So I unlocked my extended rom with Unlock_ext_rom_wizard_1 and reflashed again expectine that when config will be finished then the molski extended rom will lunch but no succes so I dont know how i errased the auto run on the extended rom and when i reboted it no my Cingular extended rom dont run and neither molski or farias I even cooked an extended rom but It have never auto runed again I do have backup of the original which I made with awizard 1.2 and other wiyh beta1.3 but I place it into phone memory or phone sd and it never runs I have to do it manually. Im tired of doing it manually and of it I want to instal another rom like molski's or Farias or maybe even cook my oun but I don't know how to make it autorun again. My extended rom in the phone is empty now because y got so p#$% with it that I erased it for compleate. I there a way that I can do it work again. Worst than this is that this damm (G4) dont let you do an sd backup image and the Cingular 8125 RUU2.25 its not intended to reflash a g4.
make sure that you have the config file and the autorun.exe file!!! if you dont have one of these it will not work at all!!!
I guess you alreay know this. I was having the problem the other day that it would get half way though and would stop!!! so i went back to the old one and i will try again whe i have more time!!!
Maybe you could tell me what you are putting in your E_rom and put the cinfig txt on here! you may have a small error.
Hey Guys!! I hope, you can help me...
I want to install a other ROM on my Orbit. But it allways brake up at 3%. So, i thought, maybe it would help to install the original ROM. Ok, now i've got the oooooold original WM6. wow...
I want to install a version of 6.5, but everytime it stops at 3% with the notice, that my ruu is corrupted (Error [270]).
So i tried to flash via SD-Card. Renamed the ROM from RUU_Signed.nbh to ARTEIMG.nbh but sometimes the orbit means, that the ROM isnt certificated but mostly the Orbit cant find anything.
So, please help me
Hi there,
I used to have a similar problem every time I tried with WM 6.1 till yesteray.
The solution I found was,
Use USPL (http://forum.xda-developers.com/showthread.php?t=311403&page=69)
Before you start USPL, be sure to remove SD card and SIM card from your phone and follow the procedure as in PDF there
Then flash whatever ROM you want to.
I think i have a clou as for the well known error number 270.
I think its either the CID is not in vendor mode ore the rom has not got the right signature.
This is what happend to me and draw your own conclusion from it, but i hope it helps a little to understand and resolve the error ( well resolve it )
I bought an t-mobile compact 3 wich whas send by mail and got bricked on the way here. So .. i searched the net for a rom and found something i liked.
using a sd card i couldnt because it said somthing like image invalid signature.
later i found a factory rom update rom at the UK t-mobile. I extracted that and putt it on a sd card. Using the bootloader manually i run the image and updated perfectly.
So i whas happy i didnt bought a brick and whas workable.
Not happy with the factory rom ( tough it work charmingly and tomtom work even better then other roms) i seeked out something more eye appealing. having a p3600 bought with manila 2d for my hunny, whas nice to see so i seeked one for the artemis.
Tried updating it and got error 270. perhaps not the correct signature ?
Maybe...
So i got back at forum and read on sticky's and found a great utility called USPL .. ( Great thanks to the creator(s)of this app ) Supposedly the app open up the CID to super mode ore open vendor mode, wich then makes it possible to insert any rom with an RUU .
(i asume you'll know it means Rom Update Utility )
The screen on the phone went black and instead of the RUU included i ran the RUU of the Manilla 2d rom and ran past the 3% so that meand it will update the rom. The screen stayed black untill it rebooted and it came alive !! ( sorry for the dramatic effect )
the rom i didnt find to be stable it crashed when i turn up the volume when using tomtom it crashed when the alarm went , and it crashed several more times. ...
More roms to try anyway and got to pdaviet 6.1 wich i didnt like but run smoothly and crashed somewhere during alarms.
So i upgraded to 6.5 .. where i went messing with the uspl app and putted the roms in the same folder including the RUU.
So at 3 precent i got the error 270 , Huh rom has invalid signature ??? neh .. the rom said singed so i downloaded the uspl again and did it my old way run uspl till it opens it RUU cancel that one and run the RUU included with the rom i wandet to upload to the phone.
i now run FlyROM 5.0 Manilla WWE with the extra english keybord rom.
and so far so good, it runs nicely tomtom again i little slower then on the factory WM5 ( both installed on device btw ) Flyrom 5.0 WWE