yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] sydtrakked:
I tried forcing it to use the .inf file to get "Android Composite ADB Interface" by going to device manager > disk drives > HTC Android Phone USB Device > Update Driver Software > browse computer > let me pick... > Have Disk... > then browse for .inf file

It gives me this message:

"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems ."

I'm pretty new to all this but to me it seems it either you can't use the driver with 64-bit (both successful roots were 32bit) or there is an issue with the .inf file...

I could be wrong... like I said... "I'm new here"... but just a thought...
[Droid Eris Android Development] HanSolo2012:
i had the same issue with xp 64.... ended up just dual booting 7 and it installed just fine on win 7 64bit about to go pick up that PNY card from my local best buy only 10 bucks
[Droid Eris Android Development] bpick:
Is it at all possible to for someone to post an ini file that has successfully installed the drive. Mine has no 64 bit section and I have redownloaded. Just may make it easier for someone.
[Droid Eris Android Development] Hairston:
Wow, just woke up. Kinda sucks someone else hasn't gotten it yet. Weird. I know it's tough, but what's with the flaming? Anyway, please, enough with the flaming. Why would anyone go through this trouble if this didn't work? I'm trying to help as much as I can, but if the lying accusations keep up I'm quietly out of here. I guess I could post a video too of the hboot version as well as it booting up into Amon recovery but come on.

I've been reading some of the posts that have to do with the Windows drivers. If you boot the phone in normal mode, turn on USB debugging, and still can't get the "Android Composite ADB Interface" to come up in device manager, it will never show in recovery. That should be priority one. Some of you may have already gotten it but would have never known because the drivers were screwed up. Again, I'm no expert, but I think this would be obvious.

I live in the Buffalo, NY area, specifically Orchard Park. If anyone is looking for hands-on help maybe we could make a meet at the local Starbucks or something with a laptop. Coffee is on you however if we can get your phone successfully rooted. :)
[Droid Eris Android Development] cptkrush:
so i figured i'd take a crack at it and while the loop is going the device isn't being found, i installed the adb driver and changed the inf file. Also, fastboot usb has no recovery option, what am i doing wrong?

win7 32

im on leak 2 if that makes any difference.

and another edit: the device manager is showing it as My HTC while in usb debugging mode.

Edit for fix: Remove My HTC driver by right clicking the device and uninstalling, make sure you check the box marked "delete driver" then browse to the driver_usb folder in your sdk and if you have edited the inf file it should come up with a driver, tell windows to piss off when it tells you that it isnt signed and install away. Device is showing "Android Composite ADB Interface" now. hope that can help someone.
[Droid Eris Android Development] HanSolo2012:
OP? Im in west seneca about to hit up best buy off south western ill deff contact you if i dont get it to work

Also where is wally world is it a store around here or a online place
[Droid Eris Android Development] homaygfresh2000:
Wal-mart :)
[Droid Eris Android Development] hallstevenson:
I've seen no (real) flaming or accusations. What I've seen is many, many people who've been unsuccessful at doing the same steps as dc_striker. Sorry, but it's not looking promising...
[Droid Eris Android Development] Hairston:
Lol, cool. There is a Starbucks at McKinley Mall.

If you are looking to buy an SD card, go to the new Walmart on Rt 5, that's where I got my $10 PNY 2GB card. Look in the digital camera section. The SD cards are actually in two places in the store, so don't let the clerk tell you they don't carry 2GB cards.
[Droid Eris Android Development] devlp1213:
ppl going into fastboot usb:

the reason we are going here is to get the computer to see the Android Composite ADB Interface" at this stage. a step left out in the directions are you have to go bac kto hboot then hit recovery :)

Also i'm on win7 x64 and the drivers went tru on mine no prob i'll try to post the file real fast

USB DRIVER I'M USING
[Droid Eris Android Development] cptkrush:
ok, i fixed my driver issue, but the loop isnt picking up the device. any tips?
[Droid Eris Android Development] devlp1213:
i'm stuck in the same spot, my device manager in both in win7 x64 and xp pro x86 will pick up the device while its on with the "Android Composite ADB Interface", both pick it up in Fastboot with the "Android ADB Interface", and neither get anyhitng in recovery..... Anyone think puting the driver file on the sd card might help? Cuz while its in recovery we can get it to read as a mass storge device, so maybe if it read the drives off the sd?.. iunno maybe just wishful thinking there =P
[Droid Eris Android Development] Wongidool:
Can you tell us -exactly- when you popped the card in? I'm sure that the timing of everything is key for this proccess and having that information is key.

