Just had a system update on Eris??

[T-Keith]

I got the system update notice for my Eris about two days ago. I waited go get to a place with better reception, and then it was gone. I don't know if the upgrade ran or not.

I don't much care, because I'm going to send in my Eris for the gift card. I just bought an nice Incredible for $132.50 including shipping. That will tide me over until the Thunder Bolt is released.

Can I ask where you got the Incredible for $132?

 

[justrelaxing]

I just got a system update also. I was running the standard Eris 2.1 I just followed the directions erisuser1 identified and my software number is 2.41.605.6

Not sure what that means.

I was thinking about rooting my phone to store stuff on SD Card, would that help as I dont have much more then 20MB of free space and cant download many applications

 

[bberryhill0]

I was thinking about rooting my phone to store stuff on SD Card, would that help as I dont have much more then 20MB of free space and cant download many applications

Definitely root and ROM. You will think you got a new phone. I ran out of room around 100 apps without storing apps on SD.

 

[erisuser1]

I just got a system update also. I was running the standard Eris 2.1 I just followed the directions erisuser1 identified and my software number is 2.41.605.6

Not sure what that means.

I think that means that a March 2011 OTA for the Eris is the real deal.

What "directions erisuser1 identified" do you mean? ( I write way too much stuff, so I have no idea )

eu1

 

[gruss]

For real they're still updating this thing....crazy.

 

[justrelaxing]

How to find out what the software number was when trying to see what the deal was for the update to see if it was a new OTA.

Also, I have seen so many different rooting processes. Which one should I follow?

 

[doogald]

Also, I have seen so many different rooting processes. Which one should I follow?

There are two that work really well for people, the 1-click root app and Root for dummies. The first is easier but the documentation is basic and several people miss a key step on the first try; the latter is extremely well documented and I think walks you through the process really well. Even if you use the 1click method, the fourth post in the "dummies" thread is worth looking at when you are ready to flash a custom ROM, as it walks you through all of the steps with screen shots along the way.

Here is a link to 1-click: http://androidforums.com/eris-all-t...is-app-apk-no-pcs-no-scripts-needed-easy.html

and to the "dummies" method: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html

Also, many people, even with working trackballs, have an issue with the Amon's Recovery that comes with these two methods (which requires a working trackball) and Scary Alien has created a version of Amon's Recovery that works with the volume up and phone keys instead. You may want to keep this in your back pocket in case you need it: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

And, while I am thinking about Scary Alien, I think that you may want to try his free app AFV (Android File Verifier), which will allow you to check the MD5 hash signatures of the custom ROMs that you download before you try to flash them to make sure that they are completely downloaded. May ROM developers will tell you the MD5 of their downloads as a way to make sure that you get a full download. https://market.android.com/details?id=sa.afv&feature=search_result

 

[erisuser1]

doogald,

There is a chance that 2.41.605.6 may not be rootable using previous methods; we're going to have to find out once folks with good familiarity get hold of the OTA.

The one-click, Dummies, and unrEvoked methods all revolved around the same exploit iirc, so if it got patched (very easy to do, btw), they would no longer work as intended.

We'll know within a few days, hopefully.

eu1

 

[justrelaxing]

Ah, so now that I got the update, I need to wait it out and see if there is a new method to do it?

I will have to hold tight then.

I appreciate all your help

 

[doogald]

doogald,

There is a chance that 2.41.605.6 may not be rootable using previous methods; we're going to have to find out once folks with good familiarity get hold of the OTA.

The one-click, Dummies, and unrEvoked methods all revolved around the same exploit iirc, so if it got patched (very easy to do, btw), they would no longer work as intended.

We'll know within a few days, hopefully.

eu1

You're absolutely right, but I am thinking that neither HTC nor Verizon really cares all that much anymore about whether the small percentage of us who root phones do so with a phone almost one year past its last official retail sale. We'll see indeed, though.

Perhaps justrelaxing will be the one who lets us know for sure.

 

[erisuser1]

Ah, so now that I got the update, I need to wait it out and see if there is a new method to do it?

I will have to hold tight then.

I appreciate all your help

Perhaps.

