yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] Cyostrife:
thanks i think it worked i got:

List of devices attached

HT9C1HG01266 device

that look about right?
[Droid Eris Android Development] iornslave:
Well, just reporting...

trying under mac OS gets me nowhere, no single sign of anything not even a slight delay in the loop process. tried about 50 times. I will try on win 7 tomorrow and see what I can get. I may try on my wifes slow and broken PC tomorrow. (bad ram I believe). would'nt that be interesting. if it worked. then if no luck I have an XP setup I will try it on.
[Droid Eris Android Development] devlp1213:
yup means ur drivers are working correctly :) and tht is the one u need to get it to so in recovery but the problem is getting it to do just tht
[Droid Eris Android Development] Cyostrife:
i see. it wont show up.. is DC sure he had NOTHING on the Sd card?
[Droid Eris Android Development] devlp1213:
that what he is saying.... think i might go a freah class 4 sd since that one guy said he used....
[Droid Eris Android Development] Cyostrife:
all i have at the moment is my stock SD and he does have Recovery running in his vid.. idk maybe its the sd card?
[Droid Eris Android Development] Cyostrife:
"Make sure you have added to the inf file ; HTC Eris"

how do i do this?
[Droid Eris Android Development] laxattack:
do the sdk setup.exe first
[Droid Eris Android Development] Cyostrife:
i did i just dont know where the file is...
[Droid Eris Android Development] iornslave:
I wonder if we could all time our attempts from the press of vol up untill SD insertion. you could start fast and then increase the wait time in 10ths of a second until somebody gets the device in ADB. then using that time as a guideline everyone can can shoot for the same time and see if it can be duplicated.

it all comes down to when the phone appears in offline mode and then popping in the SD card to keep it from stopping by way of diversion per say.

I will try to mess with the idea tomorrow. if anyone wants to participate it would help. it's better then just ramming the card in at random times which ends up with the odds of someone playing the state lottery.

I got the idea from reading about the HTC incredible root method. they believe that the phones adb is turned on, then off while loading recovery mode and that inserting the SD card right after ADB is turned on stutters the phones process and causes it to skip the turn off.
[Droid Eris Android Development] Cyostrife:
my phone doesnt show up in offline mode. i dont see that anywhere in the CMD
[Droid Eris Android Development] tereg:
The closest that I've gotten is while I'm running the loop and booting into recovery, I can see usually 2 or 3 iterations of the device being shown as "offline" and then nothing.

Here are the steps I took to do this.

I followed the alternate method mentioned here: www . unrevoked . com/rootwiki/doku.php?id=public:adb_in_recovery and adapted it for the Eris.

I will paste it here for brevity

So, I start in recovery mode with the SD card in, meaning, I go into the bootloader (volume down + power) then go into recovery knowing it's not going to work. I am using the stock 8gb SD card that came with the Eris. Then, I hit Volume Up + Power to bring up the selection menu in Recovery.

Before I make a selection, I have two Windows XP command prompts open to the SDK tools menu. One prompt window is running the loop.bat file, the other one has the command

>adb reboot recovery

typed in but not entered.

Then, I will press Power to reboot the phone (remember, in Recovery with the menu up, and reboot is selected by default). As soon as I hit Power, I take out the SD card.

During the normal reboot, as soon as I see the command prompt window running loop.bat display the device (i.e.

List of devices attached

HTxxxxxxxxxx device), I execute the command adb reboot recovery in the 2nd command prompt window.

The phone will go black with a dim light behind it, then go black with no light behind it. If I push the SD card in just before the screen goes black with no light behind it, sometimes I will get about 2 or 3 iterations while on the white screen with 3 androids on skateboards of

List of devices attached

HTxxxxxxxxxx offline

Maybe about a quarter of a second for each iteration until I hear the Windows XP prompt that indicates a device has been plugged in, and then it goes back to just "List of devices attached" with nothing underneath, and then into the recovery red triangle screen.

Now, I want to differentiate this from the moment right after I execute >adb reboot recovery and then stick the SD card in, sometimes the loop.bat file will show a string of iterations showing the device as "device" then a few brief "offline" iterations, then nothing, then as the screen goes pitch black then up to the white screen with 3 androids on skateboards, that is when I see the 2 or 3 iterations of "offline".

