yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] syrguy1969:
Total noobie ??? here: I am assuming when you start the loop and the phone is never identified (loop never stops no matter what you do to the phone) THAT is what we see when we have a card that won't work? I just want to make sure before I start buying new cards that I am dealing with the correct issue and not something else. I do have a couple spares to try first (1Gb good card and a 16Gb corrupt one....eh you never know) before I buy the Walmart special, and that is what I have now...an endless loop ever reset.

P.S. anyone else have all their ringtones get messed up or reset to stock when removing/replacing the card? Seems to happen on + off for me!

Thanks all!!
[Droid Incredible Android Development] 0mie:
On my third Incredible after I hold down+power device manager detects the phone, but Android 1.0 is missing. When I point to the sdk folder to install the driver it tells me it can't...when full boot mode it shows for ADB Devices MyHTC...should I remove HTC Sync? I had root working on other devices, but now it won't work :(
[Droid Incredible Android Development] CaptainTaco:
You could just force it to use it. Instead of choosing "browse a folder on my hard disk" go to Device manager, right click "android 1.0", select "update driver", chose "Browse my computer for a Driver Software", then "Let me pick from a list of device drivers on my computer", then choose "All Devices", select "Have Disk", and select the "android_winusb.inf" located in your aforementioned folder.
[Droid Incredible Android Development] 0mie:
Yea, I did that...selected Android ADB Interface and once I hit recovery the device vanishes :(
[Droid Incredible Android Development] CaptainTaco:
Ah, I misunderstood your issue. I was referring to the

Part.
[Droid Incredible Android Development] Blades:
I'm not very skilled with Android, nor do I own an Incredible. Are there any files that Android looks for on the SD card when it boots up? Better put, what does it poll the sd card for? If there is a relatively benign (safe) file that it looks for, you could try to rename a large (1GB) file to that file name in order to slow down this boot process. Has anyone put a large amount of small garbage files among the files they needed to flash? I doubt it scans all files, so that probably won't work.

If its not an issue with a desired slow load time, perhaps you could tailor a renamed garbage file of a specific size to achieve the delay mentioned in the first post?

Heres to hoping recovery mode scans xyz files or ALL files on the SDcard.. that'd be nice.. Thats what you need to slow down to keep that ADB 'connect window' open.. from what I understand, after that read command on the SD card is made, adb closes?
[Droid Incredible Android Development] aaronjb:
Thanks for this post. After unsuccessfully setting permanent root my first go-round, I was able to get shell in recovery again and do it the *right* way this time.

Thanks!
[Droid Incredible Android Development] 0mie:
It worked few times before, now it won't work at all :(

I am deleting all HTC drivers and starting from scratch. Maybe that will work for me =/
[Droid Incredible Android Development] k.electron:
personally i am quite satisfied with htc roms on this device, and i would flash custom only once htc stops working with the device.

now, one question i have is, once the phone is rooted, and i install/uninstall some crap, does that mean that i cannot get htc ota updates until i revert back to a stock rom? or will i still keep getting them, just not for the apps that i uninstalled?
[Droid Incredible Android Development] 0mie:
Android Phone ADB Interterface shows up while in recovery, but adb shell still shows error:device not found =/

It worked other times, why is it being so difficult now? :(
[Droid Incredible Android Development] CaptainTaco:
hmmm, did you try using a Whiffle-ball bat? It works for insubordinate people, why not phones?
[Droid Incredible Android Development] rynosaur:
You probably have an HBOOT 79 Incredible in your hand. Run the RUU PB31IMG.zip from the Downgrade thread, but know it will blank all userdata and apps.
[Droid Incredible Android Development] rynosaur:
You're exactly right. I used a funky FAT32 partition and the PB31IMG.zip, which stalled Bootloader's check on the card as well as Recovery's check on the card. While I doubt file load is a deciding factor, I'd bet formatting is, as time is definitely a factor. Others have had success with cards partitioned in linux with ext4 fs. Problem is, you need a FAT32 partition on the card too because as soon as adb shell is achieved you have to push files to keep root in Android OS.
[Droid Incredible Android Development] EPayne123:
Important Question...

When I installed SDK I went ahead and downloaded the things that many people "Fetch Failed" and it has the 2.2 platform... if we are rooted would that mean than we can run 2.2? If so, would it be a pain, would it be just a click or what?
[Droid Incredible Android Development] rynosaur:
API8/2.2 addition to the SDK is just a add-on pack to allow developers to write programs for Froyo correctly. Others are working on a port, you can be sure.
[Droid Incredible Android Development] jdmba:
....

I am starting to think that I am not going to try to root my Incredible. It seems like 1/2 a solution without NAND; and all I really want is v2.2 anyway, which IS going to be released, albeit late in the year.
[Droid Incredible Android Development] jmdearras:
Can't get ADB again!

Got it once, loaded the root essentials, but forgot busybox. It works fine, except I want to load busybox, too. But I have put 3x the time and effort into trying to get adb again, and cannot do it. Frustraiting.:confused:
[Droid Incredible Android Development] jmdearras:
Got it on my last try!

I decided to try one more time today, with my normal microsd card, using the rapid remove/insert method that has never worked for me. The triangle ! came up and I figured it had failed AGAIN, but in a couple of seconds, that wonderful directory not found error started going past in the adb window.

Got busybox installed this time, all is well!

:D
[Droid Incredible Android Development] evilone1969:
Ive tried looking for an answer, if its been posted alread sorry :(

ok after days of trying to root, diff sdcards/different ways to boot etc i finally got it working by using a diff usb plug on my cpu,

when i start doing the post stuff i

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

the last 2 lines do not work for me, says permission denied on the

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

then no such file or directory on the line:

chmod 06755 /system/xbin/su

thnx for your help in advance :)
[Droid Incredible Android Development] blakestiffler:
ok so i rooted my incredible, i went into /system/app and started deleting stuff like vvm, city app, footprints etc. But they immediately come back!!! anyone know why??????
[Droid Incredible Android Development] blakestiffler:
for those of you still struggling to get adb in recovery, i struggled for days on different o/s and sd cards, then i installed windows 7 and it worked first try following the 10 minute video. xp, vista, and mac osx all failed for me.
[Droid Incredible Android Development] jitajt:
I follow this every time after i get to the # prompt.

all you have to do is: rm /system/xbin/su

then: ln -s /system/bin/su /system/xbin/su and it should work.
[Droid Incredible Android Development] evilone1969:
got it finally!!! ty :)

for those still having problems maybe try connecting to a diff usb port? .. thats what worked for me :)
[Droid Incredible Android Development] sdorn77:
what does the part starting with export Path do? I didn't do that when I rooted my phone. It wasn't in the instructions on the wiki. Did I miss something? Everything seems to be working correctly. I have root and can use wifi tether. It sticks when I reboot the phone.
[Droid Incredible Android Development] rynosaur:
the export command points the file system to /system/bin as a part of your command path so you don't have to navigate to where the commands are stored everytime you want to use them.
[Droid Incredible Android Development] madman34:
Coincidence

Thats all it was for you, sorry ;-) the phone will go into recovery without loop or even the drivers loaded up if the timing is right.
[Droid Incredible Android Development] blakestiffler:
is anyone else having trouble deleting system apps after rooted?
[Droid Incredible Android Development] jmdearras:
you can only delete them in recovery mode, for the moment. The /system folder is locked, otherwise.
[Droid Incredible Android Development] jmdearras:
It's how you hold your tongue. ;)
[Droid Incredible Android Development] CaptainTaco:
In resposne to the above, you don't need to do this anymore, just run the newest payload-update.zip through the original wiki

