Allways the same Android_ID - HD2 Android Q&A, Help & Troubleshooting and Genera

I dont know if this problem is known here,
all (in my opinion froyo builds) have the same android_id
In every build the id is: 9774d56d682e549c
this cause problems with some apps of the market because they use this id to identify the device. for example imobsters ;-)
see this post
forum.xda-developers.com/showpost.php?p=7251507&postcount=1110
sorry for my bad english

I think this causes a problem too with pMessenger, but I'm not sure if the Android ID or the MAC address is being used by pMessenger. However, both of them are identical on all our devices for now.
I think it should be trivial for the devs to fix it, but they are concentrating on fixing more major things now.

i am not sure, but maybe there is a way to change that id:
NOT ugly market fix
No more emulators!
Push this over to your phone, and you'll be able to get a working android ID without any sort of silly fooling around.
To repeat and clarify: You will get a fresh working Android ID, from Google, just like a phone.
From early testing it still appears SOME paid apps may be missing, but this is definitely a better solution than an ID from the 1.6 emulator as I continue to look into the issue. (I think this is actually less an Android ID issue than it is an issue with PDN being a configuration that some apps refuse to support, be it resolution, version 2.0 or whatever)
(I've also found that using your phone's ID on your PDN may "taint" what you can see in the market on your phone. Personally, I'll be moving away from sharing an ID with my phone)
Instructions
1) You'll need to remount system as R/W regardless. so let's start with that:
"adb remount"
2) If you want to start over clean, I'd recommend clearing market cache and killing your existing android ID.
adb shell sqlite3 /data/data/com.google.android.googleapps/databases/gls.db "update meta set intvalue='0' where name='androidId'";
To clear market cache: Settings->Manage Applications->press menu button->choose "Filter"->choose "All"->Scroll down to Market and select it->choose "Clear Cache"
3) Apply this hack
"adb push framework.jar /system/framework/"
4) Since we replaced a main framework, clear dalvik cache just to be safe, and reboot. Yes, the first reboot will take longer since we just cleared the cache.
"adb shell rm -r /data/dalv*"
"adb shell reboot"
5) Go ahead and log into Google Talk and use the Market to ensure all is working.
Feedback welcome!
File:
framework.jar
Click to expand...
Click to collapse
From here
I dont know if that works because its not for the hd2, but someone could try it.
I Mirrored the file in case it gets deleted:
Multimirror (Rapidshare, zshare etc.)
edit: I dont think that could work, i just tried to change to /data/data/com.google.android.googleapps/databases/ and it didnt exist at all ...

News
strazzere.com/blog/?p=217
but where can i find these "/data/data/com.android.providers.settings/databases/settings.db"

is there somebody out there who can say me how can i change my android_id on my HD2?

Related

bluex problem