The thing is, the method that either the one-click or Dummies methods uses is so straightforward and simple, there is nothing that will go wrong if it fails. They won't cause any harm if they fail, so you could give either of them a whirl if you want.

eu1

 

[Jrocker23]

Hey guys, I have a replacement eris coming today or tomorrow due to my eris having the scrolling trackball issue. I will see what software and versions are on it and then will try the one click method to root it.

My current phone is rooted so I cant get any updates. If there is anything I can find out or help with let me know. i have some decent knowledge of rooting so I can help somewhat if needed. If I dont know, then just explain what to do and I will try it..

 

[justrelaxing]

Here is a link to 1-click: Universal 1 Click Eris App Apk - No PCs, No Scripts Needed, EASY

I did this and had to follow the volume down method to get into the recovery mode. I think it all work and then deleted the root file i think.

Is there anything else I need to do? If there is not, is there a way to verify that it worked?

 

[doogald]

Here is a link to 1-click: Universal 1 Click Eris App Apk - No PCs, No Scripts Needed, EASY

I did this and had to follow the volume down method to get into the recovery mode. I think it all work and then deleted the root file i think.

Is there anything else I need to do? If there is not, is there a way to verify that it worked?

If you got into Amon's Recovery, and saw a screen that looks like the picture here, then it worked.

 

[bberryhill0]

I think if the app SuperUser is now on your phone is the simplest way to verify that you are rooted.

 

[justrelaxing]

I did get the Amon's Recovery screen. I do see Superuser Permissions in my All Programs area. Would this be it?

 

[doogald]

I did get the Amon's Recovery screen. I do see Superuser Permissions in my All Programs area. Would this be it?

Yes. I think that we can say that HTC did not patch the exploit with this update then. Thanks for posting the results.

 

[erisuser1]

justrelaxing,

Make a Nandroid backup right away, before you do anything else.

The 4th post in the "Dummies" rooting thread will show you exactly how to do this. (Especially also because you are the only known rooter in the world - at this moment - that has a copy of the 2.41.605.6 software).

Having that backup will allow you to go back to your phone exactly as it is now.

eu1

 

[t5800512]

Thank you eu1 for the update instructions! My wife has an Eris also, so if I don't upgrade mine, I will do it on hers.

I have been watching and bidding on every Incredible on eBay. But I stop bidding at $150. I also dont bid are any damages (scratches or dings) noted. I also don't bid is the seller does not have good ratings. For the most part, the Incredibles phones have been going for $167 on the low side and as much as $299 for phones that say they are new, or nearly new. Not very many at the $167 price level, but some.

So the other night I put in a bid on a nice phone before I went to bed. I bid $150 and won the bid at 4 AM (while sleeping) for 122.50 + $10 for shipping. So I got lucky. But I worked hard to find the deal, so I kind of earned it also.

I now plan to send my Eris in for the $132 gift card. So I will have upgraded for 50 cents. I'm pretty happy about that. Now I can save my upgrade for the Thunder Bold, when it finally comes out. I may even wait a while for the price to drop as I expect to be quite happy with the Incredible.

 

[gruss]

That has what to do with this thread? Besides last I checked the VZW return thing you'll get nothing for your Eris.....so good luck with that and your thunderbold, whatever that is. New blackberry mayhap?

Anyway, so Eu1 if one of is gets said update, what do we have to do to get it the devs that may want it? I can throw it in dropbox before it updates if I see the new one roll out.

 

[doogald]

As I recall the OTA last May, these tend to hit phones right after midnight as they roll out. I'm thinking of unrooting to see what happens tonight... and if it's nothing, just re-root and go back to normal in the morning.

Oh, with EU1/bftb0's fancy new Recovery, of course.

 

[erisuser1]

Anyway, so Eu1 if one of is gets said update, what do we have to do to get it the devs that may want it? I can throw it in dropbox before it updates if I see the new one roll out.

Actually, it is sort of tricky to "grab" the OTA - the reason is that immediately after it downloads, the phone reboots into the recovery boot to start the installation.

If you have the Amon_RA recovery on your phone, the installation will fail immediately - unfortunately, though, the next thing that happens is the recovery boot then erases both the OTA .zip file and the command file that launches the update, too.

