Error 100 when connecting in Bootloader mode. - General Topics

Hi,
I have a M2000 which started to up the Orange NL ExtRom version 1.40.230. When I ran the app it went into bootloader mode (USB/v2.07)but BaUpgradeUT reports Error 101 and Exits.
Sooo, I downloaded the original shipping ROM and tried with that - same result, then tried using MaUpgradeUt_noID in the same folder as the original ROM - as it ignores the information that is reported back (apparently none in my case). It tells me on the next screen that it is upgrading from <blank> to <blank> - worrying. Click Upgrade and I get Error 150: ROM Upgrade Utility Error. Try to do the same with the 1.40 ROM by locating the temporary files for the .exe and running MaUpgradeUt_noID from there - same error.
It's now stuck in bootloader mode...I didn't put anything on to this before, so I can't see how the operator code would be overwritten.
Much as the M2000 works as a desk paperweight, I'd rather find a way of pushing a viable image onto it and getting it back working. Any suggestions as I am running a C500 as a replacement and going nuts with it's lack of, well, anything...
TIA
P.S. Even another ROM that will load onto it would be useful, so that I can get it back into a state where I can mess around with it again...

do you have a firewall and antivirus installed?
if i would disable them then try flashing again, I got my c500 stuck in bootloader mode after trying to sim unlock it with firewall and antivirus running
disabled them and re-ran the sim unlock and it worked, so hopfully it is the same problem as you are getting with the rom

Related

DEAD device, upgrade using MTTY? Cannot use MaUpgradeUt.exe

Is there anyway to upgrade my Dopod 818 (htc magician) using MTTY? I have tried using MaUpgradeUt.exe along with change.bat etc, but I ended up "upgrading" the device with a mixture of chinese and english files, and now the country, device, and operator IDs are scrambled on the device ROM itself. I cannot use MaUpgradeUt.exe because I no longer know what the country, device and operator IDs are and I cannot run GetDeviceData.exe because the device itself is stuck on the USB/Serial screen. I also tried reverting back to my previous working ROM by flashing from the SD card (using MTTY), but I get the error "Section 1: not allow update"
My device is completely unusable right now and I am really hoping there is some way to restore its ROM without sending it back to the manufacturer. My guess is that I somehow need dump the original ROM back onto the device using MTTY, but the only command I know is "d2s" which backs up the current device ROM to an SD card. I'd really appreciate your help! Please email me or post to this forum, thank you!
UPDATE: device fixed using MaUpgradeUt_noID.exe
what a great tool -- fixed the dead device
it is no longer a $600 doorstop

fragged my mda_c with official update

Hi all,
yesterday, i thought it's a nice day to do the official german t-mobile 1.12 upgrade on my official german t-mobile mdac. It wasn't.
After the upgrade (no errors) the bootscreen shows:
no gsm, and only one Version number: 1.12.01 Ger
on the bottom line.
After it bootet, i get no gsm and no bluetooth working. When i connect by usb, active sync hangs for about 3-5 minutes. If i try to repeat the upgrade, i get something like wrong device, and it shows empty fields on the version screen. I tried to do the update by extracting the official update rar and start the update by MaUpgradeUT_noID.exe, but it says something like wrong device.
I tried this to the same with the 1.13 upgrade from the xda ftp, same thing. I tried a rombackup from sd-card that i found somewhere on the net, but the bootloader says wrong section=1 not allowed.
Is there anybody wo could help me to resurrect my poor little mdac?
Thanks alot,
J
Hi J.
Don't know how to solve all your problems with upgrading, but did you copy the first bytes of your own romdump to the downloaded rom? Otherwise your device won't accept it, you can find a lott about this in other threads. try searching for BigStorage and you will everything about rom upgrades.
Good luck, M
Upgrade your device with the imate rom 1.12 wwe using MaUpgradeUt_noID.exe ,it should work ,then try to upgrade to the german rom upgrade.
Good luck
ongoing revival
Ok, i tried that big storage thing, i replaced the id in the new image from my backup (broken) rom, and when trying to upgrade from sd-card, i get Section = 1 not allowed update.
I'm trying to upgrade the radio stack from the bootloader screen with MaUpgradeUT.exe, but it seems that the usb port doesn't work: for 10 minutes, the update screen stands at 0%, then an error appears:
Radio Rom Update Error.. i should reset, reconnect and retry.
Any more ideas? Is there a possiblity to do the normal "online" update (not via bootlaoder/backup-image) just from sdcard?
Please Help
J,
Last night I did a BigStorage in a very easy way. I followed the description in the thread about upgrading to radio 1.13. You'll have to unzip the shipped rom, decode nk.nbf it with dnbf. Then you replace the usual bit pattern and encode nk.nb1 again. After that you can use maupgrade with or without the noid function like a regular apgrade.
Hope it helps you, M

