yashsingh1/xdaforums huggingface dataset:
[Droid Eris Android Development] JAS_21:
I finally got the 60partitions file on my sd card. I had to unzip it with 7zip, and then I had to extract the image using winrar. Then I was able to write the image to the card using imagewriter.

After all that I still have been unable to win the race.
[Droid Eris Android Development] ThorSkaagi:
Ok, how do you run fdisk on XP? If you can't, how can you partition it like everyone says?
[Droid Eris Android Development] sydtrakked:
would anyone be willing to make the partition image for a 1gb card that I could test?

I have an old 1gb card and the stock card and I'm really broke right now so I can't go and buy the 2gb PNY.

Would like to test the partition method to see if it works on cards other than 2gb.
[Droid Eris Android Development] JAS_21:
I didn't use fdisk.

I just downloaded the dd image file, and used imagewriter to write it to my sd card. I had to download imagewriter, 7zip, & winrar.

After I wrote the image file to the sd card, it said it was successful. I'm not 100% sure if I did everything correctly though, since I still cannot seem to get adb to recognize the phone in recovery.

Edit: I'm running windows7, but it should be same on xp.
[Droid Eris Android Development] kp432:
Maybe 3 out 5 times when looping I get damonerror any suggestions thanks
[Droid Eris Android Development] mortymouse:
OK, so after trying on both of my Eris's for about 100 times each and every possible way, I got replacement phones yesterday (yes they are both 2.1 with the 1.49). I got the replacements as I couldn't deal with the silent bug anymore, so as I get them going last night, one has the silent bug when I am calling Big Red, it was funny. Now I have to get another, this is just getting stupid.

Anyway, point is, I tried every possible way last night to get in and nothing worked. I am no longer looking to root, I just want my dang phone to work.
[Droid Eris Android Development] stingbliss:
Edit: Sorry for the rambling post.. if you don't care about the details much, then just be aware that none of what I did here got me into recovery, yet.. it just helped me feel better that my card is actually configured like Anoek's..

Since I had no luck with the "good" card created using 7-Zip to unzip the .img file (twice.. first the zip "shell," then the bz2 "shell") and using the imagewriter prog to write it to the card, I tried going exactly with what Anoek said..

