hi all. A friend of mine gave me an S100, and after i played for a few days with it, i decided to update it's rom. A "country error" problem appeared,cause i have the greek version, so i ran MaUpgradeUt_noID.exe which completed (as showed 100% process). My (new) problem is that i cannot update anymore. Every time i enter boot menu, i ran the upgrade
(HTCMAG_ROM_WWE_O2.rar) following all the steps normally. When the device resets (so the upgrade is going to start), it's re-reseting again and showing ERROR 101 connection error. Any ideas?
Qtek Greek version
R 1.12.00
G 1337.42
D 1.12.00 WWE
P.S. apart the problem everything is function properly
Related
today i tried to switch my xda2 from t-mobile's 1.72.170GER final rom back to o2's 1.72.184GER final which has been provided recently. i run into that damn country code error 120 because my xda2 has got a t-mobile device id. please find my steps for solving that problem:
1. unpacked the 1.72.184GER package into a folder and replaced the original HimaupgradeUt.exe by the hacked one (which is supposed to ignore country codes).
-> result: same problem - country code error 120 : 1-3-1-1-1
2. then i deleted the HimaGetDeviceData.exe in the folder containing the rom-files. and i deleted any existing DeviceData.txt in the windows folder of my xda2. time to start again the hacked HimaupgradeUt.exe.
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom 1.72.01, radio 1.17.00, extrom 1.72.170 to rom 1.72.01, radio 1.17.00, extrom 1.72.184. i am happy so far but the next screen is again that damn county code error 120 message :-( meanwhile my device is stuck in bootloader 1.06 mode.
3. at this time i deleted the HimaClearJumpCode.exe (which is no longer needed for setting the xda2 in bootloader mode, it is already there) and started again the hacked HimaUpgradeUt.exe (the third time).
-> result: first screen with no errors. it tells me that my device is going to get an update, from rom "blank", radio "blank", extrom "blank" to rom 1.72.01, radio 1.17.00, extrom 1.72.184. next screen tells me that the devices rom is getting erased now and the progress bar shows the current status. everything went through the update process fine.
and my device has been successfully transformed from a t-mobile mda2 which looks like an xda2 to a real o2 xda2 with current xda2-software
summary: i guess you can shorten the whole procedure by setting the xda2 into bootloader mode connecting to your pc by usb unpack only the three rom file images into a folder, copy the hacked HimaUpgradeUt.exe into that folder and start it. but i have no time and motivation for doing that since my device works now.
best regards
peter
where to download hacked HimaUpgradeUt.exe
Dear
where to download hacked HimaUpgradeUt.exe
beast regards
:lol: :lol: :lol:
Thank you very much
Thank you very much its work now
beast regards
o2 ruu
i have tryed upgrading my i-mate to the o2 finaleng ruu with the help of dcs i got it to work with the acked file but now i have megga probs, no camera no extrom and no caller id file so i can't open pictures or video as they are looking for 'albam' to view them, can you suggest a way to get them back???
i have tried the upgrade a fair few times and am getting to the end of a short fuze..... if i run the upgrade direct from o2 i get a model id error, in the device data file i noticed that it has::
usb30 cdl uk5
cdl 1.70.00wwe ph10
or something like that..... it's the uk5 bit that is new..
any ideas :?:
Hi Guys/Gals
Before I return my device for warranty repair I thought I'd check out if anyone else has had this problem, and whether there is a simple fix.
My device has been running flawlessly (well almost) since I installed the latest Qtek ROM up until the following episode:
I sync with 2 PC's and noticed a couple of days ago that when syncing with one of these, the sync went on all day. I therefore 'soft reset' the device as this normally solves these sort of problems but the device failed to reboot.
After numerous 'soft resets' without success, I tried a hard reset, which gave me the 'push 0 to reset... x to exit' options and I slected 0 to hard reset. Still no reboot/response from the device. Then I tried the 'x to exit' option... nothing.
Removed SD Card/SIM and tried all the above again...and again... and again, all to no effect the device appeared dead other than for giving me the 'push 0 to reset... x to exit' options. No charging light etc.
So I tried to 'reflash'. The device successfully enters 'bootloader' (USB mode) and when I run the MauUpgradeNOID I get the message that my device is about to be upgraded to etc etc, then get the 'updating radio' progress bar as normal with the device screen also indicating that the 'radio stack is being upgraded...please wait' screen. As expected the software kicks me out with 'country ID error'. If I persevere and rerun the software I get back to the 'upgrading radio' bit and then it just sits there... for hours...
My device has (had) the latest Qtek ROM, with unlocked ExtendedROM where I installed just Wisbar and PhoneAlarm. Most of my other software running from SD Card.
I am completely frustrated!!! Can anybody help, or do you think this is a 'warranty' return issue?
ROM version: 1.30.77 WWE QTEK
ROM date: 02/20/06
Radio version: 1.09.00
Protocol version: 42.42.P8
Hi,
I just got myself a Siemens SX66 (USA Cingular Version). I checked the Device information on the phone and it went something like (To the best of my memory)..
PH20B1 1 B WWE E XGULA001 1.20.10 1 0 1.02.10 02.10
Now PH20B1 is telling me that it is a PH20B1 phone..versus a PH20B0.. But I actually managed to accidentally overwrite this data so it now looks like..
PH20B 0 B WWE E XGULA001 1.20.10 1 0 1.02.10 02.10 !!
What happened was this : This occured when I was trying to upgrade my ROM to the latest one that Siemens provides (From the SX66 Blue Angel Standardization Project). When I started the update, my PC lost connection to my SX66 when it went into bootloader mode and the Sx66 got stuck in bootloader mode so the only way I could get it out of bootloader mode was using the mtty commands posted here
http://forum.xda-developers.com/showpost.php?p=934239&postcount=12
Now, after using Mtty to get out of bootloader mode.. I restarted the update ( I was trying to update to 1.33.51) but the BAUpdater now throws an Error !! It says Device ID does not match !! So I checked the device information and surely enough, it had changed !! Now, obviously one of two things messed up the device information
1. The bad update attempt that locked the phone in bootloader mode
2. The mtty stuff i typed in to to get it out of bootloader mode..
The thing is, How can I get it back to how it was previously?
Can the DeviceData be reset or reprogrammed somehow? If someone could post the devicedata for an original Cingular SX66 Phone and tell me how to put it back on my phone I would really appreciate it..
PH20B1 = No camera
PH20B = camera
Ok, so the official update will not work but you can use the maupgrade_noid.exe to update your phone without the "id" check BUT I don't know if the firmware itself checks for the device id after the boot.
It's a risk you may take, if anything goes wrong I would sugest you to upgrade to WM5 because mtty is a dangerous software
i have been lookin' around to find help to unlock my tytn. Unfortunately everything i have done with the instructions found here were not helpful!
i do have a HTC Tytn with the following version:
ROM version: 1.18.260.2
ROM date: 07/22/06
Radio version: 1.03.03.10
Protocol version: 32.34.7010.01H
ExtROM version: 1.18.260.105
Model: HERM200
IMEI: 357719006002855
I’m using a XP Home Edition, 2002 version, and for some reason the HTC_Hermes_SIM_CID_Unlock_v3a does not start automatically.
I’ve tried already the manual steps and on the tri-colour screen appears 1.09.ds (which i guess is the bootloader) and if i connect the phone to the pc by the USB cable does nothing! Then i must reset, so that it can start up and i'm able to run the RUU_Hermes.... and appears an error (200): invalid update tool. Although the error is different from the one u mention on the forum i ignore and carry on with the process.
i run Herm_Unlock, click unlock and check both boxes to unlock (sim/cid) wait and seen the success message.
i soft reset or turn off and turn on with a diferent sim card (from another company) and appears a new message saying "u have tried 13 times, plz wait until the waiting time will be exceed..." (did I exceed the number of time permitted?) and from there, there is nothing i can do!!! Neither put the code: 22051978 as u mentioned in ur forum because the OK button is unavailable!!!!
I’ve tried many times and the last one has yesterday at around 11am until this morning nothing happen. This message does stills there!!!!!!!
i am sorry for been so long but i really need ur very usefullll helppppppp.
thankssssss so much!!!!!!!!!!!!!!!!!!!!
waiting for ur replay!!!!
chears,
MESO-HTC
unit: o2 XDA IIs(htc blue angel)
device information:
rom version: 1.40.00 WWE
radio version: 1.12.00
protocol version: 1337.42
extrom version: none
history:
just revived this unit using sd rom backup after a bad flash.
after sd flashing the rom boots perfectly. smooth screen alignment.set time etc.
didn't get any problem with that.
but it appears to have errors:
*saved data error is corrupted - will erase all the data to fix this problem
* default o2 apps didn't install automatically
problem:
the system freezes after going idle. touch will not respond buttons as well unless i performed a soft reset to get my IIs back to business.
tried flashing it with wm6 after the update, hard reset no,yes yes booting option. but the rom didn't boot, am stucked in white screen. tried to reset but gives me the bootloader mode screen. good thing i still have sd rom backup.
what seems to be the problem.,
is it a hardware problem?
any fix for this.
thanks. email me at [email protected] or reply on this thread