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 just got a new P2a42. trying to update it manually to nougat by downloading S062toS233 update.zip to sdcard. But update from stock recovery is failing. I then noticed, my phone is still on S048 version. The update in settings is not working with network connection failed. Tried searching on google for stock recovery update from S048 to S062 but couldn't find anything. Can someone point me to where to download update for S048 to S062 or else I will just have to wait 14 days for bootloader unlock.
Thank You
Edit: I found the S048 to S062 update.zip. However that too is failing. I am not sure what am I doing wrong. I formatted a sdcard to fat32. Renamed zip to update.zip. Copied to sdcard. Inserted in phone. Booted phone in recovery. Apply update.zip. But that is failing immediately at 0% only without proceeding any further
Also, I think I have marked the thread wrongly as Q&A. Any mod, kindly help to change thread type!
Solved: Incase anyone else faces this issue, my sdcards were partitioned as logical. I changed one sdcard partition to primary and the update worked immediately.
i had the same problem, i just changed the name to update( not update.zip as it was already in zip format) and it worked. or try this one-http://phonedl.ota.lenovomm.com/dls/v6/P2a42_S062_170117_ROW_TO_P2a42_S233_170404_ROW_WC5805C608.zip
Hello!
Well, basically my problem is when I try to move an app to /system/app.
I am user of GPS spoofers and today I've unlocked my bootloader, flashed latest twrp by @Alberto97 and followed this thread to use Magisk:
https://forum.xda-developers.com/moto-z-play/how-to/how-to-safetynet-7-1-1-update-stock-rom-t3669086
I'm using Nougat 7.1.1 security patch December 1.
As I use GPS spoofers, I wanted to move GPS Location app to /system/app to do not use mock locations, and then hide Magisk to play Pokemon go, but every time I tried to move it to system with Link2sd, after trying, it was just showing the following error when I tried to to move the app to system:
"mount '/dev/block/dm-0'- '/system' device or resource busy"
I really don't want to downgrade to MM to try to move it, and maybe if I downgrade, the problem will not be fixed too... So, can anyone help me with it? I really want to move it to system, and I don't know what to do, I'm really new with this error.
Thanks, hope you help me!
/system write is disabled when the device is turned on, security
Use twrp. First mount /system in the mount menu, then advanced and file manager to move it from /data/app to system
And maybe it also needs to go to /system/priv-app, but I am not sure about that
user822 said:
/system write is disabled when the device is turned on, security
Use twrp. First mount /system in the mount menu, then advanced and file manager to move it from /data/app to system
And maybe it also needs to go to /system/priv-app, but I am not sure about that
Click to expand...
Click to collapse
So, I need to go to mount menu of twrp, mount /system, go to advanced, file manager and search all the app folder or just .app(?) And move it to /system/app(or just /system?) And also copy(or move?) It to priv-app?
xdaVTU said:
So, I need to go to mount menu of twrp, mount /system, go to advanced, file manager and search all the app folderAnd move it to /system/app
Click to expand...
Click to collapse
Yes, there should be a folder in /data/app/ that has the right name
xdaVTU said:
And also copy(or move?) It to priv-app?
Click to expand...
Click to collapse
Yes, move the folder to /system/app
Only if then the app does not work, try to move it to /system/priv-app instead
user822 said:
Yes, there should be a folder in /data/app/ that has the right name
Yes, move the folder to /system/app
Only if then the app does not work, try to move it to /system/priv-app instead
Click to expand...
Click to collapse
So after doing that, will I need to use Link2sd to something or your tutorial is enough?
xdaVTU said:
So, I need to go to mount menu of twrp, mount /system, go to advanced, file manager and search all the app folder or just .app(?) And move it to /system/app(or just /system?) And also copy(or move?) It to priv-app?
Click to expand...
Click to collapse
xdaVTU said:
So after doing that, will I need to use Link2sd or lucky Patcher to something or your tutorial is enough?
Click to expand...
Click to collapse
No that makes an app into a system app, that is all
user822 said:
No that makes an app into a system app, that is all
Click to expand...
Click to collapse
thank you for the help, but... Everything was okay until I test the app, i don't know if you use this kind of app, but when I moved it to system/app it should allow me to access the system functions. As the attached image shows, I cannot access it yet, but it's already in /system/app.
Please dude, help me, i really want to use this functions
Edit. And when i try to convert the app to a user app, link2sd show me the error showed by the error image.
First: never EVER even mention LP anywhere. It is strictly forbidden to even mention it, it's warez since you can crack Apps with it to not have to pay while still using paid functions, please all edit your posts!
Second: you are using Magisk @xdaVTU. So learn to use its full potential! Magisk was made to make changes especially to /sytem without actually changing that partition in order to allow OTA updates since they would scan partitions like the system partition which are cryptographically secured. If they where even mounted r/w the update will abort.
So if you want to make changes to /system, just make a module or use existing ones, it's actually very easy. In your case there should be a module in manager called app systemizer (or something like that, haven't used Magisk in about a month), that should do the job.
But in general, you can simply "write" your own module, you don't need much for that. Just get the module template from github, it should be linked in the Magisk release thread. Unzip it. open the module.prop in a text editor and edit it how you want (only the text behind the = signs, very self explainatory). Save it. Then open the folder "system" and create the sub-folder app (or priv-app) and inside create some folder for the app. Put the apk file of the app you want to install in /sytem/app/foldername inside. At the end, put everything back into a zip file (the folders common, META-INF and system together with the files. Make sure it's a simple zip file thats not encrypted and that inside the files and folders aren't inside another folder (which is the case when you download the zip from github) otherwise it will fail to install. Then just install your new zip through the Magisk Manager or TWRP and done. Everyting should work now.
@Artim_96
I'm sorry for that, I'll edit the posts.
About the Magisk, I don't know how does it work fully, and would like just to use that GPS as a system app, so I would need a little help for that. I didn't understand anything about the modules, and the only reason I'm using Magisk than SuperSU is because I've seen some users saying SuperSU wasn't stable in Nougat and they've got into bootloop...
Is this security of just Nougat or marshmallow also have it?
Should I use SuperSU instead of Magisk for that?
Please help me with it.
Ah, one more question, should I downgrade to Marshmallow to get it to work?
xdaVTU said:
@Artim_96
I'm sorry for that, I'll edit the posts.
About the Magisk, I don't know how does it work fully, and would like just to use that GPS as a system app, so I would need a little help for that. I didn't understand anything about the modules, and the only reason I'm using Magisk than SuperSU is because I've seen some users saying SuperSU wasn't stable in Nougat and they've got into bootloop...
Is this security of just Nougat or marshmallow also have it?
Should I use SuperSU instead of Magisk for that?
Please help me with it.
Ah, one more question, should I downgrade to Marshmallow to get it to work?
Click to expand...
Click to collapse
I already told you what to do. Just do one of the two things
Artim_96 said:
I already told you what to do. Just do one of the two things
Click to expand...
Click to collapse
As I said, I didn't understand
xdaVTU said:
As I said, I didn't understand
Click to expand...
Click to collapse
Just read. I told you just use app systemize, it will do the job
Artim_96 said:
I already told you what to do. Just do one of the two things
Click to expand...
Click to collapse
Artim_96 said:
Just read. I told you just use app systemize, it will do the job
Click to expand...
Click to collapse
I forgot to Tell you, i tried to use systemizer but i dont know what happened, It failed when I tried to install It with magisk
xdaVTU said:
I forgot to Tell you, i tried to use systemizer but i dont know what happened, It failed when I tried to install It with magisk
Click to expand...
Click to collapse
That's something for the Magisk forum. Otherwise try terminal app systemizer too.
Artim_96 said:
That's something for the Magisk forum. Otherwise try terminal app systemizer too.
Click to expand...
Click to collapse
As i just want to move an app to /system/priv-app(yes, priv-app), can I just use TWRP terminal and move it? Without rooting my phone neither with magisk nor supersu? Or it isn't gonna work?
xdaVTU said:
As i just want to move an app to /system/priv-app(yes, priv-app), can I just use TWRP terminal and move it? Without rooting my phone neither with magisk nor supersu? Or it isn't gonna work?
Click to expand...
Click to collapse
It will work, but keep in mind you won't be able to make OTA updates. So if you want to update your firmware you'll probably have to use either Motorola device manager or manually flush it through RSD lite. Using Magisk should give you root, it's huge possibilities and still keep OTA updates working. But with Motorola devices it's a bit of work to get it to work because there is a bug in the kernel for years now
I don't have sure if its gonna help because is a little complicated to do, i don't have sure if its gonna work with newer versions of magisk or the way that you installed because some module won't work in the way that you install but you can try this. I used some time ago in aosp rom maybe works on stock too
https://forum.xda-developers.com/apps/magisk/module-smali-patcher-0-7-t3680053
This gonna allow fake location without selection on settings or put app in systen
@Artim_96 @jst98 @user822
Thank you all for helping me, mainly Artim and user, because with user's help I learned that tarp also can make some system modifications with file manager, but it seems to need root as well(I'm not sure about that actually), and Artim, you really helped me with those things about magisk modules. I've just flashed nougat 7.0, then I flashed twrp 3.0.2-0 and flashed magisk, it works very well!
And I found a kernel download link that really worked for me, with magisk modules(systemizer and appsystemizer) I could do what I wanted to.
Everything is working now, but I'd like to know if that f2fs fix kernel really works.. When I was using 6.0.1, I downloaded the kernel fixed for that Android version, but I just caused me a bootloop, so now I'm afraid about trying the 7.1.1 version...
xdaVTU said:
@[email protected]@user822
Thank you all for helping me, mainly Artim and user, because with user's help I learned that tarp also can make some system modifications with file manager, but it seems to need root as well(I'm not sure about that actually), and Artim, you really helped me with those things about magisk modules. I've just flashed nougat 7.0, then I flashed twrp 3.0.2-0 and flashed magisk, it works very well!
And I found a kernel download link that really worked for me, with magisk modules(systemizer and appsystemizer) I could do what I wanted to.
Everything is working now, but I'd like to know if that f2fs fix kernel really works.. When I was using 6.0.1, I downloaded the kernel fixed for that Android version, but I just caused me a bootloop, so now I'm afraid about trying the 7.1.1 version...
Click to expand...
Click to collapse
Of course you need the Kernel matching your Android version.
There also is a Magisk module that's supposed to fix it, but I don't know if it even works
EDIT:
Long story short, Magisk image was being flashed, but Magisk Manager kept telling me Magisk Is Not Installed.
Found the reason myself: By default, apps on my phone are set to be installed to my SD card. Magisk Manager does not like this. Switch it to internal storage and you're all good.
Perhaps it would be of help to confused people such as myself if daisy-specific guides would mention this.
Mods please close/delete this thread.
Background
I have some entries in my hosts file and wish to keep them after installing an OTA update via lineage recovery.
My device is a/b partitioned, but since slot b is damaged I manually swap slots and install the OTA to slot a (working slot).
However, even though thinks like settings don't change during/after this OTA, my hosts file gets erased with every weekly update.
What I need
A method to keep the hosts file without being erased. If it's possible to create a script somewhere in the root partiton or elsewere which prevents the hosts file deletion, that would suffice (as long as this script won't be erased itself during OTA).
What I'd rather not do
· I know I could reverse engineer every update.zip and apply my version of the hosts file, but that would be way too much effort.
· I know I could always adb push ~/my/hosts /system/etc/ and yes, that's what I'm doing right now. But I'd rather not have to do this every time I flash an update.zip.
Does anyone have an idea?
User699 said:
Does anyone have an idea?
Click to expand...
Click to collapse
How can you damage a slot?
kurtn said:
How can you damage a slot?
Click to expand...
Click to collapse
It just happend. I think I can "repair" it with a factory reset, but I don't want to do that now.
Do you happen to have an idea (about my question)?
lineageos use the addon.d directory, you can place a script which is executed before and after OTA update.
In my LOS 18.1 there is 50-lineage.sh which backup and restore etc/hosts
Here you can find more informations