yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] jitajt:
I just tried doing it through linux and same result, once I go into recovery and it shows up in computer as two HTC USB Devices just as in windows so it isn't a driver issue, and just like windows I am able to send adb commands and get responses but as soon as it goes into recovery nada. I think my phone is just cursed, I might have them send me another phone for the "unresponsive touch screen" issue and try that one. couldnt hurt.
[Droid Incredible Android Development] rynosaur:
Hold on, did you set up a 51-android.rules driver file in /etc/udev/rules.d? If you can reboot the phone with adb reboot recovery from android OS desktop (fully booted) with adb debug checkbox on, then your linux driver is a-ok.

If everything is setup in linux correctly and you're still failing, what numbers/letters do you have in bootloader? I'm running the newest (May) firmware, and I just got my phone two days ago direct from Verizon.
[Droid Incredible Android Development] jitajt:
yes I set eveything up along with the rules and as I mentioned above I can send commands and receive responses (adb shell and get $, and I can reboot the phone into recovery) mine is the March firmware (got it when it first came out). I am literally out of ideas.
[Droid Incredible Android Development] rynosaur:
Seems like a 16gb SDHC card has been many peoples' ace-in-the-hole.
[Droid Incredible Android Development] mycomputerisjunk:
I have been trying to root since it came out 100+ tries and many methods. And I finally go it!!

I had to take out my 8GB class 6 microSD and use a really old 1GB one I had lying around. BoooM! First time, every time.
[Droid Incredible Android Development] jitajt:
I just tried my wifes 16gb sandisk and still a no go
[Droid Incredible Android Development] HolyGrail:
Did you see my walk through right above? Post #554
[Droid Incredible Android Development] rynosaur:
Yeah, I wish I hadn't given away my 1gb from my 2008 G1

that = stupid
[Droid Incredible Android Development] jitajt:
yeah I tried that along with the 50 different other ways and still the same results.
[Droid Incredible Android Development] HolyGrail:
I just posted that not long ago, you tried it already? I'm like you and tried every single thing I heard, and watched every video. My walkthrough was the only thing that worked, an it worked the first time. Been trying for 2 days prior to that.
[Droid Incredible Android Development] JaydenR:
Being that the OP is not updating. Can someone make a post that has all the current steps to get busy box, root, SU apk running? Too much to read through. We need a nice complete walk through.
[Droid Incredible Android Development] HolyGrail:
This is the steps I used after getting into recovery, and it works perfectly. Permanent root, Superuser, and Wifi tether all working.

http://www.incredibleforum.com/foru...process-my-regurgitation-perm-part-added.html
[Droid Incredible Android Development] Gimpeh:
Even that walkthrough is not that well put together.
[Droid Incredible Android Development] rynosaur:
What brand / capacity / class / partition-type (exact, ie FAT16, FAT32, exFAT) / format type (windows full, windows quick, linux format: parted/gparted etc) did you use to obtain these results? I am convinced now that our exploit lies in recovery checking the sdcard for recovery tools and in that interval adb root shell access should be possible.
[Droid Incredible Android Development] JaydenR:
Can you put one together? ;)
[Droid Incredible Android Development] Gimpeh:
I left myself open for that. If nobody else does soon I just may.
[Droid Incredible Android Development] HolyGrail:
I use the 2GB Micro SD card that came with the incredible, an I formatted it with FAT32. (formatted it full, not quick) I used Windows 7 64 bit.

After trying every walk through and every video, I had no luck. Once I figured out this alternative way, it work the first time. I broke out doing the happy dance.
[Droid Incredible Android Development] HolyGrail:
Yes it not, but if you know a better one, why not be constructive and post it for the user who requested one.
[Droid Incredible Android Development] JaydenR:
Okay about to try this. One question. I have received several diff answers. Does the 3 files (ots, root file) go in the tools folder or in the sd cards root? Thanks in advance.
[Droid Incredible Android Development] CaptainTaco:
Well I was thinking of making a batch file that just does the whole thong for you (after you get ash working) just including all the required files, but I have a feeling unrevoked team is going to he releasing something similar soon... so... I can if people want...
[Droid Incredible Android Development] HolyGrail:
Tools folder.
[Droid Incredible Android Development] b00sted:
ok, as most of you guys prob seen my 1000 posts of me crying it wont work here is what I did and got it to work. I followed this video to the letter.

