Develop Bugs

% battery - stock everything else

*I made this before any of these new roms came out and as such it was meant for and has been tested on only the stock Gingerbread rom that comes with the phone. I doubt it will be compatible with the new roms.*
*Typical disclaimer - short version - I'm not a dev, just a tinkerer, blah blah blah, use at your own risk, blah blah blah, god speed =)*
As requested, here's the framework-res.apk that changes nothing but adds the percent battery value to the stock battery icon. Everything else will look the same with the exception of the numbers on the battery, as such:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you haven't swapped framework-res.apk or SystemUI.apk, please read one of my previous posts for instructions, such as:
Blue icons and removed carrier logo
You CAN very easily brick your phone if you do this incorrectly (ESPECIALLY if you use a file explorer other than root explorer)! So please ask if you're not sure about something.
Just as a refresher,
Basic instructions -
1.) download/unzip on computer
2.) copy framework-res.apk to /sysem/ folder on phone (USE ROOT EXPLORER!)
3.) change permissions to owner: read write, group: read, others: read
4.) move framework-res.apk to /system/framework folder
5.) restart phone
Any other modifications you've made to framework-res.apk will have to be reinstated afterwards.
Hope you enjoy!

Ok first of all big thanks for this. However, I'm new to Android and it's a bit over my head. I'm going to have to check out your other thread I think.

Oh, sorry! Basically, you need root explorer from the market. I know it costs something like 3 bucks, but in my opinion, it's totally worth it if you do any mods on the phone at all. Messing with framework-res.apk with other file explorers can spell disaster. Root explorer is the only one I really trust.
1.) Using root explorer, COPY your framework-res.apk file at /system/framework/framework-res.apk to somewhere on your sd card for safekeeping, just as a backup.
2.) Move framework-res.apk from this thread's "stock icons - percent battery.zip" onto your sd card, and move it into /system folder on your phone.
3.) Long-press on this framework-res.apk in root explorer, and select permissions. Change permissions to: Owner: read/write, group: read, others: read.
4.) Move this framework-res.apk, now with the proper permissions, into /system/framework folder, and let it overwrite the original framework-res.apk.
5.) Restart your phone!

Oh, Root Browser works great for me and best of all it's free!

Have you used it specifically to replace framework-res.apk before? If it works for that, great! But if you haven't tried that already, be aware how the file explorer specifically handles framework-res.apk is the difference between the phone being fine or getting bricked. With root explorer, when you replace framework-res.apk, it prevents the phone from accessing the file while copying, and only actually swaps at reboot. With other file explorers like ES File Explorer, even with root permissions and all the same functionality of root explorer, when you swap framework-res.apk, the phone continues to try to read off the framework-res.apk as it is being overwritten, causing the phone to crash and an endless bootloop/brick. (I know because I tried to find a free alternative to root explorer and ended up with a brick =P) If Root Browser works for this, that's fantastic! But be careful! Unless you've already swapped framework-res.apk using this and it worked beautifully, be very very very cautious!!

Yep! I guess I lucked out when I went into it without really knowing what I was doing.

Haha, awesome! Great! There's a free alternative then! =) So percent worked okay with you?

I just bought the Root Explorer. I'm assuming it needs to say "Mounted as R/W". Otherwise it's in read only mode?

Yup! RW mode needed

itiskonrad said:
Haha, awesome! Great! There's a free alternative then! =) So percent worked okay with you?
Click to expand...
Click to collapse
Yeah everything looks great! Thanks.

Awesome! You're welcome!

bricked T_T
man... not sure what i did wrong but i used root explorer. now my p930 is in an endless bootloop.
what did you do to fix yours?
itiskonrad said:
Have you used it specifically to replace framework-res.apk before? If it works for that, great! But if you haven't tried that already, be aware how the file explorer specifically handles framework-res.apk is the difference between the phone being fine or getting bricked. With root explorer, when you replace framework-res.apk, it prevents the phone from accessing the file while copying, and only actually swaps at reboot. With other file explorers like ES File Explorer, even with root permissions and all the same functionality of root explorer, when you swap framework-res.apk, the phone continues to try to read off the framework-res.apk as it is being overwritten, causing the phone to crash and an endless bootloop/brick. (I know because I tried to find a free alternative to root explorer and ended up with a brick =P) If Root Browser works for this, that's fantastic! But be careful! Unless you've already swapped framework-res.apk using this and it worked beautifully, be very very very cautious!!
Click to expand...
Click to collapse

File Expert
Has anyone tried useing File Expert? I really cant see buying the root explorer for one time use... I have been using File Expert for a while but never got into the aformentioned files...

