yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] qwho:
Thanks for getting back to me.

I followed the instructions for rooting, I either missed that step or (more likely) fatfingered it.

It still works, so until I can get back into adb in recovery, I will just reinstall it each boot.
[Droid Incredible Android Development] jitajt:
I installed it while in recovery but it wouldn't show up. I think I found out the reason tho, as I tried to install it after I rebooted and it kept saying that it couldn't be installed, so I had to find another one and it installed and worked just fine, but I have to reinstall it every reboot, I am going to get back in and install it the right way here soon and push the one that I know works and see what happens.

edit: went back and pushed the superuser.apk with one I know works, and no more reinstalling on reboot.
[Droid Incredible Android Development] quagmire0:
I'm fairly convinced that it's not a card issue. Over the last two days, I probably had a 15% success rate in getting the phone to connect. A lot of it seemed to be related to how Windows was treating the driver. Seems like when it was on the bootloader screen, it loaded the driver fine, then when you progressed to the recovery screen, it failed. I was usually able to connect with a combination of uninstalling the device when it appeared in device manager and re-running everything. Tried the memory card trick, but that didn't work. Used the same card throughout the process with mixed results. I think it's just a timing thing, combined with how Windows is handling the drivers.
[Droid Incredible Android Development] tinthere:
Inconsistent

I have 2 DINCs, one is mine, which I preordered. The other belongs to my wife, and she got it from Best Buy recently. I've tried my phone at least 20 times and have had no luck with the adb shell seeing the device, while my wife's phone works every time.

I tried swapping the SD cards, but my phone still doesn't work. Is there a difference in success rates based on the manufacturing date?
[Droid Incredible Android Development] krelvinaz:
Mine was a preordered phone (got Apr 28th). I have not had issues doing this since it was first posted. done it at least 13 or more times, while testing with the folks on the irc channel as they came up with new payload files.
[Droid Incredible Android Development] WoZeR:
PNY 2GB SD from walmart does not help with achieving root on my phone.
[Droid Incredible Android Development] k.electron:
so you are saying that if i remove apps, then there is a chance that i will lose out on all future htc updates since i have messed with the phone?

what about installing stuff like wifi tether? i dont want to hinder any htc updates including but not limited to 2.2 - so will rooting? deleting? installing root apps? stop me in any way from htc updates?
[Droid Incredible Android Development] mandroid2010:
Yep they made 12 dollars on me Kmart 40 on me Ill wait.:mad:
[Droid Incredible Android Development] SimonTuffGuy:
Just wanted to post up for anyone trying... My GF purchased a 4 GB PNY card a few months back to use with her camera. I figured since it was PNY, maybe it would work.

Tried every available method out there and still got nothing. Waiting for coworker to return with a 2 GB card from Walmart and we'll see how it goes. :)
[Droid Incredible Android Development] jitajt:
when they push that stuff you should be able to reflash the stock ROM that is floating around here somewhere and it will put it back to stock like it was before root, someone correct me if I am wrong.
[Droid Incredible Android Development] veli69:
What is here boot loader vs yours?
[Droid Incredible Android Development] CaptainTaco:
It's a conspiracy, PNY just wanted to sell more cards ;)
[Droid Incredible Android Development] jmdearras:
Luck of the draw.

This is starting to look like a real chance situation, where some Incredibles can be rooted, and others cannot. Mine is an early release unit, and will not root.

*sigh*

Jim
[Droid Incredible Android Development] SimonTuffGuy:
:bow: :bow: :bow:

To all of those suggesting the PNY 2 GB card..... WOW....

Second try on the card and I got it. Following the 10 minute root video from YouTube to finish it off and I'm set. Working Wifi Tether too. :)