Hey guys,
I asked in the apps section about bluex. that I tried to use it to transfer files from my phone to a samsung behold and they told me to type this in the terminal:
mv /data/app/bluetoothFileshare.apk /data/app-private/
but when i did It says:
failed on '/data/app/bluetoothFileshare.apk' - No such file or directory
__________________
mv /data/app/com.alex.BluetoothFileshare.apk /data/app-private
this is case sensitive
enjoy
same thing
samething happened...
failed on '/data/app/com.alex.BluetoothFileshare.apk' - No such file or directory
does it matter that I have cyanogen v3.5.2 and my apps are on my sdcard?
isnt bluex automatically in the app-private folder?
so....
Is there something I have to do to get it to work with the samsung behold? Or does it just not work with that phone?
the behold would have to be rooted to receive files...i dont know if it works for just sending files
as far as i am aware the behold isnt even android powered so i dont know how you would expect it to work (in which case negate my last statement)
try this on the g1
cd /data/app/
ls (this will list all the files in that directory)
look for anything relating to bluetooth
mv /data/app/*filename.apk*/data/app-private/
hopefully with apps2sd it will all work out with the sym links
personally i dont use apps2sd so this could be the root of your troubles
instead of this code you could try a "root file browser"
and then im sure you would be able to cut and paste from one folder to another
out of curiosity, did u get bluex from a 3rd party source or the market? if it was the market i doubt there would be any problem (but where is the fun in that?)
good luck
oh, one little note...
if in the unlikely event something screws up n u need to reflash or anything else along those lines, please dont blame me
(im sure you wouldnt anyway, but just incase)
Gonna put my two cents in on this btw.
I'm trying to "pirate" this app (install it after getting a refund from the market. If I give up or succeed in "pirating the app", I'm going to rebuy it), for the sole reason I enjoy a challenge.
I believe that the app is infact not looking for whether a copy is in the app-private folder, but in the app folder.
Let me explain;
You install bluex from the market, it goes to app-private.
you give the application root permissions, and it checks to see whether there is a copy of it in the app folder. No copy, runs fine.
You install the app from an outside source. The install goes to the app folder. You copy the .apk to the app-private folder. The application looks for a copy of itself in the app folder, and OH NOES! it's there, and blocks all access to itself.
Is there anyway to adb an install to the app-private folder?
also, if the app locks itself, uninstall it, then *reinstall,* otherwise, even if you manage to succeed in installing the application and circumventing the security protection, you'll still be locked out of the application.
Bluex solution
this is how i did it - avoiding having to manually do anything
download version 1.1.2 here
rename it to com.alex.BluetoothFileshare.apk (case sensitive)
then stick it on your SD
then download SUFB (super user file browser) here
install this via watever method you normally do (personally i use ESTRONGS File Browser - free from the market)
open SUFB and navigate to /sdcard, find bluex and long press it and select copy and then navigate back to /data/app-private
press menu and select "mount /data RW" then paste bluex into app-private
press menu and select "mount /data R" to stop you screwing anything up by accident
reboot (not necessarily compulsory but it didnt work for me without it even tho bluex did appear in the dash thingie)
after reboot open bluex, enable bluetooth, enable server and enjoy
hope this helps
(the first time i did do this all in the terminal but was too lazy to type it after a couple of reflashes)
what i did find strange was that when doing a straight "mv ....." it worked without remounting RW but when using the file browser it wouldnt work without the remount
enjoy
i do encourage anyone who tries this to buy the app - i too did it for the challenge and then bought it (after my last reflash) (i was paranoid that after a reflash that i had schedualed that i would have to pay for it again). it is a great app and the developer deserves the £1.50
sorry, the links have been removed (for obvious reasons). google for droid appz and you will find a great site with some tips, tricks and appz
what phones does it work with?
does bluex only work with other g1's and android phones? or can you fileshare with blackberry's, iphones, etc.
iv not sent or received from any other phones (im in thailand now and none of my friends have bluetooth, poor them....) but it works great with my computer and the piece of crap dongle in both directions
so i dont see why it wouldnt work with other phones...its just and implimentation of the OBEX standard that is used for both infrared and bluetooth OBject EXchange
enjoy
garok89 said:
iv not sent or received from any other phones (im in thailand now and none of my friends have bluetooth, poor them....) but it works great with my computer and the piece of crap dongle in both directions
so i dont see why it wouldnt work with other phones...its just and implimentation of the OBEX standard that is used for both infrared and bluetooth OBject EXchange
enjoy
Click to expand...
Click to collapse
well I've tried with my friend and girlfriends behold and it will pair but not connect to it. and I'm the only one of my friends that have a g1, they're all iphone junkies :thumbsdown:
as far as i am aware the iphone still cant send or receive via bluetooth just like the g1
i dont think it was introduced in the new firmware upgrade
try it with someone who uses a real phone, not a jumped-up mp3 player
i can pair with my computer but not connect unless its for file transfer
the g1 and iphone only really connect to handsfree kits etc...
try sending something to your computer or something like that, it should work
also, double check that you have server enabled
once you have sent or received from one device, you can set it to automatically accept from that device on all occasions
Bluex>Options>Remote devices options>*device*>automatically accept files
i've been able to send and recieve files from my other phones sony erricson's and random other phones on the bus etc
Root has nothing to do with sending and receiving bluetooth. the only reason you need root on android is because the profile(obex) needed to exchange files is not "built-in" to android. In order to support this profile, the developer probably programmed his app to change read-only files, and that would be why the g1 requires root for obex. phones that ACTUALLY support obex don't require root/superuser/administrative privledges. So in other words, you don't need root for obex unless you're using android.
You guys shouldnt be openly discussing pirating applications. Thats not nice, and you are posting on a DEVELOPER forum. What's wrong with you guys?
garok89 said:
the behold would have to be rooted to receive files...i dont know if it works for just sending files
as far as i am aware the behold isnt even android powered so i dont know how you would expect it to work (in which case negate my last statement)
try this on the g1
cd /data/app/
ls (this will list all the files in that directory)
look for anything relating to bluetooth
mv /data/app/*filename.apk*/data/app-private/
hopefully with apps2sd it will all work out with the sym links
personally i dont use apps2sd so this could be the root of your troubles
instead of this code you could try a "root file browser"
and then im sure you would be able to cut and paste from one folder to another
out of curiosity, did u get bluex from a 3rd party source or the market? if it was the market i doubt there would be any problem (but where is the fun in that?)
good luck
Click to expand...
Click to collapse
garok89 said:
this is how i did it - avoiding having to manually do anything
download version 1.1.2 here
rename it to com.alex.BluetoothFileshare.apk (case sensitive)
then stick it on your SD
then download SUFB (super user file browser) here
install this via watever method you normally do (personally i use ESTRONGS File Browser - free from the market)
open SUFB and navigate to /sdcard, find bluex and long press it and select copy and then navigate back to /data/app-private
press menu and select "mount /data RW" then paste bluex into app-private
press menu and select "mount /data R" to stop you screwing anything up by accident
reboot (not necessarily compulsory but it didnt work for me without it even tho bluex did appear in the dash thingie)
after reboot open bluex, enable bluetooth, enable server and enjoy
hope this helps
(the first time i did do this all in the terminal but was too lazy to type it after a couple of reflashes)
what i did find strange was that when doing a straight "mv ....." it worked without remounting RW but when using the file browser it wouldnt work without the remount
enjoy
i do encourage anyone who tries this to buy the app - i too did it for the challenge and then bought it (after my last reflash) (i was paranoid that after a reflash that i had schedualed that i would have to pay for it again). it is a great app and the developer deserves the £1.50
Click to expand...
Click to collapse
Pirated programs IS NOT allowed on this forum.
Meaning if you have to pay for a program, you can not offer it to someone for free.
Warning offered.
my apologies
warning accepted
wont happen again
Idk what ur trying to do but my wifes memoir works flawless with this app and a g1. She can send and receive files from my fone with no problem.
jonnybueno said:
Root has nothing to do with sending and receiving bluetooth. the only reason you need root on android is because the profile(obex) needed to exchange files is not "built-in" to android. In order to support this profile, the developer probably programmed his app to change read-only files, and that would be why the g1 requires root for obex. phones that ACTUALLY support obex don't require root/superuser/administrative privledges. So in other words, you don't need root for obex unless you're using android.
You guys shouldnt be openly discussing pirating applications. Thats not nice, and you are posting on a DEVELOPER forum. What's wrong with you guys?
Click to expand...
Click to collapse
im well aware that phones that already support OBEX dont require root. i hadnt heard of the samsung he was talking about and thought it may have been a soon-to-be android phone...it was released under a different name here and i had interpreted the question as being that the phone ran (or was going to run) android. a simple mistake anyone could make when google is acting up (probably more the ISP than google but you get the point)
as for openly discussing pirated apps, i dont see a problem with it personally as i do things on a try-before-you-buy basis....i know it was stupid posting the links and i apologized for that and the links were removed
hiroots said:
Idk what ur trying to do but my wifes memoir works flawless with this app and a g1. She can send and receive files from my fone with no problem.
Click to expand...
Click to collapse
great. proof it works... iv still only tested it with my laptop

