Related
I found that [email protected]'s ROM had a good idea of adding WaveSecure to the system partition (preventing listing in the My Downloads part of market, and preventing uninstallation through normal means), but his version is slightly out of date now (latest version is 3.0.0.43)
As a result, I set about finding a means to install WaveSecure to ROM myself. Here are my findings for anyone interested in doing the same.
Install the latest version from the market (3.0.0.43 at this time). Now use adb pull to get it off the device onto your pc
Code:
adb pull /data/app/com.wsandroid.apk D:\com.wsandroid.apk
Now open Market back up from the menu, go to My Downloads, and choose Wavesecure Mobile Security Beta and uninstall it for just now (to get it off the data/A2SD location that normal apps are stored in) - thanks, my-space!
Then push the saved apk to the system partition after a remount (to make it read/write)
Code:
adb remount
Code:
adb push D:\com.wsandroid.apk /system/app/com.wsandroid.apk
Then set it all up as usual (will appear in apps list immediately)
and remount system as read only again
Code:
adb remount
And that seems to be it so far. Remember to change the D:\com.wsandroid.apk path to whatever you actually used.
Let me know if anyone finds any problems with this, but I've done it and, fingers crossed, it's worked OK for me.
Obviously, this is only for root users, and there are no guarantees for this.
Couple of questions that might need looked into -
- Do settings carry across after a wipe (as Paul claims Modaco's version does. I've never tried it so can't confirm)
- Is there any disadvantage to using this method? (I guess this is all Modaco's update.zip does, but I don't know)
you forgot to metion to uninstall wavesecure before it is pushed back into system....
my_space said:
you forgot to metion to uninstall wavesecure before it is pushed back into system....
Click to expand...
Click to collapse
Oops! Knew I'd forget something, as I always seem prone to do. Well spotted, and OP corrected.
Thanks
No worries I got a bit confused when i pushed it back onto the phone and was still in my downloads...
I've rooted my phone already but whenever i try to use the command adb remount I get "remount failed: operation not permitted". Suggestions?
I see more and more often, redundant threads.
What How-to will you post next time? How to change backlight settings?
You're pointlessly spamming the board.
I can't say i agree with the 'pointlessly spamming the board' comment, but i would have thought this would at least be better in the applications and themes subforum rather than in development.
Don't forget that an awful lot of android users (and more recently all HTC devices) are more and more 'newbs' and need stuff like this.
While this is good and provides info that people like that need (and myself cos i'm crap at adb and stuff like that so wouldn't have had a clue how to do this previously), maybe the development forum is not the best place for it....
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
usb0 said:
I'm guessing one won't be notified via Market if there's an update available if you push an app to /system/app/, right?
Click to expand...
Click to collapse
You won't be notified, correct
If anybody doesn't already know, WaveSecure have started hosting update.zip files. This means it's now easy to update your "baked-in" version of WaveSecure without much messing around.
https://www.wavesecure.com/installations/update.zip
Download the file, save it to your SD card, reboot into the recovery console and choose the option to apply an update.zip file.
Voila! Your version of WaveSecure will be updated to the very latest version
DJBenson said:
[...]
Click to expand...
Click to collapse
That's really awesome! Thanks for the tip!
Just a question of curiosity: If I push an app to /system/app/ and then issue the rm-command to remove its apk, won't there be lying a bunch of files associated with the program and with absolutely no function, since the app itself is removed? How do I know the name of these files and where they are located for removal?
I'm a bit confused by that question. My understanding (which may be incorrect but from what I've seen of the "guts of a ROM" appears to be the case) is that the applications reside in the apk files, they are not extracted. If you list the content of any of the app folders (/system/app, /data/app or /data/app-private) then all you get is a bunch of apk files (and some odex files). So when you 'push' an apk to the phone, that application is then "installed", when you rm/remove an application, you do so by removing the apk.
if you remove the apk you have left something in /data/dalvik-cache. wiping the dalvik-cache every now and then helps reclaiming that space, though it is not much.
the app settings and data are stored in /data/data, you could delete the files manually by checking their names (no idea if/what convention the names follow), imho not worth the trouble as it is only a few kb.
odex files aren't created if you don't do in a PITA process manually. don't worry about them, don't touch them, then you're good. odex files are only for system apps.
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
motomeup said:
I bought a used phone and it had WaveSecure already installed. I couldn't find it in the applications list to uninstall, so I did a factory reset on the phone. The application was still there and it still didn't show up in the applications list.
I have the Superuser Permissions application, so someone must have rooted it.
Is there any way to uninstall this?
Click to expand...
Click to collapse
""Just (re)flash a ROM................""
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
strife242 said:
I just noticed that WaveSecure now points to this post for instructions to install as system application, and I am not sure that the update.zip maintained with them is up-to-date.
However, you can now select to download the .apk directly to your PC thus eliminating the first Market step in this guide.
Click to expand...
Click to collapse
I believe it is kept up to date, as VillainROM kitchen uses it as a source for the WaveSecure app (fetched each night to keep it up-to-date).
I've certainly never had any problems with it.
Excellent guide Pulser,... I should really reinstall Wavesecure now Im not using a MoDacO Custom ROM. Nice one bruv.
Found this to be helpful.
https://www.wavesecure.com/blog/how-to-make-wavesecure-hard-reset-proof.aspx
I just did a search in the Market fro 'wavesecure' and two things popped up WaveSecure and WaveSecure UninstallProtection Add-on which needs to be uninstalled before WaveSecure and if the add-on is uninstalled it is supposed to lock the phone. (all this is in the description I have yet to try)
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
My device is rooted.
I've read a few other topics regarding this issue, but I'm still confused. As I understand it, using typical uninstall apps such as Titanium or Root Uninstaller do not remove the manufacturer apps from the phone still because of an S feature? I'm new to this process, so please forgive my naive rhetoric. I tried those programs, and as previously stated in other posts, the bloatware comes back.
I installed AROMA file manager to try and manually find the bloatware and delete the physical files, but I can't find the files that I'm looking to delete. I don't mind taking the time and manually deleting these unnecessary files, but, I need some guidance on where to look (or any other viable solutions.)
Thanks for your time!
Download this patch and edit update-binary file what application need remove then flash via recovery mode .
espmma said:
My device is rooted.
I've read a few other topics regarding this issue, but I'm still confused. As I understand it, using typical uninstall apps such as Titanium or Root Uninstaller do not remove the manufacturer apps from the phone still because of an S feature? I'm new to this process, so please forgive my naive rhetoric. I tried those programs, and as previously stated in other posts, the bloatware comes back.
I installed AROMA file manager to try and manually find the bloatware and delete the physical files, but I can't find the files that I'm looking to delete. I don't mind taking the time and manually deleting these unnecessary files, but, I need some guidance on where to look (or any other viable solutions.)
HTC devices are set "S on" from the manufacture. That means there are certain partitions in the nand storage that you can't access without S off ( boot partition, radio partition). The write permissions to the system partition are also not accessible unless you either obtain S off through the Sunshine app which costs $25 or a another option that is not true S off is a write permission mod called WP.MOD_ko that you flash to your phone and it installs a script and changes your phone's SElinux permissions and enables the system partition write permissions to be able to uninstall system apps or fully use certain root apps like Link2SD that also need the system write permissions at bootup.
1st option " fully" unlocks your phone and all partitions. 2nd option just installs scripts to kind of trick your system partition to allow apps to write to it and you to be able to uninstall system apps. It also changes your SElinux permissions from enforcing to permissive so be aware that's disabling the phone's security system. Not a problem unless you get malware but you should be aware of what any mod does to your phone. They have to do that because the mod can't get the phone to be true S off so this is a workaround for that one partition.
Click to expand...
Click to collapse
Okay cool, thank you for breaking that down for me. So, if I use what pham posted, then that would be a script change? But, even if it were a script change I could still fully uninstall the bloatware, with the risk of a potential virus. Is that correct?
espmma said:
Okay cool, thank you for breaking that down for me. So, if I use what pham posted, then that would be a script change? But, even if it were a script change I could still fully uninstall the bloatware, with the risk of a potential virus. Is that correct?
Click to expand...
Click to collapse
You're welcome. I'm not familiar with what Pham linked you but I'm sure it's similar to the 2nd option I mentioned. The one I was referring to was written for lollipop versions by CaptainTitti I believe is his handle but if you search XDA for our phone WP_MOD.ko that forum should be for kit Kat and a few pages forward is the link to the lollipop version with instructions from CaptainTitti on how to install it. The malware risk is minimal i just wanted to mention it. You have that as well with just rooting and also full S off it's just those 2 leave your SElinux permissions set to enforcing not permissive. Just giving you the info so your informed because no one but us pays for our devices so we should have as much info as possible I believe but good info .
The only one of these I've actually tried is the full S off one with Sunshine so understand and read the whole forum for the other before flashing so you know all the feedback but it does work. Also be aware that the WP_MOD.ko would have to be fully removed and SElinux reenabled to be able to do stock updates and there's not just an " uninstall" box with them. You have to use a root file explorer and remove what was changed and replace with the stock files I believe. Good idea to do a stock Android backup using your custom recovery before flashing any of these, S off excepted as it doesn't mess with doing stock updates. Not knocking the others but these are the things you don't find out about till after you flash them. Now you know before.
Below is the link to the forum page for the kitkat mod and if you scroll down a bit CaptainTiiti had a link to the one for lollipop.
http://forum.xda-developers.com/showthread.php?t=2707378&page=7
Can't you just use Root Browser, then go to system/app & system/priv-app to remove the bloat? That's what I do on my phone everytime I install a new ROM [emoji1]
Stachura5 said:
Can't you just use Root Browser, then go to system/app & system/priv-app to remove the bloat? That's what I do on my phone everytime I install a new ROM [emoji1]
Click to expand...
Click to collapse
I don't know my friend I've never tried that. Maybe he can try it first and see if it works. To be honest I never tried to just remove system apps before i was S off I just read of all the people here on XDA saying they couldn't without S off so I did it. Turns out I switched to debloated CM roms soon after and never even debloated my stock rom, which definitely needed it ! I used Titanium backup to debloat my Samsung tablet after root to get rid of Knox and Samsung junk but it wasn't nand locked like the HTC's are. Can't hurt for him to try it because S off costs and the other mods have their down sides also.
i have completely deleted their bloatware folder, but bloatware will appear if the device boots without root and there is no app folder in user app or system folder but they can run and update normally, maybe it specially designed. Will the above patch zip help me clear the problem completely? i want to clean up the crap, and my device uses system as root so i need to flash modified binary in boot.img separately after signing.
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
Here is a list of bloatware to safely delete. I've tried it on my freshly flashed stock rom. As always, you are responsible for your own phone, I ascertain no responsibility if you mess up. Do this AT YOUR OWN RISK.:cyclops:
The Metro PCS variant has almost 7GB out of 16GB in use out the box (The system uses 5.6GB by itself), mostly with stock phone apps most people hate anyway. However, the XT1765 is an absolute nightmare if you delete the wrong file - and we're talking about the entire rom crashing and burning and at least four hours trying to get out of a catastrophic crash. I know....personal experience, lol.:laugh:
You will have to refer to my other guide on how to delete files with ADB, as Titanium Backup and Root Explorer are not going to cut all the mustard for you. For this method I went mostly ADB, with Titanium for smaller apps.
Things to Know Beforehand:
1. If you try to delete from your File Explorer of choice the device will CRASH/FREEZE on you, meaning, you'll have to take the battery out and reboot. And that doesn't mean the delete went though.
2. You will need root. It's imperative when messing around in the system files.
3. The reason why Titanium Backup is failing this mission is because Motorola/Lenovo decided to put some of these pesky roms in the OEM folder to keep you from easily deleting them as if they were just simple apk's. The OEM folder has its own protections to stop you from, dare I say it, cleaning out the bloat on your phone (see #1).
4. Check and check again to ensure files are gone. Sometimes files will appear to be gone and the folders come back on reboot. I have ZERO clue why that happens, but its annoying.
5. Do NOT delete the camera in favor of a better one. Instant DOA.
6. There is a nice list of Moto G safe to delete list floating around that shares some of the package files. Don't be tempted and delete. I tried them and got a CATASTROPHIC ROM FAILURE that resulted in me having to painstakingly start flashing system sparse files, boot files, and everything else to get the phone back. Couldn't even boot into TWRP. You'll see the Do Not Delete List Below.
Delete List That's Okay:
package:com.nuance.nmc.sihome.metropcs
package:com.privacystar.android.metro
package:com.metropcs.metrozone
package:com.handmark.metro.launcher
package:com.nuance.nmc.sihome.metropcs
package:com.motorola.hotspotlauncher
package:com.motorola.android.fmradio
package:com.motorola.moto
package:com.facebook.system
package:com.facebook.appmanager
packages:com.lookout
package:com.google.android.googlequicksearchbox
package:com.google.android.marvin.talkback
Device Help: /system/priv-app/GuideMe.odex (With Titanium Backup)
Do Not Delete List: (BigUps to @doppelhelix for compiling this for his MotoG)
/system/app/PhaseBeam.apk
/system/app/BasicDreams.odex
/system/app/atfwd.apk
/system/app/atfwd.odex
/system/app/BasicDreams.apk
/system/app/MagicSmokeWallpapers.apk
/system/app/MagicSmokeWallpapers.odex
/system/app/MotGeoFenceSvc.apk
/system/app/PhotoTable.apk
/system/app/PhotoTable.odex
/system/app/VisualizationWallpapers.apk
/system/app/Bug2GoStub.apk
/system/app/VisualizationWallpapers.odex
/system/app/com.qualcomm.location.apk
/system/app/com.motorola.android.settings.diag_mdlog.apk
/system/app/com.motorola.android.settings.diag_mdlog.odex
/system/app/com.qualcomm.location.odex
/system/app/com.qualcomm.services.location.apk
/system/app/LiveWallpapers.apk
/system/app/LiveWallpapers.odex
/system/app/Exchange2.apk
/system/app/3c_main.apk
/system/app/3c_main.odex
/system/app/com.google.android.gm.apk
/system/app/com.motorola.android.nativedropboxagent.apk
/system/app/com.motorola.android.nativedropboxagent.odex
/system/app/MotGeoFenceSvc.odex
/system/priv-app/3c_devicemanagement.apk
/system/priv-app/3c_devicemanagement.odex
/system/priv-app/3c_notification.apk
/system/priv-app/3c_notification.odex
/system/priv-app/3c_ota.apk
/system/priv-app/3c_ota.odex
/system/priv-app/ContextEngineClient.apk
/system/priv-app/DemoMode.apk
/system/priv-app/CQATest.apk
/system/priv-app/DemoMode.odex
/system/priv-app/DeviceAuthApp.apk
/system/priv-app/fswriter.apk
/system/priv-app/fswriter.odex
/system/priv-app/EmaraPhoneExtns.odex
/system/priv-app/LMIRescueSecurity.apk
/system/priv-app/MotAuthService.apk
/system/priv-app/MotAuthService.odex
/system/priv-app/MotoAssist.apk
/system/priv-app/AudioEffects.apk
/system/priv-app/MotoCare.apk
/system/priv-app/MotoCareInt.apk
/system/priv-app/OMAProvisioning.apk
/system/priv-app/EmaraPhoneExtns.apk
/system/priv-app/GuideMe.apk
/system/priv-app/MotCamera.apk
/system/priv-app/MotCamera.odex
/system/priv-app/AudioEffects.odex
/system/priv-app/3c_checkin.apk
/system/priv-app/3c_checkin.odex
/system/priv-app/BodyGuardApp.odex
/system/priv-app/ContextEngineClient.odex
/system/priv-app/DeviceAuthApp.odex
/system/priv-app/MotoAssist.odex
/system/priv-app/MotoCareInt.odex
/system/priv-app/OMAProvisioning.odex
Articul8Madness said:
Here is a list of bloatware to safely delete. I've tried it on my freshly flashed stock rom. As always, you are responsible for your own phone, I ascertain no responsibility if you mess up. Do this AT YOUR OWN RISK.:cyclops:
You will have to refer to my other guide on how to delete files with ADB, as Titanium Backup and Root Explorer are not going to cut all the mustard for you. For this method I went mostly ADB, with Titanium for smaller apps.
Things to Know Beforehand:
1. If you try to delete from your File Explorer of choice the device will CRASH/FREEZE on you, meaning, you'll have to take the battery out and reboot. And that doesn't mean the delete went though.
2. You will need root. It's imperative when messing around in the system files.
*Well I guess you can easily and permanently delete files from twrp advanced file manager*
in case you don't want to bother using a PC or installing titanium .
Click to expand...
Click to collapse
KevMetal said:
Articul8Madness said:
Here is a list of bloatware to safely delete. I've tried it on my freshly flashed stock rom. As always, you are responsible for your own phone, I ascertain no responsibility if you mess up. Do this AT YOUR OWN RISK.:cyclops:
You will have to refer to my other guide on how to delete files with ADB, as Titanium Backup and Root Explorer are not going to cut all the mustard for you. For this method I went mostly ADB, with Titanium for smaller apps.
Things to Know Beforehand:
1. If you try to delete from your File Explorer of choice the device will CRASH/FREEZE on you, meaning, you'll have to take the battery out and reboot. And that doesn't mean the delete went though.
2. You will need root. It's imperative when messing around in the system files.
*Well I guess you can easily and permanently delete files from twrp advanced file manager*
in case you don't want to bother using a PC or installing titanium .
Click to expand...
Click to collapse
Well, the thing is, you can "try" deleting the files from the twrp advanced file manager, but it can cause instabilities in the boot. I tried that as a first line of defense after flashing the stock rom and voila, the boot crashed. I dont exactly know what fugly ugly stuff Motorola has attached to that OEM folder, but any playing around with that outside of ADB results in catastrophic failure.
This XT1765 is something else :laugh:
Click to expand...
Click to collapse
:good:haha okay I hear you ...i have xt1762 mtk which isn't too difficult ....but yeah even then you need to be careful when removing anything with a Motorola name /extension ..I like using recovery cos you can make a backup as you go along ..and if you can't boot system you can just boot back into recovery and restore to last state before crash ... furthermore changes always stick ( for better or worse ) & no need for a PC .
Articul8Madness said:
Do Not Delete List
Click to expand...
Click to collapse
Totally forgot that i that I made such a list. Brings back memories where I was much more active on xda. Thanks for mentioning it
KevMetal said:
:good:haha okay I hear you ...i have xt1762 mtk which isn't too difficult ....but yeah even then you need to be careful when removing anything with a Motorola name /extension ..I like using recovery cos you can make a backup as you go along ..and if you can't boot system you can just boot back into recovery and restore to last state before crash ... furthermore changes always stick ( for better or worse ) & no need for a PC .
Click to expand...
Click to collapse
Be thankful, lol, that you have the Mediatek version. I actually ran into a tizzy deleting bloat from Recovery. Got stuck either on the N/A black screen or if trying to reboot into recovery, the Recovery splash screen! Took 4 hours to get it back, but not before I had to get the very first .xml stock release, special tools to unpack it (winrar just would not do), and then flash first the boot.img, then each one of the sparsechunk files just to get it to run enough to get back to recovery. On the XT1765 they made it harder, or maybe that's a Qualcomm thing, lol. :cyclops::cyclops::cyclops: And get this....all I was trying to do was remove the Moto app. :laugh:
I guess mediatek has some advantages then after all .. .. sounds like a long day in front of the laptop on a Saturday ... imagine the frustration if you didn't actually like playing around with phones :cyclops:
KevMetal said:
I guess mediatek has some advantages then after all .. .. sounds like a long day in front of the laptop on a Saturday ... imagine the frustration if you didn't actually like playing around with phones :cyclops:
Click to expand...
Click to collapse
This isn't about mediatek vs perry as most variants of the latter can be easily modded relative to the apparently pesky XT1765.
Davey126 said:
This isn't about mediatek vs perry as most variants of the latter can be easily modded relative to the apparently pesky XT1765.
Click to expand...
Click to collapse
Mmm true .. I guess the cheaper they offer them the more bloat they feel you should enjoy..or depending the share holders outlook or philosophy on life ..
Flash GAPPS of your choice, though i recommend pico_gapps, it will automatically remove google bloatwares