First off, after "burning" the img to the 2GB PNY (and I'm still confused as to why it imagewriter said it was an 8GB image), my card couldn't be seen by my phone to be able to mount it.. I had to go find an SD card reader with a USB jack.. (you can find them on Amazon for $3, but the cheapest I found at the brick-and-mortar Best Buy was $15) for any of my PC's to be able to see the card well enough to manage the partitions..

Anyway, so I downloaded GParted (the 120 meg version, because I had issues with the older smaller version) and burned it to a CD.. booted to that CD with the PNY card all hooked up directly to the USB reader.. (again, because the Eris couldn't read it anymore to mount it)

Pressed [Enter] a few times, and the GUI shell finally came up.. I went to a command prompt (no SU necessary - was already in superuser mode) and typed:

fdisk /dev/sdc

(ymmv on the "sdc" part.. use the GParted program to look at your mounted drive labels, if you're not sure)

From there, I followed the scripted instructions that Anoek linked off to in his post way back on page 97 or 98.. (the first D was apparently unnecessary in my case, but every time there was a blank line, that meant to press <Enter> again, to accept the default value), and it walked me through creating the partitions exactly the way he had done it.. Not sure why the 56 extended partitions ceiling was there (I assume it has something to do with the partition table type), but there is definitely a ceiling.. I pressed N for new partition, and it said, essentially, "no dice."

Wrote the changes to the card, tried to use it to get in recovery about ten times, and... still nothing. :-D

Looking back, I wish I had looked at the imaged card in the actual GUI GParted program to see what it showed there, just to make sure the imaged card was actually configured the same as the fdisk'd card.. might do that today if I get time.. I'd also like to tweak around with some different partition table types (msdos vs pc98 vs mac, etc) and partition types (fat16 vs ext2 vs ext4, etc), just to see what might can be done to try extend the race window further.. IF it's actually being extended..

Either way, props to Anoek, Tereg, and all others who are taking time to make good instructions, and giving me hope. :)
[Droid Eris Android Development] stingbliss:
I leave mine running unless it gets stuck on that error for more than a few seconds..

No need to Ctrl-C it every time you pull the battery.. just Ctrl-C if it happens to get stuck on the error..

When I first started, mine got stuck a couple of times.. no such issues after re-installing the SDK..
[Droid Eris Android Development] szgtr:
Root success!!!

After trying ~30 times with the stock 8GB card I used a RiDATA 4GB card I had and got it on the 5th try. I tried several variations on the timing (slower/faster) and mine ended up being a little faster than the .wav file cadence. I hit it on 3-1000. I was on the 2.1 leak v3 and did NOT do the RUU. You guys rock!
[Droid Eris Android Development] JAS_21:
I'm working on new method.... everyone ship their phones to Tereg. :P
[Droid Eris Android Development] rycheme:
The dd process finished sometime last night. I tried briefly this morning before coming to work, but I was not able to get into recovery. I'll try a bit more this weekend.
[Droid Eris Android Development] zerovertex:
This is what the PNY 2GB MicroSD card looks like in Disk Management after the 60partitions.img is written to the card. Anyone seeing anything different?
[Droid Eris Android Development] walkinonthesun:
It doesn't say anything about being a healthy partition?
[Droid Eris Android Development] jimbonj:
Mine showed the same thing.
[Droid Eris Android Development] jruss:
I have not been able to have my eris recognized in the loop.. but sometimes it shows up under device manager but it can't be used, there is an exclamation point beside it.. does this mean im close to getting the timing right or do i need to fix my drivers?
[Droid Eris Android Development] zerovertex:
I don't think it is suppose to be a "healthy" partition in Windows.
[Droid Eris Android Development] walkinonthesun:
I think that is the point. We want the card to read as slow as possible.
[Droid Eris Android Development] JAS_21:
my sd card shows up as

(F: )

1.83 GB RAW

Healthy (Primary Partition)

Does anyone else see that? Or did I do something wrong?
[Droid Eris Android Development] walkinonthesun:
That is what mine shows now that I imaged my card too. Try to test and see if I can root.
[Droid Eris Android Development] metzy75:
I am having some issue with formatting the card. I have it inserted it into my computer and can see it in computer manager and in acronis disk director but not in my computer and therefore not in the image writer program. In device manager i see this under portable device WPD FileSystem Volume Driver has a code 10 device cannot start. I cant figure out how to fix it.
[Droid Eris Android Development] 13thentity:
Kp, I know that I've mentioned this in the chat, I may have not posted it on the forums, I can't remember.

If you get the daemon error especially on win xp, in your command window type "adb kill-server". This will kill the latest running instance of adb.

I can pretty much guarentee that if you looked at task manager you have mulitple adb.exe listed. Win XP while running the loop will try to start a new instance of adb.exe for each error it encounters, and will eventually stop the script.

To get rid of all of the adb.exe instances, type "taskkill /F /IM adb.exe" in the command window. You will see in the window how many adb.exe processes it killed.

Before running the loop again, you'll want to issue a "netstat" in the command window and make sure that port 5037 is not listed.

Here is an example:

TCP YourComputerName:5037 localhost:4214 TIME_WAIT.

You will have to wait a few minutes before these connections time out. At this point it is safe for you to start running the loop again. You shouldn't get the daemon errors until xp starts spawning multiple adb.exe's and ties up port 5037 again.

If you have any questions, let me know. Most nights I'm in chat.
[Droid Eris Android Development] wag3slav3:
oh my

I've been digging through the stock recovery.img and the reason there's a race condition on this is just cute.

I've found out what's causing the "time window" and I think I can intelligently extend it. I'm hoping I don't need to post a .img file to make this work, hold on for details.
[Droid Eris Android Development] cptkrush:
You may be my hero sir, first all your work on the flash exploit and now this?
[Droid Eris Android Development] wag3slav3:
The scoop.

I'm getting tired, so I'm gonna lay out what I got.

The ramdisk image does this on boot.

So we have the amount of time it takes the system to populate the property:persist table from the recovery image on mmcblk0p2 to connect to the adb.

Once connected the adbd I think it spawns a server for you so once the service drops your still on for the file switcheroo.

I'm looking at some mmc schematics to see if I can do a browndown or something on the mmc1 that will reset the whole bus and give me that extra few seconds to get this up.
[Droid Eris Android Development] rycheme:
Take a look in /sys/devices/platform - you may find what you need there.
[Droid Eris Android Development] wag3slav3:
ponderable

This is the exact same exploit that I used to root my dinc. The adbd service startup takes longer because the system must be mounting and/or ext3fscking the 7GB emmc card when it runs the initial adbd service.

I wonder if adbd is doing some kind of a scan against the mmc and that's what's taking it so long to start.

I'm going to rip apart the adbd binary tomorrow and see what it's messing around with on the mmcblk's. If I can make that first adbd service start take an extra 5 seconds it will show as never running on all the other service adbd stop's in the init,there are 2, one in ramdisk, one in the recover image.

Another thing that helps out on the dinc is that the /dev/block/mmcblk0p2 file system has a tune2fs mount count that's forcing a fsck on each mount operation. This takes and extra .03 seconds or so.
[Droid Eris Android Development] snwagner:
i think this is my first post... but; Tereg, was wondering; can I send my Eris to you, you root it (for a fee) and send it back to me? Would you be willing to do that?
[Droid Eris Android Development] wag3slav3:
geh

I can't find the source code for adbd anywhere. And my git says that the android repo is offline and so are all of the mirrors.

Must be time for sleep.

If anyone has the source files for adbd or a link to them let me know.
[Droid Eris Android Development] tereg:
I believe this is what you're looking for?

http://www.google.com/codesearch/p?hl=en#2wSbThBwwIw/adb/Android.mk&q=adbd lang:c&t=0&d=0
[Droid Eris Android Development] tereg:
I'm still considering this, but I'd rather do this as a last resort. I want to hold off on this for a little bit longer before I say "All right! Send me all your phones!" I'm a little uncomfortable with the notion of "charging a fee" for this. Something doesn't seem/feel right about it. I still need to work through that aspect of it as well.
[Droid Eris Android Development] tereg:
Does it make a difference that default.prop in the same ramdisk image has the following?

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
[B]persist.service.adb.enable=0[/B]
[Droid Eris Android Development] wag3slav3:
Yep

That should work, if it similar enough to the one that htc uses for snapdragon I should be able to figure out what the adbd is scanning for on mmc, and perhaps even use it to create a gold card.

Look for results next week.

The checks for that value come after the adbd recovery daemon starts, but before the service adb stop. They are very close together, so if we can make the initialization of adbd recovery take longer, the service starter daemon will think that adbd is not running yet and either not close it down, or the stop signal won't be heeded because the ipc or whatever the system uses to talk to the already running daemon isn't listening yet.

This is why this method works for this on occasion with certain slow SD cards, the fact that the system does an fsck.ext3 on emmc during adbd initialization on the dinc is why this works on the Dincredible much more consistently. I just need to figure out a listing of what the adbd is actually doing during init, figure out what factors of that we have control over, then use one or several of those to slow down that one service's startup while leaving the other services startups running at full speed.
[Droid Eris Android Development] xnatex21:
I love you.
[Droid Eris Android Development] tereg:
I just wanted to post some (hopefully) helpful dumpstates pre-emptively.

So, I rooted my tester phone, and flashed bftb0's custom stock recovery without making modifications.

So, with each card I started with the phone off and the card in, booted into fastboot, then went to hboot, then did

adb shell dumpstate > dumpstatePreRecovery.txt

Then in a shell command ran

adb shell recovery &

Then waited about 6-7 seconds or so, maybe a little more, then ran

adb shell dumpstate > dumpstatePostRecovery.txt

Note that the timing is most likely not going to be similar to what it would be with just the pure stock recovery because of tools that he packaged into the recovery to allow me to get these dumps. I would have to re-build the recovery with his instructions to get it close to the actual timing. But, I'm wondering if there are any clues we'll be able to find here.

"Good" card

Pre-Recovery: http://pastebin.com/vAcg9gqM

Post-Recovery: http://pastebin.com/8sRnMmmr

"Other" card

Pre-Recovery: http://pastebin.com/gbsfxTg2

Post-Recovery: http://pastebin.com/ZTpFGAAU
[Droid Eris Android Development] octavioromo:
Im trying the 60 partition img on the sd card. just to make sure, does it matter if the sd card is previously formatted (if so formatted to what?) and how long does it take to write the img to the card. im trying this now and it seems as though it will take about 2 days to finish writing the img, same result on two different computers. on a win 7 64 computer it wrote the img in about a min but not sure if that seemed right. thanks so much everyone!
[Droid Eris Android Development] bshiznit:
May be getting refurb Eris

My current Eris touchpad is not working with the n and a keys... so I may be getting it replaced. I've tried this timing trick a hundred times i would bet with a nat geo card and even with a 60 partition dd image written to it with zero success.

Can I dump all of the hardware and software info easily before getting the replacement using adb or similar? If the new works it might be good to note all the differences.
[Droid Eris Android Development] BlazinDANDAMAN:
Aww...man if u do this...you'd make some bank...please take my money...I want u to take it...I just wanna be rooted...I try just about every day to do this...and nada...
[Droid Eris Android Development] Nickboxer7:
I've been watching this thread for a while now and decided to join up and post.

I've tried three cards, the PNY 2GB one mentioned, a PQI 1GB (I think it's PQI), and the stock Eris 8GB one. No luck with any of them getting into recovery. However I did notice once you get to that "!" screen it throws a few files on your card called recovery and such when I look at it in Windows. But it has never said it found my device.

I also took the 2GB PNY one and used Gpart to partition. 3 FAT32 Primary partition at minimum size, extended for the rest, 20 logical unformatted partition at the smallest size, and 3 FAT32 partition on the end of a few various sizes. Nothing has worked.

I just thought I would throw out my luck in case it helps anyone.
[Droid Eris Android Development] cptkrush:
Just got my hands on a sloooooooooow xp laptop, gonna give it a go, see if that makes any difference.
[Droid Eris Android Development] izzaeroth:
I tried on a p3 laptop 1.2 ghz 768 ram on winxp pro sp3. Didnt have any luck.
[Droid Eris Android Development] :
Root'd

You probably won't believe this but, FIRST try this morning, ROOT. :D

I went and saw Predators last night then after stopped at after Walmart and picked up a PNY sd card (I tried 2 SanDisk cards 4/8G, and a Lexar 1G and got no where). My laptop and sd cards were all over the floor this morning (where I tried, got frustrated and quit :) ).