Any helpful suggestions besides using the ini file modification to accomplish this? Just noticed that the ADB Composite isnt showing up
[Droid Eris Android Development] cptkrush:
While in fastboot, what should the device manager show my device as, it comes up as Android Bootloader Interface

the loop is picking up the phone while on and in usb debugging, but not while in fastboot
[Droid Eris Android Development] devlp1213:
this is where i'm at :(
[Droid Eris Android Development] cptkrush:
im installing the RUU right now to see if that makes a difference, im on leak 2.
[Droid Eris Android Development] thenestor:
You should have done that anyway! You'll get working pictures in Gmail, and all copy-protected apps back in the Android market.
[Droid Eris Android Development] HanSolo2012:
http://www.bestbuy.com/site/PNY+-+2...1&skuId=8351623&st=sd card&contract_desc=null

trying to use that card i just bought not working so far
[Droid Eris Android Development] cptkrush:
installing ruu did not help, the device is still not found while looping in fastboot. i tried getting the pc to install the ADB drivers for boot mode but it wouldn't take them.
[Droid Eris Android Development] HanSolo2012:
can you link the one you got please maybe off their site
[Droid Eris Android Development] pkopalek:
I'd love to see this work, for the sake of seeing it work. If I get a phone redeemed on Insurance or Warranty for one reason or another, I'll surely need to do this.

I'm on the West Seneca/Lackawanna border at Ridge and Abbott Rd.

I'd love to get hold of a non-root Eris to try it. Unfortunately, if this happens as a result of my phone being damaged, I will be a lot more frantic to do so!
[Droid Eris Android Development] xtreme3737:
I have been attempting this for the past 2 days. I am currently on the V3 leak. I will be heading to Walmart in a bit to pick up a PNY and give it a go before I update to the RUU. What OS did you guys use to achieve this? I am using Win XP SP3. I will also give it a shot on Linux.
[Droid Eris Android Development] HanSolo2012:
so far not working and beginning to screw up my sd card slot

cards not coming have to use a tool

about 100th try
[Droid Eris Android Development] bftb0:
pkopalek,

You can test it on a root phone without worries.

How? Just use fastboot to flash the recovery.img file from any of the leak ROMs (V1, V2, V3). When you are done, just flash Amon_RA's recovery back in place. You can even leave your normal OS in place in case you need to use your phone - uh, as a phone (with your goodies on it).

After all, the thing that is being tested is the recovery image; not the bootloader, and not the OS.

The three "live" possibilities (bootloader, recovery, or OS) communicate through the BCB and also (sometimes - for OTAs) through /cache. But there is really no reason to believe the thing being tested has any dependency on the OS or the bootloader.

That's my story and I'm sticking to it.

bftb0

PS the only downside to doing this is that a lot of the dev ROMs don't seem to have a genuine version of "reboot" on them, so you can't soft-reboot out of the OS with a "adb wait-for-device shell reboot recovery".
[Droid Eris Android Development] Hairston:
Another Western New Yorker! Greetings!

Paul, I've seen you post on other android forums so I know you are helpful and knowledgable. Didn't know you were from Buffalo. If you do get hold of a 1.49 S-ON Eris let's get together and meet. Maybe the both of us can nail down some required steps to try to get rid of more of the luck factor. I did it once and I can hopefully do it again. If anything I can show you my phone with the 1.49 HBOOT to further confirm that this does indeed work.
[Droid Eris Android Development] HanSolo2012:
how did you format this what program?

is this the card you got

http://www.walmart.com/ip/PNY-2GB-microSD-Memory-Card/10242121

or

http://www.walmart.com/ip/PNY-2GB-Class-4-microSD-Memory-Card/14151210
[Droid Eris Android Development] mortymouse:
Yes, me too. Stuck at step 7. Strange as my device is listed under portable devices, and its called WPD Filesystem Volume Driver.

