yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] jdmba:
Agree ... link to method?

rynosaur ... I agree ... do NOT want to break the springs on the sd card. What method does NOT require this. Can you provide a link to working instructions that do NOT involve plugging and unplugging the SD card?
[Droid Incredible Android Development] syrguy1969:
I agree...the first time I put the PNY card in I couldn't get it out...I was starting to panic until I managed to un-hitch a corner that got caught under the Inc's frame (don't know how)....close!!!

Here is a post in another forun that I found to be very well laid out and easy for even a total noobie like me to follow:

http://www.incredibleforum.com/foru...process-my-regurgitation-perm-part-added.html

I didn't have to go past the first method, but you don't need to play with the card until the third way.

P.S. The author of this said he posted it here (XDA) but I didn't see it.

http://androidforums.com/936814-post1.html

A really cool app that will do all the steps FOR you ...if it can get into recovery your golden, couldn't be easier. It does everything from downloading the needed files and placing them in the correct location (you do need to install SDK + sync yourself) to having eash step very obviously labeled on the app screen.

Didn't work for me, but I have seen people using it.

(I hope he won't mind if I attach it here for people that are not members in the other forum)
[Droid Incredible Android Development] deficitism:
Its called a-data 16gb class 6 microsd card. No effort needed. Keep your battery and SD in. Guaranteed to work within 3 tries at the max. :)
[Droid Incredible Android Development] syrguy1969:
I haven't seen this one...if the 16Gb card I got off ebay weren't corrupted, I would be upset at learning about this way after I already got root LOL!!!
[Droid Incredible Android Development] JaydenR:
Finally tried to root and did it in 10 minutes.

Thanks for making the process easier guys. Much appreciated.
[Droid Incredible Android Development] jdmba:
Still Unsure

While the promises being made over twitter a getting a little 'long in the tooth' (for X days now, imminent release), Unrevoked has been indicating (for some time) that they are almost ready to release a (slightly) simpler way to root, along with NAND fix.

Part of me thinks I should just wait for this to happen; particularly if they come up with a simpler solution or one which integrates all subsequent steps for NAND etc.
[Droid Incredible Android Development] JaydenR:
The steps are now less. Its rellatively easy when compared to how it was in the begining.
[Droid Incredible Android Development] syrguy1969:
JaydenR makes a good point, and considering the crew making the claims on Twitter are the ones we have to thank for being able to root in any way I would put a little more credence to it, so don't give up hope!!!

That being said, if your not comfortable trying the methods posted so far, unless you have a specific need for a rooted-only function, I would say wait. Stay in your comfort zone....the only reason I did it is curiosity....see if I could LOL!!!
[Droid Incredible Android Development] jdmba:
...

I would like to root just to get it out of the way; as they say on twitter that a root will still have to happen.

That said, if they are cleaning up the process, or making it more universally workable AND including all the subsequent steps (imagine having to go into recovery AGAIN), I would rather use the newer method ...

... and while I realize these guys are making great strides, making the impossible happen, working hard on the root, protecting us all, (yada yada), I would rather see their 'imminent' promises sooner rather than later, that's all; largely because if there is a hole that HTC can plug, I would just as soon be on the other side of a successful exploit :) ... and the risk of that not happening grows every day they don't release their 'imminent' steps.

The other part is that a careful monitoring of the situation here may have been a mistake. There's like 50 different threads of various lengths, all containing 'it worked' and 'it didn't work' responses. There is no really clear way other than the original posted method, and the bazillion responses to that shows that the original posted method is no panacea.

... this is why I am unsure.
[Droid Incredible Android Development] GMK83:
People need to excercise a bit of patience. The NAND unlock will be released when it is ready.
[Droid Incredible Android Development] 760hacker:
I think we're all patient...just eager. :D
[Droid Incredible Android Development] jdmba:
Not Really

That's why I made sure to include WHY I think time is the enemy ... their own posting shows that if they disclose too much, the exploits could be taken away.

I have no specific need to root (and if Verizon sent out FroYo today, I probably never would) ... but if this risk is real enough for them to put it on their page, then its real enough for me to think that faster is probably better here.
[Droid Incredible Android Development] tdavis42:
I am not really sure there is a specific method, we would have a definitive guide on [HOW TO] already if so. There are only a few constants in each persons "yay I rooted" thread. I see SD card as #1, timing #2, and radio #3. Other than those I don't see anymore similarities. So have the card out and in at this point some at others but most have this in there process, I personally had to screw with the radio's and have seen it mentioned quite a bit, and I am sure you have noticed the mention of cards. It seems the ****tier the better but not always it all comes down to card response time witch involve materials used, manufacturing standards and specifications. It simple because anyone could have stumbled upon this but odds are 1:trillion but what to do after that is where the expertise comes in with modified files and the hot swapping while validating. I bet that the hardware in your computer even makes a difference in weather you get access or not in recovery.

I always find the method for root access is so painfully obvious that it hurt. These teams and individuals that discover these exploits have got to be like "Oh **** that was easy why didn't we look there first!". I am also so glad that this place has gone through its flip out stage that it seems every section has to go through now(unfortunately). Could you imagine where we would be at if the same treatment was given to this situation that was given to the previous? Granted the last claim was pretty shady from the beginning. I am just so glad to see the community being patient and respectful so that these guys/gals feel the need to push this phone open even further. I can only imagine how long root access would have taken to achieve if this simple exploit hadn't have been found because they would still be looking for a way in and now they can work from much closer to the center back out to reverse engineer.

Anyways great job unrEVOked team and all of you keep up the good work it is always appreciated.

!

Sorry to hijack this thread but it seems to be dieing anyways. Peace /\
[Droid Incredible Android Development] m1k3-:
And it's not like a Jake Day situation where you're getting absolutely no details at all.

We've seen proof of progress of their work. There's also even more information available via IRC.
[Droid Incredible Android Development] m1k3-:
Exactly.... and they were VERY clear in the beginning that this method was HARD TO REPRODUCE and ONLY FOR PEOPLE WHO KNOW WHAT THEY'RE DOING.

Yet everyone and their momma had to try it anyway (including people who didn't even know how to install the android sdk) and like you said, 98084901238491839 threads later, you've seen what happened.

Hopefully this will all be a distant memory soon.
[Droid Incredible Android Development] JaydenR:
Since it seems that the IRC channel changed again. Can someone please PM me the new channel?
[Droid Incredible Android Development] 760hacker:
need the new IRC channel

PM to me please if you have it.
[Droid Incredible Android Development] JaydenR:
Still waiting on it myself.
[Droid Incredible Android Development] jdmba:
Agree

Agree ... any thread over 50 posts is a non-usable thread; and double-agree ... hopefully it will be over SOON :)
[Droid Incredible Android Development] larsrya8:
Does HTC or Verizon have the ability to apply OTA updates to our phones without our consent?

If 'yes': I see your point / yikes. If 'no': what are you worried about?
[Droid Incredible Android Development] TNS201:
No they can't as far as I know. But its hard to avoid clicking on those OTAs that download automatically.
[Droid Incredible Android Development] jdmba:
nope.

AAAARGH. I didn't raise this issue in their originals posting ... THEY DID. If you go to the very first post here you will see "It would be wise not to update any further if you get this, as they will most certain plug both our holes here". I would say that there is a risk.

Again, hopefully they will release their updated, simpler, and more complete method SOON.
[Droid Incredible Android Development] CaptainTaco:
meh, I disagree, this thread provided a lot of discussion during the rooting process, helped improve the original root, and get everything working (which unrEVOked has now updated their root process to do all this for you), but before that this was very useful. I agree, it is NOT a useful thread for those coming to it for the first time, it was more of a chat session than a thread. The purpose of a thread like this is to discover all the solutions, and then have other threads made that compile it all into one for those that need it. This was also done, so all in all, I believe this thread was fairly successful, and not useless at all.
[Droid Incredible Android Development] heavensblade23:
It's still ##incredibleroot, you just have to have a registered nick now.
[Droid Incredible Android Development] JaydenR:
Thanks. I'm in.
[Droid Incredible Android Development] zeiroe:
So painful to have the line I've been dying to see come up only once (during halftime on lakers game 6) only to never see it again. I trusted a script to what I should have done manually :'(

... still trying to see the "exec '/system/bin/sh' failed: No such file or directory (2)" ... just ... one ... more ... time ;)
[Droid Incredible Android Development] Gimpeh:
When trying to get ADB in recovery I get this error on XP-

Exception Processing Message c0000013 Parameters 75b6bf7c 4 75b6bf7c 75b6f7c

This is with a Kingston 4gig sd.

Any ideas?
[Droid Incredible Android Development] tdavis42:
Was that you that I smelled on fire the other day. I figured it was someone that had that line flash before them only to go away. Someone got burned!
[Droid Incredible Android Development] sylent101:
hey i dont wanna bother you or anything but im having trouble with this command too.. when i type it in it says permission denied any tips?
[Droid Incredible Android Development] ihyln:
you have to do this while in recovery
[Droid Incredible Android Development] sylent101:
Yeah... I know its just when I put that command in while in recovery. It doesn't work it says permissions denied.
[Droid Incredible Android Development] krelvinaz:
While in RECOVERY MODE....

/system/bin/rm /system/xbin/su

Then try...

/system/bin/ln -s /system/bin/su /system/xbin/su
[Droid Incredible Android Development] mims1979:
So not to brag, but ideally help, I was in the same boats as a lot of you where NOTHING worked.

So tonight I bit the bullet, ran over to walmart and purchased the $11 2g pny card came home and suprise, it didn't work. Then just like on my other 1g, 2g, 16g cards I tried another USB port and it worked perfectly with the new card. The exact method that worked was the last method mentioned in the 10 minute root video where you hold down vol-down and power over and over. I was able to get back into adb recovery twice after only 2-3 reboots each time. Superuser.apk works, removed peeps, cityid, rss feed, etc. Installed SetCPU and autostarts, all appears to be running stable and without any problems. Oddly enough, and maybe someone else knows why, I used root explorer to delete cityid, etc on the first try, after reboot all of it appeared back again. Only way to perm remove it was from adb recovery.

Hardware wise:

hboot 0.77.0000

march 23 2010, 19:36:22

Windows 7, HTC Sync installed.
[Droid Incredible Android Development] vzw:
Still no Shell access Still no New method

Wow still no easy method.... I guess when the majority of the people can do it *SIGH*.

Not sure now if I should just get the Android X that will be out next week I love my Dinc but man I need root and EVERYTHING EVERY METHOD is a big fat FAIL.

I just can't take it anymore
[Droid Incredible Android Development] CaptainTaco:
Well, perhaps I will be wrong, and the Motorola Droid Xtreme will be significantly easier to root; but judging by how close the NAND protect removal process is (supposedly) you'll probably see an easier full root on the Droid incredible long before the Droid Xtreme. But anyone's guess is as good as mine.
[Droid Incredible Android Development] vzw:
Ok will someone take a look at this for me... is there anything that would be root access in this?

C:\sdk\tools>adb push C:\sdk\tools\android.tether /sdcard/android.tether

push: C:\sdk\tools\android.tether/wireless_tether_2_0_2-pre14.apk -> /sdcard/and

roid.tether/wireless_tether_2_0_2-pre14.apk

push: C:\sdk\tools\android.tether/fw_bcm4329.bin -> /sdcard/android.tether/fw_bc

m4329.bin

2 files pushed. 0 files skipped.

1839 KB/s (559597 bytes in 0.297s)

C:\sdk\tools>adb push busybox /sdcard/busybox

cannot stat 'busybox': No such file or directory

C:\sdk\tools>adb push ota.zip /sdcard/update.zip

1751 KB/s (2465762 bytes in 1.375s)

C:\sdk\tools>adb push Superuser.apk /sdcard/Superuser.apk

cannot stat 'Superuser.apk': No such file or directory

C:\sdk\tools>adb push su /sdcard/su

cannot stat 'su': No such file or directory

I know that some of it like the SuperUser and busybox is a no but the other stuff does it show it actually pushed?
[Droid Incredible Android Development] jmdearras:
looks like you did not copy some of those files into the tools diir on your pc. the ones with a count and no error moved OK.

Jim
[Droid Incredible Android Development] greno1:
Almost there

After a few tries with an old 1GB card, I was able to follow the Unrevoked instructions on their site, including the post instructions to install fw_bcm4329.bin on the sdcard to enable tethering

I only followed these instructions, since I saw a post earlier that said these were the most up to date ones to follow, rather than the ones in this thread.

After getting through those, I downloaded and ran "Wireless Tether for Root Users" by Muller, Lemons, Buxton. When I run it, I just get a message that says "Unable to start tethering". I don't get a prompt for SU privilege.

So, I'm not sure where that leaves me. Does the tethering app need the su and SuperUser.APK files pushed to /system/app/ ? Unrevoked instructions don't include that.

I'm trying to go through the entire process again with the other instructions here to push those files, but haven't been able to get the file not found message. Still trying though!

Thanks,

-Gregg
[Droid Incredible Android Development] motempo:
root achieved

I tried getting adb working in recovery with my 16gb card that came with my Droid, couldn't get it. Went and got PNY 2gig card, didn't work. Kept screwing around with it one day and got adb with my 16gig card, but didn't have the instructions handy. So kept trying to connect again but couldn't. this was on my notebook pc running windows 7. Few days later tried it on my girl's netbook with Windows xp and 2 gig card and worked first time. Forgot to change permissions for superuser.apk so didn't have root access. Kept trying again. Tried everything. Finally tried swapping out 2gig SD card out with 16gig one while loading into recovery and got adb working with my girl's netbook. Got it right this time and now I'm rooted and good to go. I'm still want to root my girl's incredible. I want to see if there's any consistency to swapping SD cards to get adb working. Everything seems so random right now. Whoever is still trying to get adb running in recovery, keep trying. Don't give up.
[Droid Incredible Android Development] Matt Devo:
yes - without the SuperUser.apk, you have no way to elevate to root (aka su). You need to get back into adb in recovery and push the superuser.apk as per the instructions
[Droid Incredible Android Development] elborak:
Well, su doesn't go in /system/app, but Superuser.apk needs to be there. However if you are using the current payload-update.zip it handles all of that for you.

Did you perhaps download payload-update.zip a couple of days ago and not update it? As it says on the page: "You must use these files specifically. They change from time to time; when you follow these instructions, make sure that you downloaded all the files at the same time."
[Droid Incredible Android Development] Taylor08:
Guys, I've tried everything different cards, methods, phones, and different Computers with the modified drivers and HTC sync. Anyone give me any ideas? When I do adb shell in command prompt it just VI es me error device not found. .of the daemon restarting or whatever. I've been trying for days, any help would be appreciated.
[Droid Incredible Android Development] greno1:
Thanks for the replies. I'll keep trying to restart the process.

I did get all three files at the same time from the unrevoked site. Maybe they should add the SuperUser.apk insructions.
[Droid Incredible Android Development] madman34:
Anyone in Columbus, Ohio that can not get it ??

I am here in the columbus area and have rooted mine and a friend at work. I would like to try as many as I can who says that they have tried everything and can not get it, with the end purpose of proving or disproving that there are some units that just will not work. It would also be my great pleasure to help get these working if I can. Anyone can PM me if you want to give it a whirl ;-)
[Droid Incredible Android Development] Cameron_S:
They have superuser and its associated files packed into the payload already so no need to transfer them over again.
[Droid Incredible Android Development] elborak:
You don't need any Superuser.apk instructions. That's the point I was trying to make. It's all handled by the current payload-update.zip.
[Droid Incredible Android Development] vzw:
is there anyone working on a easier root process or is it just a pipe dream at this point?
[Droid Incredible Android Development] krelvinaz:
Eventually, it might be possible to just get an updated image which has this in it. But for right now, this is not hard to do for "most" people. There are some where this is still out of reach though.

