Database Users

Get Apk file from Market

When i download and install an App from the Android Market where the Apk installation file is temporary placed? Which path?
tnx in advance

the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.

Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...

sidvizioso said:
Tnx for the answer mopodo, but if i hard reset the device, can i will use theese files to reinstall them?
i'm sorry for my bad english...
Click to expand...
Click to collapse
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.

So which is the temp path of the downloaded apk from market?
i want to grab them...

Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
of course you can.
you just have to copy them to your sdcard or pc an install them again, with «adb install something.apk» or «Astro File Manager» (or a similar file managerapp)
a hard reset will delete everything on «/data»

If you have root copy the contents of both folders to your SD card.
mkdir /sdcard/apps
cp /data/app/* /sdcard/apps
cp /data/app-private/* /sdcard/apps
Then after you wipe (I've never heard anyone call it a 'hard reset' before) you can use an app like Astore or ApkInstaller to reinstall them.
If you don't have root then not only will you not be able to read app-private, but your ROM wont have busybox so you wont be able to bash in those commands. In that case use an app like Astro or AppManager to copy non-private apks to the sdcard, but for private apps you'll have to redownload them (without being charged of course.)
Pinesal said:
No, you can make a backup to your SD card with apps like MyBackup or Backup For Root Users.
Click to expand...
Click to collapse
Only if they're non-private (reside in /app, private being /app-private).

He's probably coming from WinMo. We called a factory reset/wipe a hard reset.

mopodo said:
the apk's are stored at /data/app and /data/app-private after you installed the app and will be removed if you uninstall it.
Click to expand...
Click to collapse
Slightly off topic lol But i see you said Private does that mean you could manually back up Private apps you buy off market by just copying them /w root access?

When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.

You could try an app manager and back 'em up from there.

Just try the following command.
busybox cp /data/app/* /sdcard/<your backup loc>
askwhy said:
When I run the following from an adb shell, with or without SU root:
cp /data/app/* <my location on sd>
I always get:
cp: permission denied
In fact, no matter how or where I cp from or to, and no matter what I am trying to copy, even if I leave all arguments blank, I still get "cp: permission denied" -- I have busybox installed in /system/xbin from /data/local and as far as I can tell it installed ok. Phone is a rooted Sprint hero 1.56.651.2 running stock ROM.
I have also tried to 'adb pull /data/app' and it always find 0 files. None of this is a big deal for me, however, as I am just trying to backup a bunch of apks for free apps in case versions change too much. Mostly just curious...
Any ideas?
EDIT: Both Astro and AppManager handled the (non-private) apk backups fine -- so I have no real need for the cp method to work, but I am still wondering why it will not -- is it the adb shell? must I use a terminal emulator from on the phone instead? something else? Anyways, if I really want to pursue it, perhaps I should take it to a busybox thread at this point...
EDIT2: It appears as if the 'cp' command as I was running it wasn't getting passed through busybox (not sure why). From what I can piece together reading other threads, it seems that if you have installed busybox on top of a ROM that doesn't already have it (like stock, after rooting and recovery setup) than you must prefix commands with 'busybox' when entered, as in 'busybox cp /data/app/* <my location>' and it does work for me that way. Still cannot seem to copy /data/app-private which I thought having root access would allow -- I guess I just don't understand nearly enough about busybox implementation, linux permissions, and, well, linux in general.
Click to expand...
Click to collapse

Well in windows
'adb pull' is used if that helps

(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?

[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!

[Q] Rooting a rooted Verizon Droid 2 to Gingerbread 4.5.601.A955.Verizon.en.

Does GingerBreak work with this version of Gingerbread 4.5.601.A955.Verizon.en.us? My phone is currently rooted with Z4Root 1.3. Is there an easy way of doing this?
Sam

Use the d3 root method. Works fine.
CM7GB-601

The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?

acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I have the phone in PC Mode (instead of Mass Storage.) I don't know if that makes a difference.
The D3 Method worked great for me and my wife's phone.

Hi everyone,
I have the same question as CSSZiegler, but want to expand on it a little bit...
I have a Droid 2 that was rooted with Z4Root 1.3 several months ago. I also have SetCPU, SuperUser and Titanium Backup. No custom ROMs installed. Big Red just pushed down GB, and of course, I've lost root access. I'd like to regain root again without losing any contacts, Handcent messages, etc. I've read on several forums that the D2 can be rooted just like the D3 with a simple "one-click" operation referenced by quarky42 earlier.
Any opinions or experience with this? I greatly appreciate any and all assistance!

update
My phone downloads the update, I click install now... it reboots and starts the install, then about 35% of the way through, it turns to a triangle with ! Inside. Phone reboots and displays message software update failed. Anyone know where to find a logfile or have any suggestions?
Droid2 android 2.2.. rooted. No custom rom.

Did you fully SBF to stock using RSDLite?
Also http://forum.xda-developers.com/showthread.php?t=1246673 has a flashable version.

I will as soon as I get a computer again, thanks for the link. Unfortunately my mobo died yesterday. So I was hoping for an alternative solution. It would also be nice to keep all my texts.. I'll google that one.
So any ideas on the logs or an alternative solution?

Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.

Ardalee said:
Ok... I have also used Z4root. I got the update, it failed. I unrooted with Z4root. Re-downloaded the update, it failed. I tried to reinstall the kindle and blockbuster app. Re-downloaded the update, it failed. I reset to factory. Re-downloaded the update, it failed. Downloaded root checker, ran root checker, it said that I am not rooted. Re-downloaded the update, it failed.
This is the Detailed Results I got from the Advanced Root Checker:
Root Access is not properly configured or was not granted.
Superuser.apk - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your DROID2 device by Root Checker version 3.7 from joeykrim in the Android Market -
___________________________________________
Have I done something wrong??? I don`t understand why I can not get the update. Please help.
Click to expand...
Click to collapse
I answered the thread you started with the process to un root and put your phone back to stock.

acavallini said:
The D3 one click didnt work for me. It tries to reboot and the phone sits at the "Battery OK OK to Program Transfer Mode: USB" mode.
I was rooted before the update. I never used ROMS or anything just rooted for wireless tether and T backup. Not sure how to proceed but Im pretty happy with the update, fixed a bunch of issues for me.
Anyone else not able to root after the ginger ota?
Click to expand...
Click to collapse
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.

808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
Awesome! That did the trick, thanks for the info

808Bill said:
I had the same problem, and I think it is is because we already had Superuser installed. To remove it, from the directory where you downloaded the one click root, open the command window, then type adb shell
when you hit enter, the next line should end with a #
if it's $, run the one click again, then start this over
once you have the # prompt, type
mount -oremount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
hitting enter after each line.
After doing this, run the one click, and it should be fine. Worked great for me.
Click to expand...
Click to collapse
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.

droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
I would SBF back to Froyo with RSDLite and install the OTA GB from phone info updates. After that use the D3 one click root method and you're golden.

droid888 said:
I'm having the same problem as the original poster... Installed gingerbread with z4root... phone was already rooted.. Now I have superuser and can't get rid of it.. .Tried unrooting through z4 and it doesn't work... Tried gingerbreak and the one click root through windows... Neither of those worked...
I either want to root through gingerbread or just get rid of the superuser.
when I type adb shell in command prompt (in windows 7) it says adb is not recognized as an internal or external command, operable program or batch file.
Any ideas? Thanks.
Click to expand...
Click to collapse
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.

acavallini said:
That error is usually because your trying to run the program from the wrong directory. Make sure your command line is started from the folder that adb.exe is located in. You can do this by Shift and right mouse button and “open command window here”.
Click to expand...
Click to collapse
I searched the phone's sd card.. I couldn't find it... do you know where adb.exe is located?

The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.

idefiler6 said:
The fact that he said to hold shift and the right mouse button should tell you he's talking about a folder on your computer and not on your SD card.
Click to expand...
Click to collapse
Finally got it to work... now.. I used motorola one click root.exe where you use the exe on the computer. Just out of curiosity, is there a one click method to unroot? Thanks!

semi-success: delayed update to 6.3 and preserved root

This did not go exactly as I had planned but it ended up ok anyway and I learned some.
I am using a rooted stock rom. First, my idea was to prevent the auto update to 6.3. Second, I wanted to see if it was possible to somehow preserve root so that I wouldn't have to re-root after the update, because I am not really thrilled by the idea of installing a new boot loader and so on; I would prefer to make the minimum modifications necessary to do what I need.
The first goal appeared to be well-served by using droidwall. I used whitelist mode and blocked everything that I couldn't tell had an obvious need to access the net. I posted more detail here. From the time the update started going out until today when I had time to actually try my update, I did not receive the update automatically. So that appeared to work.
Next, my idea was to simply make a copy of /system/xbin/su to a place that wouldn't get overwritten by the update.
# mkdir /data/lunchmeat
# cat /system/xbin/su > /data/lunchmeat/salami
# chmod 6755 /data/lunchmeat/salami
The idea being that since it's still setuid root, I'd be able to execute it and become root after the update. (I just picked a silly name in case something looked for su and blew it away).
So, I turned off wifi, disabled droidwall, manually updated (copied the updates into kindleupdates and so on) and after it rebooted, I opened the terminal app and tried to execute my salami binary. I got permission denied, and the superuser app said that superuser permission was denied on the terminal app. Hmmm....
Couldn't figure out why it was behaving that way so I thought I'd try adb root, and whadya know, I had a root shell.
remounted /system read-write, copied su back into /system/xbin, renamed /system/bin/check_rooted to /system/bin/check_rootedx, created an empty executable /system/bin/check_rooted, and rebooted...
...and everything is (rooted) as it was before. I re-enabled droidwall. google play seems to be working.
Why did 'adb root' work for me after the update? That might be a good question to answer, since it could make the re-rooting process much simpler for people! 2 or 3 commands and you're done.
edit: ohhhhh, stupid me! /data is mounted nosuid. / seems to get blown away on every reboot, so even if I remount it read/write and put su there, it gets lost.
And, also, I just remembered that I did what jcase said in this post which is what allowed me to keep adb root working.
So, so far this idea is going nowhere.