Related
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
I've recently switched to an M8 from a Z2 and am no stranger to the roadblock that is the External SD access issue, but can't seem to find a solid fix for the HTC One.
Have spent the evening unlocking the bootloader an rooting only to have some strange issues. It seems that whenever an app attempts to write to the system the phone reboots. This means I can't install NextApp SD Fix or make changes to the platform.xml file since they send me into a reboot.
Additionally, removing system apps with Titanium backup doesn't stick as after a reboot they all reappear.
My question is, am I missing something that is causing these problems and is there a fix for the external SD problem?
Thanks
DeGozaru said:
My question is, am I missing something that is causing these problems and is there a fix for the external SD problem?
Click to expand...
Click to collapse
You need a kernel module:
http://forum.xda-developers.com/showthread.php?p=51543139
Or a custom kernel.
BenPope said:
You need a kernel module:
http://forum.xda-developers.com/showthread.php?p=51543139
Or a custom kernel.
Click to expand...
Click to collapse
Thanks BenPope. Gave it a try but can't get it to work. Have asked for help in the thread.
Additionally, I have solved my issue for external SD write access by following the steps here: http://forum.xda-developers.com/showpost.php?p=54696085&postcount=13
Thanks mods for moving thread. Please close.
Hey warriors!
Pls help - after installing apk and storing obb files into sd card/android/obb folder I cannot run any HD game with my G3. The application will not find the files.
My procedure:
- download apk + cache
- install apk
- place obb files into obb folder (usually the files are already in a correctly named folder, e.g. "com.pixelbite.rr3" (for recklessracing3), so I just extract and copy them from my PC over to SD card)
- run apk - it will then give me an error message, or just look for the files for eternity, or simply just crashes
I have tried couple of games - NOVA3, MC5, RecklessRacing with no luck
- is it because I am not rooted?
- is it necessary to change something in phone settings prior to installing?
- or simply what I am doing wrong?
Many thanks for your help!
leeris said:
Hey warriors!
Pls help - after installing apk and storing obb files into sd card/android/obb folder I cannot run any HD game with my G3. The application will not find the files.
My procedure:
- download apk + cache
- install apk
- place obb files into obb folder (usually the files are already in a correctly named folder, e.g. "com.pixelbite.rr3" (for recklessracing3), so I just extract and copy them from my PC over to SD card)
- run apk - it will then give me an error message, or just look for the files for eternity, or simply just crashes
I have tried couple of games - NOVA3, MC5, RecklessRacing with no luck
- is it because I am not rooted?
- is it necessary to change something in phone settings prior to installing?
- or simply what I am doing wrong?
Many thanks for your help!
Click to expand...
Click to collapse
Most of the time, that stuff is stored in the /data partition which you cannot access to write to without root. The only "people" that can access and write to that area are the app itself that wrote to it initially, and an account with root access.
Some games might store some "cache" to the internal sd card, but that all depends on the app.
This is why using the cloud is so much better for game advancement, but not all games are using that.
iBolski said:
Most of the time, that stuff is stored in the /data partition which you cannot access to write to without root.
Some games might store some "cache" to the internal sd card, but that all depends on the app.
This is why using the cloud is so much better for game advancement, but not all games are using that.
Click to expand...
Click to collapse
I think I got your point but what would be the safest way to install games without issues? Will rooting the device solve the problem, or is there still some work to do most of the time with every game?
And if root is OK, is there any one-click root available for G3 which is safe? I am very good at bricking the phones
leeris said:
I think I got your point but what would be the safest way to install games without issues? Will rooting the device solve the problem, or is there still some work to do most of the time with every game?
And if root is OK, is there any one-click root available for G3 which is safe? I am very good at bricking the phones
Click to expand...
Click to collapse
The only other way to make this work, and you would have had to backed everything up before, is to use Helium which (without root) requires you to have a Windows or Mac client app installed on your PC and you hook up you device that way. It can then backup the data and restore it, without root. However, it only works with certain apps. Not all apps can be backed up with Helium.
As for rooting, it depends on which model of G3 you have. Overall, rooting is easy, but it depends on which version of the Android OS it's running and again, which model of G3 you are using. I don't want to go into it with this thread as it can all be discovered by going to the following FAQ thread in the OP and finding the section for rooting. There it explains which root method works on which model of phone and what version of the OS you must be on. Again, this all depends on the model of the phone you have. Here is the link to the FAQ post:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
After that, you can use a lot of different apps to backup and restore your app and data. TiBu is the most popular one.
iBolski said:
The only other way to make this work, and you would have had to backed everything up before, is to use Helium which (without root) requires you to have a Windows or Mac client app installed on your PC and you hook up you device that way. It can then backup the data and restore it, without root. However, it only works with certain apps. Not all apps can be backed up with Helium.
As for rooting, it depends on which model of G3 you have. Overall, rooting is easy, but it depends on which version of the Android OS it's running and again, which model of G3 you are using. I don't want to go into it with this thread as it can all be discovered by going to the following FAQ thread in the OP and finding the section for rooting. There it explains which root method works on which model of phone and what version of the OS you must be on. Again, this all depends on the model of the phone you have. Here is the link to the FAQ post:
http://forum.xda-developers.com/lg-g3/help/help-thread-lg-g3-question-t2947298
After that, you can use a lot of different apps to backup and restore your app and data. TiBu is the most popular one.
Click to expand...
Click to collapse
But when a game with cache is officially downloaded from Google Play - this should work more or less correctly right?
leeris said:
But when a game with cache is officially downloaded from Google Play - this should work more or less correctly right?
Click to expand...
Click to collapse
What? You have me confused.
What are you expecting to happen when you download an app from Google Play? Not sure what you are asking...
Just purchased my galaxy tab s. When I found out how it behaves with external memory rooted it at once, did the thing for read/write permissions, disabled this weird safety feature and... It does not alow editing files to any program which causes a big problem when I try to use "iGO" navigator for example which keeps its files on SD, or use some office program to edit any content on SD... It does alow creating and deleting files though.
Any ideas? Many thanks in advance!
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Or try using a custom kernel
DUHAsianSKILLZ said:
Or tey using a custom kernel
Click to expand...
Click to collapse
what do you mean?
hmaxos said:
I guess it's a kitkat problem. I heard in lollipop google returned to full read write access to SD cards.
Click to expand...
Click to collapse
Maybe there is some fix possible about it?
gyrtaz said:
what do you mean?
Click to expand...
Click to collapse
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
DUHAsianSKILLZ said:
Sorry i meant try a custom kernel. Skyhigh kernel fixes sd problems. I am running it now and it does work. Perhaps you can try that?
Click to expand...
Click to collapse
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
gyrtaz said:
I only found topics about sd r/w problems where they say that I need to root and run some code (or edit some file manually) to fix permissions. Well I did it... But I couldn't find anyone talking about editing... I can get around that by saving an edited file in diferent name, deleting the original and renaming it back to original... But programs I try to use does not do tricks like that :silly:
Was your problem similar? Any links regarding the fix of this?
Click to expand...
Click to collapse
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
DUHAsianSKILLZ said:
Well I have always ran skyhigh kernel for my sd card. Even if rooted with the sd fix my sd card still worked fine(on stock rom). Perhaps it could be the file manager your using? Well i also seen the r/w fix by editing a file but that was months ago and I forget how to do it. Sometimes sd fix app would say its fixed, but it wasnt. So using another app from the playstore could fix it? Hope this helps
Click to expand...
Click to collapse
The file seems to be edited properly but none of programs are able to edit files. Biggest problem at the moment that iGO won't save its configuration and shut down when a route is entered. I assume it is because of unability to edit files in sd also
Hi, just to share with you!
Whats this? In short, it is deodexed -> resigned -> zipaligned, installed busybox, supersu, dual recovery (vol up for twrp, vol down for cwm), 5way reboot menu ...and some other changes which you can read about it here -> https://github.com/munjeni/D5503_14.5.A.0.242/commits/master .
How to download rom:
- go to here -> https://github.com/munjeni/D5503_14.5.A.0.242/tree/ae7b18de7faa97eaf01eff1c2b6abeb540feaf6f and on the right side you have "Download zip"
- after downloading rom is not ready, do not flash!!!
How to install:
- after you download rom you must repack zip since git always add things into new folder inside zip so you will need repack it first before installing!
- simple open main zip and go to folder "14.5.A.0.242.master", select all files from these folder, drag and drop it to a new empty zip, you are done. Before you flash rom please read "iportant" section! Flash these new zip with any recovery. Done.
Mirrored download link (using this you no need to repack anything, just download and install!):
- https://mega.co.nz/#!Co1yERia!eJVCBjTZrjXok3KXZxM9xp_28I9Pos-LPYKjigJ6Bok
Important:
- you must fully wipe /data partition (mean delete everything from /data folder)! Or another solution, flash only userdata from any LolyPop ftf! Why? Because all old files from internal storage is not relabeled and you will encounter a lot of problems and all these files can not be accessed from android, pictures, private files... etc is not accessible than! Don't think it will work without wipe, it will not! Wioe data factory reset have no sense, I recomend installing userdata from ftf since its more a safe way!
Changelog:
- https://github.com/munjeni/D5503_14.5.A.0.242/commits/master
Enjoy!
munjeni said:
Hi, just to share with you!
Whats this? In short, it is deodexed -> resigned -> zipaligned, installed busybox, supersu, dual recovery (vol up for twrp, vol down for cwm), ...and some other changes which you can read about it here -> https://github.com/munjeni/D5503_14.5.A.0.242/commits/master . Curently I am stoped development on this rom since I am unable to solve thing like this -> lolipop have two classpaths (BOOTCKLASSPATH and SYSTEMSERVERCLASSPATH) and I not understand how to access classes from one classpath to another classpath, if you have idea how I can get this than I will probably continue development. My plan was implementing privacy guard rom cm12 but since I have problem accessing classes I am temporary stoped
How to download rom:
- go to here -> https://github.com/munjeni/D5503_14.5.A.0.242 and on the right side you have "Download zip"
- after downloading rom is not ready, do not flash!!!
How to install:
- after you download rom you must repack zip since git always add things into new folder inside zip so you will need repack it first before installing!
- simple open main zip and go to folder "14.5.A.0.242.master", select all files from these folder, drag and drop it to a new empty zip, you are done. Flash these new zip with any recovery. I have made some automated scripts so you no need to wipe anything since everything needed will be done auto so just click "install" and wait until rom get installed.
Enjoy!
Click to expand...
Click to collapse
Flashed this ROM and it is amazing.
Debloated it, installed some mods like xposed, xposed fix, modded services.jar for superuser mode, modified mixer_paths.xml for more loudness and some apps like MyAndroidTools, TitaniumBackup, Greenify.
Works like a charm and good battery life.
Only thing is the aweful toogle change by Google (no silent, vibrate toggle on quick settings) - but this depends NOT on your ROM.
Thx munjeni (one more time) for your time, work and effort.
m.
Investigated and got solution for 5 way reboot menu
Where you got moded services with superuser mod? I wanted to start porting it from cm12 but if it is allready exist I will be glad to look into it
munjeni said:
Investigated and got solution for 5 way reboot menu, you can download from here (just download android.policy.jar and replace) -> https://github.com/munjeni/D5503_14.../system/framework/android.policy.jar?raw=true enjoy
Where you got moded services with superuser mod? I wanted to start porting it from cm12 but if it is allready exist I will be glad to look into it
Click to expand...
Click to collapse
http://forum.xda-developers.com/sony-xperia-z1-compact/themes-apps/mod-accent-systemui-t3088719
moonryder said:
http://forum.xda-developers.com/sony-xperia-z1-compact/themes-apps/mod-accent-systemui-t3088719
Click to expand...
Click to collapse
I have no idea why it is caled SuperUser Mod since it have nothing related to SuperUser. It is just SignatureDisable mod, author stupidly gave these name to these mod which apsolutly have nothing related to superuser If you look into commits on my git you will notice that you no need his services.jar since my rom allready have disabled signature verification, I not guarant you how his services is patched, but I can sugest you to replace services.jar whith one from my rom since compatibility is guaranted
This http://www.androidauthority.com/cyanogenmod-12-superuser-577985/ is what I call superuser mod (I have plan to port it here), and diferencie between "wrongly named" superusermod and real superusermod like one from cm12 is like this and this
munjeni said:
...and diferencie between "wrongly named" superusermod and real superusermod like one from cm12 is like this and this
Click to expand...
Click to collapse
LOL
Ok bro will wait for a "real" PrivacyGuard for LP 5.0.2, modded by the master munjeni itself
When trying to install an app from sd card, I am getting out of space message, can't install apps from sd card
btw.. already wiped everything, and system storage shows correct info
nemphis said:
When trying to install an app from sd card, I am getting out of space message, can't install apps from sd card
btw.. already wiped everything, and system storage shows correct info
Click to expand...
Click to collapse
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
I can install apps from sdcard [emoji18]
But I am unable to download some apps from playstore
munjeni said:
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
Click to expand...
Click to collapse
NO problems here, i can install apps from sd card am on stock rooted lollipop with unlocked boot-loader.
I'll wait for another simplified flashable version of your rom.
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Freshly installed and everything is perfect ! Thank you very much brah !!
D5503 UB Dstriker ROM KK.157
Winb33 said:
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Click to expand...
Click to collapse
i tried that and / or replaced some things like bootanimation, fonts etc.
Flashing failed, so flash it untouched and remove / add things then.
pathaniya said:
NO problems here, i can install apps from sd card am on stock rooted lollipop with unlocked boot-loader.
I'll wait for another simplified flashable version of your rom.
Click to expand...
Click to collapse
I'm trying to solve this but have no idea how to do it, it is selinux restriction (if somebody have idea how it can be solved let me know please), but temporary solution is: via terminal emulator disable selinux, than install app, than enable selinux. To disable selinux write "setenforce 0", than install app, than enable selinux "setenforce 1"
Winb33 said:
Thanks @munjeni for this release !
Will give a shot tonight when everybody is sleeping
Question : Can i remove some elements ( unuseful app for my usage when repackaging rom ) regarding your install script ?
Thanks mate !
Click to expand...
Click to collapse
You can but only if you propertly remove lines from updater-script since it is hardcoded with our rom, instead recovery will abort installation if you missed something in updater-script ! My sugestion is, remove things manualy using an root file explorer, or at least add some lines in updater script which will remove things that you want
munjeni said:
Hi, I have noticed the same thing, but I don't know if it is related to lolipop in general! Anybody confirm on stock unmodified rom?
Click to expand...
Click to collapse
First when installed FR version same problems with SD card. Also ESexplorer had problems accessing SD card
Now on stock rooted works everything fine related to SD card.
Run also SDfix app becouse Titanium problem
Sent from my D5503 using XDA Free mobile app
EasySR said:
First when installed FR version same problems with SD card. Also ESexplorer had problems accessing SD card
Now on stock rooted works everything fine related to SD card.
Run also SDfix app becouse Titanium problem
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
No man, you no need sdcard fix. I allready included sdcard fix https://github.com/munjeni/D5503_14.5.A.0.242/commit/21b396daf721791c3675de417c543ba6184e21d1 and you can read / write any storage without problems, but we speak about problem related to the "installing apps from sdcard"! For example, if you try to install blablabla.apk which is on any storage you will get "no free space" error since selinux DENIED installing it, I don't have idea why it happen since I am not familiar with selinux, only very basic things by now. I will try to solve this problem!
munjeni said:
No man, you no need sdcard fix. I allready included sdcard fix https://github.com/munjeni/D5503_14.5.A.0.242/commit/21b396daf721791c3675de417c543ba6184e21d1 and you can read / write any storage without problems, but we speak about problem related to the "installing apps from sdcard"! For example, if you try to install blablabla.apk which is on any storage you will get "no free space" error since selinux DENIED installing it, I don't have idea why it happen since I am not familiar with selinux, only very basic things by now. I will try to solve this problem!
Click to expand...
Click to collapse
Just installed app on stock rooted lolipop (3G Watchdog) from SD card
Sent from my GT-P5110 using XDA Free mobile app
Hey guys, I'm having a hard time installing xposed installer, I get "not enough space" error. Could any of you help out a fellow user..?
D5503 UB Dstriker ROM KK.157
EasySR said:
Just installed app on stock rooted lolipop (3G Watchdog) from SD card
Sent from my GT-P5110 using XDA Free mobile app
Click to expand...
Click to collapse
Ok thanks for info. On my rom selinux must be disabled temporary before installing any app from sdcard, than enabled. I will try to understand why it happening. For sure it is related to selinux. I replaced platform key in selinux_policy.xml since all apks on our rom is resigned and zipaligned but it was not solved problem related to the installing apks from sdcard.