When not in recovery and just mounted, I can see the device in adb, but when I go into recovery no matter with our without sdcard it will not show. I have tried with and without loop, with and without sd card, etc.
[Droid Eris Android Development] Hairston:
No idea if this made any difference whatsoever, I was following the Incredible root thread and someone mentioned formatting the SD card with a non-standard allocation size to try to trip up recovery. I took the micro SD card put it in it's SD card standard size adapter and put it in the card reader of my computer. From there I went into Disk Management and formatted for FAT32 with a 512byte allocation size. My card was blank too on my successful attempt.

Again, this might be snake oil, who knows.
[Droid Eris Android Development] HanSolo2012:
kk i linked some cards on the last page let me know which one you got if it was one of the 2
[Droid Eris Android Development] Hairston:
I think it was the first one. I don't remember the packaging saying Class 4 and I know it was only $9.95 and not $14. I don't have it at work with me here to check.

I only bought that card because I didn't want to accidentally hose my prized 16GB Class 6. I was just looking for the cheapest card out there in case I broke it.

EDIT: Defiinitely the first one which is made by PNY. The other one is tagged as an HP.
[Droid Eris Android Development] mam4983:
Not sure if this has any relevance here, but I have a Nexus 1 and my wife has an Eris. When I was attempting to get my pc to recognize my Nexus 1, one of the suggestions was for me to download and install the PDANet drivers. This worked for getting my N1 to show up under adb devices. I don't have the Eris with me so I can't try, but maybe someone could give that a shot.
[Droid Eris Android Development] BrownEye02:
Ok I understand this but I still cant get my computer to see my phone in fastboot. On a normal boot my phone is seen by adb. But no matter what driver I use even if its the same driver I use in a normal boot, in fastboot IT WONT SEE IT! WHAT AM I DOING WRONG?:confused:
[Droid Eris Android Development] Cyostrife:
Can you please post a detailed video of what you did? I mean like really detailed i was up since six am yesterday trying this and still nothing.. i would really appreciate some more detail..
[Droid Eris Android Development] Romparoo:
So, are you:

A. Calling BS.

B. Saying it's not possible.

C. Saying it's 1 in a 1,000,000,000 shot chance.

BTW, excellent information. I haven't a clue how to apply/perform this they way you do. The only way I know how to root is by all the great step by step, 1 2 3, instructions ya'll provide.
[Droid Eris Android Development] bftb0:
Well, for the purpose of this particular exploit, you don't need a fastboot driver anyway; if you have the ADB driver working, that is all that is needed (for this exploit). Not that you are going to get it working anyway - essentially nobody is getting it to work. (Or, let's just say that there are far more that fail than win at the moment.)

You might want the fastboot driver for future purposes, but it has no relevance in the context of this particular thread.

I know why people look for help with Windows driver issues on phone websites - they figure someone might have the same experience, and therefore quick insight into solving a particular problem. But frankly, the best place to find out about how to troubleshoot a Windows driver problem is on a Microsoft site, not here.

I'm not an expert in things Microsoft. I have had some detailed experience with Xp SP2 and USB. It is possible (in Xp) to delete the entire USB stack configuration to start from scratch without reloading the OS (even if the machine uses a USB keyboard!), but it's very tricky - you need to delete all the clients first, and then all the root hubs in the correct order, etc. Who knows if that method changed in Vista and Win 7, and x32 vs. x64 adds yet another wrinkle).

One of the things you might want to research is how to make your version of Windows display ALL Drivers - not just the ones that are currently active. Under normal circumstances, Windows won't display inactive drivers - so it is impossible, for instance, to remove a driver bound to the fastboot identifier unless you have the phone attached to the PC and in fastboot mode. There's some environment variables (and a toggle in the device manager) in Xp, but I have no idea if the same methods are used for Vista/Win7

The frustration that Windows users have over driver problems is nothing new. MS puts so much effort into making driver installs "easy, helpful, and idiot proof" that when a problem finally does appear somewhere, there is a thicket of logic (and obfuscation of details) around the driver install process that actually makes troubleshooting harder than if the driver install process exposed more "details".

good luck
[Droid Eris Android Development] thisismyanonymousaccount:
I think he is saying to stop f*cking around with windows drivers because it doesn't matter. Get adb to see the phone when it is booted and USB debugging is on and you are all set. On that note, after reading both the slide and the incredible threads, neither does the sd card.

