Root Root? No?

[Markla709]

I have a droid eris using 2.1 OTA upgrade. I want to jail break, I looked at the EMA and it was taken down 2 days before I wanted to use it. Are there other ways, I looked in the sticky and I couldnt find any. Im no pro, so an easy solution would be great.

 

[erisuser1]

I have a droid eris using 2.1 OTA upgrade. I want to jail break, I looked at the EMA and it was taken down 2 days before I wanted to use it. Are there other ways, I looked in the sticky and I couldnt find any. Im no pro, so an easy solution would be great.

Well, the 2nd sticky at the the top of this forum has explicit, step-by-step instructions how to do it

There are no "click this one button and you're done" solutions. Read through the above link - if you find the instructions too daunting, then rooting is probably not for you.

If there were simpler ways of doing it, that is what would be posted.

Just so you know, the parts that casual computer users have most trouble with seems to be: (1) getting the USB device drivers working (mostly on Windows 7), and (2) using the command line, whether that's in Windows, Mac, or on the phone (Linux).

Personally, I find the "fastboot" install method less complicated, because there are fewer things that need to be typed in at the terminal prompt, but it's not documented as a step-by-step guide.... and it also requires that USB drivers be installed correctly (Windows).

I led JrzDroid through that process (the fastboot variant) a couple of days ago, using this forum only to record the conversation - if you want, you can read that that thread, starting from post #28 to see what transpired. She eventually succeeded, with a couple of hiccups (that got solved along the way).

Good luck.

eu1

 

[Markla709]

Thank you. Your post is very informative and very well written. I say EMA and I was curious what it was, it looked like a click 3 buttons and you're done, could someone verify this please?

Thanks again
Markla709

 

[majorpay]

Well, the 2nd sticky at the the top of this forum has explicit, step-by-step instructions how to do it.

There are no "click this one button and you're done" solutions. Read through the above link - if you find the instructions too daunting, then rooting is probably not for you.

If there were simpler ways of doing it, that is what would be posted.

Just so you know, the parts that casual computer users have most trouble with seems to be: (1) getting the USB device drivers working (mostly on Windows 7), and (2) using the command line, whether that's in Windows, Mac, or on the phone (Linux).

Personally, I find the "fastboot" install method less complicated, because there are fewer things that need to be typed in at the terminal prompt, but it's not documented as a step-by-step guide.

I led JrzDroid through that process (the fastboot variant) a couple of days ago, using this forum only to record the conversation - if you want, you can read that that thread, starting from post #28 to see what transpired. HE eventually succeeded, with a couple of hiccups (that got solved along the way).

Good luck.

eu1

Fixed... and it is a great guide... That's the one I plan to use.

 

[Markla709]

I dont have SDK and I have 2.1. I dont know if its me or not, but whenever I look on a thread, I see from 1.5 to 2.1 not for 2.1 users leaked. Im 2.1 and NOT leaked. :S What do?

 

[erisuser1]

Fixed... and it is a great guide... That's the one I plan to use.

Considering creating an avatar for myself. You folks will be falling all over yourselves to help me. BTW, I'm 18 and I am smoking hot!

lulz

 

[majorpay]

Considering creating an avatar for myself. You folks will be falling all over yourselves to help me.

lulz

LOL... Yep, I had to peek behind the hood on that one...

 

[Markla709]

So, did anyone use EMA? What does it work like?

 

[erisuser1]

I dont have SDK and I have 2.1. I dont know if its me or not, but whenever I look on a thread, I see from 1.5 to 2.1 not for 2.1 users leaked. Im 2.1 and NOT leaked. :S What do?

Turns out to be the exact same process. I know, not the way things usually work with computers, but this one time it is.

eu1

 

[Markla709]

But I will be using leaked 2.1 right? And extremely buggy, right?

 

[majorpay]

But I will be using leaked 2.1 right? And extremely buggy, right?

Leaked 2.1 is OTA 2.1 (exactly), so bugs and all, it's what they've got for rooting (to clarify, don't leak, but I'm sure you already know that).

 

[Markla709]

Okay, makes sense. If anyone reading this is on IRC, please tell me as I could use some help

 

[erisuser1]

But I will be using leaked 2.1 right? And extremely buggy, right?

WHAT?

Please don't even use that word, "leak". NEVER even download anything described as a "Leak-Vx" ROM.

You will be using the "root-PB00IMG.ZIP" file for one thing and one thing only: to install an S-OFF bootloader. The MD5 checksum of that file is 63eacc5ede3b179f95dc22d8ef585f94, and you can get it from GrdLock's site (direct link) here.

That S-OFF bootloader is the stepping stone to putting on a new "recovery" partition, as well as a new ROM.

For dev ROMs which are based off of HTC code, almost all of the versions are based off of the software that comes with OTA-2.1 (yes, the OS portion of OTA-2.1 is the same as Leak-V3, but under no circumstances should you ever download or use the "leak V3" PB00IMG.ZIP file).

The ROM (main OS) that installs using the Root-ROM (md5sum 63eacc5ede3b179f95dc22d8ef585f94) is indeed buggy and old, and that's why everybody replaces it immediately. Again, all the dev ROMs (that are based off of HTC code) have current releases using OTA-2.1 as a base to start with - there isn't "something better from the factory".

eu1

 

[majorpay]

