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.
Related
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
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
Hi!
It's the first time I'm posting here, but after some days of search, I've found a lot about upgrading / downgrading, but nothing about my problem.
I've an MDAcompact / T-Mobile PM10A / Austria and tried to upgrade to BigStorage-Rom according this thread: " Magician to 1.13 + 1.13 Radio + BigStorage ALL-IN-ONE Guide ". I've backed up my original Rom, but after the flash, there was no radio-stack at all (booting device: "no GSM" on display).
I've tried to update the radio-stack again - error message: 114 - error upgrading radio-stack, the same with 1.12 and 1.13. I've tried to downgrade the rom to 1.12 - ok, but no radio-stack. I've tried to restore the original Rom via SD-card in bootloader-mode - device says: not allowed.
Can anyone help me?
Thanks in advance!
did u try to use an origional rom? i mean a non Bigstorage rom upgrade ? because that should fix the problem ( atleast i think it shoud)
Try Downloading the origional t-mobile1.13 rom and upgrade ur device using that install file . If i am not mistaken the first thing that is upgraded is ur radio stack then the extended rom and finally the operating sytem ( if u upgraded u would see that it does it in 3 steps).
I've tried that. As soon, as I upgraded to the original rom from T-Mobile, it stopped at the radiostack-upgrade. After that, I opened the "original".exe-file from T-Mobile with winrar and tried to upgrade again, but without the "radio.nbf"-file, what was no problem. After that, I tried to update with the "radio.nbf"-file (stand alone) again, but the "error 114"-statement came up again.
I got this error before, but only because I flashed my device with the wrong ROM.
(...I once misread "Universal" as a meaning and not as a device codename, and flashed the wrong Radio stack. Thing worked, but radio invalid, no phone capabilities. Fortunately, a reflash with the correct radio ROM found here saved me. And my $300 investment. -.-)
Either the radio part of the ROM's accidentially corrupted (download again), or the radio driver is incompatible with your device hardware. I'm not aware of Minis being avaliable in anything other than GSM tho...
I downloaded the original rom-version from the official T-Mobile website. Fact was: up/downgrade of the rom itself "ms_.nbf/nk.nbf" no problem (I've extracted the exe-file via winrar to a folder and made that several times to up/downgrade), but update of the radio-stack "radio_.nbf" not possible, ended in error 114. The point is: as soon as I start the update-utility, it shows the "Device CE Image version", "Device Extended Image Version" but no "Device Radio Image Version", it looks like no radio-stack is installed at all.
I got that exact same error through the aforementioned Universal ROM debacle (-.-). Radio failed to flash, no radio at all.
There should be a standalone radio stack somewhere in the FTP for magician. I know I saved mine with the 1.12.00 version. Try flashing with that, there's a file inside that allows you to bypass the version detection IIRC (which allows a from-scratch flash). Flashing a standalone radio stack will hard reset your system, but otherwise will not touch anything else.
So I been trying to upgrade my OS to the tnt 1437, however every time I try my old OS keeps popping up (OS: 5.1.xxx (Build 15671FARIA.3.5)) ... so for the last 3 days I been trying to search this site for any answers, however all I get is that only happens if the CID is locked, but my phone isn't 1) I unlocked it before to upgrade it in the first place to the above mentioned OS and 2) I checked its status with the Wizard Service Tool (which is AWESOME). So i'm at a lose here as to why every time I either upgrade or downgrade the ROM the same OS keeps showing up. BTW Everything else I can upgrade except the OS. Any help is appreciated. thanks!
Anyone? Anything?
Did you remember what version of IPL and SPL when you unlock your Wizard? It is only unlockable when IPL and SPL is 1.xx (i.e. Downgrade to Button's ROM first). You may post your WST log here for more chance to know what the problem is.
Here you go here is the log:
Wizard Service Tool v4.2.1
12/11/07 23:07:22
CPU Manuf. FAILED
MODEL: Wizard
=> Bootloaders:
IPL: 1.01 (G3 device)
Built on Sep 19 2005 at 18:00:32
Copyright (c) 2003 High Tech Computer Corporation
Getting more info...
=> Firmware:
OS: 5.1.xxx (Build 15671FARIA.3.5)
ROM: 3.8
Registry AKU: FARIA.3.5
Radio values FAILED
=>Extended_ROM:
Version: faria V4.0
Name: Extended_ROM
Status: hidden
Getting drives,disks and partitions info...
=> Drives and partitions:
|--Handle--|---Size---|
6e9d5352 - 9.99M (0x9fd800)
eea9813a - 48.23M (0x303c000)
2fb23f92 - 50.95M (0x32f4000)
efb23f3e - 2.94M (0x2f0000)
cfb23fb6 - 3.06M (0x30fc00)
All Done.
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
kegobeer said:
Did you flash back to the T-Mobile 2.26 ROM before you tried to flash to another custom ROM?
Click to expand...
Click to collapse
Yes I tried both the button ROM and the love ROM with no change ... On another note I can change the IPL and the SPL with no trouble however the OS always stays the same.
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
kegobeer said:
Not the love or button - the original carrier ROM, either T-Mobile or Cingular.
Have you tried doing a hard reset, and then flash to the T-Mobile ROM from a different computer?
Click to expand...
Click to collapse
I just tried what you mentioned however I got the following error when I was doing the ROM update .... fyi I got it from the tmobile site ... when I ran the rom update I got:
error [326]: invalid command
this nbf file cannot be used for your pda phone. please check your nbf file.
It looks like you originally skipped the 2.26 rom. I did the same thing the first time I flashed a rom. Try flashing back down to the Button rom, then to the 2.26, then the tnt 1437. It worked for me.
Am I doing something wrong here cause every time I try some downgrade its always the same OS that shows up ... 3.3.0.0 that NEVER changes, everything else does.
i have the same problem..
8125hacker said:
i have the same problem..
Click to expand...
Click to collapse
What OS does your phone boot with?
bad flash rom, you need junk the phone or donate to XDA-developers
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
da_jojo said:
first take out the sd card.then flash your phone with buttons 1.0 rom.hardreset. then flash it again with buttons rom. unlock the device totaly with the unlock software. hardreset. flash with original t-mobile us 2.26 rom
halfway above 80% pull the usb plug. the phone get stuck and the update program will tell you it doesnt respond. reset the phone (little hole on the side) you will see the 3 color screen . now restart the 2.26 update and when
you get at the part that it starts looking for the phone connect it. sometimes
it just works , sometimes you need to try a few times.. it wont ruin the phone
as i had this many times due to a crashing computer. wjen its done do a hardreset and install the rom you wanted.
hope this helps you guys
Click to expand...
Click to collapse
Out of curiosity when I downgrade to any of these roms am I looking for the OS to downgrade or just the IPL/SPL?
cgigate said:
bad flash rom, you need junk the phone or donate to XDA-developers
Click to expand...
Click to collapse
how is it a bad flash rom if the IPL/SPL and GSM all change everytime i change roms. The only thing that doesn't is the OS.
Phone is 750v, recently updated to WM6.0 from the Treo website under the 2.18 version, branded to Vodafone (starts up with voda logo), but not locked to telco providers (can change sims).
I've exhausted all me options and info from the various forums.
I've tried everything from kaiser hardspl, kaiser custom ruu, using the sd card to install the cheeimg of the 6.1 rom, cheetahunlocker, hardspl 1.1/2/3 and so on, and etc related programs. Practically everything.
Upon installation progress of ROM, either at 1 or 7% the screen either goes black/blank and the device restarts or the error 207 appears. For smaller .nbh files, progress hits 100% and within split second screen goes black/blank. The rom is not updated in any of these circumstances
I am able to restore the rom using the application downloaded from treo website. By that I mean even restoring 6.0 over 6.0. This concludes that it is possible to install rom updates using the treo provided app.
But not other apps. I'm exhausted. Do not have a solution.
Does anyone know how to resolve these issues to upgrade rom from 6.0 to 6.1.