Database Users

Extra Features on AOSP 1.6

I'm setting up this thread to keep extra functions on AOSP 1.6 & the actual development of AOSP 1.6 separate.
Discuss issues with extra functions in this thread & NOT the AOSP 1.6 thread.
________________________________________________
Googlebits:
Flash with this signed update.zip: Multiupload (RS|MU|DF|HF|ZS|4S)​
________________________________________________
Superuser:
Flash with this signed update.zip: Multiupload (RS|MU|DF|HF|ZS|4S)​________________________________________________
Busybox:
This needs to be installed if you install Superuser.
Code:
adb remount
adb shell
busybox --install /system/xbin/
adb reboot
________________________________________________
HTC Keyboard
Download Clicker.apk & HTC_IME.apk from here.
Do the following commands:
Code:
adb remount
adb install -r Clicker.apk
adb install -r HTC_IME.apk
adb reboot
Go into Settings>Locale & Text, made sure "Touch Input" is checked
Long press a text box, selected Input Method & selected "Touch Input"
________________________________________________
Thanks:
quietcbelongs for working on AOSP 1.6
gbhil for the two signed update.zips, this really makes it much easier for everyone
cyanogen for the framework-free HTC keyboard

Great thread.
A couple things to do after you get the Googlebits on:
Move su
Code:
#cp /system/xbin/su /system/bin/su
#ls /system/bin/**to verify su copied**
#rm /system/xbin/su
Install busybox symlinks
Code:
#busybox --install /system/xbin/
I'm loving this build. As soon as GPS gets working I'm deleting my 1.5 nandroid backup.

Link is broken. :-(

JasonMudd said:
Link is broken. :-(
Click to expand...
Click to collapse
Link perfectly fine for me, site is loading a little slow, but it's still there.

Thanks for posting googlebits.
Just a FYI
its a bit cleaner if you do the following.
unarchive google bits to androidsdk/tools
change dir to androidsdk/tools
adb remount
adb push system/framework /system/framework
adb push system/etc/permissions /system/etc/permissions
adb push system/app /system/app
adb reboot

lonerebel said:
Thanks for posting googlebits.
Just a FYI
its a bit cleaner if you do the following.
unarchive google bits to androidsdk/tools
change dir to androidsdk/tools
adb remount
adb push system/framework /system/framework
adb push system/etc/permissions /system/etc/permissions
adb push system/app /system/app
adb reboot
Click to expand...
Click to collapse
I prefer to push each file individually but I guess that would work also.

lonerebel said:
Thanks for posting googlebits.
Just a FYI
its a bit cleaner if you do the following.
unarchive google bits to androidsdk/tools
change dir to androidsdk/tools
adb remount
adb push system/framework /system/framework
adb push system/etc/permissions /system/etc/permissions
adb push system/app /system/app
adb reboot
Click to expand...
Click to collapse
Worked great for me! Thanks!

It may be something else I've broken (I've been tinkering), but is anyone getting gmail push with this build?
Mine seems to have stopped. I can check the mail manually, but nothing is getting pushed to me. Since this could be a Google issue, or something I've done, I'm looking for input before i troubleshoot.

incogneato said:
It may be something else I've broken (I've been tinkering), but is anyone getting gmail push with this build?
Mine seems to have stopped. I can check the mail manually, but nothing is getting pushed to me. Since this could be a Google issue, or something I've done, I'm looking for input before i troubleshoot.
Click to expand...
Click to collapse
I was getting Gmail fine the first day. I'm going to reflash my phone tonight & start fully testing it.

nevermind.

thanks so much for this works like a charm

contacts arent syncing
Hi. I'm having a problem getting my contacts to sync up.everything else though is working flawlessly though

Do the protected apps in the market place show up with this rom??
Thanks!

incogneato said:
It may be something else I've broken (I've been tinkering), but is anyone getting gmail push with this build?
Mine seems to have stopped. I can check the mail manually, but nothing is getting pushed to me. Since this could be a Google issue, or something I've done, I'm looking for input before i troubleshoot.
Click to expand...
Click to collapse
I'm also having issues with new emails being pushed to my phone, but I have been tinkering with SU, so I also may have broke it. I have already installed this on another friend's Hero & I'm going to see if they are having the same issue.
UPDATE:
My friend has not been having an issues receiving new email or with the notifications, so something related to SU or busybox, is possibly causing the issue.
darchstar said:
Hi. I'm having a problem getting my contacts to sync up.everything else though is working flawlessly though
Click to expand...
Click to collapse
I think there might be issue with Google sync after the initial sync.
jerrygon said:
Do the protected apps in the market place show up with this rom??
Click to expand...
Click to collapse
Yes protected apps show up in the market & install fine.

