Database Users

preserving market "my downloads" list between wipes/rom installs

I've wiped and installed a lot of roms lately, and generally when I go to 'my downloads' in the market, only my paid apps are there. So, I have to go though the process of searching the installing each app again. It's just easier when they are all in a list.
I figured it would be a good idea to backup all my apps and then reinstall them afterward with adb in linux as such:
for a in `ls *.apk`; do adb install $a; done
this works, but of course they don't show up under 'my downloads' and I don't get update notifications.
Is there a way around this?

gsgleason said:
I've wiped and installed a lot of roms lately, and generally when I go to 'my downloads' in the market, only my paid apps are there. So, I have to go though the process of searching the installing each app again. It's just easier when they are all in a list.
I figured it would be a good idea to backup all my apps and then reinstall them afterward with adb in linux as such:
for a in `ls *.apk`; do adb install $a; done
this works, but of course they don't show up under 'my downloads' and I don't get update notifications.
Is there a way around this?
Click to expand...
Click to collapse
You need to backup and restore the database file located in the market folder....it should be here...
Code:
/data/data/com.android.vending/databases
I'm assuming since you can backup and restore your apps thru adb then you can figure out how to pull and push this to your phone

I assume you would want to do this to get update notifications. If so you can grab "aTrackDog" from the market. It will list all you apps and when you refresh it will tell you when updates are available and give you a link to get the update from the market.

AdrianK said:
I assume you would want to do this to get update notifications. If so you can grab "aTrackDog" from the market. It will list all you apps and when you refresh it will tell you when updates are available and give you a link to get the update from the market.
Click to expand...
Click to collapse
will it only work for software installed through the market or will manually installed software show up as well?

DirectMatrix said:
You need to backup and restore the database file located in the market folder....it should be here...
Code:
/data/data/com.android.vending/databases
I'm assuming since you can backup and restore your apps thru adb then you can figure out how to pull and push this to your phone
Click to expand...
Click to collapse
Awesome. I'll do this next time I wipe and reflash with the latest coolest rom. =)

gsgleason said:
will it only work for software installed through the market or will manually installed software show up as well?
Click to expand...
Click to collapse
nope, works for the apps on my ext3 even after switching builds several times, works great.

DirectMatrix said:
You need to backup and restore the database file located in the market folder....it should be here...
Code:
/data/data/com.android.vending/databases
I'm assuming since you can backup and restore your apps thru adb then you can figure out how to pull and push this to your phone
Click to expand...
Click to collapse
For those of us who are not that familiar with adb, can you give a short tutorial on how to pull and then push that database folder?

well i just wiped and installed the latest cyanogen mod and when i went to the "my downloads" section of the store all the apps i had downloaded before were all there (paid and free)
I also thought it didnt do that, apperently it does

Gilliland12 said:
For those of us who are not that familiar with adb, can you give a short tutorial on how to pull and then push that database folder?
Click to expand...
Click to collapse
You don't need ADB, you can use the terminal emulator from the market or the recovery console.
To pull the database, open terminal or recovery and type:
Code:
su
cd /data/data/com.android.vending/
cp databases /sdcard
that will copy that database file to the root of your sdcard.
When pushing it back it is probably best to do it while the phone isn't running, so only use the recovery console:
Code:
cd sdcard
cp databases /data/data/com.android.vending/
reboot
I haven't tested this, but it will have the same results as the ADB method.

AdrianK said:
You don't need ADB, you can use the terminal emulator from the market or the recovery console.
To pull the database, open terminal or recovery and type:
Code:
su
cd /data/data/com.android.vending/
cp databases /sdcard
that will copy that database file to the root of your sdcard.
When pushing it back it is probably best to do it while the phone isn't running, so only use the recovery console:
Code:
cd sdcard
cp databases /data/data/com.android.vending/
reboot
I haven't tested this, but it will have the same results as the ADB method.
Click to expand...
Click to collapse
Many thanks.

Backup for Root works perfectly for me

if you got a paid app through adb and got a refund, can you still get updates for that app if you have it installed?

