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
#

[Q] Boot Failed, no adb, hboot... please help

I did root my htc tattoo and somehow I flashed a wrong image, from then onwards I am having problem. After that I got RUU_Click_HTC_Asia_India_1.67.720.8_release_signed_NoDriver.exe, and ran that file on my system.. at last it failed saying that 100 - File cann't read error. Please see the image. Please help.... Please see my RUU log as below:
<LOG>
<T091246><INFO><VERSION>0, 9, 7, 4029</VERSION></INFO></T091246>
<T091252><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091252>
<T091253><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091253>
<T091253><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T091253>
<T091326><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T091326>
<T091331><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091331>
<T091333><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091333>
<T091336><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:</OUT>
</DEBUG></T091336>
<T091337><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091337>
<T091338><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091338>
<T091340><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091340>
<T091346><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T091346>
<T091347><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091347>
<T091348><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091348>
<T091349><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091349>
<T091351><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091351>
<T091352><DEBUG><CMD>fastboot -s HT9A6N503511 getvar battery-status</CMD>
<OUT>battery-status: good</OUT>
</DEBUG></T091352>
<T091352><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T091352>
<T091358><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091358>
<T091359><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091359>
<T091404><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091404>
<T091405><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091405>
<T091407><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091407>
<T091408><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091408>
<T091409><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091409>
<T091410><DEBUG><CMD>fastboot -s HT9A6N503511 getvar version-main</CMD>
<OUT>version-main: 1.67.720.8</OUT>
</DEBUG></T091410>
<T091439><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T091439>
<T091444><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091444>
<T091445><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091445>
<T091452><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091452>
<T091453><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091453>
<T091454><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091454>
<T091455><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091455>
<T091456><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091456>
<T091458><DEBUG><CMD>fastboot -s HT9A6N503511 getvar version-main</CMD>
<OUT>version-main: 1.67.720.8</OUT>
</DEBUG></T091458>
<T091503><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T091503>
<T091509><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091509>
<T091510><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091510>
<T091517><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091517>
<T091518><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091518>
<T091519><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091519>
<T091520><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091520>
<T091521><DEBUG><CMD>fastboot -s HT9A6N503511 oem rebootRUU</CMD>
<OUT>... OKAY</OUT>
</DEBUG></T091521>
<T091527><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091527>
<T091528><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091528>
<T091530><DEBUG><CMD>fastboot devices</CMD>
<OUT>HT9A6N503511 fastboot</OUT>
</DEBUG></T091530>
<T091531><DEBUG><CMD>fastboot -s HT9A6N503511 getvar boot-mode</CMD>
<OUT>boot-mode: RUU</OUT>
</DEBUG></T091531>
<T091534><DEBUG><CMD>fastboot -s HT9A6N503511 erase cache</CMD>
<OUT>erasing 'cache'...OKAY</OUT>
</DEBUG></T091534>
<T091534><DEBUG><CMD>fastboot -s HT9A6N503511 flash zip "C:\Users\Venkata Ramana Dodda\AppData\Local\Temp\{623B0154-01C2-4E8A-BB91-ACF8A5DCAB42}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T091534>
<T091535><DEBUG><OUT>sending 'zip' (90675 KB)...</OUT>
</DEBUG></T091535>
<T091547><DEBUG><OUT>OKAY</OUT>
</DEBUG></T091547>
<T091547><DEBUG><OUT>g the signature contained in this image...</OUT>
</DEBUG></T091547>
<T091609><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOstart image[hboot] unzipping for pre-update check...</OUT>
</DEBUG></T091609>
<T091609><DEBUG><OUT>INFOstart image[boot] unzipping & flushing...</OUT>
</DEBUG></T091609>
<T091610><DEBUG><OUT>INFO[RUU]UZ,boot,0</OUT>
</DEBUG></T091610>
<T091610><DEBUG><OUT>INFO[RUU]UZ,boot,51</OUT>
</DEBUG></T091610>
<T091610><DEBUG><OUT>INFO[RUU]UZ,boot,100</OUT>
</DEBUG></T091610>
<T091610><DEBUG><OUT>INFO[RUU]WP,boot,0</OUT>
</DEBUG></T091610>
<T091612><DEBUG><OUT>INFOstart image[hboot] unzipping & flushing...</OUT>
</DEBUG></T091612>
<T091612><DEBUG><OUT>INFO[RUU]UZ,hboot,0</OUT>
</DEBUG></T091612>
<T091613><DEBUG><OUT>INFO[RUU]UZ,hboot,100</OUT>
</DEBUG></T091613>
<T091613><DEBUG><OUT>INFO[RUU]WP,hboot,0</OUT>
</DEBUG></T091613>
<T091613><DEBUG><OUT>INFO[RUU]WP,hboot,100</OUT>
</DEBUG></T091613>
<T091613><DEBUG><OUT>INFOstart image[radio] unzipping & flushing...</OUT>
</DEBUG></T091613>
<T091613><DEBUG><OUT>INFO[RUU]UZ,radio,0</OUT>
</DEBUG></T091613>
<T091613><DEBUG><OUT>INFO[RUU]UZ,radio,6</OUT>
</DEBUG></T091613>
<T091614><DEBUG><OUT>INFO[RUU]UZ,radio,14</OUT>
</DEBUG></T091614>
<T091614><DEBUG><OUT>INFO[RUU]UZ,radio,19</OUT>
</DEBUG></T091614>
<T091614><DEBUG><OUT>INFO[RUU]UZ,radio,24</OUT>
</DEBUG></T091614>
<T091614><DEBUG><OUT>INFO[RUU]UZ,radio,33</OUT>
</DEBUG></T091614>
<T091614><DEBUG><OUT>INFO[RUU]UZ,radio,38</OUT>
</DEBUG></T091614>
<T091615><DEBUG><OUT>INFO[RUU]UZ,radio,43</OUT>
</DEBUG></T091615>
<T091615><DEBUG><OUT>INFO[RUU]UZ,radio,48</OUT>
</DEBUG></T091615>
<T091615><DEBUG><OUT>INFO[RUU]UZ,radio,53</OUT>
</DEBUG></T091615>
<T091615><DEBUG><OUT>INFO[RUU]UZ,radio,62</OUT>
</DEBUG></T091615>
<T091615><DEBUG><OUT>INFO[RUU]UZ,radio,67</OUT>
</DEBUG></T091615>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,76</OUT>
</DEBUG></T091616>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,81</OUT>
</DEBUG></T091616>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,86</OUT>
</DEBUG></T091616>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,91</OUT>
</DEBUG></T091616>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,96</OUT>
</DEBUG></T091616>
<T091616><DEBUG><OUT>INFO[RUU]UZ,radio,100</OUT>
</DEBUG></T091616>
<T091617><DEBUG><OUT>INFO[RUU]WP,radio,0</OUT>
</DEBUG></T091617>
<T091620><DEBUG><OUT>INFO[RUU]WP,radio,7</OUT>
</DEBUG></T091620>
<T091622><DEBUG><OUT>INFO[RUU]WP,radio,12</OUT>
</DEBUG></T091622>
<T091624><DEBUG><OUT>INFO[RUU]WP,radio,17</OUT>
</DEBUG></T091624>
<T091628><DEBUG><OUT>INFO[RUU]WP,radio,26</OUT>
</DEBUG></T091628>
<T091630><DEBUG><OUT>INFO[RUU]WP,radio,31</OUT>
</DEBUG></T091630>
<T091632><DEBUG><OUT>INFO[RUU]WP,radio,36</OUT>
</DEBUG></T091632>
<T091634><DEBUG><OUT>INFO[RUU]WP,radio,41</OUT>
</DEBUG></T091634>
<T091636><DEBUG><OUT>INFO[RUU]WP,radio,46</OUT>
</DEBUG></T091636>
<T091638><DEBUG><OUT>INFO[RUU]WP,radio,51</OUT>
</DEBUG></T091638>
<T091641><DEBUG><OUT>INFO[RUU]WP,radio,58</OUT>
</DEBUG></T091641>
<T091643><DEBUG><OUT>INFO[RUU]WP,radio,63</OUT>
</DEBUG></T091643>
<T091645><DEBUG><OUT>INFO[RUU]WP,radio,68</OUT>
</DEBUG></T091645>
<T091647><DEBUG><OUT>INFO[RUU]WP,radio,100</OUT>
</DEBUG></T091647>
<T091647><DEBUG><OUT>INFOstart image[recovery] unzipping & flushing...</OUT>
</DEBUG></T091647>
<T091647><DEBUG><OUT>INFO[RUU]UZ,recovery,0</OUT>
</DEBUG></T091647>
<T091647><DEBUG><OUT>INFO[RUU]UZ,recovery,45</OUT>
</DEBUG></T091647>
<T091647><DEBUG><OUT>INFO[RUU]UZ,recovery,87</OUT>
</DEBUG></T091647>
<T091647><DEBUG><OUT>INFO[RUU]UZ,recovery,100</OUT>
</DEBUG></T091647>
<T091648><DEBUG><OUT>INFO[RUU]WP,recovery,0</OUT>
</DEBUG></T091648>
<T091648><DEBUG><OUT>INFO[RUU]WP,recovery,44</OUT>
</DEBUG></T091648>
<T091648><DEBUG><OUT>INFO[RUU]WP,recovery,89</OUT>
</DEBUG></T091648>
<T091649><DEBUG><OUT>INFO[RUU]WP,recovery,100</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFOstart image[sp1] unzipping & flushing...</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFO[RUU]UZ,sp1,0</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFO[RUU]UZ,sp1,100</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFO[RUU]WP,sp1,0</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFO[RUU]WP,sp1,100</OUT>
</DEBUG></T091649>
<T091649><DEBUG><OUT>INFOstart image[system] unzipping & flushing...</OUT>
</DEBUG></T091649>
<T091650><DEBUG><OUT>INFO[RUU]UZ,system,0</OUT>
</DEBUG></T091650>
<T091650><DEBUG><OUT>INFO[RUU]UZ,system,2</OUT>
</DEBUG></T091650>
<T091650><DEBUG><OUT>INFO[RUU]UZ,system,5</OUT>
</DEBUG></T091650>
<T091651><DEBUG><OUT>INFO[RUU]UZ,system,8</OUT>
</DEBUG></T091651>
<T091651><DEBUG><OUT>INFO[RUU]UZ,system,11</OUT>
</DEBUG></T091651>
<T091652><DEBUG><OUT>INFO[RUU]UZ,system,14</OUT>
</DEBUG></T091652>
<T091652><DEBUG><OUT>INFO[RUU]UZ,system,16</OUT>
</DEBUG></T091652>
<T091653><DEBUG><OUT>INFO[RUU]UZ,system,19</OUT>
</DEBUG></T091653>
<T091653><DEBUG><OUT>INFO[RUU]UZ,system,22</OUT>
</DEBUG></T091653>
<T091653><DEBUG><OUT>INFO[RUU]UZ,system,25</OUT>
</DEBUG></T091653>
<T091654><DEBUG><OUT>INFO[RUU]UZ,system,28</OUT>
</DEBUG></T091654>
<T091654><DEBUG><OUT>INFO[RUU]UZ,system,30</OUT>
</DEBUG></T091654>
<T091655><DEBUG><OUT>INFO[RUU]UZ,system,33</OUT>
</DEBUG></T091655>
<T091655><DEBUG><OUT>INFO[RUU]UZ,system,36</OUT>
</DEBUG></T091655>
<T091656><DEBUG><OUT>INFO[RUU]UZ,system,39</OUT>
</DEBUG></T091656>
<T091656><DEBUG><OUT>INFO[RUU]UZ,system,42</OUT>
</DEBUG></T091656>
<T091657><DEBUG><OUT>INFO[RUU]UZ,system,44</OUT>
</DEBUG></T091657>
<T091657><DEBUG><OUT>INFO[RUU]UZ,system,47</OUT>
</DEBUG></T091657>
<T091657><DEBUG><OUT>INFO[RUU]UZ,system,50</OUT>
</DEBUG></T091657>
<T091705><DEBUG><OUT>INFO[RUU]WP,system,0</OUT>
</DEBUG></T091705>
<T091711><DEBUG><OUT>INFO[RUU]WP,system,2</OUT>
</DEBUG></T091711>
<T091715><DEBUG><OUT>INFOstart image[userdata] unzipping & flushing...</OUT>
</DEBUG></T091715>
<T091715><DEBUG><OUT>INFO[RUU]UZ,userdata,0</OUT>
</DEBUG></T091715>
<T091715><DEBUG><OUT>INFO[RUU]UZ,userdata,100</OUT>
</DEBUG></T091715>
<T091718><DEBUG><OUT>INFO[RUU]WP,userdata,0</OUT>
</DEBUG></T091718>
<T091718><DEBUG><OUT>INFO[RUU]WP,userdata,100</OUT>
</DEBUG></T091718>
<T091718><DEBUG><OUT>FAILED (remote: 51 partition update fail)</OUT>
</DEBUG></T091718>
<T091742><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
</OUT>
</DEBUG></T091742>
<T091743><DEBUG><CMD>fastboot devices</CMD>
<OUT />
</DEBUG></T091743>
<T091746><DEBUG><CMD>adb devices</CMD>
<OUT>adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:</OUT>
</DEBUG></T091746>
<T091747><DEBUG><CMD>fastboot devices</CMD>
<OUT />
</DEBUG></T091747>
<T091747><DEBUG><CMD>adb kill-server</CMD>
<OUT />
</DEBUG></T091747>
</LOG>

