Database Users

[Q] I need help please......

i have flash wrong rom for my htc desire z a7272 uk version ... so it is stuck in logo screen, i need your help
i have fastboot access
i havn't adb access
hboot screen:
vision pvt ship s-on
hboot-0.82.0000
microp-0425
radio-26.02.01.15_m2
emmc-boot
sep 2 2010,17:59:38
when i try to install this RUU:
RUU_Vision_HTC_WWE_1.22.405.1_Radio_12.26.60.1301_26.02.00.24_M2_release_151197_signed
RUU_Vision_HTC_WWE_1.34.405.4_Radio_12.28b.60.140e_26.03.02.24_M_release_155297_signed
RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed
or exctract rom.zip from them to install it from fastboot i just got
sending 'zip' (291447 KB)... FAILED (remote: 02 data length is too large)
I don't know if there is a limit size to send through fastboot.exe!
if i copied rom.zip to sd card and change the name to PC10IMG.zip
I got nothing, ,
SD Checking Loading PCI0DIAG.zip
No Image!
LOading PC10DIAG.nbh
No image or wrong image!
Loading PC10IMG.zip
No Image!
Loadfing PC110IMG.nbh
No Image or Wrong Image
but if i try to install t-mobile rom
PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed
i got, before i made gold card i got wrong id model, after i made gold card i got
-----
sending 'zip' (126272KB)... OKAY [ 3.263s]
writing 'zip'... INFOadopting the signature contained in this image.
..
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 14.913s
-----
if i name it pc10img.zip put on sd it wil loading then i got the same error older main version
please i'm waiting for your help
ruu log
<LOG>
<T074907><INFO><VERSION>1.0.2.10</VERSION></INFO></T074907>
<T074907><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T074907>
<T075351><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T075351>
<T075351><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075351>
<T075352><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075352>
<T075352><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075352>
<T075354><DEBUG><OUT>HTxxxxxx fastboot</OUT>
</DEBUG></T075354>
<T075354><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075354>
<T075356><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075356>
<T075356><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075356>
<T075358><DEBUG><OUT>HTxxxxxx fastboot</OUT>
</DEBUG></T075358>
<T075358><DEBUG><CMD>fastboot -s HTxxxxxx getvar boot-mode</CMD>
</DEBUG></T075358>
<T075359><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075359>
<T075359><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075359>
<T075401><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075401>
<T075401><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075401>
<T075403><DEBUG><OUT>HTxxxxxxx fastboot</OUT>
</DEBUG></T075403>
<T075403><DEBUG><CMD>fastboot -s HTxxxxxxxxx getvar boot-mode</CMD>
</DEBUG></T075403>
<T075404><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075404>
<T075404><DEBUG><CMD>fastboot -s HTxxxxxxx getvar battery-status</CMD>
</DEBUG></T075404>
<T075406><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T075406>
<T075406><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T075406>
<T075406><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075406>
<T075408><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075408>
<T075408><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075408>
<T075410><DEBUG><OUT>HTxxxxxxxxxx fastboot</OUT>
</DEBUG></T075410>
<T075410><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075410>
<T075411><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075411>
<T075411><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075411>
<T075413><DEBUG><OUT>HTxxxxxxxxx fastboot</OUT>
</DEBUG></T075413>
<T075413><DEBUG><CMD>fastboot -s htxxxxxxxxxx getvar boot-mode</CMD>
</DEBUG></T075413>
<T075415><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075415>
<T075415><DEBUG><CMD>fastboot -s HTXXXXXXX getvar version-main</CMD>
</DEBUG></T075415>
<T075416><DEBUG><OUT>version-main: 1.34.405.5</OUT>
</DEBUG></T075416>
<T075422><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T075422>
<T075422><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075422>
<T075423><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075423>
<T075423><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075423>
<T075425><DEBUG><OUT>HTXXXXXXX fastboot</OUT>
</DEBUG></T075425>
<T075425><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075425>
<T075427><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075427>
<T075427><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075427>
<T075429><DEBUG><OUT>HTXXXXXXXX fastboot</OUT>
</DEBUG></T075429>
<T075429><DEBUG><CMD>fastboot -s HTXXXXXXX getvar boot-mode</CMD>
</DEBUG></T075429>
<T075430><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075430>
<T075430><DEBUG><CMD>fastboot -s HTXXXXXXXX getvar version-main</CMD>
</DEBUG></T075430>
<T075432><DEBUG><OUT>version-main: 1.34.405.5</OUT>
</DEBUG></T075432>
<T075437><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T075437>
<T075437><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075437>
<T075439><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075439>
<T075439><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075439>
<T075441><DEBUG><OUT>HTXXXXXXXXXX fastboot</OUT>
</DEBUG></T075441>
<T075441><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075441>
<T075443><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075443>
<T075443><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075443>
<T075444><DEBUG><OUT>HTXXXXXXXX fastboot</OUT>
</DEBUG></T075444>
<T075444><DEBUG><CMD>fastboot -s HTXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T075444>
<T075446><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075446>
<T075446><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075446>
<T075448><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075448>
<T075448><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075448>
<T075449><DEBUG><OUT>HTXXXXXXXX fastboot</OUT>
</DEBUG></T075449>
<T075449><DEBUG><CMD>fastboot -s HTXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T075449>
<T075451><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075451>
<T075451><DEBUG><CMD>fastboot -s HTXXXXXXXX erase cache</CMD>
</DEBUG></T075451>
<T075453><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T075453>
<T075453><DEBUG><CMD>fastboot -s HTXXXXXXXXX flash zip C:\Users\Secure\AppData\Local\Temp\{C1D504BD-0599-401E-BB15-D1D887F0F27B}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T075453>
<T075454><DEBUG><OUT>sending 'zip' (291447 KB)... FAILED (remote: 02 data length is too large)</OUT>
</DEBUG></T075454>
<T075459><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075459>
<T075501><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075501>
<T075501><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075501>
<T075502><DEBUG><OUT>HTXXXXXXXX fastboot</OUT>
</DEBUG></T075502>
<T075502><DEBUG><CMD>adb devices</CMD>
</DEBUG></T075502>
<T075504><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T075504>
<T075504><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T075504>
<T075506><DEBUG><OUT>HTXXXXXXXX fastboot</OUT>
</DEBUG></T075506>
<T075506><DEBUG><CMD>fastboot -s HTXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T075506>
<T075507><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T075507>
<T075507><DEBUG><CMD>fastboot -s HTXXXXXX reboot</CMD>
</DEBUG></T075507>
<T075509><DEBUG><OUT>rebooting... </OUT>
</DEBUG></T075509>
<T075509><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T075509>
<T075511><DEBUG><OUT />
</DEBUG></T075511>
</LOG>

