yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] pozer69:
I understand that and I want bashing you, everyone does start at tyke bottom and I'm no expert either but your post didn't say much so I just assumed.
[Droid Incredible Android Development] Skapunker:
I reboot normally and still have persistent root, you don't have to pull the battery.
[Droid Incredible Android Development] sethman408:
Still not working for me... what Superuser.apk are you guys using .. and im assuming your installing the su that came in the payload-update.zip file?
[Droid Incredible Android Development] blw1230:
No problem pozer69. I know how it is. I didn't take it the wrong way. But you're probably right, I might just wait for an easier method, the adb shell was a minor thing... I'm not too computer code literate. My biggest problem seems to be with the drivers and never recognizing my device.... Oh well. Thanks for the help.
[Droid Incredible Android Development] mwyrick:
persistence after Superuser

I thought mine did as well, But, I notice that when doing the su in the shell, I had to go into the GUI Superuser program and let it give superuser to the unknown shell task. After that, the su command in the shell works again.

I did not have to redo the root peristence part after installing this, infact, doing it will remove the su program that should be run instead of the sh copy that the "old" root persistence method used.
[Droid Incredible Android Development] syrguy1969:
Thanks. I have the backup assistant running and I have my apps (most anyway LOL) backed up through Astro, so I am hoping to be all set there!! (only ways I know how in Android, it isn't like WM when I run SPB Backup and have a complete image of my device saved LOL)

I am thinking of waiting for the easier way I am sure they will have out soon as you said!! I am just looking for a complete list to post in another forum I am keeping up on things happening here!

Thanks again for the info!!
[Droid Incredible Android Development] sethman408:
This is what i thought as well... but i dont even get the Superuser app in the app drawer.
[Droid Incredible Android Development] mwyrick:
I used the su and Superuser referenced in post #363, not the one from payload-update.zip, worked well.
[Droid Incredible Android Development] pozer69:
Is the device recognized by windows? Did you update the .inf file in usb_drivers folder of the sdk?
[Droid Incredible Android Development] mwyrick:
This is what it shows on mine. I had to do the install using the recovery method, when I tried to do it with root after a reboot it would not install correctly, (after a remount,rw). So I went back and installed Superuser and su using the recovery root method.

There are a lot of commands that don't seem to work correctly with /system remounted rw when booting normally. Most of my problems were fixed if I install everything with recovery root access instead of root access after a normal reboot. A good example is that when rooted and remounted, if I tried to copy or write to /system/xbin, I always received a can't allocate memory error. Once I was back in recovery mode with root, the copies went fine.
[Droid Incredible Android Development] sethman408:
Trying this now... i bet this was my problem.

yup! fixed it!

thanks
[Droid Incredible Android Development] RLKirk:
how do i install the driver on a windows 7 machine wont let me through update driver in device manager
[Droid Incredible Android Development] krelvinaz:
That's the thing. I may not be using the newest payload file. This is a moving Target. For those who are not typist it is very easy to fat finger the commands.

Also there are still many that can't even get started because they can't get in yet. Most likely a sdcard issue but nobody knows for sure.

Via mobile.
[Droid Incredible Android Development] Skapunker:
Here's everything you need to do:

Hope this helps having it in one spot
[Droid Incredible Android Development] krelvinaz:
I loaded the htcsync and it did the drivers automatically.
[Droid Incredible Android Development] RLKirk:
weird mine wont do that
[Droid Incredible Android Development] veli69:
If my phone is in fast boot it comes up as "android 1.0" and I cant connect to it. When it is running normally I can, Im guessing this is the issue.
[Droid Incredible Android Development] jster:
hboot version?

I'm one of the people who has been unable to get adb to work in recovery mode.

I got my incredible the day it was released and have hboot .77. In the "Nothing I try gets ADB to connect in Recovery" thread, everyone seems to have hboot .77 as well. I was wondering if anyone who has successfully gotten this to work has hboot .77 or if everyone has hboot .79?

Thanks for your input!

Kushiel
[Droid Incredible Android Development] solidunit:
Can't get this working at all. Tried on two PC's. I give up.
[Droid Incredible Android Development] RLKirk:
do i need a modied driver file in the usb_drivers folder in andriod sdk???
[Droid Incredible Android Development] krelvinaz:
I didn't. All I did is install the htcsync on each of the workstations I am using and when I connected the phone it found the drivers BT itself. 3 win7 and 1 winxp box.

I loaded the SDK AFTER that.

via my dinc...
[Droid Incredible Android Development] RLKirk:
alright thxs for the reply
[Droid Incredible Android Development] gladesmellzgood:
Been at this for like 5 hours lol, my timing or something just isn't working.
[Droid Incredible Android Development] antizac:
I have been unable to get adb to run in recovery .. tried every method in this thread at least 20 times each... my hboot version is 0.79.0000 what hboot versions are people running that are able to get this to work?
[Droid Incredible Android Development] b00sted:
mine is .77 and it does not work for me. I have tired 3 computers and 3 cards and all methods posted with no luck.
[Droid Incredible Android Development] CaptainTaco:
OK, so a couple quick notes. I had no problems when using the method given in post 201 (Page 19 I believe), to get ADB Recovery working. This is the easiest method, and has worked for me on two different Incredibles, I also tried several different class SD Cards, with and without data.

However, once rooted (persistent root), this method no longer works for me to get into recovery with ADB shell.

At this point you_eeeeediots method

works... with one exception... I have not seen it mentioned anywhere that this is required, but it will NOT work for me unless the following is done. After you plug the USB cable back in, via the you_eeeeediots steps above, a “device found” message pops up for “Android 1.0” that requires a driver, you need to manually use the USB3 driver for android SDK.

So for Windows machines;

go to device manager

right click “Android 1.0”

select “update driver”

choose "Let me pick from a list of device drivers on my computer"

select "Have Disk"

Browse to your AndroidSDK\android-sdk-windows\usb_driver\android_winUSB.ini

then continue on with the steps
[Droid Incredible Android Development] IncredibleGuy:
INCREDIBLEC XC SHIP S-ON

HBOOT-0.77.0000

MICROP-0417

TOUCH PANEL-ATMEL224_16ab

RADIO-1.00.03.04.06

Mar 23 2010, 19:36:22

No luck here either. I have tried 8gb Kingston mSD and the 2gb mSD with no luck. ADB sees the device except when in recovery mode. Windows doesn't see the device while in recovery mode either.
[Droid Incredible Android Development] WoZeR:
Rooting an Android phone is nothing more then getting administrator privileges on the phone's OS. Its called rooting because the admin account in linux is Root.
[Droid Incredible Android Development] mwyrick:
Both my phones have 0.77 and rooted fine.
[Droid Incredible Android Development] m1k3-:
My personal opinion is that it has a lot to do with the sd card. This is extremely circumstantial, but here's my experience:

I have an 8gb sd card (not sure what class) and I have not been able to get into recovery with adb on any of the attempts I've made (well over 100 attempts, I'd estimate).

