PDA

View Full Version : Way around the model ID 100 error...but still in the @#$!


Victor
17th May 2004, 07:15 AM
Lots are stuck in the mud now, and here are some observations I have made this weekend.

I am stuck in bootloader mode (1.06 is the new version).

things I have noticed about this bootloader (as I have spent lots of time with it...)

1. The Password BOOTLOADER is enabled on many of the commands (I understand it was not on the earlier versions) in this new version.
2. I have a bunch of XIP roms and even a few NB0 roms, and I cannot just "lnb" or "l" them over as they want start addresses and the lot (defaults do not work for either.
3. As I have access to another XDAII in the morning, I have not tried to erase the ROM on my device with the erase command. Even though I think that will solve the problem, I don't dare tempt fate again.
3a. A way around the Model ID error is to cold boot, or reset at just the right time in the upgrade program (this is when the device shuts off - or goes blank). This will then fake out the upgrade program and it will continue. However, with my problem, I get stuck at the first step of "erasing ROM". IT apparently times out as it is unsuccessful and gives you an error reading something like "there was a problem -- reset and try again" Since my problem is self inflicted (I upgraded but deleted the Radio stack and OS from the temp directory -- something the instructions tell you never to do --> but red letters or bold typing that little fact in the instructions may have helped me not to miss it!!)
3.b Maybe this info would help others in the same boat -- maybe not.
4. I am convinced that the problem is related to the new bootloader version and if I could down grade it, all would be well. But I am not that brave - would rather wait to D2S a good ROM from a good XDA2, then gamble further.

SEB152030
17th May 2004, 08:55 AM
Hi i'm on 1.72 too and I have the same problem.... impossible to downgrade... but my qtek still work and before trying to down.. i use the little software HimaGetDeviceData and I found something bizzare
before :
U S B 3 2 1 . 6 6 . 0 0 W W E P H 1 0 Q t e k W W E 1 . 6 6 . 1 3 0 1 . 1 0 . 0 0


After :
U S B 3 2 1 . 7 2 . 0 0 W W E ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ 1 . 7 2 . 1 0 4 1 . 1 2 . 0 0

(see atachement file)

SEB152030
17th May 2004, 08:58 AM
Hi i'm on 1.72 too and I have the same problem.... impossible to downgrade... but my qtek still work and before trying to down.. i use the little software HimaGetDeviceData and I found something bizzare
before :
U S B 3 2 1 . 6 6 . 0 0 W W E P H 1 0 Q t e k W W E 1 . 6 6 . 1 3 0 1 . 1 0 . 0 0


After :
U S B 3 2 1 . 7 2 . 0 0 W W E ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ 1 . 7 2 . 1 0 4 1 . 1 2 . 0 0

(see atachement file)

vwonges
17th May 2004, 09:29 AM
I think that (YYYYYYYY)is the missing point.
model ID and operator name

Panja
17th May 2004, 09:42 AM
Hi i'm on 1.72 too and I have the same problem.... impossible to downgrade... but my qtek still work and before trying to down.. i use the little software HimaGetDeviceData and I found something bizzare
before :
U S B 3 2 1 . 6 6 . 0 0 W W E P H 1 0 Q t e k W W E 1 . 6 6 . 1 3 0 1 . 1 0 . 0 0


After :
U S B 3 2 1 . 7 2 . 0 0 W W E ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ ÿ 1 . 7 2 . 1 0 4 1 . 1 2 . 0 0

(see atachement file)

I got the same devicedate.txt as yours.
Probably everyone that upgraded to the 1.72 rom has it ;-)

itsme can we work around this you think?
To upgrade and downgrade?

Ivan_R
17th May 2004, 03:28 PM
Count me in!! :evil: F%@$#&G FREAK ROM!!

ID64
17th May 2004, 04:21 PM
isn't that means we are stuck with this crapy rom forever? Since ID data is broken and none of the upgraders will recognize it properly :shock:

My unit is operational, but I've lost bootloader. Anyone know how to recover bootloader?

ID64
17th May 2004, 04:28 PM
Lots are stuck in the mud now, and here are some observations I have made this weekend.

I am stuck in bootloader mode (1.06 is the new version).

things I have noticed about this bootloader (as I have spent lots of time with it...)

1. The Password BOOTLOADER is enabled on many of the commands (I understand it was not on the earlier versions) in this new version.
2. I have a bunch of XIP roms and even a few NB0 roms, and I cannot just "lnb" or "l" them over as they want start addresses and the lot (defaults do not work for either.
3. As I have access to another XDAII in the morning, I have not tried to erase the ROM on my device with the erase command. Even though I think that will solve the problem, I don't dare tempt fate again.
3a. A way around the Model ID error is to cold boot, or reset at just the right time in the upgrade program (this is when the device shuts off - or goes blank). This will then fake out the upgrade program and it will continue. However, with my problem, I get stuck at the first step of "erasing ROM". IT apparently times out as it is unsuccessful and gives you an error reading something like "there was a problem -- reset and try again" Since my problem is self inflicted (I upgraded but deleted the Radio stack and OS from the temp directory -- something the instructions tell you never to do --> but red letters or bold typing that little fact in the instructions may have helped me not to miss it!!)
3.b Maybe this info would help others in the same boat -- maybe not.
4. I am convinced that the problem is related to the new bootloader version and if I could down grade it, all would be well. But I am not that brave - would rather wait to D2S a good ROM from a good XDA2, then gamble further.

Victor, how to downgrade, or put bootlader? I currently have running machine, but no bootloader

Victor
17th May 2004, 06:00 PM
I am having some devs look at it today. I am certain I can get it fixed today or tomorrow, but not sure of which approach is best here -- hence the developer involvement.

cairo31male
18th May 2004, 03:46 AM
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade

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

Ivan_R
18th May 2004, 12:08 PM
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade

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

NOT YET, Man!! Mine still not working!! Maybe the diffrent version of the BOOTLOADER? Mine is v1.03. Do you know how to work around BOOTLOADER? Upgrade it maybe?

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