Develop Bugs

[Q] was this radio flashing successful or not?

hi all,
just flashed radio 12.41.60.19_26.06.04.14_M in order to flash Android revolution HD using below method:
- Download the zip file in this post and extract it to a folder on your computer
- Copy your "radio.img" into this folder
- Reboot your phone into bootloader mode (poweroff and then Volume- + Power button)
- Select fastboot
- Connect your phone to the computer
- Open "Start here.bat" (don't worry, you can check that it only contains a link to command prompt)
- While in the command prompt issue the following commands:
- "adb reboot bootloader"
- "fastboot flash radio radio.img"
- "fastboot reboot"
- Your phone should now be rebooting as normal, with a newly flashed radio
Click to expand...
Click to collapse
in the CMD there are these lines as result:
C:\Users\...\Desktop\Radio flash>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
C:\Users\...\Desktop\Radio flash>fastboot flash radio radio.img
sending 'radio' (24832 KB)... OKAY [ 4.287s]
writing 'radio'... OKAY [ 23.686s]
finished. total time: 27.974s
C:\Users\...\Desktop\Radio flash>fastboot reboot
rebooting...
finished. total time: 0.151s
Click to expand...
Click to collapse
Also on bootloader mode desired radio number mentioned. According to the red text; was the flashing successful? what' wrong with it?
-----------
I downloaded Android SDK zip file and extracted it then copy radio.img into 'tools' folder. When I try to run 'fastboot flash radio radio.img' it returned error that 'AdbWinApi.dll' is missing. it's the reason I was forced to use above method for flashing radio instead. should I copy 'AdbWinApi.dll' manually to 'C:\sdk\tools' ? (i.e. from EasyS-OFF.zip package) anyone should copy it manually? Why it isn't there by default?
many Thanks in advance

writing 'radio'... OKAY [ 23.686s]
finished. total time: 27.974s
Click to expand...
Click to collapse
seems successful flashed. and yes you need to put AdbWinApi.dll in the same folder with adb.exe or just copy them to x:\windows\system32. then you can directly run adb in cmd.

187j3x1 said:
seems successful flashed. and yes you need to put AdbWinApi.dll in the same folder with adb.exe or just copy them to x:\windows\system32. then you can directly run adb in cmd.
Click to expand...
Click to collapse
Thanks a lot

Bricked Kindle, bought factory cable, got to stay in fastboot, then bricked it again

I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"

Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s

Hmmm did you try the kfu or the kindle fire unbrick utility?

Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you

You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.

three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s

When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.

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

how to flash pd98img.zip through adb

Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key

adilrenzu said:
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
Click to expand...
Click to collapse
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:

glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you

fefetron said:
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
Click to expand...
Click to collapse
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.

glevitan said:
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
Click to expand...
Click to collapse
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g

fefetron said:
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
Click to expand...
Click to collapse
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:

glevitan said:
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
Click to expand...
Click to collapse
Just Waiting for the device.. nothing more
im traying to install new drivers.
i´ll back

glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Many thanks!
I too had this boot problem on a bad flash through the Hack Kit
(my fault by the way). From power on it took 20 mins to get to the first white HTC screen . Then a further 10 mins to start normal boot.
Apart from the LONG boot, everything worked perfectly. Using TermEm I could boot into bootloader and recovery. The rom, IceColdSandwich worked perfectly in every respect but the corrupted boot was doing my head in.
Using your tutorial, I managed to flash the correct bootloader and now all is good.
hboot before was 0.85.2007
hboot after is 0.85.0024
Sorry if this is a long post but I think it is worth it. Here is a log of the fastboot process:
F:\Android\DHD\Bootloader Image\Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT11BRX11244 device
F:\Android\DHD\Bootloader Image\Fastboot>fastboot oem rebootRUU
... OKAY [ 0.375s]
finished. total time: 0.376s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot flash zip PD98IMG.zip
< waiting for device >
sending 'zip' (227 KB)... OKAY [ 0.056s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
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
OKAY [6586.776s]
finished. total time: 6586.834s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot reboot
rebooting...
finished. total time: 8.532s
F:\Android\DHD\Bootloader Image\Fastboot>
I have to say that the timings, because of the LONG boot, are completely wrong, . I was tempted to pull the plug on a number of occasions but I gave myself a talking to and went for a coffee.
The whole process took about 2 hours and I am now the delighted owner of a normal booting DHD.
To anyone who wants to attempt this procedure, the watchword is patience. Whenever you think nothing is happening, DO NOTHING!
The different stages will eventually happen just as laid out as per Glevitan. Good luck with your attempt.
Once again, many thanks.
Edit: Just an afterthought, at one stage Windows had a failed attempt at installing usb drivers that ended up as an 'Unknown Device'. Just ignore it and keep going.

Edit: I just tried again and it worked, nevermind!
Just fyi: if you get an error after flashing the ZIP, just flash it again.

Thanks! This was helpful.
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse

Problem Rooting...know this is old but...

Ok i came here from here http://forum.xda-developers.com/showthread.php?t=1751796
Droid Incredible 2 runnig GB 2.3.4 -- 6.01.605.05 710RD
TACOROOT
(TCR)
Versions: 6.01.605.05 firmware
Tacoroot is a temp root method discovered by Justin Case that will allow those on the newer firmware to flash an older version and root with Revolutionary. Before you begin, download this zip containing all the files you'll need:
http://d-h.st/yJQ
Extract this zip to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to the wherever you extracted it wherever it comes up. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is reccomended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Remove the space in the middle of the word radio before hitting enter, I don't know why it won't let me remove it. Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums tacoroot.sh Result should be 6ec06d776feb212d8b2a55817eddf76d
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devices Result should be your phone's serial number. If it isn't make sure drivers are properly installed and USB Debugging is enabled.("Its all good till i reach this step, i cant see my serial number, i have installed the drivers, the new ones from htc sync, i have reinstalled the drivers but it not work at all...)"
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue.
adb shell /data/local/tacoroot.sh --root
adb wait-for-device Running the step before this will reboot your phone again, this time it will be bootlooping, meaning it will not boot fully and get stuck on the boot animation. Once your prompt comes back after this step, you're good to continue even though the phone isn't fully booted.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tacoroot.sh --undo This will reboot your phone one more time, this time fully stable and will boot completely. Continue once fully booted.
adb reboot bootloader This will reboot your phone to a white screen with a few options. Once you are at this screen, continue with the instructions.
fastboot devices Result should be your phone's serial number, again.
fastboot getvar mainver The result should be 2.18.605.3. If it is not, something was not done correctly, you'll need to restart from the beginning.
fastboot erase cache
fastboot oem rebootRUU
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 This will take a bit of time without giving any indication as to when it will be done, be patient and do not interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )
fastboot reboot

Make sure you have USB debugging enabled, I think it's under Apps>Development.
Sent from my SCH-I535 using Tapatalk 2

It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk

Killerin said:
It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Don't install htc sync, that can mess it up. The drivers from the OP should work, nobody else has had problems with them.
Sent from my SCH-I535 using Tapatalk 2

I also tried that but the drivers of the OP doesn't work for me, I can't even install it. Will upload the screen shots.
I'm using windows 8 could it be a problem?
Sent from my HTC DROID Incredible 2 using Tapatalk

This is what i get when im trying to install the OP's Drivers

Killerin said:
This is what i get when im trying to install the OP's Drivers
Click to expand...
Click to collapse
Translation?
Sent from my SCH-I535 using Tapatalk 2

prototype7 said:
Translation?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.

gtdtm said:
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.
Click to expand...
Click to collapse
+1, dont know what appeared on spanish lol
Will Install windows 7, probably is W8 the problem with the drivers

thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!

Killerin said:
thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!
Click to expand...
Click to collapse
I am having the same problem. It sounds like this last step is supposed to take as long as the previous step. The fact that it comes up with the "FAILED (12 signature verify fail) response worries me. If I reboot and continue on with installing revolutionary, will this brick my phone? Or is it supposed to do this (12 signature verify fail)?

I've read a lot of people have that problem. Just move on with rev and go back later and update the radio. A quick search will give you LTS of threads with the instructions to install a new radio. Hint:it's done in boot loader not recovery.
Sent from my Incredible 2 using xda app-developers app