aminly said:
if i copied rom.zip to sd card and change the name to PC10IMAG.zip
I got nothing, ,
Click to expand...
Click to collapse
It needs to be called "PC10IMG.zip", not "PC10IMAG.zip".

yes you are right, it just typing mistake, sorry

C:\AndroidSDK\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8D0876E
8
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x25202
INFOTAG:hero panel = 0xF
INFOTAG:engineerid = 0x4
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__001
INFOsetting->cid::HTC__001
INFOserial number: HTXXXXXXXXX
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =466
INFOactive commandline: board_vision.disable_uart2=0 board_visio
INFOn.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
INFOboard_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=true androidboot.baseband=26.02.01.15_M2 androidboo
INFOt.cid=HTC__001 androidboot.batt_poweron=good_battery android
INFOboot.carrier=HTC-WWE androidboot.mid=PC1011000 androidboot.k
INFOeycaps=qwerty androidboot.mode=normal androidboot.serialno=H
INFOT0AGRT01053 androidboot.bootloader=0.82.0000 no_console_susp
INFOend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOaARM_Partion[6].name=devlog
INFOpartition number=7
INFOValid partition num=7
INFOjump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
INFOel_addr(0x4008000)
INFO-------------------hboot boot time:132285 msec
FAILED (status read failed (Too many links))
finished. total time: 7.658s
C:\AndroidSDK\tools>

Your HBOOT right now say it's S-ON. But what was the status of this ROM before, which ROM was on it when it was working, and did you have it S-OFF ?

yes it was s-off, then i think i installed wrong ruu rom, but i don't know which rom was on it before

Try Navigating to Recovery Mode Volume Up + Power
Navigate Menu: Volume Up/Down Select Action: Power
do a factory reset . you don't Ned custom recovery yo do this..

aminly said:
yes it was s-off, then i think i installed wrong ruu rom, but i don't know which rom was on it before
Click to expand...
Click to collapse
ok, that's worrying. If you had S-OFF and then you installed an *older* RUU onto it, then it would have installed some of the original stuff. The trouble is, it may have then got to a point where it doesn't like the fact that the "new" ROM is in fact older, and then refuses to load it. By this point though you have no ROM and stock recovery.
Sorry but this sounds bad. Once you're S-OFF in HBOOT (until we have radio S-OFF fully sorted) then you need to be very careful if you ever flash an older ROM, or you could be bricked.

steviewevie said:
ok, that's worrying. If you had S-OFF and then you installed an *older* RUU onto it, then it would have installed some of the original stuff. The trouble is, it may have then got to a point where it doesn't like the fact that the "new" ROM is in fact older, and then refuses to load it. By this point though you have no ROM and stock recovery.
Sorry but this sounds bad. Once you're S-OFF in HBOOT (until we have radio S-OFF fully sorted) then you need to be very careful if you ever flash an older ROM, or you could be bricked.
Click to expand...
Click to collapse
however in this situation, you can just tell htc all you did was flash an ruu and it happened, if you do have stock hboot and recovery now then they can't prove otherwise and will replace under warranty.

ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.enable.sdr=0
ro.ril.enable.amr.wideband=0
ro.com.google.clientidbase=android-htc
ro.ril.vmail.23415=1571,BT
# begin build properties
# autogenerated by buildinfo.sh
ro.com.google.clientidbase=android-htc
ro.com.google.clientidbase=android-htc
ro.build.id=FRF91
ro.build.display.id=FRF91
ro.build.version.incremental=273326
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=二 10月 26 18:51:01 CST 2010
ro.build.date.utc=1288090261
ro.build.type=user
ro.build.user=
ro.build.host=AA107
ro.build.tags=release-keys
ro.product.model=HTC Vision
ro.product.brand=htc_wwe
ro.product.name=htc_vision
ro.product.device=vision
ro.product.board=vision
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=vision
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=1.34.405.5 CL273326 release-keys
ro.build.description=1.34.405.5 CL273326 release-keys
ro.build.changelist=273326
ro.product.ua=
ro.build.fingerprint=htc_wwe/htc_vision/vision/vision:2.2/FRF91/273326:user/release-keys
ro.build.project=155556
ro.product.version=1.34.405.5
keyguard.no_require_sim=1
# end build properties
#
# system.prop for mahimahi
#

Bricked my tattoo pls help

Hi,
Please help me save my HTC Tattoo.
I had made ​​a GoldCard SD. I had 3.0.0.5 installed and ClockWorkMod.
The last ROM installed was: [ROM] CyanogenMod 7.0.0 - 2.3.3 Release Gingerbread.
I wanted to make an original version of the software Tattoo. namely RUU_Click_Orange_UK_1.67.61.43_release_signed_NoDriver-fixes-network-unlock-code-bug
During installation I had the "Connection lost" error. and when the phone is Brick
Now the gold card is not working. the phone does not respond to any key combination ( power+ Vol Down. Power+ menu .power+ back)
The power + vol up does make a different thing. it vibrates 3 times and the green led apears.
if i plug the phone to the computer it shows " HTC " logo plus 4 mini icons in the corner's
at that point I can start the official instalation on the PC and it goes about 80% then the connection is lost.
I have windows 7 on the PC but i try on a Windows Xp with the same rezults
One more thing to mention is that if i just plug and unplug the phone from the computer the image on the phone is changing and i get just a red "RUU" on the screen.
Please any advice is wellcome
TX

do u get to use the recovery menu??

nope ..the only thing i can do is run official ROM installation and wait ...but at 80 % it goes down.

try to flash AmonRa recovery again and then see what happens

zuba said:
try to flash AmonRa recovery again and then see what happens
Click to expand...
Click to collapse
u mean to create a goldcard with amonra IMG on it?
i have not try amon ra till now

i mean:
1. download 1clickRoot http://www.megaupload.com/?d=ODPPN8S0
2. extract it on C:\
3. delete c:\rttattoo\sdcard\recovery.img
4. download http://rapidshare.com/files/365563468/recovery-RA-tattoo-v1.6.2.img
5. rename it to recovery.img and copy it to c:\rttattoo\sdcard\ folder
6. run c:\rttattoo\rootTatto.bat
it will root and flash recovery at the same time. after that you should be able to enter recovery mode (home+power). then you flash some custom Rom (mondo rom etc). if you succeed, you will be able to run installation of stock rom

