yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] bftb0:
[SIZE=+2]+1000[/SIZE]

What is needed is to have some folks (that have had prior success) do a lot of trials, doing exactly what you suggest.

Something like this:

1) Start with whatever method you think "works best". Let's say that in advance, you think that you will "win" in 1 out of ten attempts using this "best known" method. Those are not really great odds, so you actually need to about 50 trials to quantify that number a little bit better. This becomes the "control group" for your experiment. Let's suppose you get 4 wins in 50 trials, or 8.0% successes.

2) Then, eliminate one thing - let's say the "eject SD card right after Vol-down to HBOOT" (I guess you would just leave the SD card out until you started the recovery boot). Again, do this about 50 times. If you get zero successes, then it probably IS important. But what if you get 3 successes? That might not be statistically significant. But one by one (50 trials for each experiment, ugh!), stuff will get eliminated if you see close to the same results as the control trials.

3) If you wanted to eliminate all the junk in one go, run the 50 trials by booting directly into recovery from the power-down state, and simply leave the SD card in the slot - don't even eject/replug it. That would be useful if it was found to produce the same number of successes. (It doesn't make the effort any better, but it does uncomplicate it and speed it up a little.)

Note that this kind of experiment needs to be done by someone that has a method which works sometimes, and hopefully with a high percentage of successful attempts - there is no point in comparing the experiment against a control group with 0% success, because the confidence interval is infinite.

I know why this isn't happening, BTW - it's a heck of a lot of work, and, many of the folks that have been successful (especially only once) really don't want to lose root - or spend another two days getting it back. I wish there were more rooters (w/ 1.49.2000 bootloaders) on board trying this - they have no risk of losing root.

I am trying, and would "take my own advice", but can't currently get it to work even once (I'm not using Windows, and am on a slow box with a USB port that may not even be compliant with the USB 1.0 spec).

bftb0
[Droid Eris Android Development] mortymouse:
What files did you put on the sdcard?
[Droid Eris Android Development] bftb0:
That's a pretty good question. Computers are deterministic, after all, right?

Well, yes... sort of. The CPU is completely deterministic.

But, in order to appear to "run as fast as possible", a lot of hardware operations in the full-blown (phone) system rely on processing of interrupts. Rather than poll every hardware device in the system every couple of microseconds (very inefficient), the CPU responds to hardware interrupts when they happen, and works on other things in the meantime.

So, you might be tempted to say - "but wait, I start my phone from the same state every time, why don't all the interrupts repeat at exactly the same time as well?".

And the answer would be - they "sort of" do - but not to a clock-by-clock level of precision. Many hardware devices have initialization control logic which depends on sampling of analog quantities that can be noisy, so they generate interrupts at "roughly" the same time - but not exactly at the same number of clock ticks each time.

And the kernel is free to "postpone" the handling of an interrupt (by a small amount of time, but a large number of instructions), so those tiny little differences in interrupt timing get magnified into even larger time intervals as the computer runs longer and longer - the differences keep accumulating, after all.

