I got a system update. US 1.5 - G1 General

Is there anyway for me to get the build name after I already installed it?

no, you are suppose to install log collector first

He's asking how to find the build number, not the download link. While on the G1 home screen, click the menu button, then click on settings, scroll to the bottom and click "About Phone" then scroll to the bottom yet again and wah-lah! The build number.

cant he abd in and get the url of the update? got any pics of the about phone screen showing 1.5 fm?

Probably, lets just see if he can get us some screens and the build number first.

So you posted and than ran too far away to handle clicking on " about phone " this gets old so fast...It's getting like android community lately

official build info posted.. second post this link
http://forums.t-mobile.com/tmbl/board/message?board.id=Android_MR&thread.id=81
"If your phone displays Kernel version 2.6.27 as above, then you have the latest update."

Another one:
http://forum.xda-developers.com/showthread.php?t=514378

Question,
Since we know the update link will be something in this neighborhood.
https://android.clients.google.com/updates/signed-PLAT-CRB43-from-RC33.????????.zip
Is there any rhyme or reason to the question marks? Is that sequence pulled from somewhere on the phone? I think we have a few people with the update, maybe we can track down that sequence?

akeippela said:
Question,
Since we know the update link will be something in this neighborhood.
https://android.clients.google.com/updates/signed-PLAT-CRB43-from-RC33.????????.zip
Is there any rhyme or reason to the question marks? Is that sequence pulled from somewhere on the phone? I think we have a few people with the update, maybe we can track down that sequence?
Click to expand...
Click to collapse
Those question marks are the first 4 bits (8 characters) of the sha1sum of the file. In order to get it you either need the actual URL of the file (duh) or you need the zip file itself to run sha1sum against. You can see this if you take the RC33-from-RC30 .zip to a linux box and run:
Code:
sha1sum filename.zip
EDIT: Those are the only 2 ways to get that sequence, i believe the .zip file is deleted from the phone after the update is run so even if you could access the "secret partition" where it's stored, you can't really do anything with it.

cant wait for 1.5

Related

FYI: OTA URL capture