opasha said:
if you got a paid app through adb and got a refund, can you still get updates for that app if you have it installed?
Click to expand...
Click to collapse
No, you will not get updates without re-purchasing the app. And talking about ripping off app developers on this forum is frowned up so please stop discussing it.

opasha said:
if you got a paid app through adb and got a refund, can you still get updates for that app if you have it installed?
Click to expand...
Click to collapse
If you got a refund, then you shouldn't have the app. That's stealing and it's not nice. Most apps are cheap (a couple of bucks at most), stop being a cheapskate.

Originally Posted by AdrianK View Post
You don't need ADB, you can use the terminal emulator from the market or the recovery console.
To pull the database, open terminal or recovery and type:
Code:
su
cd /data/data/com.android.vending/
cp databases /sdcard
that will copy that database file to the root of your sdcard.
When pushing it back it is probably best to do it while the phone isn't running, so only use the recovery console:
Code:
cd sdcard
cp databases /data/data/com.android.vending/
reboot
I haven't tested this, but it will have the same results as the ADB method.
i tried this but it dodnt work.
when I did the first command it said ommiting databases. so I thought it worked.
flashed to the new cyanogen 4.0 rom (which is amazing btw!) did the second command and it said cannot stat file "databases" no such file or folder.
what gives??

Id say the databases were open and couldnt be backed up.
You should try to copy them from the recovery.
Also, after copying why didnt you check if the database files were in your sdcard (or the path you specified for the copy) before wiping? If the file is not there its obvious that it cant be restored after the wipe..

thought it might have been hidden or on my ext2 partition! never mind i got atrackdog!

addiosamigo said:
thought it might have been hidden or on my ext2 partition! never mind i got atrackdog!
Click to expand...
Click to collapse
Seems you can only copy each of the four db files individually... but copying the entire folder doesn't work.

All that is needed is assets.db
Open the terminal and enter
$ su
# cp /data/data/com.android.vending/databases/assets.db /sdcard
Wipe, flash, reboot.
YOU MUST OPEN THE MARKET AND AGREE TO THE TOS BEFORE RESTORING!!!!
Open the market, agree to the TOS, and close the market. Open the terminal and enter
$ su
# cp /sdcard/assets.db /data/data/com.android.vending/databases/assets.db
# reboot

ADB Push

I searched around and couldn't get a clear answer. I'm a noob at anything command prompt/terminal related.
I was screwing around with adb last night after figuring out that I can remove program .apks with the rm <com.whatever.program> command. I got a little trigger happy and removed things that I don't use, just to test it out. I made a nandroid backup before I started. The phone runs fine, but now the Market won't download anything. It just sits on the Starting download... screen.
One of the .apks I removed was GmailProvider.apk. Whether this is the problem or not, I'd like to reinstall it for practice. I can always nand restore later.
So my question is... How can I use adb push to reinstall an apk?
I tried:
Code:
adb push C:\GmailProvider.apk
adb install C:\GmailProvider.apk
adb install C:\GmailProvider.apk \system\app
And about every variation of the 3, in and out of the adb shell.
It didn't work, and I'm at a loss to do anything else. So does anyone have any suggestions?
EDIT: I think my "\" should be "/". I got this
Code:
BusyBox v1.15.2 <2009-12-02 TIME EST> multi-call binary
Usage: install [-cdDsp] [-o USER] [-g GRP] [-m MODE] [source] dest|directory
Copy files and set attributes
Options:
Then some usage stuff here.
Then I looked at the command prompt and made a face like .
Suggestions?
It might help to say that I'm using EvilEris 2.0.1, Windows 7.

Just reflash your ROM after doing a titanium backup. Easiest fix.

try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write

silverramsrt said:
try this after putting GmailProvider.apk in your sdk\tools dir:
Code:
adb remount
adb push GmailProvider.apk /system/app
remount marks the system directory as read/write
Click to expand...
Click to collapse
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.

CPCookieMan said:
Beat me to it. ADB is powerful and pretty cool if you know some good commands, but you can really mess up your phone if you know what I mean. Not mess up like brick (unless you really try) but more like phone won't load gmail now, phone won't get past the htc screen. As long as you have a nandroid backup you SHOULD be fine, the push, pull and rm commands are really the first step of rom building. If you know what files you pushed and rm'd you can make your dream rom.[/QUOTE
i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse

i am installing htc facebook.apk on a rom that has had all the Bloat removed.do i need to do something after i have pushed a apk file into system/app?? i have tried rebooting the phone and the program isnt there,ive tried going in the phone with root explorer and tried installing while having it in r/w and r/o and still cant get it to install.im not sure what im doing wrong.any help is apreciated
Click to expand...
Click to collapse
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App

zach.xtr said:
You do not have to do anything after an adb push.
What rom? Some roms have been modified to the point some htc apps will not work. Addionally a copy of the htcfacebook.apk from an eris build may not work on a sprint based or g1 based roms do to signature variations
Sent from my Eris using XDA App
Click to expand...
Click to collapse
im running xtrom 3.0.......i just went ahead and installed the social app flash and deleted what the ones i dont uses,but thanks for the help anyways.i was looking into pushing friendstream into it but found out its only works in sprint base builds

Custom Rom App Removal

hey guys,
how would i go about removing apps from an installed custom rom?
ive tried titanium back... doesnt work, tried pulling the apps from the pack nothing,
ive tried root exploits and it just sends your phone into an almost
"paperweight"
like state,
any further moves i can do to remove various bits ? there as some things i just genuinely dont want.

Telling which rom and which apps might help

[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT] [19/NOV/10]
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??

fkofilee said:
[ROM] Pays-ROM HD SPARTA v1.0 [ULTRA LIGHT]
i cant list the apps i want to remove as im off to work, but can you do some background work into it for me??
Click to expand...
Click to collapse
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.

when i say pull... lol. i mean removing them from the system completely

fkofilee said:
when i say pull... lol. i mean removing them from the system completely
Click to expand...
Click to collapse
I've just discovered there are issues where /system isn't getting wiped correctly prior to a new rom being flashed. Keep getting apps from other roms and such sitting in my /system folder even after a wipe and flash - at this stage I assume CWM is bugged? Could be your issue is related.

nope the ADB coding doesnt work as its almost like there is a PERMANENT R/w lock on the section i need to remove apps from

unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove

fkofilee said:
unfortunately the issues AERNT related, as ive wiped everything before, these apps are pre installed on the ROM. What does me with this is that the root exploit to remove these apps as in Titanium backup ... just turns the phone into a very expensive paperweight till the battery is remove
weather apps (widgets etc,)
Twitter apps , teet and various other bits i want to remove
Click to expand...
Click to collapse
Get a new rom ???

hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.

how weird!!!... i used to terminal emulator to allow su (I.E to give system SU Permissions and now i can remove the apps ) haha
Shocked!!
Admin Please close & Deleted Thread.

fkofilee said:
hmm flash a new rom??this is the most refined rom i can find for DHD.
for that reason its more of a hassle to flash new roms
I would rather crack it, mind you i might be really thick asking this. that code you gave me have i got to get the adb.exe from android SDK and do this via a cmd.exe window on my pc or have i got to do it on my phone via termnial emulator.
Click to expand...
Click to collapse
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.

dr.m0x said:
Yes from the android sdk. It *should* work from a terminal emulator as well if you run these commands first to mount the /system/app directory as read/write:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/app
Other option would be to use the root explorer app, it is a paid app though well worth it.
Click to expand...
Click to collapse
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.

fkofilee said:
Weird thing is i tried root explorer , and it still wouldnt R/W the app folder... but as i said now solved... slightly weird though that i completely missed that lil bit on the su permissions for the system directly.
Click to expand...
Click to collapse
Yeah you ninja'd my last post
Glad to hear you're gtg now.

but mind you the mount script i ran and it didnt work lol.... maybe i did them the wrong way round, (Raise SU first then do mount cmd??)

dr.m0x said:
Have you tried doing it from terminal?
Code:
adb remount
adb shell
su
cd /system/app
ls *
rm INSERTANNOYINGAPPNAMEHERE
reboot
adb pull is not for deleting apps. It is for copying the app to your computer.
Click to expand...
Click to collapse
Works. Thanks!

