• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How to root on Linux

FergatROn

Newbie
Hi, I'm running Fedora 18 (x86) and I can't get this LG Spirit to show up in my OS. I'm trying to get the OS to recognize it so I can then use adb to root the darn thing. The connection methods: charge only, sync with windows media, etc doesn't work. Thanks for any guidance.
 
Hi Justin, not sure about the link. It's about a choosing a car charger and not about rooting my phone in linux.
 
Hi Justin, not sure about the link. It's about a choosing a car charger and not about rooting my phone in linux.

lmao hey ferga, thanks for making my day :laugh:. About your rooting problem, there's not really anything i can help you with.

Do you just have one os or a dual boot?
 
Hey Cubone. I just have one OS. I thought about it and if push comes to shove then I can fire up a VM of Windows. I'm trying to stay away from that method.
 
Not sure. I'll have to look into USB libraries. When I plug in other android devices they show up. It's just this uprooted phone that doesn't.
 
Hi, I'm running Fedora 18 (x86) and I can't get this LG Spirit to show up in my OS. I'm trying to get the OS to recognize it so I can then use adb to root the darn thing. The connection methods: charge only, sync with windows media, etc doesn't work. Thanks for any guidance.

What is the output of:

Code:
lsusb
 
Interesting... LG Electronics, Inc. must be the LG Spirit. Good call.
[HIGH]$ lsusb
Bus 001 Device 009: ID 1004:6300 LG Electronics, Inc.
Bus 003 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 003 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[/HIGH]
So; I then ran the following command, but no success.
[HIGH]$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[/HIGH]
 
Interesting... LG Electronics, Inc. must be the LG Spirit. Good call.
[HIGH]$ lsusb
Bus 001 Device 009: ID 1004:6300 LG Electronics, Inc.
Bus 003 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 003 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[/HIGH]So; I then ran the following command, but no success.
[HIGH]$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[/HIGH]

Before we go crazy and try a million things to get adb working, you did enable USB debugging in developer options, right?
 
Sometimes udev rules need to be setup. If you haven't already done so, follow these steps.

Assuming Fedora uses gedit enter the following command...

sudo gedit /etc/udev/rules.d/99-android.rules

When the rules open, go to the end and copy/paste the following and save it:

HTML:
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004:6300", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"TEST=="/var/run/ConsoleKit/database", \RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Now enter this to restart udev or you can reboot:
sudo service udev restart

Now check to see if you're good:
Enable usb debugging then plug to PC and enter...

./adb devices
 
Before we go crazy and try a million things to get adb working, you did enable USB debugging in developer options, right?
Yes I did. :eviltongue:
Oh my goodness I feel like such a noob. I assumed "USB debugging" was on. I looked at it again and realized that it was grayed out because I already had the device plugged into the computer. Once I unhooked it I had the option to select it. :pound: Thanks for simply suggesting the obvious.
 
Back
Top Bottom