I updated to the latest iMate ROM and want to revert back to the factory T-Mobile US configuration. I managed to flash back the OS and radio ROM backups, but the boot screens still show HTC. Also, it seems like the ext ROM is protected or something. I unlocked it and it's visible, but I can't copy to or from it. Lastly, what are the IPL and SPL versions? Is that not restorable from aWizard backups? Thanks in advance!
Related
I updated my T-Mobile MDA Vario from OS 1.6.2.2 to Qtek ENG 1.6.7.1 and the os is running perfectly.
The only thing im stuck at is the following: The extended rom customalizations from T-mobile NL **** up a lot of functions, like the today screen, error on boot.
I would like to use the Qtek ENG 1.6.7 Extended rom2 now but I cant seem to find how to change/replace/upgrade the Extended rom.
How is this done?
Unfortuneately any ROMs after 1.6.x.x have the extended ROM protected. If you really want to go down this route you would first need to use aWizard to backup your latest Qtek 1.6.7.1 ROM to a nba file. Then you would need to load back the T-mobile full ROM so that you could use aWizard again to backup the Extended ROM only.
You would then need to flash a pre 1.6.x.x Full ROM to allow you to write/delete the extended ROM contents.
Finally, you could copy the t-mobile files to the extended ROM and then reload the 1.6.7.1 aWizard backup.y
A word of caution though as I F**ked up my T-mobile wizard using aWizard to re-load my OS ROM, and as a result I have had to return the PDA for repair (hopefully under warranty??).
Apparantly there will be a new T-mobile ROM update in march - hopefully with the Bluetooth update we all seem to want!!
I have T-Mobile OS rom 1.6.2.2 whitch also haves the extended rom lock. I do have a backup of my t-mobile extended rom.
So I need to downgrade my os to a version older than 1.6.x.x and change the extended rom. Then I need to put my 1.6.7 version back?
Yes that's correct but first you would need to backup the 1.6.7.1 ROM only using aWizard before you downgrade to a pre 1.6.x.x Full ROM. This will make the extended ROM writable again then you can re-load the saved 1.6.7.1 nba file using aWizard - but note the warning!!
It goes like this, I have a cingular 8125 I updated it to 2.8.7 and it was good but it overwrote my extended rom, so to repair it I had to flash back to 1.5.4 and Overwrite the extended ROM with my Cingular backup I made with aWizard, so I have the extended rom fixed. So I used the aWizard to update just the OS ROM back to 1.8.11 from my cingular backup, but I noticed my SPL and IPL versions went from 2.?? to 1.?? going back to the 1.5 ROM. A side note when I do a hard reset it locks up while installing my cingular stuff from the extended ROM and it never did before. Any1 have any ideas how to use my backup to restore it completly or how to update the SPL and IPL or how to unlock the ROM on the 2.8.7 ROM ? Thanks alot!
A friend of mine gave me his TMobile (USA) MDA which is an HTC Wizard. He was trying to get it unlocked and upgrade to WM6. Suffice to say, he didn't know what he was doing. He never unlocked the CID but still managed to flash ROMs. He flashed the SPL to 3.08. Since he didn't unlock the CID, when the device boots up (when it hits the splash screen) it just freezes. I can go to into bootloader and I've changed the IPL to 1.01, 1.05, 2.26. 3.08. I can change the IPL, that's not a problem. I simply use the 2.00.1 No_ID RUU for most of it. The problem is this, in order to fix the device I need to go back to stock firmware/ROM (then downgrade to 1.05 and do a CID unlock). This is a T-Mobile device.
Unfortunately, with all non custom T-Mobile ROMs, the .nbf file is not compatible with 2.00.1. All would yield a File Read error. (this happens when the NBF structure is newer revision than the RUU version). When I try to use the RUU files to do the update (v2.6.0) it'll give me Error 296 Upgrade Only. I've trying using TyphoonNbfTool to rebuild the header on the T-Mobile file, but when you save the file, it'll only have the 2KB header. (I've tried replacing the Offcial ROM's header with the "corrected" one but that will just corrupt the file) When I try a newer patched version of RUU (v.2.5.2) I get Error 300.
I can strip the T-Mobile ROM, rebuild it with nb2nbf_wizard (which an older, compatible with 2.00.1 NO_ID, structure) and apply the flash, but it still locks up. I'm trying to get it to patch with an original T-Mobile USA complete ROM. After that I'll be able to apply a hard reset and then do a "r2sd all" from MTTY and have it back up and running. The OTHER option is to just unlock the CID via imei-check.co.uk and then do a hard-reset, but i'm sure it'll work.
What I need is a patched version of RUU v2.6 (NO_ID). Or a Original T-Mobile 1.x ROM. Help?
http://forum.xda-developers.com/showthread.php?t=316203&highlight=tmobile+rom
on the second post in that thread is a link I have of the last update for the us tmobile mda ipl/spl of 2.26 gsm 2.25. I think that is what you were looking for. hopefully it helps you out.
You can also find an english RUU in my sig that might help you also.
Thanks. I have an unpatched 2.X ROM. I've never been able to flash it because i'd get a File Read error on 2.00.1 (meaning the RUU is too old) and on the new versions weren't patched so I'd get UPDATE ONLY problems (probably because of 3.08 SPL on the device). I wanted an unpatched, original 1.X ROM because 2.00.1 NO_ID can patch 1.X kbf files without a problem. Hopefully the v2.5.2 in the link is NO_ID patched. That should solve my problems. So from here if I get File Read error, that means i need v2.6 (like in the original updater for the original ROM) or if I get 296 Upgrade Only, that means the v2.5.2 isn't patched. I'm going to try it out once I get it done charging
Hello,
i flashed my trinity with "AX3L_WM6_WWE_v3.0.7" rom, and then I flashed by my own backup rom from Orange Slovakia, but SPL in bootloader is still "SPL-9.99.CP", how i can change it to my original "SPL-1.07.0000 " for warranty?
Can I again cook my own rom version, but in rom cooker i add some spl nb file with proper version? Where i can find this file?
Thanks all for information
to flash back, you will need to extract the spl from the official rom upgrade from your phone using nbh tools or something...
you could reflash the official rom upgrade without manually entering bootloader, also... crash proof spl doesn't protect itself against being overwritten..
I can't seem to find which SPL comes with the tilt 2. I semi-bricked my phone and I need to flash the stock one back before going to ATT. Right now I flashed back the .87 SPL. Can anyone help?
It doesn't really matter. All Stock SPLs are the same as far as manufacturers are concerned, so long as it doesn't say OliNex I don't think anyone will check.
You could always flash the Shipped Exe from your supplier over the current .87 stock SPL.
Any more problems, please ask in the Hard SPL or ROM flashing thread.
Ta
Dave