Related
I have searched read and looked all over the board.
The problem very specific.
I have a stock MDA Compact with the T-Mobile Software installed.
I want to convert the phone to its O2 equivalent with all the bells and whistles.
Whats the best way to go about this?
Is there a UK O2 rom i can simply upgrade the unit with?
What extended Rom software do i install?
Thanks.
Backup your important data, hard reset your phone, and let the phone have its OS reinstalled. As you just finished the security (pin) setup page, soft reset your device (e.g. when it pop up a window saying that it will install etc etc software).
Get the O2 ROM from the xda-dev ftp, and install everything in the Exetended ROM, and you should have your O2 eqv.
hanmin said:
Get the O2 ROM from the xda-dev ftp, and install everything in the Exetended ROM, and you should have your O2 eqv.
Click to expand...
Click to collapse
I got the files from the ftp yes. Unfortunately the Extended rom is read only, how do i edit the attributes?
i can also install from an SD card, but i want to have these files permanently in the ext rom.
thanks again Hanmin
You should execute the O2 cabs from your sd-card. Or permanently flash you rom with the O2 rom to get them in your ext-rom. The ext-rom is read only & can only be written by flashing your rom or turning it into BIG Storage. To flash your rom to O2 you need MAUgradeUT_noid & the description from http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade
Regards, M
Doh, of course how could i forget, the very definition of ROM, read only.
Well i executed the Autorun from the SD Card, but its installed all the T-Mobile stuff again, (which still resides on the ROM).
I would execute the cabs individually from the sd but im not sure which are meant to be installed for my network.
After a few errors running the upgrade previously your instructions have now worked.
albeit i had to put the phone in bootloader mode after step 5 and before step 6
oltp said:
http://wiki.xda-developers.com/index.php?pagename=MagicianRomUpgrade
Click to expand...
Click to collapse
I want to replace the tmobile rom with an O2 set of files (an O2 ROM?).
How do i go about this? ( ie Keep the ext_rom )
I gather its the same as flashing a big storage ROM to the phone excepts the nbf will have the O2 files i want instead?
Thank you all for your time
is there a way to revert from a new rom back to the factory rom... if i didnt back it up to begin with. i have a xda mini s and i upgraded and now i want the old rom back.. is it possible? and how?
KwaZyLiLoBoY said:
is there a way to revert from a new rom back to the factory rom... if i didnt back it up to begin with. i have a xda mini s and i upgraded and now i want the old rom back.. is it possible? and how?
Click to expand...
Click to collapse
It's only possible if you find a dumped rom or a shipped-rom which is the version as the one you had before. Maybe your provider has a shipped-rom on its web-site? Or take a look at the ftp and maybe you're lucky to find one. If you find a shipped-rom it's easy, connect via usb & start the exe file. If you've got a dumped rom you need to change the header of the downloaded with your own device's header, write everything to sd & have the bootloader update the rom.
frantyk said:
Well i executed the Autorun from the SD Card, but its installed all the T-Mobile stuff again, (which still resides on the ROM).
Click to expand...
Click to collapse
The have the autorun starting files on sd, you need to edit it a little. It got hard-coded path & filenames and some instructions to prevent userinput (thus locking the keys & keyboard).
frantyk said:
I would execute the cabs individually from the sd but im not sure which are meant to be installed for my network.
Click to expand...
Click to collapse
Now you got me puzzled. Do you want the O2 CE-rom or just the ext-rom & keep the TMO network settings? Cause the CE-rom isn't much different for all providers, it's the ext-rom that does the customizing & changes the network settings.
So if you want an O2 ext-rom with TMO network settings I suggest you first write down your TMO settings for gprs, voicemail, mms & sms & then flash it to O2. You might even try to update the ext-rom only. It's possible to update to radio by supplying the radio.nbf only to the romupdateso I think it's possible to update the ext-rom by itself too. Can't remember the nbf name, but nk.nbf is your CE-rom & that makes only one left, isn't it.
You can use WinCECabmanager (10 trial executions) to see what's in all those cab-files.
Good luck to all of you, M
I think frantyk meant that he wants to keep the original t-mobile (mda compact) ROM while installing the customization (ext rom), such that the 'OS' is relatively the same while having O2 stuff in it.
Anyway, I think if you downloaded the correct O2 ext rom, you can install everything one-by-one manually, it shouldn't give any conflict. I'm not sure why, when you run Autorun, it install t-mobile stuff, probably the autorun is pointing to the ext rom.
You can unlock the the wizard ext rom unlocking cab, delete everything in your ext rom (MAKE A BACKUP FIRST), and copy the O2 stuff in. You should able to 'lock' the ext rom back in place. Then hard reset your device, you should have everything, including O2 stuff installed. I unlocked my ext rom before, but I can't remember if this is the one I used. --- IMPORTANT --- I've unlocked my ext rom with this cab before, but my device is a HTC Charmer, which is very compatible with Wizard. I'm NOT SURE IF IT WORKS ON MAGICIAN. You may want to look around the forum to find a ext unlocker for Magician, just to be safe.
The Magician ext-rom can't be unlocked, only flashed or turned into BIG Storage. Though I think you can flash the ext-rom only, the safest way it to flash the whole rom with an O2 shipped-rom. This will be the only way to get the correct ext-rom being executed after a hard-reset. Indeed the autorun contains a path & is unusable from sd without changes.
BTW not many people want the O2 stuff, I guess it's about network settings only. Which are on the web too, can't remember where :-(
M
What i want is the Standard CE software (ie no branding what so ever) which i think i have achieved with in flashing the phone with Shipped ROM WWE_11300_550_11200 - although it has the Qtek boot logo.
Im also using some of the Cabs from Extended Rom O2Mini_WWE_1.11.922
Why does this Ext_Rom not have and network auto config for O2 UK? Where can i get and Auto config cab for UK O2?
I want to use the phone mainly with an O2 Sim card, so i need al the O2 settings for GPRS and that, 2nd priority is having the T-Mobile GPRS settings cab for when i occasionally change chips but this is less essential that the O2 settings.
What does WWE stand for? My guess was XXEuropean?
Thanks
OK, unbranded CE is either the mentioned QTEK or any BIG Storage rom. Don't worry about the splash that can changed very easily.
WWE means World Wide English.
The network settings can be found here http://www.cctvsafe.com/support/phone_settings.htm
Cheers, M
hey.. what ports do you use for proxy, if you do use one..
Hi I am new to all this.
I have an XDA EXEC, copied the T-mobile rom all works fine...except thebusual crap GPRS/3G reception.
I was looking at installing WM6 today....
Which file is the best/most stable at the moment there are many threads with many updates etc..
What do I gain by upgrading to WM6..
I am sure I am not the only one to ask this question
I to have an xda exec looking to install WM6 it is an old one from o2 since i only hear new ones can have WM6. So please help me to obatin the right file or rom as people have called it, i have done a search and found a few things related to WM6 but not sure whats stable and right to use before bricking my xda exec.
badman112 said:
I to have an xda exec looking to install WM6 it is an old one from o2 since i only hear new ones can have WM6. So please help me to obatin the right file or rom as people have called it, i have done a search and found a few things related to WM6 but not sure whats stable and right to use before bricking my xda exec.
Click to expand...
Click to collapse
Hi there
If the instructions are followed as written, it would be quite hard to brick your device.
As a start you could try Jwright's WM6 rom version 2.02.02, works great for me & I don't have any wifi bug (I use wifi a lot).
I say it's a good starting point as it is an executable upgrade (make sure to d/l the correct one for your device) just like the OFFICIAL roms, only it installs WM6 instead of WM5.
Download that one and give it a go.
That rom is very simple to install as it is a single executable file, with the whole package contained within.
All I did was
D/L the ROM for my device (jwrights 2.02.02, locate it in the forum).
Unrar it somewhere to my pc.
Put device into bootloader mode (power,backlight & reset) a screen with no backlight appears with the words serial vx.xx (x.xx being your version of the bootloader) you may need a torch to see it.
Connect device via usb.
Execute upgrade (file that you unrared to pc)
Once finished (about 20mins or so), unplug device & perform a hard reset (both softkeys & reset until the white option screen appears) and select "Restore" from the options. I believe it's 0 (zero).
This also upgrades your radio rom to the latest V1.15.
Happy bricking!
OOPS I mean upgrading.
I am a noob .... Just trying to get up to speed, so to help me understand this stuff, I have 2 questions.
1. Should i be able to extract an official T-mo wing ROM ...... and then be able to cook it to produce an identical/ almost identical rom to the t-mo stock? I understand there is no point in doing that..... but it helps me understand it better if I know this answer..... plus I was wanting to do that first as a benchmark .... so that I at least know I am doing everything right ... then start making changes from there.
Maybe a simple alternative question, the t-mobile stock rom has t-mobile specific OEM content (my faves for example) in it..... how would you go about extracting then baking that into a custom rom? Is that even possible?
2. when you flash to a signed Rom image nbh file ... What is it replacing (ipl, spl, OS, splash, radio, xip, imgfs)?? all of those things or just certain ones? Do different nbh files replace different compenants or is it consistant to where an nbh file always replaces the same thing?
I see in some of the kitchens... you can bake in your own radio, splash screen, etc... which got mo to thinking .... what will be different with the rom between baking one of those in vs not? It seems like it is optional.
Thanks
i would like a answer to this question myself...im only interested in the part about tweaking the original stock rom..can we beef it up at all?..change the pagepools..ect?
Originally quoted from JPick:
Just trying to get up to speed, so to help me understand this stuff, I have 2 questions.
1. Should i be able to extract an official T-mo wing ROM ...... and then be able to cook it to produce an identical/ almost identical rom to the t-mo stock? I understand there is no point in doing that..... but it helps me understand it better if I know this answer..... plus I was wanting to do that first as a benchmark .... so that I at least know I am doing everything right ... then start making changes from there.
HERE is a kitchen with the only two updates from tmobile, that are considered "stock ROMs;" cook with this kitchen to make a ROM that is with the WM 6.1 builds. This will show you what is involved in cooking a ROM that only has stock - OEM - packages. Also, don't forget to use 'LZX Compression.'
You can find the kitchen that I use HERE. The 23563 build is what I use (for reference). Use this kitchen from my guide to build a ROM with the latest build.
Maybe a simple alternative question, the t-mobile stock rom has t-mobile specific OEM content (my faves for example) in it..... how would you go about extracting then baking that into a custom rom? Is that even possible?
You may be able to extract certain packages from the stock/update 6.1 ROM that you may be able to use in cooking a 6.5 ROM.
2. when you flash to a signed Rom image nbh file ... What is it replacing (ipl, spl, OS, splash, radio, xip, imgfs)?? all of those things or just certain ones? Do different nbh files replace different compenants or is it consistant to where an nbh file always replaces the same thing?
Everything that you'd find in a true/stock update ROM you'll find in a cooked ROM.
I see in some of the kitchens... you can bake in your own radio, splash screen, etc... which got mo to thinking .... what will be different with the rom between baking one of those in vs not? It seems like it is optional.
Unfortunately, I don't use that kind of kitchen. I feel it makes my ROMs a little bit more 'bulky;' my ROMs seem to not compress as well with the newer kitchens, therefore, I don't use these options you're talking about. So, I apologize, I don't really know the answer to this.
Thanks
You're Welcome
Originally quoted from idunnoV2i:
would like a answer to this question myself...im only interested in the part about tweaking the original stock rom..can we beef it up at all?..change the pagepools..ect?[/QUOTE]
Yes, you can change the pagepool.
Hi there,
This my first post, so I'll try to be short and to the point.
I just bought an sim-free HTC Radar (7720) from Expansys Japan, hoping to make a present to my Spanish mother. To my surprise, although my Japanese IS12T WP7 had several languages including Spanish, the HongKong market Radar Expansys sold me only has English and Chinese.
Since then I've been desperately trying to get a way to add Spanish display language. Found this thread on xda and thought I was saved.
Being a noob I did read every single post in the 85 pages before trying anything, unfortunately I still can't get Spanish display menu...
Here is what I did:
1) Checked I had latest Zune software (I'm running W8 CP 64bit)
2) Updated the radar up to 8107 through Zune (first 7740, then 8107).
3) Downloaded and installed WP7_update_tool
4) Downloaded and extracted WP7_Update_Cab_Sender
5) Downloaded all the Spanish language update cab files (1 for Nodo, 2 for Mango), and added them to the WP7_Update_Cab_Sender folder
6) Run the bat file, then choose "B" for backup+update
7) After a while, and a few restarts both the Update utility and the phone showed the message "Update successful".
I then went to change my display settings and found out that I still only had English and Chinese available...
Is there something I missed? Do you have any suggestions?
Right now the only thing I can think about is that maybe I shouldn't have used Zune to update. Should I try to roll back to 7740 with Zune, then update to 8107 using the Cab_Sender instead?
Thanks in advance.
Well, I got impatient so just tried to restore to the previous version using Zune...
Tried already 3 times, no particular error messages and everything seems to go fine. Yet at the end I always end up where I was, at 8107...
Am I stucked in here or is there something else I can try?
Any way of getting my phone back to 7720, or any idea of whether that would help me solve my problem ?
Having Spanish support is much more important than getting future updates... so that's not an issue...
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
GoodDayToDie said:
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
Click to expand...
Click to collapse
Thank you so much for your reply; now:
- I understood what I did wrong (over-write my previous backups when I run CAB-sender...
- Have some hope to get it done.
My hardware is: HTC Radar C110e, but unfortunately I found no file matching my current Firmware/Bootloader:
- Firmware: 1600.2200.20301.708
- RadioSofware: 16.23.03.17_16.27.00.23
- Bootloader: 2.3.160015.3(134621)
So additional questions:
- If I get one of these European ROM's, will I get also the language packs delivered by default in the European region (which include the one I want, Spanish)?
- Will my phone be updatable through the regular Zune channel afterwards?
- Should I rather get the newest, oldest, or it doesn't matter? (assuming I'll get the updates normally)
Your questions, in order:
1. Yes. These are the ROMs which are distributed on retail phones, and should include the standard language set for Windows Phones (which I'm pretty certain includes Spanish for the European phones, although I've never checked).
2. Yes. Flashing a stock ROM will make the phone behave exactly as though you'd bought it with that ROM, and it should work with Zune like any other Windows phone (including being updatable).
3. I suggest going with the newest ROM on that list, because it has the same major version number for its bootloader (2) and same revision version number for its radio (03). This reduces the risk of it not flashing correctly for some reason. That ROM is also 7740, so it will need fewer updates after flashing.
Do keep your restore point handy, in case the flash fails for whatever reason, but it shouldn't be needed. You can try recovering older restore points using the "Previous Versions" feature of Windows (requires Volume Shadow Copy service to not be disabled, and System Restore to be enabled for you user-profile disk and set to backup user files as well as system files).
Flashing a European ROM really seems like the best bet, though. You'll need to start the phone into SPL (bootloader) mode, which I believe requires turning off the phone, pressing and holding the Volume Down button, and turning it on again. You should see a screen with bands of color and info about your SPL in yellow text. At the bottom will be black text saying "Serial". Plug the phone into the computer. It will install some drivers (automatically, on Vista or later; on XP you may need to do this manually) and then the text at the bottom of the phone's screen should change to "USB". At that point, you can run the ROM Update Utility (RUU) that should have come packaged with the ROM image.
Thanks again for your precious help. It seems that's exactly what I need.
Now, sorry for asking again, but after a few hours I still couldn't find a suitable RUU... The links you gave me previously pointed to the ROM images only, any idea of where can I find "the RUU packed with those images"? Or "how to pack them myself"?
I did find a few threads in xda with a link to a RUU (here) , but it's only for the oldest version. Then they provide additional ROM images (.nbh), but it's not clear to me how can I pack those into a RUU.
Finally, I did find this other thread where someone was kind of explaining how to do it, but it seems the OP didn't even get it to work to begin with, so it doesn't feel reassuring...
Any further guidance would be appreciated.
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
GoodDayToDie said:
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
Click to expand...
Click to collapse
Well, thank you in any case for your kindness and having taken me here.
I think I'm ready to try … Just made up my mind to go in the following order:
1) Give a shot to the original RUU file (even though it has an old build of my phone); then hope that Zune updates come as you said they would (my phone unbranded phone came out of the box with Mango 7720 and it took only a few minutes to get the latest version).
2) If updates don't come, try to modify the RUU file with the newer ROM to see if I have better chance...
I'll be back to report what happened.
Well, I tried both the old and the newer ROMs, and:
- on the good side: my phone didn't get killed in the process
- on the bad side: I get an error message saying "ERROR [294] : INVALID VENDER ID" no matter what...
The ReadMe file says:
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
So I guess I'm slowly reaching a dead end... Someone has any further suggestions???
any updates here ?
Hello,
I updated my HTC Trophy using Seven Eighter. While the update itself went fine, I've missed some language packs as my system menus won't open. The Office WP7 Updates thread is an excellent resource, but at this point I'm having trouble determining which language packs I actually need to push to the phone. I've seen Heathcliffs tool 'Version and Language by Heathcliff74.xap', but don't know how to get it to and run on my phone.
According to Zune (the only way I can seem to retrieve version info), my phone is at version 7.10 (8862).
I tried the Seven Eighter support tool, but it fails every time I attempt to send languages over. I tried just downloading and sending over every language cab update, but of course that failed as well.
Any tips/pointers/links someone can share to help me out?
Thanks,
Tim
What version was in your phone before you use Seven Eighter?
What is your current language?
many people reports problems after use seveneighter...
which ROM you have before use seveneighter?
dont have trophy but advice you to flash Dynamics v2.0 ROM for Trophy
http://forum.xda-developers.com/showthread.php?t=1523976
and use Zune to update from 8858 to 8862 (no need cabs files or others)...
with Dynamics ROM you have full unlocked phone and you can install XAP files
Thanks all. So I'm not sure what ROM I was on when I started Makes it much harder to troubleshoot.
Is it possible to download a full original ROM and flash that? The Dynamics ROM looks cool, but I would like to avoid going down the HSPL route (If possible).
Do I just need to get all English language packs up to my current ROM version to load for menu functionality, or do I need all languages loaded? I've had some luck getting a few English packs to load. Very tedious though.
Tim
why to avoid HSPL? you not loose anything (always you can go back to original SPL) and with HSPL and custom ROM you have unlimited possibilities and you can do almost anything...
with original ROM you can forget to add language or do any other things...