zuba said:
i mean:
1. download 1clickRoot http://www.megaupload.com/?d=ODPPN8S0
2. extract it on C:\
3. delete c:\rttattoo\sdcard\recovery.img
4. download http://rapidshare.com/files/365563468/recovery-RA-tattoo-v1.6.2.img
5. rename it to recovery.img and copy it to c:\rttattoo\sdcard\ folder
6. run c:\rttattoo\rootTatto.bat
it will root and flash recovery at the same time. after that you should be able to enter recovery mode (home+power). then you flash some custom Rom (mondo rom etc). if you succeed, you will be able to run installation of stock rom
Click to expand...
Click to collapse
ok tryed the exact steps you indicated ..but at the rootTattoo.bat the message is:"
error: device not found
---------------------------------------------------------------------
--If you can see a long number, you can continue, if not Close the window
---------------------------------------------------------------------
Press any key to continue . . .
Creating dir and copying necessary files....
error: device not found
error: device not found
error: device not found
error: device not found
-------------------------------------------
-----------If there are errors, please close the window and do not continue
-------------------------------------------
Press any key to continue . . ."
any other idea?

i just found some log-s from officical install
maybe something helpfull:
"
<LOG>
<T021412><INFO><VERSION>0, 9, 7, 4029</VERSION></INFO></T021412>
<T021413><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021413>
<T021414><DEBUG><CMD>fastboot devices</CMD>
<OUT />
</DEBUG></T021414>
<T021414><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T021414>
<T021420><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T021420>
<T021421><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021421>
<T021422><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021422>
<T021423><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021423>
<T021424><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021424>
<T021426><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021426>
<T021427><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021427>
<T021428><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021428>
<T021429><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021429>
<T021430><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021430>
<T021431><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021431>
<T021432><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021432>
<T021433><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar battery-status</CMD>
<OUT>battery-status: good</OUT>
</DEBUG></T021433>
<T021433><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T021433>
<T021434><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021434>
<T021436><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021436>
<T021437><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021437>
<T021438><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021438>
<T021439><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021439>
<T021440><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021440>
<T021441><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021441>
<T021442><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar version-main</CMD>
<OUT>version-main: 1.67.61.43</OUT>
</DEBUG></T021442>
<T021444><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T021444>
<T021445><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021445>
<T021446><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021446>
<T021447><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021447>
<T021449><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021449>
<T021450><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021450>
<T021451><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021451>
<T021452><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021452>
<T021453><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar version-main</CMD>
<OUT>version-main: 1.67.61.43</OUT>
</DEBUG></T021453>
<T021456><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T021456>
<T021458><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021458>
<T021459><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021459>
<T021500><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021500>
<T021501><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021501>
<T021502><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021502>
<T021503><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021503>
<T021504><DEBUG><CMD>fastboot -s HT9A5LG07504 oem rebootRUU</CMD>
<OUT>... OKAY</OUT>
</DEBUG></T021504>
<T021505><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021505>
<T021507><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021507>
<T021508><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021508>
<T021509><DEBUG><CMD>fastboot -s HT9A5LG07504 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T021509>
<T021512><DEBUG><CMD>fastboot -s HT9A5LG07504 erase cache</CMD>
<OUT>erasing 'cache'...OKAY</OUT>
</DEBUG></T021512>
<T021512><DEBUG><CMD>fastboot -s HT9A5LG07504 flash zip C:\Users\Thor\AppData\Local\Temp\{9036644B-9A39-4655-8370-1233EFB756C5}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T021512>
<T021513><DEBUG><OUT>sending 'zip' (88968 KB)...</OUT>
</DEBUG></T021513>
<T021525><DEBUG><OUT>OKAY</OUT>
</DEBUG></T021525>
<T021525><DEBUG><OUT>g the signature contained in this image...</OUT>
</DEBUG></T021525>
<T021555><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T021555>
<T021555><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T021555>
<T021555><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T021555>
<T021555><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T021555>
<T021555><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T021555>
<T021556><DEBUG><OUT>INFOstart image[hboot] unzipping for pre-update check...</OUT>
</DEBUG></T021556>
<T021556><DEBUG><OUT>INFOstart image[boot] unzipping & flushing...</OUT>
</DEBUG></T021556>
<T021556><DEBUG><OUT>INFO[RUU]UZ,boot,0</OUT>
</DEBUG></T021556>
<T021556><DEBUG><OUT>INFO[RUU]UZ,boot,51</OUT>
</DEBUG></T021556>
<T021556><DEBUG><OUT>INFO[RUU]UZ,boot,100</OUT>
</DEBUG></T021556>
<T021557><DEBUG><OUT>INFO[RUU]WP,boot,0</OUT>
</DEBUG></T021557>
<T021557><DEBUG><OUT>INFO[RUU]WP,boot,50</OUT>
</DEBUG></T021557>
<T021557><DEBUG><OUT>INFO[RUU]WP,boot,100</OUT>
</DEBUG></T021557>
<T021558><DEBUG><OUT>INFOstart image[hboot] unzipping & flushing...</OUT>
</DEBUG></T021558>
<T021558><DEBUG><OUT>INFO[RUU]UZ,hboot,0</OUT>
</DEBUG></T021558>
<T021558><DEBUG><OUT>INFO[RUU]UZ,hboot,100</OUT>
</DEBUG></T021558>
<T021558><DEBUG><OUT>INFO[RUU]WP,hboot,0</OUT>
</DEBUG></T021558>
<T021558><DEBUG><OUT>INFO[RUU]WP,hboot,100</OUT>
</DEBUG></T021558>
<T021558><DEBUG><OUT>INFOstart image[radio] unzipping & flushing...</OUT>
</DEBUG></T021558>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,0</OUT>
</DEBUG></T021559>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,6</OUT>
</DEBUG></T021559>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,14</OUT>
</DEBUG></T021559>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,19</OUT>
</DEBUG></T021559>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,24</OUT>
</DEBUG></T021559>
<T021559><DEBUG><OUT>INFO[RUU]UZ,radio,33</OUT>
</DEBUG></T021559>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,38</OUT>
</DEBUG></T021600>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,43</OUT>
</DEBUG></T021600>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,48</OUT>
</DEBUG></T021600>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,53</OUT>
</DEBUG></T021600>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,62</OUT>
</DEBUG></T021600>
<T021600><DEBUG><OUT>INFO[RUU]UZ,radio,67</OUT>
</DEBUG></T021600>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,76</OUT>
</DEBUG></T021601>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,81</OUT>
</DEBUG></T021601>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,86</OUT>
</DEBUG></T021601>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,91</OUT>
</DEBUG></T021601>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,96</OUT>
</DEBUG></T021601>
<T021601><DEBUG><OUT>INFO[RUU]UZ,radio,100</OUT>
</DEBUG></T021601>
<T021602><DEBUG><OUT>INFO[RUU]WP,radio,0</OUT>
</DEBUG></T021602>
<T021602><DEBUG><OUT>FAILED (status read failed (Too many links))</OUT>
</DEBUG></T021602>
<T021735><DEBUG><CMD>adb devices</CMD>
<OUT>List of devices attached
</OUT>
</DEBUG></T021735>
<T021736><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A5LG07504 fastboot</OUT>
</DEBUG></T021736>
<T021742><DEBUG><CMD>adb kill-server</CMD>
<OUT />
</DEBUG></T021742>
</LOG>
"

