Related
Hey guys,
I think I accidentally deleted the people system APK?! I can no longer save contacts. Wondering what the best way to fix this issue would be without flashing back to stock rom. I am currently rooted and running stock 4.4.2 KK, but I have made a lot of MODS and am running the Galaxy Gear Manager for my watch which is a huge process to get running that I don't want to have to repeat.
Any help is mucho appreciated!!!
If you can find the apk somewhere install that. Otherwise flash the system.img from the factory image.
jd1639 said:
If you can find the apk somewhere install that. Otherwise flash the system.img from the factory image.
Click to expand...
Click to collapse
Will flashing the system.img reset everything?
jason.T said:
Will flashing the system.img reset everything?
Click to expand...
Click to collapse
No, it'll reinstall all the system files. If you modified any of them you'll lose that but I doubt you modified any. This will only work if your bootloader is unlocked. If it isn't then you'll lose everything unlocking it.
jd1639 said:
No, it'll reinstall all the system files. If you modified any of them you'll lose that but I doubt you modified any. This will only work if your bootloader is unlocked. If it isn't then you'll lose everything unlocking it.
Click to expand...
Click to collapse
Awesome, my bootloader is unlocked, thanks!
jason.T said:
Awesome, my bootloader is unlocked, thanks!
Click to expand...
Click to collapse
Have super su on your internal sd card so you can flash it in your recovery. You'll lose root.
jason.T said:
Hey guys,
I think I accidentally deleted the people system APK?! I can no longer save contacts. Wondering what the best way to fix this issue would be without flashing back to stock rom. I am currently rooted and running stock 4.4.2 KK, but I have made a lot of MODS and am running the Galaxy Gear Manager for my watch which is a huge process to get running that I don't want to have to repeat.
Any help is mucho appreciated!!!
Click to expand...
Click to collapse
Do you still need help with this? It's not that difficult to just pull the app and move it into the right system folder. Once you do that, change permissions to match the other apps, and reboot, you should be back to normal. I'll post the apk if you need it.
es0tericcha0s said:
Do you still need help with this? It's not that difficult to just pull the app and move it into the right system folder. Once you do that, change permissions to match the other apps, and reboot, you should be back to normal. I'll post the apk if you need it.
Click to expand...
Click to collapse
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Hi,
It's Contact.apk you would need?
jason.T said:
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Click to expand...
Click to collapse
No problem. I'll have it uploaded in a bit. It's just the People / Contacts apk, right? And you're odexed or deodexed?
jason.T said:
The APK would be amazing! I haven't been able to find it, I got the System.img that I was going to flash after work, but the APK would be a lot easier! Thanks!!
Click to expand...
Click to collapse
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
es0tericcha0s said:
No problem. I'll have it uploaded in a bit. It's just the People / Contacts apk, right? And you're odexed or deodexed?
Click to expand...
Click to collapse
Yes, the People/contacts apk, and I am still stock, just rooted and have an unlocked bootloader, so odexed, I believe.
jsgraphicart said:
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
Click to expand...
Click to collapse
I tried that with one of the apk's I found, but I couldn't get it to work. I may have gotten a corrupt file though.
Here's a flashable zip in attachment (wipe Dalvik cache just in case) for Contacts.apk (with the .odex file)...
You still have ContactsProvider.apk?
jsgraphicart said:
You can pretty much just download any ROM available, extract the Contacts.apk file (I think its in system/priv-app/) and put it on your device.
Click to expand...
Click to collapse
He might not be in a situation where he can download a large file like a complete rom. He did mention being at work. Anyway, these should work:
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.apk
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.odex
If you are deodexed, let me know, and don't use just the apk ^ there or it will force close constantly.
Just use a file manager that has root access (ES File Manager is a good, free choice, if you don't have another) and move the app and odex file to:
/system/priv-app
Make sure to change the permissions. The 3 Read options should be checked and the first Write option. If you aren't sure, just read the permissions of another app in that folder and match it. Then just reboot and should be back to normal.
viking37 said:
Here's a flashable zip in attachment (wipe Dalvik cache just in case) for Contacts.apk...
You still have ContactsProvider.apk?
Click to expand...
Click to collapse
Awesome!, thanks. The only thing I see in my app/system directory that pertains to contacts is the "GoogleContactsSyncAdapter.apk" I will be attempting to get this fixed when I get home in a couple hours.
jason.T said:
I tried that with one of the apk's I found, but I couldn't get it to work. I may have gotten a corrupt file though.
Click to expand...
Click to collapse
You need to change the permissions. If you didnt do that, then it wont work. es0tericcha0s explained it in his last post
jason.T said:
Awesome!, thanks. The only thing I see in my app/system directory that pertains to contacts is the "GoogleContactsSyncAdapter.apk" I will be attempting to get this fixed when I get home in a couple hours.
Click to expand...
Click to collapse
Re,
Contacts.apk and ContactsProvider.apk are in /system/priv-app...
You are odexed, right?
es0tericcha0s said:
He might not be in a situation where he can download a large file like a complete rom. He did mention being at work. Anyway, these should work:
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.apk
https://dl.dropboxusercontent.com/u/9903887/Apps/Contacts.odex
If you are deodexed, let me know, and don't use just the apk ^ there or it will force close constantly.
Just use a file manager that has root access (ES File Manager is a good, free choice, if you don't have another) and move the app and odex file to:
/system/priv-app
Make sure to change the permissions. The 3 Read options should be checked and the first Write option. If you aren't sure, just read the permissions of another app in that folder and match it. Then just reboot and should be back to normal.
Click to expand...
Click to collapse
Dropped those 2 files into the correct /system/priv-app, changed permissions, still nothing? What am I missing?
jason.T said:
Dropped those 2 files into the correct /system/priv-app, changed permissions, still nothing? What am I missing?
Click to expand...
Click to collapse
Dumb question, but did you reboot?
I pulled my 64 GB S6 Edge Sprint variant system folder via adb.
Would it be useful to developers to upload this somewhere for them to pull down?
Also does the system pull contain any files with sensitive/personal information specific to my phone? Usernames, passwords, pins, etc.
Kill3rmonk said:
I pulled my 64 GB S6 Edge Sprint variant system folder via adb.
Would it be useful to developers to upload this somewhere for them to pull down?
Also does the system pull contain any files with sensitive/personal information specific to my phone? Usernames, passwords, pins, etc.
Click to expand...
Click to collapse
I would like a copy of the stock recovery .img if you have it.
arlyn said:
I would like a copy of the stock recovery .img if you have it.
Click to expand...
Click to collapse
SAME.
I will try and throw that up somewhere tonight or tomorrow morning whenever I get a chance.
Well, if I can figure out how to do that. I am not currently rooted, I just did an adb pull system to get the sysdump. Not sure if not having root missed anything. (I assume maybe it did.)
bwcorvus said:
SAME.
Click to expand...
Click to collapse
I posted a copy here..
http://forum.xda-developers.com/showpost.php?p=60163751&postcount=8
http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?
NumberTwoinQQ said:
http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?
Click to expand...
Click to collapse
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.
Tulsadiver said:
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.
Click to expand...
Click to collapse
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
EDIT: I just changed these and it worked:
ro.config.dha_cached_max=12
ro.config.dha_empty_max=36
ro.config.dha_th_rate=2.3
ro.config.dha_lmk_scale=0.545
ro.config.sdha_apps_bg_max=70
ro.config.sdha_apps_bg_min=8
ro.config.oomminfree_high=7628,9768,11909,14515,16655,20469
NumberTwoinQQ said:
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
Click to expand...
Click to collapse
Most root explorers will show and allow permissions to be changed.
I actually edited mine via an app but I've done it through my root explorer text editor as well. Probably need to copy it off root drive. Edit it, then copy back. Some people say to copy it to the root folder first. Set permissions, them copy/move it to the system folder to overwrite it. Then, reboot.
I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.
musicfreak190 said:
I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.
Click to expand...
Click to collapse
According to the post, that line should have been inserted.
so i had quite an issue - my first go at it was done by copying build.prop via adb to my computer, editing and pushing back - after that, i nearly bricked the device. had to roll back to stock rom using odin .. not fun. now i decided to try again (cause i'm a masochist apparently) but i just edited the file using ES - no problems, no boot loops.. all is well for now - hopefully will see fewer apps closing for no reason. hooray.
i can say downloading the build prop that was posted here and replacing mine with it will brick a phone
I tried to modify the build.prop lines, I can save it successfully and I can see the build.prop content updated without problem. But after reboot my Mate 9, all my modifications were gone and restored to original. Are all those files under /system on Android N or Huawei require special tricks to modify? Because I also found that I am unable to add new file under /system directory, any new file created will be removed after reboot. Sorry for my dumb questions, I am new to Huawei and Android N... THANKS
Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app
Sammath said:
Doesn't editing the build.prop require root? Are you rooted?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.
raychak said:
Yes, my Mate 9 is rooted. The build.prop can be modified and saved before reboot, I can see all changed by reading the file. But the file will be replaced with original unmodified one after reboot... I also tried to modify an XML file under /system/emui/base/xml/ with same problem.
Click to expand...
Click to collapse
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.
duraaraa said:
You can't make any changes to the system partition directly... This is why we need to root with a systemless root procedure. It is also the reason why adaway and other things that modify system don't work.
One way around it is to unpack the system partition, modify it, and repack and then flash it. Big pain to do that though so I have not tried myself. Also OTA updates would no longer work right.
Click to expand...
Click to collapse
so , without changing build.props how can you rebrand to others region FW?
OnimushaPooh said:
so , without changing build.props how can you rebrand to others region FW?
Click to expand...
Click to collapse
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.
duraaraa said:
You have to modify the oeminfo, and then repartition (partitions layouts vary between regions) and flash the firmware with eRecovery. FunkyHuawei can handle the repartition and the flashing with eRecovery.
Click to expand...
Click to collapse
cool thanks, it quite complicate things, not simple as others huawei's phone.
OnimushaPooh said:
cool thanks, it quite complicate things, not simple as others huawei's phone.
Click to expand...
Click to collapse
They changed a lot when they went to Android N, unfortunately.
The real build.prop is under vendor, not system. Just for information.
So since this device was a samsung device, i thought AOD was a sure thing. But ofc samsung like to remove nice things and its not included with this phone. But i am rooted with magisk and would love to see a port for this! I know its possible since theres a few devices that has this with either magisk or modded apk
There are some third party Always on Displays which you can find on the Play Store.
I'm not sure whether you can find the exact one which Samsung is using. I can send you the original application file but I don't think it will work.
dedq said:
There are some third party Always on Displays which you can find on the Play Store.
I'm not sure whether you can find the exact one which Samsung is using. I can send you the original application file but I don't think it will work.
Click to expand...
Click to collapse
I can try that and install through adb can you send the folder from system/apps and system/priv-app if Theres folders in Both
Let us see what we can do since I'm unable to find the other folder. I will send you the application file and what I've found:
Quick Share
Expired
linksharing.samsungcloud.com
Quick Share
Expired
linksharing.samsungcloud.com
dedq said:
Let us see what we can do since I'm unable to find the other folder. I will send you the application file and what I've found:
Quick Share
Expired
linksharing.samsungcloud.com
Quick Share
Expired
linksharing.samsungcloud.com
Click to expand...
Click to collapse
And where are they placed?
mikkis2k said:
And where are they placed?
Click to expand...
Click to collapse
I think they are the same. They are under: "priv-app" in root directory. I suggest you give application file a try by installing it casually.
Ive tried every possible option so far with no luck! Tried manually place in system/priv-app, install apk, edit build.prop etc.. we need this feature! Aynone thats any good with this?