yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] tereg:
If done correctly you should not see HBOOT look/search for any update files. If the phone does start to read the sd card at that step, just pull the battery and start again.

For those of you very frustrated by this process, I am going to start something by trial run basis. I'm having a user mail me their extra don't-care-if-they-brick phone and I'm going to try to root their phone using my environment. Actually, what I'm going to do is I'm either going to use my webcam to record the process to make a video, or broadcast myself live through tinychat or some other means while I attempt to root this phone. If I'm successful perhaps something can be set up where you can send me your phone and I try to root your phone then send the phone back to you. I'm expecting this user's phone to be sent to me within 2 days.
[Droid Eris Android Development] Burgers:
No luck for me again last night. Updated from V1 leak to the Ruu, reformatted my card with disk management while it was in the phone.. tried about ~40x.

i think i may be waiting to long after i press volume up, to pop the SDcard back in.

Question: At the end of step 9, when we turn off our phone and get ready for the SD card pop. Should we enable USB debugging before we turn off the phone? Not sure if this matters or not, just throwing it out there cause everything else seems to be in place.

Will try again when i get off from work..
[Droid Eris Android Development] freethewhat:
Is there any way I can test this out while having root? I have tried a few methods but it keeps throwing me into recovery.
[Droid Eris Android Development] xtreme3737:
I am having problems pushing Amon's to my phone.

These are the command I am trying to use:

adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img

I used:

adb shell
<enter>
$su
<enter>
#mount -o rw,remount /dev/block/mtdblock3 /system
<enter>