the only thing that my phone is showing is:
CLICK PVT SHIP S-ON
HBOOT-052.0001 (CLIC10000)
MICROP-0203
RADIO-3.35.07.31
Sep 22 2009
RUU
that is it

sabothor said:
the only thing that my phone is showing is:
CLICK PVT SHIP S-ON
HBOOT-052.0001 (CLIC10000)
MICROP-0203
RADIO-3.35.07.31
Sep 22 2009
RUU
that is it
Click to expand...
Click to collapse
hi
if u have the official rom for ur country with u try this
connect ur phone and if ur phone connects via usb ie u can see the green android sync on ur pc then try flashing the official rom from ur pc it is a exe file which u can flash via ur pc u can chek in shippedrom.com for the official rom for ur country
this is not development related moved to general in the future use the Q&A thread it is a sticky and that is why it was created for OK

haree said:
hi
if u have the official rom for ur country with u try this
connect ur phone and if ur phone connects via usb ie u can see the green android sync on ur pc then try flashing the official rom from ur pc it is a exe file which u can flash via ur pc u can chek in shippedrom.com for the official rom for ur country
this is not development related moved to general in the future use the Q&A thread it is a sticky and that is why it was created for OK
Click to expand...
Click to collapse
the phone was originaly from italy.
from Fastweb..
but the rom does not install ...it just hangs in "Sending...."

sabothor said:
the phone was originaly from italy.
from Fastweb..
but the rom does not install ...it just hangs in "Sending...."
Click to expand...
Click to collapse
hi
have u tried what iv said do this
1. go to shipped rom.com get the official rom for ur phone
it will be an exe which u need to flash from ur PC
then connect ur phone via USB see if u can see the green sync on ur pc and see if ur phone also show the same then try clicking on the exe and installing the same
i did something like this long time back and got my tattoo working again
hope it helps

YEY..IT'S ALIVE..
the only ROM that worked was the Vodafone UK 1.6 ROM RUU.
Incredible...the phone is from Fastweb IT ..and with that instalation freez at begining.
With Vodafone Uk it worked like a charm.
YEY ..NEVER GIVE UP ..NEVER SURRENDER

Problem Help!

I had flashed a rom of rogers into my Htc Magic and then Flash An original rom of Htc (newest one).In the installation i got an RUU USB and i cant flash Rogers rom or the Htc official.
Rogers rom:Invalid model ID
Htc rom:stucks at checking version
At flashing pc said to me that he will try to flash from 3.54.631.3 to 3.05.401.3
What to do?
Radio version :6.35.08.29
SPL/Hboot version: 1.76.0009
product: sapphire
mid: sapp10000
security: on
build-mode: ship
When i call fastboot oem boot my device boots normal into Rogers android but at restart again RUU USB screen...

Nowone ???Please help me.My phone is not Rogers but with Rogers rom onto it!I cannot access Recovery menu because of the RUU USB mode..Any help??Any commant that will restore it?
With fastboot boot (file) doesnt work..It shows booting... and nothing on the phone!

Current installation is not completed. Google how create goldcard - it avoids CID check and you can install ROMs from different regions than your phone

I tried to do it but after that my pc can not recognise sdcard and it needs format.. I use SanDisk 2 gb..
Sent from my HTC Magic using XDA App

You MUST create goldcard. Only with goldcard you can finish installation.
Use other sdcards (Kingston, Transcend). Ask friends...
If your PC does not recognize sdcard after process - something went wrong. Read manual carefully...

with what tool i must format the SDcard??

nikosdd said:
with what tool i must format the SDcard??
Click to expand...
Click to collapse
SDCard Formatter is the best: https://www.sdcard.org/downloads/formatter_3/
But, may be you did something wrong. What manual did you use? SD Card must work after creating goldcard from it. It is no need to format.

Hmmm i have read some guides and all of them wants format at FAT32..But after HeX,the sd is not working!!!

nikosdd said:
Hmmm i have read some guides and all of them wants format at FAT32..But after HeX,the sd is not working!!!
Click to expand...
Click to collapse
Be in mind that you are editing physical disk of sdcard not logical. It is common error when creating goldcard with HeX Editor

Ok i think i had successfully created a goldcard...Now what i have to do?I remind you that we are in RUU Mode ...

Run RUU and follow instructions. If you will have errors you can review it in c:\ruu_log folder

I got 132 error!..
In log there is a error.What to do?
</DEBUG></T163647>
<T163647><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163647>
<T163648><DEBUG><OUT>HT96CKF01301 fastboot</OUT>
</DEBUG></T163648>
<T163648><DEBUG><CMD>fastboot -s HT96CKF01301 getvar boot-mode</CMD>
</DEBUG></T163648>
<T163649><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T163649>
<T163649><DEBUG><CMD>fastboot -s HT96CKF01301 erase cache</CMD>
</DEBUG></T163649>
<T163652><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T163652>
<T163653><DEBUG><CMD>fastboot -s HT96CKF01301 flash zip "D:\Documents and Settings\nikosdd\Local Settings\Temp\{B9C12851-9C0F-42DF-9664-6789186775BE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T163653>
<T163710><DEBUG><OUT>sending 'zip' (110447 KB)... OKAY</OUT>
</DEBUG></T163710>
<T163710><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T163710>
<T163710><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T163710>
<T163736><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T163736>
<T163742><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163742>
<T163743><DEBUG><OUT>List of devices attached
</OUT>

