Downgrading a G2 through Fastboot Now Phone is Completely dead. - G2 and Desire Z Q&A, Help & Troubleshooting

Downgrading a G2 through Fastboot Now Phone is Completely dead. - G2 and Desire Z Q&A, Help & Troubleshooting

I'm new to the forums but, this has been bugging for a few days. I recently did a fastboot on my G2 to downgrade it from 2.3.4 to stock froyo with temp root, which was successful but during the fastboot installation, it failed and now my phone is rendered useless. Here's what i copied from the command log:
C:\android-sdk\platform-tools> adb push misc_version /data/local/tmp/misc_versio
n
adb server is out of date. killing...
* daemon started successfully *
1218 KB/s (15837 bytes in 0.012s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1777 KB/s (712688 bytes in 0.391s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
./flashgc
Backing up sd-card MBR to file "./sdcardMbr-backup.img".
Making sd-card golden.
Writing gold-card to sd-card (/dev/block/mmcblk1) ...
SUCCESS: SD-card is golden.
# sync
sync
# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.003 secs (3333 bytes/sec)
# > adb reboot bootloader
> adb reboot bootloader
C:\android-sdk\platform-tools> fastboot devices
HT09MR210427 fastboot
C:\android-sdk\platform-tools> fastboot oem rebootRUU
... INFOerase sector 196609 ~ 197120 (512)
OKAY
C:\android-sdk\platform-tools> fastboot flash zip StockRom.zip
error: cannot load 'StockRom.zip'
C:\android-sdk\platform-tools> fastboot flash zip StockRom.zip
sending 'zip' (126272 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
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,19
INFO[RUU]WP,radio,27
FAILED (status read failed (Too many links))
C:\android-sdk\platform-tools> fastboot reboot
< waiting for device >
After that my phone is unable to turn on, charge, anything. I hope there is a solution because I really love this phone to death.

Oh no... failed radio partition flash usually means death of the phone I really hope I'm wrong and that there is someone who can help!

Did you make sure to completely update Android SDK before proceeding (mainly in reference to "adb server is out of date. killing..." unless of course that's referring to the phone).
Also if you see one error, that's usually cue not to continue and to seek assistance.
When you saw "FAILED (status read failed (Too many links))" you should not have rebooted, you would have still had a chance to flash something else.

Well when it said Failed too many links, the phone then shut off itself and that was when I could never turn it back on. I also did all the updates that was required sdk and google usb drivers. The temp root however was successful and I still have the gold card it made for me even though iI just wanted to downgrade =.

TMOICS said:
I'm new to the forums but, this has been bugging for a few days. I recently did a fastboot on my G2 to downgrade it from 2.3.4 to stock froyo with temp root, which was successful but during the fastboot installation, it failed and now my phone is rendered useless. Here's what i copied from the command log:
C:\android-sdk\platform-tools> adb push misc_version /data/local/tmp/misc_versio
n
adb server is out of date. killing...
* daemon started successfully *
1218 KB/s (15837 bytes in 0.012s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
1777 KB/s (712688 bytes in 0.391s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
# ./flashgc
./flashgc
Backing up sd-card MBR to file "./sdcardMbr-backup.img".
Making sd-card golden.
Writing gold-card to sd-card (/dev/block/mmcblk1) ...
SUCCESS: SD-card is golden.
# sync
sync
# dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.003 secs (3333 bytes/sec)
# > adb reboot bootloader
> adb reboot bootloader
C:\android-sdk\platform-tools> fastboot devices
HT09MR210427 fastboot
C:\android-sdk\platform-tools> fastboot oem rebootRUU
... INFOerase sector 196609 ~ 197120 (512)
OKAY
C:\android-sdk\platform-tools> fastboot flash zip StockRom.zip
error: cannot load 'StockRom.zip'
C:\android-sdk\platform-tools> fastboot flash zip StockRom.zip
sending 'zip' (126272 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
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,19
INFO[RUU]WP,radio,27
FAILED (status read failed (Too many links))
C:\android-sdk\platform-tools> fastboot reboot
< waiting for device >
After that my phone is unable to turn on, charge, anything. I hope there is a solution because I really love this phone to death.
Click to expand...
Click to collapse
could you still boot into Bootloader?

The Android Manual said:
could you still boot into Bootloader?
Click to expand...
Click to collapse
No I cant turn the phone on, it's just off, not even charging either.

TMOICS said:
No I cant turn the phone on, it's just off, not even charging either.
Click to expand...
Click to collapse
Bricked then, only possible way out of that would likely be finding someone who can do a jtag on it (assuming that's even an option with a DZ/G2).

Related

Stuck getting past step2 on r5 rooting

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

need to root. quick assitance needed

.so yesterday i got my replacement inc 2 in the mail. i was on the inc for awhile and rooting it was simple..
i've seen a few different guides on the forum, most of which seem to be dated earlier on with methods that would have been substantial for the time being.. from what iv read there is alot of downgrading.. its 'do this, but if you are this radio, do this".. and more back tracking.. i dont mind doing it, but its just tuff at time to remember it all..
so im making my game plan.. i'd like too root tonight so ima post this and do some more reading. i've done the tacoroot and flashed the RUU, but the radio was a problem, bootloop. factory reset.. blah blah blah..im back to confused
i'll throw out what im on, and see if someone can just throw out the basic steps i need to do, i can get the nitty gritty details from searches..
s-on
hboot 0.98
radio .0312
andriod: 2.3.4
software: 6.01.605.05 710RD
much thanks appreciated..

failed.. log posted
20twins10 said:
.so yesterday i got my replacement inc 2 in the mail. i was on the inc for awhile and rooting it was simple..
i've seen a few different guides on the forum, most of which seem to be dated earlier on with methods that would have been substantial for the time being.. from what iv read there is alot of downgrading.. its 'do this, but if you are this radio, do this".. and more back tracking.. i dont mind doing it, but its just tuff at time to remember it all..
so im making my game plan.. i'd like too root tonight so ima post this and do some more reading. i've done the tacoroot and flashed the RUU, but the radio was a problem, bootloop. factory reset.. blah blah blah..im back to confused
i'll throw out what im on, and see if someone can just throw out the basic steps i need to do, i can get the nitty gritty details from searches..
s-on
hboot 0.98
radio .0312
andriod: 2.3.4
software: 6.01.605.05 710RD
much thanks appreciated..
Click to expand...
Click to collapse
so my attempt for the night.....
C:\>cd sdk
C:\sdk>cd tools
C:\sdk\tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT14NMA03268 device
C:\sdk\tools>adb push tacoroot.bin /data/local
129 KB/s (0 bytes in 14475.000s)
C:\sdk\tools>adb shell chmod 755 /data/local/tacoroot.bin
C:\sdk\tools>adb shell /data/local/tacoroot.bin
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discover
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked an
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at lea
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
C:\sdk\tools>adb shell /data/local/tacoroot.bin --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discover
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked an
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at lea
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the sam
e, and reboot the system.
C:\sdk\tools>adb shell /data/local/tacoroot.bin --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discover
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked an
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at lea
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\sdk\tools>adb shell
# exit
exit
C:\sdk\tools>adb push misctool /data/local/tmp/misctool
1324 KB/s (0 bytes in 656708.000s)
C:\sdk\tools>adb shell chmod 777 /data/local/tmp/misctool
C:\sdk\tools>adb shell sh -c '/data/local/tmp/misctool -s 2.18.605.3'
=== misctool v1.0
=== Read/Write HTC Main Version
=== (c)2012 Getitnowmarketing Inc
Usage:
misctool <option> <value to write>
<option>
r: read main version from misc partition. No <value to write> needed
w: write new value to main version in misc partition & read back new value
<value to write>
must have a length of 10 in format of 1.00.000.0
C:\sdk\tools>adb shell /data/local/tacoroot.bin --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discover
both Justin Case and Dan Rosenberg (Rosenberg fist). I believe unrevoked an
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at lea
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Root removed, rebooting
C:\sdk\tools>adb reboot bootloader
error: device not found
C:\sdk\tools>adb reboot bootloader
C:\sdk\tools>fastboot oem rebootRUU
... OKAY [ 0.156s]
finished. total time: 0.156s
C:\sdk\tools>fastboot erase cache
erasing 'cache'... OKAY [ 0.234s]
finished. total time: 0.234s
C:\sdk\tools>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.6
Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 49.797s]
writing 'zip'... INFOadopting the signature contained in t
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 95.328s
C:\sdk\tools>fastboot reboot
rebooting...
finished. total time: 0.156s
C:\sdk\tools>adb devices
List of devices attached
HT14NMA03268 device
C:\sdk>cd ..
C:\>cd vwhk-12102011-c
C:\vwhk-12102011-c>hack-vivow.cmd
C:\vwhk-12102011-c>if /I NOT EXIST C:\WINDOWS\adb.exe copy tools\win\adb.exe
WINDOWS
C:\vwhk-12102011-c>if /I NOT EXIST C:\WINDOWS\AdbWinApi.dll copy tools\win\A
nApi.dll C:\WINDOWS
C:\vwhk-12102011-c>if /I NOT EXIST C:\WINDOWS\AdbWinUsbApi.dll copy tools\wi
bWinUsbApi.dll C:\WINDOWS
C:\vwhk-12102011-c>if /I NOT EXIST C:\WINDOWS\fastboot.exe copy tools\win\fa
ot.exe C:\WINDOWS
C:\vwhk-12102011-c>if /I NOT EXIST C:\WINDOWS\sleep.exe copy tools\win\sleep
C:\WINDOWS
C:\vwhk-12102011-c>adb shell rm -r /data/local/tmp/*
C:\vwhk-12102011-c>adb push zergRush /data/local/tmp/zergRush
662 KB/s (0 bytes in 21215.000s)
C:\vwhk-12102011-c>adb push misc_version /data/local/tmp/misc_version
494 KB/s (0 bytes in 15837.000s)
C:\vwhk-12102011-c>adb shell chmod 777 /data/local/tmp/zergRush
C:\vwhk-12102011-c>adb shell chmod 777 /data/local/tmp/misc_version
C:\vwhk-12102011-c>adb shell /data/local/tmp/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\vwhk-12102011-c>echo Sleeping 10 secs while adb restarts on the device...
Sleeping 10 secs while adb restarts on the device....
C:\vwhk-12102011-c>sleep 10
C:\vwhk-12102011-c>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_ver
-s 2.18.605.3'
/data/local/tmp/sh: permission denied
C:\vwhk-12102011-c>adb reboot bootloader
C:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.141s]
finished. total time: 0.141s
C:\vwhk-12102011-c>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.188s]
finished. total time: 0.188s
C:\vwhk-12102011-c>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2
605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 50.016s]
writing 'zip'... INFOadopting the signature contained in th
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 94.375s
C:\vwhk-12102011-c>fastboot reboot
rebooting...
finished. total time: 0.156s
C:\vwhk-12102011-c>cd ..
C:\>cd revolutionary
C:\revolutionary>revolutionary
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: ADR6350 (vivow-0.98.0000, Android: 2.3.4, ROM version: 6.
05.05)
Your device: vivow, with HBOOT 0.98.0000 is not supported at this time.
Press (almost) any key to exit.
k
C:\revolutionary>

http://forum.xda-developers.com/showthread.php?t=1726134
Used this guide 5 or 6 times. It Works.
What I do is put my androidSDK folder at C:\SDK.
C:\>cd sdk - This is wrong!
C:\sdk>cd tools - So is this!
It goes cd c:\sdk\platform-tools and cd c:\sdk\tools
These are the only 2 folders required.
Read the guide and read again
Make sure you have your sdk with all the files in the right folders.
The process is pretty easy its just the attention to detail thats important.
Also make sure fastboot is disabled, and usb debugging is enabled

cabbie12 said:
http://forum.xda-developers.com/showthread.php?t=1726134
Used this guide 5 or 6 times. It Works.
What I do is put my androidSDK folder at C:\SDK.
C:\>cd sdk - This is wrong!
C:\sdk>cd tools - So is this!
It goes cd c:\sdk\platform-tools and cd c:\sdk\tools
These are the only 2 folders required.
Read the guide and read again
Make sure you have your sdk with all the files in the right folders.
The process is pretty easy its just the attention to detail thats important.
Also make sure fastboot is disabled, and usb debugging is enabled
Click to expand...
Click to collapse
as most of the threads say, the paths are all different based on user.. i have all my exe files in c:/sdk/tools.. so thats why they all ran from there.. i spent some time on it this morning and all i did was chance the tacoroot.bin file to a different tacoroot.sh file and everything went fine.. i'm now s-off, android 2.3.3, but i need to get my radio flashed, and clockwork.. thanks for the assistance..

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

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

[Q] any ideas

FAILED (remote: signature verify fail)
finished. total time: 0.997s
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.462s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.012s
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.446s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.997s
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.448s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.998s
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.448s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.998s
C:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.448s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.998s
C:\miniadb_inc>adb devices
List of devices attached
C:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.096s
C:\miniadb_inc>adb devices
List of devices attached
HT0C6HJ04192 device
C:\miniadb_inc>adb push flash_image /data/local/
1350 KB/s (76044 bytes in 0.055s)
C:\miniadb_inc>adb push mtd0.img /sdcard/
failed to copy 'mtd0.img' to '/sdcard//mtd0.img': Read-only file system
C:\miniadb_inc>adb push flash_image /data/local/
1811 KB/s (76044 bytes in 0.041s)
C:\miniadb_inc>adb push mtd0.img /sdcard/
failed to copy 'mtd0.img' to '/sdcard//mtd0.img': Read-only file system
C:\miniadb_inc>adb shell
[email protected]:/ # cd /data/local
cd /data/local
[email protected]:/data/local # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
[email protected]:/data/local # cd /data/local
cd /data/local
[email protected]:/data/local # ./flash_image misc /sdcard/mtd0img
./flash_image misc /sdcard/mtd0img
Segmentation fault
139|[email protected]:/data/local # exit
exit
C:\miniadb_inc>adb reboot bootloader
C:\miniadb_inc>fastboot getvar mainver
mainver: 4.08.605.2
finished. total time: 0.001s
C:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.096s
C:\miniadb_inc>adb reboot bootloader
C:\miniadb_inc>fastboot devices
HT0C6HJ04192 fastboot
C:\miniadb_inc>cd \android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\android>fastboot devices
HT0C6HJ04192 fastboot
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\android>cd \miniadb_inc
C:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.092s
C:\miniadb_inc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT0C6HJ04192 device
C:\miniadb_inc>adb reboot bootloader
C:\miniadb_inc>fastboot devices
HT0C6HJ04192 fastboot
C:\miniadb_inc>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\miniadb_inc>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
C:\miniadb_inc>cd /android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.009s
C:\android>cd \miniadb_inc
C:\miniadb_inc>adb devices
List of devices attached
C:\miniadb_inc>fastboot devices
HT0C6HJ04192 fastboot
C:\miniadb_inc>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
C:\miniadb_inc>fastboot erase cache
erasing 'cache'... OKAY [ 1.099s]
finished. total time: 1.099s
C:\miniadb_inc>fastboot format
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\miniadb_inc>fastboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\miniadb_inc>adb devices
List of devices attached
C:\miniadb_inc>fastboot devices
HT0C6HJ04192 fastboot
C:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.092s
C:\miniadb_inc>adb devices
List of devices attached
HT0C6HJ04192 device
C:\miniadb_inc>adb shell
[email protected]:/ # flashall
flashall
/system/bin/sh: flashall: not found
127|[email protected]:/ # flash system
flash system
/system/bin/sh: flash: not found
127|[email protected]:/ # flash PM31IMG
flash PM31IMG
/system/bin/sh: flash: not found
127|[email protected]:/ # flash partition
flash partition
/system/bin/sh: flash: not found
127|[email protected]:/ # flash/system
flash/system
/system/bin/sh: flash/system: not found
127|[email protected]:/ # -2
-2
/system/bin/sh: -2: not found
127|[email protected]:/ # -s
-s
/system/bin/sh: -s: not found
127|[email protected]:/ # exit
exit
C:\miniadb_inc>-s
'-s' is not recognized as an internal or external command,
operable program or batch file.
C:\miniadb_inc>get var
'get' is not recognized as an internal or external command,
operable program or batch file.
C:\miniadb_inc>fastboot devices
C:\miniadb_inc>adb devices
List of devices attached
HT0C6HJ04192 device
C:\miniadb_inc>flashall
'flashall' is not recognized as an internal or external command,
operable program or batch file.
C:\miniadb_inc>adb shell
[email protected]:/ # flash update.zip
flash update.zip
/system/bin/sh: flash: not found
127|[email protected]:/ # flash sdcard
flash sdcard
/system/bin/sh: flash: not found
127|[email protected]:/ # /sd card
/sd card
/system/bin/sh: /sd: not found
127|[email protected]:/ # exit
exit
C:\miniadb_inc>fastboot devices
C:\miniadb_inc>adb devices
List of devices attached
HT0C6HJ04192 device
C:\miniadb_inc>

Develop Bugs

welcome

Downgrading a G2 through Fastboot Now Phone is Completely dead. - G2 and Desire Z Q&A, Help & Troubleshooting

Oh no... failed radio partition flash usually means death of the phone I really hope I'm wrong and that there is someone who can help!

The Android Manual said: could you still boot into Bootloader? Click to expand... Click to collapse No I cant turn the phone on, it's just off, not even charging either.

TMOICS said: No I cant turn the phone on, it's just off, not even charging either. Click to expand... Click to collapse Bricked then, only possible way out of that would likely be finding someone who can do a jtag on it (assuming that's even an option with a DZ/G2).

Related

Stuck getting past step2 on r5 rooting

need to root. quick assitance needed

S710d HTCDev Unlock 2.3.4 hboot 1.04 help, please

S-OFF Gone Wrong - Bootlooping

[Q] any ideas

Categories

Resources