Not sure this is getting anywhere, but I did want to report that.
[Droid Eris Android Development] iornslave:
Cyostrife: offline mode is when the Eris shows up on the loop as a device.

like what Tereg has reported its exactly as suspected.
[Droid Eris Android Development] Cyostrife:
alright ill be back tomorrow to work on this, it might have something to do with the quality of the SD card, but i cant be sure
[Droid Eris Android Development] npsmith:
So 40+ pages and nobody else has gotten it to work? I smell some XXXX...

Mod Edit: Refrain from foul language and respect other members in accordance with XDA rules, take as a warning
[Droid Eris Android Development] bdt1995:
Well, hey, even if it is a fake, it could still get us to find a way.

It could be a situation where he says he got it to work, lets us try to get ours to work, and then finally someone gets it to work and says oh it works this is what he forgot to tell us to do! then he gets root and everyones happy and he seems like a hero. Either way, we win.
[Droid Eris Android Development] Cyostrife:
true either way it could help
[Droid Eris Android Development] Dc_striker:
haha go head and flame me. I'm about to post the right way to do it know and look at the to videos i have on this thread no bs here buddy.

I don't fake videos
[Droid Eris Android Development] Wongidool:
[ insert giddy nerd glee scream here ]
[Droid Eris Android Development] bdt1995:
I know, i personally believe you, im just pointing out that theres no real reason to dwell on that topic. Any progress on reproducing the results for us? That would just be super! :)

edit: sorry, didn't realize you said you're working on it right now.... yay!
[Droid Eris Android Development] Dc_striker:
updated now
[Droid Eris Android Development] Zerethusta:
So the stuff to add to the driver, is that for windows only, or linux as well?
[Droid Eris Android Development] bdt1995:
Testing now, gonna report back in a few with results. Thank you!

EDIT: Results after 30 trials: Failures.

15 with a 8gb sandisk, not sure about class cause i had it back before i had my eris.

15 with pny 8gb class 4.

I formatted sd card with the default fat 32 with 4092 or whatever allocation size.

The trickiest part is getting it to pop out at the exact time it starts scanning for the card.

Anything im missing? I really want this to work.
[Droid Eris Android Development] Wongidool:
You do realize if this is something that is for sure, and I don't have many doubts, you will be like a god right? Wishing I get out of work early so I can try this!
[Droid Eris Android Development] Hairston:
I forgot that my digital camera can take video, duh. I can make one too if you want.

What would you need? Would a shot of the HBOOT screen showing 1.49 S-ON and then hitting <VOL UP> booting into Amon_RA recovery (to prove root) do it?

It really sucks that this procedure is such a living hell. Blame HTC for locking these things down so tightly in the first place. This is my first rooted phone and being able to play around with the custom roms and to do an image backup is pretty cool.

I see a lot of people in the Incredible root thread using the same basic method to root are having a tough time too. Misery loves company I guess.

EDIT: Head over to the Incredible root thread for more tips. There is a lot of great info especially with Windows drivers etc that are revelant to this thread.

h t t p : / / xdaforums.com/showthread.php?t=699088
[Droid Eris Android Development] Dc_striker:
which way did you use to get it into recovery
[Droid Eris Android Development] Hairston:
Check out my previous posts, I tried to include as much information as I could. It might be scattered over multiple posts, I'll try to combine them when I have time.

The only thing different I did from the procedure outlined for the Slide was that I started with the SD card initially out. I also never did the loop thing, I just watched Device Manager for the "Android Composite ADB Device" to show up. When it finally came up I did an "adb devices" just to confirm it was there. It took about an hour of constant battery pulling, but it finally came up.

After that I followed the rest of the instructions like pushing the fake payload (which I messed up twice because I was hitting Enter too early, thankfully you can re-try it). When I finally saw the "Clockwork Mod" screen come up I knew I hit pay dirt.

I am hesitant to try to replicate it again because I do not want to further damage my SD card slot. I got a buddy who is in the same boat with the leak. I'll contact him and see if he would be willing to give me a shot on his phone to try it again.
[Droid Eris Android Development] Dc_striker:
My way i tired it multiple times and it worked its hard but you get use to it lol
[Droid Eris Android Development] jvward:
Hey Dc_striker,

