Hi all,
Here's my big problem I have right now
not return to stock HTC Rom for a return SAV is my topic in the section problem is transformed into ROM installation problem
http://www.forum-htc-dev.net/t53344-aide-retour-sav-jack-audio-hs
Can you help me when I run the RUU after it said 10% AC: ERROR [131]: ERROR ID CLIENT
I can watch one on the net and it looks like it come from:
ERROR [131]: ERROR ID CLIENT
One of these error messages displayed when you use the wrong RUU
to do the update. RUU will check if the Model ID and Language ID are
compatible with the Android phone. Make sure to use the correct RUU
to update.
Help me please guys!
This is my S-OFF with Revolutionary
try and flash from RUU. Not a rom, should get you back on stock.
http://forum.xda-developers.com/showthread.php?t=1208485
this error is with the RUU
Did you try S-On afterwards?
Connect phone to computer, open terminal, 'fastboot oem lock'
Related
I extracted these error codes from a Hermes rom upgrade 'read me' document, these should be of help if you get an error message during a rom upgrade. They should be common to all roms, please correct me if I am wrong.
ERROR [202, 204] : CONNECTION
This error message will appear when the device is not connected to ActiveSync correctly. Make sure you properly connect the device to the PC through ActiveSync before running RUU.
ERROR [260] : CONNECTION
This error occurs when there is an “open port error” before upgrading the CE ROM image.
Solution: You can reset the device and run RUU again. If you still encounter an “OPEN PORT ERROR” again, reset your computer and try again.
ERROR [206] : MEMORY ALLOCATION
ERROR [280] : UPDATE ERROR
When you see any of these error messages, close other running programs on the computer and run RUU again.
ERROR [208] : FILE OPEN
ERROR [210] : FILE READ
These error messages indicate that RUU lacks certain important files and cannot continue with the update. Please get the complete RUU package again.
ERROR [212] : FILE CREATE
ERROR [214] : FILE WRITE
ERROR [222, 224] : DEVICE NOT RESPONDING
These error messages will appear when remote access control has failed. Check the ActiveSync connection and try running RUU again.
ERROR [220] : MAIN BATTERY POWER
This error message will appear when the device’s battery power is not sufficient. Although RUU will instruct you to plug in the AC adapter, it still has to make sure that your device has enough power to upgrade the radio. (Even when you plug in the AC adapter, the device is unable to charge the battery when it is upgrading the radio).
ERROR [238] : FILE READ
This error message may appear when, for some unknown reason, the ROM image on the Mobile Device is corrupt. Download the whole RUU and try again.
ERROR [240] : FILE OPEN
When this error message appears, check whether the downloaded image is placed in the directory of RUU. If, for some unknown reason, you find that the ROM image is not located in the RUU folder, you have to download the RUU and retry again.
ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
ERROR [246] : DEVICE NOT RESPONDING
This error message indicates that RUU cannot start the update process. Please contact your service provider for assistance.
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
ERROR [330] : ROM IMAGE ERROR
This error message will appear when you use the incorrect RUU to upgrade and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version to upgrade.
Please read this post first http://forum.xda-developers.com/showthread.php?t=339961 I`m hoping someone can give me instructions in how i can do this so I can change or upgrade my rom.
Thanks in advanced
http://forum.xda-developers.com/showthread.php?t=322225
Download the herm1.nb file in that thread and flash it to your device using the instructrutions on page one.
http://forum.xda-developers.com/attachment.php?attachmentid=46888&d=1186868649. It uses Hermes 200.
If you want to edit it to a different Device ID, use a HEX Editor and edit bytes 4008-400D.
Hi Drummer 10630,
I have red the thread and I have to start by downgrading my spl and that’s just the problem I cannot downgrade or upgrade to anything because I keep on getting the error message Invalid model Id.
Now I’m trying my best to understand what it all says in the thread but what’s easy for you guys is Chinese to me and I’m from Holland.
So could you explain to me in lames terms which action I should take first to get my model id name changed back into HERM200 in nand.
I’m sorry if I’m a pain in the ash………e but I can’t do this without your help.
It's all in the thread. Read Mr Vanx's downgrading SPL pages...then flash the nand.
Hey Drummer10630,
Like I said I cannot downgrade I have red the thread several times and the Mr Vanx's downgrading SPL pages, tried the hard spl v7 but still get the error message invalid model id.
As you can read in this thread http://forum.xda-developers.com/showthread.php?t=339961 if I go to boot loader using the OK and Power button I get
H
IPL-1.01
H
SPL-1.40.Olipro
But if I use the spl wrapper I get
H
IPL-SSPL by des
H
SPL-1.09.ds
Does this make any difference?
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeGuide
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
ERROR ?242 : INVALID LANGUAGE ERROR ?244 : INVALID MODEL ID ERROR ?294 : INVALID VENDER ID ERROR ?296 : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
Hey Drummer10630,
I followed the instructions but it starts with installing HARD SPL which wont work because of the MODEL ID error so I skipped that and tried the rest and everything went fine I change the MODEL ID to H which is what it says on my device put the RUU_SIGNED.NBH file in the HTC rom folder and fired it up and guess what MODEL ID error.
I think what I need to do is to change my MODEL ID in nand like Olipro says.
Olipro said:
Your ModelID is stored on NAND and can be edited quite trivially (mostly).
how it got corrupted I don't know, however, the important question is; can you get into the OS?
Click to expand...
Click to collapse
device id
Hove the imei is related to the device id ?
There is relations ?
I mind part of the imei is the device id ?
Regards
Hello.
I want to change another version rom on HTC Hermes but when start loading new rom the "ERROR [262]: UPDATE ERROR
The rom update utility has encountered communication errors during the update process ... RECOVERY ...."
Phone is correctly connected to USB and entered on bootloader.
ex. Old rom is Schap's and i want to change to RDZ-ROM-STORM (for example) but not works!
When load similar version (Schap's) works!
What could be the problem?
Sorry 4 my eng.
I HAVE HTC MAGIC 32A radio 3.22.20.17 I DOWNLOADED THE RUU FROM THE HTC WEBSITE AND EVERY TIME I TRY TO UPDATE IT THAT ERROR KEEPS ON POPPING AND MY UPDATE IS FAILED. I KNOW THAT I HAVE DOWNLOADED THE RIGHT RUU. PLEASE HELP. THANKS!
If anyone could spare a moment that would be most appreciated. I have searched for hours and my laptop is crying under the "weight of a thousand tabs" at the moment and have finally decided that my problem is not going to be solved by more forum browsing. Luckily I have all the links to tutorials I was following so I can pinpoint exactly where things went wrong.
The carrier: Virgin Mobile
The problem: Stuck in bootloader, no options working. Recovery and factory reset both yield nothing. RUU fails with error 170.
The History: I decided I was going to try and root my phone today. That actually worked via stock. Followed a guide that showed me how to unlock the phone (using HTCDEV) and pushed TWRP as my recovery.img. I flashed the stock ROM and had root access. Then I was following another guide to obtain S-OFF. It said that I should flash SetMainVersionLow via my recovery and the next step was to run "fastboot oem lock" which worked. Then it told me to run the RUU.exe which simply gives me error 170 "USB Connection Error". I was running adb and fastboot commands early from this same machine, and nothing changed from the point of "fastboot oem lock" and running the RUU, though now my device won't even show up in fastboot or adb.
Any help would be most appreciated. I'm 12 hours in surfing on the web for solutions and have got nothing. I have learned that this site rocks (just looking through posts and the general responses people get) and you can bet and help some stranger will give me on the internet will be paid forward five times over. I'm a computer major in school so I am well versed with technology but as you can tell my rooting experience is non-existent. Thanks all.
More info:
Windows 8 64-Bit
Bootloader displays the following:
*** RELOCKED ***
*** Security Warning ***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
RADIO-1.09.00.0108
OpenADSP-v2.6.0.226.00.0217
eMMC-boot
May 17 2012,15:06:44
EDIT: I have, through restarting both laptop and phone a few times, obtained fastboot. My RUU now proceeds past where I would encounter error 170, but still fails. When I unplug the USB it says HBoot older. Anyone have a "newer" RUU?
fastboot getvar cid = SPCS_002
fastboot getvar mainver = 1.00.000.0
I was trying to use:
RUU_Shooter_ICS_35_S_Sprint_WWE_VM_1.13.652.2_Radio_1.06.00.0426_NV_1.53_144_release_262287_signed.exe
I also tried:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
'
which gave me the error "CID incorrect"