Once NAND unlock is achieved however, you will only need to do this once and anyone that already has root now, will be able to make that next step without "re-rooting" the phone.

Everything is concentrating on NAND unlock now.
[Droid Incredible Android Development] rynosaur:
The newest Unrevoked Wiki has an alternate method that looks pretty easy . . . http://www.unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery
[Droid Incredible Android Development] heavensblade23:
They're going to work on it after the NAND unlock is released.
[Droid Incredible Android Development] rynosaur:
Why don't we ask Verizon to push out an OTA that turns off NAND/Security? ;)

Does anyone know if VZ/HTC are sending out remanufactured units as warranty replacements yet? That's how G1 users got off the tri-color bootloader and got an unlocked NAND.

Anyhow, I really like Binny's alternate method in this new Unrevoked wiki. No battery pulls, no fast card flipping--I got into the phone on my tenth time, which is good for more! On the last method, it took me 8 straight hours. Good work, Unrevoked, Shadowmite, and Binny!
[Droid Incredible Android Development] JaydenR:
Looking forward to nand unlock. Sound easy.
[Droid Incredible Android Development] SeanRinVA:
+Eleventy-Billion
[Droid Incredible Android Development] jitajt:
the replacement that VZW sent me for my unresponsive screen issue had the build date of Mar 23 2010, 19:36:22, same as the one I returned (as shown on the bootloader screen). in EPST it has no refurbishment date (<not available>) and manufacturers Date as 5/5/2010. so I don't think it is remanufactured they probably just had a return, set it back to stock and sent it to me.
[Droid Incredible Android Development] thenewb:
I registered just to let you guys know what finally worked for me.