There are two or three ways around this, in order of difficulty:

(1) Method One - Get the File Name Only

The easiest way is to "sniff the log". Not the one in the toilet, no; The output of the "logcat" command. It requires that you have the USB drivers installed correctly on your PC and also have the "adb" program. All we are going to do here is figure out what the name of the downloaded zip file is.

- Turn on USB debugging (Menu -> Settings -> Applications -> Development -> USB debugging) before the update arrives.
- First, you get the notice that there is an update available.
- If you can get to your PC right away, do nothing for a moment; otherwise, press the "Later" button. (I think the 3 choices you get are "Continue", "Cancel", and "Do this Later", or something like that)
- Attach the phone to the computer, and using the "adb" program in a command window, first type the command

adb devices

If everything is working OK, you will see your device ID number printed on the screen; then

 adb logcat -v time > captured_logcat.txt

The 2nd command will appear to "hang"; that is because it is continuously recording output from the logcat program to the file "captured_logcat.txt", and will do so until the phone reboots.

- Accept the update. (If you did a "Later" earlier in the day, go to Settings -> Phone Status -> System updates. That should get the ball rolling again.)
- Go through the update and let the phone reboot.

Now open up the "logcat.txt file" using notepad or wordpad. Towards the very end of the file, there will be a line that reads something like

Rebooting to install update BlahBlahBlah....blahblah.zip <- That's the file name right there.

Based on past experience, we can then reconstruct the full URL (there are one or two alternative path names).



(2) Method Two - Capture the File With a Custom Recovery

I actually made a modified version of Amon_RA's recovery boot which fiddles around with the recovery booting sequence in a way that it copies and then deletes the OTA file(s) out of the /cache area before anything else starts running on the phone. This allows the complete file to be captured to the SD card - so even if the /cache partition gets wiped/cleaned up, we'll get the full file as well as discover it's name. It is supposed to be engineered in a way that it behaves essentially identically to a normal Amon_RA recovery in all other respects.

That custom recovery can be found in this XDA post. It's really meant only for people that are very comfortable replacing their custom recovery (either by flashing it with fastboot because they have the S-OFF bootloader, or using the "flash_image" program, either with Amon_RA running, or a rooted ROM running - kind of like the original "Grdlock/Acidbath" rooting instructions.



(3) Method 3: WiFi Sniffing.

(An incredible amount of work.)

In this method you set up your Eris on WiFi only, and flood the packets to/from the WiFi router to a network flight recorder (e.g. tcpdump or Wireshark running on a promiscuous I/F). This requires either a dual-port linux box or a switch with a monitor port. This allows you to see the DNS resolver requests to figure out what hostname is being used when the OTA download begins. If the transfer is done with HTTP, rather than HTTPS, the full URL can also be sniffed out of the traffic.


cheers

eu1

 

[gruss]

My Eris is stock, so I'll leave it that way....if I get the update ill pull the files and give em to whoever. Just want to save ya the hassle, stock Eris is painful to me now after seeing how it runs on custom roms
I'll see what I can grab, have adb set up....maybe ill check out your thread on xda tomorrow and check your custom recovery out and re root it. I'm using it as my work phone so I can't leave it on my WiFi at home to sniff.

 

[erisuser1]

As I recall the OTA last May, these tend to hit phones right after midnight as they roll out. I'm thinking of unrooting to see what happens tonight... and if it's nothing, just re-root and go back to normal in the morning.

Probably so; VZWs network traffic should be lightest at that time.

Also, I think that VZW stages the rollout so that very, very, few of their customers get it for the first couple of days. Call this "last-minute field testing"; it gives them the opportunity to yank the plug on the OTA before it goes wide if a whole bunch of those "guinea pig testers" start showing up at Verizon's doors mad as a hornet.

Then, after that, it rolls out slowly and randomly (not geographically) to avoid spiking their traffic all at once.

I've had mine on 2.1 (2.37.605.1) for two days or so - no luck yet.

 

[gruss]

Where is the random foreigner with the leak? That's what used to happen in the good old days.