I must've tried 200 reboots in different manners from day 1 release and NOTHING worked until now.
[Droid Incredible Android Development] phoenx06:
I got mine on the first try with my 2gb PNY card. I remember one day pre me doing the root, I made the comment that no one had mentioned using PNY cards. Glad they ended up working.
[Droid Incredible Android Development] MAD450r:
I have a question or 2 for those that rooted there INC`

Mine is rooted, but im having trouble getting the recovery to update one command keeps failing out saying file exists

ln -s /system/bin/su /system/xbin/su

thats the line that fails for me from its from the Simple HTC Droid Incredible Root.zip file I found on an earlier post ?

1.bat

adb push payload-update.zip /sdcard/update.zip

adb shell

su

export PATH=$PATH:/system/bin

cat /sdcard/Superuser.apk > /system/app/Superuser.apk

cat /sdcard/su > /system/bin/su

ln -s /system/bin/su /system/xbin/su

chmod 06755 /system/xbin/su

reboo

EDIT: I tried again this time I skipped ahead to just push the new recovery instead and it worked
[Droid Incredible Android Development] MAD450r:
Now im ready for a rom Woohoo

Im so waiting for Petes BB to be ported the Incredible but till then i'll be open to try other's see what I like as I been doing on my 3 moto droids :)
[Droid Incredible Android Development] krelvinaz:
If it says it exists, then the /system/xbin/su already exists. You can't write to an existing symbolic link. You have to remove it first.

rm /system/xbin/su
ln -s /system/bin/su /system/xbin/su
[Droid Incredible Android Development] zedomax:
Apparently

Apparently, this hack only works if you have the right phone, I believe mine doesn't work. Trust me, I've rooted my Nexus One and HTC Evo 4G but this one isn't working and I know I got the right drivers installed, even tried 5 different SD cards, tried using all the methods.

It will only work if you have one of the "luckier" phones, I believe this is some kind of hardware issue.

Also, I was talking to my Verizon customer service when activating my phone, the tech asked me if there were red Xs on the back of my phone. I guess that could be different?

Does everyone have that red Xes mark on the back of your INC? That could be another clue to whether there's differences in the INC phones.
[Droid Incredible Android Development] elborak:
While certainly possible, the evidence thus far implies that any Incredible can be rooted if you follow the right process and have a suitable microSD card.

Several folks have "given up" after trying the half-dozen microSD cards they had lying around only to be stunned when (as a last gasp) they tried their friend's card and voila!
[Droid Incredible Android Development] mmaibl2011:
The red x's are located on the back of the phone and the battery. it is to indicate any possible water damage. Apart from that im not aware of any other red x's... I have successfully rooted my incredible btw.
[Droid Incredible Android Development] bodagetta:
Here's what worked for me

My phone was a pre-order and I got it on the day it was released.

I used the method in the 10 min you-tube video

I was unable to get shell using Windows 7 32-bit with the stock Sandisk 2GB uSD card

I was unable to get shell using Windows 7 32-bit with the Walmart PNY 2GB uSD card

I was able to get shell by using OS X with the Walmart PNY 2GB uSD card (I didn't try OS X with the stock uSD card).

After I had shell, I then booted my macbook back to Windows 7 32-bit (with the phone attached) and finished the rest of the instructions in the video.

I'm using wifi tethering right now!
[Droid Incredible Android Development] rgsilvers:
HTC Incredible Root

I am a rookie with this stuff, but I rooted two of these phones pretty easily.
[Droid Incredible Android Development] vzw:
Someone that knows programing lang help?!~

Ok I am the guy that has tried everything to get root other than the buying another 2gig mem card which I should hope I wouldn't have to do that...

Anyway here is where I am hope someone can help or explain to me why I am getting what I am....

So my method is I am runing 2 cmd prompts one with loop.bat and the other I am doing the adb reboot recovery when the reboot recovery window hangs the loop.bat screen goes to a $

at this point I go to that screen and type in ctrl C to stop the loop.bat then type in ??? What?

I have tried typing in the adb shell again at that prompt but it returns:

error: protocol fault (no status)

I tried to run the 1.bat from the sdk hack pack for shell hack can't remember from whom but it runs the 3 or 4 commands i get:

error: protocol fault (no status) again...

If i do a adb devices i get it to show up shoes device and its online.... then DING nothing

I only have about a 7-10 sec window with that prompt.... then device not found again....

*SIGH*... didn't know if there was anything I could type there to get in passed shell?

when I get the $ on the screen

On a side note I have tried this with a second Dinc the first one was pre-order have had before launch official second one I got today so.... neither are working at this point it has to be the system i'm on right win7 64bit premium? I have tried this on win xp and same same... not sure what to do other than I REALLY HOPE ANOTHER EASIER METHOD COMES QUICKLY or I might hunt down the programmers at HTC and pick them off one at a time for coming up with adb Shell!~

lol jk... I wouldn't do that.... but man do I hate this SHELL!
[Droid Incredible Android Development] jitajt:
you only need to run one cmd window if you run two then there is the chance of them conflicting with each other, run the loop and once you get the exec '/system/bin/sh' failed: No such file or directory (2) - hit ctrl+c and do all the rest of the cmds from that window. follow these instructions, start from where you get the exec '/system/bin/sh' failed: No such file or directory (2) - on the page, (at end method 2) you follow that and you will have root.
[Droid Incredible Android Development] elborak:
And there's really no reason to run a looping script at all. Simply keep (assuming windows) your Device Manager open and if you get the Android Phone device when you hit the recovery screen, you hit the jackpot. Otherwise try again.
[Droid Incredible Android Development] jitajt:
yeah what he said
[Droid Incredible Android Development] Shadowmite:
updated first post with our best guess at a good way to hit the race window...
[Droid Incredible Android Development] Cameron_S:
I checked my dmesg from boot and my mmc1 is recognized at 5.04 sec into the boot. The card I am trying to use is a ScanDisk 8gb class 2 from my old BB Storm. No luck with root in recovery.
[Droid Incredible Android Development] rynosaur:
How do you check dmseg, use the "cat" command?
[Droid Incredible Android Development] Shadowmite:
when does adbd start? calculate the delay needed... then, when the white screen hits count EXACTLY that and reseat sd...
[Droid Incredible Android Development] Cameron_S:
To check dmesg you have to run the adb shell command when the device is starting up once in adb shell and you are running in the unix and th $ prompt shows up you can type the command dmesg. I am going to check right now and see when adbd starts. I will update post in a few min..

<6>[ 5.302825] mmc1: Slot status change detected (0 -> 1)
<6>[ 5.302886] mmc1: MMC_BUSCLK_PWRSAVE is enabled
<6>[ 5.303009] incrediblec_sdslot_switchvdd: Disabling SD slot power
<6>[ 5.303283] mmc1: Qualcomm MSM SDCC at 0x00000000a0400000 irq 26,115 dma 8
<6>[ 5.303314] mmc1: Platform slot type: SD
<6>[ 5.303314] mmc1: 4 bit data mode enabled
<6>[ 5.303314] mmc1: MMC clock 144000 -> 50000000 Hz, PCLK 64000000 Hz
<6>[ 5.303344] mmc1: Slot eject status = 0
<6>[ 5.303344] mmc1: Power save feature enable = 1
<6>[ 5.303344] mmc1: DM non-cached buffer at ffa05000, dma_addr 0x3b29f000
<6>[ 5.303375] mmc1: DM cmd busaddr 0x3b29f000, cmdptr busaddr 0x3b29f300

adbd doesn't start until almost 4 seconds later.

<6>[ 9.450073] warning: `adbd' uses 32-bit capabilities (legacy support in use)
[Droid Incredible Android Development] alexdw369:
Busybox Oops