Hmm . That's weird.
Error 132 means CustomerID (CID) difference between phone and ROM and means that your goldcard is not working.
Error 12 signature verify fail - means that phone does not want flash unsigned files.
Is this log current? May be it is old log...

Before trying i had deleted this folder...Im sure about this log..Wait please to try a new sd..

Also i tried the original latest rom and here is the details
</DEBUG></T164034>
<T164034><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T164034>
<T164035><DEBUG><OUT>HT96CKF01301 fastboot</OUT>
</DEBUG></T164035>
<T164035><DEBUG><CMD>fastboot -s HT96CKF01301 getvar boot-mode</CMD>
</DEBUG></T164035>
<T164036><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T164036>
<T164036><DEBUG><CMD>fastboot -s HT96CKF01301 flash zip "D:\Documents and Settings\nikosdd\Local Settings\Temp\{419AB917-7F1F-4DF7-A8A0-ABA0C654CD5C}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom1.zip"</CMD>
</DEBUG></T164036>
<T164051><DEBUG><OUT>sending 'zip' (91561 KB)... OKAY</OUT>
</DEBUG></T164051>
<T164051><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T164051>
<T164051><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T164051>
<T164123><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T164123>
<T164123><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T164123>
<T164123><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T164123>
<T164123><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T164123>
<T164123><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T164123>
<T164123><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T164123>
<T164126><DEBUG><CMD>adb devices</CMD>
</DEBUG></T164126>
<T164127><DEBUG><OUT>List of devices attached
</OUT>

This error told that you tried install Rom with lower version than phone has now.
Flash Rogers RUU.
Sent from my A7-040 using Tapatalk

Again!
</DEBUG></T163647>
<T163647><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163647>
<T163648><DEBUG><OUT>HT96CKF01301 fastboot</OUT>
</DEBUG></T163648>
<T163648><DEBUG><CMD>fastboot -s HT96CKF01301 getvar boot-mode</CMD>
</DEBUG></T163648>
<T163649><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T163649>
<T163649><DEBUG><CMD>fastboot -s HT96CKF01301 erase cache</CMD>
</DEBUG></T163649>
<T163652><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T163652>
<T163653><DEBUG><CMD>fastboot -s HT96CKF01301 flash zip "D:\Documents and Settings\nikosdd\Local Settings\Temp\{B9C12851-9C0F-42DF-9664-6789186775BE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T163653>
<T163710><DEBUG><OUT>sending 'zip' (110447 KB)... OKAY</OUT>
</DEBUG></T163710>
<T163710><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T163710>
<T163710><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T163710>
<T163736><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T163736>
<T163742><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163742>
<T163743><DEBUG><OUT>List of devices attached
</OUT>

nikosdd said:
Again!
Click to expand...
Click to collapse
What error did you have on screen?

5{strogino} i need your assistence!!
5{strogino} i need your assistence!! i have a problem, i need 3.05.401.1 HTC Europe with 3.22 radio!! is there such a file??
also i was wondering if i can change the ''andriod-info.text'', you see i saw one of ''binery10010'' -(or was that his name), anyhow that guy managed to change the files in the official zip!
you know what i will also donate this time!!
thanx

132 cid error!..Or ModelId i dont remember..One of this but it was 132 error..

[Q] 32A Changed the SLP that comes briked???

Dear All,
Sorry that i already searched a lot of thread, but there no same as my case.
I need your help please support me.
Thank you very much.
My phone is MyTouch 3G 32A ORIGINAL config as below:
SAPPIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0010(SAPP10000)
CPLD-12
RADIO-6.35.16.19
Jan 14 2010, 00:14:58
After i made to S-OFF config as following:
SAPPIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007(SAPP10000)
CPLD-12
RADIO-6.35.16.19
Aug 21 2009, 18:19:15
Unfortunately once i success get S-OFF, but i forgot that i have download and delete a file call"SAPPIMG.nbh" from SD card, once i boot up the fastboot, that are processing this file....then config have been changed as following:
SAPPHIRE UNKNOWN 32A SHIP S-ON G
HBOOT-1.33.0006(SAPP10000)
CPLD-12
RADIO-2.22.19.26I
May 27 2009, 19:06:41
After that i stuck at ROGER boot up logo. Could any brother let me to change to original one?
Thank you very much for your support and help.
Thank you.

Just only can go to Hboot and fastboot mode, cannot goes to recovery mode...

Go into fastboot and get some info:
Code:
fastboot getvar cid
fastboot getvar cidnum
fastboot getvar version-main
http://forum.xda-developers.com/showthread.php?t=659403
Search for RUU matching with your CID. If yes - you can install this RUU without goldcard. Note: choose RUU from 'Magic 32A' section ONLY
Then you can get S-Off and other things...

5[Strogino] said:
Go into fastboot and get some info:
Code:
fastboot getvar cid
fastboot getvar cidnum
fastboot getvar version-main
http://forum.xda-developers.com/showthread.php?t=659403
Search for RUU matching with your CID. If yes - you can install this RUU without goldcard. Note: choose RUU from 'Magic 32A' section ONLY
Then you can get S-Off and other things...
Click to expand...
Click to collapse
Dear 5[Strogino]
cid: SMCVD001
cidnum: SMCVD001
version-main: 3.05.631.7
could i change be original SPL 1.76.xxxx?

Yinhello said:
Dear 5[Strogino]
cid: SMCVD001
cidnum: SMCVD001
version-main: 3.05.631.7
could i change be original SPL 1.76.xxxx?
Click to expand...
Click to collapse
Hmmm. It is a few harder than i thought. According your info you have old combo hboot/radio, but phone said that he has 3.05.631.7 rom...
Or you installed 3.05.631.7 successfully over problematic combo and have new combo now???
Try make goldcard and flash RUU 3.05.401.1

5[Strogino] said:
Hmmm. It is a few harder than i thought. According your info you have old combo hboot/radio, but phone said that he has 3.05.631.7 rom...
Or you installed 3.05.631.7 successfully over problematic combo and have new combo now???
Try make goldcard and flash RUU 3.05.401.1
Click to expand...
Click to collapse
Dear 5[Strogino]
Thank you, i try it first.