I believe you man :)

You used the PNY Class 4 8 gig SD card right?
[Droid Eris Android Development] jvward:
Also another quick question about your instructions.

do you wait an additional 3-5 seconds after system sound because I am already on the recovery screen by that point?
[Droid Eris Android Development] homaygfresh2000:
So, you don't turn on fastboot at all?
[Droid Eris Android Development] thisismyanonymousaccount:
Striker, do you remember if you had wifi enabled on the last boot of the phone when you won the race?
[Droid Eris Android Development] HanSolo2012:
will be testing this sd card later today

ill post my results

http://www.walmart.com/ip/8GB-Secure-Digital-Micro-SDHC-Flash-Memory-Card/14550241#ProductDetail
[Droid Eris Android Development] jvward:
Noodles is famous this must be true!

Honestly,

So lets say this **** works, but it works rarely. And it some how works for person X. they get happy and post on the boards and their not 10000% super devs so they dont understand exactly what went but that it went on. So they let us know and us each being half normal folk & half internet trolls cant 100% believe them. I honestly don't know where i am going with this, but I fell these guys are probably not bsing but who knows.

Either way they deserve the benefit of the doubt and everyone who does not believe this should explore other options.

Because unless these guys are part of a walmart sleeper cell on XDA and are secretly trying to promote the sale of 8GB PNY class 4 cards they have no reason to BS us this much.
[Droid Eris Android Development] Hairston:
Geesh guys if you don't have anything constructive to post and get all off topic then why post it?

Lol @ Walmart sleeper cell. I actually got a chuckle from that. I only went to Walmart because I knew they would sell the cheapest and crappiest card on the planet.

Anyway, so would that video I suggested in my last post showing the HBOOT 1.49 S-ON booting into Amon recovery help to ease the tension? If yes, I'll make it in a heartbeat. I just want to prove that this is possible. Whether you choose to pursue it is your choice.

Like Striker's my HBOOT says:

PB00100 XC SHIP S-ON

HBOOT-1.49.0000 (PB0010000)

MICRO-0111

TOUCH PANEL-MELFAS_45_17

RADIO-2.42.00.04.12

Feb 8 2010,00:08:56

I was on 2.1v1, then I flashed 2.1v2, and then v2.1v3. I have no idea if the HBOOT version changed between those leaks.
[Droid Eris Android Development] HanSolo2012:
100+ tries for me 2.1 v3

i believe the same card as you

well the one i got was this

http://www.bestbuy.com/site/PNY+-+2...1&skuId=8351623&st=sd card&contract_desc=null

i just debating on spending another 28 bucks for something that might work

did the 512k format and the format op suggested

dont know what im doing wrong

about to take you up on that coffee
[Droid Eris Android Development] Sjflowerhorn:
has anyone been able to get this to work aside from the first 2? If not where are the original 2 located at? You guys can start taking trips to them since they got it working. ROADTRIP. and if anyone in the South Jersey area would like a second mind to help make the attempt, im currently rooted (s-off) but i will lend any helping hand and info i can. I would like to be there when they crack that dirty little leak open.
[Droid Eris Android Development] bftb0:
DC_striker,

I see you put up more detailed instructions.

You were attempting to repeat the original exploit by flashing the stock recovery (leak V3?), and attempting to duplicate the original rooting.

Were you able to REPEAT the original hack?

I guess what I am asking is, are the newly updated instructions a result of you DUPLICATING the original event, or you just remember it better now?

bftb0
[Droid Eris Android Development] Hairston:
I posted a crappy You Tube video with my digital camera showing the HBOOT 1.49 S-ON screen as well Amon_Ra recovery, Evil Eris, and SetCPU on my phone.

I tried to keep the phone in full path of the camera at all times so you can't accuse me of swapping phones in the middle of the video like some of you did with poor Striker.