I don't know how useful this will be, since many of the devs have probably gleefully pounced on the 2.1 leak (and can't roll back now to Cupcake), but...
The OTA update process (1.16.605.1 -> 1.17.605.1) is completely different than the RUU/HBOOT methods... it actually boots into android and performs file-by-file binary patching on all sorts of stuff as well as installing new files and other miscellany - controlled by an "update-script" (not a shell script, but quite readable).
The OTA .zip files which are downloaded from a Google server are not signed the same way as the RUU "rom.zip" files - they use the app .apk manifest signing method. (manifests and certs a la "jarsigner").
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Note: because the 2.1 release is so vastly different than the 1.5 release, an OTA (if that's the way VZW/HTC rolls it out) for that will probably be very different than a patch release like this example ... but it would still be very useful for anyone who gets notice of an update to capture the URL using the "logcat" method shown above. There might be "interesting" tools included that could be exploited.
I don't think this will help get an "early OTA" - I'm not sure that hboot/fastboot methods can make use of an "update.zip" with an unrooted phone. Someone can correct me if I am wrong about that.
bftb0
Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.
pharaohmd said:
Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.
Click to expand...
Click to collapse
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.
nindoja said:
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.
Click to expand...
Click to collapse
Thanks...thought so but wanted to check...I tried to search but there have been so many */*/*/etc posts it's a bit confusing.
(edited out the example search terms so as NOT to contribute to the mess with this post...)
can sombody do this with the Update that just started pushing tonight?
iornslave said:
can sombody do this with the Update that just started pushing tonight?
Click to expand...
Click to collapse
Since so many of the XDA members are rooted, we're going to have to count on one of the "leakers" to capture it. We've confirmed (on android forums dot com) that it's coming to those on leak v3, which makes sense since that's up-to-date with the RUU and OTA.
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I'm sort of wondering if VZW had some customer problems with it and pulled the plug on it. In the past, there have been claims that VZW starts the rollout in very small groups - several hundred at a time - and then ramp it up if they don't see complaints coming in from their customer support channels.
Sure does seem like there's very little chatter about it.
I've got my phone running OTA-2.1 to try and intercept it, and I also hacked a custom recovery that doesn't automatically erase files in /cache (basically, a recovery boot that doesn't run /sbin/recovery at all). That way I can just pull it out of /cache as soon as it is downloaded via OTA.
Nevertheless - to anybody reading this - please post up the URL to the zip file download if you capture it.
bftb0
[Edit] For references, PRIOR OTA URLs were
1.17.605.1 (aka "MR2") OTA: https://android.clients.google.com/packages/desirec/desirec-ota-104882.7b1e5cca.zip ( md5sum: f6bd240c726874e3922767979ecc6b32 )
2.36.605.1 (aka "OTA-2.1") OTA: https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip ( md5sum: 9a3a82e4b5afb4e885b41d28085b9adc )
Note: both these links verified working w/ correct checksums as of 2010-07-01.
hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I agree I have been hoping someone would have posted it considering that several have claimed to have received it. Oh well, hopefully soon.
Maybe all the people who are "smart" enough to do this are already rooted?
Stonent said:
Maybe all the people who are "smart" enough to do this are already rooted?
Click to expand...
Click to collapse
Nothing about root prevents you from running a copy of OTA2.1 for a couple of days in order to capture the URL; that's what Nandroid backups are good for. S'pose you could run Plain Jane or Ivanmmj's Official and add back in the updater apps & certs if you really needed root in the meantime.
OTOH, it's been mighty quiet the past few days; I'm starting to wonder if there was a problem with the new OTA, and VZW pulled the plug on it.
bftb0

DROID Eris Update/Root Thread: 3.14.2010 -- Root Attained

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.

Devs Need volunteers that are using 1.5

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?

[Q] Dexter mod ?

Hi I am a newbie I did everything the instructions told me to do but when I put the sd card in my a7 it said bad can't open file what did I do wrong I wiped the a7 I clean the cache I cant figure out what I did wrong I even formatted my micro sd card please help me
SD card had to be formatted as Fat32 not NTFS...
Regards
how do i format it like that
opening update package
i tired it again and it says can't open/sdcard/update.zip(bad)
Geekylj said:
i tired it again and it says can't open/sdcard/update.zip(bad)
Click to expand...
Click to collapse
Update. with a cap U name of file. It will not work.
Geekylj said:
i tired it again and it says can't open/sdcard/update.zip(bad)
Click to expand...
Click to collapse
Also, downloads for Dexter's mods have historically been buggy for many users. The file you download (through 1.3) should be around 100MB. The exact size varies between versions. If the above suggestions don't work for you, try downloading the file again.
If you still have issues with the downloaded file, other users have found download success by using a browser download plugin called flashgot. It only works with Firefox and Thunderbird though.
http://flashgot.net/
I had an issue with the download with similar results to yours. My download was only about 63K whem it should of been a little over 100MB.
I had to start down loading the 1.2 update, that would start to download the whole 1.2 file. I'd cancel the download then download 1.3. For some reason after that it downloaded the complete 1.3 update file and I was able do the update.
So, check your downloaded file size and see if that's you issue. Also make sure you rename it Update with a capitol "U".
how long does the download take? i followed the instructions and my screen went to a picture of an android? and a box and stayed that way.
mattduck said:
how long does the download take? i followed the instructions and my screen went to a picture of an android? and a box and stayed that way.
Click to expand...
Click to collapse
Did you boot into recovery (1. by turning off the unit, then power it on by holding the power button for a second, release, and then hold again until the recovery menu pops up), or did you use the settings menu to run the Update file (2. Open Settings > About device > System updates > Update device)?
If you did option 1, the soft keys on the side of the tablet allow you to navigate from the image you reference (android robot & box):
Search Key = Up
Back Key = Down
Home Key = Menu
Menu Key = Select
When you see the robot, press the Home key to take you to the update menu. Navigate the menu to clear your cache. After the cache wipe is complete, select the option to install Update.zip. Give it about 10min to run through the update, and it should reboot. If it reboots into an Elocity Logo loop, long press the power key until it shuts down. Your next boot should take you into a properly functioning tablet. Depending on the version of the OS you currently have installed, the update may retain your current apps and settings.
I haven't tried option 2 in a while, but it should do everything for you automatically - but it will probably factory reset the tablet and you'll lose any previously installed apps.
thanks. Did not know this when i posted found out byaccident when wipinfg off fingerprints. Wish they sent directions with the A7.
mattduck said:
thanks. Did not know this when i posted found out byaccident when wipinfg off fingerprints. Wish they sent directions with the A7.
Click to expand...
Click to collapse
NP. Did exactly the same thing back in December.
if you have not solved your issue I believe I had simular problem. the file when you download is already a .zip file. So when you rename it just rename it "Update"
Another newbie here with a question.
My new A7 is due to be delivered tomorrow.
From what I have gathered so far from this board is that the Dexter Mod allows you to get apps from google marketplace, correct?
I am not sure which version of firmware will come on the A7 but I am going to assume that it will not be the latest one released in February.
My question is should I do the firmware update first, and then download and install the Dexter Mod?
Thanks in advance.
rharrad said:
Another newbie here with a question.
My new A7 is due to be delivered tomorrow.
From what I have gathered so far from this board is that the Dexter Mod allows you to get apps from google marketplace, correct?
I am not sure which version of firmware will come on the A7 but I am going to assume that it will not be the latest one released in February.
My question is should I do the firmware update first, and then download and install the Dexter Mod?
Thanks in advance.
Click to expand...
Click to collapse
Dexter's mods have all been based on firmware updates from Elocity. He has kindly added market functionality and fixed a few bugs. I don't see any value in updating with Elocity's firmware prior to installing Dexter's latest.
As the other poster said there is no need for the elocity 7 update but if I were youI would keep it handy. I had a problem with the mod and had to reset the device with the old firmware. Also it seems a weird problem with android reading the file as when reading in astro the upddate.zip looked like update.zip.zip. w
Wierd.
So you just write update i dont even capitalize it.
Also want to add as newbie to andrid as well and it makes a huge difference in performance too. Think it is fast now when you put the mod it seemed to increase overall performance for me which I did not expect.
Good luck
Rob
robbbzilla said:
As the other poster said there is no need for the elocity 7 update but if I were youI would keep it handy. I had a problem with the mod and had to reset the device with the old firmware. Also it seems a weird problem with android reading the file as when reading in astro the upddate.zip looked like update.zip.zip. w
Wierd.
So you just write update i dont even capitalize it.
Also want to add as newbie to andrid as well and it makes a huge difference in performance too. Think it is fast now when you put the mod it seemed to increase overall performance for me which I did not expect.
Good luck
Rob
Click to expand...
Click to collapse
That is not an android problem. That is what happens when windows explorer is set to hide known file extensions and people dont think when remaming things.
Please do not insult people because we lack knowledge which is why we are here to figure out what is going on. I had no idea windows explorer was set to hide file extensions. I never set it that way nor was i ever told before now. Now that I know i can do something but I was thinking, maybe i do not know what i am doing but you could offer help without making me feel like an idiot.
Rob
robbbzilla said:
Please do not insult people because we lack knowledge which is why we are here to figure out what is going on. I had no idea windows explorer was set to hide file extensions. I never set it that way nor was i ever told before now. Now that I know i can do something but I was thinking, maybe i do not know what i am doing but you could offer help without making me feel like an idiot.
Rob
Click to expand...
Click to collapse
So it is not OK for me to point out an obvious mistake (seriously, this one is like calling grass purple). BUT it is perfectly fine for you to assume that it is a "problem with android" and disseminate misinformation like its your job.
Yup, I am obviously in the wrong.
It is obvious to you. I made a mistake and never said I was an expert and pointed that out in my response by saying I was a newbie too and this was what happened to me and my best guess was what I said. I never said I knew it was an andriod glitch but because I had no other idea until someone like you with more knowledge chimmed in.
All I am saying is you could have corrected me as a newbie with a sense of friendship and not superiority. I was sharing my experience to help someone else. That is all I want to do. I am no expert and am learning as I go.
I have seen others in linux forums when i started with that with the tone. Maybe it seems like thecolor of grass to you but is not so obvious to others. If I sounded like I was telling people mis information then I apologize. That was not my intention.
It is up to you how you treat others and if it feels like the right thing then that is your right. Just understand that some of us are not out to show we are smarter than anyone else and are just trying to help even when we make wrong assumptions.
Thanks for correcting me and setting the record straight.
Rob
rename teh update - update- DONOT PUT THE ZIP PART.
i had the same problem. i noticed the elocity update did not use the zip in the update name.

Build.prop of newest update?

If someone has been able to properly update can you please pull the build.prop and post it up here? I'm using enomthers ROM and want to get rid of the annoying update message.
If your getting the message, download the file and give us the location / filename and i'll be happy to give you the current buildprop
Ok even though I've been a nexus one owner for over a year now and have flashed various roms, and know how to use adb, I have not a clue how to do that. Tell me step by step and I'll do it.
ksc6000 said:
Ok even though I've been a nexus one owner for over a year now and have flashed various roms, and know how to use adb, I have not a clue how to do that. Tell me step by step and I'll do it.
Click to expand...
Click to collapse
Install alogcat or a logcat logger from the market and then do a checkin (call *#*#2432546#*#*) then filter the logcat (Menu - Filter from within alogcat) and search for http or .zip
Hollow.Droid said:
Install alogcat or a logcat logger from the market and then do a checkin (call *#*#2432546#*#*) then filter the logcat (Menu - Filter from within alogcat) and search for http or .zip
Click to expand...
Click to collapse
I don't think it worked. I installed alogcat, opened it, then went to my dialer and typed that in...and then now my notification bar no longer shows the update, but shows "Checkin succeeded"..so went back to alogcat, hit filter and typed in http and none of these look like the right links. it's the link that goes along the lines of //android.clients.google.com/checkin (1 requests sent).
filtering by zip comes up with nothing.
also as i said above now my update message is not in my notification bar.
Okay. got the update thing back. went into settings>about phone>system updates and now it's showing there again.
Connect the phone with your computer.
Run adb logcat and make sure your phone's logs
Download the Update
Send us the complete output of adb logcat after downloading has started
georgemv said:
Connect the phone with your computer.
Run adb logcat and make sure your phone's logs
Download the Update
Send us the complete output of adb logcat after downloading has started
Click to expand...
Click to collapse
Just to be clear once again, I don't WANT the update..so by trying to install it, it should fail as I have a custom recovery and ROM right? I don't want to screw up my setup.
EDIT: F$ck. Sorry guys I think I might have screwed it up. I ran adb logcat, and instead of going into settings>about>system updates and hitting download I hit install now from the notification bar thing. The phone rebooted and then the installation cancelled. And looking through the logcat I didn't see any links so I decided to try it again, but now when I go to settings>about>system update it says my phone is up to date. I've heard that people who don't want the update try that and let it fail so that it doesn't bother them again, but also heard that it doesn't work as the message comes back after a little while. Hopefully it's the latter for me so I can get it right this time. If and when it does come back, am I correct in assuming that what I should do is go to settings>about>system update and try to download it there rather than hitting the install now option from the notification bar?
It should fail with a custom recovery, but do take a backup just in case.
Flash FOTAKill and don't bother yourself with build.prop and such.
Would you mind then sending me a PM with your IMEI and SN so I can fake them to Google and get the download link?
I guess he does mind...
Makes sense. It's a hard decision

Categories

Resources