Last night, I asked my roommate if he had a spare sd I could test with. He had a kingston 1gb card (model sd-c01g). I used it and was pretty much immediately able to get adb in recovery (1st or 2nd try).

Once I confirmed the procedure with the 1gb card, I tried again with my 8gb card and was unable to get it to work. I tried again with the 1gb card and was able to get it to work pretty much every time.

I agree with what a lot of people have said that there's a reasonable amount of circumstantial evidence that points to the sd card as being a key component.

My .02.
[Droid Incredible Android Development] WoZeR:
Its a Linux command prompt on the phone. Try some commands like "ls" its like doing a DIR in windows.
[Droid Incredible Android Development] syrguy1969:
Thanks, I was thinking that it wouldn't affect any data on the device, but I wanted to check for sure. I am guessing when new ROMs (or whatever that are called in Android) will wipe a device clean like in the WM world?
[Droid Incredible Android Development] antizac:
I dont have the /usb-drivers/ folder in my android-windows-sdk folder? ?? how can get it ?
[Droid Incredible Android Development] WoZeR:
Yeah, if you flash a rom you will wipe everything on the phone but not the data on the SD card.
[Droid Incredible Android Development] blw1230:
Yep. When I'm in the cmd prompt, if I enter "adb devices" just to see what devices are connected, I get nothing. When the phones on, its correct. So I'm not sure...
[Droid Incredible Android Development] Hatman41:
Run the SDK Setup.exe and download the USB drivers.
[Droid Incredible Android Development] b00sted:
I tired with the following

