yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] Jp50:
this is a perfect example of why we should be documenting everything. I bet if you compare the software versions there may be some differences. did you check his baseband version, software etc?

If we document every aspect of each phone, we'll probably see common traits in all the phones that rooted easily.
[Droid Eris Android Development] carycooke:
post homay post lol soomething you got the answer in your hands lol
[Droid Eris Android Development] npsmith:
Windows 7 32 bit

When I try to intall USB driver from .inf file I get:

The folder you specified doesn't contain a compatible software driver for your device. If the folder containts a driver, make sure it is designed to work with Windows for 32-bit systems.

I got it to work once, "browse my computer..." > "Let me choose..." > "Have Disk"

But when I plugged it in, in fastboot and go through the process, I get the error.

I also tried using a different USB cable and got the same error. Help...
[Droid Eris Android Development] homaygfresh2000:
Gonna have to wait.... I was just in a meeting and he's left work now. I'll see if he can email me his hardware info later this evening so that we can figure this out.
[Droid Eris Android Development] bhilgeman:
Question,

I was trying to root my brothers Eris that came from the store with Hboot 1.49 using these methods. I could not get it to recognize the device while trying to boot to recovery, BUT

I could connect to adb running the loop while powering up the phone into the OS. Even while it was fully booted I could access adb. I couldn't mount the system as it said access denied but for the hell of it, I tried installing superuser.apk and it worked, and I tried pushing files and it worked. Unfortunatly this is as far as I got as he had to leave for work.

Is there anything I could have done while booted to the OS with access to adb? I tried to mount the system thinking I could flash the recovery or something. I got a shell promt $ but obviously couldn't su....

Are there any commands I can use once booted to the OS with adb access to root the phone? Thanks
[Droid Eris Android Development] Zalatorisaurus:
Same for me. Except I have Vista 64 bit. I get the same error message more or less and I've already tried the "Disable signature enforcement" thing on the help page. No dice. I need help too. SOMEONE PLEASE HELP US!
[Droid Eris Android Development] HanSolo2012:
format the card again
[Droid Eris Android Development] HanSolo2012:
No...

Thats good that your phone is seen when starting up

means you are past the driver part

Just keep trying its easy once you get that hang of it
[Droid Eris Android Development] HanSolo2012:
This is what my phone looks like turned on