CG4zAOMLMAQ <- youtube (cant post links still)

I also used the moto droid 16gb card and laptop running win7 x64 with fresh driver install.
[Droid Incredible Android Development] rynosaur:
Fact is, without an accurate understanding of what's going on in the hardware, SPL and recovery software, anyone's directions are going to be a hodge-podge of correct steps and steps that were tangential to success, including some which may actually be barriers to reproducing root on any DI, any PC, and any SDcard!
[Droid Incredible Android Development] CaptainTaco:
HolyGrail please don't answer unless you are sure of the answer. The OTA.zip and payload-update.zip, Superuser.apk, SU file, Busybox etc go in the sdcard root . They are then transfered to your phones partition using "apply update.zip" through recovery or the "cat" command through adb shell in the case of SU, Superuser.apk, and Busybox later in the steps.
[Droid Incredible Android Development] seanmcd72:
this didn't change anything for me, so there is still something to do with the card, or who knows what.
[Droid Incredible Android Development] JaydenR:
A batch file would be awesome.

Btw, thanks Holy. ;)
[Droid Incredible Android Development] pozer69:
Wait a minute, I didn't setup any drivers in linux but I am able to see my device with adb devices...please elaborate on this driver for linux
[Droid Incredible Android Development] HolyGrail:
Here is the thing, after figuring out my way into recovery, I used the instruction I posted to finished it up. So what I posted worked as its posted.

The user asked a question, and I gave him the best answer I knew and one that worked on my incredible. Would you have rather I tell him that there are no good instructions and good luck figuring it out?

Botom line, if a user asks for help, I try to provide him/her with options, and I don't think I should be scrutinize for it.
[Droid Incredible Android Development] jwood:
Subscribed
[Droid Incredible Android Development] onodontbescurred:
so what would the loop command be in a cmd prompt?

I know it involves the FOR command but dont know exactly how to do it
[Droid Incredible Android Development] Braden:
Confirmed! :D :D :D
[Droid Incredible Android Development] seanhassars:
couple questions:

1. if i'm on 2.1 update1 with software # 1.22.605.2 and I accepted that exchange update back when the phone was first released, do I need to downgrade first? answered in OP

2. is there anyway to backup both my apps AND their settings or is it strictly backing up apps?
[Droid Incredible Android Development] IncredibleDoes:
sorry, its before OTA... my mistake
[Droid Incredible Android Development] zeke1988:
deleted, got the answer from OP's post
[Droid Incredible Android Development] junjlo:
Confirmation

Dumb question plz dont flame is this root access?
[Droid Incredible Android Development] Braden:
This may explain why mine, while taking the patched update, still won't allow me access to su. I can see it in my /system/bin but whenever I run it, I get permission denied. I'm currently running with the OTA.

For Windows users BTW, if you want to get an adb loop, open Powershell instead of the command prompt and run this command from the adb directory:

while ($true) { .\adb shell }

Also, I found that I had to attempt to run the update.zip and let it fail before I could push busybox or the update zips to the sdcard.
[Droid Incredible Android Development] zebdor44:
Just create a batch file and put this in the contents:

:TOP

C:\adb shell

GOTO TOP

Then run the batch file from cmd prompt.

And yes this will give root access but its gonna be based on luck until they can control the race condition a little more.

Thanks again devs! Gonna roll-back to pre-ota and give this exploit a go...
[Droid Incredible Android Development] zeke1988:
anyone got a ADB guide for dummy? im new to this.

tried google, but only got the one for droid....
[Droid Incredible Android Development] jonnybueno:
I successfully rooted my DINC with the latest OTA update. No need to downgrade
[Droid Incredible Android Development] jonnybueno:
Actually, me too... gonna try to reboot into recovery and try again
[Droid Incredible Android Development] Drukan:
im still trying!!! Im on reboot 12.... gonna give it a few more shots before bed!

THANX TO ALL THE GUYS WHO FIGURED THIS OUT AND GOT IT GOIN!!! :D
[Droid Incredible Android Development] madman34:
Clarify please: Do we need to do the downgrade ??

