Database Develop

instructons

how do you send this to the g1 using adb
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
can someone send step by step instructions of how to do this so i can bypss the activation screen without using wifi

[Q] After installing custom rom - Phone isn't rooted

Hey all, I rooted my phone using SuperOneClick, Was fine, restarted my phone all good. Then I decided to install a custom rom, That also worked all fine except now that I've installed it, my phone seems to not be rooted (I checked using root checker before installing rom and after, said it was rooted before, But now it says it's not rooted) What could be causing this? I've repaired it and started over 3 times with the same result. Could someone please shed some light? Thank you.

Try with other custom rom....maybe rom that you installed causing it
Sent from my Shakira using XDA App

Some roms like, per exemple, HAKA's Original W8 Room aren't rooted!
Try another rom or, try rooting that rom

Oh ok, thanks for the reply, tried rerooting, it ended up going to not responding, I have access to system files, the su file is there, but I don't know about the other files that allow the device to be rooted. Is there some way I can copy and paste the rest of the su binary's? The ROM came with super user app so I just assumed it was rooted.
Sent from my X8 using XDA App

Which Tom, clone tell us a little bit more
Sent from my Xperia X8 using XDA App

Running; cm7-138 (2.3.4)
Found it here; "
Code:
http://forum.xda-developers.com/showthread.php?t=914513"
Info from Root Checker;
Code:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System environment PATH: /sbin/vendor/bin/system/sbin/system/bin/system/xbin
The adb binary is set to default shell user access is root
Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx 1 0 0 15 oct 19
22:21 /system/bin/su -> /system/xbin/su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-xr-x 1 0 0 26332 aug 1
2008/system/xbin/su
Alternate su binary location
ls: /sbin/su: Permission denied
Alternate su type binary location:
ls: /system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
I'm not sure if that was any help, put it there just incase.
Hope that's enough info, If you need more just ask

[Q] Rooted but no root access?

First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?

clyde1914 said:
First, here is what root checker pro says about my root
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2013-07-02 09:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your DROID BIONI
I've had my verizon droid bionic rooted for a few months now on ICS using razors edge. Then I used Voodoo OTA root to temp unroot and updated to Jellybean. I restored root and everything was fine. So then I tried to install busy box after, but superuser wouldn't come up. So I deleted superuser and reinstalled it. Now Root checker says I don't have proper root access. (Also root browser still works fine) All other apps instead of having a su prompt they say I'm not rooted. Whats happening to my phone?
Click to expand...
Click to collapse
Try rebooting.

If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link Here. If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.

nobe1976 said:
If rebooting it doesn't work, it might be because when installing the busybox something on the System side messed up. The only way to fix this would be to HOB with Data and the re-rooting the device. Everything which can be found through this link If you don't run a Linux distro this can be ran off of a Live USB setup. You can make a simple one using a 4 or 8 gig USB thumb drive and make sure that you let it make some space for updates and adding files. I would keep this around just for the fact that you don't need any specific drivers to run on Linux like you need on Windows. There are treads that have instructions on using Windows to get this done, but I would say that Ubuntu would be the best way to accomplish anything. Best of Luck.
Click to expand...
Click to collapse
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.

clyde1914 said:
Would it brick if I flashed it using RSD Lite? Just wondering because I've done that before and am familiar with it. If not, yes I do have Windows, not Linux, so I can try the HOB.
Click to expand...
Click to collapse
I would stick with the HOB just to keep the data. The only route I have found that will successfully re root it is done with Linux. It can be done running Linux on a thumb drive as long as there was space created for updates.
Sent from my XT875 using Xparent Red Tapatalk 2