mdkrush said:
Has anyone tried useing File Expert? I really cant see buying the root explorer for one time use... I have been using File Expert for a while but never got into the aformentioned files...
Click to expand...
Click to collapse
I use root browser. Its free and worked for me.

daebaybay said:
man... not sure what i did wrong but i used root explorer. now my p930 is in an endless bootloop.
what did you do to fix yours?
Click to expand...
Click to collapse
I took mine back to the AT&T store =/ I was still within 30 days after purchasing.
You can follow the unbrick solution in this thread here
That sucks, dude! Any clue what happened? After copying framework-res.apk into /system/ but before putting it into /system/framework, did you change the permissions to owner: read write, group: read, others: read? Or did you use a file manager other than file explorer? Sorry, man! =(

heh, i did everything here with the root explorer so not sure what caused the bricking.
mine stopped doing the bootlooping but it force closes everything.
i wonder if it can be recoverable in this state without flashing.
maybe i can just sign up for the beta testing of the new dev roms since it's already bricked lol.
if you have any suggestions to what i can try, let me know
Forgot to mention, my unit is the bell optimus lte. Not sure if that is the difference.
itiskonrad said:
1.) Using root explorer, COPY your framework-res.apk file at /system/framework/framework-res.apk to somewhere on your sd card for safekeeping, just as a backup.
2.) Move framework-res.apk from this thread's "stock icons - percent battery.zip" onto your sd card, and move it into /system folder on your phone.
3.) Long-press on this framework-res.apk in root explorer, and select permissions. Change permissions to: Owner: read/write, group: read, others: read.
4.) Move this framework-res.apk, now with the proper permissions, into /system/framework folder, and let it overwrite the original framework-res.apk.
5.) Restart your phone!
Click to expand...
Click to collapse

thanks for the contribution! is it ok to do this change on the kernalpan1c custom ROm? it has been deodexed , i am unsure if that matters and wanted to double-check.
ty

Ohhh, I don't know. I tend to doubt it will work with a custom ROM... My gut says no

drat!
thx for the reply.

[How-to] Disable OTA updates on Stock + Rooted ROMs

I see this question come up once in a while here, and I had a similar thread on the ET4G about this so I thought I'd recreate it here for you S3 folks. I recently flashed to LJ7 to do some testing and while there was getting bugged by the OTA update, so I tried this method out and confirmed it does work on the S3 as well.
[How-to] Disable OTA updates on Stock + Rooted ROMs
1. Download FOTAKill.apk* and copy to your Phone/SD
2. Use a root explorer (such as ES Explorer) to copy the file to /system/app
3. If the update already downloaded, use your root explorer to delete it from /cache
4. reboot
If the update notice is still in the notification bar after the reboot, simply swipe it away. That should be the last time you are ever prompted to update via OTA. Even if you manually go to system update and click check now it will no longer offer you the OTA. You can simply delete the apk from /system/app to reverse this mod.
*Credit for the apk goes to the CM team and or the folks who create the gapps packages!
*If anyone would like to make a CWM flashable I would be happy to add it here and give you credit.

rocket321 said:
I see this question come up once in a while here, and I had a similar thread on the ET4G about this so I thought I'd recreate it here for you S3 folks. I recently flashed to LJ7 to do some testing and while there was getting bugged by the OTA update, so I tried this method out and confirmed it does work on the S3 as well.
[How-to] Disable OTA updates on Stock + Rooted ROMs
1. Download FOTAKill.apk* and copy to your Phone/SD
2. Use a root explorer (such as ES Explorer) to copy the file to /system/app
3. If the update already downloaded, use your root explorer to delete it from /cache
4. reboot
If the update notice is still in the notification bar after the reboot, simply swipe it away. That should be the last time you are ever prompted to update via OTA. Even if you manually go to system update and click check now it will no longer offer you the OTA. You can simply delete the apk from /system/app to reverse this mod.
*Credit for the apk goes to the CM team and or the folks who create the gapps packages!
*If anyone would like to make a CWM flashable I would be happy to add it here and give you credit.
Click to expand...
Click to collapse
CNexus created a really good sticky guide to talk about OTAs. You might want to post this over there. Could you let us know what FOTAKill does? Does it work regardless of phone/carrier?

topherk said:
CNexus created a really good sticky guide to talk about OTAs. You might want to post this over there. Could you let us know what FOTAKill does? Does it work regardless of phone/carrier?
Click to expand...
Click to collapse
I expect it will work on other carriers/phones but only speak for devices I personally test it on.
The apk works by overriding the built in android OTA service. It has traditionally been included in Gapps packages as a way to disable carrier updates on AOSP roms but works just as well on stock based roms.
Sent from my SPH-L710 using xda app-developers app