redownload file may be corrupted
if u can enter hboot ( as expecting after view pic ur phone on hboot ) try this
there is a ROM.zip in temp folder where from ruu setup running ( in task manager goto process than goto open file location ) copy that zip rename as CLICIMG.zip put on SD reboot hboot than goto fastboot if file ok your stock ROM will install

yatin kumar said:
redownload file may be corrupted
if u can enter hboot ( as expecting after view pic ur phone on hboot ) try this
there is a ROM.zip in temp folder where from ruu setup running ( in task manager goto process than goto open file location ) copy that zip rename as CLICIMG.zip put on SD reboot hboot than goto fastboot if file ok your stock ROM will install
Click to expand...
Click to collapse
Thanks Yatin for the reply, as it is S-ON and I don't have HBOOT mode. I think I bricked my phone.

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,

[how to]change your MID without the eng bootloader

this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T,developer,google play MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0712000 for modelid
fastboot reboot
________________________________________________________________________________________
-t mobile MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0713000 for modelid
fastboot reboot
________________________________________________________________________________________
-HTC_Europe MID:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0710000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/showthread.php?t=2477792
change lock status flag(lock/unlock bootloader): http://forum.xda-developers.com/showthread.php?t=2475914

i dont think im going to add any more MIDs in the above post,as i dont think many(any?) will be flip flopping to something other than those 3. it could be dnagerous to try and convert m7_ul to m7_u or m7_wlv
if you need to change to something different let me know,and i can put it here,so all the comands are in one place. this post is for reference only.
for HTC_Europe international m7_ul PN0710000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for m7_u PN0711000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for other gsm international m7_ul PN0714000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x34\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
for verizon,m7_wlv PN0731000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
*please note that neither sprint nor vzw devices can be converted to gsm or vice versa
for sprint, m7_wls PN0720000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
*please note that neither sprint nor vzw devices can be converted to gsm or vice versa
for htc one dual sim PN0751000
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x35\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384

