Build.prop of newest update? - Nexus One General

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

Related

I got a system update. US 1.5

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

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?

Screenshots of update. Keep your phone charged, update will be postponed

So I got a notification in the bar stating "Connecting to DM server". About 30 min later, another message stating "Update Available". Well, my battery is about 25%, so it postponed the update. Good thing though, it says to click the "Software Update" in the System Settings when the battery is charged.
See screenshots below.
My friends phone the same issue
My friend has the same issue. So I'm charging it for him. Going to run a log on his phone once we can upgrade it and see if we can get some nice information like a URL and such.
androidmonkey said:
So I got a notification in the bar stating "Connecting to DM server". About 30 min later, another message stating "Update Available". Well, my battery is about 25%, so it postponed the update. Good thing though, it says to click the "Software Update" in the System Settings when the battery is charged.
See screenshots below.
Click to expand...
Click to collapse
Would you mind trying to do an adb pull /cache to try and grab the ota zip file?
Cheers
s0niqu3 said:
Would you mind trying to do an adb pull /cache to try and grab the ota zip file?
Cheers
Click to expand...
Click to collapse
Yes this would be awesome.
s0niqu3 said:
Would you mind trying to do an adb pull /cache to try and grab the ota zip file?
Cheers
Click to expand...
Click to collapse
I have adb working at home, cant remember where I got the driver though for the phone. I put the phone in debug mode, hook it up via usb. WinXP pops up and wants a driver.
Where do I get this driver?
androidmonkey said:
I have adb working at home, cant remember where I got the driver though for the phone. I put the phone in debug mode, hook it up via usb. WinXP pops up and wants a driver.
Where do I get this driver?
Click to expand...
Click to collapse
Found it on Samsung site. nevermind.
androidmonkey said:
I have adb working at home, cant remember where I got the driver though for the phone. I put the phone in debug mode, hook it up via usb. WinXP pops up and wants a driver.
Where do I get this driver?
Click to expand...
Click to collapse
Hi again,
Do you need 32-bit or 64-bit drivers?
I have the 64-bit driver package on dropbox, can PM you the link, but I don't have the 32-bit drivers, sorry
I love how it says Congradulations! like you just won the update lottery.
So where would this update file be located? I have Dalvik Debug Monitor running. The only folder that has a change date of today is the "Data" folder. I cannot access anything in it though.
I haven't installed the update yet, if someone tell me the steps to get the files you need, i could help out
If you're rooted -- you should be able to look in /cache for a file named update.zip.
j0hnZ said:
I love how it says Congradulations! like you just won the update lottery.
Click to expand...
Click to collapse
Pretty much! Some of us are getting updates, others are still waiting.
ipugh said:
If you're rooted -- you should be able to look in /cache for a file named update.zip.
Click to expand...
Click to collapse
Im not rooted. Havent had the urge to do it, dont want to spend all my time modding my phone like I did with the G1
@ j0hnZ
so you have updated yours? if yes would you mind sharing the status of your phone please.
iynfynity said:
@ j0hnZ
so you have updated yours? if yes would you mind sharing the status of your phone please.
Click to expand...
Click to collapse
What status are we looking for?
I have an updated phone right here. (not mine though.)
swehes said:
What status are we looking for?
I have an updated phone right here. (not mine though.)
Click to expand...
Click to collapse
is it running smoothly? and is it a stock vibrant?
iynfynity said:
is it running smoothly? and is it a stock vibrant?
Click to expand...
Click to collapse
Stock with root (the root stayed)
Running smoothly. I don't see any issues with it. But it isn't my phone and I have lots more stuff on my phone so I will be able to run a better test.
Battery needed to be at least 50%. Updating my phone now.
swehes said:
Stock with root (the root stayed)
Running smoothly. I don't see any issues with it. But it isn't my phone and I have lots more stuff on my phone so I will be able to run a better test.
Click to expand...
Click to collapse
Any way you could pull the .zip out of the /cache folder and send a PM to s0niqu3? It would help the devs out as I don't believe anyone has done that yet (could be wrong and just don't see it though).
ShinyBuddha said:
Any way you could pull the .zip out of the /cache folder and send a PM to s0niqu3? It would help the devs out as I don't believe anyone has done that yet (could be wrong and just don't see it though).
Click to expand...
Click to collapse
I can not find the update.zip file. The only thing I see is a downloadfile.apk in there. I think it downloaded this file first, then restarted the phone into an installation mode. Well there it did the rest as in downloading the zip file. When going back trying to find it, it is gone. Not sure what else to do. I uploaded to files of the log if there is any smarter people than me that can interpret it.

