Database Users

How do I know that my phone (legend) is rooted or not?

hi firends
How do I know that my phone (legend) is rooted or not?
what are Symptoms for a rooted phone?

Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.

Liquid211 said:
Enable usb debugging, install driver, open cmd, type adb shell and press enter. Then type su and if you get this # you are using a rooted rom. If it says access denied you are not.
Click to expand...
Click to collapse
1- how to install driver?
2- please see this picture and tell me what is wrong...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you haven't even installed ADB I don't know how you would think your phone is rooted? Did you buy it used?
Anyways. Download this ADB. Unzip to c: and run adb.exe shell from a cmd in c:\android-sdk-windows\tools
But make sure you install the driver first.
Go to Settings, Programs, Development and Tick Off "USB Debugging". Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.

thanks Liquid211 very much!

Liquid211 said:
... Then when you connect your device to your computer it ask for a driver. It can be located in the android-sdk-windows folder under usb_driver.
Click to expand...
Click to collapse
I have no such folder under "android-sdk-windows". I only see "add-ons", "platform" and "tools"...

just try a app that needs root rights.
for example many screenshot apps need su.
another way would be to look if u ve got the superuser app in ur app menu.
and ofcause a terminal like program could help to indicate if uve got root rights.

Simply download a terminal emulator from market and type 'su'...
Sent from my Legend using Tapatalk

[SOLUTION] How I got ADB to communicate with my Kindle Fire HD!

Originally when I tried rooting my Kindle Fire HD on 7.2.3, ADB Devices wasn't showing my Kindle Fire HD device. So, a solution to my problem was installing the Google USB Driver from my Android SDK Manager. After the installation, I was able to open up CMD (Administrator) and see if ADB Devices would show my Kindle Fire HD. Bingo! It appeared!
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After:
-
I'll probably be asking what method I used, and I was using this thread:
http://forum.xda-developers.com/showthread.php?t=2049288
My computer is:
WINDOWS 7 X64
--
Proof of my root:

ADB Server Out of Date
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip

if updating adb doesn't work...
prokennexusa said:
Great post. I If updating the driver does not do the trick, update the ADB daemons. Here are the latest versions:
https://dl.dropbox.com/u/54456659/ADB%20Update.zip
Click to expand...
Click to collapse
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515

ADB Communication Issues
bbanghyung said:
And if updating ADB daemons doesn't work try this -> (this is the problem I had)
I was also having trouble getting adb to see the device, even though Composite ADB Interface was there in the Device Manager. After much searching, I found that I needed to put 0x1949 in C:\Users\<my name>\.android\adb_usb.ini. Neither the file nor the directory existed on my system, so I created them both and put that number on a line by itself, saved the file, unplugged/replugged the Fire, and it worked!
found here: http://androidforums.com/kindle-fir...6683-root-kindle-fire-hd-7-a.html#post5363515
Click to expand...
Click to collapse
bbanghyung,
Great work and informative, thank you.
I love this community, we work together
for everyone's benefit. Keep up the great
work.

Nexus 4 Not Recognized by ADB in Mac OS X

Hi Folks,
I am running Mac OS X 10.8.2 and I have ran into the following issues. I am trying to root a friend's Nexus 4 that's on 4.2.2, unlocked bootloader and USB debugging enabled/on.
I can easily root this on my Windows desktop but I thought I'd try out the Mac. Do note that I am not getting the "Allow USB Debugging" message that pops up on the phone when you connect it to a computer normally and you select Allow for the respective RSA key. The one that shows up after 4.2.2 is updated from 4.2.1.
I am not getting the above prompt when hooking up the phone to my Mac. *PS I removed the name of my MBP pro and the user name.
Okay so here are the two issues/scenarios:
1) I downloaded the latest ADB and Fastboot Mac OS X 64 bit files from the ADB dev tools website, etc. The files are "adb" and "fastboot"
When I type "./adb devices" since the "./" command is for Mac on the terminal, I get the following message and it does not show up any device listed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then when I type "./adb reboot-bootloader", I get the following:
__________________________________________________________________________________________________________
2) When I use an older adb and fastboot files from last year: "./adb_Mac" , "./fastboot_Mac" and "ADB-Install-Mac.sh", I get the following:
When I type in the adb devices command and the adb reboot-bootloader command:
The serial # shows up this time (Again I have crossed out half of it lol)
When typing in the reboot-bootloader command:
Now to my knowledge, I know that I am getting the device offline mode based on using the old ADB and Fastboot files. So the way to fix it, is to download the updated files but it doesn't result in anything at all.
With the updated ADB and fastboot files, and by booting into fastboot mode manually and then typing in ".fastboot devices", I get the Error Could Not Get Pipe Properties error in a loop.
Would appreciate the help folks!
T.I.A