So just to clarify as soon as it is determined for sure, do we need to do the downgrade if we have .2 update 1 on ours ????? Mucho Grazi ;-)

Well right there at the top Shadowmite says that we do NOT need to downgrade, so I wonder if the problem is that maybe you who are having trouble are missing the last step of installing Superuser.apk ???? I am going to do mine in the next day or two ;-)
[Droid Incredible Android Development] scuccia:
I've been ROOTED. Thanks unrEVOked team!!!
[Droid Incredible Android Development] tats_06:
I am going to try the update.zip method...what's the sequence to get to recovery? Volume up + power? Thanks. :)
[Droid Incredible Android Development] drsuse:
does anyone have the update.zip and a dummy's guide? i rooted my droid and have done my crappy iphone, but have to know where to start.. i will be more than happy to paypal someone
[Droid Incredible Android Development] madman34:
Look up,,,,,,

The needed files are there in ShadowMite's first post, look where he links you to the process and open it and there are links to all you need there ;-) Etu Roote'
[Droid Incredible Android Development] zeke1988:
will this brick my phone?
[Droid Incredible Android Development] madman34:
Yes Junior, it could happen

As with anything we do in here, or for that matter just turning it on in the morning could brick it. Granted that any time you start messing around in the deep recesses of the device you are more likely to kill it. That said, the chances are greatly reduced by good experience with the type of task you are undertaking and understanding of what you are doing and how it works, and reliable equipment, and a fully charged battery, but if you have never done anything like this before and really can not say that you reeeeeeeeeeally need the advantages of root access, or can not bear the risk that it may die, then I would not touch it with a 10 foot pole. Just my opinion, I could be wrong ;-)
[Droid Incredible Android Development] JaydenR:
So all sd card root?

I got the same thing over irc. Diff answers. Lol
[Droid Incredible Android Development] HolyGrail:
I was sure of the answer, I use this guide and it worked. It puts update, ota, busybox, and superuser in the tools folder. You might have a different way, but don't criticize alternatives.

http://www.incredibleforum.com/foru...process-my-regurgitation-perm-part-added.html
[Droid Incredible Android Development] JaydenR:
I appreciate any and all help guys. Thanks all. I am not a noob just want to do it first try. I have a adata 16 gb class 6 so that should help. Lol
[Droid Incredible Android Development] CaptainTaco:
Following the install procedures, you will use ADB PUSH to push all files from your host computer to /sdcard. So where you download them does not matter, they will indeed need to end up on /sdcard aka the top folder of the sdcard partition. From there they will be moved later in the steps. If they are not on your SD card, (or somewhere on your phone) the shell will not be able to read them with the cat command to properly copy the files to their proper directories. OTA.zip and Payload-update.zip MUST be on your sdcard in the top level directory, otherwise "apply update.zip" in recovery will not find them.

Sorry for the confusion :)

When all else fails, if you have two different answers, use the one that has a follow up explaination as to why... on either forum.
[Droid Incredible Android Development] rynosaur:
This guy doesn't know what the "ln" command does in linux and so his expertise is deprecated to "windows-only" in my mind, i.e., knows enough to be dangerous, and has the right DI-firmware/sdcard to reproduce his success on his own phone. I know I have my drivers/setup 100% in linux and I'm still unable to get adb in recovery--I'll probably switch to windows 7/x64 with a clean card and get the same results as in Ubuntu and Linux Mint.
[Droid Incredible Android Development] antizac:
holy crikeys this worked for me!!!!
[Droid Incredible Android Development] CaptainTaco:
This was taking off the post you have linked to.

QUOTE:

adb push busybox /sdcard/busybox
adb push ota.zip /sdcard/update.zip
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk

Those lines of code are putting the files on the /sdcard... As i stated, it does not matter where you download the files, as long as they end up on the sdcard. The tools folder is a perfectly fine location to store them temporarily if you choose, but you will still need to put them on the sdcard at some point. I'm not trying to be rude or condescending, just trying to eliminate confusion. :)
[Droid Incredible Android Development] JaydenR:
I also noticed that. Thanks. I'm off to root. Wish me luck.
[Droid Incredible Android Development] CaptainTaco:
HolyGrail, none of us are scrutinizing you for trying to help. However, there is enough confusion with the DI Root process, it is one of the most difficult roots so far at this point. We just ask you fully understand the process before answering questions others may have. Otherwise this process will go from hard, to impossible to others reading the forum. I nor anyone else is trying to bash you in any way, we are just trying to make everything as easily understandable as possible. Please don't take offense ;)