Can't find my 2.3 update

I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).
DMC78 said:
I was out of the country and used my phone on wifi. Of course as soon as I am gone, I get the notification for the 2.3 update. I downloaded it (160 megs or so) over wifi, but didn't install it since I wasn't sure if it would turn off my airplane mode and I would get slammed by tons of txt which add up $$ quick. It was always in my notification bar for the update and when I cleared all notifications it was still there under "ongoing". I landed back in the US and turned on the cell. A few minutes later I looked in the notifications and the update was gone. Anyone know where the file was saved on my phone so I can go ahead and run the update? Thanks in advance. I checked the "about" screen and I am still running 2.2 (was hoping it automatically updated without me knowing it).
Click to expand...
Click to collapse
here, download THIS FILE, and rename it to "PD15IMG.zip"
place it in the root of your sdcard, reboot into hboot/bootloader by holding power +volume down buttons, then follow the onscreen instructions.
good luck
That file saranhai gave you is exactly what you need. Do as he says, and you'll get what you are wanting. Its the least dangerous flash you can make to your phone. If you walked into T-mobile and asked for the update they would pop in an sd card with that file and follow the same procedure.
BTW, its important that the name be all caps.
Sent from my HTC Glacier using XDA App
Correct me if I'm wrong, but I believe doing this manual install will wipe your device's memory. Just a heads up as a reminder to backup your data beforehand.
Yeah, it will. Sms backup & restore will save your sms messages at least.
Sent from my HTC Glacier using XDA App
Thanks for the help. Is there any way to run the update that I already downloaded ? I assume that it is stored somewhere, and wanted to see if anyone had an idea where.
Hello,
I really dont know if the file has the same name but you can try using find.
Something like that :
Code:
adb shell find / -name PD15IMG.zip
Regards

[Q] Random reboots - Is there a log I can view?

Hey all,
running CM7 (in particular this), and have always experienced these random reboots since I rooted/ROM'd etc.
I have worked out it is to do with 3G/4G data connection and/or swapping back to 2G to save battery or something along those lines. I have tried different radios, but not other ROMs (dont particularly want to change ROM).
My question is, is there a log file or some sort of diagnostic i can run to see exactly the cause so i can better find a fix/report the bug?
Cheers.
Ye, just write su than logcat > /sdcard/logcat.txt in terminal emulator this will save the logcat to the logcat.txt file, you can than copy that to your pc and see what happened before the reboot.
I'm going to try and provide a log too. Problem is, I usually only notice it after a while, when I take my phone and see that it has rebooted and waiting for PIN.
crnkoj said:
Ye, just write su than logcat > /sdcard/logcat.txt in terminal emulator this will save the logcat to the logcat.txt file, you can than copy that to your pc and see what happened before the reboot.
Click to expand...
Click to collapse
Thanks man, will do this very soon and post my log (if thats ok? and if there isnt anything personal in there)
EDIT: Holy c***. its 14,500 lines of code... what should I be looking for?
I have found there are several errors relating to GTalk (which i never/cant use). I didnt realise I hadnt Frozen this with Titanium Backup, so I have done that now.
I was also getting errors relating to sqlite and the Market, but not sure this is causing any reboots as yet, the error was as follows:
Code:
I/Database(12351): sqlite returned: error code = 0, msg = Recovered 8 frames from WAL file /data/data/com.android.providers.downloads/databases/downloads.db-wal
I will see if I get any more reboots and let everyone know, but I suggest freezing GTalk as a start if you are getting reboots.
FWIW the culprit in my case was SKYPE
wintermute000 said:
FWIW the culprit in my case was SKYPE
Click to expand...
Click to collapse
Really! Interesting. Did you uninstall or freeze?
Also, I can tell you that freezing GTalk definitely has reduced the number of reboots, but not eliminated it. I have just tried uninstalling Skype (I never use it anyway) as wintermute000 suggested, and will follow up again in a few days.
Uninstalling Skype has greatly helped. Thanks wintermute000!
No worries. I just run skype when I need and exit fully when done, no need to freeze or uninstall
Sent from my Sony Tablet S using Tapatalk
You can redirect stdio (will increase logcat events):
http://developer.android.com/guide/developing/tools/adb.html
sometimes dmesg it's useful too...

Categories

Resources