Not sure if anyone noticed that the wiki (posted in the original post on this thread) was updated with the correct Superuser.apk. as well the "payload-update.zip" was updated to correctly apply perma root, most of the information is this thread is now not needed as long as you download the newer files from the wiki, and follow its process. As a matter of fact, if you follow the instructions on unrevoked's wiki, and push busybox to your SD card, the payload-update.zip now automates everything, no need for this thread anymore.

The newest payload-update.zip does all of these things for you automatically.

-Roots phone with Perma Root (persistent on reboot)

-Installs correct Superuser.apk

-Installs BusyBox

and by following post install instructions on there, installs WifiTether

So while all everyones hard work on this forum thread is well appreciated, please don't feel the need to run all of the command snippets we've all come up with throughout the thread, they are now all automated in the original process. (Thanks Unrevoked, I hope some of the items in this thread helped)

Link in case anyone is lazy enough to not want to hit "first page" ;)

http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery

EDIT: Perhaps the thread author could update the original post letting people know this fact so people don't go crazy reading through and running all the commands listed throughout this thread.?
[Droid Incredible Android Development] evilone1969:
ahhh tyvm for the update 8) was unaware of this 8)
[Droid Incredible Android Development] jessescfan:
This is how I rooted my INC, I believe the FAT32 format is the reason it works. Just my opinion.
[Droid Incredible Android Development] j1000:
Post #820 worked for me after days of trying. Thanks Alot.