I tried the 2GB PNY card from Wal-Mart and STILL was not able to get adb in recovery...

I ended up reformatting the card using FAT32 and 512 byte block sizes (not the default 4096) and it worked on the very next try.

So if you have tried everything else like I did, you can try changing the default block size to something smaller (maybe larger works too, I don't know).

I'm assuming this slows the card down even more, thereby increasing the window you have to hit adb in recovery.
[Droid Incredible Android Development] nfcrockett:
Used the sandisk 2gb that came w/ the DI,

formatted FAT32 and 512 byte,

plugged phone into usb port while already booted into the os,

entered adb reboot recovery, inserted sd card as soon as i seen the screen flicker, entered adb devices, and bam 1st try!

Never give up!
[Droid Incredible Android Development] rr12106:
I used the as card from the droid and it worked with no problem when I followed this method:

enable htc sync with phone on

turn off phone

go into bootloader

remove sd

press recovery mode

once computer chimes, insert sd

upon entering recovery, push and pull sd

insert sd when computer chimes again
[Droid Incredible Android Development] NCX Designs:
Binny's method doesn't work for me, nor does any other method so far . . .

its ridiculous how hard this is to root. . .

i'm close to giving up since it seems impossible (on mine anyway)
[Droid Incredible Android Development] andrew53517:
Don't worry, they are making an easier method I heard. So it should help all of us people who cant root!

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

Sent via the XDA Tapatalk App
[Droid Incredible Android Development] jdmba:
Please help please

I am logged in; got the recovery; followed the instructions, and it didn't say unrevoked. so i did it again and

did a whole bunch of things

Finding update packge

opening update package

verifying update package

installing update

veridying curernt system

unpacking patches

removing unneeded files

patching system fioles

symlinks and permission s...

then I got

e:multiple firmware images

e: can't store zip image

installation aborted

Now I also cant get into ADB SHELL

when I type adb shell I get

- exec '/system/bin/sh' failed: No such file or directory (2) -

but no prompt

I will try to stay logged in and everything BUT PLEASE HELP. What do I do?
[Droid Incredible Android Development] dnchattan:
Just re-push ota.zip and try again from that step.

For me, if you press enter the moment 'verifying update' appears on the screen, it works every time.. YMMV.

Once you get the unrevoked screen (success!) you can then access the device using adb shell.
[Droid Incredible Android Development] SifonX:
Le sigh. Guess I'm not as computer savvy as I thought. Or at least not Android savvy, tried every single method, including PNY card, Binny's method, and the 10-minute video. Tried reformatting the card, tried adjusting the allocation size and I'm just plain out of options.

Reason I'm posting is to say that this forum is just plain awesome. Even though all the methods I've tried didn't work, I still appreciate all the intelligence and genuine helpfulness all the posters display. Keep up the good work guys (and gals for the interest of political correctness)!

Here's hoping the unrEVOked team is able to expand the race window after NAND.
[Droid Incredible Android Development] jdmba:
Thanks

That was the key ... THANK YOU
[Droid Incredible Android Development] heavensblade23:
Release candidate for NAND unlock is being tested and refined now.