http://www.youtube.com/watch?v=uHD0GdOMhtE
[Droid Eris Android Development] Sincidius:
Video looks legit (though I never doubted that this works or previous videos) It is clear as day. Congrats on getting this to work. Looks like I'm adding to my 127 attempts when I get home today.
[Droid Eris Android Development] HanSolo2012:
same here

was this the card Hairston

http://www.bestbuy.com/site/PNY - 2...3&st=sd+card&contract_desc=null&ref=39&loc=01
[Droid Eris Android Development] Hairston:
Lol, yup. That's the card. I remember the National Geogrphic thing on it.

Anyway, I wouldn't go nuts over getting the perfect card. I truly believe this is more luck than skill (with my lack of skill I am proof of that).

I sincerely wish you leakers good luck. :)
[Droid Eris Android Development] bdt1995:
Hey hairston, are there any tips you can add to strikers list? Ive tried a couple hundred times and its still failing.
[Droid Eris Android Development] bftb0:
At this point, nobody really cares whether you got it to work or not - they've tried everything suggested, and nobody can duplicate your results. That's not saying anybody is lying - it's just pointing out that a method that works for practically nobody isn't worth much, and generally just wastes folks time.

(BTW, If you want, I'll produce a video with the Amon_RA and a custom ROM with the 1.47 bootloader. I could do exactly the same with the 1.49.0000 bootloader, but I don't want that thing touching my phone. The exploit has never worked on my phone.)

What matters to the folks that are following this thread with some interest is whether or not they can do it to their own phones.

If it should turn out that it is possible, but at extremely low odds, then it really is immaterial whether you got it to work or not. It's sort of like a lottery winner claiming, "Look, I won the lottery, so you can too!". Theoretically correct, but really bad advice to 99.99999999% of the people who are within earshot.

If you want to help make this method more successful, stop with the videos already - as they really don't prove anything at all, anyway. Instead, if you think you have some special insight into how to make it happen, well then - repeat it. And keep repeating it until you can make it happen more frequently. That's what people still paying attention to this thread would value the most.

If you were able to get a rooted ROM onto your phone, then you can certainly re-install (via flash_image) the old (non-rooted) recovery. If you are unable to reproduce your initial result, no worries... just put Amon_RA back onto the phone with flash_image and call it a day. (After you've helped us out by reporting, "Guys, I've tried it and can't get it to work").

Not ranting here (or at least I hope nobody takes it that way) - just trying to encourage you to add value. Further videos are not going to add any value.

bftb0
[Droid Eris Android Development] Hairston:
I agree the videos are useless, but have you read the posts where people were calling Striker a fraud and then calling me lazy for not posting a video? On another forum I got called just another "sockpuppet" for not providing proof. LOL, what to do. Videos or no videos, doesn't matter, I still fail.

And if what you are saying is possible that you can flash a HBOOT 1.49 S-ON over a 1.47 if you have root, then neither of the videos hold any water anyway. Guess we should all give up and go home.

If it wasn't for Striker posting here initially with his videos, I would never have been able to root my phone. Thanks DC, I owe you.

In all seriousness, let's just get on with the task at hand. I'm all for constructive posts. I still need to compile a complete list of what I did the same and what I did different than Striker's method. The bottom line is that all known methods still suck at multiple levels and you seem to be right about the "winning the lottery" thing. If it sounded like I was bragging or something that was not my intent at all. If I offended anybody I apologize. :o
[Droid Eris Android Development] bberryhill0:
^^ Thank you.
[Droid Eris Android Development] bftb0:
Hairston,

no worries - I wasn't trying to bust your chops; if anything, I want to encourage you to try and test some more (if you are willing).

I want to see this succeed, if it is possible to do so.

There are a couple of chaps (a few posts back, I'll find the links and add them here in a little bit) that are testing things the right way - they devise a test plan, and then very methodically work their way through it.

If anything will shed some light on this, proceeding in a careful and methodical way seems like the best approach. There's also a bunch of statistical things to bear in mind - more on that later.

bftb0

[ Edit 1]

Something close to that, but not quite. If you have the 1.49.2000 S-OFF ("root") bootloader on the phone, you can use fastboot to overwrite the 1.49.2000 S-OFF bootloader with any bootloader of your choosing - but you can't do that with any other bootloader, it has to be an S-OFF bootloader for the phone to allow fastboot to work that way. So, if you had a rooted phone to begin with, you could do some useless things as a demonstration, for example: Install Amon_RA recovery, flash a 1.5 OS to the phone, boot into fastboot mode and then use fastboot (on the PC) to install the 1.47 bootloader. In a video, that would look like a 1.5 phone that was mysteriously rooted so that the recovery boot had been replaced - but of course, that's not what happened.
[Droid Eris Android Development] Wongidool:
I've got a few more questions, they probably have no bearing on the outcome of the tests, but I'll ask anyway (what's the harm at this point, really?).

1) What charge level was your battery at when you got the root? I don't need an exact number (68.133454%), but a ballpark would be nice (full, med full, etc.).

2) Someone previously asked if wifi was enabled when you acheived root. I'm curious how this could affect the process since I don't believe wifi is up at the reboot screen but I could be wrong.

3) What were your PC connectivity settings? Always ask, charge only, disk drive, or HTC Sync?
[Droid Eris Android Development] :
Yea, the third option wongidool posted is vital for us to know, if we are to attempt to root.
[Droid Eris Android Development] dbnaruto:
Just wanted to day I rooting (no pun intended) for you all. I have tried the old and new guide to no avail but I still believe this can work :D . Just wanted to show my support, you rock DC_striker
[Droid Eris Android Development] It IS Lupus:
in the command prompt type this without the quotes "cd C:\android-sdk-windows\tools" or what ever and where ever you placed/named the android SDK then type loop
[Droid Eris Android Development] HaRdC0r3:
ok guys another first time poster for you all to hate but I can get the clockwork mod recovery to show after the 2e recovery update.zip install....then i did the root.zip install in clockwork....my problem is this....how do i install superuser.apk without mounting the system and in order to mount the system dont i need su????? this is for my girlfriends eris which i jumped the gun and put the leaks on for the navi....I have a moto droid and have been messing with it since i got it so i am good with adb

