The Xposed threads for older HDs haven't been updated in months, so I thought I would start a new one for the 2017 HD 10.
Before I begin, the standard disclaimer: This is a risky undertaking. If you encounter issues or, worse, end up with a brick, I (or the others here) will try to help you, but the risk is all yours. Before you start with Xposed, do a dd backup of your SuperSU-rooted /system (with SuperSU in /system) to use as a fallback. Details are below.
Xposed: Follow this guide to install Xposed. As of this writing, v89 works well.
Modules: See the screenshots for the modules I have installed and confirmed working and for the look of the status bar and the navigation bar using GB, FSBI, and Xstana.
Some other apps of choice:
Launcher: Apex (free)
Keyboard: Gboard
Browser: Lightning
File explorer: Root Explorer (only because I got it for free from an old Amz promotion)
Office: OfficeSuite (ditto reason above)
YouTube: OGYouTube
Media: VLC for Fire
Adblocker: AdAway
Backup: Titanium Backup and Backup+
Boot manager: ROM Toolbox Lite and All-In-One Toolbox
VPN: OpenVPN Connect
Update: I have finally been able to get FlashFire working, albeit an older version. I have tested backup/restore extensively (backup and restore of /system and /data) and flashed a few zips with success.
Requirements:
-- Root with SuperSU
-- FlashFire v0.24 or modified v0.51
-- Xposed with Per App Hacking module (to use Time Machine to load time-bombed FF)
-- Low risk aversion
-- Patience
Downloads:
-- Download the Xposed Installer from here. You should be downloading this framework: xposed-v89-sdk22-arm64 (the installer will likely pick it up from here).
-- Search for and download all the Xposed modules (the screenshot below contains the version numbers of the modules I have installed) from the Xposed Installer's Download tab. For modules that aren't in the Xposed repo, do a Google or XDA search. The Per App Hacking module is here.
-- Download FlashFire v0.24 or modified v0.51 from the attachments in this post.
I have now created a custom image (using dd) with SuperSU, Xposed, and FlashFire in /system. After a factory reset or adb sideload, I root with Kingo, dd this custom system.img, and reboot to have a SuperSU-rooted /system with working Xposed. You may have to run each of these apps once and reboot for things to work properly. Finally, install the Per App Hacking module to allow FlashFire to function. I would have loved to put the PAH module in /system as well, but FF doesn't like that.
FlashFire: How to get FF working and use it to backup and restore /system and /data:
-- Install FlashFire but do not open it. You can make it (and anything else) a system app at this point. I used Link2SD (long-press on the app and convert it to a system app), but manually moving it to /system/app or /system/priv-app works just as well. For SuperSU, just choose the option in Settings to make it a system app (this moves SuperSU to /system/app; you can confirm this using a root explorer). Reboot after you convert user apps into system apps.
-- Assuming you have Xposed working, install and activate the Per App Hacking module.
-- Go to the aforementioned module and scroll down to FF. Under Time Machine, choose a date around the time the version was active. For v0.24, I went with late Sept. 2015. The format is (date time): 2015-09-25 12:55.
-- Now start FF. It should open w/o complaints. Under Settings, use the best compression and all the cores.
-- This is not needed if you use FF to backup /system as a raw image, but here's how you use dd (to use as a failsafe in the event of a careless wipe, make sure you copy the backup off the tablet after it's done):
Code:
adb shell
su
dd if=/dev/block/mmcblk0p13 of=/sdcard/system.img
-- If you are happy with your system partition, you can now backup using FF. Choose "raw" backup.
-- Here's where you wait ... and wait ... and wait. I have timed this wait: First, the Fire will reboot to a near-black screen. It will spend about 4 minutes on that screen before a huge Loading sign in the center and a bunch of /system modules being loaded. Next, you will be on a black, but slightly brighter, screen for another 4 minutes, after which you will see the red FF at the top and the backup progress at the bottom. The actual backup should take a minute or so and the Fire will reboot. Your backup should be in /sdcard/FlashFire/Backups/. Open system.gz in 7-Zip and extract system. Save it as system.img (file extension optional).
-- To backup /data, choose Normal backup in FF, check the data partition, and repeat the rest of the steps in FF (above).
-- You can chain actions in FF. For example, you can backup /system as Raw and /data as Normal in one shot, saving you an eight-minute wait.
-- After a factory reset (or if root is lost), use (offline) Kingo to root as usual (do not reboot), but don't jump through hoops to install SuperSU. Use dd to write back the saved system img (assuming it's in /sdcard):
Code:
adb shell
su
mount -w -o remount /system
dd if=/sdcard/system.img of=/dev/block/mmcblk0p13; sync
Note: Doing a live dump onto a mounted partition is risky. The above process is meant to save a few minutes. If you have time to burn, use FlashFire to restore /system. Using the steps in "FlashFire w/o Xposed," this will be even quicker.
Wait a few minutes and reboot. (If your Fire reboots before this is done, you will be stuck at the Fire logo, but adb shell and su will still be available. Repeat the dd and it should work this time. I have noticed that the likelihood of reboot during dd is (much) greater when moving from one version of FireOS to another.)
-- After confirming SuperSU is working as expected (change the default access to Grant), uninstall the Kingo junk.
-- Finally, restore the data partition using FF, but before you do so, install Per App Hacking and tweak it to get FF working.
FlashFire w/o Xposed: If you only care about FlashFire and don't want Xposed, here's a quick-and-dirty non-Xposed way to get FlashFire working (say, after an adb sideload and SuperSU): Change the date using busybox:
Code:
busybox date -s "201509221745"
Changing the system date has implications beyond FF, so this is just a quick fix to get FF working to do a restore, after which you should look to PAH as the permanent solution.
Given the risk of data corruption when dding back a system.img into a mounted /system, here's my recommended approach:
-- adb sideload update.bin
-- Root with (offline) Kingo
-- Install SuperSU v2.79
-- Get FF working with backdating using busybox
-- Use FF to restore /system and /data from backup
I like to use swype for keyboard. I use a version 1.8 from oppo which has a bult in voice key that activates google voice input, instead of dragon. it just seems to read my mind much better than gboard, or swiftkey.
For launcher, i use nova.
for browser i use chrome, just because it has all my passwords and history from my desktops and laptops.
for youtube, i use iYTPB Vanced version. I used to mess around with OG Youtube but it wasn't nearly as functional for me; maybe it's gotten much better over the years. I install regular youtube, login, then rename the modded youtube to iYTPB and replace the base.apk for youtube. It stays logged in. The main thing it does is get rid of ads and unlimited resolution on mobile
edit: what does a boot manager do?
mistermojorizin said:
what does a boot manager do?
Click to expand...
Click to collapse
Prevents apps from running automatically at boot. You can also prevent apps from autorunning even after boot. This is a safer alternative (relative to wholesale uninstall).
ETA: See the updated OP for FlashFire-related information.
retyre said:
Prevents apps from running automatically at boot. You can also prevent apps from autorunning even after boot. This is a safer alternative (relative to wholesale uninstall).
To answer my question in the OP, I have finally been able to get FlashFire working, albeit an older version. Can't do much more than backup/restore at this point, but that's all I need (backup and restore of /system and /data). It has trouble restoring /system (presumably because FF starts by loading a minimal /system), but I just use good old dd to live-restore system.img.
Requirements:
-- Root with SuperSU
-- FlashFire v0.24
-- Xposed with Per App Hacking module (to use Time Machine to load time-bombed FF)
-- Low risk aversion
-- Patience
I have now created a custom image (using dd) with SuperSU, Xposed, FlashFire, and AdAway in /system. After a factory reset or adb sideload, I root with Kingo, dd this custom system.img, and reboot to have a SuperSU-rooted /system with working Xposed. Each of these apps has to be run once and rebooted for everything to work properly. Finally, install the Per App Hacking module to allow FF v0.24 to function. I would have loved to put the PAH module in /system as well, but FF doesn't like that.
Click to expand...
Click to collapse
this is very interesting! Nice work! Let me know if i got this right:
get flashfire working with Per App Hacking, make a backup of /data
make SuperSu, Xposed App, AdAway, and FlashFire system apps
created a custom image (using dd) with SuperSU, Xposed, FlashFire, and AdAway in /system
root with Kingo
dd this custom system.img and reboot
run SuperSu and reboot
run Xposed (app) and reboot
run FlashFire and reboot
run AdAway and reboot
install Per App Hacking module to make FF function
restore /data with flashfire
Now come the stupid questions. I've tried researching this but couldn't figure these parts out.
In step 1, how do you use PAH to get FF working? How do you backup /data from inside FF? (I see the guide for installing xposed, so that's a given, but then what?) Do you also backup system.img with FF? Do you backup /data as an .img? Also, which version xposed do you use? in the guide it says use v87 but v89 is the current version.
In step 2, how do you check if SuperSu is properly installed as a system app? (I had run "make supersu a system app" when I rooted, but I don't know if it actually worked. I was just happy to get permanent root.) If SuperSu is not a system app, what's the best way to do it? Use the option from within SuperSu or move the apk to /syste/app and set proper permissions?
In step 3, I don't know how to do that. I researched "dd" and I know it's an adb command. But how do you use it specifically make a live-restore system.img?
In step 4, do you mean run the kingo from the PC and get the "temp root" without rebooting (the state right after we root with kingo but if we reboot without doing anything else, the root is lost)?
In step 5, same question as step 3 - how do you specifically do it?
In step 11, how do you restore /data with flashfire
sorry for all these questions, just want to make sure I am doing it exactly how you did it.
mistermojorizin said:
Let me know if i got this right:
Click to expand...
Click to collapse
Snipped a lot of your post, but here are the answers:
-- Do 2. and 3. first. If you make a backup of /data with the four apps and then make them system apps, you will have duplicates (one in the data backup and one in your system img).
ETA: Most of the FlashFire-related information that used to be here is now in the updated OP.
retyre said:
Snipped a lot of your post, but here are the answers:
-- Do 2. and 3. first. If you make a backup of /data with the four apps and then make them system apps, you will have duplicates (one in the data backup and one in your system img). But before you do that, you need to get FF working:
Click to expand...
Click to collapse
I tried installing xposed using the steps from your post here: https://forum.xda-developers.com/showpost.php?p=74913548&postcount=160
now I am in a bootloop. it goes fire, optimizing apps, then loads walpaper and sometimes lockscreen, then reboots back to the fire logo. I use adb shell, su, mount system writeable, rm app_process64_xposed, says file not found (which makes sense because i made sure to delete it from system/bin before rebooting). What should I try?
mistermojorizin said:
I tried installing xposed using the steps from your post here: https://forum.xda-developers.com/showpost.php?p=74913548&postcount=160
now I am in a bootloop. it goes fire, optimizing apps, then loads walpaper and sometimes lockscreen, then reboots back to the fire logo. I use adb shell, su, mount system writeable, rm app_process64_xposed, says file not found (which makes sense because i made sure to delete it from system/bin before rebooting). What should I try?
Click to expand...
Click to collapse
Try this first. If that doesn't work, then this (not in TWRP obviously, but in a root shell from adb).
If SuperSU was working before you installed Xposed, you should be able to get to a root shell from adb, delete the xposed installer from /data/app and /data/data, and reboot.
Did you follow the steps to the letter?
retyre said:
Try this first. If that doesn't work, then this (not in TWRP obviously, but in a root shell from adb).
If SuperSU was working before you installed Xposed, you should be able to get to a root shell from adb, delete the xposed installer from /data/app and /data/data, and reboot.
Did you follow the steps to the letter?
Click to expand...
Click to collapse
yes pretty sure i followed the directions closely. here's what I did: installed xposed installer, selected install arm64-v89, deleted process_64, reboot. it optimized files for a while then went into this bootloop
i created a blank file from adb shell root system rw /data/data/de.robv.android.xposed.installer/conf/disabled and then used the ls command to make sure it is indeed in there. I changed the xposed installer in data/app and data/data to .bak rather than deleting altogether. still not working
mistermojorizin said:
yes pretty sure i followed the directions closely. here's what I did: installed xposed installer, selected install arm64-v89, deleted process_64, reboot. it optimized files for a while then went into this bootloop
i created a blank file from adb shell root system rw /data/data/de.robv.android.xposed.installer/conf/disabled and then used the ls command to make sure it is indeed in there. I changed the xposed installer in data/app and data/data to .bak rather than deleting altogether. still not working
Click to expand...
Click to collapse
See whether wiping the cache partition in recovery and rebooting helps. And /data/dalvik-cache/ from a root shell.
retyre said:
See whether wiping the cache partition in recovery and rebooting helps.
Click to expand...
Click to collapse
i tried that and it didn't help, so i wiped dalvik cache from adb
rm -r /data/dalvik-cache
rm -r /cache/dalvik-cache
took 10 minutes to boot, but didn't work, same behavior
mistermojorizin said:
i tried that and it didn't help, so i wiped dalvik cache from adb
rm -r /data/dalvik-cache
rm -r /cache/dalvik-cache
took 10 minutes to boot, but didn't work, same behavior
Click to expand...
Click to collapse
I think we have tried the usual Xposed-bootloop troubleshooting tips. Before you do adb sideload (w/o a factory reset), can you think of anything else you may have done to /system after your last working reboot? In particular, anything SuperSU-related?
no i didn't touch supersu, and i don't think i did anything with system either. is there any way to boot into safemode? also will sideloading 5.6 without factory reset get rid of root?
edit: it's so frustrating, it'll sometimes load the lockscreen and systemui, and even started nova launcher and i saw my homescreen. but it soft-reboots so quickly it seems like.
mistermojorizin said:
no i didn't touch supersu, and i don't think i did anything with system either. is there any way to boot into safemode? also will sideloading 5.6 without factory reset get rid of root?
edit: it's so frustrating, it'll sometimes load the lockscreen and systemui, and even started nova launcher and i saw my homescreen. but it soft-reboots so quickly it seems like.
Click to expand...
Click to collapse
Earlier Kindles had a safe mode (power + vol down), but I don't think ours does. Yes, sideloading update .bin will clean /system, thus removing root.
Putting the "disabled" file in /data/data/de.robv.android.xposed.installer/conf/ disables Xposed, so I doubt your current issue is Xposed-related (it may have been caused by the Xposed install, though).
Did you uninstall any system apps (or convert user apps like your launcher to system apps) after your last successful boot?
retyre said:
Earlier Kindles had a safe mode (power + vol down), but I don't think ours does. Yes, sideloading update .bin will clean /system, thus removing root.
Putting the "disabled" file in /data/data/de.robv.android.xposed.installer/conf/ disables Xposed, so I doubt your current issue is Xposed-related (it may have been caused by the Xposed install, though).
Did you uninstall any system apps (or convert user apps like your launcher to system apps) after your last successful boot?
Click to expand...
Click to collapse
no not since the last successful boot. i tried disabling a few root apps through adb, and then gave up and am doing the sideload. i've done this a ton of times the other day when i was trying to root. but now...it's stuck at 64% and in the screen says "patching system unconditionally'. It's been stuck for 5 minutes. I don't think this is normal, though i've never watched the whole process before.
Edit:it got through it and the %age is increasing at a reasonable pace now.
mistermojorizin said:
Edit:it got through it and the %age is increasing at a reasonable pace now.
Click to expand...
Click to collapse
After you root with SuperSU and set everything up, but before you try Xposed again (if you're not ready to give up yet!), do a dd dump of your system partition to use in the event of a boot loop.
retyre said:
Snipped a lot of your post, but here are the answers:
-- Do 2. and 3. first. If you make a backup of /data with the four apps and then make them system apps, you will have duplicates (one in the data backup and one in your system img). But before you do that, you need to get FF working:
-- Install FF v0.24 but do not open it. You can make it a system app at this point. I used Link2SD (right-click on the app and convert it to a system app), but moving it to /system/app or /system/priv-app works just as well. For SuperSU, just choose the option in Settings to make it a system app (this moves SuperSU to /system/app; you can check it using a root explorer). Reboot after you convert user apps into system apps.
-- Assuming you have Xposed working (v89 works fine), install and activate the Per App Hacking module.
-- Go to the aforementioned module and scroll down to FF. Under Time Machine, choose a date right after v0.24 was released (but before v0.26 just to be safe). I went with late Sept. 2015. The format is (date time): 2015-09-25 12:55.
-- Now start FF. It should open w/o complaints. Under Settings, use the best compression and all the cores.
-- This is not needed if you use FF to backup /system as a raw image, but here's how you use dd (make sure you copy the backup off the tablet after it's done):
Code:
adb shell
su
dd if=/dev/block/mmcblk0p13 of=/sdcard/system.img
-- If you are happy with your system partition, you can now backup using FF. Choose "raw" backup.
-- Here's where you wait ... and wait ... and wait. I have timed this (I know what you're thinking!): First, the Fire will reboot to a near-black screen. It will spend about 4 minutes on that screen before a huge Loading sign in the center and a bunch of /system modules being loaded. Next, you will be on a black, but slightly brighter, screen for another 4 minutes, after which you will see the red FF logo at the top and backup progress at the bottom. The actual backup should take a minute or so and the Fire will reboot. Your backup should be in /sdcard/FlashFire/Backups/. Open system.gz in 7-Zip and extract system. Save it as system.img (file extension optional).
-- To backup /data, choose Normal backup in FF, check the data partition, and repeat the rest of the steps in FF (above). FF does not give you the option to backup /data as a raw image (thankfully, so you're not left with a 20G backup because /sdcard is in /data).
-- After a factory reset (or if root is lost), use the Kingo PC app and root as usual (do not reboot), but don't jump through hoops to install SuperSU. Use dd to write back the saved system img (assuming it's in /sdcard):
Code:
adb shell
su
mount -w -o remount /system
dd if=/sdcard/system.img of=/dev/block/mmcblk0p13; sync
Wait a few minutes and reboot. (If your Fire reboots before this is done, you will be stuck at the Fire logo, but adb shell and su will still be available. Repeat the dd and it should work this time.)
-- After confirming SuperSU is working as expected (change the default access to Grant), uninstall the Kingo junk.
-- Finally, restore the data partition using FF, but before you do so, install Per App Hacking and tweak it to get FF working.
Click to expand...
Click to collapse
So I'm back up and running. I made a dd backup .
I got xposed going and I used time-machine for FF. Opened FF and hit the plus sign under actions, and selected only the data partition. It's been stuck on the fire splash screen for about 17 minutes now. Is that normal? I know you mentioned the raw system backup takes forever, but I thought data would go quicker, and I didn't expect it to spend all its time on the splashscreen.
edit: i force reboot after like 35mins of the boot screen. was glad to see that it reboot normally just fine. so i decided to try the raw system backup (by the way, in there it had system and boot prechecked, I unchecked boot - is that OK?). So I was expecting it to reboot to a blank screen as you mentioned, but nope, its just sitting at the "fire" boot screen again. I can get into ADB shell.
edit 2: i installed the wrong version of flashfire. gonna try again.
edit 3: 0.24 did the same thing
edit 4: changed FF to a user app, and now it seems to be working on backing up data partition (at least it's giving me a black screen instead of that boot logo). But to do system, i will need to move it to system. I've been using link2sd and it puts it in priv-app. maybe it should just be in system/app? It's working for you to backup system as a system app? Is it in priv-app?
mistermojorizin said:
So I'm back up and running. I made a dd backup .
I got xposed going and I used time-machine for FF. Opened FF and hit the plus sign under actions, and selected only the data partition. It's been stuck on the fire splash screen for about 17 minutes now. Is that normal? I know you mentioned the raw system backup takes forever, but I thought data would go quicker, and I didn't expect it to spend all its time on the splashscreen.
edit: i force reboot after like 35mins of the boot screen. was glad to see that it reboot normally just fine. so i decided to try the raw system backup (by the way, in there it had system and boot prechecked, I unchecked boot - is that OK?). So I was expecting it to reboot to a blank screen as you mentioned, but nope, its just sitting at the "fire" boot screen again. I can get into ADB shell.
edit 2: i installed the wrong version of flashfire. gonna try again.
edit 3: 0.24 did the same thing
edit 4: changed FF to a user app, and now it seems to be working on backing up data partition (at least it's giving me a black screen instead of that boot logo). But to do system, i will need to move it to system. I've been using link2sd and it puts it in priv-app. maybe it should just be in system/app? It's working for you to backup system as a system app? Is it in priv-app?
Click to expand...
Click to collapse
Changing FF to user vs. system app should have no bearing on being able to backup /system as a raw image. I use it as a system app (in /system/priv-app) and it works fine. Did the /data backup complete? What's the size of the .gz file in /sdcard/FlashFire/Backups/**/? Which backup option are you choosing and which partitions are you checking in there?
Read my section about FF starting up (and how many minutes each step should take). Look carefully at the screen and tell me whether you see the "two stages of black." The first black should be darker than the second, and there should be a bunch of scrolling text (this will only last a second or two, so you will have to stare at your screen like your life depends on it) between the two stages. If you don't see the red FlashFire at the top in 8-10 minutes, something's gone wrong. In general, it would be a good idea to keep an eye on the Fire's screen for the entire 10 minutes after you click Flash in FF and press OK.
retyre said:
Changing FF to user vs. system app should have no bearing on being able to backup /system as a raw image. I use it as a system app (in /system/priv-app) and it works fine. Did the /data backup complete? What's the size of the .gz file in /sdcard/FlashFire/Backups/**/? Which backup option are you choosing and which partitions are you checking in there?
Read my section about FF starting up (and how many minutes each step should take). Look carefully at the screen and tell me whether you see the "two stages of black." The first black should be darker than the second, and there should be a bunch of scrolling text (this will only last a second or two, so you will have to stare at your screen like your life depends on it) between the two stages. If you don't see the red FlashFire at the top in 8-10 minutes, something's gone wrong. In general, it would be a good idea to keep an eye on the Fire's screen for the entire 10 minutes after you click Flash in FF and press OK.
Click to expand...
Click to collapse
I ended up getting it to work. Had to uninstall, reinstall, change to user app again and everything worked. Don't know why it didn't work before. I appreciate all of your help. when doing the raw system backup, i only checked "system" and unchecked "boot". That sound right?
One thing I've been wondering about is why the arm64 version of xposed works on this devices. It does have a arm64 cpu, but it's instruction set is armv7 only, and from what i can tell, all of the apps it runs are not arm64 versions.
mistermojorizin said:
... when doing the raw system backup, i only checked "system" and unchecked "boot". That sound right?
One thing I've been wondering about is why the arm64 version of xposed works on this devices. It does have a arm64 cpu, but it's instruction set is armv7 only, and from what i can tell, all of the apps it runs are not arm64 versions.
Click to expand...
Click to collapse
Yes. You can check all the partitions just for completeness (esp. boot and recovery), but there's not much we can do with them at this time (other than for debricking; better to use dd with those images).
Yes, I noticed that as well. After trying the arm version, I realized the Xposed Installer cares more about the CPU architecture than the instruction set.
So, you never got FF to work as a system app? If it does, the only app to install after a dd restore will be PAH.
Were all the partitions backed up properly?
retyre said:
...
To answer my question in the OP, I have finally been able to get FlashFire working, albeit an older version. Can't do much more than backup/restore at this point, but that's all I need (backup and restore of /system and /data). It has trouble restoring /system (presumably because FF starts by loading a minimal /system), but I just use good old dd to live-restore system.img.
Requirements:
-- Root with SuperSU
-- FlashFire v0.24
-- Xposed with Per App Hacking module (to use Time Machine to load time-bombed FF)
-- Low risk aversion
-- Patience
Click to expand...
Click to collapse
May I inquire why you were using FF v0.24 ? What's wrong with the newer FF versions? Do they not work?
retyre said:
I have now created a custom image (using dd) with SuperSU, Xposed, FlashFire, and AdAway in /system. After a factory reset or adb sideload, I root with Kingo, dd this custom system.img, and reboot to have a SuperSU-rooted /system with working Xposed. Each of these apps has to be run once and rebooted for everything to work properly. Finally, install the Per App Hacking module to allow FF v0.24 to function. I would have loved to put the PAH module in /system as well, but FF doesn't like that.
Click to expand...
Click to collapse
What's the reason to save an img for /system, instead of just reloading everything upon getting root?
P.S. Wanted to add on the subject of Xposed. My must have Xposed modules are App Settings v1.13 (to make Chrome tabs behave like on a cell phone, instead of taking an extra line - link), GravityBox (to make status bar display notifications in colors, and up/down network traffic), and the module with a yellow smiley face (kind of like Walmart's)
Related
Latest end-user Omnirom 4.4.2 for the LG P500 can be found here:
http://jenkins.androidarmv6.org/job.../archive/omni-4.4.2-20140214-p500-NIGHTLY.zip
I am starting this to stimulate interest in the Omnirom, get/give advice and help on how to get it working on our device. My hope is that one of the devs would take this over and move from a discussion to a dev thread if need be. I can really offer no help at this point as I have not yet gotten this installed and running.
Another reason to start this is to keep from less than courtiously cluttering other threads with this stuff.
Finally, cm-11 for our device is quite problematic so I seek another Kitkat chocolate treat
==================================
Omni has two big problems holding up a working install on our device:
1. Omni is not rooted by default. I tried flashing a superuser.zip, still had no root. I have copied a full cm-11 su (binary) to the zip, tried that but installation was aborted for other reasons so could not yet test this approach. Please, devs, give us normal root in this ROM. Not so useful without it.
2. No adb until boot completed and I approve it. Great idea for security, but this thing is still experimental. So I cannot ride herd on the installation as I am accustomed nor run a certain script that I need from later cm10.* and cm11. As it turns out, Omni will run the script, cm11 would not. However, once I have attempted an Omni boot, I cannot get adb back outside of that successful boot until I restore another ROM! Means no adb reboot, adb reboot recovery, nada. Makes things very very problematic.
Omni will run my /data/local/userinit.d/ scripts which recent cm10.* and cm11 refuse. I always ran ICS this way, and I could presumably get a complete startup sans boot this way. To try this next--caution: Kitkat Link2sd mount script is not identical to previous ones so this must be placed to try this. Using the older version (maybe newer one as well!), everything simply FCs out, get nowhere. Link2sd needs root the create the script normally, Xposed needs root to get going, and Titanium and other tools are more useful with root as well. Lack of root is the main problem right now. Please ...
==========================
The usual disclaimer: If you have rooted your device, the warantee is void. Of course, for this oldie but goodie, that is just a distant memory. However, these phones are still being sold so if you got a new one, be warned.
I can not be responsible for brickage and breakage. Especially without that always active adb umbillical, it is much easier to soft-brick the device and it can get hairy-scarey getting back to recovery. Again, be warned.
The recent JB and KitKat ROMs are too large for our devices and must be trimmed before installation. My philosophy is that anything not needed to get Android up and running does not belong on system. Practically, anything installable from Play or side-loadable as user apps should be removed from system/app. Examples are Calendar (install Play version), calculator, camera/gallery, browsers, emailers and such. There are superior choices on Play or side-load those included with the ROM. If using Google Search, also remove the quicksearchbox. system/usr/srec, system speech recognition config, can be pushed to sdext and symlinked from there, freeing a good few meg. You do not need a lot but do need a few meg free on system.
Link2sd or equivalant is needed to keep data space available. Things get flakey when data space gets too low. Gluttonous apps like the newer Swype and Tapatalk (just a few examples--great apps, do not get me wrong) will very quickly run you out of data space and gobble up too much RAM as well, slowing the works. Choose wisely
So here is my next trial:
BACKUP!
Make sure no old 11link2sd script is on /data/local/userinit.d/
Wiped dalvik-cache, restored the sdext from the backup since the CWM seems to wipe this as well.
Wiped cache partition (actually, no longer used for very much!).
Installed the omni nightly which formats /system and proceeds.
Installed the minimal GAPPSlight.zip.
Reboot.
Came up just fine. First asks to enable adb for this computer, said "yes," "always for this computer."
Adb now active and adb, in any event, adb does have root!
Went to link2sd. Cannot get root. Went through all the setup options (including root for apps and abd!). Still not root.
So copied a new 11link2sd to /data/local/userinit.d/
Power menu advanced reboot active in setting and it actually works, avoiding above-mentioned fears
Rebooted.
Bootup runs all my scripts so now have all the link2sd-linked apps.
I could call this a BUG: It neither re-asks the adb question nor places it online. So ... no more abd
Still no root -- tried to activate exposed which without root will not do anything.
Rebooted anyway.
Came up just fine, as before. No root, no Xposed, Still no abd.
Comments:
Otherwise, works just fine, seems responsive. If I were willing to live without root, I could go on with it as a daily driver. Next trial, I will not check "always for this computer." Maybe then it will re-ask me and so re-enable abd.
Shares with cm-11 the flash of a disabled homescreen before the lockscreen. Harmless (as long as it is very brief).
Shares with cm-11 the "upgrading ... restarting apps ..." message on each reboot. Harmless, as long as linked apps, dexes are not being unlinked. Did not check, but cm-11 was no longer do that with the newest link2sd version.
The screen begins to turn off much more quickly. In cm-11, this took a good few minutes, eating the battery as it went.
Background processes came up more quickly (subjective) than cm-11, even though some lacked root to function correctly.
Did not really check if it shares the dissappearing data space problem which for many is a showstopper in cm-11. Initial space seemed appropriate, not half of expected amount. Without adb, can be checked using the SLW storage widget. I should really have done this.
Root remains the main problem with this. Neither flashing a superuser nor placing a full cm-11 su on the ROM enable root. Someone know how?
Attempts at getting root:
The recommended way is to flash SuperSU's zip (available from their XDA thread, surprisingly, not from Play). Since flashing this has twice bricked me up, I am loath to try that once more.
First attempt was the create an init.d type script to start the su daemon. I had placed a Cm-11 su on the ROM's zip before flashing. Voile, manually running that script from adb got me root. The command on adb shell hung up but it had run. Link2sd made its mount script (of which I have my own copy so whatever ...), even accepting the previous approval!
So I placed it on /data/local/userinit.d/ with all my others. On reboot, daemon was indeed running. Tried to activate Xposed. Attempts hung up, then failed. Running superuser (installed from Play as user app, symlinked) would FC. Noticed that I had multiple incidences of the su running which might be indicative of something!
So went back to recovery, removed my script, and flashed the CMW superuser.zip. On reboot, daemon was running. However, any attempt to use superuser FC'd. Removed the apk from system/app, rebooted to regain use of my installed version. Same result.
This issue of root needs be properly resolved to use this ROM.
So back to recovery and cm-10.2 which meanwhile may well be the optimal ROM for this device!
BTW: If the always for this computer was not checked on giving adb permission, after reboot and after a while, the question will be re-asked and one can get adb once again which is good new, though a bit less convenient.
This omni ROM from my humble opinion is quite bizarre and funny. What's really the intention to release ROM that need rooted device to install it (need recovery so first device must be rooted), but then rooted apps didn't work since no SU installed .
Sorry omni devs and anyone. No offence. Just express my opinion.
I tried Superuser.apk and SU from xda but failed.
Sent from my Optimus One using xda app-developers app
Some things I'd like to ask/share
1. My play store isn't working. I've trimmed the ROM n installed gapps too n installed play services too. Bt when i open play store, it works fine. But i can only see spinner loading under 'My Apps' n when I install any app, it gives fc. Then i have to clear data to open it again. What to do? Is it something to do with dpi? Because I've changed the dpi.
2. How to change tiles? I can't get its settings.
3. Any other int2ext script working?
4. Screen record has a very low fps and after recording, the phone becomes unusable. Have to restart
5. I found this ROM more snappy than any other CM11. Thanks to performance controls. Its awesome!
6. Only if root worked, this would be the BEST KitKat ROM for our phone.
(I'm trying to fix it too)
This ROM can be used aa a daily driver if u don't use much apps and root isn't a big issue. Great work
:thumbup:
EDIT:
Link for root in Omni ROM:
http://forum.xda-developers.com/showpost.php?p=50863602
Sent from my LG-P500 using XDA Premium 4 mobile app
Tried again to get root:
I can, in adb shell, su --daemon.
This gets me root for this session. Link2sd will create its mount script!
Rebooted. Thought that the root could be magically persistent as someone posted on some thread somewhere (did a lot of searching! and there were two instances the last time when I used a init.d script to do this). It was not so did su --daemon. Tried to use Xposed. Chugged a while, permission denied. CWM superuser's UI does not work on cm-11, not on this either. But it did not FC!
So I adb pushed SuperSU to system (I have enough room!). It wanted to install its binary. So I rebooted into recovery and flashed that.
On reboot, the su daemon was indeed running It has an 'R' instead of an 'S' on the column before its name. SuperSU also had a process running so thought hey, OK (and it did not brick the phone this time!). Tried to run Xposed. Simply sat there. Tried to run SuperSU, said it needed its binary and could not install it. Yuk! Never did like this app. On cm-10.2, even if CWM superuser wants a new binary, its UI will work anyway. Tried to run that. FC this time.
I never did check free data space.This after several successful reboots with no alarms about it. Overlayed the SLW widget onto link2sd and ran it. Only had 20meg. Fact is I had never ran link2sd to clean up dalvik and such so tried it now. Relink all apps simply chugged along. This can take time, even if it reports nothing to do! Finally lost patience with it but could not kill link2sd with back key (My fault? Options do not take effect until setting run, even if they were checked, it seems). Have to consider the possibility that the "disappearing data space" bug may be in this ROM as well as cm-11 (which, if so, would place it in the AOSP code!). No real way to check it without working root so everything plays.
Rebooted recovery, back to cm-10.2. BTW: the su daemon here has the 'S'.
rhar**** said:
Some things I'd like to ask/share
1. My play store isn't working. I've trimmed the ROM n installed gapps too n installed play services too. Bt when i open play store, it works fine. But i can only see spinner loading under 'My Apps' n when I install any app, it gives fc. Then i have to clear data to open it again. What to do? Is it something to do with dpi? Because I've changed the dpi.
Click to expand...
Click to collapse
Don't know. I only change DPI using Xposed which has not been enabled yet
2. How to change tiles? I can't get its settings.
Click to expand...
Click to collapse
I assume you mean those on the right-side pulldown. Have not found the interface either. Toggle to get that and enough of them are there.
3. Any other int2ext script working?
Click to expand...
Click to collapse
Need root. I did get link2sd to create it mount script after su --daemon.
4. Screen record has a very low fps and after recording, the phone becomes unusable. Have to restart
Click to expand...
Click to collapse
Never tried it. May also be DPI related?
5. I found this ROM more snappy than any other CM11. Thanks to performance controls. Its awesome!
6. Only if root worked, this would be the BEST KitKat ROM for our phone.
(I'm trying to fix it too)
This ROM can be used aa a daily driver if u don't use much apps and root isn't a big issue. Great work
:thumbup:
Click to expand...
Click to collapse
Yeah. Since I can get link2sd mounts either by running the daemon once or placing my copy, I have all my apps available (root ones will not be very happy). I used Xposed and need one round of root for this but that, as opposed to link2sd, did not work.
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+.
Sent from my LG-P509 using Tapatalk 2
ibub said:
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Is that su in /system/xbin is binary command to get root access on system file? You must run this command in terminal. However, Terminal.apk only can be launched if SU.apk or Superuser.apk present in /system/app.
So, in my opinion SU or Superuser is needed to run rooted apps (such as TB, Link2SD). Maybe Busybox is required too?
Sent from my Optimus One using xda app-developers app
ibub said:
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+. :confused
Click to expand...
Click to collapse
System/xbin/su is the binary. One included on the ROM is tiny, barebones (no root). I replaced it with one from cm-11. When it is working right, I believe this gives you the dialog: Allow-Deny, Now-10min-always and such. It also has a daemon mode which services root access. I have not gotten the dialog on the Omni after manually starting the daemon.
That daemon needs be started early-on. Even an init.d script may not be good enough (Omni has real init.d capability as opposed to cm-11!). There is a "persistant-root" item in cm-11's build.prop. Maybe this will work here too the with cm-11 binary?
The apk is a user installable app (or gets placed on system by flashing zip). This gives access to the application-by-application permissions granted or denied in the above dialog, enabling changing them. SuperSU offers the most alternatives but is the most ticklish. CWM superuser is simpler, less finicky but seems not to work on 4.4.*. This is part of the problem. On cm-11, I have root, have the above dialog, superuser does not FC but no UI. On the Omni, since root was achieve manually after-the-boot, more problematic.
There are other apks around, superuser-elite, paid versions, etc. They are not exclusive--I had three of them around until I removed them and kept CWM. Any one of them good on cm-11? Should!!! work here too, he-he. The apk is not necessary to service root (i.e. mine is link2sd-symlinked and before link2sd gets its root, no mount script so no app seen).
xu3sno said:
Is that su in /system/xbin is binary command to get root access on system file? You must run this command in terminal. However, Terminal.apk only can be launched if SU.apk or Superuser.apk present in /system/app.
So, in my opinion SU or Superuser is needed to run rooted apps (such as TB, Link2SD). Maybe Busybox is required too?
Click to expand...
Click to collapse
Busybox is there, we do not have gnutls like normal distros--most everything goes through included busybox.
Terminal will work without the apk on /system/app. Cannot judge from the Omni because of no or incorrect root
I just learned a new set of tricks.
[email protected]:/ $ su -h
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
[email protected]:/ $
Sent from my LG-P509 using Tapatalk 2
ibub said:
I just learned a new set of tricks.
[email protected]:/ $ su -h
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
Click to expand...
Click to collapse
Yes, this simply a root version of sh. The one on this ROM probably will not allow anything.
The one from cm-11 will check permissions, give the dialog to ask if root working correctly.
Latest build omni-4.4.2-20140227 is up, triggered by androidmeda :good:
http://jenkins.androidarmv6.org/job/omni/4/
Download here:
http://jenkins.androidarmv6.org/job/omni/4/artifact/archive/omni-4.4.2-20140227-p500-NIGHTLY.zip
Will try is that SU or Superuser included
EDIT:
Just flashed it with clean install.
1. System reboot took under 3 minutes :good:
2. su binary exist at /system/xbin but not link to busybox binary which is present also at /system/xbin.
3. Installed Terminal.apk, it works but denied to run su command line
4. Installed Root Explorer.apk, works fine but failed to access root, such to change permission R/W of /system folder.
5. Referring to 3 and 4, apps need root access failed to work.
6. Tried to install SuperSU flashable zip, it replaced su binary from stock and it caused apps which is need root access (in my case gooim manager, root explorer, and Link2SD) not responded and apps're getting hang
7. Installed Superuser, launched it, works but need su binary.
Do we need latest SuperSU or Superuser, hence su binary is compatible with Android 4.4.2 ?. The installed one is for Android 2 and 3.
xu3sno said:
Latest build omni-4.4.2-20140227 is up, triggered by androidmeda :good:
http://jenkins.androidarmv6.org/job/omni/4/
Download here:
http://jenkins.androidarmv6.org/job/omni/4/artifact/archive/omni-4.4.2-20140227-p500-NIGHTLY.zip
Click to expand...
Click to collapse
Do not know what has changed. There have been kernel merges, etc.
***
2. su binary exist at /system/xbin but not link to busybox binary which is present also at /system/xbin.
3. Installed Terminal.apk, it works but denied to run su command line
***
Click to expand...
Click to collapse
The /system/xbin/su included with this ROM is for no-root access allowed. A blocker.
I placed the su from a cm-11 ROM. This can run its daemon and get root access. Works for link2sd but nothing else (i.e. Xposed), apparently. According to some googled posts, that daemon must be started very early on (as I stated before). I had it in an init.d script. Started but had same negative results. May try the persist.sys.root_access=1 flag in build.prop. Maybe the internally buried code in boot.img will start the daemon as requested here (if it was not removed). There is no explicit script in the cm-11 ROMs to start that daemon.
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
rhar**** said:
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
Click to expand...
Click to collapse
Okay. Waiting for edited omni ROM (SuperSU included ?), as you did with cm-10.1.5-KITKAT-Update_3 :good:
Wish you luck
Sent from my SM-T311 using xda app-developers app
rhar**** said:
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
Click to expand...
Click to collapse
Great. SuperSU itself is problematic but will suffer with it if it works. Would prefer generic like other ROMs.
Anyway, as in my OP, I would be looking for a dev to take this thread over as a dev thread (or open one).
Another OMNI build
Another Omni build is released @ Jenkins, triggered by Androidmeda.Can d'load it from : http://jenkins.androidarmv6.org/view/All/job/omni-experimental/12/
sumansur2008 said:
Another Omni build is released @ Jenkins, triggered by Androidmeda.Can d'load it from : http://jenkins.androidarmv6.org/view/All/job/omni-experimental/12/
Click to expand...
Click to collapse
Labeled for commits about boot animation.
Anyway, downloading.
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
pennywaltz said:
I am trying to move an app from /data/app to system/priv-app. I never encountered this issue before.
My Nexus 7 2013 LTE tablet (deb/razorg) was acting up and I had a bunch of apps on it. I figured the easiest thing to do is just wipe the thing and start fresh. So I used Nexus Root Toolkit to flash the latest version of stock OS (6.0.1 (MOB30X)) and then I rooted it using the latest Magisk (v18).
So I have root, I am able to see all the files in /. I tried using FX with mount R/W (tried mount R/W on "/", "/System" and "/system/priv-app") to copy the app folder from /data/app to /system/priv-app., however it failed.
I tried using 'App systemizer (Terminal emulator)' created by veez21 with Terminal emulator to move the app, but that didn't work either... despite App systemizer stated it was done.
I figured it could be the OS so i tried flashing it again and rerooting it again with Magisk, same issue and I tried an earlier version of the stock OS (6.0.1 (MMB30S)) same issue. Tried it again on the latest OS and this time rooted it with NRT instead of Magisk, same issue.
I clearly have root as titanium backup works fine with restoring apps.
So I think for some reason the OS is denying me write access to /system/priv-app, despite I did mount r/w.. I think I did all the steps correctly..so I am wondering if anyone can point me in the right direction. .. maybe I am missing a step somewhere..
Click to expand...
Click to collapse
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted?
2) you have Magisk root manager installed?
3) you have the latest version of busybox installed and have granted it root permission.
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting)
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?)
6) your bootloader is unlocked? (this may or may not be necessary)
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary)
8) have you checked to see if there are any Magisk modules that you might need?
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option?
Sent from my LGL84VL using Tapatalk
REsponses below
Droidriven said:
Let's try to cover the bases and go from there.
1) root checker verifies the device is rooted? Based Root Checker I am rooted
2) you have Magisk root manager installed? Yes I have Magisk Manager installed, safetynet passed
3) you have the latest version of busybox installed and have granted it root permission. Yes, installed to /system/sbin
4) you have gone to system settings>developer options>root access and have set root access to "apps and adb"? (you may or may not have this setting) Not an option
5) you have set mount R/W? (you have also granted your file manager/root explorer superuser/root permissions?) Yes, FX has roots right based on Supersu and i have mounted R/W prior to pasting it into the director
6) your bootloader is unlocked? (this may or may not be necessary) It is unlocked
7) you have set your SELinux polcy to "permissive" mode instead of "enforcing mode? (this may or may not be necessary) Base on App Systemizer, SE Enabled is False, therefore I assume it is off
8) have you checked to see if there are any Magisk modules that you might need? Not that I know of, I have moved this app as system without it on my Nexus 7 before without any other modules and also have done it on my Pixel 1 phone without it
9) you said that Titanium Backup is working, Titanium Backup has a feature that converts user apps into system apps for you, have you tried this option? Yup tried it, it just hangs there, nothing happens
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Sounds like I covered all my bases... so I am puzzled
Dear early adopters, I recently switched to Android 10 without any hassle. Root and TWRP have been contained after taking the necessary steps, already mentioned over and over.
The one thing I do not get however is why the app "System App Remover (root needed)" seems to be softbricking my device.
I am on the latest TWRP 3.3.1-65 by mauronofrio, Magisk beta 19.4. Everything is working fine, until I use the app mentioned above.
The apps I am deleting did not yet ever cause any problem at all getting deleted by this exact app so this seems to be app-specific.
Apps I am deleting e.g.:
Chrome
Netflix
Gmail
Google
Google Movies
Google Music
Google Books (or slightly different)
In general just some bloatware. Everything is working flawlessly until I reboot. I am then shown the typical safetynet screen for about 30 seconds and then taken to the fastboot screen, rendering the device useless-as-is. I did try deleting Netflix only as well with the same results.
The only thing reverting those steps is flashing the ROM in TWRP, flashing TWRP and magisk for obvious reasons and trying all over again.
I did try deleting the same apps in Titanium Backup. Deleting Netlix worked without any hickups it seemed. A reboot brought it back up again.
Google apps such as Chrome and Gmail are even getting me a nice "apk-file could not be found/located" message.
How do you guys get rid off those unwanted apps on Android 10 then? Am I missing something? I would appreciate a more technical explanation on the topic as to why things are the way they are if anyone of you guys experiences the same.
I had the same problem until I flashed Magisk Stable. Now no problem to remove system apps on android 10.
You can manually remove system apps using a file manager with root access. Go to system/app and delete the apks. If you mess up, just reflash the rom.
Yes with root file manager I was having the same problem with apps returning after reboot. Canary Magisk was the problem. After installing Magisk Stable all problems were gone. hope this helps someone.
I meanwhile flashed the 19.3 stable magisk. Seems like I had a broken instance of 19.3 on my device as well which caused the same bootloop as the beta. Thanks for the hint.
dtown808 said:
Yes with root file manager I was having the same problem with apps returning after reboot. Canary Magisk was the problem. After installing Magisk Stable all problems were gone. hope this helps someone.
Click to expand...
Click to collapse
tropical cactus said:
You can manually remove system apps using a file manager with root access. Go to system/app and delete the apks. If you mess up, just reflash the rom.
Click to expand...
Click to collapse
Yes, I know that is possible. Still I would prefer some more technical insight on the topic. Status quo at magisk 19.4 is that the apps can be deleted in "root remover"-apps and else, but show up again after a reboot.
Titanium still tells me the apks could not be found. What has been changed by switching to Android Q causing this to happen? After all it was still working fine that way in Pie.
why not disable them ? all this hassle
RfBob said:
Titanium still tells me the apks could not be found. What has been changed by switching to Android Q causing this to happen? After all it was still working fine that way in Pie.
Click to expand...
Click to collapse
Take a look at this post
Toutatis_ said:
Take a look at this post
Click to expand...
Click to collapse
Thank you a lot. This clears the fog. Exactly what I was looking for.
Yandvoiris said:
why not disable them ? all this hassle
Click to expand...
Click to collapse
I don't like freezing/disabling apps instead of deleting them so this is a no-no. Probably more of a personal preference in attempt to keep the device relatively bloatware free.
It's the same with storage extension back in the days. Of course you could go for the 32gb version of the phone and expand by SD card. But I'd rather take the 64gb one and still be able to but not necessarily have to use the SD slot. You get the point, I guess.
Why not just use ADB to remove them? It works fine and is simple enough.
You can also boot in twrp. In mount option put check mark on System. Then in the advanced option use the file manager and navigate to system/system/product/app OR /priv-app. There are the google and other apps. Delete what you wish. when done, unmount system and reboot
There's a magisk modules I used to use on pie that worked flawlessly. Its called debloater or debloat. It removes system apps by using a terminal app by typing the command 'debloat', and its self explanatory from there. Also if there's any issue, you can reinstall the app right back the same way you uninstalled. Haven't tried on Android 10 just yet tho. Worth a try.
One other thing, I'm the same way, if I'm never going to use certain apps, I want them gone. However, phones these days that are coming with base model of 128gb and 8gb( like the one plus 7 pro) I'm not as worried as I used to be with removing the bloat.
P.s. im guessing by the apps you named you also have a 7pro, but I might be wrong. If you a Samsung device, there is the Package disabler app on the play store. And now, I guess they have a version for all Android devices and you don't need root. Here it is https://play.google.com/store/apps/details?id=com.pdp.deviceowner
Good Luck
Debloat indeed does still work. I used it today on 10
Sheetzie03 said:
There's a magisk modules I used to use on pie that worked flawlessly. Its called debloater or debloat. It removes system apps by using a terminal app by typing the command 'debloat', and its self explanatory from there. Also if there's any issue, you can reinstall the app right back the same way you uninstalled. Haven't tried on Android 10 just yet tho. Worth a try.
One other thing, I'm the same way, if I'm never going to use certain apps, I want them gone. However, phones these days that are coming with base model of 128gb and 8gb( like the one plus 7 pro) I'm not as worried as I used to be with removing the bloat.
P.s. im guessing by the apps you named you also have a 7pro, but I might be wrong. If you a Samsung device, there is the Package disabler app on the play store. And now, I guess they have a version for all Android devices and you don't need root. Here it is https://play.google.com/store/apps/details?id=com.pdp.deviceowner
Good Luck
Click to expand...
Click to collapse
Well I don't know what happened me, but youtube (system app) was gone from my phone this morning for no apparent reason. Had to reinstall it from the store as just a normal user apk. Very strange
equlizer said:
Debloat indeed does still work. I used it today on 10
Click to expand...
Click to collapse
Well here you go @RfBob confirmation from @equlizer that Debloat works on 10.
Good to know equlizer, I appreciate you jumping in and confirming this.
On pie, it was my go to, because it worked so well.
Neat little mod. And if you run into issues by uninstalling an app and the system goes haywire, because it has happen to me before where I was sure removing a certain system app would be fine, but it found out it was not, so you can easily reinstall the app the same you uninstalled it.
Take care.
Meanwhile I found some time to play around with the debloater terminal module.
Unfortunately most of the apps good to go are nowhere to be found. E.g. chrome, duo and else. I guess they should be located in vendor apps but they're not. Any suggestions?
I have not yet tried the adb method but guess it should work. For sake of simplicity I'd prefer the debloater module though as my devices are rooted anyway and reverting back to stock apps is no hassle.
RfBob said:
Meanwhile I found some time to play around with the debloater terminal module.
Unfortunately most of the apps good to go are nowhere to be found. E.g. chrome, duo and else. I guess they should be located in vendor apps but they're not. Any suggestions?
Click to expand...
Click to collapse
Three of the first four choices you can search for apps you want to uninstall. The fourth choice you can insert yourself ie., /system/product/app or priv-app. That will give you more choices also.
jcsww said:
Why not just use ADB to remove them? It works fine and is simple enough.
Click to expand...
Click to collapse
Indeed, if you are rooted, then a couple of basic linux commands will do.
You just have to remount the /system partition as writeable.
Code:
> adb shell
$ su
# mount -o rw,remount /system
# cd /system/app/
# rm -rf Netflix_Stub
# rm -rf xxx
# rm -rf yyy
# ...
# sync
# reboot
Above is example to remove the Netflix_Stub ...
If the above is like Chinese for you ... then stay away from it.
Yep, also usually prefer ADB...
foobar66 said:
Indeed, if you are rooted, then a couple of basic linux commands will do.
You just have to remount the /system partition as writeable.
Code:
> adb shell
$ su
# mount -o rw,remount /system
# cd /system/app/
# rm -rf Netflix_Stub
# rm -rf xxx
# rm -rf yyy
# ...
# sync
# reboot
Above is example to remove the Netflix_Stub ...
If the above is like Chinese for you ... then stay away from it.
Click to expand...
Click to collapse
You cannot mount system as rw anymore on android 10, even if rooted.
Code:
flame:/ # mount -o rw,remount /system
mount: '/system' not in /proc/mounts
Code:
flame:/ # mount -o rw,remount /
'/dev/block/dm-4' is read-only
Worked using debloater, but...
Sheetzie03 said:
Well here you go @RfBob confirmation from @equlizer that Debloat works on 10.
Good to know equlizer, I appreciate you jumping in and confirming this.
On pie, it was my go to, because it worked so well.
Neat little mod. And if you run into issues by uninstalling an app and the system goes haywire, because it has happen to me before where I was sure removing a certain system app would be fine, but it found out it was not, so you can easily reinstall the app the same you uninstalled it.
Take care.
Click to expand...
Click to collapse
I did follow the steps to remove youtube app from OOS 10 on One plus 6 and rebooted but it didn't completely remove it, instead it converted it to user app. I simply uninstalled it like a user app, did a reboot and then installed youtube vanced from Magisk. So far everything is working fine.
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
iBreakStuff said:
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
Click to expand...
Click to collapse
It may be having a conflict with cached data from the version that you installed, removing the cached data might allow you to install the version you want.
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Click to expand...
Click to collapse
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
iBreakStuff said:
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
Click to expand...
Click to collapse
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So I tried what you suggested, I got the same result. Maps uninstalls but still lives in the root directory. Not being an ADB expert I went into adb shell super user mode and tried the the rm command to delete the folder, also the remount system command. Neither of those worked. Trying to install the older APK results in "App not installed"
And yes I have Magisk manager. It installed the latest version automatically. I use RootExplorer and it has superuser permissions.
Would something like this work? I'm not completely clear on how this works.
https://www.isrgrajan.com/how-to-copy-and-delete-files-in-android-using-recovery-mode.html