I looked at the boot logs of my custom recovery over 20 different boot cycles, making note of the timestamps of certain significant hardware operations. Surprisingly, very early on in the boot, I was seeing two "clusters" of times (for relative times of certain USB transactions - each cluster of times were pretty tight - maybe 3-8 mS of differences in the time values - but the two clusters were 70 mSec apart!. Later on in the boot (~ 7seconds), the inspection of the SD card slot would occur at times that varied by as much as 400 mS!

So, you are right - there is some risk of looking under the hood on this and finding out, after very much effort, that there are no "knobs to turn" which work any better than just doing nothing and hoping for the right result to randomly pop out. That's one possibility; the other possibility is that we discover a knob. (Unfortunately, both outcomes require the same amount of work - quite a lot).

bftb0
[Droid Eris Android Development] tereg:
Going to multi-quote this because this is something that is constantly on my mind.

I'm right with you on this. My mind is constantly thinking about things that I knew were things that I classified as "This is one of those things that probably doesn't make a difference, but I need to report that the conditions of my computer were such" when I first reported what I did to Captainkrtek on how got this to work. I thought of a handful of little things that the likelihood of certain things in my condition set were most likely not even essential to the core steps needed to get the result. I still felt like it was an obligation to provide those things and not leave them out, but I knew that I'd have to do further testing to see if I can test it removing pieces of the fat.

I just haven't had much of a chance in the last couple of days to do some serious testing. When the user who mailed me their "don't-care-if-you-brick" phone gets here, I intend to do more of this specific type of testing if I can get some successes.

I am willing to do this level of testing. I seriously am. If the person is all right with me having the phone for this kind of testing, and I can focus my energies on testing (which will take time away from troubleshooting other people's issues and keeping people posted) I am willing to put the time and effort into it (given that I can first get some successes)
[Droid Eris Android Development] dawynkoop:
I'd be willing to do a bunch of testing to sort it out to the fewest steps necessary as well, I just have to actually get it to work once first. I've ordered the 2GB Nat Geo Micro SD card for store pickup at best Buy, I'll be stopping in to grab it on my way home from work. Once i can get it to work repeatedly I'll test each variable and see how many steps can be cut out.
[Droid Eris Android Development] Zalatorisaurus:
I've found something that's pretty interesting. Or it seems interesting. Then again, I don't know my way around here yet. Anyway, yesterday I determined that I have the 2.1 leak version 1 (I found this by comparing the kernal version, build number, etc.), but there are some things that don't seem to add up.

First, I have experienced none of the infamous bugs that were on version 1.

Second, when I booted into recovery (volume up+ power), I noticed that my hboot was 1.49 and not 1.49.2 or 1.492 (or whatever the number is).

Third, when I booted into fastboot, just to see if it would work, I got the android man with the /!\. After a couple of button presses (volume up+ power repeatedly), a blue screen came over the android man and /!\, it asked various options. The one that stood out was if I wanted to run update.zip. Could I run the ota or another update file though this and have it install successfully? Can someone shed some light on this for me please?
[Droid Eris Android Development] cptkrush:
this is normal behavior, aside from the fastboot part, which can be explained as what i like to call a "recovery loop" where your phone got stuck in recovery mode. the blue screen is the recovery menu.
[Droid Eris Android Development] orkillakilla:
I'm trying this as I type. Formatting SD card right now, taking a good while to do. I'll be using the stock Scandisc class 2 8gig sd card and windows vista home premium 32bit. I'll be posting my success (i can only hope and pray :D ) when/if it happens. Wish me luck all!!
[Droid Eris Android Development] Zalatorisaurus:
Hmm. I thought so, I can also boot into recovery without the leak starting automatically. It asks me to start recovery, so I press that, and I see something else flash under it but the leak update starts too fast for me to see waht it is. Do you know what that is?
[Droid Eris Android Development] carycooke:
I thought the boot loader 1.49.2 was a root boot loader version not sure
[Droid Eris Android Development] Gambinno:
Severly decreased battery life?

I hate to get off topic gents but is it possible that we could be causing problems with the battery from all the battery pulling (maybe while the usb is still plugged in). Before I use to get a full day out of my battery, and now after I've spent the last 2 days nonstop trying to get this method to work I barely get 5 hrs out of it.
[Droid Eris Android Development] cynikalJ:
I have a question. Do we absolutely have to flash the ruu or can we root with leak3. I have tried for 2 days on win7 64-bit and leak3 with no success :(
[Droid Eris Android Development] DjCalvin:
Been at this for a few days with my nat geo 2gb pny card without any luck whatsoever.. what I dont get is what exactly is the "placing the card in a a certain time" (timing trick) doing to allow the phone to be in recovery mode...

Just trying to understand the logic behind it, thats all..
[Droid Eris Android Development] joebob213:
The logic behind it is it makes the phone "hiccup" at the right moment and "forget" to unload adb when you enter recovery mode. Whether the card has anything to do with it is up for debate but so far i think all who were successful did something with the card during the process.
[Droid Eris Android Development] mam4983:
Thanks for the response. I haven't had any luck getting this work, so I decided to go ahead and pick up the PNY sd card just to remove one additional variable on my end (I have been using a Sandisk 8GB card). Hopefully we can all figure this out together.
[Droid Eris Android Development] orkillakilla:
Ok so on step 6, I've installed the driver when the phone was in fastboot usb, then i restarted the computer as prompted. When i try to install the driver when the phone is booted normally to sense ui, i get this error "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 32-bit system."

I have booted vista to not enforce digital signing or whatever. I don't know what to do here.

Apparently now after 10+ tries my phone goes directly to recovery when i power on with end + send and skips fastboot all together....
[Droid Eris Android Development] bftb0:
You are correct.

There have been only two bootloaders in the wild whose version numbers start with 1.49:

1.49.0000 <== This is the bootloader that shpped on all the "Leak" ROMs

1.49.2000 <== This is the ROOT-ROM bootloader (aka "God-Mode" bootloader)

There has never been a "1.49" bootloader - that's just folks being lazy in their posts and dropping all the zeros.

bftb0
[Droid Eris Android Development] bftb0:
I can't say that I have experienced the (battery) problem that you are having, but I will say that in all this battery-pulling I've done, I have come across three different unusual conditions:

1) On four separate occasions, my phone kept on running after I pulled the battery. The USB cable was plugged in, so I suppose that it was getting power from the USB. On one of those occasions, it turned off after a couple of seconds; on another, it turned off when I did the Vol-up+End to go into the menu, and the other two times it continued to run indefinitely until I yanked the USB cable.

2) One time I had the phone (in a power-off state) come alive and start booting when I inserted the USB cable.

3) One time my phone appeared to be absolutely dead - could not power it up into any mode at all. Pulled battery (but left the USB cable in) and replaced it - no go. Pulled the USB cable and the battery, waited 10 seconds, pressed all the buttons, re-inserted the battery (but no USB).... and it booted up just fine. Whew! (That was a scare).

