Problem Solved: Dead devices due to tmob 1.72 + Downgrade

[cairo31male]

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.

[ID64]

Unfortunately, i don't have device even with working bootloader :( And it stuck in TMObile screen :(

[cairo31male]

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 ....

[hcnsoft]

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,

[Ivan_R]

Okey.... I will try FIRST!! :D :D

[SEB152030]

please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks

[applecom]

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

[Panja]

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

[Ivan_R]

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? :cry:

[cairo31male]

@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

[Ivan_R]

@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

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?? :cry:

F@#$!%G FREAK ROM!! :evil:

[vwonges]

Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72

[applecom]

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

[SEB152030]

Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....

I found a solution : Here (http://forum.xda-developers.com/viewtopic.php?p=41544#41544)

[watchdogsdg]

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.

[Ivan_R]

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.

Go go go... Just downgrade it!! 8) Then you will join me in HERE!! (http://forum.xda-developers.com/viewtopic.php?t=8638) Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!

[mkriemersma]

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.

[Ivan_R]

So I'm guessing this downgrade problem may be specific to bootloader versions.

No expert, just letting you know what i did.

I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!! :oops:

[nilron]

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?

[cairo31male]

@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.

[Victor]

bootloader v 1.06 is locked. you will not be able to flash in the manner you are attempting, I believe.

there are or will be found ways around this, I am sure, but the cat and mouse game the OEMs play with the persons/forums(like this one) trying to keep up have lead to these types of situations.

Another example of this game is the new EXT ROM procedures for loading. The programs write a file to the windows directory and this is read back during the loading process.

When someone finds a fool proof method of replacing the bootloader ROM (fool proof in the sense that non-developers can do it), this may make most of these problems go away.

I think you are stuck, like a few others on the forum with that bootloader (just search for the very angry posts...)

[Victor]

Maybe the 1.06 people can get their problem solved in this manner

http://www.qtek.nu/default.asp?nc=4596&id=68&element=0

but I doubt it. Country ID error can be gotten around, but model ID error cannot (easily)

[nilron]

Hi

Well qtek 1.66 from www.qtek.nu does not work for me.

Model id error, can be bypassed by resetting when the screen becomes black, then the upgrade goes to upgrade rom ... with the rom 1.72 . radio etc.. klick next, goes to erasing rom and after a while a time out occurs.

I guess resetting also kills the process that should start and erase the rom.
But it also not for sure because if you can fool the program by switching devices, it can´t be depended on a program in a certain state waiting for the next command.

Any other suggestions?

And yes I cold not upgrade with SD cards, bootloader ver 1.06 ............

[watchdogsdg]

How can we determine which bootloader version our XDA II has without doing a cold reset?

Steve

[nilron]

Hi
This is from himalya upgrade program ver1.1, error text extracted from the exe file when loaded in memory, (of course this is only the order of the text apparing in the program not the logical order it may be executed in)

I guess this is the part when it goes wrong before erasing the ROM
If it is works by switching devices (that uses bootloader 1.06) it looks like it could be something with the crypt... and password..
Can someone with bootloader ver 1.06 confirm that the device could be upgraded by switching PDA.


If its not works to switch devices it could be something similar thats happen when you reset the device to fool model iD, losing the thread, have a look at "ContinueFlashEvent "

Any more suggestions?




+++++++++++++++++++++++++++++++++++++++++
5 F800

set 2 1

set 6 ffff

set 1 0

password wrong!

Connection with Serial
Connection with USB \\.\WCEUSBSH
PortTestEvent
COM1PortTest

COM2PortTest

\\.\WCEUSBSH009 \\.\WCEUSBSH008 \\.\WCEUSBSH007 \\.\WCEUSBSH006 \\.\WCEUSBSH005 \\.\WCEUSBSH004 \\.\WCEUSBSH003 \\.\WCEUSBSH002 USBPortTest

\\.\WCEUSBSH001 COM1
Failed to create hPasswordEvent event !
PasswordEvent
%s\RUULog.log
%s\NK.nbf
Exit USBReadThread!

Read thread exit

Line 572: USBSerialReadThread close !

Invalid password.
:A=A0040000 :A=A1FC0000

Failed to create hReadJumpCodeAreaOKEvent event for thread!
ReadJumpCodeAreaOKEvent ParserEvent
Line 2275:
WriteFAT0Fail==TRUE
WriteBinaryFail==TRUE
Error during CryptReleaseContext
Error during CryptDestroyKey
Error writing plaintext!
Error during CryptDecrypt!
Error reading ciphertext!
Out of memory!
Error during CryptDestroyHash
Error during CryptDeriveKey!
Error during CryptHashData! Error during CryptCreateHash!
Error during CryptImportKey!
Error reading file header!
Memory allocation error.
Error reading file header!
Error during CryptAcquireContext!
Microsoft Enhanced Cryptographic Provider v1.0
Error opening plaintext file!
Error opening ciphertext file!
Program terminating.

Error number %x.

%s
An error occurred in running the program.
download
:A=70010000 info 2
WriteFAT0 is fail
WriteBinary is fail
Line 509: Recive bootloader return false

Line 505: Recive bootloader return TRUE

Line 546: Erase complete!

:L=
port.c line 512: bLength!=TRUE
Port.c Failed to create hGetBootloaderVersionEvent event !

Port.c Failed to create hBootloaderGetPlatformNameEvent event !

Failed to create hReadA0040000Event event for thread!

ReadA0040000Event
Failed to create hBeginWriteEvent event for thread!
BeginWriteEvent
Failed to create hContinueFlashEvent event for thread!

ContinueFlashEvent
Failed to create Erase event for thread!

EraseEvent

Line 1490: Read file fial!


Line 1506: SendString
TXQUEUE,TXQUEUE
fial!

Port.c Line 1505: Request record 90 seconds time out


Line 1473: SendString
TXQUEUE,TXQUEUE
fial!

Upgrade Radio success

Stage 5 complete

Port.c Line 1110: Request record 90 seconds time out

line 1606:Send HTCE

rwdata 0 10000

[hbahaie]

dear cairo31

i just upgraded to tmobile yesterday, just for fun and trial, i want to downgrade to o2 or carrier devices, i didn't try any thing yet, my device working normally. Thank to Allah, i just read ur thread before trying to downgrade, is there any advice?, what will happened if i tried to downgrade as we do usually?

thank u very much

[watchdogsdg]

Hey guys what am i missing. I thought some of you were working on how to downgrade this Rom safely, not just a fix for when it f***s up. Then silence. Many of us are dependantly waiting for instructions on how to get rid of this T-Mobile ROM. XDA DEVELOPERS PLEASE HELP!

[cairo31male]

@hbahaie:

My advice to you is to wait and NOT try to downgrade for now, untill the Developers come up with a simple solution. If you absolutely have to downgrade, Solution 1 described at the begining of this post should work for you.


@nilron:

Yes, I can confirm both solutions described here were used with Bootloader 1.06 successfully.

[hbahaie]

dear cairoman
thanks for ur prompt reply, in fact, i tried allready to downgrade with many different roms, only till the confirmation screen with the upgrade icon ready to click on, but i regretted. Is this a positive sign, or it is normal, and problems usually occur afterwards?
another question please how to know the version of my bootloader and regarding solution 1, how to put my phone in bootloader mode prior to put it in cradle.

thanks alot

[nilron]

Hi, Thanks for the information.

Maybe its depends on the SD card I have tested SANdIsk 128, Dane-ELEC 256 with HAMA 8 in1 USB reader writer.

I have also Dane-Elec 512Mb and Panasonic 16Mb(not tested )

All of the above cards works fine when the XDAII is working

Which cards works for flashing ROM?
I am more than happy to buy a working SD card.

Regards,

[cairo31male]

@hbahaie:
If you get to the screen with different versions and the "Upgrade" button, all is going OK so far and I do not expect problems. To enter Bootloader, Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together. You should get the bootloader screen with the word "Serial" at the top and the version of your bootloader at the bottom e.x. "1.06". The screen will not be backlit, so it will be difficult to read, but you can still read it.

@nilron:
I do not think it depends on the card, since your cards work with other versions. I am using Sandisk 64MB.

[evolvd.]

Hey. Tried the SD ROM solution meantioned at the beginning of the thread.

Downloaded the 1.72 sd rom from post and copied to SD ok.

When in bootloader, says:

{

SD Download
=========

Sections=1
Not allow update!

}


I'm using the O2 XDA II. Is this SD ROM designed for the TMOBILE or O2 operator? If not O2, can we get an O2 version.

I originally upgraded to v1.72 using the instructions from the v1.72 thread, using er2003edit to change the operator of the upgrade [posted here: http://forum.xda-developers.com/viewtopic.php?t=8515&postdays=0&postorder=asc&start=100]

Anyone got an XDAII working using the SD ROM flash?

[ewdb]

I put on the following adress the last ENGLISH ROM UPDATE
The origin of this ROM is DANGARD

ftp://xda-developers.com/Last%20rom%20qtek%20english%20version%20RUU166130W WE_Qtek-Generic-ship/

Login & Pasword are : XDA (in miniscule)

Perhaps can this version help you.

EWDB

[Panja]

Just downgraded succesfully to Qtek 1.66WWE!!
No problems at all using solution one provided in this thread!

For anyone that want to know, I have bootloader version 1.01

[cairo31male]

Glad I could help.

For those who do not have a second device, you may want to try this:

http://forum.xda-developers.com/viewtopic.php?t=8903

It did not work for me, but it may for you ....

[dr_kaan]

Hi people,

I have the 1.60.00 wwe rom (12.3.2003) with radio 1.06.01 protocol 1337.16
ext.rom 1.60.06 (i think it's the dutch rom)

The original rom was t-mobile german, the device is t-mobile mda 2.

Should i upgrade to a new version? I've been reading the forums for some time and i saw people who are "very happy" with the new rom 1.72 and some people say "their device is DEAD!".

Any comments?

Thanks

K.G.

[noone]

Hi folks

though i'm not sure if this is still of interest i'm posting my solution to the downgrade problem.
I had my unit repaired for a broken screen and while they needed >1 month (!) to replace the LCD they also installed 1.72.01_ger_o2. My backup which was based on 1.60.52_ger_o2 was incompatible then.
Trying to downgrade I ran into the same problems described here and this is what i figured out:
- himaupgradeut v0.9.1.0 (from 1.60.52) crashes when 1.72 is installed
- himaupgradeut v0.9.1.0 errors about "model id" when nothing is installed after this crash
- himaupgradeut v1.2.0.0 (from 1.72.01) errors about "checksum error" with 1.60.52 nbfs

you have to decrypt 1.60.52 nbfs to nbas with xda2nbftool, 0.9.1.0 procedure (cf. xda2nbftool wiki page) and to reencrypt these nbas with 1.x.0.0 procedure. then you can use himaupgradeut v1.2.0.0 to flash the recoded 1.60.52 nbfs.

Thanks for all the precious advice in this thread

Matthias

[Jimate]

Hey guys, I had the same problem after upgrading my i-mate (XDAII) from the original 1.72 to WM2003SE, it crashed a lot so i wanted to go back badly, I discovered a very simple solution:

1. Obtain the new .exe files for the new (original) version you want to downgrade to.
2. Run the file, it will unpack, then give you the welcome screen, do NOT press any button, rather, go to the temp folder, usually located in C:\Documents and Setting\your_name\Local Settings\Temp

andd....guess what? you'll find there all the needed .nsf files..
3. Obain the files, modify them with ER tool, and flash as usual.

Chheeeeers:)

[Danniel]

[thkx for the info.
but i got stock while upgrading so i got a V 1.02 in my screen
can someone help me??