Anyway, here's me:

-Windows XP SP3

-Java SDK 6 Update 21

-PNY 2GD SD Card

How I did it:

-Formatted the card through mounted phone (last night)

-Reboot phone to bootloader (without card it)

-Pulled up device manager through mycomputer -> properties

-Then connected it to pc

-DID NOT RUN LOOP!

-Select Hboot, did my count and popped in

-Device manager refreshed to android phone from android usb device

-Open cmd prompt, adb devices

And there it was in recovery just chillin.
[Droid Eris Android Development] Nickboxer7:
ROOT SUCCESS!

I saw your post this morning and tried what you said. I didn't run the loop. I reformatted from that partitioning one I did so the PNY was just 2GB, formatted FAT32 with 4096.

I didn't run the loop, and just put it in and it didn't work. I tried one more time between 4-1000 and 5-1000 and in device manager it popped up as ANDROID USB DEVICE. I didn't know what I was looking for before but I think not running the loop might have helped. Once I saw that I ran adb devices as well and there is was.

I almost screamed in JOY!
[Droid Eris Android Development] Nikolai2.1:
Wow that's actually pretty awesome. I wondor if the adb loop is a bad thing...
[Droid Eris Android Development] sickbox:
Has anyone with success tried running "adb status-window" instead of the loop to check the adb state when trying to root? It should be better than tons of crap being printed while nothing is going on.
[Droid Eris Android Development] dantonuci:
Could someone please make a