So, I suppose given these sorts of flaky behavior involving power, maybe it is possible to wreck the phone or the battery - someone reported last night that they had bricked their GF's phone somehow (n2imagination, iirc?). I hope he is still alive. ;)

bftb0
[Droid Eris Android Development] mortymouse:
I have had every one of those things happen to me today alone. I think I am going to give up for now. I have followed everything perfect, I have the NatGeo card (picked it up last night), I keep trying and now I am getting to the point I dont care anymore. Until there is a for sure way to do this, I think I am done. I will just keep watching the thread.
[Droid Eris Android Development] DjCalvin:
I'm right there with ya, Im more pissed off at this phone than I should be.. its only a device.. root was nice while it lasted for me anyways.

My nat geo sd card will no longer eject out or in after doing this for 2 days straight... (multiple sd cards affected. have to pull em out with tweezers)
[Droid Eris Android Development] Gambinno:
I agree....While I believe this method will work after x number of tries, I think the chances to damage the phone far outweigh the chances for a successful root. I'll wait for a more reliable method.
[Droid Eris Android Development] dave.viola:
I'm encountering a similar error at this step: "The specified location does not contain information about your hardware."

Also, the android_winusb.inf file is in android-sdk-windows\usb_driver, not android-sdk-windows\tools\usb_driver as is specified in the tutorial. Is it safe to assume this is just a typo?
[Droid Eris Android Development] BlazinDANDAMAN:
Man, I want to do this so bad. But I only have one Eris, and no money to buy a new one. With my luck, I'd be one of the ones it doesn't work for. Patiently waiting a more reliable method. If none in a few weeks, I might breakdown and try it.
[Droid Eris Android Development] orkillakilla:
So after x number of tries (lost count) my phone now boots directly into recovery when pushing end + send and skips fastboot all together. I tried to timing method here but still to no avail. any ideas why its going directly to recover?

Just tried to boot normally and it went to recovery. had to choose reboot system from recovery to get it to boot back to sense
[Droid Eris Android Development] orkillakilla:
yeah i figured that out too. Still, I try to time it right, but I don't know if its not working cause the drivers aren't installed correctly or if im just not that lucky. (knowing me its both :) )
[Droid Eris Android Development] Zalatorisaurus:
Has anyone tried this with a 2gb sandisk? I'm about to try that with v1.
[Droid Eris Android Development] orkillakilla:
Ok so i deleted the drivers for the device in device manager and reinstalled them and everything went ok there. Hopefully making some progress.
[Droid Eris Android Development] nesgodawg:
I'm sure this has been asked and I apologize for reasking, it's hard to go through 53+ pages and find the answer.