Try this command
adb kill server
adb start server

scream4cheese said:
Try this command
adb kill server
adb start server
Click to expand...
Click to collapse
Beauty! I didn't know that it has to be done for the same in OS X. Query, does this have to be done every time or?

Big problem (I think)

I've tried rooting my Nexus 7 and not sure what's gone wrong.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?

UrbanDesigns said:
I've tried rooting my Nexus 7 and not sure what's gone wrong.
This is what happens when I load CWM.
Prior to this point what I did was unlock the bootloader and then process to flash CWM, then load CWM and flash SuperSU from sdcard but it's gone a bit wrong.
Anybody got an ides what the hell I've done wrong?
Click to expand...
Click to collapse
Hi, UrbanDesigns...
Are you sure you have the correct version of CWM installed on your Nexus 7 ?
The references in your screenshot to an SD Card are a bit odd, given the Nexus 7 doesn't have an SD Card.
(...and the most recent version for Nexus 7 of CWM is 6.0.3.6... your screenshot shows your version to be 6.0.2.3).
Download the correct CWM recovery image from here for either your 'tilapia' (3G & WiFi) Nexus 7 or your 'grouper' (WiFi only) Nexus 7... whichever one you have.
And fastboot flash it with...
Code:
fastboot flash recovery recovery.img
...where recovery.img is the actual name of your recovery image file. Personally, I just think it's easier to rename it to recovery.img, and then flash it. Less scope for typos at the command prompt.
Hope this helps... good luck.
Rgrds,
Ged.

I was following this.
For some reason windows says it does not recognize my device now, it says "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
I was following this:
http://forum.xda-developers.com/showthread.php?t=2150661
So I assume everything was correct.
The only difference is I used Minimal ADB and Fastboot
The tablet is fully functioning now but won't get recognized by my PC, it's listed as "Unknown Device" under "Other Devices"
When I try to manually select where the driver folder is it instantly fails and says windows was unable to install your unknown device

Problems with codeworkx TWRP (zl0)

Hello,
I am having problems with adb recognition on recovery mode. I did manage to contact codeworkx, but it seems it's just me, because for him it's working. The drivers are installed correctly, because adb sideload works just fine. I want to use the new adb backup function, to backup files right into my PC, but no recognition is stopping me. Has anyone ever had this problem? If so, any ideas on how to fix it are really welcome. Thanks in advance!

adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?

sk8223 said:
adb backup isn't particularly useful because it doesn't backup stuff like SMS.
By recovery, do you mean fastboot mode? And only the adb command doesn't work? That's strange. Have you tried switching the cable or trying a different PC? What error are you getting?
Click to expand...
Click to collapse
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

punpun1 said:
Hello, I understand that it doesn't backup things like sms, I just need the system, data, and boot backed up directly to my PC. By recovery I mean recovery and not fastboot. The adb command works, the device is just not showing up in adb devices, that's why I can't do adb backups, although this feature was implemented in TWRP a couple versions back. What's strange that when I try using adb sideload, the device is detected perfectly fine, which means not a driver problem.
Leaving a picture. First adb devices ran when in main recovery screen, second adb devices ran when in adb sideload mode. (Detected!)
Click to expand...
Click to collapse
That's not recovery, that's simply adb.
Are you sure you're using the correct command? Read this: https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
I just tried using adb backup with my device and it works fine. You're supposed to do it from within actual ROM itself, not TWRP. So boot into your ROM and try again.