Hello All,
I recently upgraded my T-Mobile PPC to ROM version 4.00.16 (from version 3.14.40). I loaded it via an .exe created on Yorch. The installation worked without a hitch. The problem is, now I would like to reload another ROM version and cannot seem to figure it out.
This is what I have done so far: Floowing some of the post in the forum, I have:
Created a new ROM image (.nbk or nb1) on the Yorch website of the lastest official T-Mobile official ROM (version 3.14.40). Using theXDA tools program, I loaded the .nb1 file onto my SD card. When I try to load it onto the PPC, I get the message asking to format (yes/no) and I choose no. After that, I do not get any other messages on the PPC.
Is there some different type of bootloader protection in 4.00.16 that would prevent the bootloader from seeing the boot image on the SD card?If anyone else out there has ran into this problem or knows how I can get around it, I would greatly appreciate any help.
Thanks,
SB :lol:
Hi All,
After a little more investigating, I was able to flash the ROM on my PPC.
I read in a previous post that you could determine your ROM and bootloader version by powering on the unit while holding your stylus in the reset hole (the soft-reset hole- not the hard reset hole that is closet to the ear-phoe plug).
Anyway, I did that and noticed that my bootloader version was version 5.15 instead of version 5.17 which I thought was causing the problem. I then reset the unit again using the same method, but just held the reset button just a second longer and the boot loader menu came up and asked me if I wanted to flash the unit.
I hit the center key of the directional button and it started to load the ROM image I had created earlier and placed on the SD card.
So for whatever reason, it did not start automatically but started and ran fine once I kicked it off from the bootloader menu.
Thanks for the help that I know you guys would have provided if I hadn't stumbled across the answer.
Regards,
ssurfer :lol:
I am happy to hear that you solved your problem. These things can be a tad tricky, eh...
jta
Related
Hello All,
I was wondering if any of you were able to recover from this particular error:
I have a Qtek 1010 which I upgraded to ROM 3.16 and RS 3.19. I was really curious about ROM 3.15.15 as I had heard so much about it on the forums so I got my hands on a copy and tried to upgrade.
First, the Upgrade utility refused to work because I was trying to flash an older ROM with and already existing newer ROM. So I resorted to the Bootloader way. I backed up the existing Bootloader and ROM Image and wrote the 3.15.15 ROM back onto the SD Card. Unfortunately, I wrote the CLoader_usb.nb that came with the Upgrade Utility back onto the SD card. I booted up and flashed the ROM with the SD card, did a cold boot and nothing happens.
I charged the phone until the LED was a steady green and tried again. Nothing. I did note that I get a quick red LED flash whenever I press the Cold Boot button the second time, for example: press [red flash], press [no flash], press [red flash], etc.
If anyone has ever come across this problem and managed to undo it, please let me know.
Anyway, I guess it was my own fault, but it was not too clear on the website how to rewrite the bootloader because the example graphic says 5-15.nb0. So all you guys out there who are just getting into flashing you ROM the bootloader way, make sure you use the Boot Image that you backed up and not any other (unless you have a new Boot Image that you want to upload)
See you guys around.
I have exactly the same thing. See here: http://xda-developers.com/phpBB/viewtopic.php?t=3284
Have you found a solution yet?
CLoader_usb.nb does not contain a bootloader, so if you wrote that over the bootloader, you probably have permanently damaged your device.
you would have to look into this for a possible solution http://xda-developers.com/jtag/
Your guys' XDA are dead. How could your guys wrote "CLoader_usb.nb" to overwrite to bootloader!
Only hardware solution could bring the life back (I can help)!
If your phone is still on warranty, you could send back to them to repair or replace!
Please note, flashing is dangerous for newbie!
I've upgraded a couple of US T-Mobile phones to the latest AT&T radio stack and v1.1 of your special edition ROM. Both work really well - however on one of the phones I no longer seem to have access to Boot Loader mode by holding the power button on reboot.
It's not a problem right now, but I imagine it could be if I needed to upgrade at some time in future.
Does anyone have any suggestions as to how I might recover this functionality. Booting with a SD card holding a ROM image doesn't do the trick.
Thanks,
Malcolm
Strange.... Very strange....
Used the 1.1 ROM from Jeff's .exe ?
Yes it's Jeff's 1.1 image in both cases.
The only thing I can think of which might cause this is the fact that the phone with the problem has the 128MB upgrade installed by PocketPC Techs.
At the bottom of your page describing the boot loader it says "When some tests fail it will load the entrypoint of CE into the PC register (and jumps there...)"
I wonder whether it's failing on a memory check then jumping directly to CE....
Any suggestions would be very welcome. Do you think I might be able to update the boot loader via ActiveSync? I'm a little apprehensive as I don't want to lock myself out altogether.
Malcolm
The phone also does not recognise the additional 64MB of RAM through the T2TDisk driver. I had assumed that this was a problem with the driver software but now I see elsewhere on this forum that for others with similarly upgraded phones the driver works correctly.
I don't think it's a hardware problem as prior to the installation of the AT&T radio stack and the SER 1.1 ROM everything worked correctly.
Malcolm
I've experimented a little and I can certainly upgrade the Radio Stack and CE ROM using ActiveSync. Does anyone know of a mechanism by which I can re-flash the boot loader using ActiveSync? I imagine it's possible.
Malcolm
malcolmct said:
I've experimented a little and I can certainly upgrade the Radio Stack and CE ROM using ActiveSync. Does anyone know of a mechanism by which I can re-flash the boot loader using ActiveSync? I imagine it's possible.
Click to expand...
Click to collapse
This is the strange thing we've noticed:
The NBF files needed by "Programme A" contain a bootloader. In fact, when we did our first experments with adaptROM we forgot to put in a bootloader once, and that toasted a unit.
But now if we put in a bootloader, it doesn't seem to overwrite the bootloader in the device, which seems to contradict the fact that we toasted a unit by overwriting it with a CE.
More experimentation is needed, but preferrably after we succeed in flashing with JTAG (which we're making good progress on, BTW)...
I applied the latest NK.nbf file that was available from one of the FTPs listed in the groups and modded it w/ adaptrom. Didn't install right the first time (stuck on Upgrading screen) but I was able to get it to connect w/ Activesync and eventually did install. Seemed to go fine, rebooted and am now stuck on a screen that reads:
Test Only Not for Sale
(Microsoft Windows Powered Logo)
G324e4
R6.18.00
4.00.01
Anyone got any ideas how to get this thing working? I think my next step is to go to CompUSA and buy a PCMCIA SD adapter and start doing the SD flashes....do I have an alternative?
--Mike
Hey Mike,
Sorry to hear that your upgrade didn't go well. I have noticed that if you need to install WM2003, or downgrade WM2003, the bootloader flash method is the way to go.
I think that due to the fact that the 2003 ROM is a test/developer edition, they have not really bothered to have proper ROM Upgrade Utility support.
On to CompUSA, I guess...
Hey guys I just copied your posts with a call for help in the new version WM2003 thread. You may want to keep an eye over there if people step to the plate and list some helpful info for you mike.
I agree with you Sheran on the bootloader method being the cleanest way to do it.
Unfortunatly not eveyone has an NT based machine, or the swager to go this route so hopefully the people who have had no trouble using upgrade utility will post. :roll:
Cheers guys,
E
I've managed to get myself stuck up a dead end.
My device: Orange UK spv c500.
SPL: 2.00.0013
OS: None!
I upgraded to wm2005 but despite updating the reg keys posted by subliminal I couldn't install the certificate I use to ActiveSync with my Exchange Server; so I decided to downgrade.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
My next mistake was to try and re-flash the 'phone with the latest Orange UK ROM (v4.2.1.1). What I'd forgotten was that this updates the bootloader at the same time.
The flash appeared to go fine, but on restart I'm stuck in the bootloader. When I attempt to re-flash again the summary in the RUU says "Image Version:" ie no image version present.
If I was still on a v1 bootloader I'd be able to run IU_SPL+PatchedRUU again to give me an IU mode bootloader. With a v2 bootloader I can run this as many times as I want, but it won't put a lower version on.
Without an IU mode bootloader I can't "r2sd spl" to use itsme's dowload tools. Without a working OS I cant use TyphoonNBFTools to flash the SPL.
Can you think of any other solution?
If there was someway to "con" the rom update process into installing an older version of the SPL I'd be OK. Alternatively if it was possible to change the version of the SPL in SPVDEVS-SPL.nbf I could get it on.
Thanks for your help.
robhughadams said:
I've managed to get myself stuck up a dead end.
I immediately realized my first mistake - I didn't have a backup of the old ROM on SD. Instead I downloaded one from a link in one of the forums and used psdwrite to put it on my SD card. I ran the update, but it failed and the device wouldn't start.
.
Click to expand...
Click to collapse
did you tried this rom backup with your card writer i used this one with psd write and it worked download this one and try it ;-)
greets { ps let me know if this time you sucseeded ;-) }
http://rapidshare.de/files/2633600/backup.rar.rename.html
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?