Only got it to work once installed everything but wireless tether but now I know it can be done.
[Droid Incredible Android Development] EPayne123:
Thanks a bunch Ryno... that clears it up. Can't wait until we figure out how to exactly get Froyo 2.2!
[Droid Incredible Android Development] jdmba:
Answer!

Since NAND is still locked down tight, I suspect the answer to your question is ... wait for Verizon to deploy it.
[Droid Incredible Android Development] EPayne123:
I hear that... we(Incredible users) are supposed to be getting it in late October-mid November but Vanilla will be coming out in August... apparently the delay is due to Sense UI
[Droid Incredible Android Development] jdmba:
hmmm

Well unless they can get NAND unlocked as well, there won't be cooked ROM's; and while they came up with this 1/4 of 1/2 of a root pretty quick, I suspect that the rest may not come so soon, particularly if to get us this far you have to go thru machinations which launch a 823 post thread and a ton of other helper threads.

I am actually concerned that this "1/2-___ed" root may be incompatible with their ultimate full root. As I read more and more on the topic, I think I want to stay far away from the root at this point.
[Droid Incredible Android Development] thawkth:
Incompatible how? It should be trivial to unroot at this point...

Whether you write a script or new payload or just flash the original Rom...I don't see why this root should be avoided if someone wants it!
[Droid Incredible Android Development] EPayne123:
Even if it is in the way of full root it is actually QUITE simple to "un"root the Incredible... have done it to my phone. Rooted, then "un"rooted then went right back in and "re"rooted.
[Droid Incredible Android Development] CaptainTaco:
I have to agree with others.

A) With the current root, there will be no "incompatibility, the "full" root you speak of will still need the things we've done here, and even if the SU is updated, or Superuser.apk is update it will be as simple as, the new root process would overwrite this one.

B) It's soooo immensely trivial to unroot right now, it's literally a matter of wiping the phone to factory. The only difference is you would still have lost any apps you deleted. In which case, run an RUU, they're out there, and they'll return your phone to factory everything (including apps). They arn't even difficult to run, they might as well be called installers.

C) This isn't a 1/2 root, this the phone is rooted, by definition we are fully rooted. What it isn't is NAND protectionless, and when someone cracks that, I'm going to cringe when they call it "fully rooted". The definition of Rooted is to have the ability to act on behalf of Root, we have that... A "whoami" as su will return "whoami = root/uid0" aka Root. The removing of the NAND protection is removing a lockdown on the system partition set in place when the phone is running. Truly has nothing to do with "root" at that point. Sorry, just get annoyed when things are called something they're not

.... PIN number anyone? ... ;)

EDIT: and D) 720 of these 800 odd posts are "I can't get ADB shell working so I can follow the instructions to root." It didn't take 800 odd posts to root, it took the hard workings of Unrevoked team, and some (few) of the posts here worked out some kinks we all found, which unrevoked would/did probably find on their own, and updated their wiki with them.
[Droid Incredible Android Development] m1k3-:
Rumor has it they're close to unlocking NAND.
[Droid Incredible Android Development] heavensblade23:
Where'd you hear that? I hope we're not waiting on the random guy that said he might be able to get a test rom.

Also, why can't we flash custom roms right now? We can load a working custom recovery to flash a rom from, even if the recovery itself is only temporary.
[Droid Incredible Android Development] c1rcaa:
Its on their twitter, it says "The unrevoked USB bootloader NAND unlock for Incredible/EVO is getting close. We've been testing it with a small group and it works well!"

