Related
Quick Notes: If you have suggestions/questions to add to my post please PM them to me and I will update it. I will be paying very close attention to this thread. As a new user I am currently unable to post links, this restriction will be removed in time.
Alright folks, keep it simple, and please don't repeat questions 12 dozen times.
Onto what this post is really about!
==========================================================
DROID ERIS UPDATE AND ROOT STATUS THREAD --- I am not responsible for anything you choose to do in regards to the steps listed in this thread. By reading and following any/all of these instructions you understand/agree to the fact that you are doing this under your own risk and that if anything goes wrong you had a chance to turn around, but CHOSE TO PROCEED REGARDLESS.
Quick Table of Contents: continue scrolling for more "updated" details
ROOT STATUS: ROOTED NOT YET RELEASED HOWEVER
MOST RECENT UPDATE("non-legit"): 2.1 with Sense
Scroll down for more info!
*NEED IMMEDIATE CONTACT FOR AN ISSUE/QUESTION/INQUIRY??
IRC: irc.thefuzz4.net #roottheeris and #dev (this is listen only for most)
or PM ME!
--------------------------------------------------------------------------
***ROOT STATUS***- There appears to be a dev build of 2.1 that is rooted floating around.
The problem is that it is an older build than the leaked 2.1, so anyone who upgraded is now unable to flash to this rooted rom.
Current progress is being pointed at trying to figure out how to downgrade to 1.5 so that we can go to this 2.1 that has SU in it.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Common Questions about the 2.1 LEAKED update:
Where did it come from?
-It was leaked via some chinese person
Is it SAFE?
-For the most part, yes. There is however a reason that HTC hasnt released it themselves, could be to something that were not capable of seeing, could just be a matter of "filtering"
Are there LIVE WALLPAPERS?
-Not yet.
Am I able to downgrade in the future for a shot at root /// any other reason?
-at the moment, No. Note that the eris wasn't rooted for MONTHS under the "old" update, and being that lots of people are on the new version, theres a likely chance that if there needs to be a downgrade in order to get rooted, the devs will figure out how to do that as well.
Do I VOID MY WARRANTY running this update?
-technically speaking, yes.
If I want to wait, how long until the REAL 2.1 hits the streets?
-suspected release dates are near the end of March IE: end of Q1. Then again, it was also near the end of January and also near the end of February after that.
Will updating to 2.1 cause me to lose all apps, phone settings, music, contacts, & text messages that are saved?
-Anything that is not on your sd card will be WIPED.
Does the 2.1 software make it possible for my Eris to both send AND receive Bluetooth files?
Yes. Things like bluetooth network sharing also become possible.
Noteable Bugs:
1) some users are noticing multi touch issues
2) some users are having trouble with the gmail apk
3) Google Earth, installs but doesn't run (no loss we didn't have it before at all)
4) Making out going calls with google voice doesnt use google voice (same on 2.1 with nexus one). Work around is to make the call from the contacts OR downgrade to an older version of the google voice app.
5) On reboot you may have an authentication error with google, forcing you to relogin.
6) Audio issues during calls/certain apps.
7) Some people are stuck with speaker phone while making calls.
Fixes for bugs?
3) Some people have noted that you can install an older version, which you can get @ (this is a link)goo.gl/Byy5
--------------------------------------------------------------------------
***3/3/2010 ERIS 2.1 ANDROID UPDATE*** This update was LEAKED TO US. It is currently suspected to be a variant of RELEASE VERSION.
How to FLASH this update: (please note, there is a certain amount of computer literacy required in order to understand some of these steps. If you are not comfortable with them but wish to continue anyway, good for you, but realize it might be a bit frustrating at times as well as SLOW. Patience is key here)
Some of these steps aren't necessary in order for it to work, this method just attempts to give multiple people the same kind of experience.
*** BEFORE YOU START BE SURE TO DOWNLOAD THE 2.1 UPDATE FILE HERE *** www(dot)sendspace(dot)com/file/frqze0
1) Take your SD CARD out of the phone and someHOW plug it into your computer so that you are able to BROWSE ITS FILE SYSTEM. If you are unable to do this, then either find a different way that involves not removing the card (you can do it by just plugging the phone in to the computer and going that route)
2) Create a new folder named OLD DATA or something relative to that in the ROOT of the sdcard. Move everything currently on the card into that folder. Copy that folder somewhere safe to your computer (this is for backup purposes)
3) Copy the file you downloaded earlier, named "PB00IMG.zip" to the ROOT of the sdcard.
4) After you have confirmed the file is on the card, turn your phone off.
5) Insert the card into the phone.
6) Hold the GREEN CALL button and then press power button WHILE CONTINUING TO HOLD THE GREEN BUTTON.
7) After the phone is booted, you will come to a menu that says something along the lines of "press volume down". Press the "VOLUME DOWN" to start the update process
8) The phone will spout off some random stuff and then ask for you to take action. PRESS THE TRACKBALL HERE.
9) The phone will turn off and then turn back on. It will then ask you to take some more action. PRESS THE TRACKBALL AGAIN.
10) Be patient, your phone is now applying the update, make sure nothing happens to it while it is in this state...
11) Go through the HTC setup and make sure everything is peachy.
12) Congrats, your ERIS is now running android 2.1
For questions regarding the situation you now face with your phone, please read on!
--------------------------------------------------------------------------
Failed Root attempts:
tba
--------------------------------------------------------------------------
Brief Droid Eris History:
***Eris UPDATE MR2***
This update arrived via Over the AIR for most people. It is based on android 1.5, not much else to say.
i'm a first time poster....looonngg timme follower, i would just like to say that i asked a verizon worker the other day about the actual 2.1 update and they said it's scheduled release is quarter one. quarter one ends at the end of march so its due by then im assuming, i hope they wont screw with us anymore lol but doesnt matter i proudly messed with my first android device. i was rather proud, im a little too used to the jailbreaking process.
Just so people know, our IRC chat is setup on:
irc.thefuzz4.net (round robin, aka random server specific servers are ircd.thefuzz4.net and irc.wastate.net)
General eris chat is at #roottheeris
our OPEN dev chat is #dev , however it is moderated and you will need to request voice to speak. People without dev input are welcome to sit and listen. People will dev input will be voiced and/or op'd/
################
Known issues with our 2.1 update
1. Google Earth, installs but doesn't run (no loss we didn't have it before at all)
2. Making out going calls with google voice doesnt use google voice (same on 2.1 with nexus one). Work around is to make the call from the contacts OR downgrade to an older version of the google voice app.
3. On reboot you may have an authentication error with google, forcing you to relogin.
4. Audio issues during calls/certain apps. (I have tried over and over to reproduce this, and can't. 2.1 works flawlessly for me.)
################
Numerous older exploits have been tried with no luck.
Tonight we tried flashing the 2.1 rom cooked with su included, signed as a hero rom with a hero gold card. Failed.
jcase
IRC Admin.
Eris junkie.
Regarding known issue #2 (Google Voice) - does anyone know where to download an older version? Thanks for the help.
updated the looks, let me know if its good or not so good
slugabed24 said:
Regarding known issue #2 (Google Voice) - does anyone know where to download an older version? Thanks for the help.
Click to expand...
Click to collapse
It was posted in the leaked thread on page 50 something, but here it is (insert http:/ /) docs.google.com/leaf?id=0B3k8BMVWRldLMzVlY2MzNTgtY2I3Zi00YzFlLWE3O WItNWVkMzc2NjM0ZDhj&hl=en
I haven't installed 2.1 yet so I personally can't confirm but this is supposed to be G-Voice 0.2.0 which is said to be working.
Recovery Mode Menu Apparently does not exist anymore.
thanks for the info - i can confirm that this works.
CUProf said:
It was posted in the leaked thread on page 50 something, but here it is (insert http:/ /) docs.google.com/leaf?id=0B3k8BMVWRldLMzVlY2MzNTgtY2I3Zi00YzFlLWE3O WItNWVkMzc2NjM0ZDhj&hl=en
I haven't installed 2.1 yet so I personally can't confirm but this is supposed to be G-Voice 0.2.0 which is said to be working.
Click to expand...
Click to collapse
I can confirm this works. I uninstalled the current version of GV, and installed this version.
I keep just getting the Triangle Exclamation point
I am following the directions, and I am "assuming" I am supposed to go into recovery mode. When I do this, I hit FASTBOOT, since it's the only thing I see as an option. I then get this screen (see picture attached) and nothing happens at all...
Guessing this is not good..
Any help?
DIFFERENT REBOOT MODES:
vol_up + power = recovery
vol_dn + power = hboot
send + power = fastboot
Got it
Thx man! I think it's rollin now! Hopefully gonna make some Hero carriers jealous
2 ?s about 2.1 update.....
Will updating to 2.1 cause me to lose all apps, phone settings, music, contacts, & text messages that are saved ?
Does the 2.1 software make it possible for my Erius to both send AND receive Bluetooth files?
Yes amd Yes,
The Contacts that you have SYNC'd with Google will be saved, but everything else will be erased. Except for what is on the SD Card.
And Yes you can finally send files through bluetooth.
one other thought.....
If I upgrade now, will I still get the official update from Verizon once they finally decide to release it?
Sorry to interrupt, but please use the search button. this section is about root not 2.1. The 2.1 thread is right outside of this one and all the questions are already asked in there. So please do not clutter this thread with non root related Q/A. Thanks and sorry to but in!
PS not trying to come off as an asshole just a tip for ya,
tdavis42 said:
sorry to interrupt, but please use the search button. This section is about root not 2.1. The 2.1 thread is right outside of this one and all the questions are already asked in there. So please do not clutter this thread with non root related q/a. Thanks and sorry to but in!:d
ps not trying to come off as an asshole just a tip for ya,
Click to expand...
Click to collapse
+1 98765432
To be fair, I had included some guided questions regarding the recently leaked update, only as a filler into what would need to be corrected in the event that root came AND we were able to get some custom roms going.
Personally, I don't mind sifting through more questions and searching out answers for people, and while I don't know that it helps anything to create a second spam thread, I will have to agree that the search function is a valuable tool when there are 900+ posts to go through with possible answers.
Regardless, I've updated some questions and moved some more things around to better address the final goal of this thread, which is in the end to discuss Rooting methods ON 2.1. Getting people to 2.1 is part of that process
I am all for getting people to use 2.1 and their is a 70 page thread for that. I have been over there answering all kinds of questions for a while.
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
This is NOT for those on 2.1 leak. It is ONLY for those on 1.5 Stock or 2.1 OTA OS version.
This is a Windows Only version. We are porting it to JAVA now for cross platform compatibility.
Major update - Re Uploaded the App
We have brought back the Eris Master App as the Android Master App. It has a new name in preparation for support for more Android devices. We are working on fixing the XP bug where files wont download. Until we get a full fix working, DO NOT USE IF YOUR ON WINDOWS XP Stay tuned for updates. We have also included an Error Log handling feature. If there are any errors, it will try to automatically send us an email with the log file. If it cannot send us the email, the log file will pop up for you so you can get in contact with us and send us the log so we can fix the issue.
Again, if you are on Windows XP, DO NOT USE. We have been getting a lot of email logs from those on XP, and we know its not working, so dont bother wasting your time trying to see if it works.
Download the application from here: http://tinyurl.com/2doknnb then run the self extracting .exe zip file, and let it extract to its default location, which is c:\AMA\ then go into the folder there and run the application. Select a ROM to download, and the Root Image, and Recovery Image, then start the downloads.
If you need any support, it is always available on the IRC server.
You can also follow us on Twitter: www.twitter.com/THE_ECLIPS3
Check the thread and the IRC server for updates.
ECLIPS3 and Jamezelle
- Fixed files not downloading in windows XP a little bit more, full fix in works
- Fixes a few minor bug fixes
- Streamlined the code more
This App is being worked on by ECLIPS3 and Jamezelle
We are now on Google Code. Please visit the page here to let us know of any bugs / errors you get while using the app. It is not meant to help you solve your problem there. That is what this thread or our IRC server is for. The IRC server login info is at the bottom of my signature. A web based IRC server is available through this link.
On step 2, when you get to the part of doing the update. our app will tell you to push volume up to start update. you might also have to push the trackball in as well. the link will say <action> YES. push trackball in to start update.
- Market updates for apps. (coming soon)
We have figured out how to restore apps, and restore market update links, need to roll it into the app, but it is possible. We might even have a way to restore links for those non root. Any other app that does market update links requires root first to backup the links.
UPDATE 5/5/2010
Version 2.1 (released 5/5/2010)
Files are now hosted on http://android.grdlock.net
-Fixed where app wont upload custom rom to phone
-New download links for files
-Ability to download roms via app, instead of including them
-Choose what rom to install easier
-Download of ROOT Image instead of including it
-Progress bar for downloads
-Splash Image install
-Cleaned up a lot of the code
-Many bug fixes
-Made user interaction a lot more friendly
-Fix device not found in app.
-Check if phone is connected to PC. If not, setup will not continue.
-Fixed spelling issue.
We have now finished the core of the Application. What it consists of is a GUI (Graphical User Interface) to make going from 1.5 stock to 2.1 root with a custom ROM installed. There is also an easy way to reboot your phone, enter the recovery mode, and enter the bootloader mode. Finally the third part available in this release is a way to backup all of your applications along with restoring all of them. Currently this is root only. We do have an update coming to backup apps for non root.
For rooting there is a 4 step process. Just go through the steps, one at a time and make sure you read and pay attention to the instructions.
We will be adding more functionality and options to this application. Stay tuned for future updates. If there is an update, just re download the whole app.
Please let us know of any bugs or options you would like to see in the application and we will do what we can to add those in or fix those bugs.
Prereq's for using the application:
You must have Microsoft .NET version 4. Direct Download Link
Then also download the drivers file. Unzip it to your desktop. Follow these instructions on how to install a driver. Select have disc, then navigate to your desktop, inside the corresponding folder, and continue the prompts.
Requests
- Support for other android phones.
- Save Layout and Scenes. (Working on now)
- backup apps for those NOT ROOTED (Have it working. need to roll it into an update)
- Restore email settings for Gmail and HTC Mail (Working on now)
- Download speed for file downloads
- Boot andimations (new name for animations)
- Progress bar for copying files to sdcard
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok though because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
ch4sethe5un said:
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok thought because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
Click to expand...
Click to collapse
Thanks for your feedback. I am working on creating a standalone application for backing up the apps, reinstalling, rebooting, rebooting into bootloader and recovery. It will also be able to install the bootanimation files amongst other things. hopefully i will be able to have it do the rooting process as well. though im not sure how often that will be used considering most have already rooted their phones. if some people would like to vote on those options and let me know what they want as well as requests for other features that would be great.
bootanimation is good and boot image logo like in here, maybe?
http://forum.xda-developers.com/showthread.php?t=654042
though im not sure how often that will be used considering most have already rooted their phones.
Click to expand...
Click to collapse
Thats not necessarily true, because 'all people' aren't trolling the internet like we are all the time.
So im sure there are people that dont even know we have root access on the eris. I bet there are also a ton of people that dont know what root is and even how to go about it, so an automated system would be a great addition.
Most of the world is not technology oriented. Think of (most)Best Buy shoppers.. hahah (i used to sell computers there) They look for someone to 'deal' with the tech for them.
i may just be a ritard but i plug my phone in to computer with debugged mode on, i have the skd driver thing updated and my sd card is mounted and it says error device not found any idea wat im doing wrong like i said im a ritard lol thanks guys yall do amazing work keep it up!!!!!!
I use these scripts whenever I flash! I will be glad to test your app!
iamgodnkg said:
i may just be a ritard but i plug my phone in to computer with debugged mode on, i have the skd driver thing updated and my sd card is mounted and it says error device not found any idea wat im doing wrong like i said im a ritard lol thanks guys yall do amazing work keep it up!!!!!!
Click to expand...
Click to collapse
dont mount your sd just leave it ur phone on charge. And follow the instructions that are mentioned in the script before you start it.
I the core of the app done which is going from stock 1.5 to 2.1 root, with recovery image and new rom installing. i have a few people beta testing it for me. once i make sure it is stable for the XDA community i will release that with periodic update of new features.
ECLIPS3 said:
I the core of the app done which is going from stock 1.5 to 2.1 root, with recovery image and new rom installing. i have a few people beta testing it for me. once i make sure it is stable for the XDA community i will release that with periodic update of new features.
Click to expand...
Click to collapse
I was having issues using the scripts to backup on aloysius 2.0 port I did yesterday. It refused to backup; I'm not sure why..
Spencer_Moore said:
I was having issues using the scripts to backup on aloysius 2.0 port I did yesterday. It refused to backup; I'm not sure why..
Click to expand...
Click to collapse
the rom you ported, its a hero rom? thats probably why because i have found that roms that have been ported from other devices have issues with my scripts, which is because of how the rom and its core are built. will try and add that functionality at some point.
for everyone else. these scripts only are verified to work on eris based roms and legend based roms.
Great job! saves so much time and work!
UPDATE: Application is now released. please view first post for more info.
Nice work!
ch4sethe5un said:
So i tried this out and it works great. It is a really nice addition to the anyones android tool set.
I did notice that once i reinstalled all apps it did take quite a long time to load all of them again... 5 minutes. That was ok though because it saved me alot more time from having to download and install all of them again. I did i reboot too just to make sure.
Thanks a lot for this script!
note: put the scripts in your sdk\tools section on your computer.
Click to expand...
Click to collapse
On fresh installs, or after wiping, it takes some time to build up the cache again.
Eris Master App update file
The update file can not be found.
he requested URL /Eris_Master_App_By_ECLIPS3.exe was not found on this server.
Re: [Application] Eris Master Application
The update file can not be found.
he requested URL /Eris_Master_App_By_ECLIPS3.exe was not found on this server.
Click to expand...
Click to collapse
that is because I don't have an update for it yet.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
ECLIPS3,
Ok....Well my Eris now has the latest 2.1 ROM and when I ran the program it told me that the ROM installed is older that the one being installed. So if I replace the newer rom in the upload/root folder should I be ok?
-Tony
Re: [Application] Eris Master Application
Are you on 2.1 leak, 1.5, or 2.1 root? This only works on 2.1. The file in the root folder is the 2.1 root image. In rom folder is custom roms to install. An update will be released today.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
ECLIPS3,
I am on the 2nd 2.1 leak unrooted.
-Tony
Re: [Application] Eris Master Application
I hate to say it but please read first post again. It will be answered for you.
Sent from my Eris using the XDA mobile application powered by Tapatalk
Eris Master App update file
Ok..sorry Sir!
Yanked straight from my Eris.
http://db.tt/w9LQH7N
sent from my phone
Awesome your the hero of the day!
These are flashable from Amon_Ra's recovery. They do not flash the radio or recovery, but I can make versions with those if you want. You have to be on the right most version for them to flash.
OTA_2.37.605.4_2.36.605.1 --> http://46.4.208.146/OTAs/OTA_2.37.605.4_2.36.605.1.zip
OTA_2.41.605.6-2.37.605.4 --> http://46.4.208.146/OTAs/OTA_2.41.605.6-2.37.605.4.zip
I'm working to fix DNS now, so sorry for the direct IPs...
Sweet you guys work fast, not sure what this includes, I rooted real quick so I could pull it per request from eu1 on another forum. Couple folks still stock have installed it though.
sent from my phone
FYI for anyone wanting to play with these files, the zips only contain .P files which are patches. They are designed to be patched against a stock rom.
So if you really wanted something, you'd have to take your system full stock and then apply this and then dump a nandroid or use ABD to transfer files off the phone.
gruss01 said:
Sweet you guys work fast, not sure what this includes, I rooted real quick so I could pull it per request from eu1 on another forum. Couple folks still stock have installed it though.
sent from my phone
Click to expand...
Click to collapse
Well if you have a Mercedes your in luck. Better bluetooth connection. somme MMS tweeks and "better signal" here is a link that I found with a "full description"
http://androidspin.com/2011/03/03/htc-droid-eris-for-verizon-receives-random-ota-update/
gnarlyc said:
These are flashable from Amon_Ra's recovery. They do not flash the radio or recovery, but I can make versions with those if you want. You have to be on the right most version for them to flash.
OTA_2.37.605.4_2.36.605.1 --> http://46.4.208.146/OTAs/OTA_2.37.605.4_2.36.605.1.zip
OTA_2.41.605.6-2.37.605.4 --> http://46.4.208.146/OTAs/OTA_2.41.605.6-2.37.605.4.zip
I'm working to fix DNS now, so sorry for the direct IPs...
Click to expand...
Click to collapse
I would like the new radio as a flashable please. That's probably the only useful thing from this ota. Thanks man.
dreed75 said:
I would like the new radio as a flashable please. That's probably the only useful thing from this ota. Thanks man.
Click to expand...
Click to collapse
Tried to flash and got an installation aborted....no big deal I was thinking of putting a decent Rom on there anyway, stock has been bugging me and traveler testing is about over anyway.
sent from my phone
dreed75 said:
I would like the new radio as a flashable please. That's probably the only useful thing from this ota. Thanks man.
Click to expand...
Click to collapse
As I read on the Verizon description, the radio included on this OTA is 2.42.01.04.27. So the radio did not change. -=/
endoki said:
As I read on the Verizon description, the radio included on this OTA is 2.42.01.04.27. So the radio did not change. -=/
Click to expand...
Click to collapse
oh, ok. i forgot i had flashed an old radio to try to clear up a bug so my version was less than the "new" one.
FWIW, here's some "picking it apart" analysis.
I flashed a virginal copy of the July OTA (2.37.605.4) plus it's associated stock recovery to my phone, and then applied this newest (2.41.605.6) OTA (letting the stock recovery for the July OTA do the install). After it completed and rebooted, I used the stock recovery to perform a factory reset. Following that, I made a Nandroid backup.
In both of those configurations (while they were booted), I pulled /proc/config.gz for later comparison.
Then I unpacked (unyaffs) the "system.img" files from each of the respective Nandroid backups, and did an offline comparison of the before & after condition of the /system mount point.
The pastebin with the summary results can be found here. Note that files noted as exhibiting differences only indicates a changed MD5 checksum.
[SIZE=+1]Highlights:[/SIZE]
- most changes are in /system/app (as expected) and 20+ changes in /system/framework
- Library (/system/lib) changes: libandroid_runtime.so, libhtc_ril.so, libopenobex.so
- Native binary ( /system/bin ) changes: vold, wpa_supplicant, dmagent, debuggerd, btipsd
A comparison of the kernel compile options for both (/proc/config.gz) revealed that identical config files were used to build both kernels. There was of course, one minor difference: the time stamps in the config files:
Code:
[email protected]:~$ diff march11OTA/config julyOTA/config
4c4
< # Tue Sep 7 17:35:16 2010
---
> # Thu May 13 12:30:48 2010
After seeing this, I unpacked the boot images, and uncompressed the kernel. Indeed, this newest kernel was built ... wait for it ... nearly 6 months ago. No big deal, I expect VZW/HTC to move at a snails' pace on a "legacy" phone; OTOH, what I find bothersome is that HTC recently released kernel sources "for the Eris" that had time stamps from February 23 of this year. WTF?
I suppose that means that there may not be any reason to believe that there is good correspondence between what VZW is shipping and the sources that HTC is producing under its' GPL obligations.
The ramdisks of the boot.img file were bitwise identical - so, no boot/init changes for this OTA release, either.
cheers
bftb0
bftb0 said:
Code:
[email protected]:~$ diff march11OTA/config julyOTA/config
4c4
< # Tue Sep 7 17:35:16 2010
---
> # Thu May 13 12:30:48 2010
After seeing this, I unpacked the boot images, and uncompressed the kernel. Indeed, this newest kernel was built ... wait for it ... nearly 6 months ago.
Click to expand...
Click to collapse
Sprint had an update to the Hero last fall. Maybe Verizon was just catching up?
bftb0 said:
FWIW, here's some "picking it apart" analysis.
I flashed a virginal copy of the July OTA (2.37.605.4) plus it's associated stock recovery to my phone, and then applied this newest (2.41.605.6) OTA (letting the stock recovery for the July OTA do the install). After it completed and rebooted, I used the stock recovery to perform a factory reset. Following that, I made a Nandroid backup.
In both of those configurations (while they were booted), I pulled /proc/config.gz for later comparison.
Then I unpacked (unyaffs) the "system.img" files from each of the respective Nandroid backups, and did an offline comparison of the before & after condition of the /system mount point.
The pastebin with the summary results can be found here. Note that files noted as exhibiting differences only indicates a changed MD5 checksum.
[SIZE=+1]Highlights:[/SIZE]
- most changes are in /system/app (as expected) and 20+ changes in /system/framework
- Library (/system/lib) changes: libandroid_runtime.so, libhtc_ril.so, libopenobex.so
- Native binary ( /system/bin ) changes: vold, wpa_supplicant, dmagent, debuggerd, btipsd
A comparison of the kernel compile options for both (/proc/config.gz) revealed that identical config files were used to build both kernels. There was of course, one minor difference: the time stamps in the config files:
Code:
[email protected]:~$ diff march11OTA/config julyOTA/config
4c4
< # Tue Sep 7 17:35:16 2010
---
> # Thu May 13 12:30:48 2010
After seeing this, I unpacked the boot images, and uncompressed the kernel. Indeed, this newest kernel was built ... wait for it ... nearly 6 months ago. No big deal, I expect VZW/HTC to move at a snails' pace on a "legacy" phone; OTOH, what I find bothersome is that HTC recently released kernel sources "for the Eris" that had time stamps from February 23 of this year. WTF?
I suppose that means that there may not be any reason to believe that there is good correspondence between what VZW is shipping and the sources that HTC is producing under its' GPL obligations.
The ramdisks of the boot.img file were bitwise identical - so, no boot/init changes for this OTA release, either.
cheers
bftb0
Click to expand...
Click to collapse
As always, a wonderfully thorough and knowledgeable analysis. Thank you.
bftb0 said:
FWIW, here's some "picking it apart" analysis.
I flashed a virginal copy of the July OTA (2.37.605.4) plus it's associated stock recovery to my phone, and then applied this newest (2.41.605.6) OTA (letting the stock recovery for the July OTA do the install). After it completed and rebooted, I used the stock recovery to perform a factory reset. Following that, I made a Nandroid backup.
In both of those configurations (while they were booted), I pulled /proc/config.gz for later comparison.
Then I unpacked (unyaffs) the "system.img" files from each of the respective Nandroid backups, and did an offline comparison of the before & after condition of the /system mount point.
The pastebin with the summary results can be found here. Note that files noted as exhibiting differences only indicates a changed MD5 checksum.
[SIZE=+1]Highlights:[/SIZE]
- most changes are in /system/app (as expected) and 20+ changes in /system/framework
- Library (/system/lib) changes: libandroid_runtime.so, libhtc_ril.so, libopenobex.so
- Native binary ( /system/bin ) changes: vold, wpa_supplicant, dmagent, debuggerd, btipsd
A comparison of the kernel compile options for both (/proc/config.gz) revealed that identical config files were used to build both kernels. There was of course, one minor difference: the time stamps in the config files:
Code:
[email protected]:~$ diff march11OTA/config julyOTA/config
4c4
< # Tue Sep 7 17:35:16 2010
---
> # Thu May 13 12:30:48 2010
After seeing this, I unpacked the boot images, and uncompressed the kernel. Indeed, this newest kernel was built ... wait for it ... nearly 6 months ago. No big deal, I expect VZW/HTC to move at a snails' pace on a "legacy" phone; OTOH, what I find bothersome is that HTC recently released kernel sources "for the Eris" that had time stamps from February 23 of this year. WTF?
I suppose that means that there may not be any reason to believe that there is good correspondence between what VZW is shipping and the sources that HTC is producing under its' GPL obligations.
The ramdisks of the boot.img file were bitwise identical - so, no boot/init changes for this OTA release, either.
cheers
bftb0
Click to expand...
Click to collapse
So, does that mean HTC's kernel sources are more recent, and thus improved? And if so, can/are any XDA devs able to build a kernel from the latest HTC source? Is this something Conap/Decad3nce could/do use?
KarateExplosion6 said:
So, does that mean HTC's kernel sources are more recent, and thus improved? And if so, can/are any XDA devs able to build a kernel from the latest HTC source? Is this something Conap/Decad3nce could/do use?
Click to expand...
Click to collapse
More recent, yes. Improved is hard to say; "worth the effort" is even harder to say. I did a brief analysis of the differences between the last two HTC kernel source releases, and put that question to Conap last night. Maybe I should have asked him privately, rather than in the forum, though.
To me it seems like a pretty good chunk of work is required to do that, and so it is therefore worthwhile to ask the question: what gain is won through the effort?
It would be pretty easy to just compile the HTC kernel "as is", but no-one would be happy with that, esp. in the areas of overclocking, schedulers and scaling governors.
What has happened over time is that the "dev" Eris 2.6.29 code has been branching away from the HTC code base that zanfur started with, and Decad3nce/Conap have incorporated a lot of new goodies (bfs, cfs, new governors, etc) downstream from zanfur's mods into what is currently "CFSv9". At the same time, the HTC code has also been branching away from that same starting point. Some of those changes more than likely overlap, esp. if code from later mainline Android releases are being back-ported into both "2.6.29" source branches simultaneously.
Maybe the right approach is to start by looking at the HTC code changes in individual areas, and just cherry-pick individual patches out of it where it looks like there is either a performance opportunity, or a "big" bug fix. (I'm not optimistic that we are going to see giant performance leaps twiddling with the kernel; and it's probably a good idea to be conservative about kernel patching anyway.)
bftb0
Why did the phone keep offering the update after I did the AmonRA flash from zip?
Stonent said:
FYI for anyone wanting to play with these files, the zips only contain .P files which are patches. They are designed to be patched against a stock rom.
So if you really wanted something, you'd have to take your system full stock and then apply this and then dump a nandroid or use ABD to transfer files off the phone.
Click to expand...
Click to collapse
My phone is quite vanilla -- stock ROM but rooted. I took the ZIP file from gnarlyc and applied it. It seems to have been successful.
I put details in an androidforum thread. (I'm too new to this forum to post that as a link. The URL, in text form is: androidforums.com/htc-droid-eris/286167-just-had-system-update-eris-4.html#post2483781 )
I did have to re-root the phone.
Surprisingly, after the patching said it was successful, and successfully booting up the phone and confirming the Software number was now 2.41.605.6 instead of the old 2.37.605.4, the phone still kept popping up an alert offering me the update.
How come, if all the files are now in place for the update, does the phone still think I need the update?
wcattey said:
Surprisingly, after the patching said it was successful, and successfully booting up the phone and confirming the Software number was now 2.41.605.6 instead of the old 2.37.605.4, the phone still kept popping up an alert offering me the update.
How come, if all the files are now in place for the update, does the phone still think I need the update?
Click to expand...
Click to collapse
Well, the program logic which normally would initiate the upgrade actually never checks to see whether the update occurs or not - the only thing it seems to be aware of is whether you press the "OK, do the update" button.
This also means that the reverse is also true - if you accept the nag screen, but the update fails, you will no longer be nagged - it only seems to remember whether or not you "pressed the OK button".
And you can be sure that it will fail if you have the Amon_RA recovery on the phone... so go ahead and hit the "OK" button, and be rid of the nagging. (If you are worried that what I am saying might not be true, then make a nandroid backup before you begin)
bftb0
Thanks for the clarification.
I suspect the update initiation logic is not what you or I would have written, had we been the developers of that particular piece.
Indeed, I hit the OK button, watched Amon_RA try and fail as expected, and then the phone quit inviting me to update, also as expected.
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
EncryptedCurse said:
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
Click to expand...
Click to collapse
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Eclipsys said:
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Click to expand...
Click to collapse
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
jimyv said:
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
Click to expand...
Click to collapse
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Eclipsys said:
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Click to expand...
Click to collapse
I didn't have any problem doing the modifications myself and I'm no Pro that's for sure. Never written a line of code in my life. I just tend to thoroughly research and understand before I attempt things and I've been practicing here for a while if you go to the, rollback .0.1 and safestraped thread there is quite detailed instructions serval times throughout the thread I would skim it.you will just be substituting version numbers and kind of a inverse idea compared to what we were doing there but it should accomplish it. I used rOM Toolbox lite I believe as an editor and saved each timeI didn't have any problems with the permissions getting screwed up while tampering with it rOM Toolbox took care of that issue. I have seen tons of people brick trying to make these modifications. But I don't think they understood completely what they were attempting to do it's actually very simple and as long as you do it thoroughly and get all of them changed I have not seen any problems other than maybe having to repeat the process.there are a couple of lines that only use the last section of your version numbers I even changed those back then.
Eclipsys said:
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Click to expand...
Click to collapse
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
p1gl3t said:
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
Click to expand...
Click to collapse
https://mega.co.nz/#!wlQl2bZD!Kk-rcWtcMPWxoEH5VcHrtZb7nOsJet9si1pm5FYhT44
5.2 build prop file