2GB sd that came with the Inc. (no luck)

1GB sd a trancend card my wife had (no luck)

16GB from my old moto droid (no luck)
[Droid Incredible Android Development] andrew53517:
I hope they package an easier method soon. I had no luck with my 8 gb SD card either.

-------------------------------------

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] antizac:
I tried this.. finally installed the drivers (didnt know I needed them) and still nothing.... this is getting really frustrating
[Droid Incredible Android Development] AlexanderJohn:
Now that ROOT is achieved... Will it be easier, harder or the same problem to find an exploit?
[Droid Incredible Android Development] xcsdm:
The question is whether or not those with successful root keep working on an exploit... to obtain root.

There are now many new areas that need work also, custom recoveries, kernels, etc.

Just my $.02

XC
[Droid Incredible Android Development] CaptainTaco:
If you mean will it be easier to create a more simplified way of rooting, the answer is both yes and no. It makes it easier in the sense that what needs to be done is known, and creating a full script that completes the root process for you will be able to be made as each individual component of rooting is discovered, i.e. Root privs, Persistent Root, Superuser.apk install, BusyBox install. However, this is all still based on the same method of rooting, and the bigest issue at the moment is entering ADB Shell through Recovery, which no matter how easy the actual rooting process is made, that one step (entering ADB shell through Recovery) will still be required.

However, the discovery of Root does make it easier to test possible fixes and workarounds to getting ADB Recovery working consistently on all Incredible devices, as it is very touchy at the moment. That is until HTC Patches the current hole that allows us to get into adb shell through recovery, and trick the updater into allowing us to use an unsigned update.

None of my information is fact, it is my own view on it as a programmer, nor have I kept watch on the latest workings of Unrevoked teams latest discussions. So don't get mad if you disagree with me :)
[Droid Incredible Android Development] CaptainTaco:
From what I've experienced so far, it seems like HTC has A LOT of automated scripts built in to their custom Android build (Sense), that does its best to disable and overwrite our work and efforts put into rooting, hense the need to trick it into allowing an unsigned update, the need to edit permissions and pull the battery to keep your root after you complete the process, and of course my favorite, the fact that should you decide to enter Recovery after you have rooted, you will need to complete half the rooting process over again, just to get back to the shell... Bravo HTC, why is it they hate us so? Just let us enjoy our phones, Motorola did...
[Droid Incredible Android Development] ludeboy:
The funny thing is they're probably doing it to protect their Sense crap when most of us are trying to get rid of it.
[Droid Incredible Android Development] E30kid:
+1000, I want out.
[Droid Incredible Android Development] b00sted:
hell i am desperate, anyone in/near Rochester NY want to give me a hand? lol
[Droid Incredible Android Development] polo2883:
Same boat your in. Might try again later tonight. I am also from the Rochester NY area
[Droid Incredible Android Development] blw1230:
+1 to that. Anyone in the Raleigh, NC area?
[Droid Incredible Android Development] b00sted:
if you get it let me know LOL
[Droid Incredible Android Development] WoZeR:
I don't care for sense or City ID.
[Droid Incredible Android Development] dincodee:
OK i had the same problem all day trying to root yesterday and no luck. Finally got it today and its got to be the sdcard which was causing it. I tried my friends sdcard fromhis nexus one and that allowed me to get into adb while in recovery. Not sure why this is the case but its obvious some sdcards prevent you to do that.......
[Droid Incredible Android Development] ilinfinityil:
Posting my method which has worked for me now 5/5 times on my PNY 2gb card (and cuz someone asked me to post it i think)

<infinity678> run your adb shell loop, go to recovery (obviously not gonna work), take out battery, unplug usb cord, wait about 10 seconds, put battery back in, go to hboot, wait about 10 seconds, press volume down, when you press power and AS YOUR PHONE IS DOING THE SHORT VIBRATE plug in the usb cord. recovery comes back up and i get -exec "/system ..." message