I must be doing something wrong. I am unable to move the file, I keep getting "file is read only"
Update: I found that if you click on the downloaded apk that it installs itself in the correct folder however it still did not work for me.
I am on the DaRTHSTAULKER ROM S3 vX
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

EVObastard said:
I must be doing something wrong. I am unable to move the file, I keep getting "file is read only"
Update: I found that if you click on the downloaded apk that it installs itself in the correct folder however it still did not work for me.
I am on the DaRTHSTAULKER ROM S3 vX
View attachment 1914304
Click to expand...
Click to collapse
You need to mount /system as RW
If your file manager does not give you the option to do so, go into a terminal and type the following:
Code:
mount -o remount,rw /system
The app needs to installed as a system app, if you simply install it by selecting it, it will be installed as a user app. Uninstall, mount system as ready write, and copy it to /system/app

That's correct, if you just click it and install like a normal app it won't work because it needs to be installed as a system app.
Sent from my SPH-L710 using xda app-developers app

So do I move the hole file or extract the app then move that?
NM I noticed it's a .apk file :fingers-crossed:
Ok, that worked it's now in my app list, thank you hopefully this does it.
Sprint GS3 Rooted, DaRTHSTAULKER X

Woohoo, it's been 4 hours or so and no notification, thank you thank you thank you.
Sprint GS3 Rooted, DaRTHSTAULKER X

Ok so I took a look inside the apk and heres how it works
App gets triggered when: Google Services state is changed; Android device checks in the the Google servers; and when Android device finishes booting (BOOT_COMPLETE)
If there is, it gets the info from the Google Services Framework intent (url, time, etc), logs it, and then cancels the notification
Sets the link to be empty (" ") and overrides the GSF notification, and then clears the notification
Removes the notification and OTA data from the Google Services Framework database
Attached is a universal flashable (meaning, for any Android device) that puts FOTAKill.apk into your /system/app.
EDIT: File pulled for the moment...

CNexus said:
Ok so I took a look inside the apk and heres how it works
App gets triggered when: Google Services state is changed; Android device checks in the the Google servers; and when Android device finishes booting (BOOT_COMPLETE)
If there is, it gets the info from the Google Services Framework intent (url, time, etc), logs it, and then cancels the notification
Sets the link to be empty (" ") and overrides the GSF notification, and then clears the notification
Removes the notification and OTA data from the Google Services Framework database
Attached is a universal flashable (meaning, for any Android device) that puts FOTAKill.apk into your /system/app.
EDIT: File pulled for the moment...
Click to expand...
Click to collapse
This is great, I am standing by. Since I did it the other way should I redo it this way? (I would guess no) Also I was going to ask if it worked for my wife's E4GT but sounds like this new one you are making will. TIA

EVObastard said:
This is great, I am standing by. Since I did it the other way should I redo it this way? (I would guess no) Also I was going to ask if it worked for my wife's E4GT but sounds like this new one you are making will. TIA
Click to expand...
Click to collapse
The file itself will work on ANY phone because it blocks the GSF app. I would recommend just using a root browser to put it in /system/app for the moment, i pulled the file because it somehow wiped my entire /system partition (yeah, i dont know either) so i didnt want anyone else to have issues.
And no, you dont need to redo it with the zip im making, it wont change anything.
Also, im not modifying the file in any way, I'm just making a zip that will flash it on any device.

This definitely works on the ET4G, I had that phone before the S3 and used it to stay on a GB rom for a long time.
Sent from my SPH-L710 using xda app-developers app

Thank you both very much. :good::good:

Here's a flashable http://db.tt/lfeO3giy fix permissions after flashing just in case
Sent from my ANTHRAX sniffing GS3

Disabling OTA updates
Hi,
Would anyone know if the FOTAKill.apk procedure works on a Galaxy S3 flashed to Boost or would that not make a difference?
Thanks.

andee39 said:
Hi,
Would anyone know if the FOTAKill.apk procedure works on a Galaxy S3 flashed to Boost or would that not make a difference?
Thanks.
Click to expand...
Click to collapse
Try it. Shouldn't hurt anything if it doesn't.

Thanks. A friend had mentioned to me he read about freezing SDM 1.0 but I don't have that file and wasn't sure if it was related to being flashed to Boost. I searched and came across your post but wasn't sure if I would run into a similar type issue. Will give it a try and fingers crossed it works!
Thanks again!

Fota will not paste into Apps folder
Every time I try to copy or cut and paste the file never goes into the apps folder. My phone is rooted using Mr. Robinsons method.I have tried two different root explorers witht he same results.

