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.
Same for me
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)
Same for me
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 think that (YYYYYYYY)is the missing point.
model ID and operator name
Re: Same for me
SEB152030 said:
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)
Click to expand...
Click to collapse
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?
Count me in!! :evil: F%@$#&G FREAK ROM!!
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?
Re: Way around the model ID 100 error...but still in the @#$
Victor said:
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.
Click to expand...
Click to collapse
Victor, how to downgrade, or put bootlader? I currently have running machine, but no bootloader
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.
Problem Solved : Dead devices due to tmob 1.72 + Downgrade
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
http://forum.xda-developers.com/viewtopic.php?t=8606
Re: Problem Solved : Dead devices due to tmob 1.72 + Downgra
cairo31male said:
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
http://forum.xda-developers.com/viewtopic.php?t=8606
Click to expand...
Click to collapse
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:
Related
My xda ii have Rom with DeviceData.txt
U S B 3 2 1 . 7 2 . 0 0 W W E P H 1 0
Q t e k W W E 1 . 7 2 . 6 0 1 1 . 1 4 . 0 0
I want to up Rom to new rom 172.181 but I cant because Country ID error N-5-1-1-1.
Please help me! Thanks
Take a look at my post here.
Hello! I've been trying the few past days to upgrade my XDA 2 to Win 2003 SE but I've made one huge mistake
Somehow I've change "MyDeviceData"
U S B 3 2 2 . 0 6 . 0 0 W W E
P H 1 0 P H 1 0
- C D L
1 . 1 8 . 0 0
I've chage my language to CDL may be?
When I try to install any ROM I've got Language Error.
PLEASE SOMEONE HELP.
I don't know what to do.
You are my last hope.
http://forum.xda-developers.com/viewtopic.php?t=16136
HTH
Fin
10x I hepl myself. I change the Language to CDL. Cuz the other thing doesn't help. 10x a lot
Here DataDevice.txt for me : (O2 XDAII)
U S B 3 2 1 . 6 6 . 0 0 W W E P H 1 0 O 2 CHT 1 . 6 0 . 5 0 1 . 0 8 . 0 0
I download Rom 2003Se but i can't up Rom . help me "CHT" what is ??? and download Rom where ??
Thanks
I’ve buy the T-mobile version of 2020
And immediately reflash it with English version of MW2003
Before reflashing HimaGetDeviceData.exe gives me following
U S B 3 2 1 . 7 2 . 0 1 G E R
P H 1 0
T M O B I L E
G E R
1 . 7 2 . 1 7 0
1 . 1 7 . 0 0
So in xda2nbftool I use Language: GER and operator TMOBILE everything was OK:
After reflashing HimaGetDeviceData.exe gives me following;
U S B 3 2 1 . 7 2 . 0 0 W W E
P H 1 0
C D L
W W E
1 . 7 2 . 1 2 6
1 . 1 4 . 0 0
I’ve found older Radio and extended ROM but it was not a problem.
Main that I have English in device. I was happy.
But today I decide to flash WM2003SE from XdA2JoJo.v3.2zS (respect)
When I use language WWE and operator CDL that I’ve get after reflashing. I've get error of wrong country code. :shock:
Trying the options from fist reflashing language GER operator TMOBILE I’ve get an language error (it was panic at first)
But finally I success using WWE language and TMOBILE operator :?:
Funny isn’t it ???
Is It should be so ??
Hello,
This is my first post in xda-developers
I came here to ask a question. How to install the lollipop AOSP got from this link: h t t p s : / / w w w . a n d r o i d f i l e h o s t . c o m / ? f i d = 2 4 2 6 9 9 8 2 0 8 7 0 1 0 4 6 0 (copy and paste without the blanks), (FreeXperia Project) to my Xperia E3 with TWRP Custom Recovery installed? I'm a noob in terms of rooting and custom roms. I am rooted (SuperSU) and unlocked my bootloader. I don't want to get involved with adb or anything command-related. Is this possible with TWRP?
Or, if it isn't, please help me with the commands as I don't want to brick my device.
NOTE: I have done a nandroid backup, so don't worry about that.