S-OFF Gone Wrong - Bootlooping - Verizon Droid Incredible 2
Well, I had unlocked my son's HTC Incredible 2 with the HTC Dev Tool. All was good until I went to install a ROM and it choked at the white HTC screen. I got it up thanks to the forums but then decided to go for full blown S-OFF via the comprehensive directions.
It was going well but something must have went wrong somewhere and I'm slightly fearful that I may be screwed.
Here's my fastboot info as of now:
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-boot
It's bootlooping now. If I reset it in fastboot, it will come up and stay up until I reboot it myself. I have no recovery and when I try to unlock the phone with the steps via the dev tool, it fails (signature verify fail).
Anyone have any ideas? I've got a log of my comprehensive adventure if it helps.
Meh, here is the log anyway. Things look weird when I lock it and at the end...
Code:
D:\htc>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.062
2_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
D:\htc>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
D:\htc>md5sums misc_version
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
misc_version 050f55d34ddbcc860efa5982491437de
D:\htc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT144MA07332 device
D:\htc>adb push CWM-SuperSU-v0.94.zip /mnt/sdcard
1447 KB/s (674673 bytes in 0.455s)
D:\htc>adb reboot bootloader
D:\htc>fastboot devices
HT144MA07332 fastboot
D:\htc>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.692s]
writing 'recovery'... OKAY [ 0.946s]
finished. total time: 2.638s
D:\htc>adb push misc_version /data/local/tmp/misc_version
error: device not found
D:\htc>adb push misc_version /data/local/tmp/misc_version
1792 KB/s (367096 bytes in 0.200s)
D:\htc>adb shell chmod 777 /data/local/tmp/misc_version
D:\htc>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
D:\htc>adb reboot bootloader
D:\htc>fastboot devices
HT144MA07332 fastboot
D:\htc>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s
D:\htc>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.543s
D:\htc>fastboot erase cache
erasing 'cache'... OKAY [ 0.182s]
finished. total time: 0.182s
D:\htc>fastboot oem rebootRUU
... OKAY [ 0.162s]
finished. total time: 0.162s
D:\htc>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_
1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 47.862s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,31
INFO[RUU]UZ,boot,73
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,22
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,63
INFO[RUU]UZ,recovery,84
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,13
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,61
INFO[RUU]UZ,system,65
INFO[RUU]WP,system,0
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,13
INFO[RUU]WP,system,16
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,30
INFO[RUU]WP,system,33
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,47
INFO[RUU]WP,system,50
INFO[RUU]WP,system,55
INFO[RUU]WP,system,59
INFO[RUU]WP,system,65
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,67
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,73
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,98
INFO[RUU]WP,system,65
INFO[RUU]WP,system,67
INFO[RUU]WP,system,70
INFO[RUU]WP,system,73
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,7
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,21
INFO[RUU]UZ,radio,27
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,42
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,55
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,83
INFO[RUU]UZ,radio,90
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,5
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,33
INFO[RUU]WP,radio,42
INFO[RUU]WP,radio,100
OKAY [208.359s]
finished. total time: 256.221s
D:\htc>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.245s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.096s
finished. total time: 6.087s
D:\htc>fastboot reboot
rebooting...
finished. total time: 0.155s
run revolutionary THEN flash the radio
JehC said:
run revolutionary THEN flash the radio
Click to expand...
Click to collapse
Lol I remember telling you that
Did you re-lock the bootloader before trying to s-off? That needs to be done
Sent from my HTC Incredible 2 using xda app-developers app
You guys rock! I didn't even think about running Revolutionary. I just assumed something was jacked and it wouldn't work. I'm not sure if I did something wrong to get it in that state but it would have been nice to see this mentioned in the comprehensive instructions.
At any rate. I'm back in business. Thanks for the help.
Sure did, and I've spread the word a few times myself
sent from my paranoid android
clambert11 said:
You guys rock! I didn't even think about running Revolutionary. I just assumed something was jacked and it wouldn't work. I'm not sure if I did something wrong to get it in that state but it would have been nice to see this mentioned in the comprehensive instructions.
At any rate. I'm back in business. Thanks for the help.
Click to expand...
Click to collapse
What do you want mentioned in my guide? That you need to flash the radio after Revolutionary? I had it that way originally but people weren't able to boot before flashing the new radio. I haven't actually run it myself so I don't know for sure what works all the time.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
What do you want mentioned in my guide? That you need to flash the radio after Revolutionary? I had it that way originally but people weren't able to boot before flashing the new radio. I haven't actually run it myself so I don't know for sure what works all the time.
Click to expand...
Click to collapse
When I was done following the steps, the phone was bootlooping. Maybe that's not normal. The only way I could get it to stop was to do a factory reset from Fastboot. If the phone was rebooted or powered off after that, the bootloops would happen all over again.
I just thought if the booplooping was normal it might be worth mentioning in the tutorial, that's all. But I could have been the exception, in which case it wouldn't make sense to mention it.
if i remember right, after i downgraded i was able to boot once without bootlooping, then ran revolutionary, then flashed the radio
pppp
this problem i have too. any ideas?
gioodo said:
this problem i have too. any ideas?
Click to expand...
Click to collapse
run revolutionary first and when its done flash radio
here use these instructions
download and run Revolutionary
you can have revolutionary install a recovery,or install one manually after s-off is achieved. included in miniadb_inc2.zip (the one you downloaded for s-off) download is the 0312 radio, which you will need to flash if you start experiencing bootloops.
if you need to flash the 0312 radio:
put the phone in fastboot mode(select fastboot from hboot menu),open a cmd window,change to miniadb_inc2 directory then enter:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)
fastboot reboot-bootloader (make sure your baseband changed)
fastboot reboot
i have error on flashing process C:\inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.362s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.715s
gioodo said:
i have error on flashing process C:\inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.362s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.715s
Click to expand...
Click to collapse
You need to run revolutionary first before flashing radio radio can't be flashed with s-on
Sent from my ADR6350 using xda app-developers app
ArslanQureshi said:
You need to run revolutionary first before flashing radio radio can't be flashed with s-on
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
please see this my post http://forum.xda-developers.com/showthread.php?p=47003009#post47003009
i have unlock token Can't see locked or not
Related
[Q] (semi)bricked nand | hboot (s-off) + clockworkmod (without usb) alive
info: htc desire bravo | hboot 0.93 S-OFF | clockworkmod 2.5.0.7 well, beeing brain-afk while following a guide for cyanogenmod6 with a2sd, i used a mtd-repartition tool for the g1. after repartitioning and rebooting, clockworkmod cant mount sdcard anymore - probably because device nodes got changed. "E: Can't mount /dev/block/mmcblk0 i reflashed clockworkmod via fastboot hoping it could fix something, but no, didnt help. i cant install any zip because i have no sd-card. i cant boot to the android system, because i dont have an android system. my idea would be: erase recovery, flash a tool which restores partition table, start "recovery" so that this tool does its job, flash clockwork mod again and install the operating system. any better ideas or hints for what that "magical tool" can be would be appreciated.
after more reading and more testing, i understand, i destroyed the SPL this would explain: why sdcard isnt mountable why i cant access the device via adb why linux doesn't detecht a propper device - only a high-speed usb device next on investigate list: how to flash an spl - isnt that what hboot s-off includes?
mad-murdock said: after more reading and more testing, i understand, i destroyed the SPL this would explain: why sdcard isnt mountable why i cant access the device via adb why linux doesn't detecht a propper device - only a high-speed usb device next on investigate list: how to flash an spl - isnt that what hboot s-off includes? Click to expand... Click to collapse yes alpharev is a modfied spl, but i dont know if your going to flash it if nothing will detect your device as a desire
well, even more testing... my alpharev hboot does support flashing all partitions! great! i did like its said on the alpharev homepage: Code: fastboot flash hboot bravo_alphaspl.img it said, it worked. i had an old leedroid backup and found this: Code: V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash boot boot.img sending 'boot' (2944 KB)... OKAY [ 0.564s] writing 'boot'... OKAY [ 0.816s] finished. total time: 1.381s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash recovery recovery .img sending 'recovery' (4608 KB)... OKAY [ 0.636s] writing 'recovery'... OKAY [ 1.318s] finished. total time: 1.955s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash cache cache.img sending 'cache' (14 KB)... OKAY [ 0.017s] writing 'cache'... OKAY [ 0.289s] finished. total time: 0.306s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash data data.img sending 'data' (113672 KB)... OKAY [ 15.289s] writing 'data'... FAILED (remote: partition does not exist!) finished. total time: 15.293s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash system system.img sending 'system' (247291 KB)... FAILED (remote: data length is too large) finished. total time: 0.005s so, no system and data partition around - hboot, recovery and boot already reflashed. i also tried the spl with less system and more data bravo_alphaspl-n1table.img - but it doesnt seam to create the partitions if they are missing. edit: why is fastboot missing in the linux android sdk btw? have to use windows for this...
its late, and i cant find a way to get further. no idea how to re-setup my mtd partitions atm or why i dont have adb in clockworkmod even i reflashed the spl. tomorrow is a new day, and i am hoping for you guys...
mad-murdock said: well, even more testing... my alpharev hboot does support flashing all partitions! great! i did like its said on the alpharev homepage: Code: fastboot flash hboot bravo_alphaspl.img it said, it worked. i had an old leedroid backup and found this: Code: V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash boot boot.img sending 'boot' (2944 KB)... OKAY [ 0.564s] writing 'boot'... OKAY [ 0.816s] finished. total time: 1.381s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash recovery recovery .img sending 'recovery' (4608 KB)... OKAY [ 0.636s] writing 'recovery'... OKAY [ 1.318s] finished. total time: 1.955s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash cache cache.img sending 'cache' (14 KB)... OKAY [ 0.017s] writing 'cache'... OKAY [ 0.289s] finished. total time: 0.306s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash data data.img sending 'data' (113672 KB)... OKAY [ 15.289s] writing 'data'... FAILED (remote: partition does not exist!) finished. total time: 15.293s V:\nandroid\LeeDrOiD 2.2a - 2010-10-14.19.57.06>fastboot flash system system.img sending 'system' (247291 KB)... FAILED (remote: data length is too large) finished. total time: 0.005s so, no system and data partition around - hboot, recovery and boot already reflashed. i also tried the spl with less system and more data bravo_alphaspl-n1table.img - but it doesnt seam to create the partitions if they are missing. edit: why is fastboot missing in the linux android sdk btw? have to use windows for this... Click to expand... Click to collapse The /data partition is called 'userdata'. So use 'fastboot flash userdata <img>'. In regards to the system partition, fastboot has a 220M (about that size) limit. To overcome this limit (and do all of the above at once): Zip the images you have: -boot.img -recovery.img -cache.img -userdata.img -system.img Add to this a file called android-info.txt: Code: modelid: PB9920000 cidnum: HTC__001 cidnum: HTC__E11 cidnum: HTC__N34 cidnum: HTC__203 cidnum: HTC__102 cidnum: HTC__K18 cidnum: HTC__405 cidnum: HTC__Y13 cidnum: HTC__A07 cidnum: HTC__304 cidnum: HTC__016 cidnum: HTC__032 hbootpreupdate:3 mainver: 2.10.405.2 DelCache: 1 Flash the zip using fastboot: fastboot erase cache fastboot oem rebootRUU fastboot flash zip <whatever-you-called-it.zip> Done!
thanks for your reply ieftm. i really was full of hope, that this would work / fix my phone. unfortuatly, it throws an error: Code: d:\android-sdk-windows\tools>fastboot flash zip hope.zip sending 'zip' (220155 KB)... OKAY [ 29.738s] writing 'zip'... INFOzip header checking... INFOzip info parsing... INFOchecking model ID... INFOchecking custom ID... FAILED (remote: 42 custom id check fail) finished. total time: 35.256s will search the forum now for infos about android-info.txt - do you think, this also would fix the part why clockworkmod cant access the sdcard anymore? edit: i tried both unix and dos format for the .txt file (crlf vs lf) - both produces the same result
i downloaded RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe i extracted the rom.zip and extracted the android-info.txt - still the same error. to be honest, i am thrilled to install the RUU and start all over again. but if that fails, i got nothing left - no modified hboot, no clockworkmod
mad-murdock said: edit: why is fastboot missing in the linux android sdk btw? have to use windows for this... Click to expand... Click to collapse You can get the linux fastboot from here: developer.htc.com/adp.html#s2 (I'm not allowed to post external links, so I had to remove http)
Solved! Device working again. |Jason8| -my personal hero for october 2010- told me on irc to check this guide - turns out, things on desire are slightly different. my problem -for anyone running in similar stuff later- is called usb brick - and the solution for desire is found here thank you so much |Jason8| - i finally can use my phone again ...18 hours of confusion at an end
This is what i did, use a Micro SD card reader and format your SD card. Here is a link to a formatter, http://www.sdcard.org/consumers/formatter/ then when you double click the sd card on My Computer, it will say you need to format again. Do it and then repartition your SD card. YES, what i did WORKED. because i had the exact same problem. hope this helps
that wasnt my problem - the sdcard was fine - problem was, i messed up the misc mtd-partition on nand. its solved now - see first page, last post thanks for your reply anyways ^^
S710d HTCDev Unlock 2.3.4 hboot 1.04 help, please
Hey, guys. Been searching around the forums for a couple days. Found plenty of people with my problem, but no one seemed to post their solutions. I'm a Candian living in China, and am looking to root for obvious reasons. Running HTC S710d, 2.3.4 with Hboot 1.04 I'm using Prototype7's guide, however when I get to: adb shell /data/local/tmp/misc_version -s 2.18.605.3 adb shell /data/local/tmp/misc_version -s 2.18.605.3 Patching and backing up misc partition... Error opening input file. Is my return. Any help would be greatly appreciated.
Exzyle said: Hey, guys. Been searching around the forums for a couple days. Found plenty of people with my problem, but no one seemed to post their solutions. I'm a Candian living in China, and am looking to root for obvious reasons. Running HTC S710d, 2.3.4 with Hboot 1.04 I'm using Prototype7's guide, however when I get to: adb shell /data/local/tmp/misc_version -s 2.18.605.3 adb shell /data/local/tmp/misc_version -s 2.18.605.3 Patching and backing up misc partition... Error opening input file. Is my return. Any help would be greatly appreciated. Click to expand... Click to collapse Firmware version? Are you running a custom ROM or stock 6.x?
Actually, the ROM version says 3.x.
type "adb shell /data/local/tmp/misc_version -s 2.18.605.3"
JehC said: type "adb shell /data/local/tmp/misc_version -s 2.18.605.3" Click to expand... Click to collapse C:\Android>adb shell $ /data/local/tmp/misc_version -s 2.18.605.3 /data/local/tmp/misc_version -s 2.18.605.3 --set_version set. VERSION will be changed to: 2.18.605.3 Patching and backing up misc partition... Error opening input file. $ Recognized the dollar sign, so I tried SU. $ su su # /data/local/tmp/misc_version -s 2.18.605.3 /data/local/tmp/misc_version -s 2.18.605.3 --set_version set. VERSION will be changed to: 2.18.605.3 Patching and backing up misc partition... # exit exit $ exit exit C:\Android>adb reboot bootloader C:\Android>fastboot devices HC27JMA00835 fastboot C:\Android>fastboot getvar mainver mainver: 2.18.605.3 finished. total time: 0.001s That however, got me here... C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip sending 'zip' (292817 KB)... OKAY [ 62.949s] writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 102.758s There is an option to disable signature verification in 4ext. Is this what I want to do?
Exzyle said: C:\Android>adb shell $ /data/local/tmp/misc_version -s 2.18.605.3 /data/local/tmp/misc_version -s 2.18.605.3 --set_version set. VERSION will be changed to: 2.18.605.3 Patching and backing up misc partition... Error opening input file. $ Recognized the dollar sign, so I tried SU. $ su su # /data/local/tmp/misc_version -s 2.18.605.3 /data/local/tmp/misc_version -s 2.18.605.3 --set_version set. VERSION will be changed to: 2.18.605.3 Patching and backing up misc partition... # exit exit $ exit exit C:\Android>adb reboot bootloader C:\Android>fastboot devices HC27JMA00835 fastboot C:\Android>fastboot getvar mainver mainver: 2.18.605.3 finished. total time: 0.001s That however, got me here... C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip sending 'zip' (292817 KB)... OKAY [ 62.949s] writing 'zip'... INFOadopting the signature contained in this image... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 102.758s There is an option to disable signature verification in 4ext. Is this what I want to do? Click to expand... Click to collapse Relock your device then flash Sent from my Goonified Paranoid Jelly Droid Incredible 2
The device was locked, although I should have included that. Skipped it since it worked. Here's all of the pertinent code, of course as I said, the device has been relocked at this stage. C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01 .0622_NV_VZW1.92_release_199487_si.zip MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+ Copyright (C) 2001-2005 Jem Berkes Type md5sums -h for help [Path] / filename MD5 sum ------------------------------------------------------------------------------- [C:\Android\] RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255 C:\Android>fastboot devices HC27JMA00835 fastboot C:\Android>fastboot getvar mainver mainver: 2.18.605.3 finished. total time: 0.001s C:\Android>fastboot oem lock ... INFODevice was already locked! OKAY [ 0.006s] finished. total time: 0.006s C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.141s] finished. total time: 0.141s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.146s] finished. total time: 0.147s C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip sending 'zip' (292817 KB)... OKAY [ 60.221s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 110.190s
Exzyle said: The device was locked, although I should have included that. Skipped it since it worked. Here's all of the pertinent code, of course as I said, the device has been relocked at this stage. C:\Android>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01 .0622_NV_VZW1.92_release_199487_si.zip MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+ Copyright (C) 2001-2005 Jem Berkes Type md5sums -h for help [Path] / filename MD5 sum ------------------------------------------------------------------------------- [C:\Android\] RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255 C:\Android>fastboot devices HC27JMA00835 fastboot C:\Android>fastboot getvar mainver mainver: 2.18.605.3 finished. total time: 0.001s C:\Android>fastboot oem lock ... INFODevice was already locked! OKAY [ 0.006s] finished. total time: 0.006s C:\Android>fastboot erase cache erasing 'cache'... OKAY [ 0.141s] finished. total time: 0.141s C:\Android>fastboot oem rebootRUU ... OKAY [ 0.146s] finished. total time: 0.147s C:\Android>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip sending 'zip' (292817 KB)... OKAY [ 60.221s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 110.190s Click to expand... Click to collapse Try again, redownload and try a few times. If it still won't work, try renaming it to PG32IMG.zip, put it in the root of your sdcard and just boot into the bootloader.
I re-downloaded the file, renamed the file PG32IMG and dropped it in the root of my SD card. Booted into bootloader, the bootloader found the zip file, a blue progresss bar filled, then said it was checking, a yellow progress bar filled and then... Nothing. Figured maybe you meant the Radio file, so I did the same. Also nothing. Am I missing something?
Still no luck guys. Anyone able to offer any help? Getting very frustrated.
You're still at 2.3.4 s-on right? try this in command prompt/terminal whichever you use: "fastboot devices" "fastboot getvar mainver" make sure its 2.18.605.3 "fastboot oem lock" (unless your bootloader already says relocked) "fastboot erase cache" "fastboot oem rebootRUU" wait until you're at a black screen that says HTC "fastboot flash zip (name of zip, the RUU)" it'll take awhile, don't touch anything till it's done. you'll now be at android 2.3.3, run revolutionary. once that's finished. "adb devices" "adb reboot bootloader" "fastboot oem rebootRUU" "fastboot flash zip (name of zip, the radio)" same as before
[Q] Can't flash firmware
I'm trying to flash firmware from this thread http://forum.xda-developers.com/show....php?t=1957376 CID HTC__001 and I'm constantly getting error remote: not allowed I've followed instructions to the letter http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html#more but I'm getting this error every time. Any help appreciated.
Dr. MadMan said: I'm trying to flash firmware from this thread http://forum.xda-developers.com/show....php?t=1957376 CID HTC__001 and I'm constantly getting error remote: not allowed I've followed instructions to the letter http://www.flow-wolf.net/2012/10/htc-one-x-perfect-guide-for-beginners.html#more but I'm getting this error every time. Any help appreciated. Click to expand... Click to collapse If you boot your device into bootloader, does it say UNLOCKED at the top? Chances are that it is still locked.
You need to be locked to update firmware.
I don't know if it's necessary but i relocked the bootloader to flash the firmware. Here are the steps i performed fastboot oem lock ( to relock the bootloader) fastboot oem rebootRUU (note the capitals on RUU) fastboot flash zip nameoffirmware.zip I then reunlocked and flashed arhd custom rom Sent from my HTC One X using xda app-developers app
I have S-OFF and for firmware flash you have to bel locked so on top I have ****RELOCKED**** and Hboot is on version 1.12
Got firmware flashed! Now I flashed recovery and when I booted to recovery I only get blank screen. So recovery is up but no graphics.
Please give more info. Does it just sit on a black screen Is there anything at all on the screen Does it just flash black and then carry on booting as normal Sent from my HTC One X using xda app-developers app
When I want to boot recovery it looks like it's booting and then it switches to completely black screen. When I press power button long enough i get three flashes on hard buttons on bottom and then phone powers down.
Below is my whole flashing procedure. I have firmware for cid HTC__001 got it from here http://forum.xda-developers.com/showthread.php?t=1957376 I took boot image from ARHD 17.1 link and recovery from official link. Did I missed something? or am I doing it in wrong way? Code: C:\onex>fastboot oem lock ... (bootloader) Lock successfully... FAILED (status read failed (Too many links)) finished. total time: 0.181s C:\onex>fastboot oem rebootRUU ... (bootloader) Save data from original MSC... (bootloader) Save data from SIF... (bootloader) Update partition data to SIF partition (bootloader) Update partition data from original MSC... (bootloader) [MSG] OKAY OKAY [ 0.346s] finished. total time: 0.346s C:\onex>fastboot flash zip firmware.zip sending 'zip' (12875 KB)... OKAY [ 1.713s] writing 'zip'... (bootloader) shift signature_size for header checking... (bootloader) checking model ID... (bootloader) checking custom ID... (bootloader) start image[hboot] unzipping for pre-update check... (bootloader) start image[hboot] flushing... FAILED (remote: 90 hboot pre-update! please flush image again immediately) finished. total time: 17.005s C:\onex>fastboot flash zip firmware.zip sending 'zip' (12875 KB)... OKAY [ 1.654s] writing 'zip'... (bootloader) shift signature_size for header checking... (bootloader) checking model ID... (bootloader) checking custom ID... (bootloader) start image[boot] unzipping & flushing... (bootloader) Format partition LNX done (bootloader) [RUU]WP,boot,100 (bootloader) start image[recovery] unzipping & flushing... (bootloader) Format partition SOS done (bootloader) [RUU]WP,recovery,100 (bootloader) ERASE backup cid OKAY [ 2.712s] finished. total time: 4.366s C:\onex>fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.153s] finished. total time: 0.153s C:\onex>fastboot flash unlocktoken Unlock_code.bin sending 'unlocktoken' (0 KB)... OKAY [ 0.029s] writing 'unlocktoken'... (bootloader) unlock token check successfully FAILED (status read failed (Too many links)) finished. total time: 5.878s C:\onex>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img sending 'recovery' (5742 KB)... OKAY [ 0.830s] writing 'recovery'... (bootloader) Format partition SOS done OKAY [ 0.571s] finished. total time: 1.401s C:\onex>fastboot flash boot boot.img sending 'boot' (5192 KB)... OKAY [ 0.672s] writing 'boot'... (bootloader) Format partition LNX done OKAY [ 0.572s] finished. total time: 1.244s C:\onex>fastboot erase cache erasing 'cache'... OKAY [ 0.210s] finished. total time: 0.210s
mhm... looks fine. maybe the download of the recovery is defect or corrupt. did you try to download the recovery again and install it?
If I flash same recovery file when I have stock RUU 2.17 on phone it boots normally. So the file is OK.
Unrooted, Stock HTC One X dead
hi, my htc one x is dead, i cannot on it. heres what happened. i was facebooking then the app keep crashing then after that everything started crashing, like got this google processor thing and aft that my whole phone just shut down then when i hold the power button, got this weird thing come out like some weird numbers then got option HBOOT, REBOOT, REBOOT something loader, and POWER DOWN after that i managed to got into recovery and hard resetted it but it got stuck at the htc one logo. help!
If you never unlocked the bootloader ....send it in for warranty. Nothing we can do about that !
D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem readcid ... INFODEBUG: cid: VODAP001 OKAY [ 0.035s] finished. total time: 0.035s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot getvar version-m version-main: 3.14.161.27 finished. total time: 0.035s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem RebootRUU ... INFO[ERR] Command error !!! OKAY [ 0.020s] finished. total time: 0.021s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem lock ... INFOLock successfully... FAILED (status read failed (Too many links)) finished. total time: 0.152s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem RebootRUU ... INFO[ERR] Command error !!! OKAY [ 0.128s] finished. total time: 0.129s D:\Tel\one x\soft\Fastboot\Fastboot> i can't run rebootRRU i want return to stock rom .i not have backup from 3.14.161.27 what can i do ? thx
Type fastboot oem rebootRUU (Not RebootRUU)
thank you very mutch you right can you help me more ? firmware111.zip is OTA_ENDEAVOR_U_JB_45_S_Vodafone_UK_3.14.161.27-2.17.161.4_release_299172atv1b11ychs0d2fs D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem readcid ... INFODEBUG: cid: VODAP001 OKAY [ 0.012s] finished. total time: 0.012s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem lock ... INFOLock successfully... FAILED (status read failed (Too many links)) finished. total time: 0.141s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem rebootRUU ... INFOSave data from original MSC... INFOSave data from SIF... INFOUpdate partition data to SIF partition INFOUpdate partition data from original MSC... INFO[MSG] OKAY OKAY [ 0.206s] finished. total time: 0.207s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware.zip sending 'zip' (12876 KB)... OKAY [ 1.676s] writing 'zip'... INFOadopting the signature contained in this i mage... INFOsignature checking... INFOchecking model ID... INFOchecking custom ID... INFOchecking main version... INFOchecking hboot version... INFOstart image[hboot] unzipping for pre-update check... INFOstart image[boot] unzipping & flushing... INFOFormat partition LNX done INFO[RUU]WP,boot,100 INFOstart image[hboot] unzipping & flushing... INFO[RUU]WP,hboot,50 INFOsignature checking... INFOstart image[recovery] unzipping & flushing... INFOFormat partition SOS done INFO[RUU]WP,recovery,100 INFOERASE backup cid OKAY [ 4.825s] finished. total time: 6.503s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip sending 'zip' (374962 KB)... OKAY [ 48.630s] writing 'zip'... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 65.465s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot erase cache erasing 'cache'... OKAY [ 0.186s] finished. total time: 0.186s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot oem rebootRUU ... INFOSave data from original MSC... INFOSave data from SIF... INFOUpdate partition data to SIF partition INFOUpdate partition data from original MSC... INFO[MSG] OKAY OKAY [ 0.193s] finished. total time: 0.194s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip sending 'zip' (374962 KB)... OKAY [ 48.869s] writing 'zip'... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 65.693s D:\Tel\one x\soft\Fastboot\Fastboot>fastboot getvar version-main version-main: 3.14.161.27 finished. total time: 0.006s
Well you flashed your firmware. What else do you need? What are you even trying to do?
I guess a custom recovery and a brand new JB Rom
Mr Hofs said: I guess a custom recovery and a brand new JB Rom Click to expand... Click to collapse I installed custom ROM, based on the 3.14 stock, I had the working device but without cellular network (no signal / no service) and with WiFi whish is working incorrectly (it couldn't detect my home wireless network, for example) but i prefer to install the stock rom (vodafone UK) . i don't no what i did wrong
Did you flash the correct boot.img file ?
TToivanen said: Well you flashed your firmware. What else do you need? What are you even trying to do? Click to expand... Click to collapse my firmware not was completed when i flash D:\Tel\one x\soft\Fastboot\Fastboot>fastboot flash zip firmware111.zip sending 'zip' (374962 KB)... OKAY [ 48.869s] writing 'zip'... INFOsignature checking... FAILED (remote: 12 signature verify fail) finished. total time: 65.693s ---------- Post added at 12:07 AM ---------- Previous post was at 12:02 AM ---------- Mr Hofs said: Did you flash the correct boot.img file ? Click to expand... Click to collapse yes the boot from custom rom , afther erase cache , install rom , i switch on the phone same problem everithing ok but network signal and wifi doesn't work , after this ncx_317_v14-RENOVATE , boot.img and update zip ...
your main version number tells me you have an updated JB hboot ! did you do a FULL wipe in the recovery before installng the new rom ?
yes i did every time , i think all i need is a compatible karnel with mods , i try a lot but i didn't find. can you help me with OTA_ENDEAVOR_U_JB_45_S_Vodafone_UK_3.14.161.27-2.17.161.4_release_299172atv1b11ychs0d2fs.exe ??
What do you mean.....the kernel delivered with the rom is in 99% the right boot.img. except for some aosp roms. Flash the delivered boot.img from the desired rom, perform a full wipe and install the rom ....must work ! Dont know what you tried ? I bet your ruu has not been released Btw you need to full wipe that means, cache, dalvik cache, data, system before you install the new rom......dalvik cache is forgotten a lot
Hey this thread is going in the wrong direction. Lol! This isnt even about my question..
PokMahPok said: Hey this thread is going in the wrong direction. Lol! This isnt even about my question.. Click to expand... Click to collapse You've been highjacked mate.... so what about your problem ? Edit : and i never got a answer from you regarding your question !
WLAN does not work after 4.4 Update
Hey Guys, i wanted to upgrade my HTC One M8 to the newest T-Mobile Germany Firmware. My HTC One was rooted and I had the TWRP Recovery with ViperRom. I installed a Nandroid Backup with the 1.12.111.18 (4.3) Firmware. After that i installed the 1.57.111.2 Stock Recovery, than I relocked the Bootloader and after the Root was gone, I updated my Phone to the 1.57.111.2 (4.4.2), and now my WiFi is not working. I even upgraded to a newer Version of the Stock Recovery, but it still not working. Here are some Information about my Phone. HBOOT-3.18.0.0000 RADIO-1.19.21331147A1.09G OS- CIDNUM: T-MOB101 If you guys, need some other Information. Just let me know.
lepush said: Hey Guys, i wanted to upgrade my HTC One M8 to the newest T-Mobile Germany Firmware. My HTC One was rooted and I had the TWRP Recovery with ViperRom. I installed a Nandroid Backup with the 1.12.111.18 (4.3) Firmware. After that i installed the 1.57.111.2 Stock Recovery, than I relocked the Bootloader and after the Root was gone, I updated my Phone to the 1.57.111.2 (4.4.2), and now my WiFi is not working. I even upgraded to a newer Version of the Stock Recovery, but it still not working. Here are some Information about my Phone. HBOOT-3.18.0.0000 RADIO-1.19.21331147A1.09G OS- CIDNUM: T-MOB101 If you guys, need some other Information. Just let me know. Click to expand... Click to collapse Are you S-Off? You can't revert to older firmware while you are S-On.
xunholyx said: Are you S-Off? You can't revert to older firmware while you are S-On. Click to expand... Click to collapse I'm on S-On, but I want to install a newer Firmware not downgrade to an older one. This is what I get when I try to install the OTA Update Code: xxx-imac:~ x$ cd Desktop xxx-imac:Desktop xxx$ cd adb xxx-imac:adb xxx$ ./fastboot devices HT459WM15609 fastboot xxx-imac:adb xxx$ ./fastboot oem rebootRUU ... (bootloader) Start Verify: 3 OKAY [ 0.010s] finished. total time: 0.010s xxx-imac:adb xxx$ ./fastboot flash zip OTA_M8_UL_K44_SENSE60_SECURITY_TMO_DE_1.70.111.1-1.57.111.2_release_383280.zip target reported max download size of 1830612992 bytes sending 'zip' (253074 KB)... OKAY [ 9.223s] writing 'zip'... (bootloader) zip header checking... (bootloader) zip info parsing... FAILED (remote: 24 parsing android-info fail) finished. total time: 9.713s And when I try to get to the Stock Recovery, I get the HTC One Icon with the red triangle This is what I get, when my Bootloader is relocked Code: xxx-imac:adb xxx$ ./fastboot oem rebootRUU ... (bootloader) Start Verify: 3 OKAY [ 0.010s] finished. total time: 0.010s xxx-imac:adb xxx$ ./fastboot flash zip OTA_M8_UL_K44_SENSE60_SECURITY_TMO_DE_1.70.111.1-1.57.111.2_release_383280.zip target reported max download size of 1830612992 bytes sending 'zip' (253074 KB)... OKAY [ 9.539s] writing 'zip'... (bootloader) signature checking... FAILED (remote: 12 signature verify fail) finished. total time: 19.701s xxx-imac:adb xxx$