maf49 said:
Every time I try to copy or cut and paste the file never goes into the apps folder. My phone is rooted using Mr. Robinsons method.I have tried two different root explorers witht he same results.
Click to expand...
Click to collapse
Have you changed the read/write settings in the root explorer apps? They default to read only in order to edit you have to change to write.
Sent from the future via Tapatalk 4

edfunkycold said:
Have you changed the read/write settings in the root explorer apps? They default to read only in order to edit you have to change to write.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
System folder and app folder both have owner rwx group rx and other rx. there is a checkbox to add w but it wont keep the setting

Cant see old files after flashing to 4.3 after 4.1

Im sure this has come up a few times but I cannot find the answer...I went from 4.1.2 mc2 to 4.3 and everything is running smooth as butter, but my files such as music and even the newest rom zip is still on my internal storage taking up so much space but I cannot see them through es file explorer or through my pc to delete them and free up space. When I flashed, I wiped cache, dalvic, factory reset then formatted system data and cache in that order, 3 times each and that's how ive always done it. I restored my backup of 4.1.2 (which after the fact I read that's the ultimate no no) but all files are there and the phone worked like it always had. I did flash 4.3 again and im still running it with no issues but I can't figure out how to see my old files from 4.1.2...any insight on this would be greatly appreciated!!! GO BRONCOS!!!

blacksmith_84 said:
Im sure this has come up a few times but I cannot find the answer...I went from 4.1.2 mc2 to 4.3 and everything is running smooth as butter, but my files such as music and even the newest rom zip is still on my internal storage taking up so much space but I cannot see them through es file explorer or through my pc to delete them and free up space. When I flashed, I wiped cache, dalvic, factory reset then formatted system data and cache in that order, 3 times each and that's how ive always done it. I restored my backup of 4.1.2 (which after the fact I read that's the ultimate no no) but all files are there and the phone worked like it always had. I did flash 4.3 again and im still running it with no issues but I can't figure out how to see my old files from 4.1.2...any insight on this would be greatly appreciated!!! GO BRONCOS!!!
Click to expand...
Click to collapse
Your older files from 4.1.2 are stored in the /data/media folder. Newer Android versions now store internal data on /data/media/0. Use a file explorer with root permission features like Root Explorer to find and copy those files.

d3cypher said:
Your older files from 4.1.2 are stored in the /data/media folder. Newer Android versions now store internal data on /data/media/0. Use a file explorer with root permission features like Root Explorer to find and copy those files.
Click to expand...
Click to collapse
Thanks man! Does root explorer dig deeper for files/folders? I have es file explorer but the only data folder I see is empty and I used the search in es file explorer for media but all thats in there are these in the screen shot. Im baffled!! I greatly appreciate your help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I tried out ES file explorer and I couldn't get it to recognize the folder. I do not think it offers the full features that root explorer dose.
Sent from my SPH-L900 using Tapatalk HD

blacksmith_84 said:
Thanks man! Does root explorer dig deeper for files/folders? I have es file explorer but the only data folder I see is empty and I used the search in es file explorer for media but all thats in there are these in the screen shot. Im baffled!! I greatly appreciate your help!
Click to expand...
Click to collapse
Press your menu key while in es file explorer on left side of screen click on tools scroll down to the root option and turn it on approve root then a new screen will pop up select mount read write on all options now you can see everything but hidden.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Press your menu key while in es file explorer on left side of screen click on tools scroll down to the root option and turn it on approve root then a new screen will pop up select mount read write on all options now you can see everything but hidden.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That did it, thank you guys for your all of your help!!! jlmancuso, you saved my sanity my friend I GREATLY appreciate you man!!! I bet this will help out my fellow noobs too lol!!Have a great day everyone!

[Fix][ND8] TW KitKat external sd write permission fix

I was getting pretty frustrated with how KitKat handles the ext sdcard permissions. After doing a search I came to THIS post by poit and it worked great. So I thought I would make a flashable for folks. All this will do is replace the system/etc/permissions/platform.xml with the only change detailed below.
*Note: I've only tested this on my device running Stock rooted obtained by flashing the [FULL RESTORE][TAR] Stock ND8 4.4.2 with Odin found HERE.
Just flash in recovery.
Down Load HERE
These are the instructions in case you would rather do this yourself.
Instructions:
1- Using a root-enabled file manager, navigate to /system/etc/permissions
2- Edit platform.xml
3- Find the following code:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r"/>
<group gid="sdcard_rw"/>
</permission>
4- Add "<group gid="media_rw" />" so that the code looks like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r"/>
<group gid="sdcard_rw"/>
<group gid="media_rw"/>
</permission>
5- save and restart
-----------------------------------------------------------
Here is a good article detailing what we're dealing with and why.
http://m.androidcentral.com/kitkat-sdcard-changes
-----------------------------------------------------------
Disclaimer: Flash/use at your own risk!
*It is important to note that there may be additional issues I don't know about and as I am a truck driver, not a programmer I may or may not be able to fix things.
Everyone is encouraged to do what ever you like with anything I post, but a little credit would be appreciated.