5[Strogino] said:
Hmmm. It is a few harder than i thought. According your info you have old combo hboot/radio, but phone said that he has 3.05.631.7 rom...
Or you installed 3.05.631.7 successfully over problematic combo and have new combo now???
Try make goldcard and flash RUU 3.05.401.1
Click to expand...
Click to collapse
Dear 5[Strogino]
I downloaded the version of 3.05.401.1 to run, but it's still fail... i think is it revert back the SPL with 1.76.xxxx first running the RUU?
Thank you.

Yinhello said:
Dear 5[Strogino]
I downloaded the version of 3.05.401.1 to run, but it's still fail... i think is it revert back the SPL with 1.76.xxxx first running the RUU?
Thank you.
Click to expand...
Click to collapse
There are some logs in c:\ruu_log from RUU. Post it and i can review it.

5[Strogino] said:
There are some logs in c:\ruu_log from RUU. Post it and i can review it.
Click to expand...
Click to collapse
Dear 5[Strogino]
<LOG>
<T170827><INFO><VERSION>1.0.1.30</VERSION></INFO></T170827>
<T170827><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T170827>
<T170833><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T170833>
<T170833><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170833>
<T170834><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170834>
<T170834><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170834>
<T170835><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170835>
<T170835><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170835>
<T170837><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170837>
<T170837><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170837>
<T170838><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170838>
<T170838><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170838>
<T170839><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T170839>
<T170839><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170839>
<T170840><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170840>
<T170840><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170840>
<T170841><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170841>
<T170841><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170841>
<T170842><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T170842>
<T170842><DEBUG><CMD>fastboot -s HT95TKF03916 getvar battery-status</CMD>
</DEBUG></T170842>
<T170843><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T170843>
<T170843><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T170843>
<T170843><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170843>
<T170844><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170844>
<T170844><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170844>
<T170845><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170845>
<T170845><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170845>
<T170847><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170847>
<T170847><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170847>
<T170848><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170848>
<T170848><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170848>
<T170849><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T170849>
<T170849><DEBUG><CMD>fastboot -s HT95TKF03916 getvar version-main</CMD>
</DEBUG></T170849>
<T170850><DEBUG><OUT>version-main: 3.05.631.7</OUT>
</DEBUG></T170850>
<T170853><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T170853>
<T170853><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170853>
<T170854><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170854>
<T170854><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170854>
<T170855><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170855>
<T170855><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170855>
<T170856><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170856>
<T170856><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170856>
<T170857><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170857>
<T170857><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170857>
<T170858><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T170858>
<T170858><DEBUG><CMD>fastboot -s HT95TKF03916 getvar version-main</CMD>
</DEBUG></T170858>
<T170859><DEBUG><OUT>version-main: 3.05.631.7</OUT>
</DEBUG></T170859>
<T170904><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T170904>
<T170904><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170904>
<T170906><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170906>
<T170906><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170906>
<T170907><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170907>
<T170907><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170907>
<T170908><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170908>
<T170908><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170908>
<T170909><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170909>
<T170909><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170909>
<T170910><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T170910>
<T170910><DEBUG><CMD>fastboot -s HT95TKF03916 oem rebootRUU</CMD>
</DEBUG></T170910>
<T170911><DEBUG><OUT>... OKAY</OUT>
</DEBUG></T170911>
<T170911><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170911>
<T170912><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170912>
<T170912><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170912>
<T170913><DEBUG><OUT />
</DEBUG></T170913>
<T170914><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170914>
<T170915><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170915>
<T170915><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170915>
<T170916><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170916>
<T170916><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170916>
<T170917><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T170917>
<T170917><DEBUG><CMD>fastboot -s HT95TKF03916 erase cache</CMD>
</DEBUG></T170917>
<T170919><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T170919>
<T170919><DEBUG><CMD>fastboot -s HT95TKF03916 flash zip C:\Users\YIN\AppData\Local\Temp\{FF6166B7-C538-4685-895E-E31B25471153}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T170919>
<T170923><DEBUG><OUT>sending 'zip' (11094 KB)... OKAY</OUT>
</DEBUG></T170923>
<T170923><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T170923>
<T170923><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T170923>
<T170926><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T170926>
<T170926><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T170926>
<T170926><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T170926>
<T170927><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T170927>
<T170927><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T170927>
<T170927><DEBUG><OUT />
</DEBUG></T170927>
<T170927><DEBUG><CMD>fastboot -s HT95TKF03916 oem rebootRUU</CMD>
</DEBUG></T170927>
<T170928><DEBUG><OUT>... OKAY</OUT>
</DEBUG></T170928>
<T170928><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170928>
<T170929><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170929>
<T170929><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170929>
<T170930><DEBUG><OUT />
</DEBUG></T170930>
<T170931><DEBUG><CMD>adb devices</CMD>
</DEBUG></T170931>
<T170931><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T170931>
<T170931><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T170931>
<T170933><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T170933>
<T170933><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T170933>
<T170934><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T170934>
<T170934><DEBUG><CMD>fastboot -s HT95TKF03916 flash zip C:\Users\YIN\AppData\Local\Temp\{FF6166B7-C538-4685-895E-E31B25471153}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom1.zip</CMD>
</DEBUG></T170934>
<T170951><DEBUG><OUT>sending 'zip' (92063 KB)... OKAY</OUT>
</DEBUG></T170951>
<T170951><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T170951>
<T170951><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T170951>
<T171018><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T171018>
<T171018><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T171018>
<T171018><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T171018>
<T171018><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T171018>
<T171018><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T171018>
<T171559><DEBUG><CMD>adb devices</CMD>
</DEBUG></T171559>
<T171601><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T171601>
<T171601><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T171601>
<T171602><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T171602>
<T171602><DEBUG><CMD>adb devices</CMD>
</DEBUG></T171602>
<T171603><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T171603>
<T171603><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T171603>
<T171604><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T171604>
<T171604><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T171604>
<T171605><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T171605>
<T171605><DEBUG><CMD>fastboot -s HT95TKF03916 reboot</CMD>
</DEBUG></T171605>
<T171606><DEBUG><OUT>rebooting... </OUT>
</DEBUG></T171606>
<T171606><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T171606>
<T171607><DEBUG><OUT />
</DEBUG></T171607>
</LOG>

You have error "remote: 42 custom id check fail" and it said that you don't have goldcard. Make it and run RUU again.