But if you have OTA 2.1 and no leak with boot loader 1.49 then these are the same steps in which to take, correct?
[Droid Eris Android Development] Dc_striker:
The TYPE of sdcard doesn't affect it. It should work with any sdcard
[Droid Eris Android Development] mortymouse:
Yep, if you have 1.49 this is the only way to do it so far. Some have it really easy and others like myself have given up.
[Droid Eris Android Development] jdog94:
there was an edit to the loop.bat posted a few days ago i cant find it now can someone post it please
[Droid Eris Android Development] dave.viola:
Which drivers specifically? Did you follow this procedure:

androidforums.com/htc-droid-eris/40790-cannot-mount-usb.html#post310521
[Droid Eris Android Development] orkillakilla:
yeah the drivers are installed correctly now. Now i just can't get it show up in adb during recovery (most everyones problem i know :) )
[Droid Eris Android Development] n2imagination:
+10000!

I quit because of this very reason and I think all who look into this need to know the definite risk of physically damaging your phone with all this wear and tear. IMO it might be best for most to let the geniuses that know what they are doing bang on this a while to refine the process so it can be more repeatable with less attempts before giving this a shot x times.
[Droid Eris Android Development] dave.viola:
Hmm, I tried that and got the same error message as before. I did confirm that I can communicate with the phone following the instructions in the OP, so hopefully it doesn't make a difference anyway.
[Droid Eris Android Development] tereg:
It is a typo, and it has been fixed.
[Droid Eris Android Development] orkillakilla:
Should adb be able to recognize the phone when in bootloader? cause mine doesn't...
[Droid Eris Android Development] tereg:
Regarding the battery pulling: the only other alternative I can think of would be instead of pulling the battery after a failed attempt at getting into recovery, you would pull up the menu in recovery (Vol Up+Power) and do a reboot, then power off the phone, then start the step again. Edit: It takes a bit more time to test, but that way you wouldn't have to keep pulling the battery out physically and stuff.
[Droid Eris Android Development] Realm:
I guess its time for me to get the sd card with the most success rate
[Droid Eris Android Development] Dc_striker:
I have tired it with 4 diff sdcards.

Its all about the timing
[Droid Eris Android Development] listyb01:
For a faster reboot without pulling the battery...

When in recovery hold end and up volume and choose reboot from the recovery menu. Then go to your open command window and hit control+c to stop the loop. About 30 seconds after the phone boots to the androids on skateboards (white) screen type this command in your command window...

adb reboot bootloader

And further testing is needed to determine if we even need to go in to hboot for this method to work but you can reboot directly in to recovery with this...

adb reboot recovery
[Droid Eris Android Development] HanSolo2012:
@ECHO OFF

:TOP

adb devices

GOTO TOP

is the edited one

:TOP

adb devices

GOTO TOP

is the regular one

just right click and go to edit and replace

Really suggest that the loop.bat should be taken out of tutorial

people are pulling battery as soon as they get to /!\ screen

and the device not showing up

really should go something like this

sd card pull

/!\

count to 5-7 when on the /!\ screen

then run

adb devices

if nothing shows up start over

this will give people more time on the /!\

and stop all the people from posting the adb deamon errors
[Droid Eris Android Development] snyluc13:
Wow thank you for the tip gonna give it a try in the morning

Sent from my Eris
[Droid Eris Android Development] HanSolo2012:
if anyone around or near buffalo ny need help with this shoot me a pm
[Droid Eris Android Development] lostpilot28:
Can you elaborate on this? SD Card pull is the first part to go into Fastboot USB, right? YOur instructions don't say anything about when to put the card back in.
[Droid Eris Android Development] vandykky:
If anyone is in chicago area that can do this I would really like some help, can't get it to work on my wifes eris. I know that's a lot to ask but maybe someone is willing, pm me. Thanks!
[Droid Eris Android Development] __arock__:
So I am kinda confused now. Are we supposed to start counting to reinsert the sd card when the android skateboard guys are on the screen or wait until /!\ is on the screen? Or have people had luck doing it both ways?
[Droid Eris Android Development] DMOs:
Count me in, I'm ROOOTED