If that doesn't work and you need restore it to JB, here are the relevant links:
FXZ files for Bionic:
http://forum.xda-developers.com/showthread.php?t=2240725
RSD Lite Example (not for bionic, but gets you some of the links you'll need):
http://forum.xda-developers.com/showthread.php?t=2231249
If you want to try it from linux, fastboot from linux:
http://forum.xda-developers.com/showthread.php?t=1263009&highlight=fxz
And if you need to root once you flash your JB stock image, you'll need something like this:
Easy root:
http://forum.xda-developers.com/showthread.php?t=2256439

Unable to Root

I have an HTC One Dev Edition (M7) and since day 1 I have had issues with getting root access. I have had it now for a few months and it seemed like I could only have root access for a few minutes after a reboot and then root access would be denied. I finally decided to dump the stock ROM and installed Android Revolution 3.0 GE and since installing it I am unable to even obtain root at all. I have tried several different methods, nothing seems to work. I have never had an issue with prior phones, which I buy 2-4 phones a year and always unlock and root it as soon as I power it on. I have even tried using Hasoon2000's Toolkit and the root process, flashes fine but when I reboot, no root. Here is the link from Root Checker.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 366952 2008-08-01 05:00 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your HTC One device by Root Checker Pro version 1.3.3 from joeykrim in the Android Market - http://goo.gl/NcnHn
Anything thoughts?

phenixdragon said:
I have an HTC One Dev Edition (M7) and since day 1 I have had issues with getting root access. I have had it now for a few months and it seemed like I could only have root access for a few minutes after a reboot and then root access would be denied. I finally decided to dump the stock ROM and installed Android Revolution 3.0 GE and since installing it I am unable to even obtain root at all. I have tried several different methods, nothing seems to work. I have never had an issue with prior phones, which I buy 2-4 phones a year and always unlock and root it as soon as I power it on. I have even tried using Hasoon2000's Toolkit and the root process, flashes fine but when I reboot, no root. Here is the link from Root Checker.
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 366952 2008-08-01 05:00 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your HTC One device by Root Checker Pro version 1.3.3 from joeykrim in the Android Market - http://goo.gl/NcnHn
Anything thoughts?
Click to expand...
Click to collapse
go to recovery.....flash ARHD 3.0 GE...after install dont reboot....go to instal and point to the file you downloaded from:
http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip then reboot...you should have your root back:good:

Cool, that worked for me.
Any to thoughts on why with the stock ROM I would lose root after a few minutes? Doesn't really matter now but I am curious to why this was happening.

Probably you did not hit thanks button after somebody helped You...
LOL

Never noticed it before.

[Q] Incredible S root issues

Hello, I tried to root my Incredible S yesterday and had some issues.
It doesnt seem to be rooted.
****Bootloader
BlackRose
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3805.06.03.03_M
****Recovery
ClockworkMod Recovery v5.0.2.0
****SU
Supeuser 3.1.3-arm-signed
****Rom
VivoKat_BETA_#1_#11.18
****Kernel
3.0.101 ck1 TESCO v3.1 g580ad1b [email protected] desktop #2
Ive rooted Android phones before but never a HTC though... what can be the problem? Here is the data from Root checker pro:
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 2008-08-01 14:00 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2013-11-27 16:06 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your Incredible S S710e device by Root Checker Pro version 1.3.5 from joeykrim in the Android Market
Click to expand...
Click to collapse
Ive tried fix permissions from clockword recovery in the advanced tab..
Any suggestions?

It might be a ROM problem, open Superuser and disable the CM-Root-Setting thingy
and Reboot

Gizmo648 said:
It might be a ROM problem, open Superuser and disable the CM-Root-Setting thingy
and Reboot
Click to expand...
Click to collapse
That and you probably forgot to flash the latest supersu.
I believe the latest version is v1.7.5

Gizmo648 said:
It might be a ROM problem, open Superuser and disable the CM-Root-Setting thingy
and Reboot
Click to expand...
Click to collapse
072665995 said:
That and you probably forgot to flash the latest supersu.
I believe the latest version is v1.7.5
Click to expand...
Click to collapse
Thanks a lot! It worked perfectly