Related
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
Seems there is an issue affecting most devices when ro.serialno is not set in build.prop.
ANDROID_ID is generated by running the ro.serialno through a command, if not set then ANDROID_ID is always the same. Some apps on the market, for me it is "Fast Web Installer" from appbrain that is giving me an issue because my ANDROID_ID is currently the magic number = 9774d56d682e549c
Seems some other developers use the Android_ID to identify handsets on the market when apps are installed. There is an app on the Market to view the android_id and if rooted be able to change it.
I'm about to update my build.prop with my device serial number and see if I get a true random ANDROID_ID
I'm currently using Cog 2.2 beta7
Could someone check the build.prop file on a stock ROM? By stock I mean truly stock because I believe the handsets from the factory have this set, but when we flash the JF6 it no longer has the ro.serialno.
Edit: http://code.google.com/p/android/issues/detail?id=10639
looks like adding ro.serialno does not help us since the ROMs we use are not true first boots, the system.db already has the value set so it doesn't generate a new one.
next I will try removing the ANDROID_ID from the system.db and see if that fixes it...
im bookmarking this, it would really be a big help
well i found an app that allows you to change it, but can't find a way to set it to what it should be from factory using serial number.
would be easy to get an app to use same method and just ask for your serialno if not set
turns out cynogen had the same issue since the ro.serialno was not set, they added code recently to generate based on serialno and first boot time so it would have seed data even if serialno was not set.
http://github.com/CyanogenMod/andro...mmit/81ed751a1dcf1e7c722db2cdded38bef4308a1c5
so something in samsungs source may be goofed cause they don't seem be pulling ro.serialno, i set android_id to "" in the database and rebooted, it stayed the same.
I then deleted the entry all together and rebooted and it went back to the magic number.
edit: well checked with getprop and ro.serialno is blank even though I set it in build.prop
I'm done tinkering for tonight, I changed my value manually for now to a randomly generated hex value and my "fast web installer" is working fine now.
Does seem to be an issue though, and not sure the code solution on cyanogen's site is best way either. They are looking at using ro.serial and time to generate random just in case the serial is blank.
If your someone who purchases a lot of apps, then it might be a good idea to make sure your android_id is random and then keep it so you can restore it later if needed. Some app developers use this to identify the end user.
If you go back to 2.1 you can retrieve your original Android ID and manually set it in Froyo
I did a fresh restore to JF6 and it was set to a unique one, then done a restore to a nandroid I had from an old 2.1 install and it was the same ID. So hopefully that one is unique to my device
well i installed the froyo leak on my gf's captivate after i had zero problems after like a week or 2....now she needs an app in the market and calls me complaining about how she cant find it. Whoops, forgot to tell her about that little tid bit!
Any work on at least a temporary fix? I was going to just tell her to sideload the app using sideload wonder machine, but i can't find an .apk for a free app on the market!!
well i installed the froyo leak on my gf's captivate after i had zero problems after like a week or 2....now she needs an app in the market and calls me complaining about how she cant find it.
Click to expand...
Click to collapse
This is normal for pre-release firmware.
1. Root her phone.
2. Edit her /system/build.prop file
3. Find the line that starts with this: ro.build.fingerprint=
4. Make it say this: ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys
Save, exit, reboot.
The fingerprint line is carrier agnostic. Android Market just looks for known (to Google) fingerprints. If you have a known good one, you get to see all the protected apps that your unknown fingerprint prevented you from seeing.
Joe1981AL said:
well i found an app that allows you to change it, but can't find a way to set it to what it should be from factory using serial number.
would be easy to get an app to use same method and just ask for your serialno if not set
turns out cynogen had the same issue since the ro.serialno was not set, they added code recently to generate based on serialno and first boot time so it would have seed data even if serialno was not set.
Click to expand...
Click to collapse
hi im curious about the name of the app that let you change the android id can you post a link for it or the name of the app ty
Edit: found an app but havent tried it heres the link anyone who rooted the phone with busybox can try this http://adaptiveeng.blogspot.com/2010/10/android-id-changer.html
I am having this same problem. I wanted to use the fast web installer but it wouldn't work as well.
Has anyone figured how to change it so this will work?
jdsemler said:
This is normal for pre-release firmware.
1. Root her phone.
2. Edit her /system/build.prop file
3. Find the line that starts with this: ro.build.fingerprint=
4. Make it say this: ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys
Save, exit, reboot.
The fingerprint line is carrier agnostic. Android Market just looks for known (to Google) fingerprints. If you have a known good one, you get to see all the protected apps that your unknown fingerprint prevented you from seeing.
Click to expand...
Click to collapse
thats great! thank you for the quick reply! just tried this on my phone and it worked great. I knew it was a common problem but never found a real answer on what to do. It's just too bad she lives 6 hours from me and i'm not sure i feel like writing her a step by step (as in button by button) guide for her to do this. She will live without the app for another week or so haha.
I was hoping that there would be an app on the market that would allow me to put her a random android id like the above guy stated. Anyways...thanks again.
I'm not running Cog2.2b7, but it seems to me you could use this method to generate yourself a unique Android ID using the emulator option under Make a new androidID with the Emulator. Then, using this command to pull the unique ID off the emulated Android device:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Once you have the Android ID, close out the emulator, and put this Android ID into your phone.
Like I said, I'm not running that version of Cognition, but give this a shot.
i am curious as to what the difference is between what i did (modifying the build.prop file as stated a few posts up) and getting my unique android ID and insterting it back into the phone while running froyo? I can see the apps on the market, was that not the issue at hand with the android ID?
The Android ID is a unique identifier for your phone.
The fingerprint is more of a signature to tell the Android Market that you have a known good firmware and what firmware version it is (2.2 in this case). When you have an approved signature, you get to see apps that were promoted to the market with the "Protected" flag enabled. If you do not have an approved signature, it is as if those apps aren't there.
Need clarafication
Hi Im interested in this ID changing process, but have a question about it. Now does this also fix other issues with 2.2 like not being able to log in to certain apps because the ID of your phone has been changed? I have a captivate but I have been reading thru the threads and noticed a lot of devices, well the ones who upgraded to 2.2, are having the same issue. If this does that i thank you very much cuz i have been looking for a fix for a few weeks now.
jdsemler said:
I'm not running Cog2.2b7, but it seems to me you could use this method to generate yourself a unique Android ID using the emulator option under Make a new androidID with the Emulator. Then, using this command to pull the unique ID off the emulated Android device:
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/accounts.db "select * from meta";
Once you have the Android ID, close out the emulator, and put this Android ID into your phone.
Like I said, I'm not running that version of Cognition, but give this a shot.
Click to expand...
Click to collapse
hi how can i change my android ID MAnually seems the link i provided on top doesnt work on me xD
I have been successful with these steps in getting my phone's id corrected (Cog 2.2 Beta6)
adb
su
sqlite3 /dbdata/databases/com.android.providers.settings/settings.db "update secure set value = '[your HEX android id]' where name = 'android_id';"
sqlite3 /dbdata/databases/com.google.android.gsf/gservices.db "update main set value = '[your DEC android id]' where name = 'android_id';"
reboot
I got my old id by doing a text search with notepad++ on a backup made with rom manager.
jfl0wers said:
I have been successful with these steps in getting my phone's id corrected (Cog 2.2 Beta6)
adb
su
sqlite3 /dbdata/databases/com.android.providers.settings/settings.db "update secure set value = '[your HEX android id]' where name = 'android_id';"
sqlite3 /dbdata/databases/com.google.android.gsf/gservices.db "update main set value = '[your DEC android id]' where name = 'android_id';"
reboot
I got my old id by doing a text search with notepad++ on a backup made with rom manager.
Click to expand...
Click to collapse
I did play around with sqlite3 as well, I didn't search through my old backup though I just put JF6 back with Odin, one click root, and downloaded "Android ID" from the market, wrote down the ID, and then flashed to cog 2.2 beta7 and restored.. Of course then setting my ID with app..
I know I went the long way, but it worked
When I went and flashed back to Coke .40 (to unlock GPS after letting Verizon customizations run), then a stock 2.x series radio rom for my Sprint Vogue (that I normally run on Verizon), the ERI disappeared! Its completely gone from the system. I look at the system information, and ERI reads "version 0," and when I browse to my /ERI folder, it is empty.
The phone seems to work fine, but I cannot program it via *228 because the ERI is gone! lol
My request is this, can someone with a Sprint Vogue please ##DIAG# and browse to /ERI with Bitpim/QPST and dump the file in ERI and post it here, rared. Trying to manually upload it is my last resort. I tired uploading a Verizon ERI and even a Bell ERI, but the file has different names on each carrier (which I think may be way they won't work).
Unless someone else has ran into this issue (and I've dug on google for the last week finding nothing), I really don't know what else to try. I'm praying that just dumping a stock Sprint ERI will make the phone work like it used to.
And yes, I am 100% sure it is gone, the folder is empty!
http://forum.xda-developers.com/showthread.php?t=377514
Wouldn't you be able to re-flash from the original Sprint RUU update exe file?
Doesn't that restore the vogue to factory?
Or is this a special file that can't be recovered?
If you can PM me on how to recover that ERI via BitPIM or QPST, let me know.
I still have another family member using a Vogue on Sprint service.
see, flashing the original ROM is what got me into this mess in the first place. Even if one of the old factory ROMS has an ERI update, I prob can't use them because the run during the customeization phase, and all the instructions for unlocking a borked Verizon GPS (i converted this phone to verizon) say to not let customizations run. Perhaps I should let the Sprint Customizations run on the GPS ROM?
As for the eri file it's self, gettint to it is pretty easy. Type ##daig#, find the com port that your phone is on in device manager. Open bitpim and for phone settings choose "other" and then select the com port of you Vogue. Then go to view and select "file system". After that you can browse the file system and the ERI is in the /ERI directory. Right click the file (whatever its name might be) and choose to extract it somewhere. Then zip/rar it.
If you could do that for me it'd be awesome. I've been trying to get NuAngel to do it for me, but he's been busy.
Hmmm...
I don't see an ERI on mine either?
Does that get deleted when you flash it to Android maybe?
Only thing I have not tried is re-flashing the original RUU file from Sprint.
I will try that when I get home and see what I can find.
strange. in my device settings, ERI is being reported as verison 0... perhaps I just need to let Sprint customizations run... I need to find my Vouge, I have no clue where I put it last.
I like to update CM every night with CyanDelta, but one drawback with this phone is that every time I do, it resets to the default DPI. The default DPI, 460, is way too big for me, and I like to have it around 360. Is there any way I can change this every time I flash without having to edit the build.prop each time? Thanks!
I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.
teeg07 said:
I'm kind of curious about this too. although a quick search tells me that it basically isnt possible unless you either create a zip to change it and flash that every time you flash a new nightly, or set an app to auto start when you boot the phone to change it. You would have to reboot once again to get the change.
Click to expand...
Click to collapse
I've thought about making a zip to flash it, but doesn't build.prop change with every nightly? I wonder if there is a way to make a script that will just find and change the DPI in build.prop.
any updates on this? I have been struggling with this problem for years. I've also tried different software to change it but it does often break my play store for some reason so I do it manually every time.
i would like to know if that's possible, too...
it should be, despite the build.prop changing with every build, i assume(!) the lines (read: line numbers) remain the same... so, one could write a script, that changes EXACTLY the necessary line ("ro.sf.lcd_density=[whatever value is preferred]", i for one change it to 400 instead of 480), while leaving the rest untouched... and even if the line numbers change, could one find the line and replace it?
correct me if i'm wrong, please
If i knew how to write scripts for android (or better TWRP for that matter), i'd do it myself, but i have no idea...
I don't have a g2 but I was googling for this exact thing and turned up here... There has to be a way to create a .zip to flash with updates... i just don't know how
upon further googling i turned up this -
http://forum.xda-developers.com/showthread.php?t=2405288
here http://forum.xda-developers.com/showthread.php?t=2612552
Sent from my LG-D802 using xda app-developers app
Hey there,
So I just installed Hyperdrive 17.1 via Safestrap onto my AT&T Galaxy S4. Everything is going smoothly, except one key issue. The build prop is entirely Verizon based and that has somehow confused the Google Play Store into not allowing me to install the following apps I need and use:
Hello SMS
WhatsApp
AT&T Visual Voicemail
Starbucks
GoWallet
It says that these apps don't support my version of Android, which ostensibly is 4.4.2, but something in the build prop must be fooling the Play Store into thinking that it's incompatible.
So, I guess I should edit the build prop. I've looked in the Hyperdrive thread for someone who had the same problem as I did, to no avail. Then I tried to find a stock build prop for an AT&T GS4 running NC1, but to no avail. And besides, I'd rather just edit one entry if that would be easier and give me a better chance of solving the problem without bricking my phone. I believe the entry most likely to help me would be ro.build.description? What would that entry read on stock NC1?
Thanks for your help!
Try the AT&T build.prop/APN file found here:
http://forum.xda-developers.com/showpost.php?p=51112381&postcount=9
However, be aware that when I flashed that file over Hyperdrive 17.1, it interfered with Hyperdrive Tweaks (which would then force close when trying to open). I'm not sure if the dev has fixed that problem... I moved on to a different ROM because at the time there wasn't a known solution I could find to the "+ being added to incoming/outgoing calls" issue (app Prefixer seems to be the solution most commonly mentioned, now).
I encountered the same problems with downloading apps based on the phone identification that you are seeing, and I did change one build.prop item manually (I forget which one), but it wasn't enough to get the store to properly recognize the phone. I think there are a few of them that need to be changed, and I didn't invest time to figure it out.
You will probably fix it if you go through the ATT build.prop file line by line and adjust on your phone just the items that refer to phone model ID... that would probably not break Hyperdrive Tweaks.
Marc