What do I need to use for the adb push commands?
[Droid Eris Android Development] tereg:
If you have flashed the RUU, you will need to turn on USB debugging again. And yes, USB debugging was on for me before I turned off the phone.
[Droid Eris Android Development] Burgers:
Thanks Tereg.. A NEW HOPE! too bad I'm stuck at work for 10 hrs..
[Droid Eris Android Development] Hairston:
I rooted without doing the RUU, so it's obviously not a requirement. But if doing the RUU gives you a better chance to win the race war, I can't answer that question.
[Droid Eris Android Development] tereg:
Try this if you see a root (#) prompt

# exit
$ exit

Now you're in the regular command prompt (C:\android-sdk-windows\tools)

Run these commands

adb push recovery.img /sdcard
adb push flash_image /system/bin

Now, you have to drop into shell again and do su

adb shell
$ su
# chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/recovery.img

Try this and see if that helps.
[Droid Eris Android Development] HanSolo2012:
adb push recovery.img /sdcard

adb push flash_image /data/local

adb shell

su

(it gave me #)

chmod 755 /data/local/flash_image

/data/local/flash_image recovery /sdcard/recovery.img

this worked for me right in this order from what tereg gave me last night on the chat

just copied and paste

oh nvm tereg beat me to it
[Droid Eris Android Development] davinci27:
Are you saying I shouldn't see the word HBOOT or just that it shouldn't scan the card?
[Droid Eris Android Development] homaygfresh2000:
It shouldn't scan the card.... no scrolling list of green text looking for update IMG's and stuff.
[Droid Eris Android Development] vandykky:
I think I've lost the 'race' about 700 times in the last few days. Not sure what I'm doing wrong. Went up to RUU the other day, drivers are OK, but maybe my sd card is wrong. it is really old and crappy and I cant seem to figure out what class it is. it is a PNY 2GB has printed "MM8GR02GUACY-NA | F1220000 752 Made in TAIWAN" on the back. Any ideas? Do I scrap it and buy the magic card you all have used?

Also thanks everyone who has worked hard on this. I can't stand it when people can't get an exploit to work so they blame the people who developed it... they are all jackasses i tell you!
[Droid Eris Android Development] mortymouse:
I picked up the card from Best Buy tonight after crazy attempts without it. I tried about 15 times last night and it will not go. Going to try all day today and see if I can do it.

With Windows 7 no matter what I try I can disable the auto drivers, and I wonder if thats the death of this for me. I have deleted all of the drivers, and then refreshed and used the winusb drivers, but it still will not see it in recovery.

Anyone that has done this on Windows 7 have any tips?
[Droid Eris Android Development] DjCalvin:
Ok, Im at a loss here. Been trying this for 2 days now.

I have the Nat geo 2gb PNY Card - listed in 1st post from wally world. same model number.

I have a replacement device from VZ that came 2 weeks ago with the 1.49 boot loader and 2.1 already on it. (Esentially the RUU)

Drivers are loaded fine (win7 32 bit)

When The device boots up and I eject the card while going into hboot, device manager shows Android Bootloader Device.

When I hit up and start counting, that device dissapears. When I miss the timing, it just comes up as a usb storage device.

Im doing my timing from www.metronomeonline.com I cant get the F'ing timing down.. (I am counting to the metronome after giving up with the one one thousand, two one thousand )

Ive tried:

2gb PNY nat geo

2gb PNY non Nat geo

4gb Sandisk

8gb Stock sandisk

1gb Sandisk

Timing from everything from a second to a real 6 seconds via stopwatch.

We really need a mp3 file, video or ANYTHING to get the timing down.
[Droid Eris Android Development] jordon47203:
There is an audio file on the first page where he shows how fast he was counting.
[Droid Eris Android Development] DjCalvin:
Holy crap.. Awesome

havent looked at the 1st page in a day.

Thank you
[Droid Eris Android Development] diablo908:
There is an mp3... refresh your tutorial... it's under step 10
[Droid Eris Android Development] HanSolo2012:
windows 7 64 bit

successfully rooted 5 times

as long as your phone shows android composite adb device when the phones on

you should be good to go on the driver part

make sure your mounting the phone as a usb drive

when you do this

go into computer

right click drive

go to format

do all the format settings from tutorial

once its done formatting

take out the battery with the phone on

and try going for root again
[Droid Eris Android Development] tereg:
I just cut out a step, so Step 10 has now become Step 9.
[Droid Eris Android Development] davinci27:
WOOHOOO!!! Add me to the list of successes, but I've got a new kink to throw in. I tried at leaset a 200 times with no success. The last time I got /!\, I left the phone in the /!\ and popped the card out tand then right back in. Still had /!\ on the screen, but suddenly the device showed up in the loop. Finished the rest of the steps and now I've got root. I was doing this on a OS X 10.6. PNY 2GB card. Don't know if it was dumb luck or another twist in the steps.
[Droid Eris Android Development] dawynkoop:
Been trying off and on for 2 days now with no luck. Looks like I'll be stopping by Best Buy today to pick up the 2GB PNY SD card. I've tried with 3 different SanDisk cards, a 1GB, 2GB, and 8GB Class 2 card and no luck with any of them.
[Droid Eris Android Development] homaygfresh2000:
Any idea how long it was on the /!\ screen before you did this? Right away or a couple seconds in?
[Droid Eris Android Development] DjCalvin:
<whine>

This is driving me f'ing nuts trying to get it into recovery mode.

</whine>
[Droid Eris Android Development] davinci27:
That's the hard part. It really was an accident. It wasn't more than a second or 2, and it could have had nothing to do with the whole process. I saw the dreaded /!\ and in frustration just clicked the card in and out. I was just going to pull the battery when I saw my loop switch from no devices to HTC12328373 recovery.

It could also be a timing thing. I had pretty much been yanking the battery whenever I got /!\. I may have been timing the process correctly the whole time and just not waiting long enough for the loop to pick it up.

Not sure any of this information helps or hurts, but its what happened.
[Droid Eris Android Development] tereg:
Ooh, this is really interesting. I'd definitely like to test this some more. I will promptly add you to the list with a link to this post and a note.
[Droid Eris Android Development] snyluc13:
I plan on giving this a shot during my lunch break, gonna try it with the stock card atm i dont have the pny one
[Droid Eris Android Development] dawynkoop:
Let me know how it goes, I've been trying with the stock card for 2 days and just can't seem to get the timings right or something.
[Droid Eris Android Development] HanSolo2012:
One of my roots happpened like this

i had loop running on my computer

my phone was caught in a recovery loop

where it just keeps restarting and going to recovery

i didnt touch the sd card

i looked at my phone it had recovery screen

then looked at my computer and it was showing my device

it was random
[Droid Eris Android Development] mortymouse:
So this is strange. I finally saw something different happen after about 25 attempts. Now when I go from HBOOT to recovery and watch the device manager, the Android phone goes away, but rather than the usual WD hardware !, I see no errors and I see the phone listed under drives as HTC Android Phone USB device. So I am in recovery and seeing that, but I cant see it in adb devices, etc.

Anyone have an idea before I get out of this? I have not seen this before.
[Droid Eris Android Development] mortymouse:
Disregard. Still goes back to WPD Filesystem Volume Driver
[Droid Eris Android Development] davinci27:
I got caught in a loop like that 4 or 5 times. I wonder if I had just left eh phone alone if it would have shown up in recovery?
[Droid Eris Android Development] Jp50:
Wondering the same thing myself. The loop how long should we wait? Should it show up instantly or does it take some time for the device to pop up in the loop?

I usually waited a few minutes and if nothing would ctrl c and battery pull, start over again.
[Droid Eris Android Development] timoyo3:
how did you get it to loop? becouse ive been trying everything else, thanks
[Droid Eris Android Development] bftb0:
I created a custom recovery boot based off of the Leak-V3 (= OTA2.1) recovery boot, and tested it on a rooted phone to look at the normal timing of the start sequence. This "custom" recovery only differed from the ones the leakers are trying to hack by setting the persist.???.adb.enable property to 1 in the default.prop file so that adb would start every time.

The result? Adb starts about 7.2 sec after the kernel boots! This always happens after the /!\ splash screen shows up. So, I can imagine that there have been a number of people yanking their battery right after they insert the SD card if they don't see adb show up in the loop. (Note that the kernel boot timer starts running sometime after you hit vol-up, so the perceived wall-clock time will be longer than this)

Bottom line? Your need to wait until at least 2-3 seconds after the splash screen shows up before you decide that adb isn't going to show up on that trial.

bftb0

PS. The kernel doesn't even look to see what is in the SD slot until right about the same time...~7 sec. Probably the timing of the SD card insertion doesn't even matter.
[Droid Eris Android Development] HanSolo2012:
This was random for me

dont be aiming for the loop

just follow the guide

I am really stressing the format part it seems to mean the most

at least during my testing
[Droid Eris Android Development] HanSolo2012:
Thank you for that info

i have been thinking that in the back of my head

seemed i was able to get root without touching the sd card on that one attempt <- really weird but i swear it happened

and the different timing sometimes 2 seconds sometimes 5 seconds
[Droid Eris Android Development] snyluc13:
didnt work for me got to the /!\ part put the card in then out multiple times

got this:

** daemon still not runningerror: cannot connect to daemon
** daemon still not runningerror: cannot connect to daemon
List of devices attached

List of devices attached

List of devices attached

List of devices attached

** daemon still not runningerror: cannot connect to daemon
List of devices attached

List of devices attached

List of devices attached

List of devices attached

* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
List of devices attached

* daemon not running. starting it now *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
* daemon not running. starting it now *
[Droid Eris Android Development] TheSonicEmerald:
okay, after i take the sd card out right when the phone goes into hboot what happens? does the phone just stay in hboot? or does it do something else?

Since the hboot doesn't seem to run when i take the card out, i go into cmd on my computer, type in "cd C:\android-sdk-windows\tools" press enter, then i type "loop" and press enter. But it says "'loop' is not recognized as an internal or external command, operable program or batch file."

What's the deal? Phone has been formatted correctly (sd card more specifically), previous steps worked, but not this one.
[Droid Eris Android Development] djg57:
Finally got my phone rooted last night.

I was using an old PNY 2g card I've had for about 2 years(SD-C02G JAPAN) formatted per the instructions.

I left the card popped out until I hit vol+ to enter recovery. From my experience hitting Vol- and popping the card out at the same time is an unnecessary step.

I used a clock to count off 6 to 9 seconds and popped the card in but I feel the time had less to do with it than luck. Every time adb recognized my device it was after the /!\ recovery screen appeared.
[Droid Eris Android Development] Nikolai2.1:
Follow the tutorial!
[Droid Eris Android Development] lostpilot28:
Doesn't your Device Manager on your PC find it well before 6 seconds?? Mine is a hair over 4 (real time) seconds. I would think that after the Dev Mgr in Windows doesn't find it, then popping in the card afterwards isn't going to help you. Or am I misunderstanding what you're saying?
[Droid Eris Android Development] bftb0:
I absolutely believe you.

There is a reason why we see a pattern to the results - people win the race randomly... when duplicating the same sequence of voodoo rituals of others before them, and then after some time it starts to look like the voodoo is important...

Clearly if people only try using a single brand of SD card, then all the successes will come from that card (as an example - I'm not singling that out for ridicule)

bftb0
[Droid Eris Android Development] cptkrush:
After reading through a few peoples attempts and seeing that they have all had success with different methods of execution, i believe you are 100% correct. I'm going to begin testing the method by just going straight into recovery SD card in the whole time, stock, not formatted. After all, my pny hasn't arrived yet, so if i can get it to work this way, i can just send it back.
[Droid Eris Android Development] tereg:
It will just go into HBOOT and do nothing else.

If you are in a command prompt in the tools folder, do a

dir

command and make sure a file is listed there called loop.bat

If doing "loop" doesn't work, try typing

loop.bat

as the command and execute it.
[Droid Eris Android Development] djg57:
Actually my device manager didn't update until 6-7 real time seconds. I'm using Win7 x64. In any case, I'm not really sold on the timing of inserting the SD card. I actually got adb to recognize my phone 3 different times and each time the SD card was inserted at different time intervals.
[Droid Eris Android Development] Zalatorisaurus:
I'm still scared to try this. I'm pretty new to android besides getting the leak. Should I wait for a better/easier way or should I go for it?
[Droid Eris Android Development] cptkrush:
I say go for it, it has been a much needed learning experience for me, and after countless tries, i still haven't gotten it, but im not going to give up. as long as you know your way around a command prompt and can follow directions, you should be fine.
[Droid Eris Android Development] thewanton:
Well, it's my birthday. I sure as hell hope that helps my luck out. I'll try the 'keep pulling sd card' method in a few. Waiting till my mom leaves. She hates it when I mess with this phone. :P
[Droid Eris Android Development] mortymouse:
Just driving me nuts and I cant stop as I never do until I have success. I have tried just about everything. I am running Windows 7 64 bit, standard mini USB cable, I have had the RUU installed since it came out, it will find my phone in adb as long as I am not in recovery. As soon as it goes into recovery, it changes to an Android USB device and will not be found.
[Droid Eris Android Development] Zalatorisaurus:
Thanks. I think I will go for it. I've done some stuff like this before that involved the command line. I'll try it when I get to a computer.
[Droid Eris Android Development] dawynkoop:
Has anyone who has repeated success at getting this to work tried it by booting directly into recovery (vol up + end)?
[Droid Eris Android Development] lostpilot28:
When mine goes into Recovery (volume up button), it is never found in Windows Device Manager. I thought this was normal behavior for being unsuccessful in this step. If it IS found in the Device Manager when you enter Recovery (I thought) you are successful. Or am I wrong?
[Droid Eris Android Development] IlKYoSuKElI:
Hmm I'm seeing an interesting pattern here. I, as well, am running on win 7 x64 and from what it seems... has anyone gotten any success from this OS? I know everyone says that OS doesn't or shouldn't matter but from what I'm been seeing is that a lot of people that have this OS setup are having issues and with no success of root. Just an observation that I wanted to bring into light.
[Droid Eris Android Development] djg57:
You are correct, everytime adb saw my device in recovery I could also see "Android Phone" in the device manager. It just doesn't happen that often.
[Droid Eris Android Development] bftb0:
lostpilot28,

When the phone is in HBOOT mode, for all practical purposes the USB is dead; the phone does not advertise a single interface in this mode.

When you boot into recovery, the first thing that happens is that the Mass Storage interface comes up on the phone (0bb4:0ff9) - that happens right around 3-4 seconds. Note that this happens in the kernel in the middle of the boot - the kernel doesn't finish booting until about 7 seconds.

[SIZE=+1]IF[/SIZE] the ADB composite interface comes up (0bb4:0c98), it only will happen if the "adbd" program is running on the phone - and this can not happen until the kernel has finished booting, because it is a program, not the kernel, which brings this interface up (and knocks the 0bb4:0ff9 "off the air"). This will not happen - can not happen - until about 7+ seconds after the boot.

Because the bootloader must do a little housekeeping and load the recovery boot image, the kernels clock is a little bit delayed from when you press the Vol-Up button on the phone; moreover, the PC will take a little bit of time before it makes a kerplunk noise, so you will never see the ADB/Composite interface appear until at least 7 or 8 seconds.

I believe you that you are seeing "something" at 3-4 seconds - that is the Mass Storage Interface coming alive midway through the kernel boot.

bftb0
[Droid Eris Android Development] mortymouse:
That is correct, I am unsuccessful over and over.
[Droid Eris Android Development] Eoghann:
Has anyone tried creating a pared down instruction list that removes everything "non-essential" based on the success reports in this thread?

It might be interesting to do that and see what is left and whether anyone who has already achieved root could repeat it that way.

From a quick skim it seems that even stock SD cards have been successful in a few cases and ejecting the SD card prior to HBOOT may not be necessary. Plus theres a question over whether the timing even matters. It would be easier to start with a shorter list of requirements and vary one element at a time for testing purposes.
[Droid Eris Android Development] djg57:
I'm running Win7 x64 Professional - It works just takes a lot of patience and some luck.
[Droid Eris Android Development] mam4983:
If this is the case then what determines if the adb interface comes up or not? Because at this point (assuming the timing doesn't matter), the only variables are OS, drivers, and the sd card. If those are the only variables in the equation then we should be able to get this working 100% of the time by determining what OS, drivers, and sd card to use.

Unless it just comes down to dumb luck on whether your phone works with this method or not...
[Droid Eris Android Development] gnomesarealive:
Has anyone with a refurbished Eris done this successfully?
[Droid Eris Android Development] k2pro78:
Unable to run RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver on Vista, tried compatiblity mode and nadda, Vista error or User error?
[Droid Eris Android Development] HanSolo2012:
My first Smart phone was this eris phone i got a week and 1/2 ago

before that i was rocking the razor for almost 3 years

this is a easy way it just takes time

i think you should go for it
[Droid Eris Android Development] Eoghann:
Well that's the question isn't it? And the only way to get an answer would be to approach this scientifically. In other words work on one variable at a time and confirm it's relevance.

In order to do that we'd need people who are prepared to root and re-root their phones, removing one element from the list each time. Most people won't want to risk root like that.