They don't have an ETA yet, but they are "close" seems that they are just smoothing out the process.
[Droid Incredible Android Development] daddymacbuff:
http://twitter.com/unrevoked

latest update

Our NAND unlock will flash a custom recovery that gives you full control over the device. You'll need to root once via adb.
[Droid Incredible Android Development] heavensblade23:
Thank you, made my day. Unfortunately there's still the problem of not everyone being able to get into ADB. Fortunately, I am. :D
[Droid Incredible Android Development] JaydenR:
Does root explorer work for removing system apks? after root.
[Droid Incredible Android Development] dhardison:
Thank you for all the hard work :)
[Droid Incredible Android Development] TNS201:
not yet.........
[Droid Incredible Android Development] shoman24v:
I'm so pumped, I can't wait to get the official release of 2.2 on this *****.

if we are running vanilla 2.2 when it's released will get get OTA updates?
[Droid Incredible Android Development] ludeboy:
Screw OTA updates. Custom ROMs are way better. Plus, no Sense! I'm using my Droid until we get some custom ROMs on the DI.
[Droid Incredible Android Development] gripper4hire:
I've been playing with trying to get root for a couple of days with no luck.

I am starting to think this isn't all consistent, and people are grabbing at straws with SD Card timings, etc.

If we can compare others who can get root with those of use that can't, maybe that would help crack this puppy.

First, my system specs: Win7 x64, HTC Sync installed, Android SDK installed.

Here are my observations / questions:

1. When I enter recovery mode, I don't have the "Android ADB Composite Interface" (or "My HTC", if you use the HTC driver), nor a category for "Android Phone". The computer only detects two "HTC Android Phone USB Device" entries as disk drives, under a generic USB Composite device.

I've been trying for a few days rebooting in recovery mode (adb reboot recovery) and do not get the ADB device.

I assume those that are able to get root, and have been able to repo it regularly have the "Android Phone" category, and either a "My HTC" or "Android ADB Composite Interface" listed. For those that have successfully rooted the phone, do you have the disk drives in addition to the ADB device? And do they all pop up in Device Manager at the same time? (An easy way to check this would be to open Device Manager, and show device by connection, and find the USB Host controller path, and watch it as the device enumerates... This would be under ACPI System/PCI Bus/USB Host Controller (after finding out which one)/USB Root Hub/USB Composite Device/Android Composite ADB Interface or My HTC, and USB Mass Storage Device)

2. When I hold the optical joystick down, and press power to power-on the phone, that loads the white Android bootloader...

My bootloader version info (at the top of the white screen) is:

HBOOT-0.79.0000

MICROP-0417

TOUCH PANEL-ATMEL224_16ab

RADIO-1.00.03.04.06

May 14 2010,14:15:44

The time stamp of my bootloader is rather new... May 14th, compared to the first large batch of Incredible's that shipped in early May before they sold out (I assume they are time stamped sometime in April or eariler).

For those that rooted successfully, do you have an earlier date? And for those that can't root... do you have a later date?

I am wondering if HTC already patched this "hole", and maybe that is why some of us can't root. :confused:

-gripper
[Droid Incredible Android Development] wpbear:
ERROR: [1] Segmentation fault /system/bin/su

After succesful adb push payload.... and Unrevoked shows on device screen I try to remove CityID and after:

you@host$ adb shell

$ /system/bin/su

I get the Segmentation fault....what should I do?

EDIT: This worked to remove CityID

you@host$ adb shell

$ su

# /system/bin/rm /system/app/CityID.apk
[Droid Incredible Android Development] syrguy1969:
OK...I got a PNY card and got root !!! One problem though....busy box doesn't seem to take. I have superuser and I installed a few apps requiring root (LED flashlight, wifi and add-free), but when trying to run Titanium backup I get an error that it can't find root access because busy box isn't there.