EDIT: It should also be noted that the post you linked to, left out the complete steps to installing busybox. He had you copy busybox binary to the sdcard, but then forgot about it there. The full busy box install steps can be found in my previous post, Post 491
[Droid Incredible Android Development] HolyGrail:
I understand, but for me there was no other way but to put them in the tools folder, because the only way I was able access recovery was to format my sdcard. Which meant I had to get them from the tools folder. I thought JaydenR's was going to try my walk through and my answer was based on that. I know users had success with accessing the recovery. (The videos shows them getting it in like 2 tries. I ending up battery pulling for 2 days.) In my alternative method you have no choice but to put them in the tools folder.
[Droid Incredible Android Development] HolyGrail:
I understand completely Captain. No Prob. Thanks for the tip on busybox, will try and get it installed right.

On your busybox method, can I use terminal emu, or would I have to go through the whole root process again?
[Droid Incredible Android Development] CaptainTaco:
This is my point about understanding the process. You do have a choice where you download them. When you ADB PUSH you need to get them off the host computer, who cares where they are? The important part is where they need to be, and they need to be on the sdcard to complete the root process.

I could do

ADB PUSH C:/busybox /sdcard/busybox

If on a windows machine and downloaded the files to C:/

I could do

adb push /home/usr/busybox /sdcard/busybox

If on my linux machine and downloaded the files to my home. What matters is where they go, and that is /sdcard in any tutorial, using any method at this point for the DI root.

To the user asking the question, if he put the files in the tools directory, and later ran "apply update.zip" he would recieve, error update.zip not found.

It's just a matter of what the user asking the question is going to percieve from the answer. Can't assume he is using your walkthrough :)
[Droid Incredible Android Development] CaptainTaco:
Unfortunately the filesystem is still locked down, so any change (other than name change or deletion) needs to be done through reboot recovery, which means half the root steps need to be done over again...
[Droid Incredible Android Development] j1000:
Can someone please tell me what I'm doing wrong or attach the file I need please. I'm sure I'm an idiot and its simple. But .....

My problem is the phone is recognized as a disk drive etc. in windows 7 32 bit, but when I try to root it always fails and says I need to install drivers. I don't have any drivers install under C:\android-sdk-windows\drivers

Any help would be appreciated.
[Droid Incredible Android Development] antizac:
holy schnikeys that worked!
[Droid Incredible Android Development] HolyGrail:
Darn....Well i face a dilemma then. The only way I can access recovery is to first format the card, place it in the phone, and do it this way. I can't place busybox on the sdcard because the format will just erase it. Any ideas Captain? :(

As of right now my wifi tether works and root explorer appears to be working. What does busybox control?
[Droid Incredible Android Development] LeoD:
First I'd like to say thank you for your post HolyGrail, I wanted you to know I followed your directions to the letter, like you I used 2 seperate SD cards formatted them both fat32, swapped them when outlined in your instructions etc etc and I to am running a win 7 64 bit machine and still was not able to get in. BTW I also installed, reinstalled the drivers as well. Obviously to me there is just not one cure all for everyone. I have done alot of testing with this root over the past few days and have tried them all but my Dinc just does not want to work with me.

Anyway thanks for the info and thought you would want to know someone's outcome with your method.
[Droid Incredible Android Development] CaptainTaco:
If you are not having problems, then I would just wait till an easier method comes around. Busybox can be pushed to the SD card with adb push, as you've used in previous methods, after the getting adb to work in recovery (which would be after you format the card.)

This wouldn't effect any of your other work, as nothing is using the files you put on the sdcard anymore, other than the ota.zip and payload-update.zip that you will have to push over to get adb to work in recovery again.

Busybox is just a command set that expands the androids command set and adds back many commonly used unix/linux commands such as "cp" (copy) and a wealth of others. Some applications requiring root use these commands (like Root Explorer, Titanium Backup, and others)