I'd hope no one ever accidentally leaks their phone, but I don't think the Eris roms are based on the OTA (I don't think they were able to scrape the "real" OTA), but instead on leak V3 because it was an identical OS if I am understanding this correctly, but of course, I have been known to be wrong a few times in my life?

Evil Eris v1.1 (ERIS BASED)
v1.1
---------
Runs Faster/Smoother now!
Runs on newer kernel (2.1 "OTA" Leak from 3/24/2010)
Audio Volumes fixed!
Dialer Lag fixed!
Removed Bloatware.
Removed GSM Stuff(NOT NEEDED)
Navigation "should" be working
Removed Extra Languages ( English + Spanish are only options now)
No Random Crashing/Rebooting
Google Maps Fix
Market Fix

 

[erisuser1]

I'd hope no one ever accidentally leaks their phone, but I don't think the Eris roms are based on the OTA (I don't think they were able to scrape the "real" OTA), but instead on leak V3 because it was an identical OS if I am understanding this correctly, but of course, I have been known to be wrong a few times in my life?

When the OTA runs, it does several different things, under control of the factory recovery partition ( All the commands can be examined in META-INF/com/google/android/update-script ):

- deletes old files that will be unused in the newer release
- drops in place new files that were not there before
- performs binary patching on many, many files (371, iirc) that have changed
- other cleanups like file permissions, creating symbolic links, etc

That means, among other things, that a lot of what is distributed in the OTA download are binary patch files - not the completed files that result when patching is finished.

When it is finished, however, a dev that knows what they are doing (batery pull trick) can root the phone without blowing away the OTA-2.1 OS and boot partitions - at that point they just boot into (Amon_RA's) recovery, mount the /data and /system partitions, and do something like

C:\Phooey> adb pull /system ./OTA21/system
C:\Phooey> adb pull /data ./OTA21/data

("adb pull" works recursively if you give it a directory name, so you can back up everything. You have to do this with the recovery boot, though, because the adb shell with the OTA-21 is not root privileged... and because those partitions would be "live" at that point).

(They can also just use the "mkyaffs2image" program in the recovery shell - that would actually be better, because it would preserve the file permissions and ownership info as well as the file contents themselves)

That gives them more or less exact copies of the (offline) /system and /data partitions from the OTA-2.1. (A liitle cleanup of /data is necessary because it has stuff from prior usage of the phone on 1.5; but that can be mostly avoided, too by running the OTA-2.1 immediately after a 1.5 rollback)

But, that is a little bit of work - you are right that they may have punted and just used the contents of the "Leak-V3" system.img and userdata.img files to extract whole files, acting with the belief that the OS contents (not the bootloader!) of OTA-2.1 and Leak-V3 are identical.


eu1

 

[Markla709]

The phone I got was a replacement, and a new one, and had a new boot loader, says a dev. So I cant root it and I need to wait until one genius at xda who roots 2.1...

Thanks for your responses,guys.

 

[erisuser1]

The phone I got was a replacement, and a new one, and had a new boot loader, says a dev. So I cant root it and I need to wait until one genius at xda who roots 2.1...

Thanks for your responses,guys.

What version number did the screen show when you powered it up in HBOOT mode (Vol-down + End/Power)?

 

[Markla709]

1.47.00

RADIO-2.42.00.04.12

OCTOBER 23, 2009

17:02:23

I was thinking 5:02 PM and 23 seconds?

 

[erisuser1]

1.47.00

RADIO-2.42.00.04.12

OCTOBER 23, 2009

17:02:23

I was thinking 5:02 PM and 23 seconds?

The "1.47.00" suggests quite strongly that you should be able to root - I would guess better than 99.99% chance that that is the case.

Perhaps you worded your question oddly on IRC - what was the nicname of the person that told you otherwise on IRC?


eu1

 

[Markla709]

jcash
suppliesjesus or something
someone else

I saw here though, posted by you.

[SIZE=+1]Trial 7: Attempt to root OTA-2.1 with "standard" method[/SIZE]

Method: Using Root PB00IMG.ZIP on SD card root, Vol-Down+End/Power


MD5 Checksums:
- (Root-ROM) PB00IMG.ZIP 63eacc5ede3b179f95dc22d8ef585f94


Starting Conditions:
- hboot: S-ON 1.47.0000
- radio: 2.42.00.04.12
- recovery: OTA-2.1
- OS: OTA-2.1

Result: [SIZE=+1]SUCCESS![/SIZE]

 

[erisuser1]

jcash
suppliesjesus or something
someone else

I saw here though, posted by you.
--snip--

That was indeed my experience.

jcase is usually not wrong, so perhaps you asked your question in a way that created a misunderstanding.

Now go root your phone and then tell them they were wrong... if you dare.

 

[Markla709]

I will. Could you give me EVERY thing that you used and all of the steps so I could get a success as well?

 

[erisuser1]

I will. Could you give me EVERY thing that you used and all of the steps so I could get a success as well?

Everything that I have done to my phone is an extraordinarily long list, there is no way I could document it.

What exactly is it that you find wrong with the sticky post http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html at the top of this forum?

Perhaps what is making you uncertain is that you are on OTA-2.1; but as I said, right up there in this thread a few posts ago

Turns out to be the exact same process. I know, not the way things usually work with computers, but this one time it is.

I walked user JrzDroid through this the other day (using a slightly different method), and the entire conversation, including some hiccups, is online in this forum, starting from post #28 in this thread.

Even if you didn't start trying to root your phone right away, you can get a sense of what is involved just by reading that thread, all the way through to the end.

eu1

 

[Markla709]

Thanks for your quick and long responses. I dont know what happened. After loading it, it checks but then takes me to the regular boot screen

 

[erisuser1]

Thanks for your quick and long responses. I dont know what happened. After loading it, it checks but then takes me to the regular boot screen

Did it ask if you want to continue? How long did this take? (One minute or five? ) I have no idea what you mean by "regular boot screen", please be precise.