edit: here's a "list version"

**this seems to be the beginning part that is needed**

boot into hboot

wait until you have menu control

press volume down to highlight recovery

get your connector ready (that plugs into the phone duh)

*READ THIS* as you press power, your phone will go to recovery mode, and the HTC screen will come up and the phone will vibrate. you want to have the connector COMPLETELY in as the vibrate stops.

recovery should come up and youll get the " - exec ..." blah blah blah error that's needed to the rest of the process

i typed up everything i did prior just in case it has any effect whatsoever. if you don't get the error then you can just start at the recovery screen

it might be hard to replicate because i'm almost certain the timing here is key, so if you can't time anything correctly then...well idk what to tell you ;)

<egghead79> I was successful using infinity's method on a 2GB PNY....probably class 2
[Droid Incredible Android Development] jonnybueno:
Thanks for that... I am backing up with titanium at this very moment!
[Droid Incredible Android Development] dephtones:
Ok, I installed the Android SDK and it successfully detects the device.

So using the method posted by someone where you go to the bootloader menu and select fastboot; after I plug in the USB cable, it comes up with an Android 1.0 device found and asks for the driver.

I am running windows XP 32bit, point it to the location where usb-driver folder is and it absolutely will not install it. Just says a sufficient driver for your device cannot be found.

Am I retarded here?
[Droid Incredible Android Development] gonella:
Hero Action

Just for curiousity, Its possible to use some steps to rooted the HTC HERO? or its totally differents.

Thanks
[Droid Incredible Android Development] stanfna:
FINALLY!!!!! I got it. I followed all the instructions on here. ALL OF THEM! :D

I tried every little trick and here is what I noticed.

- unplug your phone from your USB cable

- turn your phone on normally...like you would every day. so you can use it.

- then don't power it down...just pull the battery out

- then press the optical jotstick & power button

- then follow the rest of the instructions listed in previous posts

i think for some reason...rebooting the phone into recovery from various states does not work (it did not for me). i think when you just kill the phone from it's normal state and then boot into recovery it works (it did for me).

I hope this is helpful!!!!

a HUGE thank you to all that have contributed to this...the original ones who figured it out...the ones who have posted tips and methods and a big thanks to DiegoMejia over at http://androidforums.com for taking the time to make the videos walking us through this.

The Incredible is rooted...let the fun begin!!!:D
[Droid Incredible Android Development] b00sted:
honestly I think it is all just random, as i try everything I see posted with no change.
[Droid Incredible Android Development] onodontbescurred:
i am consistantly getting an error while in recovery

c:\sdk\tools>adb shell

* daemon not running. starting it now *

ADB server didn't ACK

*failed to start daemon *

error cannot connect to daemon

_________________________________

i am also getting

** daemon still not runningerror: cannot connect to daemon

does anyone know what I am doing wrong? or what the problem could be.
[Droid Incredible Android Development] b00sted:
I would try reinstalling the drivers.
[Droid Incredible Android Development] kntdookoo:
Dont think this has anything to do with his drivers.

Onodontbescurred why dont you check out this http://xdaforums.com/showthread.php?t=532719
[Droid Incredible Android Development] incredible_rooter:
DUDE!! You rock! This totally did it for me on the FIRST try!

I have been reading every word on this forum and the "Can't do it" forum for two days trying everything. I must have rebooted 200+ times. Nothing worked until I tried this. First TIME!!! NICE!

Thank you everyone!:D:D:D:D:D:D:D:D:D
[Droid Incredible Android Development] CaptainTaco:
Out of curiousity, I've seen several posts related to "now just have to get busy box installed". I am confused about this minorly in that wasn't that one of the first things we did? I installed it when I did the Root and Superuser portion of the program. I used an older method (extracting the busybox binary into xbin) and was just corrected on another forum by one, "adrynalyne" who informed me the busybox binary could just be placed in /system/bin or /system/xbin.

To those that did not have it installed yet just add this to your steps when rooting. After you get adb running in recovery, and get the shell going, add;

