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 have searched the forums but can't find anyone that has had a similar situation. I have downloaded and flashed two different ROMs to my phone so far. Now I want to flash a third, but when I go through the process of doing the flash, strange things happen and the process fails... I don't want to make a wrong move here and end up with a brick so I will explain exactly what happens and maybe there is some easy fix. First, some details on my phone:
Whenever I power up my phone, I see two splash screens (one from each of the previous ROMS I have flashed to the phone) displayed sequentially. (I am sure this is part of the problem... but not sure how.)
The Bootloader lists the following information:
HERM100
IPL-1.04
HERM100
SPL-2.10.0lipro
And I am using ActiveSync v4.5.0.
Finally here is what happens when I try to flash a new ROM:
0. Downloaded the new ROM (in this case RUU_Hermes_CINGULAR_WWE_3_1_.57.502.1_6275_1.48.00.00_108-ATT-MR3_Ship).
1. Sync the phone with my PC using ActiveSync.
2. While the phone is still synced I fire up the upgrade utility that came with the above mentioned ROM.
3. I go through the steps, it recognizes the current ROM (in this case ProBlack 3.0.1).
4. Then when the progress bar shows up, the phone simply turns off. After a little while, I get an connection error message from the upgrade utility (of course because the phone just shut off).
Again there is probably a very simple fix. I think I need to be using a different flash utility instead of the one that is coming with the ROM.. but in that case how do I use an official ROM (like the official Cingular ROM) with a different flash utility?
* Opps.. my mistake, this should probably be posted in upgrading forum *
OK, I don't know an answer, but seeing as you've had no replies in a few hours I figured a hint that may or may not be right is better than nothing!
Is the ROM you're downloading an official one, or a cooked one from here? I'm sure I heard something about official ROM flash programs not recognising the Olipro SPL, so not flashing. In this case, you had to extract the .nb file from the official package, put it in a folder with the CustomRUU file and flash using that.
Might be worth trying redownloading the ROM (in case it's slightly corrupt) or trying a different cooked ROM to see if the problem is the phone or the file.
Sorry it's nothing conclusive, but I hope you end up finding the problem.
i have made a mistake
have tried to upgrade my T-MOBILE MDA COMPACT III(aka htc p3300) with the HTC TOUCH ROM
it started to upgrade and an error occured
then i have lost the display and all
when i connect it to my laptop using USB i hear a beep in my computer but active syn didnt find any device
i have downloaded the correct rom version from T-Mobile but it doesnt seem to work
i dont know what to do now..please help me it has to be recovered
there must be some way pls pls anyone help me to get my working phone back
will appreciate your concern
thanks
Regards
Faraz Feroz
as i said on the other post
well you have to get the original ROM for your device.. see their website.. it should be there for free. or try to get it from anyplace.. (the original rom)
and then flash it using SD Card flashing
info for flashing it by that are here:
http://wiki.xda-developers.com/index..._Card_Flashing
hope it will work
i think you can get it from here
http://www.tm-phonedownloads.com/sd_compact3.html
if WM6 did not work.. try WM5
thanks i m downloading it...but tell me one thing if there is a software issue then why isnt ther any display i mean no backlight no display no charging led
having same problem with both WM5 and WM6 upgrades!!
"error occur : invalid update tool
this update cannot be used for your pda phone, please get newer update utility"
i think that becuase the bootloader , ISP or one of these stuff are corrupted.. don't know.
and as i told once i got my artemis completely dead
and finally i got it fixed by putting the ARTEIMG.nbh in SD card as they said in the wiki and then by pressing the camera button and the power.
and it started flashing it as the SD card flashing but it took about 30 mins .. and there was three phases in the flashing progress which it was the first time i see.
having same problem with both WM5 and WM6 upgrades!!
"error occur : invalid update tool
this update cannot be used for your pda phone, please get newer update utility"
Click to expand...
Click to collapse
did you flashed it by SD card or RUU?
if you used RUU try by SD card flashing
did u get the same prob? i mean the phone seems to be dead? if so...there is a hope then
well...i used RUU simply downloaded it and tried to install by setup,,, dont know about card flashing but will try
where can i find that NBH file?
do u have that .NBH file?
you have to extract the file you using a program like winrar
there will be few files.. one of them is the nbh
that's how i got the nbh file.
and about the SD card flashing is here...
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
I was running the R1A generic ROM on my Voda Xperia (not using HardSPL) and just tried to flash the R2A ROM when I got a screen full of red writing after the "OS" section. saying
"KOVSIMG.nbh - FAIL"
"UPDATE TERMINATE", "UPDATE FAIL", with a code "00018002" at the top of the screen. I am using the MicroSD method.
EDIT: Restarted the phone and it is continuing the update, I will let you know on status this time.
EDIT 2: Fail again. Any ideas?
Cure
Had same problem (same problem address etc)
Cure:
Re-download rom
Format SD
copy fresh .nbh to SD
Done!
Suspect it was bad byte or similar
Yeh
Hey, I did the same thing and got it working, very strange though.
I didn't redownload I just formatted the memory stick again and copied the same file I already had over. Put it back and it installed fine the 3rd time. How strange that it was the same address, obviously wasn't the file, because like I said I didn't download it again, used the same one.
I HardSPLed mine and it worked fine
whats the difference between hardspl and no hard spl?
Did you install the hardSPL correct version ?
Or did you follow exactly the Tutorial ?
I know that for the french version, I had to use the nbh tool to extract the OS image from the full image to flash correctly my X1.... Take a look in the Tutorial to be sure that this step was not necessary (from memory, if I remember well, the nbh step is not necessary for DE or US, but the best way is not to listen to me but to the tutorial). I personnaly flashed mine but in french & perfect flash !
Difference
The difference between HardSPL and no HardSPL is presumably, that I, without the HardSPL can only flash official ROMS be they Vodafone UK or GENERIC_UK, or presumably any other locale of Official ROM. Since the Vodafone UK phone does not come Sim Locked, there is no reason I guess for them to protect from flashing other official ROMS including the GENERIC.
Since I plan to keep my warranty I do not intent to HardSPL my phone and am happy to keep it to official ROMs as long as they are generic and not the utter ****e that Vodafone dumps on us.
As to tutorial I did not follow any tutorial, I simply copied the rom image to my memory card as Kovsimg.nbh, rebooted using VolDown+Power and followed the on screen instructions. I do not believe a tutorial is required?! Again, as I said, no HardSPL, so that entire stage and attached complications are irrelevent.
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Hookwitz said:
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Click to expand...
Click to collapse
I have no idea what is happening with your phone and why is it happening... But I can tell yoy one thing. Whenever I had any problems when phone would not go further one step, I would do TASK29 and follow all the steps all over again. TASK29 is sth like wiping everything off your NAND. Hope it helps.
I kind of think this is a hardware issue... My boys did the same thing... Never got it back up and running.
Sent from my HTC HD2 using XDA App
what about the radio ?
do task 29 and flash radio if you haven't (ignore if you did it earlier) then install MAGLDR and flash the rom from within MAGLDR or follow whatever instructions the developer has posted in his thread.
I too have tried everything and although magldr and wm6.5 both flash from sd, still wsod. My advice is take it to tmobile, and talk them into admitting its a hardware problem ;-)
Sent from my HTC HD2 using XDA App
I forgot to mention I did try the Task29 and it too failed. So I am thinking it is a hardware issue.
UPDATE: I figured out where to find the .nbh files in my temp folder and was able to copy and paste them to the SD card. I have also gotten to the image load screen to flash the leoimg.nbh file. However all of them fail at RADIO and subsequently fail the update. I have tried new and old stock ROM and the Radio ROM by itself. I also used the Task29 nbh file and was successful in flashing that from my SD card ... but the HSPL is still there at the boot loader screen.
I can't seem to figure out what is causing the fail.
Thoughts anyone?
Sorry
HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TM OUS successfully
Did you check is this version quiet similar to your phone's hardware configuration
Ram 1024
My version is compatible. Again, it was running fine. In fact, I have a phone previous that I installed it and it worked beautifully but I dropped and shattered the screen. When I got this new one (same model) I performed the installation the exact same way. It worked a day and a half and then froze.
Based on other searches, it looks like I may have bricked my radio.
UPDATE:
I think I was able to solve this and hopefully I won't be as cryptic as someone else who had a similar problem. Don't Give Up is good advice however attempting the same time over and over is probably not the best.
This is what I did ... after banging my head at the redundancy.
I used NBHExtract from the NBHExtract forum on the Stock ROM T-Mobile_HD2_MR_Software_2.13.531.1 that I downloaded from T-Mobile. This extracted all the .nb files and thankfully they were well labeled.
I then used the NBH Creator from the NBH Creator forum (yes you will have to register to download this application.)
In the NBH Creator I used the settings provided to me in the NBHExtract window and used the SPL, Splash, and OS only ... leaving the Radio blank.
I created the leoimg.nbh file and put that on a blank 2Gig FAT32 formated SD card.
Booted the phone in Bootloader.
The update failed however it uninstalled the HSPL
From here I did a Hard Reset to clear the ROM Update failure message on the tri-color screen.
I attempted to update the ROM via USB to the 3.14 version (again downloaded from T-Mobile's site). This got to 4% and failed. I now had the warning triangle symbol on my screen indicating the Software Update failed and to try again.
I tried again however this time with the 2.13 version (the ROM I extracted at the beginning) via USB. This time is successfully installed.
This is probably not a fool-proof nor verified option, however it worked for my phone model PB8112000. It might work for you.
I am tempted to try Android again, however, I don't know if the radio issue was hardware or software.