OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
Problem: New version changes Device ID, as well as ID format.
If you upgrade to tmob 1.72, you cannot downgrade back, as you cannot supply valid NBF files for the new device ID. If you try to play around, you end up with a very dull bootloader screen "Serial V.1.06", and nothing more can be done. SD card images cannot be flashed due to the same reason.
Untill our developers come up with a simple tool, the following 2 solutions can be used to get out of the disaster:
Solution 1:
(tested and 100% working for both dead devices stuck in bootloader and devices working but stuck with the tmob 1.72 version.)
You will need a working device (with old ROM before 1.72), besides your dead one.
1. Prepare your DEAD device in Bootloader mode. Don't connect it yet. (If it is still working but you want to downgrade, press Power+Action+Stylus, if it is already stuck in bootloader, just reset with stylus).
2. Connect your WORKING device, with OLD version via activesync.
3. Start the rom installation of your choice normally, with a version compatible with this WORKING device (Official or Modified NBF files via HymaUpgradeUT). If you don't know what I am talking about, just use your official file downloaded from your WORKING devices' provider).
4. Press NEXT, untill you are presented with the Current version and the one that will be installed. DO NOT click "UPGRADE" yet. (If you got an error so far, you are not using the correct version for your working device.)
5. When you get the dialog with the versions, disconnect the WORKING device from the craddle and connect your DEAD device, in bootloader mode.
6. Click "UPGRADE" and go get yourself a drink.
Et Voila.
Thanks to Victor for inspiring this solution.
Solution 2:
If you don't have another working device, and only have a dead one stuck in BootLoader, you can flash the attached image, through SD card. It will bring back your device to life with the BETA tmob 1.72 CE ROM.
Write the image to the card using "NTRW". Info on SD images and NTRW can be found in this forum.
Unfortunately, i don't have device even with working bootloader And it stuck in TMObile screen
I am sorry I have no solution for screwed Bootloaders, but if your device loads into the tmob screen, there must be something there still working. The only thing I can advise is to try to hard reset and not go into the extended ROM setup files (Soft Reset right after the Hard Reset and welcome procedure), but I guess you don't reach that far ....
What is about for XDA 1?
HI !
I have a Dead XDA. The bootloader is OK. How can I do with it ?
I need some advice for doing it, please !
Best reguard,
Carlo & Victor... You are GREAT!!
Okey.... I will try FIRST!!
please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks
When i posted the T-mobile 172 rom i did not know how much greif it would cause people, sorry to everyone for this
As to the second solution using the SD card is it possible to use this method on a working XDA2.
Basically i have a UK XDA2 and of corse i getthe ID error if i run the upgrade, i dont understand very well how to change the ID part so could i just make the SD card with the rom on it and follow your instructions to recover a dead XDA2
Thanks
John
What should I do when I want to upgrade/downgrade...
I have the T-Mobile 1.72WWE rom installed.
Everything works ok for now, no problems.
But do I need to do when I want to upgrade/downgrade?
I don't have a second device so thats not an option
Please advise.
Thanks
To cairo31male!!
NOP!! Can't HELP!! Maybe the BOOTLOADER got the diffrent version? Mine is 1.03. Can u tell me how to upgrade the bootloader to 1.06?
And you mentioned about OLD version, what do you mean by that?
@hcnsoft:
The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.
@SEB152030:
The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.
@applecom:
If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.
@Panja:
Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
cairo31male said:
@hcnsoft:
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
Click to expand...
Click to collapse
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!
So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER??
[email protected]#$!%G FREAK ROM!! :evil:
Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant
anyway thanks for youe info
John
Solution 1
Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....
I found a solution : Here
Radio Stack Downgrade
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Re: Radio Stack Downgrade
watchdogsdg said:
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Click to expand...
Click to collapse
Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
Didn't have any trouble downgrading
I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).
IT WORKS!! everything went fine and is fine.
I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
This site is amazing. Thanks for everything.
Re: Didn't have any trouble downgrading
mkriemersma said:
So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
Click to expand...
Click to collapse
I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!!
Hi,
Thanks for all help!
I have a dead unit due to 1.72 ROm.
Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?
Is there anyone out ther that can disassamble the himalyprogram and
make a small program without error checking?
I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"
It works writing the image but my bootloader don´t loads any rom.
Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?
Any more suggestions?
@nilron:
Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.
I flashed a custom rom before the radio. Im not an idiot,,, Im just acting like one
I see that several threads say to simply flash with the official carrier ROM if you mess up and flash a custom a ROM without flashing the radio first. But I cant connect via usb to flash a official ROM. It says that the device is not connected. I thought I could just then flash using the SD method but I cant find info on how to do that with the official rom speciffically.
I have flashed many phones but left for about 6 months and it looks like just because I use to know what I was doing doesn't me that I still do. Please help Im stuck on the carrier logo. I can get to the bootloader but it doesn't do me any good.
use the sd card method.
http://forum.ppcgeeks.com/showthread.php?p=181044#post181044
you will need to unpack the sprint rom first using winrar, to obtain the RUU_signed.nbh file.
So there is hope,,, great!
What I couldn't figure out this morning was,,,,,, I downloaded the official Alltel ROM but from what I understand I need to place a file with a nbh extension on the card....
Its been on the splash screen all day,,,,,, I get off in a few hours,,,, I'll go over the link u gave me and see if it leads me to a nbh file. Thanks.
Hey all. I need a little help. I have the new ROM and have tried to start the Sprint TV. However, when I try to install the cab, it says my device is restricted from downloading this file. So, I got it from this site, but when I try to copy it to my phone, it says that the file cannot be transferred. I even went so far as to rename the file, but to no avail. Any help would be appreciated.
Thanks
Jeff
I can't help you... but... to make things a little easier....
please post relevant information:
Phone model
Carrier
Bootloader version
Radio Version
Rom Version
(Did you install the Carrier's CAB?)
You might get a better answer
Hi all, I've purchased an HTC Mozart T-Mobile (German) branded, the firmware version number is 2250.09.12301.111, the phone is sim lock free but the only available languages are German and English UK; I live in Italy and i would have my own languages on my phone, so, which Rom I have to use to unbrand the phone and get italian language? Thx all
I second that.
Can someone post a detailed description as to how to unbrand Mozart phones for noobe?
For example I have those versions installed:
Firmware: 2250.09.12505.111 (--> 1.25.111.05)
Radio: 5.50.09.18_22.24.50.09U
How do I know my CID?
I can't find any guide to find CID please someone help us!
Firmware 2250.09.12301.111
Radio 5.50.09.18_22.24.50.09U
Bootloader 1.23.2250.1(110315)
I suppose that the "easiest" method here is to try every type of ROM and one that won't give "invalid vender id" error is designed for your CID as well. That's how I found that I have HTC_Asia branded version.
Isn't that method a little risky for the phone?
phoenixx666 said:
Isn't that method a little risky for the phone?
Click to expand...
Click to collapse
It is! That is how I killed my Orange-UK branded mozart.
Isn't possible to restore the phone whit the original firmware when bricked?
Yes, it should be fine IF you have the original ROM. But if you can, and you should be, use the gold card method to debrand your phone. It is actually quite easy if you follow the instructions.
The phone is already sim lock free, i would load a rom with italian language (i'm italian and the phone (T-mobile DE) have only german and english language), anyway a will give a shot today, later i let know you if my phone will be alive
Um.. I don't see how trying to flash ROM WITHOUT gold card can kill the device. It checks CID and if ROM isn't compatible with device, it won't flash at all. It is done BEFORE flashing. I tried flashing HTC_Europe this way - didn't start with this "invalid vender id" error. but it did work with HTC_Asia one and after flashing I got my device in the state I first ran it (with Australia settings)
Sorry, I'm a newbie
P.s. What's gold card?
nayato said:
Um.. I don't see how trying to flash ROM WITHOUT gold card can kill the device. It checks CID and if ROM isn't compatible with device, it won't flash at all. It is done BEFORE flashing. I tried flashing HTC_Europe this way - didn't start with this "invalid vender id" error. but it did work with HTC_Asia one and after flashing I got my device in the state I first ran it (with Australia settings)
Click to expand...
Click to collapse
Sorry to say it but you are wrong. This is exactly what I thought and I downloaded a ROM from Ansar. I thought it will give me an error if it is not compatible. But lo and behold, I received no error and the flashing process started. I was even happy and surprised. But the progress stopped at 11% and then told me my phone can not be flashed due to write error or something like that. Every time I put it on thereafter, it goes straight to the rainbow bootloader screen.
I had to go back to my HD2/7 until Ansar posted orange-uk rom which helped restored my phone. I have since debranded it using the gold card method and then received the update.
Summary, IF you have your correct factory ROM, you apparently can experiment, but if not you'd better stay off. Wrong ROM may give you an error, but like my case it may be only when your phone has been messed up.
abbas said:
Sorry to say it but you are wrong. This is exactly what I thought and I downloaded a ROM from Ansar. I thought it will give me an error if it is not compatible. But lo and behold, I received no error and the flashing process started. I was even happy and surprised. But the progress stopped at 11% and then told me my phone can not be flashed due to write error or something like that. Every time I put it on thereafter, it goes straight to the rainbow bootloader screen.
I had to go back to my HD2/7 until Ansar posted orange-uk rom which helped restored my phone. I have since debranded it using the gold card method and then received the update.
Summary, IF you have your correct factory ROM, you apparently can experiment, but if not you'd better stay off. Wrong ROM may give you an error, but like my case it may be only when your phone has been messed up.
Click to expand...
Click to collapse
You're totally right!
I had experienced the same: tried to flash an uncorrect ROM, had the same error, but - luckily - I immediately could re-flash the previuos and original one and everything went all right!
Well... Still I don't have italian language for the keyboard, but soon I'll experiment again!
Hello everyone,
Here is my story and the reason I am posting looking for someone with enough patience to help me.
I live in the UK and last week I purchased an HTC ONE XL on Ebay, I didn't realize that the phone was being shipped from Hong Kong.. When the phone arrived It had installed Android Ice Cream Sandwich, so far so good....
The first thing I did when I received the phone was to try and update the Android software through Software update.. and here is when my problems started.. It turned out that the recovery software of the phone had been replaced with CWM and hence I am unable to actually update the firmware as every time I do so the system boots into recovery mode and it doesn't allow me to run the ZIP file.
Doing a bit more research I found out that in theory using the correct RUU I should be able to stock/unroot my phone and then be able to install the original software again and be able to update my phone.. Unfortunately the CID of my phone has been changed to CID:11111111 and so far I have not been able to find the correct RUU for it.
After a few days of research I learned how to install custom ROMs and I am running now CyanogenMod 10.0 Stable release with gapps installed as well.
Now here comes the question and hopefully someone with more experience in the Android field might be able to help me out.. Is there any chance of finding out the correct model of hardware so that I can then find the correct RUU for my phone? When I tried to update my phone using OTA the phone got this OTA package downloaded: OTA_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_0.23a.32.09.29_10.128.32.34a_release_299070u0mcx8aiaku8jgn4, would this be of any help in order to identify the correct RUU for my phone?
I have been searching around the internet since I got the phone and doing loads of research but unfortunately despite the fact that I learned how to use Fastboot to flash the ROM, recovery image etc.. I have not been able to find this piece of information which should allow me to restore my phone back to default...
Some of you might be wondering why would I want to restore my phone back to the factory settings since CyanogenMod is really cool and boot much faster... yes you are right, I love CyanogenMod but I am having a bit of an issue with the text and icons in my Android device.. basically the text looks a bit strange and some letters do not seem to display correctly as they have funny shapes.. also the buttons appear with lines on them... so this made me think that the wrong firmware might have been installed and that due to this my phone could having issues with the display... not sure if that might be the cause...
If you guys could maybe provide some help with this or maybe point me to a threat that would help me find out how to identify my RUU that would be fantastic... I have been looking into XDA forums for a few days and although I found lots of very useful info I haven't been able to figure out how to match/find the correct RUU for my device since my CID has been changed as I already mentioned...
Thanks in advance
Wrong forum, this is the HTC One forum not the One x
Sent from my HTC One using Tapatalk 4
http://forum.xda-developers.com/forumdisplay.php?f=1538
i think this is the forum you need