5[Strogino] said:
You have error "remote: 42 custom id check fail" and it said that you don't have goldcard. Make it and run RUU again.
Click to expand...
Click to collapse
Dear 5[Strogino],
I make sure that for the goldcard was make successful. That i tried to put this SD card into my girlyfriend's MyTouch 3G 32A, that can run RUU for 3.05.401.1. but once put back into my phone when processing the update that always show me "ERROR [131] CUSTOMER ID ERROR"
could you have any idea on this case?
Thank you very much
<LOG>
<T225627><INFO><VERSION>1.0.1.30</VERSION></INFO></T225627>
<T225627><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T225627>
<T225632><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T225632>
<T225632><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225632>
<T225633><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225633>
<T225633><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225633>
<T225634><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225634>
<T225634><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225634>
<T225635><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225635>
<T225635><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225635>
<T225636><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225636>
<T225636><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225636>
<T225637><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225637>
<T225637><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225637>
<T225639><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225639>
<T225639><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225639>
<T225640><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225640>
<T225640><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225640>
<T225641><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225641>
<T225641><DEBUG><CMD>fastboot -s HT95TKF03916 getvar battery-status</CMD>
</DEBUG></T225641>
<T225642><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T225642>
<T225642><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T225642>
<T225642><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225642>
<T225643><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225643>
<T225643><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225643>
<T225644><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225644>
<T225644><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225644>

<LOG>
<T225627><INFO><VERSION>1.0.1.30</VERSION></INFO></T225627>
<T225627><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T225627>
<T225632><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T225632>
<T225632><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225632>
<T225633><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225633>
<T225633><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225633>
<T225634><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225634>
<T225634><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225634>
<T225635><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225635>
<T225635><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225635>
<T225636><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225636>
<T225636><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225636>
<T225637><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225637>
<T225637><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225637>
<T225639><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225639>
<T225639><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225639>
<T225640><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225640>
<T225640><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225640>
<T225641><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225641>
<T225641><DEBUG><CMD>fastboot -s HT95TKF03916 getvar battery-status</CMD>
</DEBUG></T225641>
<T225642><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T225642>
<T225642><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T225642>
<T225642><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225642>
<T225643><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225643>
<T225643><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225643>
<T225644><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225644>
<T225644><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225644>
<T225645><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225645>
<T225645><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225645>
<T225646><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225646>
<T225646><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225646>
<T225648><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225648>
<T225648><DEBUG><CMD>fastboot -s HT95TKF03916 getvar version-main</CMD>
</DEBUG></T225648>
<T225649><DEBUG><OUT>version-main: 3.05.631.7</OUT>
</DEBUG></T225649>
<T225651><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T225651>
<T225651><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225651>
<T225652><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225652>
<T225652><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225652>
<T225653><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225653>
<T225653><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225653>
<T225655><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225655>
<T225655><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225655>
<T225656><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225656>
<T225656><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225656>
<T225657><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225657>
<T225657><DEBUG><CMD>fastboot -s HT95TKF03916 getvar version-main</CMD>
</DEBUG></T225657>
<T225658><DEBUG><OUT>version-main: 3.05.631.7</OUT>
</DEBUG></T225658>
<T225702><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T225702>
<T225702><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225702>
<T225703><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225703>
<T225703><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225703>
<T225704><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225704>
<T225704><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225704>
<T225705><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225705>
<T225705><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225705>
<T225706><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225706>
<T225706><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225706>
<T225707><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T225707>
<T225707><DEBUG><CMD>fastboot -s HT95TKF03916 oem rebootRUU</CMD>
</DEBUG></T225707>
<T225708><DEBUG><OUT>... OKAY</OUT>
</DEBUG></T225708>
<T225708><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225708>
<T225710><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225710>
<T225710><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225710>
<T225710><DEBUG><OUT />
</DEBUG></T225710>
<T225711><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225711>
<T225712><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225712>
<T225712><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225712>
<T225713><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225713>
<T225713><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225713>
<T225715><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T225715>
<T225715><DEBUG><CMD>fastboot -s HT95TKF03916 erase cache</CMD>
</DEBUG></T225715>
<T225716><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T225716>
<T225716><DEBUG><CMD>fastboot -s HT95TKF03916 flash zip C:\Users\Yin\AppData\Local\Temp\{52050982-E0B7-4EF3-9329-6874E932911C}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T225716>
<T225720><DEBUG><OUT>sending 'zip' (11094 KB)... OKAY</OUT>
</DEBUG></T225720>
<T225720><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T225720>
<T225720><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T225720>
<T225723><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T225723>
<T225724><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T225724>
<T225724><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T225724>
<T225724><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T225724>
<T225724><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T225724>
<T225724><DEBUG><OUT />
</DEBUG></T225724>
<T225724><DEBUG><CMD>fastboot -s HT95TKF03916 oem rebootRUU</CMD>
</DEBUG></T225724>
<T225726><DEBUG><OUT>... OKAY</OUT>
</DEBUG></T225726>
<T225726><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225726>
<T225727><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225727>
<T225727><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225727>
<T225727><DEBUG><OUT />
</DEBUG></T225727>
<T225728><DEBUG><CMD>adb devices</CMD>
</DEBUG></T225728>
<T225729><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T225729>
<T225729><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T225729>
<T225731><DEBUG><OUT>HT95TKF03916 fastboot</OUT>
</DEBUG></T225731>
<T225731><DEBUG><CMD>fastboot -s HT95TKF03916 getvar boot-mode</CMD>
</DEBUG></T225731>
<T225732><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T225732>
<T225732><DEBUG><CMD>fastboot -s HT95TKF03916 flash zip C:\Users\Yin\AppData\Local\Temp\{52050982-E0B7-4EF3-9329-6874E932911C}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom1.zip</CMD>
</DEBUG></T225732>
<T225749><DEBUG><OUT>sending 'zip' (92063 KB)... OKAY</OUT>
</DEBUG></T225749>
<T225749><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T225749>
<T225749><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T225749>
<T225815><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T225815>
<T225816><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T225816>
<T225816><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T225816>
<T225816><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T225816>
<T225816><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T225816>

It exactly explains that don't want install ruu cause you have cid what is not in ruu list.
Try search for another sdcard and make goldcard from it.
Sent from my A7-040 using Tapatalk

5[Strogino] said:
It exactly explains that don't want install ruu cause you have cid what is not in ruu list.
Try search for another sdcard and make goldcard from it.
Sent from my A7-040 using Tapatalk
Click to expand...
Click to collapse
Dear 5[Strogino]
Thank you, i will check and made another goldcard.
Thank You Very Much, Have a nice day=)