Win 7 64 bit
[Droid Eris Android Development] bdt1995:
So just to clarify, you successfully installed superuser.apk while booted in normal mode? Could you write out the steps you used and were intending to do after that had he not left for work?
[Droid Eris Android Development] reidd:
I can't even get the RUU to flash. I've tried probably 15 times on two different laptops, both with and without USB debugging. One laptop is Win 7 64 bit and the other is Win 7 32 bit. It just pulls up the screen on my phone that shows the HTC logo, and on the computer it shows 'waiting for bootloader' then after a while, it just says Error 171 USB connection error when the USB cable is plugged in firmly in both ends. I don't understand?
[Droid Eris Android Development] cvmagic:
You can install the package, but it does you nothing. You still get permission denied anyway.
[Droid Eris Android Development] eris-:
I had the same problem, What i did was made sure the phone display didn't go dim. I just kept moving the ball around on the phone during the RUU process and it worked. Keep in mind that the RUU wipes your phone clean. I still can't get the timing down though in recovery :(
[Droid Eris Android Development] djg57:
Is your modified .inf file in your usb_driver directory? I was having a similar issue when I tried to install the modified driver from my downloads directory
[Droid Eris Android Development] bhilgeman:
Not sure, I was hoping I could somehow mount the system and flash Amon_Ra's recovery.

I tried it for about 5 minutes while botting into recovery and nothing. I rooted my Slide using this method first try with my stock Class2 8GB card after trying for hours with my Class6 8GB card. I tried 4 different cards with the Eris and nada. I will try again when I have more time with the phone...
[Droid Eris Android Development] reidd:
I tried that and touching the screen too, and it still didn't work. I even tried checking the 'stay awake while charging' box, and STILL nothing.

One thing I did notice, however, is that everytime I try this, it always has to reinstall the driver for HTC Bootloader because it always popped up. It always installs correctly though. But after the program says it failed, and I click exit, it says Windows must be restarted for these changes to take effect. It does the same thing every time. I'm stuck.

Another thing I should tell you is it doesn't even start to flash to the phone. It just sticks on 'waiting for bootloader'. It won't even start flashing.
[Droid Eris Android Development] FosterFTbT:
I took the battery out, and the phone won't turn on. Bricked?
[Droid Eris Android Development] joebob213:
Been answered several times, no. Pull the battery, wait a few minutes, reinsert battery, ...profit.
[Droid Eris Android Development] homaygfresh2000:
Just unplug the USB cable and remove the battery and let it sit for 30seconds or so. Should be fine. Happened to me many times.

Damn, someone beat me to it....
[Droid Eris Android Development] dantonuci:
Hello I am a Leak V3 person after this method is exhausted and or perfected is there a chance that there will be a flashable rom that can achieve root or is it going to have to involve all the wild steps we're dealing with now, I apologize if this has already been brought up, by the way big fan of the seidio 3500 extended life battery now i just wish i had live wallpapers to eat it up
[Droid Eris Android Development] nesgodawg:
Okay, I'm no longer a leaker, got a replacement phone and it came with the updated 2.1. I'm having the same issue as some other people though. I can't flash the RUU, it keeps saying that after I get to the waiting for bootloader that my phone is no longer connected to my PC.

My PC is a Win7 64bit

Also in my device manger I have Android Phone listed with Android ADB Interface listed twice with the yellow triangle ! symbol next to it. Tried to update the driver numerous, but always get the error 10.

Also in device manager I have Android USB Devices and under that My HTC... no update needed.

UPDATE: Okay, so I uninstalled the two bad drivers and then did off the My HTC one, everything is now how it is supposed to be according to the steps at the beginning.
[Droid Eris Android Development] lander16:
I tried the timing step about 50 times in XP and another 50 on a Mac, neither worked. I'm using the stock 8Gb card since I'm in Mexico and haven't been able to find the PNY.

Anyhow, hope the process gets perfected soon.
[Droid Eris Android Development] mam4983:
I'm really starting to think that this just works on some phones and not others...depressing.
[Droid Eris Android Development] sznaps:
I agree, I honestly believe only some phones are vulnerable to this.
[Droid Eris Android Development] Eoghann:
If that is the case (and I'm starting to wonder the same thing) then identifying what the difference is between the phones it works for and phones it doesn't would tell us a lot.
[Droid Eris Android Development] :
I too think this. Now, we'll need either A. a new method for those leakers who have no success with this way of doing root, which is unknown at this point (as stated by several) though devs here are probably looking right now for an alternate way to root successfully.

or B. An even more refined, even more perfected version of this current method that works for all Eris 2.1 phones, including those who leaked (v3 especially, like the one I have)

If A or B is ever possible, then maybe some of us without root (and wanting it) will then get it, and like other have said we can go home and enjoy our root.

Also I don't understand why go through all of this mess to root, even if it works, and some people un-root. It's a step back. :P
[Droid Eris Android Development] :
Actually I take that last part back, seriously, I guess un-root is okay if you didn't REALLY want root or want to keep your warranty fine, etc, etc. I can see that, like you know, if you were playing or experimenting with root. Yea totally understandable. :D

Also can someone enlighten me as to why my Eris, though it has a slightly lower CPU speed (Eris's 528 Mhz vs Droid's 550 Mhz) than Motorola Droid etc etc, still doesn't perform that well though I am using the non-root v3 leak on my phone? Like, for instance, when I try to install many, many apps at once, it takes FOREVER and i mean FOREVER to actually process through those. (downloading is not the problem though, that works even with my limited 3G here at home. I compare to the Moto Droid because my father uses one, and though he has problems with the call audio quality, the speed on his phone is substantially faster depite being only a little faster than my CPU? Ok I guess I need a computer scientist type guy to answer me.

And YES I have cleared everything, and started over to fresh today by hard factory reset (it was about 5 hours ago, haven't done anything with it yet). On the phone, is it a defective, or otherwise bad unit, that would be bad. Or is it simply a limitation of all Eris phones that they work this way. Thanks,

no pressure.

Just wanted a good answer from some devs or other people on the thread. If there is a quick even a not so quick fix I'd be obliged towards someone to give me a link, or otherwise drop me some good advice on this problem, is this a known issue with the Eris? Plus I don't have the silent call bug, which is good in and of itself, everything else is fine with it but app install speed is very slow with Android Market, for instance, as I mentioned earlier. If I did root, I'd be happy if I could just eventually go back to 1.5 Cupcake, the Eris default that it came with. Ok thanks.
[Droid Eris Android Development] sznaps:
Well, I can start by posting the information of my phone, which this did not work on?

I went from 1.5 to Leak V1 to Leak V2 To Leak V3 to RUU

My S/n is HTXXXX7952

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-MELFAS_45_17

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56

Anything else you need let me know.
[Droid Eris Android Development] Zalatorisaurus:
Alrighty. I've tried this with the 8gb stock sdcard and have had no luck. I'm gonna try a 2gb sandisk as soon as it finishes formating.
[Droid Eris Android Development] FosterFTbT:
This RUU Flash worked. To clarify, this means that I now have the OTA update and am unrooted, so I no longer have the leaked 2.1 version on my phone correct? If so, couldn't I just root using another method?
[Droid Eris Android Development] TopazAaron:
no cuz ur bootloader is still 1.49

you need a lower bootloader for that to work
[Droid Eris Android Development] FosterFTbT:
okay, thanks. So, step 9, the timing step, is to enable root then?

Yes, I am new.

What happens for me :

I've gotten two results from attempting step 9 : Either the loop keeps going after I count to 4 in thousands, then stops, or when it will stop as soon as I enter in the flash-drive and say :

"Daemon still not runningerror: cannot connect to daemon

*Daemon not running. starting it now.*

ADB server didn't ACK

*failed to start daemon*...."

Anyone else getting something similar?

I'm worried I may have done step 6 wrong. Where it mentions to redo the previous steps. I'm rather confused as to why do something, then redo it the same exact way. Am I missing something with step 6?
[Droid Eris Android Development] fox_dye:
Well guys its been a crazy ride. I tried this on all 3 of the phones I've had. I got 2 replacements in a week and had no luck. The second replacement I got was actually a mistake. It should have been a MOTO Droid. But my Droid will be in tomorrow and I plan on having it rooted and romed in a short time after opening it. Good luck to everyone.
[Droid Eris Android Development] Zalatorisaurus:
I'm convinced that this won't work for me. I've tried two different sd cards and I believe I have the timing down. 4 seconds after pressing volume up and inserting the sd card and 4 seconds before windows makes the connected device sound. Can anyone help? Do I have the timing down?
[Droid Eris Android Development] nesgodawg:
I can't get past the timing step either.

I've tried the stock card and two of the 2gb cards. Still no luck. I must have tried 50 times or more with each card. Nothing.
[Droid Eris Android Development] lostpilot28:
I saw this a lot when trying to root my Eris using my Windows XP machine. Windows 7 didn't do it. What I did notice was that there were a BUNCH of ADB.exe instances running in Task Manager. I'm guessing that may be a problem.
[Droid Eris Android Development] Zalatorisaurus:
Same here man. I even tried those other methods (taking out and reinserting the sd card at the /!\ screen). I don't know what to do. I need help. Someone help please.
[Droid Eris Android Development] FosterFTbT:
likewise, hmmm.
[Droid Eris Android Development] lostpilot28:
Sooo, regarding the Timing Step...is it the phone that we're trying to time with, or the PC? I know that Windows XP will display the result of ADB's query, but aren't we really trying to interupt the PHONE going into Recovery??

If that's the case, I have a feeling a lot of us are counting to 4 and listening to Windows and the Beep Boop, Boop Beep...when we really should be paying attention to the /!\ and when it comes up. Mine comes up at around 7 seconds, which is right after the first Beep Boop in Windows. Not sure if any of this is relavent, but thought I'd throw it out there. I'd love to get this thing rooted.
[Droid Eris Android Development] lostpilot28:
OK, I know this is a shot in the dark, but I just e-mailed HTC asking for help. I told them I'm aware of the risks and willing to proceed with Rooting and wave my warranty. Maybe if enough people e-mail them, it will get their attention. :rolleyes:
[Droid Eris Android Development] Nikolai2.1:
Doubt it. Htc people know e

ither nothing or everything. If its the second one then they do a good job at conceiling their knowledge.
[Droid Eris Android Development] npsmith:
Nevermind. I got it to work using the disable signature check trick.
[Droid Eris Android Development] npsmith:
Well I have tried using 2 os's (OS X and Windows 7 32-bit) as well as 3 different sd cards and 3 different usb cables... but no luck so far.

I will tell you one thing though: I am a pro at popping the sd card out and hitting the volume down button simultaneously.
[Droid Eris Android Development] Realm:
good luck on that one. I would give them a call instead if I were you ;)
[Droid Eris Android Development] CoolBone:
This is what I wonder. I'm afraid I'm timing to something completely irrelevant. I'm a classical musician so being able to count 16th notes shouldn't be exceptionally challenging. I'm pretty sure I'm either aiming for the wrong event, or my gf's phone is unrootable.

From my Incredible Drooooiiiiiid.
[Droid Eris Android Development] Nikolai2.1:
GoldCard

EDIT: nevermind..
[Droid Eris Android Development] g19max1:
I agree we need to start documenting, so I'll be the first ;) Also, this phone was flashed with the RUU, fyi.

THIS METHOD

DID NOT

WORK FOR THIS PHONE

HBOOT

Touch Panel: Melfas_45_17

HBOOT: 1.49.0000

Software

Firmware Version: 2.1

Baseband Version: 2.42.00.04.12

Kernel Version: 2.6.29-8a03cb9a

htc-kernel@and18-2 #1

Build Number: 2.36.605.1

Software Number: 2.36.605.1

Browser: Webkit 3.1

PRI Version: 2.11_002

PRL Version: 51866

ERI Version: 5

Hardware

Hardware Version: 0002

Model Number: ADR6200

SD Card

Generic Brand 1GB microSD
[Droid Eris Android Development] sydtrakked:
does having the RUU over v3 make any difference? to me it seems that there have been more successes with the RUU...
[Droid Eris Android Development] bftb0:
They are identical. Believe it or not, when the RUU runs and unpacks it's wares, it contains the same PB00IMG.ZIP file that everyone refers to as Leak-V3. (It is named "rom.zip" inside the area that the RUU unpacks).

Were not talking "kinda similar" here, we're talking identical checksums - not one bit in 800 million is different.

It may be that you have seen more people report success having used the RUU; that is either because (a) more people are using it - so therefore more successes, or (b) there's something about the method that makes it sensitive to what kind of files are in the various flash partitions.

The latter hypothesis is sort of hard to imagine, however, because the race is already over by the time /data and /cache get mounted by the recovery boot.

bftb0
[Droid Eris Android Development] homaygfresh2000:
Okay, here it is:

HIS INFO:

Firmware Version: 2.1

Baseband Version: 2.42.00.04.12

Kernel Version: 2.6.29-8a03cb9a

htc-kernel@and18-2 #1

Build Number: 2.36.605.1

Software Number: 2.36.605.1

Browser: Webkit 3.1

PRI Version: 2.11_002

PRL Version: 51866

ERI Version: 5

Hardware Version: 0002

MY INFO:

Firmware Version: 2.1

Baseband Version: 2.42.00.04.12

Kernel Version: 2.6.29-8a03cb9a

htc-kernel@and18-2 #1

Build Number: 2.36.605.1 CL1650907 release-keys

Software Number: 2.36.605.1

Browser: Webkit 3.1

PRI Version: 2.11_002

PRL Version: 51920

ERI Version: 5

Hardware Version: 0002

Completely identical, except I have a newer PRL. We had both updated leaks pretty much the same day after one of us installed it and told the other, starting from leak1 all the way up to RUU. I have no idea what could be making the difference....?

PS - He didn't give me the "release keys" part after build number, but I'll try to get it form him today just to confirm that it's the same as well.
[Droid Eris Android Development] tereg:
The phone did not come in, so I'll check again today. When I have a spare moment I'll try to compile some sort of document that lists out successes and unsucessful attempts.

Mine was successful. I went from leak v1 -> RUU OTA

My FASTBOOT is as follows:

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-MELFAS_45_17

RADIO-2.42.00.04.12

Feb 8, 2010,00:08:56

Because I'm using ELB 2.7, I have limited information about hardware version and stuff. However, I can provide a dmesg dump of a fresh reboot.

But here's what I can provide from Settings -> About Phone

Baseband version: 2.42.00.04.12

PRL Version: 51920

Anything else you think I can provide in a log dump, I would be more than happy to provide.

dmesg dump after a fresh reboot: http://pastebin.com/K1wL8x8G
[Droid Eris Android Development] gnomesarealive:
I don't know if this means anything, but here is my Fastboot screen

PB00100 XC Ship S-ON

HBOOT-1.49.0000 (PB0010000)

TOUCH PANEL-SYN0104

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56

I highlighted the only difference I see
[Droid Eris Android Development] dawynkoop:
My Info: No successful root attempts :mad: after hundreds of tries with 3 different SD cards

HBOOT:

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-SYN0104

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56

SOFTWARE INFO

Firmware Version: 2.1

Baseband Version: 2.42.00.04.12

Kernel Version: 2.6.29-8a03cb9a (htc-kernel@and18-2 #1)

Build Number: 2.36.605.1 CL165907 release-keys

Software Number: 2.36.605.1

Browser Version: WebKit 3.1

PRI Version: 2.11_002

PRL Version: 51920

ERI Version: 5
[Droid Eris Android Development] diablo908:
My info:

Firmware version: 2.1

Baseband version: 2.42.00.04.12

Kernel version: 2.6.29-8a03cb9a htc-kernel@and18-2 #1

Build number: 2.36.605.1 CL165907 release-keys

Software number: 2.36.605.1

Browser version: WebKit 3.1

PRI Version: 2.11_002

PRL Version: 51731

ERI Version: 5

Hardware version: 0002

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-MELFAS_45_17

RADIO-2.42.00.04.12

Feb 8 2010, 00:08:56

So far unsuccessful.
[Droid Eris Android Development] dawynkoop:
Have you had any luck rooting or even getting adb to work in recovery?
[Droid Eris Android Development] snyluc13:
I have the same Touch panel, i wonder if other users that have not been able to root have the same TOUCH PANEL-SYN0104
[Droid Eris Android Development] dawynkoop:
I have the same touch panel as well and have been unable to get root.
[Droid Eris Android Development] DRAGON TB7:
My Info

HBOOT:

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-SYN0104

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56

SOFTWARE INFO

Firmware Version: 2.1

Baseband Version: 2.42.00.04.12

Kernel Version: 2.6.29-8a03cb9a (htc-kernel@and18-2 #1)

Build Number: 2.36.605.1 CL165907 release-keys

Software Number: 2.36.605.1

Browser Version: WebKit 3.1

PRI Version: 2.11_002

PRL Version: 51866

ERI Version: 5

Trying on Windows 7 64 bit.Using stock 8 gig sd card. Went from leak v1 to v2 then to v3 now RUU. The RUU took 2 tries failed the first time, cant recall what i did different the second time to get it to work. Drivers went in better on my desktop then with the laptop? Think I got the timing thing do ok but nothing happens. Hope this helps us all some time soon.

PS Thanks to the devs for all the hard work on this.
[Droid Eris Android Development] HanSolo2012:
If this is happening to you then dont run loop.bat

just go to to cmd

and your tools directory

type in adb devices

it should return device not found but start adb for you

go through the whole timing step

and when you get up to the /!\

wait the 10-15 seconds on the /!\ screen

then just go into command prompt

and type adb devices

press enter

if your device found then just procceed to next step

if not then start over again

Loop.bat is only making it so you dont have to tell your computer to look for device

nothing more

It is not sending special commands to your phone to make it go into recovery with adb
[Droid Eris Android Development] octavioromo:
I also have the same touch panel TOUCH PANEL-SYN0104 and have been completely unsuccessful. Has anyone been able to root with TOUCH PANEL-SYN0104 this is shown when you fastboot. thank you this would help to narrow down why some people are having problems and others not. If it is the TOUCH PANEL-SYN0104 is there a way to change it(is it that the actual screen, or software?) Thanks everyone.
[Droid Eris Android Development] Nikolai2.1:
I doubt that matters. I have MELFAS_45_17 and no luck after hunnddrreeeds of tries.

But out of curiosity. Anybody know what touch panel tereg has?
[Droid Eris Android Development] cptkrush:
He has MEFLFAS_45_17 i believe, it was posted earlier.
[Droid Eris Android Development] Nikolai2.1:
Quite honestly, should any of that matter? I dont see how that messes with adb
[Droid Eris Android Development] octavioromo:
i dont see it either but if anyone has been successful with TOUCH PANEL-SYN0104 it will help narrow down the possibilities and for some give them hope, like me. :) i really want this to work! thanks.
[Droid Eris Android Development] djg57:
My info - I was able to root with this method

HBOOT-1.49.0000 (PB0010000)

MICROP-0111

TOUCH PANEL-SYN0104

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56
[Droid Eris Android Development] octavioromo:
Thanks, Guess ive got to keep at it!
[Droid Eris Android Development] carycooke:
my info on my phone is the same as all the others but i dont have the melfast touch panel

Im wondering if there is a way to read anything on the ADB specs????

I GOT THE 2E ANDROID SYSTEM RECOVERY
[Droid Eris Android Development] carycooke:
Im wondering if there is anyway to swap out sd cards after the signature check has been done and run unsigned code after the check almost like on xbox 360s where they did a dvd hot swap during code check then putting in a burnt dvd to finish the process?????just trying to think of possibilities dont know