I followed all the steps, can't find the problem.....any help?
[Droid Incredible Android Development] EPayne123:
Ok... after moving SDK folder to C: drive root and installing HTC Sync and SDK, you must go ahead and re-open SDK and look under Installed Packages". If it does not say that USB Driver Revision 3 is installed then you MUST download it. To do this, open SDK, go to "Available Packages", click on the "+" next to the only package available and scroll down to the bottom and the last one should be UBS Driver Revision 3, place a check mark next to it and press "Install Selected Packages". After this, then close SDK and run get ADB shell running(not in recovery) by going to command prompt and typing cd c:/... cd sdk... cd tools... adb shell(EVERYTHING LOWERCASE!)

1. Go ahead and plug in or replug your phone into the USB chord and wait 20 seconds or until the bubble for the drivers near the taskbar disappears.

2. Open device manager(Start, Right click "My Computer" and select properties). Once in Device Manager, the first one in DM should be ADB and expand that choice and if their are any devices being shown under the ADB choice then you're good. Now, this is what you are to need to see after you are at the "!" screen in reboot.

3. Before you turn your phone off unplug the phone from USB.

4. With phone unplugged and still on go ahead and go to CMD.exe, execute ADB shell. cd c:/...cd sdk... cd tools... adb shell(EVERYTHING IN LOWER CASE!)... if it says Out Of Date or anything else then you are fine as long as in the end it says Running successfully or something along those lines. Do not start loop or anything.

5. Reboot phone with Optical Pad. Select BootLoader. Select Recovery from next menu. Once on the "!" screen go ahead and check DM and after 20 if it says has a device still under the ADB Devices menu then you WILL connect no matter how long you take. Now while you are on the "!" it will disappear and reappear once or twice but what you are looking for it to DM is blink and then stay there for 3-4 secondary and once it does then you are golden.

Throughout the steps of 1-5 it will disappear a time or 2 but you don't have pay attention to it until you are literally at the "!" screen seriously. I guarantee this woo confuse many people with the way I have mentioned steps above so if you are having trouble with a step or 2 just post and I will answer if with an answer better explaining the step that you are having trouble with... it should work because I have done this on 3 Incredible and has worked within first 6 at the most. The reason it could take a couple of tries is because there is a race and basically the hole we are waiting for sends an Open command and then a Close command and overtime we do this we are waiting for the Open command to take longer to loss than the Close command which happens mprethan you think DP go to town and let me know if it helps you and also let me know if nothing...
[Droid Incredible Android Development] scott8357:
Which LED Flashlight did you install? the one thats still WIP does not require root...Is there a new fully functional one out now that does?
[Droid Incredible Android Development] elborak:
use lamppu
[Droid Incredible Android Development] jitajt:
you need to hit "problems?" in titanium backup then "yes do it" and it will download and install another version of busy box. after it downloads and installs it, restart titanium and it should be fine.
[Droid Incredible Android Development] pozer69:
Wow, this form has really died down. Any update on an easier way to root or at least what the issue at hand is for so many people (sd cards?)
[Droid Incredible Android Development] syrguy1969:
Beat me to it, but elborak is correct, that is the one...and it works GREAT!!! (P.S. Did we mention it is free???)

You the man!!! Thanks a lot. I knew I saw something like that somewhere, but I couldn't track it down again after it happened to me. I was starting to think I made a mistake in root, but it works great now!!!!
[Droid Incredible Android Development] syrguy1969:
I can't speak for everyone, but like a lot of others I have seen the key for me seemed to be getting the PNY card (2Gb for $10 at Best Buy or Walmart). After a couple nights I broke down + purchased one and within the first 2-3 tries got it rooted!!!
[Droid Incredible Android Development] pozer69:
What

What technic did you use to achieve root? There are so many different ways now, i wonder if it is card specific.
[Droid Incredible Android Development] EPayne123:
I didn't have to bother to get another SD Card because around 4 days ago I got it with as 2Gb Kingston.
[Droid Incredible Android Development] syrguy1969:
I used eeeeeediot's directions:

I don't want to take up space posting them all, but basically just starting loop and reseting the device in recovery until it is recognized...took 2-3 tries last night.
[Droid Incredible Android Development] rynosaur:
+1 I am a big fan of the no battery pull/no sdcard-slamming method, I like not wearing the hardware prematurely :) It means having more patient and just using up vol+power, soft reset followed by adb reboot recovery after the first screen.