I got my Incredible rooted a few minutes ago. Superuser.apk installed, WiFi tether works, but I think I goofed the install on Busybox. I was trying to use Metamorph and it's claiming that Busybox doesn't appear to be installed. It pushed to /sdcard/busybox correctly, but is there any way to install it from Better Terminal Emulator or Root Explorer, or do I absolutely HAVE to boot back into ADB shell again? It took forever, and I'm trying to avoid it, but if I must, could anybody post the bare minimal code required to get into ADB shell and install Busybox from where it resides on /sdcard/busybox?

Thanks
[Droid Incredible Android Development] Ffej5647:
I got root and installed the update all correctly and restarted but cant push anything or pull anything and have access to nothing after the update and it all seemed correct but i cant figure out how to get superuser.apk pushed do i have to get adb back in recovery for that? Please help i only was able to get adb in recovery twice and the 2nd time i was only able to get root.
[Droid Incredible Android Development] Shadowmite:
if you look you will notice that is not your sd read stamp, find the one with the size of the card, also mmc1...
[Droid Incredible Android Development] tcberg2010:
Download titanium backup from the market, select having problems and it will install busybox for you, as for metamorph, I would leave it alone until we have a good recovery so you wouldn't have a risk of bricking your phone.
[Droid Incredible Android Development] alexdw369:
We having known problems with Metamorph?
[Droid Incredible Android Development] tcberg2010:
I'm not a developer, the titanium backup fix for busybox worked for me though. A thread in general stated that we can't write to /system so it won't work. Also I would think that if you made a mistake you could brick your phone cause there's no recovery to create backups with..yet.
[Droid Incredible Android Development] jonnybueno:
Did I miss something? Did you guys disable nand protection? Cause if you didn't, then its not metamorph, its our HTC Droid incredibles. No /system write=no theme
[Droid Incredible Android Development] mrlanrat:
I tried about 8 different SD cards I had lying around. No luck on any if them. Then I got the 2gb pny from Walmart, worked on the second try and every after that.
[Droid Incredible Android Development] xm0nkey:
The Busybox you download for TiBackup won't work with any other programs that require it, as far as I understand from reading about it here. There are additional commands you need to do once you have root in recovery to get it working completely that weren't in the 10 minute root video.

