Hi Everyone
Because I'm lazy and was tired re-rooting manually my devices after installing manufacturers OTA updates, I wrote an app that protects root in one touch event.
It is available for free on Android market and its source code is Open Source under WTFPL (github).
Translations and code contributions are welcome.
Features: :
- Backup root before OTA & Restores it right after.
- Temporary un-root your device.
Requirements:
- Device must be already rooted.
- Protection is effective only for devices with Ext2/Ext3/Ext4 /system partition
- Non ExtFS devices will still be able to use the temporary un-root feature
OTA RootKeeper will detect what's possible or not and display available options accordingly.
Typically works for: Nexus S, Every Honeycomb tablets.
On ExtFS partition, root survives anything but true formating or partition wiping.
It means some update tools like KIES/Odin for Samsung device will wipe the whole thing anyway because they write complete new partition.
I needed this app so I wrote it, hopefully it will be useful to you too!
Android 4.3 Notes:
Based on Android 4.3 release notes, on Enterprise and Security, Restrict Setuid from Android Apps, su binaries and Superuser apps designed for previous Android generation will simply not work on 4.3:
Restrict Setuid from Android Apps
The /system partition is now mounted nosuid for zygote-spawned processes, preventing Android applications from executing setuid programs. This reduces root attack surface and likelihood of potential security vulnerabilities.
Click to expand...
Click to collapse
It means preserving root with OTA Root Keeper won't be possible anymore as new rooting techniques rely on more than just a setuid su binary in /system.
I'll look into solution of course to preserve the functionality if possible, but until then please follow Chainfire's job on SuperSU betas.
Aw, so its a no go on my sgs2..
Thanks for the amazing work as always anyways!
nanujra said:
Aw, so its a no go on my sgs2..
Thanks for the amazing work as always anyways!
Click to expand...
Click to collapse
You're welcome
On Galaxy S II, temporary unroot is working and allows you to "hide" root from stupid apps refusing to work as expected after detecting root.
Its not really hidden but so far, those stupid apps (like Google movies) use stupid detection routines.
Supercurio. do you think you can backup Superuser.apk too please. I can see where it needs to be done in github but I'm no expert in compiling apk. or Will apkmanager work for that and i Will have a go at that.
crypticc said:
Supercurio. do you think you can backup Superuser.apk too please. I can see where it needs to be done in github but I'm no expert in compiling apk. or Will apkmanager work for that and i Will have a go at that.
Click to expand...
Click to collapse
Why backup Superuser.apk?
If it's not installed, you already get automatically a button to access the market page automatically.
When you update your device via an OTA, Superuser.apk is not uninstalled.
Please describe your need
supercurio said:
Why backup Superuser.apk?
If it's not installed, you already get automatically a button to access the market page automatically.
When you update your device via an OTA, Superuser.apk is not uninstalled.
Please describe your need
Click to expand...
Click to collapse
Thanks for replying.
Busybox because is part of xbin and could be lost.
superuser apk because that would be a full unroot and reroot in one app. E.g. If I want to unroot during work hours and reroot after say if work sync calendar app doesn't like root.
Or do you think this will be a nice way to cut my teeth on android development? I see two java code places that seem to backup and then restore.
crypticc said:
Thanks for replying.
Busybox because is part of xbin and could be lost.
superuser apk because that would be a full unroot and reroot in one app. E.g. If I want to unroot during work hours and reroot after say if work sync calendar app doesn't like root.
Or do you think this will be a nice way to cut my teeth on android development? I see two java code places that seem to backup and then restore.
Click to expand...
Click to collapse
I never noticed an OTA that destroyed xbin directory? Do you have an example? (please show me the updater-script so I can study it)
Why I made this utility is because /system permissions are reset via recursive chmods during OTAs: what causes su binary to not be efficient anymore.
But saving files in not the main purpose. As long as you're rooted, you can re-install busybox in /system anyway.
Ah. I am thinking odin not ota
Ta
crypticc said:
Ah. I am thinking odin not ota
Ta
Click to expand...
Click to collapse
With Odin the whole partition is wiped, I can't backup/restore root − and as a result restore busybox either because it would require root to do so.
Any reason not to backup su to /data instead of /system? I've tried this on a Bionic and it works just fine. I tried this:
adb shell
su
cp -p /system/bin/su /data/su
rm /system/bin/su /system/xbin/su
exit - reboot phone
adb shell
/data/su
I'm root.
Seems like /data has a better chance of being untouched and as long as it's mounted correctly that copy of su will be there and executable.
crpeck said:
Any reason not to backup su to /data instead of /system? I've tried this on a Bionic and it works just fine. I tried this:
adb shell
su
cp -p /system/bin/su /data/su
rm /system/bin/su /system/xbin/su
exit - reboot phone
adb shell
/data/su
I'm root.
Seems like /data has a better chance of being untouched and as long as it's mounted correctly that copy of su will be there and executable.
Click to expand...
Click to collapse
Yes. Every Android device is supposed to mount /data with "nosuid" option, which makes su permissions inoperative.
The modded test device you used miss that; it's kind of a bug
thank you very much
as iran
Do you have to install this program after reverting to stock? Or can you install it in any custom rom before the OTA update?
matthskim said:
Do you have to install this program after reverting to stock? Or can you install it in any custom rom before the OTA update?
Click to expand...
Click to collapse
You need to install this app, make the su backup before applying your OTA.
Then, the app will be able to restore su.
If it's an OTA, this app and Superuser apk will still be installed after applying it.
Do you need to revert to stock or not before applying an update? That I don't know; depends.
Wow, this may be the app I have been looking for. I have an app for work that will not work if it detects root. Really would like to keep my phone rooted as some apps I have require it, such as Titanium Backup (which I love). I am going to give this a shot tomorrow and see if this works for me.
you are a god send
Thanks a lot, great app, works on Asus TF101 !
Faher said:
Thanks a lot, great app, works on Asus TF101 !
Click to expand...
Click to collapse
Hehe yes I saw there's an OTA for Transformer ATM
Thank you!
Playing Rented Movies that you rent from the Android Market WORK AROUND confirmed working!
Playing UltraViolet Digital Copy Movies in the Movies aka Flixster App WORK AROUND confirmed working!
pocket BLU WORK AROUND NOT confirmed working Yet! If you try it let me know
jangst123 said:
Thank you!
Playing Rented Movies that you rent from the Android Market WORK AROUND confirmed working!
Playing UltraViolet Digital Copy Movies in the Movies aka Flixster App WORK AROUND confirmed working!
pocket BLU WORK AROUND NOT confirmed working Yet! If you try it let me know
Click to expand...
Click to collapse
Thanks for the feedback about the "plus" feature which is not the main aka temporary un-root
How to test pocket BLU?
Related
I tried searching on the forum for a13 allwinners zeepad 7.0 but can't find anything.
I bought this from amazon,
Android version:
4.0.4
Model number:
A13MID
Kernel Version: 3.0.8
Can someone help me root this tablet?
Anyone? :|
Baoish said:
Anyone? :|
Click to expand...
Click to collapse
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
:good:
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
So, just install su and it will work?
deeno33 said:
Zeepad comes rooted already, at least mine did...install superuser from market and any app that needs root permission, if your able to grant such permissions your rooted. Sorry i cant remember the command for adb or terminal emulator to get this answer quicker...
Click to expand...
Click to collapse
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Yes there is A Solution To This Via A Simple App
meskes said:
My daughter just got one of these devices for Christmas, as well. I saw this post as well and thought "Great, I don't have to do the part" so, I installed SuperUser, when I went to update the su binary, which was shown as "Legacy" it got all the way to where it needs to remount the / file system as rw, and to my surprise, it wont remount. Another thing I noticed was that even though it does have su installed, I can't get to the point to where the app even asks for root permission. I tried to update Busybox, as well, and it wouldn't let me even do that... The version which is installed to the tablet appears to be 1.18, but when SuperUser goes to update the su binary it reports back as being the same as the installed version, which I know for a fact that it is not. So while I do in fact have root, it seems to only be a partial root. Anyone willing to throw around some ideas as to where I can go from here to A) get the / file system to remount rw, and B) get SuperUser, an updated su binary and an updated Busybox installed so that I can a full root going and get down to business to installing CWM and CM10 installed and running on here for her.
Any help would be appreciated,
Matt
Click to expand...
Click to collapse
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
MikeG_MG56 said:
all zeepads come prerooted and shouldnt block u from updating or to have root access (download root checker) from market
Ur Binarys Should Still Update And Say Current If U Download New Binary Just Wont Show Up Till Reboot
If u Want To Stop This Error While Not Having To Reboot Everytime
Ya This IS Annoying to Do Everytime But Simple solution
THis Proplem IS Do To The Tablet Having A Stock Kernel That Doesnt Allow System Read/Write Access
This Is Why SuperUser Fails Cause It Needs Write Access To The Devices File System...(system/xbin/su)
Which means to Remount system after updating to take Affect And Most Stock Devices Do Not Allow This
so if u updated and it said current version ur ok this is to prevent anymore errors in the future
superuser can have different error witch mean different things just cuz u get one doesnt mean
they didnt take affect but remount of system is the most common error check superuser faq
1.Download Mount System R/W App From PlayStore And Install And Open.
2 .Allow Root Access To The App Then Select Mount System R/W Button
3. Press Home Button And Navigate To SuperUser App And Then Try Updating Binary
This Method Should Work For You
Hope This Works For You
As for cwm and cm9/cm10 it depends if u have a8 or a10 device a13 are not yet supported
Click to expand...
Click to collapse
Sorry for bringing up an old thread, but I got the a13 and was wondering if anyone was making a cm9/cm10 rom for it as well. I have the a13. I tried to Google and can't find any info about any custom roms for this device.
I used kingRoot version 4.1 Any newer version would not root it.
Hey everyone, I have seen a lot of people asking about flash, or upset that they lost it after doing the Jelly Bean OTA update from Asus. Here is a quick guide on how you can install Flash on your new JB install. Unfortunately, it does require that you have root and Busybox installed. I also make use of ADB, because frankly, it rocks. There are probably easier ways to do this which I will consider writing about later, but here it is. Execute the following commands from a command prompt, and make sure that adb is able to be found.
adb shell
su root
mount -o remount,rw /dev/block/mmcblk0p12 /system
cd /system/app
mv Browser.apk Browser.org
mv Browser.odex Browser.odex.org
busybox wget http://flipcircuit.com/android/Browser.apk
cd /data/app
busybox wget http://flipcircuit.com/android/com.adobe.flashplayer-1.apk
adb reboot
Note: This will likely work on any JB device, I simply haven't tested it on others.
droidhaxxor said:
Hey everyone, I have seen a lot of people asking about flash, or upset that they lost it after doing the Jelly Bean OTA update from Asus. Here is a quick guide on how you can install Flash on your new JB install. Unfortunately, it does require that you have root and Busybox installed. I also make use of ADB, because frankly, it rocks. There are probably easier ways to do this which I will consider writing about later, but here it is. Execute the following commands from a command prompt, and make sure that adb is able to be found.
adb shell
su root
mount -o remount,rw /dev/block/mmcblk0p12 /system
cd /system/app
mv Browser.apk Browser.org
mv Browser.odex Browser.odex.org
busybox wget http://flipcircuit.com/android/Browser.apk
cd /data/app
busybox wget http://flipcircuit.com/android/com.adobe.flashplayer-1.apk
adb reboot
Note: This will likely work on any JB device, I simply haven't tested it on others.
Click to expand...
Click to collapse
Is that simply using ICS Browser.apk to replace JB Browser.apk?
Yes, its the ICS browser and flash APK's. I simply threw them on my server because wget is the most convenient way to get the file on your device. Have you tried it yet?
Nice thread
So having the flash app backed up from Titanium or other program, won't work after the update? I thought backing up the program this way would allow us to reinstall the app.
fsured, this is purely my speculation, but I would assume that the update package from Asus will overwrite the old Browser APK with the new one. I don't know if Titianium Backup will backup system apps or not? If Titanium backup did in fact backup the old Browser.apk, and the flash.apk, then you should be fine. If not, then this is a way to get it back. Hope that helps?!
Thanks for the answer. Only one way to find out! I'll be giving it a try shortly.
fsured said:
Thanks for the answer. Only one way to find out! I'll be giving it a try shortly.
Click to expand...
Click to collapse
would non-stock browsers like firefox/opera still retain flash though?
SayWhat10,
I think the biggest issue is that you can no longer download the Flash package from the Play Store, at least thats my experience. Having said that, third party browsers that support flash should still be able to support it, but you may have to side-load the flash APK. You can get that here: http://flipcircuit.com/android/install_flash_player.apk
Just copy that to your SD Card, or phone (or use ADB), and install it.
Running the reinstall from titanium back up worked fine. Tested it out already. I actually think it didn't need to be reinstalled. It showed installed but I did it anyway to play it safe.
Flash still works fine after the JB update. I did not have to reinstall.
Good, so this is likely only applicable to those bums like me who never took the time to add flash in the first place!
My JB stock browser works with flash player side-loaded. No need to load ICS browser again.
macaumen said:
My JB stock browser works with flash player side-loaded. No need to load ICS browser again.
Click to expand...
Click to collapse
try espn.com
Sent from my ASUS Transformer Pad TF700T
So this doesn't work? http://forum.xda-developers.com/showthread.php?t=1774336
Also you can still get flash player at adobe:
Just pick the latest Android version.
FF plays flash just fine, no root required after installing the apk mentioned below. Dolphin Beta starts nagging that Flash is disabled when you install it fresh.
http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html
Hello,
I used "OTA RootKeeper" too "save" my root, and then updated my phone.
I had to re root manually, and since this moment when I try to install busybox or to update su binary my phone reboots.
I tried to manually remove the root (by removing the Superuser.apk and su files), to wipe /data, dalvik_cache, cache etc...
Nothing seems to solve the problem
Does anyone have an idea?
Thanks for your answers!
(Sorry for my English I'm French )
Yep, the jb update has a kernel that write protects /system, at least for the One x and Droid DNA
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
RootJunkie said:
Is that to say Hassoon's toolkit won't work on a JB updated device?
I've just updated and I'm regretting every minute that I've used it since....
Click to expand...
Click to collapse
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
absolutelygrim said:
That means root doesn't really exist on jb.. even if you install su, any changes made will be undone at a reboot
Click to expand...
Click to collapse
What to do?
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
mihaiolimpiu said:
Actually the phone gets rooted fine busybox is installed, checked with Root Validator after several reboots, but it seems system partition, or something else is not mounted with write privileges.
S-On ?? Maybe? I'm not a HTC guy....
Click to expand...
Click to collapse
System is write protected.. due to the kernel, you need s-off or a different kernel, and seeing as there is no kernel source, ICS or aosp are your options. Try making a folder in /system, it should be gone after a reboot
But the files I create from TWRP recovery aren't removed after a reboot. The Superuser.apk is still here after a reboot.
So it seems that I can write to /system from recovery.
Do you know if there's a flashable zip for busybox?
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
Su + Busybox
WAY LATER EDIT:
System Partition RW on JB stock roms via kernel module
mihaiolimpiu said:
I flashed the one in the JB discussion thread... I think it contains Busybox and SU and it works like a charm... It's a problem but there are workarounds...
For me everything works as long as it doesn't write data to system .
AdBlock works, it gets SU rights but it cannot write the hosts file... I will try later to use the symlink solution...
http://forum.xda-developers.com/showpost.php?p=35907661&postcount=1928
Click to expand...
Click to collapse
I just tested it and everything I used before on my phone is working again and no more unwanted reboot
Thanks a lot !
I sent a PM to TeHashX, he was asking for review on his work, and also thanked him... His work could benefit others... so make his post more visible!
Remember, that because of the kernel, AdBlock still doesn't work, basically every program that modifies /system works but only apparently. I could use Titanium very well, only Integrate in Rom option doesn't work so take care using "ROOT" on HOS JB.
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.
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.