Related
I rooted my Captivate. No errors, I have the Superuser listed in my Applications now.
But how do I verify this worked? How on earth do I nix the ATT Navigator and such?
Go to the market and download an app that requires root. If it works, then you have root.
Dave2582 said:
Go to the market and download an app that requires root. If it works, then you have root.
Click to expand...
Click to collapse
Like, any examples?
If you have a custom recovery installed for your captivate, go to the market and download quick boot. Once installed, go into quick boot and select recovery. That should boot your phone into your custom recovery. If that works, then you are rooted.
Dave2582 said:
If you have a custom recovery installed for your captivate, go to the market and download quick boot. Once installed, go into quick boot and select recovery. That should boot your phone into your custom recovery. If that works, then you are rooted.
Click to expand...
Click to collapse
It came up with a "Superuser Request" and booted into recover mode
SWEET!
Question...
How can I figure out what an Application's package name is so that I can uninstall it (IE, the ATT preinstalled crap like Family Maps).
Follow this thread on how to remove preinstalled apks. Good stuff.
Dave2582 said:
Follow this thread on how to remove preinstalled apks. Good stuff.
Click to expand...
Click to collapse
Here's what I did:
cd c:\android-sdk-windows\tools
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
ls (This displays all apps on the phone.)
To delete ATT Maps:
rm attmaps20-1094.apk
Now when I try to run the RM I get a permission denied error??????
I was thinking of removing these:
attmaps20-1094.apk <<-- ATT Maps
MediaHub.apk <<-- Samsung Media Hub
MobiTV_800x480_320_20100610_1.0.0.15-118829.apk <<--ATT MobiTV
ATT_Radio_2.1.07.apk <<--ATT Radio
ATTNav-Samsung-Vega-1488.apk <<-- ATT Navigation
Didn't see ATT Music or anything like that but that would've given me a good start.
Once you have achieved root (see other thread), to update the Superuser.apk to the latest version, run these commands:
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /system/app/Superuser.apk
pm uninstall com.noshufou.android.su
Then search on the market for Superuser and download the one by ChainsDD. Confirmed working on latest Droid2 2.2 ota.
EDIT: To be safe, go to Settings>Applications>Manage Applications and find Superuser. Then clear the data. This should prevent any of the Superuser issues discussed.
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
metman87 said:
sorry..new to the whole android scene. are there any advantages to updating the superuser app the the latest version and can this command be input on the droid itself through the terminal app?
Click to expand...
Click to collapse
i like the interface much more and its got a new autoaccept after 10 seconds if you arent paying attention when the popup shows. it's up to you. i'm sure future root tools will just include it.
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
metman87 said:
alright thanks. is it as simple as installing the new version and uninstalling the old? or does one need to enter the command prompts listed above?
Click to expand...
Click to collapse
that is what the commands do. unfortuantely, the old version is on the system partiton. this means that we must first mount the system and read/write and then manually delete the old version ourself. then the new version can be easily downloaded through the market. anyways, adb shell means it's done via your computer so its very easy to copy and paste like 3 commands.
Instructions work perfectly... thanks!
I need Mac instructions
Sent from my DROID2 using XDA App
greg25 said:
I need Mac instructions
Click to expand...
Click to collapse
These instructions are not specific to the OS on your computer, they work with anything.
Perfect!
Worked great! Thank you!
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
n0yd said:
Instructions worked fine (I just made them up for Linux), but the newest SuperUser is giving me weird results. Every program that requests root access will ask me numerous times, like it never remembers that I gave the app access. Like removing one app with titanium will it will ask me 4 seperate times to accept or deny permission. Other apps do this also. Anyone have a copy of the old apk I could reinstall? Anyone have any ideas or suggestions?
Thanks
Click to expand...
Click to collapse
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Nice, thanks!
I had that issue too. I ironically un-installed superuser and re-installed it and it worked fine too
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
that works too though without having the superuser apk and rebooting, that could be a little dangerous for others hence my adb tutorial. no need for a restart either. could easily just use root explorer, delete the old, download new from market.
Worked great
I just renamed Superuser.apk to .bak then tried to install. Don't forget the last step. I had to adb (I was using terminal emulator) to do the last step then installed fine and removed Superuser.bak.
Thanks I like the New look.
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
jerseyh22accord said:
yeah i can't get superuser from the market to install, keeps telling me unsuccessful
Click to expand...
Click to collapse
I had the same problem. I rebooted my phone and then it installed fine. Not sure if it's risky to reboot once you remove the apk or not. However, it didn't cause any problems for me.
jmonte345 said:
I used Root Explorer to delete the old Superuser.apk from /system/app. Then I rebooted and installed the new version from the market. Worked great.
Click to expand...
Click to collapse
I basically did the same thing except I renamed instead of deleting it. Well, once I installed SU from the market, I can't find the .apk file even though it's running and launching correctly. I assumed it would be called superuser.apk in the system/app folder but only my old renamed superuser.bak is there. I'm just worried if there is an update in the future, I won't be able to rename since I can't find the .apk file. Anyone know where the .apk file is for this new version of superuser?
facelessuser said:
I had the same thing happen to me. Launch the new superuser app and go to settings. Unselect and reselect Notifications. Apparently it shows it being checked, but you have to recheck it for the actual setting to get saved.
After I did this, it only asks once for a program, and then I never see it again.
Click to expand...
Click to collapse
Tried this, and it didn't work for me. With Titanium Backup in particular, it will literally ask upwards of twenty times for permission. It's insanely annoying. Any other tips?
Sent from my DROID2 using XDA App
I'm running XBoarder's GB 2.3.3 ROM Version1.2.2. I flashed it this morning.
The "old" version of Swype is working just fine. However, when I download the Beta.apk and try to install, Swype won't work.
I'm using Titanium to "Freeze" the original Swype so the Beta will load onto my phone. It used to work like a charm, but is not working anymore.
Anyone else having any problems?
Does it Force Close on you?
you have to uninstall completely the old swype. then you have to use a file explorer to remove a file called libswypexxxx.co or something like that. It is located in system/lib. Then you install the beta installer and finally you download the beta and install it through that app. you can also at this point use one of the swype themes, which look amazing.
adevilfish said:
you have to uninstall completely the old swype.
Click to expand...
Click to collapse
Adevilfish,
How do I completely uninstall Swype? I go into Settings - Apps - Manage Apps - ALL APPS, and then I scroll down to SWYPE. It does not give me the option to Uninstall. Just to Force Close and/or Clear Data.
What do you do at this point?
TeldenW said:
Adevilfish,
How do I completely uninstall Swype? I go into Settings - Apps - Manage Apps - ALL APPS, and then I scroll down to SWYPE. It does not give me the option to Uninstall. Just to Force Close and/or Clear Data.
What do you do at this point?
Click to expand...
Click to collapse
It's a system app so you can't use the manage applications setting.
Code:
adb remount
adb shell rm -f /system/app/Swype.apk
adb shell pm uninstall com.swype.android.inputmethod
adb shell rm -f /system/lib/libSwypeCore.so
After that install the beta.
wewoapsiak ,
I sincerely appreciate the information, but that could not have made any LESS sense to me.
That was WAY over my head. I'm getting better with this phone stuff, but I clearly still am a "White-Belt Noob".
Forgive the following questions:
What was that?
What do I do with that code?
ADB---Android Device Bridge. How your phone communicates with your computer.
There are many alternatives, but if you want to learn about it, try here.
Or simply download Android Commander, it's a GUI for your computer that allows you to drag and drop or delete. Or use root explorer. There are plenty of ways. Delete the two files (Swype.apk and libSwypeCore.so), install the beta.
Can this be done using "Root Explorer"?
TeldenW said:
Can this be done using "Root Explorer"?
Click to expand...
Click to collapse
Yes. Navigate to those directory file listed in the adb posting above.
Delete those lines
Got it handeld...
Rocking the beta again.
Thank you all for your help!
You know what distinguishes a good the from the from a bad on? The good one spend his time is helping others, while the bed one spend his is time consolidation power
There are no stupid question, every question is a quest for knowledge..Knowledge flows freely here at XDA! ask and ye shall b answered.
ThaNx to all the member that TEAM AD with the various tips and trick for this post I walk away, but my knowledge increased by the experiences shared with is wonderful group people. Long Live Android!
Installation:
1. Download files below, do not rename them! Transfer to SD Card.
2.* Use any file explorer and mount system as RW and delete file name (Root Explorer works nicely)‘Vending.APK’ and ‘MarketUpdater.apk’ from /system/app/. You can also delete folders com.android.vending and com.android.vending.updater in /data/data.
*Do a reboot.
* Open File explorer/ Root Explorer and Mount your file system as RW and copy ‘updater.apk’ from SD Card to /system/app/ and do a reboot.
* Now, mount your file system as RW from explorer and copy ‘market.apk’ from SD Card to /system/app/ and Reboot phone.
Edit: I feel retarded.. forgot to mention that this method is iffy on my rooted stock ROM, but it works great on my rooted custom rom.
[B said:
acolwill[/B];16952837]What functionality? All I see is fancy graphics designed for children and iRetards, there's no discernible change in how apps are grouped or searched for since version 2.12.
I have 5 android devices ranging from the HTC Hero up to the Samsung Galaxy Tab and the new market looks **** on every one. Application presentation is marred with oversized text and incessant scrolling, making it slower to actually see information pertinent to what you are looking at. Emphasis should be on the applications contained within the market, not the market application itself.
Other than that, the obfuscated way that application permissions are presented to a user in the newer versions makes it far too easy for the layman to install things with less than honourable permission requests. At least in version 2.12 you HAD to move your fingers around to accept permissions, since then all it takes is two jabs with a finger with little or no perceived consequence.
The fault lies with Google for forcing the new market style on users, no choices outside of root&destroy.
So thanks for actually taking the time for making the Google apps look nice, just let those whom want the 'clean' version have their say.
--
The attached Vending.apk is the "old" market. In order to install it, you must be rooted and you need either a little knowledge of ADB or Root Explorer from the market.
Using ADB;
Reboot into recovery and plug into pc, mount /system using your recovery
From your preferred ADB console:
adb push Vending.apk /system/app
adb shell rm /system/app/MarketUpdater.apk
adb shell chmod 644 /system/app/Vending.apk
adb shell chown root.root /system/app/Vending.apk
Reboot.
Using Root Explorer;
Download apk to sdcard
mount /system rw
browse to /system/app
remove MarketUpdater.apk
remove Vending.apk
browse back to sdcard and copy the Vending.apk to /data/local/tmp
copy the Vending.apk from /data/local/tmp to /system/app
using permissions action, set permissions on Vending.apk [Owner: Read Write. Group: Read. Others: Read]
using set owner action, set owner to 0 - root, group to 0 - root.
Close and reboot.
The Root Explorer method may not work for all phones, and will not work on HTC phones which do not have s-off. The ADB method should work on any rooted device which previously had market access.
Click to expand...
Click to collapse
[B said:
here.david[/B];16956089]Thanks that worked BTW, on the Vibrant (MiUi) here is the command I used to mount without going into CWM....
From your preferred ADB console:
adb shell mount -o rw,remount -t ext4 /dev/block/stl9 /system
adb push Vending.apk /system/app
adb shell rm /system/app/MarketUpdater.apk
adb shell chmod 644 /system/app/Vending.apk
adb shell chown root.root /system/app/Vending.apk
Reboot.
Click to expand...
Click to collapse
[B said:
nygmam[/B];16959137]I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.
Click to expand...
Click to collapse
I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.
Why would anyone want to do that? To put it in a different way: What are the advantages of the old market?
Thanks man, the new market sucks...
For some people the new market lags a lot especially on lower end phones, the last version was terrible for me so I had to use the old one but this latest update is a huge improvement, so i'll stick with it.
Sent from my HTC Wildfire using XDA Premium App
If you change the density of your phone's display, you wont't be able to download many apps(shazam free for example). It says that your device is incompatible, that's why I reverted back to the old market.
Sent from my HTC Desire
new market sucks..it lags on older phone
Agreed. Installed it, and soon had to restore old version from backup!
Any chance this will work without root? My wife hates the new market.
Sent from my ADR6350 using Tapatalk
QBall45 said:
Any chance this will work without root? My wife hates the new market.
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
Have you given a brief look at the benefits of root vs stock? Well worth it.. Just a little research about rooting your particular phone and you can do it quite simply
i just downloaded the old market apk again and replaced it over the new one , and it worked , i have samsung galaxy s2 ,but still the new market is slow
I use a simple method, which works very well, and so far has not had a down side:
1) Using Titanium Backup (Or another app that lets you do this) either Freeze (Paid app) or Backup, then delete Market Update (Free App)
2) Go to Settings, Applications, Manage Applications, and scroll down to market, and select
3) Uninstall updates from Market
This is very easy to do, and you may be able to use other freeze or backup apps to achieve the same result. Also note, no reboot required.
shadows of yesterday said:
i just downloaded the old market apk again and replaced it over the new one , and it worked , i have samsung galaxy s2 ,but still the new market is slow
Click to expand...
Click to collapse
If you don't delete or disable Market Updater, new market will return... Maybe not right away, but it will be back. Also no need to reinstall old market, it is still on your phone. Just see my post above on how to uninstall the updates to market (Step 2 and 3), just uninstall updates, and go back to market, accept teh T&C and you will be back using old market again.
This worked for me ONLY after following the steps in OP and:
1. Changing the permissions of both files to rw-r-r
2. Renaming market.apk to Market.apk
3. Renaming updater.apk to Updater.apk
I think you'd need to 'chown root.root' on both files too...
GRRemlin said:
This worked for me ONLY after following the steps in OP and:
1. Changing the permissions of both files to rw-r-r
2. Renaming market.apk to Market.apk
3. Renaming updater.apk to Updater.apk
Click to expand...
Click to collapse
Maybe the mods can add this bit of info to the first post. Thank you!
You can edit it (or should be able to)
hello.
i'm using an xperia x10 mini E10i, and just did those steps. My market dissapeard, and now i don't know how to install it back( i didn't make a backup of the apks i deleted =( ). Can you please tell me what should i do?
I also tried GRRemlin's version and still doesn't work.
Thanks in advance.
li9ht said:
new market sucks..it lags on older phone
Click to expand...
Click to collapse
after themeing the market for the last five versions i would have to say the new market adds fuctionality over the old.
sounds like your blaming google for having a slow outdated phone.
still a good post though for those that like the look of the old market
Try restoring your apps and following the directions posted in post 2 it really is easier, and you don't have to mess with chmod and renaming and rebooting.
Sent from my ACA Gingerbread HTC HD2 using XDA App
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.