Also, Root Explorer shouldn't work properly yet because we don't have full access to everything (NAND, etc) yet.
[Droid Incredible Android Development] sorphin:
gah.. i feel like such a tard... after 100000000 tries.. i got it into adb recovery twice.. and well... both times, moving the phone, i accidentally hit power (while it was sitting on reboot in the menu)... 3rd time doesn't seem to want to appear... (trying the reseating the SD card method).. none of the other methods even attempted to work for me.... ah well.

Update: well, that 3rd time came, and i didn't F it up this time.. lol. so now i'm rooted...

FYI... Hboot .77, PNY 2GB SD card, done on a Mac running 10.6.3
[Droid Incredible Android Development] zeke1988:
i just want titanium backup and maybe 2.2 if htc havent released their 2.2, yet.

question: if i run the adb shell in a loop, will it stop when i plug in my phone? or it will keep looping and looping.
[Droid Incredible Android Development] jonnybueno:
You're not gonna get titanium up and running without good Linux knowledge. It won't run without the proper setup. I know cause I don't have it running despite having root.
[Droid Incredible Android Development] junjlo:
anyone have a video or some step by step for this i have adb in cmd prompt c:\android\tools\ do i just keep turning on my inc in boot mode until something happens or do i run c:\adb shell every time i boot into boot loader? or am i just way off lol?
[Droid Incredible Android Development] krelvinaz:
I've been successful getting to the point where the update is loaded, the messae unrEVOked for Incredible etc...

I can adb shell in and use su and get a # prompt.

I even removed CityID.... however.

after I reboot, I lost root. Also, I have been unable to load Superuser.apk.

Seem to be missing some step that keeps the root. I'm guessing it is a permission thing.
[Droid Incredible Android Development] jonnybueno:
You guys should hold off for now. Other than having terminal access, without busybox and superuser whitelist setup properly, having root access will be useless for you.

If you wait for a day or two, then some nice dev will get things all nice and packaged up for you ;-)
[Droid Incredible Android Development] krelvinaz:
Makes sense..

was able to get rid of CityID though... nice.
[Droid Incredible Android Development] AceBoonKoon:
Chatroom

What is the chatroom channel on mIRC? I'd love to see what all is going on. Thanks in advance.
[Droid Incredible Android Development] Archon810:
I started coverage of this here. Rock on, unrevoked team!
[Droid Incredible Android Development] Tobias39:
Easy as pie...got it in 2 minutes.

I created a batch file that looped adb shell. I ran the batch file 3 seperate to create 3 processes all hitting the droid with the command at the same time. I got it second reboot.

followed the directions, done.

Boo yah.

PS - don't do what I did as you might brick your phone and I am not responsible, yadda..
[Droid Incredible Android Development] 1wayjonny:
I was using a similar method in my try's for rooting by swapping the sdcard at certain points, I could not get it to work and now by reading I understand where my idea went wrong or what they did better.

I took me 20-30 seconds to swap card card and I would have never made the hammering effect needed by the shell. There might have even been a check for the sdcard being removed as well with a hotswap.

Congrats and thanks for the information of your success, I will get some donations over to the team.

**EDIT **

Now we need a Amon recovery port, if I get time maybe I get this done from source if not one else gets it done. Bit busy but I will see what I can do, but flashing the recovery parition is still locked out most likely so you will have to boot any recovery as of now

Does anyone have the partition layout for the droid incredible, if so PM it to me please
[Droid Incredible Android Development] mrozzeh:
We're already working with koush to get a recovery
[Droid Incredible Android Development] MrSmoofy:
1. If I do this, could I brick? (Looks like Yes)

2. If I do this can I undo? How?

3. Are there any downsides?