@scotty1223
My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?

Great!
Please make for MID: PN0710000.

Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.

Nerekan said:
Great!
Please make for MID: PN0710000.
Click to expand...
Click to collapse
I think this is the command for "PN0710000"
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
but wait scotty1223 to confirm my theory.....
see U!

electronical said:
@scotty1223
My MID is currently: PN0711000 and i want to change it to: PN0710000
Can you add the correct command line in adb shell?
Click to expand...
Click to collapse
zaphodbeeb said:
Kudos 2 u man. Another really useful post. I would appreciate the code for PN0710000 also as I am currently planning on converting to the google edition, but would like to know the code to revert back to the above if I need to return to HTC at sometime. Much more convienient (and less risky) than using eng boot method to change.
Click to expand...
Click to collapse
what model/variant do you guys have? if this is another variant of m7_u,let me know if you run into any snags or issues with the conversion to google play,wich is an m7_ul. id really appreciate reports of success or failure for OTAs.
id like to convert my dads m7_u(PN0711000) to HTC__001 and PN0712000 so he could recieve european updated. not sure if OTAs will catch some other flag since the m7_u has no provisions for LTE.
feel free to post here or pm me anything you learn while converting,and if you intend to OTA or not
ervius said:
I think this is the command for "PN0710000"
Code:
echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384
but wait scotty1223 to confirm my theory.....
see U!
Click to expand...
Click to collapse
looks fine- x30 = 0 so just need to replace the 31,wich obviously = 1