The process for you, if you need to format your card, would be. Do what you have to (format, reboot to recovery using your steps as previous)

Then you would just

adb push ota.zip /sdcard/update.zip
adb push busybox /sdcard/busybox

(use full paths if its not in your tools folder like you said)

aka adb push c:\Folder_File_Is_In\ota.zip /sdcard/update.zip

then follow the rest of the procedure

adb push payload-update.zip /sdcard/update.zip (((DON"T PRESS ENTER YET)))

use "apply update.zip" on phone

press enter in shell for the above command

etc etc, following the instructions, you have already. Once you are in adb shell in recovery, follow the instructions I posted.
[Droid Incredible Android Development] HolyGrail:
That sucks man, wish it would have worked for you. Have you seen this video yet? I only watched a little bit, but it appears to be a another method to try.

http://www.youtube.com/watch?v=CG4zAOMLMAQ&feature=player_embedded
[Droid Incredible Android Development] CaptainTaco:
Run "C:\android-sdk-windows\SDK Setup.exe" to run the Android SDK package manager, and accept the install for

"Usb Driver package, revision 3"

You will then have a usb_driver folder in C:\android-sdk-windows\

Open the ".inf" file inside your C:\android-sdk-windows\usb_driver and add the following lines at the end of the [Google.NTx86] block of code, and the end of [Google.NTamd64] (under the the ";Google NexusOne" entries)

;
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

When plugging your phone in, point to the "C:\android-sdk-windows\usb_driver" to associate the driver with your device.
[Droid Incredible Android Development] b00sted:
ok well i thought i did everything right but I think i hit a snag. I followed the newest youtube vid and it got me root and superuser.apk and tethering working as well as root explorer. but when I try to install busybox I get this error..

# cat /sdcard/busybox > busybox

error cannot create busybox: read-only file system.

what did I do wrong or how can i fix it? please dont tell me re-root as i been at trying to get the phone to boot recovery with adb for a hr now again lol.

i remember back on the moto droid I would have to mount the file system first? is that theroy still true here?

mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system <-- from my old droid records lol

EDIT:

when i try to mount it like back in moto days i get this...

cat /sdcard/busybox > busybox

cannot create busybox: not enough memory
[Droid Incredible Android Development] j1000:
I've tried all this and it says driver installed but it always says no device found in SDK window any other suggestions
[Droid Incredible Android Development] deadlinguo:
Reposting this for an answer hopefully. I just want to confirm that my drivers are not the problem here. Under Device Manager, it says Android Phone->Android Composite ADB Interface. The "adb devices" command works fine when the phone is booted up, but returns nothing when I try doing it on the recovery screen. Does everything sound like it's functioning like it should?
[Droid Incredible Android Development] jackattack:
Same here. It shows Android Composite ADB Interface even at the FastBoot screen. As soon as I'm in recovery, it shows up as a generic USB Mass Storage Device and I can't change it. Keep getting device not found.
[Droid Incredible Android Development] mwyrick:
You have to do it while in recovery root, if you reboot even with persistance root and remount rw it will not work.
[Droid Incredible Android Development] n0-0ne:
ditto, I've removed all drivers, tried just the android sdk drivers modified for the inc and just the htc drivers, and a combo of both. I still only get generic volumes in device manager when in recovery. I've yet to see anyone show me what they have in the device manager when in recovery on an exploitable phone, but I bet it's the same and no one cares to check.

I've watched every youtube video read every doc and tried every method, I'm no rooting newbie, I did the mytouch the day the gold card method came out, I've been hacking winmo phones and bb's for years.

I may try to do this from another pc and see if I get the same results, but I just don't have the time. I also don't have an extra sd card to try and I'm doubting it's gonna make a difference from what other people are saying.
[Droid Incredible Android Development] rynosaur:
I was responding to who should do another How-To and how. The original one is very slim on details, and I'm concerned we get accurate details, that's all.
[Droid Incredible Android Development] j1000:
still getting no device found have tried xp and windows 7 32 bit ?
[Droid Incredible Android Development] b00sted:
*swears* i cant get it back into recovery lol