cbackup v0.4 - backup/restore tool

I've been a lurker since I got my eris back when root was a dream. Now I have quite a few things floating around my work dirs that aren't on xda or are wanted, so I figured I would start releasing some of my better/more polished things. So here is my first:
cbackup v0.4
Based upon craft_backup v0.5.3: showthread.php?t=628743 (sorry no links)
Backup and restore apps/data just like craft_backup
Changes/Features of cbackup:
- Change names to cbackup and crestore because I got tired of typing out "craft_backup" and "craft_restore"
- Move backup dir to /sdcard/backups/cbackup/*
- For cbackup, allow a choice for destination in backup dir (defaults to cb<date>)
- For cbackup, automatically move backup dir to timestamped location instead of overwriting it
- For crestore, display menu of all cbackup dirs along with original craft_backup dir if it exists. This menu has the latest last, numbered first with number 1 being the default.
- Works with roms that don't have the busybox symlinks installed
Changelog:
v0.3
- First public release
v0.4
- Fix problem when missing bb symlinks
Disclaimer: I am not responsible for damage caused by this app. I take no credit for the good work done on craft_backup, I just wanted something it didn't do so I hacked it up to suit my needs. Eventually it became nice enough to share. I will not support it, unless there is something wrong with my added code (which is possible, since the listing code is complex). Refer to the original app's thread for almost all problems.
nXuaJunYYc
Testing it now.
EDIT: WORKS PERFECTLY- 5 STARS.
Crestore- not found.... help?
I assume you're running "crestore" and not "Crestore" nor "Crestore-". Can you post the output of:
echo "$PATH"
from adb shell?
If that's fine, I think I know what may be wrong, but try that first
edit:
I'll be uploading a new version in a minute that I think will fix your problems, but if it doesn't, if you could also try the following it would be helpful:
# which crestore
# which sed
# echo abc | sed -es/a/d/
# ls -l /system/bin/crestore
# ls -l /system/bin/cbackup
# /system/bin/crestore
So I got it to find it, but it says not found for everything. Also comes up in Italian no matter what, but no biggie.
or use the eris master app, which can do most of that right now. the good thing is that its in a gui interface. jamezelle and i will be adding additional features later for the backup / restore apps as well. and one thing that we will have shortly is the ability to restore market update links for apps installed outside of the market.
@ECLIPS3:
Sorry, I'm a command line guy and I'm a linux guy. I really don't want to install wine and mono on my poor little linux netbook just to run your app and then navigate a gui. Plus these scripts run entirely on the phone, so you should be able to run them anywhere with only your phone (maybe even using terminal on the phone...haven't tested that yet). And before we start a war, I'm not saying that there is anything with wrong with your app, and I'm sure it has/will help a lot of people who want the easy gui, but it wasn't for me, and I thought other people may feel the same way. There's no reason both apps can't exist. I also appreciate you letting people know in this thread so the less cli-oriented people know their options.
@Erisftw:
That is really strange if it's continuing to not give you a choice for language. Are you sure you flashed the latest one that I uploaded (cbackup-v0.4-signed.zip)? And that you made your backup either using v0.4 or using v0.3 on a phone with busybox properly installed. If so could you copy and paste the first ~20 lines of output from crestore, and let me know if you are on windows or linux?
dont worry, not trying to start a flame war at all. i love diversity and competition as it creates better programs to arise, that ultimately are better for the end user. theres plenty of room for everyone here. i love CLI as well, but not a lot of people do. arent you glad this is a free world to have competition?
Changed to 4, restored. fine, but it has old rosie, and when you click on the app, it says app no longer installed.

ro.serialno and android_id issues

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

Market won't stop force closing! - PLEASE HELP!

Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
maybe you should try an other android rom ?
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
SMS92 said:
Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
Click to expand...
Click to collapse
yz.hd said:
maybe you should try an other android rom ?
Click to expand...
Click to collapse
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
Click to expand...
Click to collapse
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
SMS92 said:
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
Click to expand...
Click to collapse
This should help cos if u do it this way u actually not installing/reinstalling the app. u actually repleace the sys market.app for the original one from the ROM. So there is no way it will not work again if it was working before after u flashed the ROM.
I'm pretty sure it will do the trick, but also I may be wrong .
I had some issue on my ROM with cam.app and this proced. helped me.
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
FIXED! [Edit: not]
Here's what I did.
Downloaded THIS
Extract it to C:\Droid
Boot into Win Mobile and move your data.img in \Android\ into the \Droid\ folder on your PC.
Start > Run > CMD
type "cd c:\droid" (without quotes) to get into the directory you've created.
Type "e2fsck -f data.img" (without quotes) and say 'y' (yes) to all the errors you encounter. There will be dozens. When done you'll be notified the modified data.img has been saved.
Copy the newly modified data.img from \Droid\ to \Android\ on your device.
Boot into Android - things might be a bit slower/laggy at first.
All should be well!
Edit: This fix seems to have really slowed my phone down. It takes at least 2x as long to run stable on boot (i.e. stop lagging, load all background apps etc). I've imported my previous data.img over and will be trying the fix by Dom (above).
Edit2: And I'm now getting com.android.media force closes with the modded data.img! Music app won't work. Jesus!
ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Thanks for that Dom, I'll keep that in mind for next time! Great tip!
ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Same here ...?
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
Sent from my HD2 Jaws-MIUI
Did fix_permissions via the app ROM Manager and the Market force close still remains
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
rikardo1979 said:
Same here ...?
Sent from my HD2 Jaws-MIUI
Click to expand...
Click to collapse
Hmm, it seems that this script isn't inluded in your roms. But for you SMS92 it seems that it is another problem anyway.
If you wanna try sth. else see this:
http://all-google-android.com/google-android-forums/t-mobile-g1-modders/fix-permissions/
This is an "improved" fix permission tutorial which goes further than the command I posted above...quote from the link above: "fix_permissions is only intended for correcting ownership issues. It does not modify permissions, as is being requested."
In this post is a downloadlink for the advanced script so it doesnt matter if its already included in the rom...
@ricardo: see here if you still wanna try it: http://modmymobile.com/forums/567-motorola-backflip-general/556261-fix_permissions-script.html
Greetz Dom
johncmolyneux said:
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
Click to expand...
Click to collapse
It's a no-go I'm afraid.
So far the only thing that's worked is running the repairs on my 2gb data.img using e2fsck on my PC, but this in turn created a load more problems (com.process.media started force closing and the rom seemed to be much slower)
Will try some more suggestions tonight.
if your running gingerbread make sure the app is installed on the phone not the sd
I'm also suffering from this issue it started for me when an automatic update downloaded (which I didn't install) I will see if any of the above fixes work for me & if not I will start with a fresh copy of the ROM. Have to admit I have barely used winmo since I started using this build!
I have the same problem using froyo 2.2
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
robdee102 said:
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Any chance you could walk me through the steps you took for a fresh install? I am at my wits end with the FCs and a mount/partition error. Here is my setup:
HTC Hd2 Leo
HTC Desire
Android 2.2.1
Mod darkstone SuperRAM FroYo v1.5
Build FRG8
I am up for a new ROM or whatever to get my phone back in order. Thanks so much!
BOYPPC-SHIFTPDA v.37 Market Force Closes
BOYPPC-SHIFTPDA v.37 Market Force Closes
Please Help my Market is constantly force closing on me the error is:
Sorry!
The application Market
(process com.android.vending)
has stopped unexpectedly.
Please try again.
then it has a force close button.
I would really like to install some apps with the market but
every time I try and use the market I get this error,
I am running the BOYPPC-SHIFTPDA v.37 ROM
Please Help Me

[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