I have a m7_ul.

zaphodbeeb said:
I have a m7_ul.
Click to expand...
Click to collapse
and are PN0711000?
edit:
i see,you are international. outside the us m7_ul is the PN710000. had some MID confusion,lol.. move along,nothing to see here

OK I have a uk HTC one my current mid is PN0710000
I would like the gpe MID is this the att developer edition you have listed on the first page?
Edit also guessing you need root?

ngagephone said:
OK I have a uk HTC one my current mid is PN0710000
I would like the gpe MID is this the att developer edition you have listed on the first page?
Edit also guessing you need root?
Click to expand...
Click to collapse
correct,to the best of my knowledge,the GPE shares PN0712000 along with dev edition,att,and canadian variants.
yes,you need root and s-off.

Thank you

Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?
Sent from my HTC ViperOne

tommy0411 said:
Just clarify,
If I have an US T-mobile One, I wanna convert to International version as I can get the x.xx.401.xx OTA, I have to change my CID to HTC_001 and MID to PN0710000. Is this correct?
Sent from my HTC ViperOne
Click to expand...
Click to collapse
correct

That's one neat hack. Thank you for this!
Sent from my HTC One using Tapatalk

io53 said:
That's one neat hack. Thank you for this!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
glad it was helpful. basically the same idea as hex editing p4 to change cid with evita and ville,so its not a new concept. all i did was locate the mid and apply the same idea