gu1dry said:
I'm also having issues with new emails being pushed to my phone, but I have been tinkering with SU, so I also may have broke it. I have already installed this on another friend's Hero & I'm going to see if they are having the same issue.
UPDATE:
My friend has not been having an issues receiving new email or with the notifications, so something related to SU or busybox, is possibly causing the issue.
I think there might be issue with Google sync after the initial sync.
Yes protected apps show up in the market & install fine.
Click to expand...
Click to collapse
Thanks. I went the whole way back. RUU, rooted with 1.5.2 recovery, flashed quietcblongs 1.6 and copied over googlebits. I'll leave it for a while and verify sync works as expected.
I don't see how busyboxes symlinks or moving su could break it, but your research mirrors mine, so we will see what happens.

Sometime last evening Google syncing stopped again. I'm going to try some mixing and matching with the various 1.5 and 1.6 versions of googlebits.

When i put the code in the cmd it says code not found

i meant error device not found

Did you install the Android SDK? If you did, did first cd to the tools folder of you Android SDK, before you did all the adb commands?

i did i do not know what is wrong

Superuser?

Does anyone know how to install this on the aria?
http://forum.xda-developers.com/showthread.php?t=682828

It's best to flash your Aria to a Liberated ROM. You can find it within the forums here. Since I can't post links yet. This will root the device and SuperUser will be added.
Not sure about that app. It looks like it does the same thing as the SU that comes in the Liberated ROM by attn1, just without the few extra options.

I tried booting into clockwork and mounting the system partition and doing this:
adb push Superuser.apk /system/app
adb push su /system/xbin
adb shell chmod 06755 /system/xbin/su
adb reboot
but when it rebooted the superuser app did nothing at all. No prompt or nothing running apps that needs su. I had usb debugging enabled. So I just restored a nand backup.

Might be a dumb question, but did you do adb remount ?

I used clockwork to mount the system partition. When I tried it with just adb remount it wouldn't mount the system partition. I would always get "Not a directory" error. But when clockwork mounted the partition it wrote the files fine with no error. When I rebooted the superuser icon and version were different than the one that came with the liberated rom.

I'm trying this now, I'll report back when I do it. I'll try a few different apps that require SU

I did the commands it said, I see the new icon, and when I press 'Menu', it shows the prefrences, but when I click it, it freezes the app.

It's probably not compatible with our phone yet.

Could be, but I'm pretty sure it does work, because if I remember correctly, Titanium Backup needs SU permissions, and I haven't encountered any kind of errors with it yet.

I see you posted on the thread for the program itself. Hopefully someone there will have a response.

Yeah, I'm hoping to get a response to it. We will see.

The newer version 2.2.2 works.

Awesome, ill give it a shot a little later.

Tried the newer version, and I get the same issues.

How did you install this one? I booted in to clockwork and selected install from zip file on sd and selected that file on my sd card.

I just did it through adb. I'll give that method a shot.

Looks like after doing your method, it works perfect now. Not sure why using adb doesn't work.

(Q) Root with Super User

So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?

Have they asked for superuser?
Via EVO on 4G with XDA App

awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device

krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.

richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...

krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su

Please delete

krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.

richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.

rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?

richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.

rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.

followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"

spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?

richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!

spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.

if you flash noobnl's latest kernel, it includes superuser and it works perfectly.

rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.

richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.

I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?

ROM Manager problem

Hi, when I tried to flash a rom using ROM Manager, it said that I don't have ClockWork mod, which I do. Also when I try to flash the ClockWork Mod it says
"An error occurred while attempting to run privileged commands".
Any ideas why that happened? Thanks.

Have u rooted it?
Sent from my HTC click using XDA App

i guess andynroid is right... sounds, as if the root wasn't done... just check this possibility
my description in this thread also gives you a brief overview about the steps to flash your rom

I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?

wolf.thalian said:
I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?
Click to expand...
Click to collapse
try typing in a root shell: ln /system/bin/su /system/xbin/su

Just rooted - unable to backup

Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.

cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)

bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer

cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.

bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again

I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.

cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.