adb push busybox /sdcard/busybox
adb shell
$ su
# export PATH=$PATH:/system/bin
# cd /system/xbin (((or /system/bin I personally always use xbin)))
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# rm /sdcard/busybox

if you prefer to have the binary extracted (don't have to type "# busybox <command>" before each busybox command(not as easy to undo afterwards) do the following instead.

adb push busybox /sdcard/busybox
adb shell
$ su
# export PATH=$PATH:/system/bin
# cd /system/xbin
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# busybox --install -s /system/xbin
# rm /sdcard/busybox
[Droid Incredible Android Development] giantcrazy:
Just can't seem to get past that last step of flashing. I can get into ADB in recovery, and I've tried every bit of timing I can (simultaneously, stepping increments of a quarter second, waiting for the yellow text), and nothing.

What's holding me back is that only the 16GB card I have will even get me to recovery.
[Droid Incredible Android Development] CaptainTaco:
This happened to me when using you_eeeeeidiots method of getting ADB to work. The error occurred due to when booting into FASTBOOT (holding trackball down and turning power on). The hardware ID for the phone changes, this is why "New Device Found - Android 1.0" Comes up, and asks to install driver, if you don't manually install the driver as defined in my post (post# 455 on page 46), the daemon will shut down and restart as it can't find a way to communicate with the device found, and will do this until you reboot the phone back to your desktop where it can re-communicate. Just manually install the driver as the post entails, and try again.

A line could also be added to the android_winusb.INF similar to how we got the ADB driver to work with the Incredible earlier. I'll add what the line should be in a minute.

[EDIT]

The line to add to your android_winusb.inf is %SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

this belongs below the two lines you added previously, so the Incredible entries under [Google.NTx86] and [Google.NTamd64] should look like the following

;
;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
[Droid Incredible Android Development] sethman408:
anyone get wifi tether or barnacle working yet

barnacle no errors but dont see it

Wifi tether I can see and connect.. but get no address
[Droid Incredible Android Development] jster:
This worked for me as well first try after days of unsuccessful attempts. Thanks stanfna for the base procedures and ilinfinityil for the usb timing trick!
[Droid Incredible Android Development] ilinfinityil:
curious, what card did you both use?
[Droid Incredible Android Development] giantcrazy:
Well, just before I had to leave the house, the timing went just right and root was in play!

To those ready to give up, keep on plugging...
[Droid Incredible Android Development] mwyrick:
I have no problems using wifi tethering. It gives me a 192.168.2.100 address.

I did move the fw file onto the sdcard before installing the wifi software. See the wifi thread for version info.
[Droid Incredible Android Development] jitajt:
can someone that has this process working fine go into recovery on your phone like you would if you are rooting for the first time, while you are in recovery, go to device manager on your computer and see if it shows it as android device or if it shows it as disk drives. you can either post it here or PM me.
[Droid Incredible Android Development] incredible_rooter:
I used the stock 2GB Sandisk
[Droid Incredible Android Development] giantcrazy:
Didn't show as drives for me, said android 1.0 device
[Droid Incredible Android Development] mwyrick:
If the phone is propertly setup with ADB in recovery as it would be to proceed with the root shell,

It shows in Device Manager:

Android Phone

Android Composite ADB Interface

If is is not propertly setup, there is no device that I see for the phone.

I don't do any loops any more, I leave Device Manager open and look to see if the Android Phone ADB Interface stays. It will always blink on any reboot, if the recovery works, it will not disapear. If it shows in Device Manger while in recovery, it is ready to go.
[Droid Incredible Android Development] jitajt:
no matter what computer I use it shows up as two disk drives while in recovery, while in bootloader it shows up as android bootloader interface, and while the phone is on it shows up as Android composite ADB interface. so I think because it isn't showing up as android 1.0 or Android composite ADB interface is the reson that I cant root.
[Droid Incredible Android Development] mwyrick:
Do you have the USB Connect To PC option set to Ask or set to auto? I leave mine on Ask.

I never see the disk drive interface show up while in recovery, I either see it as ADB or nothing at all.
[Droid Incredible Android Development] GMK83:
I think thats the issue I'm having. As soon as it boots into recovery android phone goes away and never comes back