Is the MID on the same place in the GE bootloaders?
Sent from my HTC One using Tapatalk

io53 said:
Is the MID on the same place in the GE bootloaders?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The mid is not located in the bootloader,it's in p6. I'm fairly certain the mid is in the same location,but I've not checked it. You're welcome to dump it and we can verify.
Sent from my HTC One VX using Tapatalk

Change MID to 710000 from 714000 (S-off)
scotty1223 said:
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-AT&T,developer,google play MID:
enter the following:
adb shell
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0712000 for modelid
fastboot reboot
________________________________________________________________________________________
-t mobile MID:
enter the following:
adb shell
Code:
[B]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x31\x00\x33\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify PN0713000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
http://forum.xda-developers.com/showthread.php?t=2477792
http://forum.xda-developers.com/showthread.php?t=2475914&highlight=+how+to+lock+unlock
Click to expand...
Click to collapse
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)
---------- Post added at 03:08 PM ---------- Previous post was at 03:07 PM ----------
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error (error 24)

papubhai said:
Hi,
I'm on Hboot 1.55 and I'm s-off MID =714000 and CID =11111111. Please guide me to change the MID to 710000 as i need OTA from CID HTC__001. Urgent help would be very welcomed...Many many thanks.. Eng method fails with remote parsing error
Click to expand...
Click to collapse
you just enter the adb command in the second post for 710000. if you need more guidance than what the OP states,you maybe not should do this.
im not sure you should do this,anyway. there is likely a reason the eng method failed. what variant is 714000?
if you are m7_ul it should be ok to switch to 710000.but if you are something else(m7_u,m7_wls,etc) it may not be safe to convert to that cid/mid