Nice, good work Chad
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

For some reason the instructions I posted are wonky and I'm unable to edit it. (Weird) so for now I'll just post this pick of the instructions until I can fix it properly.
Edit: got it fixed. I hope it's easy to understand.

Chad The Pathfinder said:
For some reason the instructions I posted are wonky and I'm unable to edit it. (Weird) so for now I'll just post this pick of the instructions until I can fix it properly.
Click to expand...
Click to collapse
It's not letting me edit my Debloater OP either

This worked great for external SD Card. Any way to get write permission on Device>Sd card? I can't download apps from Amazon App Store because it wants to write a folder there for the apps but it won't let it.

Subscribed for future use. Haven't had any issues yet, but I'm only on day 3 with ND8

Wrightperspective said:
This worked great for external SD Card. Any way to get write permission on Device>Sd card? I can't download apps from Amazon App Store because it wants to write a folder there for the apps but it won't let it.
Click to expand...
Click to collapse
If you deodex the Rom then use xposed framework in there that allows write permission. Or use a root explorer go to storage sd and then properties and change the permission there
Sent from my SPH-L710 using XDA Free mobile app

This is what I get when I try to install xposed framework... Any ideas?

The only xposed module I use is wanam and I've not seen that popup so... BTW this isn't xposed.

Chad The Pathfinder said:
The only xposed module I use is wanam and I've not seen that popup so... BTW this isn't xposed.
Click to expand...
Click to collapse
Yeah but it's extracting the zip on the internal storage is what he means I think...I'm having the same issue where none of my apps can write to the internal storage, but external storage is fine

CNexus said:
Yeah but it's extracting the zip on the internal storage is what he means I think...I'm having the same issue where none of my apps can write to the internal storage, but external storage is fine
Click to expand...
Click to collapse
That was my my problem I used es root explorer mounted system changed permissions to all storage the changed system permission and added uid to system permissions. Then rebooted and all good. It had my internal sd blocked apps couldn't show thumbnails some could some couldn't.
Also I had that same error with exposed until I changed those permissions. Now all well got wanam call recording, back to kill, all the goodies
Sent from my SPH-L710 using XDA Free mobile app

download app called folder mount in market.. run it reboot all fixed

Robalboa said:
That was my my problem I used es root explorer mounted system changed permissions to all storage the changed system permission and added uid to system permissions. Then rebooted and all good. It had my internal sd blocked apps couldn't show thumbnails some could some couldn't.
Also I had that same error with exposed until I changed those permissions. Now all well got wanam call recording, back to kill, all the goodies
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Can you expand on how you did this? I'm trying to do just this, but I'm not sure what you mean by mounting the system changed permissions to all storage...
Is that under the permissions.xml or is that somewhere else?

McBadass said:
Can you expand on how you did this? I'm trying to do just this, but I'm not sure what you mean by mounting the system changed permissions to all storage...
Is that under the permissions.xml or is that somewhere else?
Click to expand...
Click to collapse
OK you must be Rooted and have supersu first of all.
Second open es file Explorer
Goto tools (swipe right) turn on root Explorer grant super user permission
Next I press root Explorer (the tool you switched on)
You'll see a pop up that gives you options click mount system r/w
Next navigate to each internal folder (legacy emulated and 0) long press each one separately
Long press o choose properties in the more section change to r/w on both the top rows all the way a crossed 3 check boxes
Do this on all 3 folders next
Navigate to system long press, then properties again check same boxes and also check uid.
Close out es and reboot.
Tada all apps work fine.
Sent from my SPH-L710 using XDA Free mobile app

Of course why they have changed the permissions of the external sdcard is puzzling since the internal memory sdcard still allows full access. So, I imagine their next step will be the internal storage permissions. Isn't this a strange restriction from a company like Google who claims to be so 'open'. I guess they are hiring too many of those Apple defectors nowadays.
Anyway, I download podcasts, and I really don't like the way if I use the default external sdcard permissions that anything the app puts in the extsdcard/android/data/(app) directory gets deleted when I remove the app, and since most apps are being changed to abide by these new permission restrictions in kitkat, will this modification stop kitkat from deleting the app data on the external sdcard when the app is removed?
Sent from my Nexus 7 using Tapatalk