thorough start to finish easy to understand instructional post of this new method , this is the most exciting breakthrough in a while!
[Droid Eris Android Development] kellerg:
Just wanted to make sure...

I have a phone that came from Verizon with HBOOT 1.49 and Android 2.1. Will this process still work for me, even though I don't have the leaked 2.1? I'm assuming so, but want to make sure I'm not ruining my SD-pushing-finger in vain.

Thanks!

-keller
[Droid Eris Android Development] ericFuels999:
Yes, it will work for you.

EDIT: I suppose I should qualify "work" in this case. There has been very little success all around, so it's more dependent on the specific SD card you have.
[Droid Eris Android Development] vandykky:
I tried to root my wifes eris (ruu hboot 1.49) for several days on my desktop and had no success but got it to work using the usb 1.1 port on my wifes netbook. Also did not have java sdk installed, don't think it is needed. Good luck all.

Sent from my DInc
[Droid Eris Android Development] christopad:
help

Ok guys, I got into clockwork recover mode once and then wen i tried again to double check my steps, I cant get back into it. Now the phone won't reconize the card. Also when in ADB i keep geting permision denied now. Can someone please help me complete this root?
[Droid Eris Android Development] tereg:
So today, I went to Wal-Mart and bought the exact same card I bought when I first did this method. It was the same price.