best of luck.
[Droid Eris Android Development] BrownEye02:
Thank you thats all I wanted to know. See I thought that in order for adb to see my phone in recovery it had to be able to see it in fastboot. THANK YOU!

But again I will keep trying to see if I can win the one of those golden tickets.

And if I get it I will post VERY detailed instructions on how I did it.
[Droid Eris Android Development] bftb0:
Nope. I have my doubts, but race conditions totally suck a$$ at being repeatable in the first place, so it's hard to prove anything one way or another.

I was trying to convince people to stop wrecking their driver setups that were already working. In retrospect, I should have also told people that are trying to resolve a driver problem that they should not try to resolve a driver problem AND run the exploit at the same time - that's idiotic.

Nope. Just saying (in that last bit about USB sniffing) that not only have I never won a race, but I've never even seen the ADB interface come alive on the USB bus (that I am using) during a recovery boot.

Really only one way to find out what the current odds are would get everybody to estimate the total number of trials they have made. Total all those trials up - whatever_number_that_is, and then the odds would have an upper bound of

"two in whatever_number_that_is".

bftb0.
[Droid Eris Android Development] Wongidool:
There was some talk earlier that you had to have your phone popping up under the composite ADB interface in the device manager while in a normal boot connected to the machine, could this possibly not be the case then?

I can get adb to recognize my phone when it is booted and connected (just a simple adb devices pops up with it), but I can't get it to show as the composite interface in device manager when I look. Just trying to make sure I'm not wasting time recovery booting when it wont show/messing with settings that don't need to be altered to see the phone in recovery mode.
[Droid Eris Android Development] bftb0:
The litmus test you should be using is whether or not you can communicate with the phone using ADB on the PC, with your phone booted normally and USB debugging turned on. If you can communicate (for instance "adb devices" returns your phone serial number), then you are good to go.

bftb0

PS appearances are that we are all wasting our time with this - so you'll be in good company.
[Droid Eris Android Development] thisismyanonymousaccount:
Exactly. I'm just not very articulate at the moment, my apologies.

Thank you, that is exactly what i meant.
[Droid Eris Android Development] :
Litmus? Litmus test eh, hm. I don't know. I've had ADB working this whole time, though not when I'm in recovery mode, only when the phone is in "normal" mode with USB Debugging on.

Even in recovery mode, I still get two devices: WPD Filesystem and E:\ under portable devices. There's got to be a fix for this too.
[Droid Eris Android Development] Wongidool:
Lol, well at least I have company :)

And ADB devices command does return a serial number, thanks much for clarifying. This is my first go at any sort of android hacking/dev/work of any kind, so it's proving to be interesting. But makes for a nice side project while working on my comp. sci. majo ;)
[Droid Eris Android Development] :
@Wongidool: yea, hope this "educational experience" of ours will help you along with your computer science Major or whatnot. I had a friend who pursued one of those but he's just into Linux and OSS stuff now, don't know if he has an Android phone or anything like that. :D
[Droid Eris Android Development] bftb0:
Romparoo brings up an interesting question - what are the odds?

Of course, I don't know for sure, so let's play "educated guessing game".

This thread has something like 17,000 page views and 320+ posts.

Let's suppose that there are only repeat visitors to this thread, and they only reload the thread when a new post is made - that would mean that there are about 50 unique visitors to the thread. Not really all that many, huh?

Let's suppose that every one of those 50 visitors have tried this exploit somewhere between 20 and 100 reboots of the recovery. That's somewhere between 1000 and 50,000 trials.

Let's further suppose that everything is on the "up-and-up" - two successes. That's a range that runs from 1 part in 500 to 1 part in 25,000.

Now, whatever the odds were - let's suppose the favorable case of 1 in 500 - then about 50% of the people that did half that number of recovery boot cycles (250) would succeed in winning race #1. (Worst case: 50% at 12,500 trials).

So, let's be optimists, and say that "there's a 50% chance you will succeed in 250 reboots, and nearly 100% chance of a win by 500 trials. (Or pessimistic: 50% by 12,500 trials and 100% in 25,000 trials).