M500 brick

Brother in law got a m500 with the original uk ornage rom on it. He downloaded an ornage upgrade from oranch.ch and started the upgrade process IN VISTA.
It went into bootloader mode and then came up with an error message.
When it resets now it goes through all the setup and installs all the software and customisations and then crashes back into bootloader mode.
we have tried all sorts of combinations now using my xp computer:
Using no_id with orange.ch rom, qtek, imate, tmobile rom, with USB on and off and also the tmobile radio upgrade too.
THe closest we can get is country id error when upgrading a rom.
On the radio upgrade it hangs at 0% giving error 114
Anybody got any ideas?

Cingular Branded 750 WM6 Upgrade..Update vs Bootloader

Ok...
I have successfully upgraded my Cingular branded 750 from WM5 to WM6 using the bootloader method. However, my Software Version still reads TREO750-1.13-CNG.
Is there a issue with this? Do I lose any WM6 features if my v is not 2.23? My firmware is 1.54.00.00, so, it's ok there.
I also tried to use the Update method. I changed the payloads.xml file to the correct settings for my phone. Device changed to CNG (ATT did not work) and 1.16 changed to 1.13, and high changed to 1.16, 2.23, and 2.24 to try all I have seen.
When the update starts (after changing the xml file) the display on the updater reads loading files, then when it begins to start the update, my phone display says "Goodbye" shuts off like I had hit the end button to turn off the radio, and goes to a screen that has 4 horizontal color bars (R,G,B,W) and then the updater says that it lost the connection to the phone. I'm screwed after this point.
So, if there is no issue with the 1.13, then I don;t really care about the above. At 1.13 the phone is working.
If there IS an issue, then does anyone know why I cannot complete the update without the phone disconnecting from the updater?
Update.
After reading some other posts elsewhere, someone made a veiled reference to my 2nd issue with the loss of connection during the update, and suggested plugging the Treo into my PC while already in bootmode[. No drivers tried to load, so after a quick trip to device manager, and a reinstall of the driver, the Treo no longer disconnects during when the updater switches the phone into bootmode. It's updating as we speak.
The bootloader method does not upgrade all aspects of the phone's ROM. You need to use the .exe method, but you'll need to edit the .xml file that is created in your temp dir after the FIRST STEP of the installation program.
Search around. This has been discussed a million times.

Possible to Flash a sprint 6700 to VZW?

Help!!!
I have a sprint 6700 and have tried to flash to VZW with zero success. I have tried everything I could think of...
Found the sprint msl with getspc no problem.
Downloaded the vzw latest aku3.3 rom, won't install.
Tried to install in bootloader and not in bootloader mode.
Tried different roms and none work (official sprint ROM loads fine)
Tried BuildOS with noid and get the same error.
I have ver 102 bootloader and have tried with activesync on and tried with activesync disabled.
I never get past the first screen. I get "Error 120 Country ID Error" window and only option is exit. I looked here, ppcgeeks, pdaphonehome, and google and have not come up with any solutions....
This seems to be an impossible thing, to change from sprint to verizon....
Any thoughts or ideas????
Thanks
T
Same Here ! Help !!
I have the same problem with you all,, but it seems no one relpies to this thread. So what i should then using rom for sprint or what?

Categories

Resources