Great write up and everything you guys do on this forum. I am a newbie and want to let you all know this can be done will little experience. I have been reading for awhile now and followed the steps to a T. If you guys are getting stuck on the SD Card timing going into recovery, download the .WAV file. It helped me and I went from 15-20 times before to 2 tries after. Listen to it and follow it word for word. Thanks again and I will offer any help I can. :D
[Droid Eris Android Development] tereg:
These are (Edit: some of the) things I intend to run a series of tests of with the phone that is being sent to me. The person who sent it to me gave me the green light to use it for as long as I need to. So, I intend to get to the core of what is necessary and what isn't necessary.
[Droid Eris Android Development] lostpilot28:
Congrats. How about posting your PC specs, what SD card you used, etc. I'm pretty sure that 100% of us trying this can read, and most (I hope) can follow directions to a T. That being said, it seems that 95% of us still can't get past the Timing Step.

I've personally tried the instructions "to a T" about 200 times. Then I started trying variations on that entire step. Still no luck.
[Droid Eris Android Development] refthemc:
Can someone please make a Youtube video already? lol 57 pages later
[Droid Eris Android Development] bkfist:
I tried this for about 20 minutes on multiple reboots (although with a 2GB Lexar SD card from an old blackberry) with no luck. (I fried my PNY last night attempting to root...)
[Droid Eris Android Development] DMOs:
PC Specs: Windows XP 2.5 Ghz 2 GB Ram crappy little Acer laptop.

SD Card: Same as everyone, BB 2GB PNY Nat Geo

Maybe the only difference on the timing is after I put back in the SD, I waited about 3-5 sec before I noticed the phone being recognized, before, once I got the /!\ I was pulling out the battery and trying again. That and counting faster than before I listed to the .wav

Try waiting after you put in the SD till maybe 10 sec and then pull out the battery. Maybe we've been thinking it didn't take too soon.
[Droid Eris Android Development] tereg:
I think it's great that you've gotten it to work with different SD cards. To me, that just means that more testing needs to be done and we need to have other users have more successes with different, various cards. We need more confirmation from other users that this is the case than what is currently being reported.

The tutorial specifying what card has been having the most success in no way means that we are saying that you absolutely have to use the SD card linked in the tutorial (even though it was originally worded that way when it was first drafted). If more people can find success with different SD cards, the tutorial will reflect that change.

The key for me is finding some semblance of a reliable pattern or some semblance of confirmation with what you are saying.
[Droid Eris Android Development] Zalatorisaurus:
I'm stuck on reinserting the sd card and seeing the htxxxxxxxxx number on the command prompt. The htxxxxxxx number never shows. I assume I don't have the timing down, but I noticed that the htxxxxxxx number appeared when I loaded sense ui by accident. Is that normal?
[Droid Eris Android Development] tereg:
Check to make sure USB debugging is turned on if you can't get it to show when you're in Sense UI
[Droid Eris Android Development] pabent:
Shortcut...

http://de.codeplex.com/releases/view/47457
[Droid Eris Android Development] Realm:
My phone shows up when i type:

While I'm in fastboot
[Droid Eris Android Development] thenestor:
Why is this the first I'm seeing of this? :eek: This is an awesome program!!!
[Droid Eris Android Development] devlp1213:
lol hasnt done much for me xD
[Droid Eris Android Development] Nikolai2.1:
Ugh

Im fixing to give up on rooting until something else is found.

PNY 2GB National Geo card

Windows 7 32bit

ive tried just about every bit of timing, plugged the card and cable in at the same time, nothing.

The closest ive gotten is when device manager took 5 seconds to refresh.

and help would be greatly appreciated
[Droid Eris Android Development] Realm:
bizillion tries and still nothing