Dear 5[Strogino]
I tried another goldcard, it still stuck as cid check...
Thus i think that, my phone is completed bricked...
haha i think i need to purchase another android phone... do u have any model that you are recommend... except samsung i9100...that because i own already...
=) Thank you.

Yinhello said:
Dear 5[Strogino]
I tried another goldcard, it still stuck as cid check...
Thus i think that, my phone is completed bricked...
Click to expand...
Click to collapse
That's weird, but I think what you went wrong when created goldcard. May be you did not reverse string. May be you did not choose physical disk when changed image. Too many people avoided cid-error with goldcard, but you can't
Sent from my A7-040 using Tapatalk

The goldcard trick only works if you load the ruu file using hboot mode.
As you can see in the log, the ruu-application is using:
fastboot -s HT95TKF03916 flash zip C:\Users\....\rom1.zip which renders the goldcard useless.
FIX:
Download the following 2 files:
https://rapidshare.com/files/531578080/Rogers_3.05.631.7_pt1.zip
https://rapidshare.com/files/4256602161/Rogers_3.05.631.7_pt2.zip
1)Rename the first file to sappimg.zip and put it in the goldcard.
2)Put the goldcard inside the device
3)Reboot into hboot mode and let it flash.
4)Repeat step 1 - 3 for the second file.
5)Reboot and wait(10 mins) and you should be inside android os.
6)follow my guide found in my signature and get custom recovery / eng spl.
7)flash what ever rom you like :0)
Stop posting the long log files in here (waste of space). Use pastebin.com

Dear mumilover,
Thank you Very Much. I really really really happy for your great support.
Thank you! =)
Yin,

Haha,
My phone it's became another situation... when i installed a ROM Manager and choose reboot to recovery, that my phone are reboot as a ROGERS screen then reboot reboot and reboot as same screen, i thus that phone are stuck at recovery.
Hboot and Fastboot both cannot entry...i pull out the battery and rest for 1 hour... is still happened same situation....
haha is difficult situation more then before...
Thank you,

Lenovo YT2 1050f (stuck on fastboot starting.....)

So, my tab was working perfectly and it just went off. after leaving it for a few months, i decided to charge it and when i turned it on i get a flickering error message, it goes off and turns on with 'fastboot starting....'
So i did my research on it and i tried adb, fastboot commands - like reboot, continue...nothing worked. then i downloaded the flash tool got the appropriate drivers and installed them. but i keep getting this message
04/21/18 00:14:44.102 INFO : Phone Flash Tool V 4.4.4-1 Win32 External (build on Mon Apr 28 09:56:35 UTC 2014)
04/21/18 00:14:44.102 INFO : Using xFSTK version: 1.5.3
04/21/18 00:14:44.133 INFO : Using Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\Program Files (x86)\Minimal ADB and Fastboot\adb.exe
04/21/18 00:14:44.133 INFO : OS version detected: Windows 8 (x64)
04/21/18 00:14:44.263 INFO : Adb and fastboot binaries OK
04/21/18 00:14:44.266 INFO : Phone Flash Tool initialized successfully
04/21/18 00:14:44.281 INFO : Loading Flash file ...
04/21/18 00:14:44.281 INFO : Ready to flash!
04/21/18 00:15:05.196 INFO : Loading Flash file (C:/Users/User/Downloads/YT2-1050F_S0198_150422_ROW/YT2-1050F_S0198_150422_ROW/SW/flash.xml)
04/21/18 00:15:05.198 INFO : GP_Flag is set to 0x80000045
04/21/18 00:15:05.200 INFO : Ready to flash!
04/21/18 00:33:44.424 INFO : Unzip Flash Archive "C:/Users/User/Downloads/YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L).zip"
04/21/18 00:34:20.595 INFO : Loading Flash file (C:/Users/User/Downloads/YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L)/flash.xml)
04/21/18 00:34:20.596 INFO : GP_Flag is set to 0x80000045
04/21/18 00:34:20.597 INFO : Ready to flash!
04/21/18 00:35:35.991 INFO : Port 0/1: Flashing OS
04/21/18 00:35:35.992 INFO : Port 0/1: fastboot -s Baytrail7094EABC -S 500M flash osloader "C:/Users/User/Downloads/YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L)/efilinux-user.efi"
04/21/18 00:35:38.087 INFO : Port 0/1: fastboot -s Baytrail7094EABC -S 500M boot "C:/Users/User/Downloads/YT2-1050F_USR_S100031_1506111400_WW52_ROW-(L)/droidboot.img"
04/21/18 00:35:40.767 INFO : Port 0/1: sleep 25000 ms
04/21/18 00:36:05.768 INFO : Port 0/1: fastboot -s Baytrail7094EABC -S 500M oem wipe ESP
04/21/18 00:36:07.844 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem wipe ESP":
< waiting for device >
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:09.845 WARNING: Port 0/1: Retry to execute fastboot -s Baytrail7094EABC -S 500M oem wipe ESP
04/21/18 00:36:09.916 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem wipe ESP":
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:11.916 WARNING: Port 0/1: Failed to execute non mandatory command fastboot -s Baytrail7094EABC -S 500M oem wipe ESP, ignoring error
04/21/18 00:36:11.916 INFO : Port 0/1: fastboot -s Baytrail7094EABC -S 500M oem wipe reserved
04/21/18 00:36:11.986 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem wipe reserved":
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:13.988 WARNING: Port 0/1: Retry to execute fastboot -s Baytrail7094EABC -S 500M oem wipe reserved
04/21/18 00:36:14.025 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem wipe reserved":
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:16.026 WARNING: Port 0/1: Failed to execute non mandatory command fastboot -s Baytrail7094EABC -S 500M oem wipe reserved, ignoring error
04/21/18 00:36:16.026 INFO : Port 0/1: fastboot -s Baytrail7094EABC -S 500M oem start_partitioning
04/21/18 00:36:16.098 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:18.099 WARNING: Port 0/1: Retry to execute fastboot -s Baytrail7094EABC -S 500M oem start_partitioning
04/21/18 00:36:18.151 WARNING: Port 0/1: Failed to execute ""C:/Program Files (x86)/Intel/Phone Flash Tool/fastboot.exe" -s Baytrail7094EABC -S 500M oem start_partitioning":
...
FAILED (remote: unknown command)
finished. total time: 0.003s
04/21/18 00:36:20.152 ERROR : Port 0/1: Flash failure
help, i don't know what to do