need to root. quick assitance needed - Verizon Droid Incredible 2

.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..

Related

[Guide] How To Downgrade 6.01.605.05 and gain S-Off

How to Gain S-OFF on the HTC Droid Incredible 2​
After you have S-OFF, you can root it, or install a custom rom, like CyanogenMod 9​
Please don't forget to rate and thank the thread so I can get this stickied!
UPDATES:
July 25th
For all those people receiving ERROR 43 codes please read. Note that this is just a test so it may not work. In the attached files I have a flash-able .zip file (SetMainVersionLOW.zip) that should set your misc_version to 1.00.000 and allow and RUU to be flashed to the phone. Just boot into recovery and flash the file from the root of your sd card. I have not been able to test this as I am already s-off so anyone that tries this please provide feedback =D
July 23rd
Updated the downgrading process for better clarity and fixed a file name. Also updated the RUU download link.
June 28th
In step n. (where you flash the RUU file be aware that in the name there is a space in the word radio. Please delete this space as it is not supposed to be there. (for some reason i am unable to remove the space.)
June 20th, 2012
A few people have reported to me that they are running sense roms without the vicious bootloops! This could just be luck of the draw, however I am looking into the stability of this phenomenon. (I did experince the wrath of bootloops after downgrading myself, but fixed the issue with ease by flashing an AOSP rom)
June 27th, 2012
IF ANY DEVS NEED THE 6.01.605.05 PLEASE PM ME. I NOW HAVE THE SYSTEM FOLDER!
DISCLAIMER:
This process will void the worthless warranty on your Incredible 2. If you read all the steps first before doing this, then do it following every step very carefully, I can guarantee you that your phone will be just fine. I recommend doing this in Linux, because it works best that way, but it can be done in Windows... it's just harder and there is a greater chance you will run into problems. I also understand that this guide has been posted elsewhere by me but i feel it will be more useful under the development section. There are other guides on this but i feel they are outdated and cause quite a bit of confusion to some members, so i tried to clear a few bits and pieces as best i could :victory:
1. Setup
Download both the misc_version and tacoroot.sh files that are attached, you also need the RUU 2.3.3 File which can be found here
Windoze users:
a. Uninstall anything that is HTC related on your computer, such as HTC Sync.
b. Install the HTC Drivers at this link: http://downloads.unr...er3.0.0.007.exe
Linux Users:
a. Install the ia32-libs package. If you are on Ubuntu or Debian, type this in the terminal:
Code:
sudo apt-get install ia32-libs
c. ALL THESE STEPS ARE ASSUMING YOU ARE USING COMMAND PROMPT AS ADMINISTRATOR (open start menu and type cmd, the right click<run as administrator)
d. DISABLE FASTBOOT in Settings/Power (possibly causes bootloops with tacoroot)
e. Turn on USB Debugging in under Settings > Applications > Development > USB Debugging
f. Place the misc_version and tacoroot.sh into your /Android/android-sdk/Platform-tools folder. (platform-tools may also just be named platform, depends on which sdk version you have)
g. Place the RUU_Vivo.....zip folder in the /Android/android-sdk/tools folder. (Leave it as a .zip file, do NOT extract the contents to the tools folder)
2. Tips
Here are a couple tips you may want to try that could possibly help the process run smoother.
-Make sure you have a SD card in your SD card slot and its mounted.
-Between each script wait 5-10 seconds after the previous script has completed before moving on to the next step.
-After each phone reboot, wait for the phone to completely reboot and start up before proceeding to the next step.
-Run in 'Charge Mode Only'
-Back up your SD card and Format it.
3. Downgrading
a. In cmd type cd C:\Program Files (x86)\Android\android-sdk\platform
(your destination folder may be different, but you want to use the file path for where ever your Platform-tools or platform folder is. In this case mine is in my local directory under platform not Platform-tools)
b. adb push tacoroot.sh /data/local/
c. adb shell chmod 755 /data/local/tacoroot.sh
d. adb shell /data/local/tacoroot.sh --setup
d1. This should boot your phone into recovery, when you see the red exclamation mark, hit Volume Up and Power to get into the stock recovery, once in stock recovery, HOLD Volume Up Volume Down and Power to force reboot the phone.
e. adb shell /data/local/tacoroot.sh --root
e1. Wait for the phone to reboot back up, if everything worked up until now, adb should have root (you can try by typing 'adb shell' and seeing if you get a #, if you do this means tacoroot was successful in gaining a tmp reoot, type 'exit' to get out of shell mode)
===side note=== Your device may bootloop after this process, if it does don't be alarmed its normal.
f. adb push misc_version /data/local/tmp/misc_version
g. adb shell chmod 777 /data/local/tmp/misc_version
h. adb shell sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
i. adb shell /data/local/tacoroot.sh --undo
j. adb reboot bootloader
k. Now we want to change directories to the tools folder so type cd C:\Android\android-sdk\tools (again, this file path will differ for you depending on where your android tools folder is located)
l. fastboot oem rebootRUU
m. fastboot erase cache
n. 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
(If you are having problems with this step please refer to the UPDATES section at the beginning of the post!)
o. fastboot reboot
4. Gaining S-Off
WARNING! This will void your warranty... but, it's not yours till you void the warranty.
a. Download revolutionary from here.
b. Run revolutionary. It should do all the work for you. Just get a beta key on the website.
c. Revolutionary should ask you if you want to flash ClockworkMod when it's done. Say yes if you want it. (your going to want it!)
Troubleshooting
IF: you get an error that looks something like
Code:
FAILED (remote: 43 main version check fail)
THEN: This is a error related to the misc_version not being properly "replaced". In many cases people have forgotten to use the code "adb push misc_version /data/local/tmp/misc_version" which took care of the problem for the most part. Still troubleshooting methods to get around the error for people that cannot get it to work, check back later.
IF: you get
Code:
Unable to chmod /data/local/misc_version: No such file or directory
THEN: This again is with the misc_version not being placed properly. (Where many errors will occur). If this error happens to you try using steps f and g without the tmp. So it would look like this
f. adb push misc_version /data/local/misc_version
g. adb shell chmod 777 /data/local/misc_version
IF: You get an error stating something along the lines of 99 version check fail
THEN: You must have an unlocked bootloader and must relock it. To do this type "fastboot oem lock"
IF: you still can't get the misc_version steps to work
THEN: You can manually change the version by looking at this great post by drellisdee here
Below is what a successful downgrade should look like after finished
Code:
C:\Program Files (x86)\Android\android-sdk\tools>cd C:\Program Files (x86)\Andro
id\android-sdk\platforms
C:\Program Files (x86)\Android\android-sdk\platforms>adb push tacoroot.sh /data/
local
297 KB/s (2129 bytes in 0.007s)
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 755 /data/l
ocal/tacoroot.sh
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --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 discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
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 same tim
e, and reboot the system.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --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 discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
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:\Program Files (x86)\Android\android-sdk\platforms>adb push misc_version /data
/local/tmp/misc_version
1896 KB/s (367096 bytes in 0.189s)
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/tmp/misc_version
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell sh -c '/data/loca
l/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...
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --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 discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
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:\Program Files (x86)\Android\android-sdk\platforms>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platforms>cd C:\Program Files (x86)\A
ndroid\android-sdk\tools
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem rebootRUU
... OKAY [ 0.147s]
finished. total time: 0.147s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY [ 0.117s]
finished. total time: 0.117s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash zip RUU_Vivo_W_G
ingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487
_si.zip
sending 'zip' (292817 KB)... OKAY [ 48.539s]
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 [197.732s]
finished. total time: 246.272s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot reboot
rebooting...
finished. total time: 0.144s
Hopefully this works for everyone as it did for me, If not feel free to PM me or post below with any further questions and i'll be happy to help
, also don't for get the push the THANKS button! :good:
Thank you for this!!!!!!!!!! The only issue I had was when you tell it to flash the ruu, where it says signed.zip, I looked at your list of a complete code and it was si.zip. So I changed it and somehow that made it work Again thanks a lot!
accord1 said:
Thank you for this!!!!!!!!!! The only issue I had was when you tell it to flash the ruu, where it says signed.zip, I looked at your list of a complete code and it was si.zip. So I changed it and somehow that made it work Again thanks a lot!
Click to expand...
Click to collapse
Hahah great! im glad it worked for you! :good:
Thanks for writing this up. I'm waiting on a warrantied replacement of my DInc 2 (the "1" on the alpha keyboard no longer works) and I'm a little concerned about rooting because of the need to downgrade (something that wasn't required when I rooted originally) but this makes it look fairly manageable.
My biggest concern? Making sure I hit the volume up AND down buttons in conjunction with the power button!
If someone could instead of just pulling the modules, do a pull of /system .....?
Sent from my vivow using xda premium
I just got my replacement and will try to pull this today. Will just need to look up how to first lol.
CondemnedSoul said:
If someone could instead of just pulling the modules, do a pull of /system .....?
Sent from my vivow using xda premium
Click to expand...
Click to collapse
I'm assuming from before we do anything? I have a replacement that should be at my house when I get home today, I'll be attempting this tonight. If you need me to pull something I can, just have to tell me how. Feel free to PM me.
adb pull /system (insert where to place it) then put it in a zip file
Sent from my vivow using xda premium
CondemnedSoul said:
adb pull /system (insert where to place it) then put it in a zip file
Sent from my vivow using xda premium
Click to expand...
Click to collapse
uploading to my dropbox now.
Orange Terror said:
uploading to my dropbox now.
Click to expand...
Click to collapse
Sweet, thanks!
Sent from my vivow using xda premium
so where is the RUU for this?
Edit, nevermind, I'm an idiot, just had to read
Orange Terror said:
so where is the RUU for this?
Edit, nevermind, I'm an idiot, just had to read
Click to expand...
Click to collapse
haha yeah i had to sneak it in there
if any of the devs need the 6.01.605.05 folder please pm me and i will send it to you.
Ok, I tried this, following the steps accordingly and my device is stuck in the HTC screen after
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
and when I try flashing it I get this:
Code:
error: cannot load 'RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip'
Any thoughts? should I try this from the start again?
cowboyv said:
Ok, I tried this, following the steps accordingly and my device is stuck in the HTC screen after
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
and when I try flashing it I get this:
Code:
error: cannot load 'RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip'
Any thoughts? should I try this from the start again?
Click to expand...
Click to collapse
For the
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
you should only see the HTC logo. This is normal. As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
dets34 said:
For the
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
you should only see the HTC logo. This is normal. As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
Click to expand...
Click to collapse
I'm also having an issue while running the command to flash the RUU file, I'm gonna try from scratch
Sent from my ADR6350 using xda app-developers app
dets34 said:
As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
Click to expand...
Click to collapse
Yep, I just opened it to make sure. I'm gonna start it from scratch following the steps again, will report once I'm done.
Stiil getting an error trying to load RUU file...
Edit: I think i got it! There were a couple spaces in the code that i didnt see
Triscuit said:
Stiil getting an error trying to load RUU file...
Edit: I think i got it! There were a couple spaces in the code that i didnt see
Click to expand...
Click to collapse
:good: let me know if it worked!
cowboyv said:
Yep, I just opened it to make sure. I'm gonna start it from scratch following the steps again, will report once I'm done.
Click to expand...
Click to collapse
double check your typing the file name correctly. its long and annoying to type :silly:. Also make sure you don't unzip it. (im sure you didn't, but just triple checking)
If it still doesn't work you may want to try to download the same RUU file but from a different source. Sometimes the files get corrupted and do not load correctly.

Downgrading a G2 through Fastboot Now Phone is Completely dead.

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).

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

FAILED (remote: 99 unknown fail)

Hello,
Trying to root my first phone and downgrade it following the directions (http://forum.xda-developers.com/show....php?t=1298990) very precisely...or so I thought. I keep getting an error at the second to last command when the rom actually gets flashed. Google has turned up several threads but those remedies don't seem to apply here. I'll give you my phone details as it stands right now.
HTC Droid Incredible 2
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0722
eMMC boot
July 18th 2011, 12:39:36
HBOOT
Vol up / down etc instructions then fastboot, recovery, etc with 3 droids on boards at the bottom.
So this may be redundant but I'm going to paste every command and the results.
I start from the phone fully booted looking at the home screen.
C:\Users\GPGVM\Desktop\Rooting>adb shell rm -r /data/local/tmp/*
adb server is out of date. killing...
* daemon started successfully *
C:\Users\GPGVM\Desktop\Rooting>adb push zergRush /data/local/tmp/zergRush
1883 KB/s (21215 bytes in 0.011s)
C:\Users\GPGVM\Desktop\Rooting>adb push misc_version /data/local/tmp/misc_version
1546 KB/s (15837 bytes in 0.010s)
C:\Users\GPGVM\Desktop\Rooting>adb shell chmod 777 /data/local/tmp/zergRush
C:\Users\GPGVM\Desktop\Rooting>adb shell chmod 777 /data/local/tmp/misc_version
C:\Users\GPGVM\Desktop\Rooting>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 ! 0x00016118[*] Scooting ...[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10[*] Sending 149 zerglings ...[*] Trying a new path ...[*] Sending 149 zerglings ...[*] Trying a new path ...[*] Sending 149 zerglings ...[*] Trying a new path ...[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd25bb9 0xafd39a87[*] Poping 24 more zerglings[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!
C:\Users\GPGVM\Desktop\Rooting>adb shell /data/local/tmp/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
adb server is out of date. killing...
* daemon started successfully *
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up partition 17...
C:\Users\GPGVM\Desktop\Rooting>adb reboot bootloader
At this point the phone reboots back to the "bootloader screen??" with the three droids at the bottom. It says FASTBOOT USB. One thread I read on this forum said the 99 error was because you were not in fastboot so I threw in this command and my device shows up???
C:\Users\GPGVM\Desktop\Rooting>fastboot devices
HT14VMA22756 fastboot
C:\Users\GPGVM\Desktop\Rooting>fastboot oem rebootRUU
... OKAY [ 0.158s]
finished. total time: 0.160s
The phone now goes to black with HTC logo on it. From what I've read in other forum threads this is proper.
C:\Users\GPGVM\Desktop\Rooting>fastboot erase cache
erasing 'cache'... OKAY [ 0.277s]
finished. total time: 0.279s
C:\Users\GPGVM\Desktop\Rooting>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_signed. zip
sending 'zip' (292817 KB)... OKAY [ 49.180s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 55.007s
And there I sit unable to get past this 99 unknown fail.
Any thoughts, suggestions or helpful reading would be appreciated.
TIA
JB
ramjet69 said:
Hello,
Trying to root my first phone and downgrade it following the directions (http://forum.xda-developers.com/show....php?t=1298990) very precisely...or so I thought. I keep getting an error at the second to last command when the rom actually gets flashed. Google has turned up several threads but those remedies don't seem to apply here. I'll give you my phone details as it stands right now.
HTC Droid Incredible 2
***UNLOCKED***
VIVO_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0722
eMMC boot
July 18th 2011, 12:39:36
TIA
JB
Click to expand...
Click to collapse
Your link is broken. You should be using prototype's tacoroot method I believe. It's a sticky in the development section. Is that what you are using?
gtdtm said:
Your link is broken. You should be using prototype's tacoroot method I believe. It's a sticky in the development section. Is that what you are using?
Click to expand...
Click to collapse
Here is the full link without the tags to chop it so you might have to cut and paste.
http://forum.xda-developers.com/showthread.php?t=1298990
Checking into the tacoroot sticky now....
He is htcdev unlocked. So tacoroot wiukdnt work. Use the 2nd post in the same thread
sent from my paranoid android
JehC said:
He is htcdev unlocked. So tacoroot wiukdnt work. Use the 2nd post in the same thread
sent from my paranoid android
Click to expand...
Click to collapse
Just to clarify it is unlocked using the method from HTC. I can relock too if that is better.
Jehc is right. Go to this thread:
http://forum.xda-developers.com/showthread.php?t=1751796
and look at the second post.

Phone won't unlock after **Relocked**

Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
please help!
***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***
itzjonjon69 said:
Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
please help!
***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***
Click to expand...
Click to collapse
Apply for a next token
Sent from my HTC One_M8 using Tapatalk
I did, same thing
i tried this (http://forum.xda-developers.com/showthread.php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as my super SU... please someone help me
I also did .
itzjonjon69 said:
i tried this (http://forum.xda-developers.com/showthread.php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as my super SU... please someone help me
Click to expand...
Click to collapse
I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.
mc_365 said:
I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.
Click to expand...
Click to collapse
oops i thought i updated the thread, but forum member russellvone SAVED my ass. So what he did was he had me download this file for my ATT M8
https://mega.co.nz/#!NUURzC5T!tCjG3n...c6zRAwOPZ8T2PI and told me to rename it 0P6BIMG.zip and place it in my adb fastboot folder
then he told me to run these commands:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot
then once everything was done we ran the commands from this thread (http://forum.xda-developers.com/show....php?t=2708571) and voila! i'm once again unlocked! He explained to me that when i tried to run the unlock commands before it didn't work because i had the secure boot.img and what he had me flash was a file he created which made it unsecure so i could run the command. HUGE HUGE props to this guy.
good to hear

Categories

Resources