[Q] Google Books on GT 10.1 from Google I/O

I can't speak for all GT 10.1s, but the one I received at Google I/O certainly does not have Google Books installed and it's not available in the Market. It comes with Kindle pre-installed, so I'm guessing Samsung has inked a deal with Amazon, but uhh... what about choice? I have several books from both Amazon and Google and use both applications on my Xoom, but now I'm curious why I can't use Google Books on my new tablet. Do I need to try to get the Google Books APK off my Xoom or what? Anyone else found a solution, besides reading their purchases online?
EDIT: The attached file is what finally worked for me. Thanks to smaskell for the link.

Books works fine on the 10.1. Just grab it off another device. My guess is that the market may not know the 10.1 yet as it is not really released now aside from IO.
Sent from my HTC Vision using XDA Premium App

I wasn't able to install the tablet version but I did manage to push it to /system/app/ and it works.
1. get root access
2. download busybox
3. adb push busybox /sdcard
4. adb push BooksTablet.apk /sdcard
5. adb shell
6. cd /sdcard
7. su
8. mount -o remount,rw /system
9. ./busybox cp busybox /system/bin - yes, I'm using busybox to copy itself
10. busybox cp /sdcard/BooksTablet/apk /system/app
and you're good to go!

I'm still struggling with this and I've tried installing (via adb, adb shell, and via Astro / app manager) both a BooksTablet.apk (with and without BooksTablet.odex) from a stock Xoom dump and with a copy from my Honeycomb 3.1 Xoom. Am I missing something? Installing always fails and simply putting the files in place does nothing as well (with a reboot). Anyone have any more ideas? I'm out at this point and it seems as if it should be so simple from what you guys are saying! Thanks for the help!

have you tried a deodexed version of the apk?

I have not and cannot seem to find these files anywhere and am not sure how to deodex the files I have. I tried the 1.2.7-dev version of baksmali with no luck. Any other thoughts or perhaps a link to the files you used that seemed to work? Thanks!

I used the one from this thread
http://forum.xda-developers.com/showthread.php?t=1071047
works like a charm

Case closed
Perfect! Thanks for the link, one of the two files in that thread worked like a charm! In case anyone else is looking for it, I've attached the file that worked for me.

Each time I try installing the BooksTablet.apk file provided above, it fails on the device. When I try installing it via "adb install BooksTablet.apk" it constantly fails with the error "INSTALL_PARSE_FAILED_NO_CERTIFICATES"
I took a look at the logcat output and it seems to be having an issue finding the "fallback_covers.png" file in the assets folder.
I tried renaming the apk to .zip and poking around and I was not able to find this file.
Anyone else having this issue when installing the Google Books app?
I searched around regarding the error message on installation and the solution is to uninstall the app and reinstall it. But because I don't have the app installed to begin with then this isn't an option.
Any help would be greatly appreciated. Thanks.

yeah, I had the same problem. The only way I got it to work was by pushing it to /system/app. see my earlier post for details.

Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader

nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
Did you try navigating to the apk and launching it?

nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
While I did have BusyBox installed, I can only vouch for the last thing I did that wound up working since I'd tried so many different things before getting the right APK. So once I had the file in the first post (and of course a rooted GT 10.1), I opened a shell, mounted the /system directory for read/write, chmod'd the app directory to 777, pushed the APK into the /system/app folder and then chmod'd the directory back to 644 (IIRC?). So the steps would have been:
1. adb shell
2. su
(if you get a permission denied error, make sure you leave your screen on and accept the prompt by Superuser Permissions, I forgot this on the freshly rooted tablet the first time)
3. mount -o rw,remount /system
4. chmod 777 /system/app
(now either exit the shell or open a new command prompt)
5. adb push BooksTablet.apk /system/app/BooksTablet.apk
(now back in your su'd adb shell)
6. chmod 644 /system/app
(you'll probably want to note what permissions were there previously as I'm going from memory)
There was no need to launch the APK or issue an install command (it fails anyway), the Books app appeared right away in my app drawer but got a FC after only a moment of it being opened the first time. After a reboot, everything has been working just like on the Xoom!

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.