Stuck getting past step2 on r5 rooting - Desire General

hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>

InspectorFrost said:
hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>
Click to expand...
Click to collapse
Try set your device to HTC Sync, and do the ./... again

disconnect then reconnect your device and try again

Error 42, isn't that related to a goldcard?
Do you have a branded Desire?

I had the same problem. Started out rooting on my Win7 x64. Got past step 1 - failed with device not found on step 2.
Finally I started all over using a Tiny Core Linux guide (sorry - for some reason I'm not allowed to post outside links - yet?). Google "easy desire Linux rooting guide".
I know it's Linux but it's really not that hard. Only thing I missed in the guide was the fact that when selecting something from the recovery menu you have to actually press the optical trackball.
Good luck

Rudolfje said:
Error 42, isn't that related to a goldcard?
Do you have a branded Desire?
Click to expand...
Click to collapse
I would also recommend the Goldcard method here. Although my Desire is supposedly unbranded, I got the same error which was solved by using a Goldcard.

I previously hit 42 error as well.
Its related to the Goldcard in Step1... try to use another SD card. I used Sandisk 1GB and it works.

Device seems Bricked? PLS HELP URGENTLY!
InspectorFrost said:
hi
Im not getting past step2 on this guide
Im getting device not found error....see below (NB. i have htc sync installed and working correctly
(might also be worth noting that i noticed this line come up whist doing step 1 "FAILED (remote: 42 custom id check fail)"
(is this the cause of the problem below?)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\Chris\Desktop\HTC STUFF\Unzipped R5\r5-desire-root>
Click to expand...
Click to collapse
I attach the log here of what happen (not a 42 error but a 51 error... during step 1)
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] flushing...
INFO[RUU]WP,hboot,0
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,40
INFO[RUU]UZ,boot,85
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,45
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,16
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,65
INFO[RUU]UZ,radio,73
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,51
INFO[RUU]WP,radio,59
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,24
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,65
INFO[RUU]UZ,recovery,93
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,22
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,67
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[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,3
INFO[RUU]UZ,system,7
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,20
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,29
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,41
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,50
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,66
INFO[RUU]WP,system,0
INFO[RUU]WP,system,66
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,72
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,80
INFO[RUU]UZ,system,83
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,66
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
FAILED (remote: 51 partition update fail)
sending 'zip' (137446 KB)... OKAY
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...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,40
INFO[RUU]UZ,boot,85
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,45
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,16
INFO[RUU]UZ,radio,24
INFO[RUU]UZ,radio,33
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,49
INFO[RUU]UZ,radio,57
INFO[RUU]UZ,radio,65
INFO[RUU]UZ,radio,73
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,24
INFO[RUU]UZ,recovery,44
INFO[RUU]UZ,recovery,65
INFO[RUU]UZ,recovery,93
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,22
INFO[RUU]WP,recovery,44
INFO[RUU]WP,recovery,67
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[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,3
INFO[RUU]UZ,system,7
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,20
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,29
INFO[RUU]UZ,system,33
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,41
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,50
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,66
INFO[RUU]WP,system,0
INFO[RUU]WP,system,66
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,72
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,80
INFO[RUU]UZ,system,83
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,66
INFOstart image[userdata] unzipping & flushing...
INFO[RUU]UZ,userdata,0
INFO[RUU]UZ,userdata,100
INFO[RUU]WP,userdata,0
INFO[RUU]WP,userdata,100
FAILED (remote: 51 partition update fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
C:\Users\admin\Desktop\HTC Root\r5-desire-root>step2-windows.bat
Desire Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
I should note it is an unbranded HTC Desire. After Step 1, phone went off with 2 vibrations. Never went back into bootloader mode (as described in the step 1 bat file). Also the USB connection to the computer (win 7) died. Should note I have already installed HTC Sync v.33. Can not get the phone to enter boot loader mode. Only activity is when battery & usb cable is reinserted, I can see the charging led/green led go on. Pressing the on/off, makes charging/green led go off.
Hope you can help....

FAILED (remote: 51 partition update fail)
Click to expand...
Click to collapse
There's your error..

Thanks for all the responses .
I started over using a slightly different guide ( the one on the Nimbu site....still one of Pauls i think)
anyway, still had trouble getting the step2 going....
All fixed now, it seems my command prompt went a little weird on my laptop.
everytime i clicked the .bat file (when phone was in recovery, red triangle) the command prompt window would open for about half a second then dissappear and nothing would happen on the Phone.
Fix was just to reboot the laptop, worked like a charm afterward
then flashed Pays Bravesoul 2......now thats a speedy little rom !!!
using Launcher pro too
I love being able to mix things up
thanks again

Related

[Q] Help needed! Telstra Desire w/ 4 excl marks, radio_v2 partition update fail

Hoping you guys can help out. I have a HTC Desire from Telstra (A8183). which was rooted with Unrevoked and running Villain_AU ROM. Randomly rebooting and getting stuck on splash screen, so I was intending to return it to HTC under warranty.
Tried to run stock Telstra Froyo RUU to unroot: _HTC Desire_RUU_Bravo_Froyo_Telstra_WWE_2.26.841.2_Radio_32.48.00.32U_5.11.05.14_release_150162_signed.exe...
"Error [152]: Image update error". I unplug the cable as instructed and get a white screen with:
BRAVO PVT SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.17.05.08
Aug 10 2010,17:52:18
RUU
Parsing...[downloaded ZIP]
[1] RADIO_V2 - Fail-PU
[2] RADIO_CUST - OK
[3] BOOT - OK
[4] RECOVERY - OK
[5] SYSTEM - OK
[6] USERDATA - OK
[7] SPLASH1 - OK
[8] SPLASH2 - OK
Partition update fail!
Update Fail!
Remove/replace the battery and I now have a black screen with HTC logo and 4 exclamation marks in triangles. Re-running the Telstra RUU brings the same result.
Tried using Android Flasher 1.8.0 with radio.img from Telstra Froyo RUU
fastboot.exe flash radio radio.img
sending 'radio' (26112 KB)...
OKAY [ 3.559s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
FAILED (remote: 12 signature verify fail)
finished. total time: 7.186s
fastboot.exe reboot
rebooting...
finished. total time: 0.090s
Cannot boot into recovery or see device with adb. Can see device with fastboot, but get that "signature verify fail" error when I try flashing.
Here's the log from attempting to flash with fastboot and the rom.zip from the Telstra RUU:
sending 'zip' (169497 KB)...
OKAY [ 23.046s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 50.239s
Any assistance you can provide would be very much appreciated
Hi guys,
Any suggestions? I've checked a bunch of similar threads and nothing in there seems to work or get me any closer to getting the wife's Desire working again. Please help!

S-OFF Gone Wrong - Bootlooping

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

Complications during CM install. Can't find HTC__Y13 firmware; CWM recovery bootloops

I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.
Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom
Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(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.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(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 [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?
Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium
All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.

htc stck ruu

Hello i hope someone can help me out i am trying to reflash the stock ICS rom for my htc one v but i keep getting an error halfway through the flashing saying an unknown error has occured and something about flashing the correct rom. To my knowledge i am flashing the correct stock rom which i have downloaded from http://www.androidfiles.org/ruu/?developer=Primo. Their are 2 roms for H3g ics and i have tried both with the same error. Iff someone could point me in the right direction i would much appeciate it thankyou in advance. Atm i am stuck in fastboot everytime i reboot the phone as i have relocked the bootloader also as suggested in the instructions on how to reflash.
I don't know if its why or not. But you also have to flash the stock kernel and recovery before re locking. You can get these files by first running the RUU. Without doing anything go into your temp folder and you'll see a folder with all the flash images.
The RUU also has to be for your HBOOT/RADIO as far as I know.
sam0056 said:
Hello i hope someone can help me out i am trying to reflash the stock ICS rom for my htc one v but i keep getting an error halfway through the flashing saying an unknown error has occured and something about flashing the correct rom. To my knowledge i am flashing the correct stock rom which i have downloaded from http://www.androidfiles.org/ruu/?developer=Primo. Their are 2 roms for H3g ics and i have tried both with the same error. Iff someone could point me in the right direction i would much appeciate it thankyou in advance. Atm i am stuck in fastboot everytime i reboot the phone as i have relocked the bootloader also as suggested in the instructions on how to reflash.
Click to expand...
Click to collapse
ain't this funny..
i am trying the exact same thing.. and i am getting stuck 2..
Code:
C:\htc\Fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\htc\Fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY
C:\htc\Fastboot>fastboot oem rebootRUU
... OKAY
C:\htc\Fastboot>fastboot flash zip "rom.zip"
sending 'zip' (321386 KB)... OKAY
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...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,22
INFO[RUU]WP,radio,30
INFO[RUU]WP,radio,38
INFO[RUU]WP,radio,48
INFO[RUU]WP,radio,53
INFO[RUU]WP,radio,61
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,77
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,91
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
C:\htc\Fastboot>
:laugh:
---------- Post added at 10:22 AM ---------- Previous post was at 09:52 AM ----------
oNNoZeLe said:
ain't this funny..
i am trying the exact same thing.. and i am getting stuck 2..
Code:
C:\htc\Fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\htc\Fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY
C:\htc\Fastboot>fastboot oem rebootRUU
... OKAY
C:\htc\Fastboot>fastboot flash zip "rom.zip"
sending 'zip' (321386 KB)... OKAY
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...
INFOchecking hboot version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[radio] unzipping for pre-update...
INFOstart image[radio] flushing...
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,22
INFO[RUU]WP,radio,30
INFO[RUU]WP,radio,38
INFO[RUU]WP,radio,48
INFO[RUU]WP,radio,53
INFO[RUU]WP,radio,61
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,77
INFO[RUU]WP,radio,85
INFO[RUU]WP,radio,91
INFO[RUU]WP,radio,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
C:\htc\Fastboot>
:laugh:
Click to expand...
Click to collapse
i locked the device b4 upping the signed boot.img and signed recovery.img..
i am gonna try a stock rooted lite rom
oNNoZeLe said:
ain't this funny..
i locked the device b4 upping the signed boot.img and signed recovery.img..
i am gonna try a stock rooted lite rom
Click to expand...
Click to collapse
If you locked it you cant flash a kernel. It has to be unlocked to do that.
bandit97 said:
If you locked it you cant flash a kernel. It has to be unlocked to do that.
Click to expand...
Click to collapse
true..
i found this thread an after unlocking and a redo i got my V back to stock..
slimbean
oNNoZeLe said:
true..
i found this thread an after unlocking and a redo i got my V back to stock..
Click to expand...
Click to collapse
I gave up in the end and i installed the HOV slimbean rom and have found it to be brilliant i think ill stick with it.
sam0056 said:
I gave up in the end and i installed the HOV slimbean rom and have found it to be brilliant i think ill stick with it.
Click to expand...
Click to collapse
i installed
http://forum.xda-developers.com/showthread.php?t=1647052
this one..
and seems to be working fine so far..
what is the HOV?
H=HTC
O=one
V=v
htc ics lite
mrcorey said:
H=HTC
O=one
V=v
Click to expand...
Click to collapse
their is also a lite verision of ICS around somewhere which i also tried for a few weeks and it was also very good but the only problem was it wasnt a rooted rom so thats why i went to slimbean. That other rom is here http://forum.xda-developers.com/showthread.php?t=2121780

Very long boot time htc one m8

Hello to all members of this wonderful forum.
I'm Italian, so my English isn't perfect.
I have a htc one m8, I unlocked it, I installed the TWRP recovery, I installed Android HD Revolution 10.2 and the kernel Elementalx.
I noticed, however, that in addition to the red writing at bootup, the phone takes a long time to turn on, even 3/4 or 5 minutes.
Why?
I can't understand where is the problem, I have already tried to wipe cache and dalvik.
I don't have enabled ART.
Can you help me please?
I would hazard a guess you have older Firmware installed on your phone and that version of Android HD requires the newer firmware of whatever carrier phone you have . Most complaining of long boot times and wifi issues is generally a result of a mismatch of firmware version . Check your firmware version in "About Phone" section of your device then check the thread of the before mentioned rom you are running and see if they are similar firmware versions .
SouthernEvo said:
I would hazard a guess you have older Firmware installed on your phone and that version of Android HD requires the newer firmware of whatever carrier phone you have . Most complaining of long boot times and wifi issues is generally a result of a mismatch of firmware version . Check your firmware version in "About Phone" section of your device then check the thread of the before mentioned rom you are running and see if they are similar firmware versions .
Click to expand...
Click to collapse
I heard of custom rom, recovery, kernel, unlock, s-off. but never by firmware.
I never had these problems with one m7, galaxy s2/s3 and s4. can I have a guide for the firmware?
however, if I update the firmware, can I lose the data?
I can't see the current firmware version.
to do the firmware update should be s-off?
because a month ago when I tried I couldn't do the s-off. maybe because I had the custom rom. ??
denisdm91 said:
I heard of custom rom, recovery, kernel, unlock, s-off. but never by firmware.
I never had these problems with one m7, galaxy s2/s3 and s4. can I have a guide for the firmware?
however, if I update the firmware, can I lose the data?
I can't see the current firmware version.
to do the firmware update should be s-off?
because a month ago when I tried I couldn't do the s-off. maybe because I had the custom rom. ??
Click to expand...
Click to collapse
To get your firmware version you also can use the getvar main command in fastboot mode. For more detailed guides just search this forum.
By updating firmware you won't loose any date, but you have to be s-off to do it, yes. Firewater s-off does the job for some of the users, but not all. SunShine does it in most off the cases were firewater doesn't. But it won't work on a custom ROM. You got to have a stock RO.M to perform the S-Off procedure.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
To get your firmware version you also can use the getvar main command in fastboot mode. For more detailed guides just search this forum.
By updating firmware you won't loose any date, but you have to be s-off to do it, yes. Firewater s-off does the job for so be users, but not all. SunShine does it in most off the cases were firewater doesn't. But it won't work on a custom ROM. You got to have a stock RO.M to perform the S-Off procedure.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
ùI'm trying to do s-off with sunshine.
but it ask me the stock kernel. where is it?
denisdm91 said:
ùI'm trying to do s-off with sunshine.
but it ask me the stock kernel. where is it?
Click to expand...
Click to collapse
As I wrote you've got to be on a stock ROM, not on a custom ROM.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
As I wrote you've got to be on a stock ROM, not on a custom ROM.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
can I use this?
http://forum.xda-developers.com/showthread.php?t=2694994
odexed
denisdm91 said:
can I use this?
http://forum.xda-developers.com/showthread.php?t=2694994
odexed
Click to expand...
Click to collapse
and, how can I return one m8 to 100 % stock?
my CID is: T-MOB101
denisdm91 said:
and, how can I return one m8 to 100 % stock?
Click to expand...
Click to collapse
On the arhd downloads site they have a stock odexed ROM that I used for sunshine. Worked perfectly.
Heisenberg420 said:
On the arhd downloads site they have a stock odexed ROM that I used for sunshine. Worked perfectly.
Click to expand...
Click to collapse
where?
can you send me the link please?
I just have to flash the rom, right?
denisdm91 said:
where?
can you send me the link please?
I just have to flash the rom, right?
Click to expand...
Click to collapse
I read that MaximusHD 5 is compatible with sunshine.
I feel that at this point
denisdm91 said:
I read that MaximusHD 5 is compatible with sunshine.
I feel that at this point
Click to expand...
Click to collapse
Read that too, but never tested it.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
Read that too, but never tested it.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
ok, with the maximushd 5.0 rom sunshine worked.
my device is now s-off.
where can I check if it worked?
now I have to update the firmware to version 2.22.401.5 to install the viperone 2.1.0.
can you send me a guide?
denisdm91 said:
ok, with the maximushd 5.0 rom sunshine worked.
my device is now s-off.
where can I check if it worked?
now I have to update the firmware to version 2.22.401.5 to install the viperone 2.1.0.
can you send me a guide?
Click to expand...
Click to collapse
In bootloader you can check if you are S-Off. If SunShine gave a positive you should be by now.
What you have to do is:
1) download firmware 2.22.401.4, ViperOneM8 Full ROM and TWRP.
2) Change CID I if needed to correspond with above named FW.
3) flash firmware
4) flash TWRP
5) got to recovery, enable adb sideload and sideload Viper ROM from adb folder and install.
6) reboot and be happy to use ViperOne ROM
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
In bootloader you can check if you are S-Off. If SunShine gave a positive you should be by now.
What you have to do is:
1) download firmware 2.22.401.4, ViperOneM8 Full ROM and TWRP.
2) Change CID I if needed to correspond with above named FW.
3) flash firmware
4) flash TWRP
5) got to recovery, enable adb sideload and sideload Viper ROM from adb folder and install.
6) reboot and be happy to use ViperOne ROM
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
asks me to change the cid.
I tried to give the command fastboot oem writecid VZW_001 but doesn't work
denisdm91 said:
asks me to change the cid.
I tried to give the command fastboot oem writecid VZW_001 but doesn't work
Click to expand...
Click to collapse
fastboot oem writecid 11111111
and then:
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping for pre-update...
INFOstart image[sbl1-1] flushing...
INFOsignature checking...
INFO[RUU]WP,sbl1-1,0
INFO[RUU]WP,sbl1-1,100
INFO...... Successful
INFOstart image[sbl1-2] unzipping for pre-update...
INFOstart image[sbl1-2] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[sbl1-3] unzipping for pre-update...
INFOstart image[sbl1-3] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[rpm] unzipping for pre-update...
INFOstart image[rpm] flushing...
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[tz] unzipping for pre-update...
INFOstart image[tz] flushing...
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[sdi] unzipping for pre-update...
INFOstart image[sdi] flushing...
INFO[RUU]WP,sdi,0
INFO[RUU]WP,sdi,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
I repeated the command and it gave me this:
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping for pre-update...
INFOstart image[sbl1-1] flushing...
INFOsignature checking...
INFO[RUU]WP,sbl1-1,0
INFO[RUU]WP,sbl1-1,100
INFO...... Successful
INFOstart image[sbl1-2] unzipping for pre-update...
INFOstart image[sbl1-2] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[sbl1-3] unzipping for pre-update...
INFOstart image[sbl1-3] flushing...
INFOsignature checking...
INFOverified fail
INFO...... Bypassed
INFOstart image[rpm] unzipping for pre-update...
INFOstart image[rpm] flushing...
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[tz] unzipping for pre-update...
INFOstart image[tz] flushing...
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[sdi] unzipping for pre-update...
INFOstart image[sdi] flushing...
INFO[RUU]WP,sdi,0
INFO[RUU]WP,sdi,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediat
C:\ Fastboot \adb-windows>fastboot flash zip firmware1.zip
sending 'zip' (99380 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOtotal_image_number=12
INFOstart image[adsp] unzipping & flushing...
INFO[RUU]UZ,adsp,0
INFO[RUU]UZ,adsp,11
INFO[RUU]UZ,adsp,21
INFO[RUU]UZ,adsp,33
INFO[RUU]UZ,adsp,44
INFO[RUU]UZ,adsp,54
INFO[RUU]UZ,adsp,66
INFO[RUU]UZ,adsp,76
INFO[RUU]UZ,adsp,87
INFO[RUU]UZ,adsp,99
INFO[RUU]UZ,adsp,100
INFO[RUU]WP,adsp,0
INFO[RUU]WP,adsp,100
INFO...... Successful
INFOcurrent_image_number=0
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,14
INFO[RUU]UZ,boot,24
INFO[RUU]UZ,boot,36
INFO[RUU]UZ,boot,47
INFO[RUU]UZ,boot,63
INFO[RUU]UZ,boot,82
INFO[RUU]UZ,boot,96
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFO...... Successful
INFOcurrent_image_number=1
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,9
INFO[RUU]UZ,dzdata,16
INFO[RUU]UZ,dzdata,23
INFO[RUU]UZ,dzdata,31
INFO[RUU]UZ,dzdata,38
INFO[RUU]UZ,dzdata,46
INFO[RUU]UZ,dzdata,55
INFO[RUU]UZ,dzdata,62
INFO[RUU]UZ,dzdata,67
INFO[RUU]UZ,dzdata,74
INFO[RUU]UZ,dzdata,81
INFO[RUU]UZ,dzdata,86
INFO[RUU]UZ,dzdata,93
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,9
INFO[RUU]WP,dzdata,28
INFO[RUU]WP,dzdata,39
INFO[RUU]WP,dzdata,47
INFO[RUU]WP,dzdata,54
INFO[RUU]WP,dzdata,59
INFO[RUU]WP,dzdata,67
INFO[RUU]WP,dzdata,74
INFO[RUU]WP,dzdata,83
INFO[RUU]WP,dzdata,97
INFO[RUU]WP,dzdata,100
INFO...... Successful
INFOcurrent_image_number=2
INFOstart image[pg2fs_spcustom] unzipping & flushing...
INFO[RUU]UZ,pg2fs_spcustom,0
INFO[RUU]UZ,pg2fs_spcustom,23
INFO[RUU]UZ,pg2fs_spcustom,45
INFO[RUU]UZ,pg2fs_spcustom,67
INFO[RUU]UZ,pg2fs_spcustom,88
INFO[RUU]UZ,pg2fs_spcustom,100
INFO...... Successful
INFOcurrent_image_number=3
INFOstart image[ recovery ] unzipping & flushing...
INFO[RUU]UZ, recovery ,0
INFO[RUU]UZ,recovery,8
INFO[RUU]UZ,recovery,14
INFO[RUU]UZ,recovery,21
INFO[RUU]UZ,recovery,28
INFO[RUU]UZ,recovery,37
INFO[RUU]UZ,recovery,42
INFO[RUU]UZ,recovery,61
INFO[RUU]UZ,recovery,68
INFO[RUU]UZ,recovery,74
INFO[RUU]UZ,recovery,81
INFO[RUU]UZ,recovery,86
INFO[RUU]UZ,recovery,91
INFO[RUU]UZ,recovery,99
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFO...... Successful
INFOcurrent_image_number=4
INFOstart image[sensor_hub] unzipping & flushing...
INFO[RUU]UZ,sensor_hub,0
INFO[RUU]UZ,sensor_hub,100
INFO[RUU]WP,sensor_hub,0
INFO[RUU]WP,sensor_hub,4
INFO[RUU]WP,sensor_hub,8
INFO[RUU]WP,sensor_hub,12
INFO[RUU]WP,sensor_hub,16
INFO[RUU]WP,sensor_hub,20
INFO[RUU]WP,sensor_hub,24
INFO[RUU]WP,sensor_hub,28
INFO[RUU]WP,sensor_hub,32
INFO[RUU]WP,sensor_hub,36
INFO[RUU]WP,sensor_hub,40
INFO[RUU]WP,sensor_hub,44
INFO[RUU]WP,sensor_hub,48
INFO[RUU]WP,sensor_hub,52
INFO[RUU]WP,sensor_hub,56
INFO[RUU]WP,sensor_hub,60
INFO[RUU]WP,sensor_hub,64
INFO[RUU]WP,sensor_hub,68
INFO[RUU]WP,sensor_hub,72
INFO[RUU]WP,sensor_hub,76
INFO[RUU]WP,sensor_hub,80
INFO[RUU]WP,sensor_hub,84
INFO[RUU]WP,sensor_hub,88
INFO[RUU]WP,sensor_hub,92
INFO[RUU]WP,sensor_hub,96
INFO[RUU]WP,sensor_hub,100
INFO...... Successful
INFOcurrent_image_number=5
INFOstart image[sp1] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=6
INFOstart image[tp] unzipping & flushing...
INFO..... Bypassed
INFOcurrent_image_number=7
INFOstart image[tp] unzipping & flushing...
INFO..... Bypassed
INFOcurrent_image_number=8
INFOstart image[wcnss] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=9
INFOstart image[ radio ] unzipping & flushing...
INFOtrying to rename MBA
INFO...... Successful
INFOcurrent_image_number=10
INFOstart image[rcdata] unzipping & flushing...
INFO...... Successful
INFOcurrent_image_number=11
OKAY
now on the phone is the HTC logo and a progress bar half green and half black.
Reflash again immediately. Most times you need to flash firmware twice
stathis95194 said:
Reflash again immediately. Most times you need to flash firmware twice
Click to expand...
Click to collapse
I turned off the phone in bootloader and leave and re-gives me this:
M8_UL PVT SHIP S-OFF
CID-T-MOB101
HBOOT-3.18.0.0000
radio-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.401.5

Categories

Resources