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.