I was using Ubuntu with a VirtualBox VM of WinXP SP3.

I formatted the card as I did the "good" card, and then began my testing, but couldn't get it to work over a handful of tests. Then, I decided just for kicks (READ: I don't think this is a necessary step, I was just tinkering around with things) to format the card in FAT32 with an allocation table size of 8192.

I started with the card out, booted to FASTBOOT, then straight to HBOOT, then pressed Vol Up to go to recovery, and I did a 3-1000 count (yes, a slightly faster count than with my other card). And I was able to get it to work. I then repeated the test with the same cadence, and it worked. Then I used my original "good" card and was able to get a success with a 4-1000 cadence.

So then, I decided to try to test out ECLIPS3's sd card, tested for about an hour or so and still was unable to get a success using various timings and such.

So, I just wanted to report that.
[Droid Eris Android Development] rycheme:
I was talking to Decad3nce who hails from Hero land and talked to him about our leak root issue. He recommended taking a look at this thread for some possible helpful tips:

http://xdaforums.com/showthread.php?t=710483
[Droid Eris Android Development] claym88:
success

I followed the directions to the letter and couldn't get into recovery with my stock card. Attempt #3 with the suggested card was a success. I did have trouble pushing clockwork recovery, I think some clarification is necessary to repeat the whole step (as in pushing files) and not just the final timing step. I'm very glad since I have a 6 hour drive tomorrow and I can now surf the web the.whole.way there on my laptop wirelessly. Thanks to everybody who has put so much time into this, when I saw the # sign during the superuser step, I got so excited.
[Droid Eris Android Development] Dc_striker:
Like i said many times it doesn't matter what sd card you use
[Droid Eris Android Development] Dc_striker:
Funny thats the way i did it maybe people are finally understanding it all about the timing and not the sdcard
[Droid Eris Android Development] listyb01:
It is definitely all in the timing.

I did 4 1000's with 1 coinciding with pushing the volume up button and 4 coinciding with the actual click of the sd locking in. I feel like I could replicate it but don't have a device to test I am not about to unroot, that is madness :p
[Droid Eris Android Development] timmywa:
What about whether the card is formatted? Does that matter?
[Droid Eris Android Development] cnp112:
2.1ota root

Please Help...

I am a complete noob when it comes to rooting a phone. I am by no means technically challenged, just rooting phones for some reason. My wife has a STOCK droid eris and it is SLOW. I have searched for quite some time now and seem to be coming up with mixed answers.

Her phone currently has the 2.1ota (just to be clear - we downloaded the android 2.1 update directly from the "Settings" / "System Update" tabs within the phone itself about a month ago).

Can I root this phone in any way, shape, or form. I REALLY want to get her "Kaos Froyo v20 Rom." Can I follow the instructions at the beginning of this post. Would this get the job done? If not can someone please offer me a lamens terms step-by-step list of how to root if possible? I have also read that I may be able to go back to 1.5 and then root the 1.5 and upgrade to a rooted 2.1. I am fairly confused with all this at the moment so any help will be greatly appreciated. Thank you so much for the help if possible.
[Droid Eris Android Development] ktemkin:
The pure OTA doesn't update the bootloader and thus should be able to root in exactly the same manner as if it were a 1.5 device.

Let's verify this, to save you a bit of frustration. Turn off your phone. Hold SEND and END to turn it back on. You should see several red lines of text up top; if you post the one that starts with HBOOT, we can verify that you're not a 'leaker'.
[Droid Eris Android Development] cnp112:
Thank you for the response...

HBOOT = 1.47.0000

If this proves "OK"...Can I follow the same instructions to root a ERIS on 2.1ota (pure) as listed for rooting a stock ERIS 1.5...and then load any custom ROM by following the instructions specific to that particular ROM...thanks once again...