DaWeav said:
Of course why they have changed the permissions of the external sdcard is puzzling since the internal memory sdcard still allows full access. So, I imagine their next step will be the internal storage permissions. Isn't this a strange restriction from a company like Google who claims to be so 'open'. I guess they are hiring too many of those Apple defectors nowadays.
Anyway, I download podcasts, and I really don't like the way if I use the default external sdcard permissions that anything the app puts in the extsdcard/android/data/(app) directory gets deleted when I remove the app, and since most apps are being changed to abide by these new permission restrictions in kitkat, will this modification stop kitkat from deleting the app data on the external sdcard when the app is removed?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Easy way to find out is to backup the data folder and remove the app. Will probably take as long to test as it did to ask.

bilgerryan said:
Easy way to find out is to backup the data folder and remove the app. Will probably take as long to test as it did to ask.
Click to expand...
Click to collapse
Plus getting the data folder and file permissions correctly set can be a little difficult.
It would probably be easier to backup the app with Titanium to begin with since it saves and restores the data for you.
Edit: And to address the original question about external SD saved data folder, I have no idea other than to copy it off before you remove the app and copy it back before you first launch it.

Can't Mount /system R/W with Magisk

So I run my own custom builds of Lineage with a bunch of cherry picks to bring back the blue and grey Pixel theme, bypass SafetyNet, disable dm-verity and many other tweaks (they are many of the same cherry picks in Invisiblek's builds).
I'm noticing a strange issue now though. I switched over to Magisk (the modded Pixel version found here on XDA) from my many years of using SuperSU because it can pass SafetyNet, however I just I noticed now that I am unable to mount /system as RW. No app that mounts /system is able to do it and if I try it manually through ADB or the terminal app, I get an error saying "/system not found in /proc/mounts".
Does anyone know how I can fix this to mount /system as RW. Realistically, I don't need to mount it for any reason since I don't include any apps I don't want in my own builds but it just kind of bothers me that I can't do it if I wanted to.

admiralspeedy said:
So I run my own custom builds of Lineage with a bunch of cherry picks to bring back the blue and grey Pixel theme, bypass SafetyNet, disable dm-verity and many other tweaks (they are many of the same cherry picks in Invisiblek's builds).
I'm noticing a strange issue now though. I switched over to Magisk (the modded Pixel version found here on XDA) from my many years of using SuperSU because it can pass SafetyNet, however I just I noticed now that I am unable to mount /system as RW. No app that mounts /system is able to do it and if I try it manually through ADB or the terminal app, I get an error saying "/system not found in /proc/mounts".
Does anyone know how I can fix this to mount /system as RW. Realistically, I don't need to mount it for any reason since I don't include any apps I don't want in my own builds but it just kind of bothers me that I can't do it if I wanted to.
Click to expand...
Click to collapse
im actually having the same concern as you . im also trying to look on threads to see if there is a way to fix this mount issue with magisk, but still cant seem to find an answer till now...

reyscott said:
im actually having the same concern as you . im also trying to look on threads to see if there is a way to fix this mount issue with magisk, but still cant seem to find an answer till now...
Click to expand...
Click to collapse
Well, at least I'm not the only one

Magisk is systemless root, is it not? I don't know if that make a difference.

jova33 said:
Magisk is systemless root, is it not? I don't know if that make a difference.
Click to expand...
Click to collapse
That simply means it doesn't need to modify the system partition to provide root access. That doesn't stop the user/apps from mounting system and modifying it themselves.

This ended up biting me in the ass 'cause now I can't mount /system in TWRP and restore. :|

Root Explorer can mount System r/w. I do this once a month to move my Adguard HTTPS cert to System. Still passes SafetyNet, too.

This seems to be a major issue in the custom Magisk build for Pixel phones. I've seen a few threads about it and even started my own, but as far as I'm aware, there's no fix. The Magisk dev doesn't seem to want to officially support Pixel phones despite there already being pull requests on the project which implement A/B support. I'm pretty sure it's the same issue that stops Magisk modules from working if they touch /system to make file changes.

carlylemiii said:
Root Explorer can mount System r/w. I do this once a month to move my Adguard HTTPS cert to System. Still passes SafetyNet, too.
Click to expand...
Click to collapse
I've been modifying system from the jump with Root Explorer and FX file explorer works too with it's root addon

Quoting chainfire's writeup from when he first rooted the Pixel: "what we originally thought of as /system is now a subfolder inside that partition's filesystem... The system partition is now mounted to /system_root, with the /system directory symlinked to /system_root/system. This move is blatantly stolen from the stock recovery mechanism."
I don't feel like re-rooting with superSu to check if it still works that way (i.e. if I can see a /system_root mount and/or see if /system is a link (IIRC one of this later changes was actually to change this to a bind mount).
When using Magisk, I haven't been able to find evidence of a /system (or /system_root) mount anywhere (using "mount" and "df" commands). Which leads me to guess that "/" is actually the mount point to the partition containing system (i.e. /system is actually just a straight-up sub folder of /) -- but I'm no expert at interpreting linux/unix mounts/disks/etc.
I have Root Explorer and I have to hit the "mount r/w" button while in "/" and NOT while in "/system", which leads me to guess that when these apps are giving rw access to /system that they're actually remounting (or something similar) the "/" as rw. BUT I have yet to determine what specific command one could run on the cmd line to reproduce this behavior.
Theoretically @goodwin_c or maybe @topjohnwu would know better what /system actually is at runtime...

I have this exact same issue using OnePlus One, so it might not be a Pixel XL-specific issue?
Magisk + MagiskSU are installed successfully.
TitaniumBackup is granted root privileges and functions normally.
But I found that other apps don't. For example:
1. it grants Wakelock Detector root privileges just fine, but when trying to "INSTALL AS A SYSTEM APP", it returns error "An error occurred mounting system rw. Aborted".
2. Similar case with GSam Battery Monitor (Root Companion), error message displayed is: "Unable to copy the file "yyy/aaaa/xxxxx.apk" to "/system/priv-app/gsamrootcompanion.apk".
You may need to try this manually using a tool such as Root Explorer.
3. Guess what. Root Explorer won't open either.
Anyone with any hints or tips for solving this would be greatly appreciated.

Nikola G. said:
I have this exact same issue using OnePlus One, so it might not be a Pixel XL-specific issue?
Magisk + MagiskSU are installed successfully.
TitaniumBackup is granted root privileges and functions normally.
But I found that other apps don't. For example:
1. it grants Wakelock Detector root privileges just fine, but when trying to "INSTALL AS A SYSTEM APP", it returns error "An error occurred mounting system rw. Aborted".
2. Similar case with GSam Battery Monitor (Root Companion), error message displayed is: "Unable to copy the file "yyy/aaaa/xxxxx.apk" to "/system/priv-app/gsamrootcompanion.apk".
You may need to try this manually using a tool such as Root Explorer.
3. Guess what. Root Explorer won't open either.
Anyone with any hints or tips for solving this would be greatly appreciated.
Click to expand...
Click to collapse
That's weird because I flash a new ROM about every five days and consistently replace the stock phone app in a few different ROMs by using root explorer to drop in the priv app folder

Nikola G. said:
I have this exact same issue using OnePlus One, so it might not be a Pixel XL-specific issue?
Click to expand...
Click to collapse
Unless it has the a/b setup and the same changes to the system partition (see my post above about what chainfire explained), then I wouldn't think it's related at all.
Pretty sure you've needed to set SELinux to permissive for TiBu to install/remove system apps for a while now.
----
Back to the Pixel. I reread chainfire's explanation of what his root method does for Pixels (https://plus.google.com/+Chainfire/posts/fvEPo42GKXS). I don't have much knowledge on partitions, mounts, Kernels, or Androids boot process, but I believe what he is saying is that supersu changes things such that "/" is actually from the boot partition rather than from the system partition (which then matches the way most/all other phones work). That makes sense to me why there is a /system_root mount and a /system bind mount (in other words, once you change "/" away from the system partition, you need to mount what it used to be somewhere to actually get to the system folder)
Now, just a guess here, but I'm thinking that Magisk isn't doing this at all. Which would mean that "/" is still actually mounted from the system partition and /system is still just a subfolder of that partition. This would explain why "/system" can't be mounted rw, since it's just a folder. And that would explain why I need to be in the "/" folder in Root Explorer to mount rw, since this folder would actually be the mount point.
Of course, if that is all accurate, I'm still curious to know what that remount command would actually be from the cmd line
Sent from my Pixel using Tapatalk

I have this exact same issue using Sony Xperia z5 Compact ! will a combination of SU and magisk work? just going to try it out. ( later removing the su)

Set seliux to permissive.

rori~ said:
Set seliux to permissive.
Click to expand...
Click to collapse
this doesnt fix the problem lol..the problem iswith googles implementation of tge new partition layout.. if u actually look in the fstab you will see the problem, system as we know it isnt there lol
if fact, what we would call root fs or / has the only "system" reference in the fstab.in fact, here are the procs/mounts in my fstab on my pixel 2 xl on los 15.1:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/soc/1da4000.ufshc/by-name/system / ext4 ro,barrier=1 wait,slotselect,avb
/dev/block/platform/soc/1da4000.ufshc/by-name/userdata /data ext4 errors=panic,noatime,nosuid,nodev,barrier=1,noauto_da_alloc latemount,wait,check,formattable,fileencryption=ice:aes-256-heh,eraseblk=16777216,logicalblk=4096,quota
/dev/block/platform/soc/1da4000.ufshc/by-name/misc /misc emmc defaults defaults
/dev/block/platform/soc/1da4000.ufshc/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=ubject_r:firmware_file:s0 wait,slotselect
/devices/soc/a800000.ssusb/a800000.dwc3* auto vfat defaults voldmanaged=usb:auto
/dev/block/zram0 none swap defaults zramsize=536870912,max_comp_streams=8
as u can see, what we knew as rootfs is now list as:
/dev/block/platform/soc/1da4000.ufshc/by-name/system / ext4 ro,barrier=1 wait,slotselect,avb
itvis ro and good ole avb
I do feel however system is more than just a folder now.. its almost like the "new" rootfs... like normally the default prop is contained in the boot.img, now it is in /system/etc/prop.default and is linked/appears as default prop in the root directory
to add, the vendor partition is more equal to system now.. the structure of these two are very similar.. heck, they even each hold portions of the sepolicy files.. supposedly this was intentional.. i can mount rw all day but in my experience my changes revert after a reboot lol.. im on a userdebug build with verity disabled,magisk, permissive etc etc and changes do not stick as the untouched img from the non used slot seems to be in play in my situation
this layout isnt goin away soon lol. with project treble and phones being released with oreo having to follow the same scheme we will simply need to find other ways im afraid.. the vendor partition is probably the most modified now as its oje of if not the only partition google is letting vendors update to streamline the process and to leave amajority of the os untouched/unmodified by vendors.. its actually quiye smart as it should allow for carriers to push out updates more quickly
also, looking at the boot process, since system and vendor have more power now and hold things like sepolicy they are actually mounted extremely early in the boot process and not allowed to be mounted again later on sort of like a "never allow" flag saying no matter what circumstances these partitions cannot be mounted after earlyfs
but anyone, ill close my rant by saying you cannot mount something that doesnt exist in the mount point/fstab

Piccit, you are absolutely right!
in terminal I replaced "/system" with "/" and it worked. thank you very much.

piccit said:
Unless it has the a/b setup and the same changes to the system partition (see my post above about what chainfire explained), then I wouldn't think it's related at all.
Pretty sure you've needed to set SELinux to permissive for TiBu to install/remove system apps for a while now.
----
Back to the Pixel. I reread chainfire's explanation of what his root method does for Pixels (https://plus.google.com/+Chainfire/posts/fvEPo42GKXS). I don't have much knowledge on partitions, mounts, Kernels, or Androids boot process, but I believe what he is saying is that supersu changes things such that "/" is actually from the boot partition rather than from the system partition (which then matches the way most/all other phones work). That makes sense to me why there is a /system_root mount and a /system bind mount (in other words, once you change "/" away from the system partition, you need to mount what it used to be somewhere to actually get to the system folder)
Now, just a guess here, but I'm thinking that Magisk isn't doing this at all. Which would mean that "/" is still actually mounted from the system partition and /system is still just a subfolder of that partition. This would explain why "/system" can't be mounted rw, since it's just a folder. And that would explain why I need to be in the "/" folder in Root Explorer to mount rw, since this folder would actually be the mount point.
Of course, if that is all accurate, I'm still curious to know what that remount command would actually be from the cmd line
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
If anyone is still reading this thread....I successfully got rw access with:
Code:
mount -o rw,remount /

fritz.barnes said:
If anyone is still reading this thread....I successfully got rw access with:
Code:
mount -o rw,remount /
Click to expand...
Click to collapse
I got error while trying to mount /system folder.
alioth:/ # mount -o remount,rw /system
mount: '/system' not in /proc/mounts
Click to expand...
Click to collapse

dRakeNNNN said:
I got error while trying to mount /system folder.
Click to expand...
Click to collapse
Thank you for this helpful comment. Do you have any idea why this would allow me to modify my system/app folder but *not* my system/priv-app? Ostensibly they should both have r/w access, yet when I try to remove facebook's apps from my priv-app folder I get this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried specifically to remount /system/priv-app but get the same proc/mount error. I actually went further and just tried /system/priv-app/FBServices but this is now giving me a separate error:
Do you have any idea how I might go about resolving this? Other apps that attempt to change r/w access in my /priv-app folder are encountering errors as well.