NEVERMIND after i rebooted the phone I pushed Superuser.apk to sdcard with adb then just installed with astro LOL....and now i have su
[Droid Eris Android Development] Wongidool:
Holy fraking......*punches wall*

I had it...

It was effing there....

And I lost it....

/sob

"List of devices attached

HT(blaa blah blah) offline"

/wrist
[Droid Eris Android Development] Wongidool:
Can you tell us -exactly- what you did? Even if you followed DC or Hari's instructions to a tee, can you type it out? The more data we have, the better chance we can make this work for everyone
[Droid Eris Android Development] bftb0:
It is possible to unpack the "recovery.img" files that come with the RUU (or OTA http downloads) and inspect the contents. The stock recovery boots have never contained the kernel module for the Eris Wifi, nor are there any of the associated executables (e.g. wpa_supplicant) that help manage WiFi. There is absolutely no credible evidence that wifi works in the stock recovery boots. The same thing may even be true of the mobile network, too.

The main OS (/boot, /system, /data, and /cache) is not operating during the recovery boot; moreover, the recovery boot does not "share" any information with the main OS through filesystems other than certain circumstances where the main OS drops files into /cache (that's how the OTA process works). There is a small amount of information that can be communicated from one boot to the other, but it seems exceedingly unlikely that the settings in the main OS have anything at all to do with the behavior of the recovery boot.

There is a practical issue about "USB debugging ON", though. Since the recovery menu only has a "Reboot" menu item, there are only two ways to restart the recovery repeatedly from that menu: (a) pull the battery and start either HBOOT or FASTBOOT using key combinations (and then go to recovery from there), or (b) go ahead and select "reboot" in the menu, and then from a command window on the PC, do something like

adb wait-for-device shell reboot recovery

In this latter case, what is happening is that the main OS is starting up. If you have enabled USB Debugging, it will come on quite early in the boot process, and you won't have to wait quite as long (for the full boot). But that's the only reason you need it, and it is there only as a practical matter - it is quite unlikely that this setting affects what happens in the recovery boot.

bftb0
[Droid Eris Android Development] bdt1995:
What did you do to get there?! Have you been keeping a testing log?!

Okay how did you get adb to run in recovery?