It takes 15+ seconds just to get the <2e> menu, so the fastest it could possibly be done is 240 trials per hour (zero time for battery pull/replace + hboot reboot + keying to recovery boot) realistically, though, it's probably only 80 trials/hour.

So there's an estimate; if you want to be an optimist, you can expect success within about 6 hours of continuous trials; and if a pessimist... about 300 hours.

Good luck to all.

bftb0
[Droid Eris Android Development] HanSolo2012:
3 people got it to work

can anyone tell me what class this card is i cant seem to find it anywhere

sd-co2g is what it says at the bottom

http://www.walmart.com/ip/PNY-2GB-microSD-Memory-Card/10242121#ProductDetail
[Droid Eris Android Development] bftb0:
The mass storage endpoint is active all the time for both recovery and OS boots. I think my detailed post contained that info - if you looked for it. Under normal conditions, it is the ONLY USB device endpoint present in the recovery boot. That's the whole point of this "race" nonsense - on the Incredible and the Slide, the ADB or "Composite Interface" apparently shows up very briefly, and if you "talk to it" during that time it stays alive rather than dying off (or so it is claimed). You certainly shouldn't expect to be seeing it under "normal" recovery boot conditions.

The fact that you've got a bunch of willy-nilly drivers on your PC to support pluggable mass storage devices has nothing to do with whether or not your ADB device driver is working. And you have that working.

bftb0
[Droid Eris Android Development] mortymouse:
Yes, this is my issue. I am working on this right now using usbdeview
[Droid Eris Android Development] hallstevenson:
2, not 3 (unless I missed it ... dc_striker's friend didn't do this to his, if that's who you're referring to).

Googling the model # from the Walmart page suggests it's a Class 4.
[Droid Eris Android Development] AcidRoot:
Ok I'm not sure if this would work but what about using the adb tcpip command and then trying does anyone know what port is normally used for using adb over tcpip?
[Droid Eris Android Development] :
Ok so is this adb tcpip ( the actual command is: adb connect [IP Address of Phone]:[Port] ) really going to get us adb working when the phone is in recovery? If so, then I would be interested in trying again with that command first, before anything else in the guide.

Plus the port is 5555 according to google search, though others said 5554 try the one that works for ya. :P
[Droid Eris Android Development] :
Ok here is from Black Droid mod's page on the subject of adb and tcpip:

"1) Connect phone to PC (if it isn't already)

2) type adb tcpip <port> (I use 5555 as the port)

3) determine phones IP address (I used Android System Information, free from market, app)

4) type adb connect <phoneIP>:<port you used above>"

This should work. Hope I'm helping you guys more than hurting. :P
[Droid Eris Android Development] Realm:
I've had an hour of sleep last night due to trying to figure this out ugh!
[Droid Eris Android Development] :
Yea the IP address part is hard for me, since I still do not understand what IP to use, and whether to use Wifi on the phone, for instance. So that's a gray area, or unknown for me too. Ugh.
[Droid Eris Android Development] bftb0:
I'm pretty sure that neither the mobile network nor WiFi are alive in the recovery boot - no reachable IP address for the phone.

Ask if you could connect from another node on the loopback interface next :D

Besides, if you can connect to the recovery boot using adb, what exactly is the point?

bftb0
[Droid Eris Android Development] Dc_striker:
Does anyone know how to flash hboot 1.49.2 so i can have normal recovery but have it so i can go back to root

I wanna re try the adb recovery hack. I try just flashing recovery but i still got adbd running in it
[Droid Eris Android Development] bdt1995:
So, im not sure if this even matters, but when you were successful, were you using the usb cable that came with it (the extusb) or whatever its called, or a standard mini usb?

Chances are though, dc, if you try it again you wont be able to do it. Unless theres some secret your not sharing with us, it seems to be impossible.
[Droid Eris Android Development] :
Well the whole point of hooking adb to the recovery mode, in this case is to run the original commands in the first post of this thread by Stryker. If ADB can detect the Android phone, in recovery, then the rooting method he posted can be used.

I guess the WPD thing and the E:\ thing in my Device Manager on my Windows is normal according to those on this thread too. So all I need is that extra device to show up whatever it is, "ADB Composite" and I'm set. Any more details on how to get this to show up? Thanks.
[Droid Eris Android Development] Dc_striker:
Uninstall the drivers and reinstall them