Hi All,
I've been looking for the install location where MarketPlace installs apps?
Can someone help?
I can not find any apps I have installed in:
/system/app
/data
I have rooted my X10
Please help if you can
/data/app
/data/app-private
Well this may be "odd"..
In both of those locations.. They're empty.
I have installed about 12 marketplace apps.
Is this normal? :S
You're sure you're rooted then?
Code:
# cd /data/app
cd /data/app
# ls -l
ls -l
-rw-r--r-- system system 637063 2010-06-28 22:14 stericson.busybox.apk
-rw-r--r-- system system 4201344 2010-06-28 22:14 com.google.android.apps.maps.apk
-rw-r--r-- system system 823161 2010-06-28 22:14 com.dropbox.android.apk
...
I have root.
I am actually redoing all root steps again.
Is there a GUI file explorer that will let me see what is in /data/apps?
The basic one's show nothing.
..obviously you need a file explorer capable of escalating to root privileges first...
Using root explorer I see my /cache directory contains a lot of .apk files (like "Downloadfile-x.apk where x is from 1 to 12) and some .jpg (corr.) files.
What kind of reposotory is it? Can I remove theese files? Is it safe?
after a backup I removed all files.
No problem
Original question post below...
IF YOU DO NOT HAVE THIS PROBLEM PLEASE BACKUP YOUR /EFS NOW!!! this will save you pain in the future.
One of the things I see over and over in the DEV forum for different ROM's is I flashed this ROM and I do not have any cell service. This seemed common enough that I wanted to put what I found in one place. I am not an expert on this and I will credit the posts and users that helped me. I am actually looking for help in creating a fool proof way to fix a broken /efs, product code (Vibrant is SGH-T959ZKBT), and IMEI.
It seems that the issue here is a corrupt /efs partition/folder (/dev/block/spl3)
You can check this a couple ways first look at your /efs folder in Root Explorer (show hidden files) or via "adb shell ls -a -l /efs". As many of you know this is where you find the nv_data.bin file used for unlocking and stores your product code (needed to be accurate for Kies to work). It is also where the phone stores your IMEI. My good /efs looks like this:
Code:
adb shell ls -a -l /efs
drwxrwxrwx root root 2009-12-31 23:00 .android
-rwx------ radio radio 2097152 2011-05-30 00:44 nv_data.bin
-rw-rw-rw- radio radio 15 2011-05-28 17:46 .imei
drwxrwxrwx radio radio 2010-09-12 03:29 imei
-rwx------ radio radio 2097152 2011-05-07 18:24 .nv_data.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv_data.bak.md5
-rwx------ radio radio 32 2011-05-30 00:44 nv_data.bin.md5
-rw-rw-rw- radio radio 801 2011-05-07 18:24 nv.log
-rw-rw-rw- radio radio 1 2011-05-07 18:24 .nv_state
-rwx------ radio radio 1048576 2011-05-07 18:24 .nv2.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv2.bak.md5
The .imei file holds your IMEI in hex format.
You can also check your IMEI by pressing *#06#. You should check that against your IMEI printed on the back of your phone under the battery.
To get your radio working again with correct IMEI you will need a good backup of your /efs folder or partition. You may have a backup and not know it, some ROM porters have added a script to backup your /efs to /sdcard/backup/efs you should look for it. If you are not lucky enough to have one then find a ROM where you see the generic IMEI number (004999010640000) when you press *#06# in the dialer. I used an old Galaxy S 4G port by Eugene373 (he has removed it) to get the generic IMEI.
There are disadvantages to using the generic IMEI as some services will not work (i.e. security on corporate email)
Now that all that is out of the way let's get to the steps for getting you cell service back:
STANDARD DISCLAIMER APPLIES!!! I cannot be responsible for bad things that could happen playing with your /efs folder/partition
Create a copy of your current /efs partition (/dev/block/stl3) with this command: (Thanks Candanga http://forum.xda-developers.com/showthread.php?t=859914)
Code:
# busybox cat /dev/block/stl3 > /sdcard/efs-stl3-backup.img
Mount this file to another location like /testefs:
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Copy all the files from your backup into /testefs and overwrite them
Set all the files and directories (except .android should be root) to the owner and group radio:
Code:
# busybox chown 1001:1001 nv_data.bin
# busybox chown 1001:1001 .imei
# busybox chown -R 1001:1001 imei
# busybox chown 1001:1001 .nv_data.bak
# busybox chown 1001:1001 .nv_data.bak.md5
# busybox chown 1001:1001 nv_data.bin.md5
# busybox chown 1001:1001 nv.log
# busybox chown 1001:1001 .nv_state
# busybox chown 1001:1001 .nv2.bak
# busybox chown 1001:1001 .nv2.bak.md5
Set the file permissions as follows:
Code:
# busybox chmod 700 nv_data.bin
# busybox chmod 666 .imei
# busybox chmod 700 .nv_data.bak
# busybox chmod 700 .nv_data.bak.md5
# busybox chmod 700 nv_data.bin.md5
# busybox chmod 666 nv.log
# busybox chmod 666 .nv_state
# busybox chmod 700 .nv2.bak
# busybox chmod 700 .nv2.bak.md5
Unmount /testefs
Code:
# busybox umount /testefs
Now your /sdcard/efs-stl3-backup.img should be all fixed. If you have the generic IMEI you can try editing the .imei file with a hex editor of your choice and change it to your IMEI it is just the hex representation of your IMEI and nothing else in the file. (I did not test this as I had the files backed up.
Next we are going to create an odin tar to flash to the phone: (Thanks cellgeek http://forum.xda-developers.com/showpost.php?p=10622481&postcount=12)
Code:
# cd /sdcard/
# busybox cat efs-stl3-backup.img > /sdcard/efs.rfs (this is the key step!!)
# tar -cf efs.tar efs.rfs
# exit
Now your back at your PC. Do the following step to get the .tar file off your phone.
Code:
c:\Android\tools> adb pull /sdcard/efs.tar
This tar file can be put in the PDA section of Odin and flashed in download mode.
If all worked you should not have a repaired /efs that should work on most/all ROMs.
What I did not cover here was how to fix the Product code but this post from bames explains how to do that for a Captivate and should work the same for our Vibrants. Difference is our Product Code is SGH-T959ZKBT and you may need to be on Stock JI6 to do the steps in the post.
http://forum.xda-developers.com/showthread.php?t=881162
I hope this helps some and feel free to let me know if I missed something or if it does not work or if there are easier ways.
Original Question:
philow said:
I have been flashing ROMs on my Vibrant for a while and all has worked OK. I never really bothered to look at my IMEI number but I am sure somewhere along the line it changed and probably my Product Code. I just decided to go back to stock and clean up the phone a bit before I continue now that CM7 is officially supported
I Odin back to JFD with the 512.pit and partition. After the reboot the phone will only stay on for a short time then reboot or turn off and I have no signal.
I then Odin to JI6 w/o repartitioning and it will boot and is stable. I root the phone then I look in the /efs folder and all that is there is a .android folder. I have no signal at this point. I can copy a backup of my /efs or just mount as r/w with root explorer and I will get the nv_data files that I need and get signal. If I copy my backup first then I will also have the correct IMEI for my phone. If I do not restore from my backup my IMEI is null/null.
My problem is that if I reboot my phone I again have no files in /efs just the .android folder.
I have tried to change permissions and ownership on the files to radio (1001) but no matter what I do the files disappear.
Anyone else having this problem? Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
what rom did you came from?
Sent from my SGH-T959 using XDA App
iynfynity said:
what rom did you came from?
Click to expand...
Click to collapse
It was my Son's phone so I am not sure what all he has had on it or when it started having a problem but the latest was the 5/7/2011 MIUI rom.
MIUI worked fine on reboot as far as signal is concerned. Not sure what IMEI it had.
Thnaks
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Sent from my SGH-T959 using XDA App
iynfynity said:
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Click to expand...
Click to collapse
I have tried that post and this one from the Captivate forum.
http://forum.xda-developers.com/showthread.php?t=881162
And it still deletes the files when I reboot. I have actually contacted Tmobile and they have sent a new phone but I am trying to see what has happened in case it happens again.
Also, I just flashed an old GalaxyS4G ROM my son had on it and it seems to work OK as well but with a generic IMEI and the 4G Product code.
strange!!!
Thanks for your quick reply
Added possible Solve
I added what I did to solve my issue in the OP! Hope it helps someone!
Thanks
No EFS backup and EFS got currupted| How to recover Vibrant
philow said:
Original question post below...
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Original Question:
Click to expand...
Click to collapse
How to repair IMEI and get back signal If you dont have efs back up or NV_data.bin backup?
I am in big trouble.
Flash to stock using ODIN and it should be fixed, check your IMEI with the one in the back of your phone.
The easiest way to do it is using this http://forum.xda-developers.com/showthread.php?t=954509, as it comes with the pit and pda files you need. (Many thanks to bay_wofl)
how if I don't have the stl3, in fact my /dev/block is empty !!!
do I still have chance to restore my phone with only the efs backup ?
NO Signal ** no /efs folder
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
serginhog said:
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
Click to expand...
Click to collapse
Did you find a solution? I just received my goophone i5 and have no service
You almost made me cry !!! Followed about 90% of all the guides to restore my backed up efs. Went from no signal to bootloop and back. Spend 6 days trying to fix my phone and you were my last resort. If your guide wouldn't work I would've given up. I did push the Thanks button but wanted to say thank you too
Got a used alpha sm-g850y. It seems that knox counter is already tripped to 1. However the phone is not rooted (seems like bugger flashed stock rom before selling) and Iam having following issues
1. WiFi passwords are lost after reboot (Unsecure WiFi is still saved after reboot)
2. Bluetooth takes a long time to start file send (though file receive is fast)
3. Sometimes the battery drain is rapid
In logcat I can see following message is printed every 1 or 2 secs
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon sent config to TA/driver
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)system error
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)=============================================================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)It is failed to write a file to /efs partition.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)Please check
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(1) if there is a valid /efs partition, and
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)(2) if /efs directory has the correct permission.
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)=============================================================
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
E/SecureStorage( 4914): [ERROR]:SPID(0x00000000)
W/SecureStorage( 4914): [WARN]: SPID(0x00000000)Error sending config file to TA/driver!
I/SecureStorage( 4914): [INFO]: SPID(0x00000000)Secure Storage Daemon stopped
Click to expand...
Click to collapse
I verified the /efs directory is present and it has ownership radio:system. Iam not able to see contents of directory though.
What is the solution to this problem?
Iam thinking of flashing it with stock rom. Will it work? or it may corrupt /efs altogether?
Or should I root and change ownership/permissions of /efs? If so what is the right ownership/permission?
Also what is best way to root without flashing custom rom?
Thanks
vsevani said:
Got a used alpha sm-g850y. It seems that knox counter is already tripped to 1. However the phone is not rooted (seems like bugger flashed stock rom before selling) and Iam having following issues
1. WiFi passwords are lost after reboot (Unsecure WiFi is still saved after reboot)
2. Bluetooth takes a long time to start file send (though file receive is fast)
3. Sometimes the battery drain is rapid
In logcat I can see following message is printed every 1 or 2 secs
I verified the /efs directory is present and it has ownership radio:system. Iam not able to see contents of directory though.
What is the solution to this problem?
Iam thinking of flashing it with stock rom. Will it work? or it may corrupt /efs altogether?
Or should I root and change ownership/permissions of /efs? If so what is the right ownership/permission?
Also what is best way to root without flashing custom rom?
Thanks
Click to expand...
Click to collapse
Ok rooted the device. Observed that file /efs/ss_data had ownership root:root. Changed the ownership to system:system. WiFi now stores password even after reboot. I saw several other files had ownership as root:root as well. Changed the ownership/permissions of the files as follows
-rw-rw-r-- radio system 152 2013-04-21 04:44 00000000.authtokcont
drwxrwxr-x system system 2015-11-28 00:31 FactoryApp
drwxrwx--- radio system 2015-11-28 00:30 TEE
drwxrwxr-x radio system 2014-01-01 18:05 bluetooth
drwxr-xr-x root root 2013-01-01 05:32 carrier
drwxrwx--x radio system 2015-11-30 13:15 cpk
drwxrwxr-- drm system 2014-01-01 17:55 drm
-rw------- system system 0 2015-02-02 16:28 fm_data
-rw-r--r-- system system 12 2013-04-21 04:39 gyro_cal_data
-rw-r--r-- radio radio 1100 2013-01-01 05:32 h2k.dat
drwxr-xr-x radio system 2013-04-21 04:44 imei
drwx------ root root 1970-01-01 05:30 lost+found
drwxrwx--- radio system 2015-11-28 00:30 mc
-rw-r--r-- radio radio 4352 2014-01-01 18:05 nv.log
-rwx------ radio radio 1048576 2015-12-11 12:30 nv_data.bin
-rw-r--r-- radio radio 32 2015-12-11 12:30 nv_data.bin.md5
drwxrwx--- radio system 2014-01-01 18:42 prov
drwxrwx--- radio system 2014-01-01 18:43 prov_data
drwxrwx--x radio system 2015-11-30 13:15 recovery
-rw-r--r-- radio radio 880 2015-12-10 23:00 redata.bin
drwxrwxr-x radio system 2015-11-28 00:30 sec_efs
-rw-rw---- system system 124 2015-12-10 22:12 ss_data
drwxrwxr-x radio system 2012-01-01 05:30 wifi
-rw------- radio radio 220 2014-01-01 18:05 wv.keys
Click to expand...
Click to collapse
Can someone with rooted alpha please confirm if the permissions are correct?
Iam still getting following two errors in logcat
This error is coming every 1-2 secs
E/SMD (18841): smd Interface open failed errno is 2 -1
Click to expand...
Click to collapse
E/Sensors ( 3119): HAL: Correct Accel Invalid timestamp - 9558595634159, old_timestamp=9558970037452
Click to expand...
Click to collapse
Any idea what these errors are? And their solution?
Thanks
Hello.
I recently switched from a Galaxy S2 running CM 10.2 (Android 4.3.1) to a Nexus 5 running 6.0.1 (stock rooted).
My goal was to migrate all my WhatsApp data (history, media, etc.) over to the new device. Restoring the history was no problem using WhatsApp's builtin backup/restore functionality.
I then proceeded to copy all the .../WhatsApp/Media/ folders over to the new phone, however, I still got an error message stating that the file could not be found when trying to open any (old) received images or videos from within WhatsApp.
Upon further investigation, it seems like WhatsApp is (or was?) storing the absolute path to every individual media file in its database, e.g. on my S2: /storage/sdcard0/WhatsApp/Media/WhatsApp Images/IMG-20140813-WA0020.jpg
It just so happens that the /storage/sdcard0 symlink doesn't exist on my Nexus 5 and hence WhatsApp can't access older files since the links are broken.
So I figured all I needed to do was create the /storage/sdcard0 symlink, like this:
Code:
ln -s /sdcard /storage/sdcard0
Code:
[email protected]:/ # ls -l /storage
drwx--x--x root sdcard_rw 1970-07-07 17:59 emulated
lrwxrwxrwx root root 2015-12-30 16:26 sdcard0 -> /sdcard
drwxr-xr-x root root 1970-07-09 08:57 self
Unfortunately, WhatsApp still couldn't access my old media files (not to mention that the symlink was gone after a reboot).
What am I doing wrong?
Thanks!
Bump.
Bump.
Bump.
Bump.
Bump.
Bump.
Bump.
kveikur said:
Bump.
Click to expand...
Click to collapse
Make sure whatsapp has storage permissions?
Also try to symlink directly where /sdcard goes, not symlink to another symlink