4. So far it looks like it lets you "DELETE" apps that came with the phone that you don't want/need Is simplying RM'ing an app the best way to remove it or is there stuff still hanging around from it like settings/data/etc.
[Droid Incredible Android Development] vVv mDaWg:
I've been putting off signing up for this forum for awhile now due to the childish and immature conversations that have been going on over this phone.

However, I just had to sign up today to say congratulations. I've been waiting patiently for this phone to be rooted since release date. I'm glad we finally got it! Just in time for my trip too. WifiTether FTW!
[Droid Incredible Android Development] determinato_1969:
I managed to get root long enough to remove the annoying CityID app while I was still in recovery (which makes me a VERY happy panda). I lost root when I rebooted the phone, but that's fine. I know you guys will come up with a permanent method soon.

I just thank everybody involved for getting us this far!
[Droid Incredible Android Development] onodontbescurred:
will this command line work to loop adb shell command in windows on cmd prompt if im in my folder in cmd prompt

for /L %a in (1,1,750) do @(echo run %a&adb shell)
[Droid Incredible Android Development] borgey420:
In hboot is just said wrong image or no image, but when renamed to update.zip and when i tried it in recovery it started to apply it and then just errored out. But hey I don't know if you were in the IRC at the time, but some guy said he's got access to signing key :) you know what that means ahahaha and he had shadowmite give him an update.zip to sign
[Droid Incredible Android Development] krelvinaz:
Using Windows...

To be honest, you don't need to loop. I start out in shell, do the command in another cmd prompt and then when the shell exists, keep trying to get in until it errors.

I just keep pressing the up arrow and enter.
[Droid Incredible Android Development] dephtones:
Shadowmite is the king. I remember all the roms he made for the palm treos. You're awesome dude.:D
[Droid Incredible Android Development] b00sted:
great work guys.

I apparently am not intelligent enough to get it atm so I got to wait til someone tosses out some fancy bat files for me to hammer on lol
[Droid Incredible Android Development] mrchambo:
Fantastic work, guys! All your effort is much appreciated!
[Droid Incredible Android Development] Cronus1995:
<4>[ 5.728454] mmc1: host does not support reading read-only switch. assuming write-enabled

<6>[ 5.728668] mmc1: new SD card at address aaaa

<6>[ 5.738891] mmcblk1: mmc1: aaaa SU02G 1.84 GiB

<6>[ 5.739318] mmcblk1: p1

then we drop down all the way to....

<6>[ 21.490356] warning: 'adbd' uses 32-bit capabilites (legacy support in use)

so do i have a massive window, am I reading this wrong, or is something booting different about my phone over yours?

edit:

I tried a dmesg again just to pull down all of the lines in the original post. Here's what I got.

<6>[ 4.766174] mmc1: slot status change detected (0 -> 1)

<4>[ 5.265014] mmc1: host does not support reading read-only switch. assuming write-enabled

<6>[ 5.265228] mmc1: new SD card at address aaaa

<6>[ 5.279693] mmcblk1: mmc1: aaaa SU02G 1.84 GiB

<6>[ 5.280181] mmcblk1: p1

<6>[ 8.874877] warning: 'adbd' uses 32-bit capabilites (legacy support in use)
[Droid Incredible Android Development] sorphin:
I had noticed my window vary from a few seconds, to a good 10 seconds longer..
[Droid Incredible Android Development] Cronus1995:
I can't get adb shell in recovery though. So what's the deal with that? I know I have the right drivers as I've checked and double checked to make sure everything right. Still no recovery shell though.
[Droid Incredible Android Development] sorphin:
As I said in my post, I couldnt' get it w/ that window, i had to 'test the longevity' of the SD card holder's spring by 'reseating' it quite a bit, to trigger..
[Droid Incredible Android Development] dhardison:
I've tried 4 so far....

Do you happen to have a part # for that card? I'd love to try one out and get my phone rooted ;)
[Droid Incredible Android Development] k.electron:
so since no-one is correcting him, i guess hes right on that.

also, how does one flash a rom onto the phone?
[Droid Incredible Android Development] xcsdm:
Correct, you can always use one of the 2 stock ROMS in this forum to go back to a stock/non-rooted status. Then, you can do the OTA update to any new firmware.

However, keep in mind, that the hole used to root now will most likely be "fixed" or plugged with any new firmware release. As with the Moto Droid, it is probably better to wait for the custom ROMs, and eventually a rooted stock 2.2 ROM will be available here. I will wait to flash that version before I let any OTA update my phone.

XC