Database Develop

[Q] Rooting Kindle Fire HD On Ubuntu 12.04(Linux)

I just bought a kindle fire the new ones and was wondering how do i go about rooting the kindle fire through adb on ubuntu?? i dont understand how i install the adb drivers and also do the same rooting commands work for ubuntu as they do in windows?? any help would greatly be appreciated as i cant use a windows system at the moment

install a virtual box (learn about that if you dont know what it is) and run windows

All you really need are the fastboot and adb binaries. You can install these out of the Android SDK. If you run them as root, it should work just fine. Otherwise, you need to insert the proper udev rules to give an unprivileged user access to the device. All of the rooting commands are the same. The only thing you really have to worry about is changing file path syntax from Windows to Linux, but I don't think there's any of that in there.
You could probably use soupkit for the original KF for the binaries and getting your linux environment setup.

Yes it should be the same, once you're in adb. The big difference is that linux usually doesn't require drivers for different phones. Instead you need to configure your udev rules. I'm running Debian and have a file at /etc/udev/rules.d/51-android.rules that looks like this:
#Acer
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666", OWNER="jack"
#Dell
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666", OWNER="jack"
#Foxconn
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666", OWNER="jack"
#Garmin-Asus
SUBSYSTEM=="usb", ATTRS{idVendor}=="091E", MODE="0666", OWNER="jack"
#Google
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", OWNER="jack"
#HTC
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666", OWNER="jack"
#Huawei
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666", OWNER="jack"
#Kyocera
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666", OWNER="jack"
#LG
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666", OWNER="jack"
#Motorola
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="jack"
#Nvidia
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666", OWNER="jack"
#Pantech
SUBSYSTEM=="usb", ATTRS{idVendor}=="10A9", MODE="0666", OWNER="jack"
#Samsung
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", OWNER="jack"
#Sharp
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666", OWNER="jack"
#Sony Ericsson
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666", OWNER="jack"
#ZTE
SUBSYSTEM=="usb", ATTRS{idVendor}=="19D2", MODE="0666", OWNER="jack"
#Casio
SUBSYSTEM=="usb", ATTRS{idVendor}=="04f2", MODE="0666), OWNER="jack"
#Google
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666", OWNER="jack"
#kindle hd
SUBSYSTEM=="usb", ATTRS{idVendor}=="1949", MODE="0666", OWNER="jack"
Click to expand...
Click to collapse
Once you create this file, you need to reload your udev rules and restart the adb server if it's running.
udevadm control --reload-rules
adb kill-server
adb devices
Click to expand...
Click to collapse
Honestly I still can' seem to get the Kindle Fire HD to show up in adb. But usually this does it, you just need the vendor id. You can find it with the lsusb command.

[GUIDE] Convert Your Nexus into KaliPwn Phone

for other devices follow this
****i am not responsible for your phone or anything you do with aircrack-ng
this guide will help you, do what a $1,295.00 PWN PHONE can!!
{
"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"
}
------------------------------------------------------------------------------------------------
Things You Need
------------------------------------------------------------------------------------------------
1) Nexus 5 (rooted)
2) OTG Cable
3) list of USB supported
.TP-LINK TL-WN722N(confirmed by me & DragonHunt3r)
.Linksys WUSB600N V2 (confirmed by DragonHunt3r)
.TP-LINK TL-WN725N V1 & V2
.ALFA Network AWUS036H
(if you have other wifi usb then just ask ill try to add it into the guide)
4) Ubuntu (to compile kernel)
------------------------------------------------------------------------------------------------
PART A
(Compiling Kernel)
------------------------------------------------------------------------------------------------
Setting up your ubuntu machine
Code:
$ sudo apt-get update
Code:
$ sudo apt-get install oracle-java6-installer
Code:
$ sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
create a file /etc/udev/rules.d/51-android.rules (as the root user)
copy paste the below code and save
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"
<username> must be replaced by the actual username of the user who is authorized to access the phones over USB.
Setting correct paths
Code:
gedit android-path.sh
cope paste the code and save it
Code:
export CC=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export CROSS_COMPILE=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
export SUBARCH=arm
export PATH=$PATH:$(pwd)/andorid_boot_tools_bin
Make it executable and source to current terminal window.
(you need to source it to your current terminal window before you compile)
Code:
$ chmod +x android-path.sh
$ source android-path.sh
Download Source (any kernel source can be used)
ElementalX Kernel Source
Franco.kernel Source
Android Kernel Source
using andoid kernel source
Code:
$ git clone https://android.googlesource.com/kernel/msm.git
Code:
$ cd msm/
$ git branch -a
$ git checkout origin/android-msm-hammerhead-3.4-kitkat-mr2
Code:
$ make hammerhead_defconfig
$ make menuconfig
Adding required drivers
For TP-LINK_TL-WN722N
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN722N"]wikidev[/URL] will tell you that TP-LINK TL-WN722N uses [URL="http://wireless.kernel.org/en/users/Drivers/ath9k_htc"]ath9k_htc[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]ath9k[/URL] drivers in kernel
To enable ath9k, you must first enable mac80211 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable ath9k through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > cfg80211 - wireless configuration API
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable ath9k in the kernel configuration under
Code:
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Atheros Wireless Cards ---->
< * > Atheros 802.11n wireless cards support
< * > Atheros HTC based wireless card support
save and exit menuconfig
check in your .config file if you have them enable(its a hidden file)
Code:
CONFIG_ATH_COMMON=y
CONFIG_ATH9K_HW=y
CONFIG_ATH9K_COMMON=y
CONFIG_ATH9K_HTC=y
[/CODE]
For TP-LINK TL-WN725N V1 & V2
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v1"]V1[/URL] & [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v2"]V2[/URL] wikidev will tell you that TP-LINK_TL-WN725N uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl819x"]rtl8192cu[/URL] & [URL="https://github.com/lwfinger/rtl8188eu"]8188eu[/URL] drivers
To enable rtl8192cu & 8188eu, you must first enable rtl8192cu & 8188eu through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8192cu & 8188eu through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter
For Linksys WUSB600N V2
Code:
quick look in [URL="https://wikidevi.com/wiki/Linksys_WUSB600N_v2"]wikidev[/URL] will tell you that WUSB600N V2 uses [URL="http://wireless.kernel.org/en/users/Drivers/rt2800usb"]rt2800usb[/URL] drivers
To enable rt2800usb, you must first enable rt2800usb through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rt2800usb through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Ralink driver support ---->
< * > Ralink rt27xx/rt28xx/rt30xx (USB) support -->
< * > rt2800usb - Include support for rt35xx devices (EXPERIMENTAL) (NEW)
< * > rt2800usb - Include support for unknown (USB) devices
For ALFA Network AWUS036H
Code:
quick look in [URL="https://wikidevi.com/wiki/ALFA_Network_AWUS036H"]wikidev[/URL] will tell you that AWUS036H uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl8187"]rtl8187[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]rtl8187[/URL] drivers in kernel
To enable rtl8187, you must first enable rtl8187 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8187 through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > Common routines for IEEE802.11 drivers
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable rtl8187 in the kernel configuration under
Code:
[CODE]
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek 8187 and 8187B USB support
save and exit menuconfig[/CODE]
save and exit menuconfig if you dint do it
now your ready to compile
Code:
make -j4
this will take some time to compile
you should get something like this in the end
Code:
Kernel: arch/arm/boot/zImage-dtb is ready
now you need to get a boot.img from any nexus 5 rom and place it in boot_img (create this folder where you earlier downloaded the toolchain and the kernel)
Code:
$ cd .. # if you was in msm directory
$ git clone https://github.com/pbatard/bootimg-tools.git
$ cd bootimg-tools/
$ make
$ cd cpio/
$ gcc mkbootfs.c -o mkbootfs -I../include
$ cd ../..
$ mkdir andorid_boot_tools_bin
$ cd andorid_boot_tools_bin/
$ cp ../bootimg-tools/mkbootimg/mkbootimg .
$ cp ../bootimg-tools/mkbootimg/unmkbootimg .
$ cp ../bootimg-tools/cpio/mkbootfs .
$ cd ..
time to create your own boot
Code:
$ unmkbootimg -i boot_img/boot.img
$ cp msm/arch/arm/boot/zImage-dtb kernel
$ mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x02900000 --second_offset 0x00f00000 --tags_offset 0x02700000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1' --kernel kernel --ramdisk ramdisk.cpio.gz -o boot.img
install the boot.img to your phone (this wont flash the kernel, it will temporarily boot with this kernel, after you restart you will go back to what ever kernel you had before
Code:
$ adb reboot bootloader
$ sudo fastboot boot boot.img
------------------------------------------------------------------------------------------------
PART B
(setting up your phone)
------------------------------------------------------------------------------------------------
For TP-LINK_TL-WN722N
Code:
download the firmware files [URL="http://wireless.kernel.org/download/htc_fw/1.3/"]here[/URL]
1. htc_7010.fw
2. htc_9271.fw
For TP-LINK TL-WN725N V1 & V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YWlVaZ1NFRDF4RTA&usp=sharing"]here[/URL]
For Linksys WUSB600N V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YMGZTcjJ2ei10V1k&usp=sharing"]here[/URL]
1. rt2870.bin
For ALFA Network AWUS036H
Code:
hopefully nothing to do here,... if it doesnt work let me know
copy them to your phone
use a file manager with root to copy firmware files to /system/etc/firmware/
install Linux deploy on your phone
fire up linux deploy and go to properties-->Distribution and select kali linux
installation path set to /sdcard/linux.img
hit the install button
after installation click start button
start your favorite ssh program and happy aircrack-ng
(SH credentials are “android” for the username (configured via Linux Deploy) and “changeme” as the password.)
​

hello ... how did you get those two lines of commands on the keyboard ?!

which command are you talking about?
you should use the commands one by one

chiragkrishna said:
which command are you talking about?
you should use the commands one by one
Click to expand...
Click to collapse
If I'm not mistaken, I believe he means your screen shot. In terminal with Ctrl, alt, etc above the keyboard.

you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1

chiragkrishna said:
you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1
Click to expand...
Click to collapse
Love this reply.Honestly if u don't know how then you should not be trying it
Sent from my Nexus 5 using Tapatalk

What does this do, get you better WiFi connection in terms of speed/stability?

Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app

GT-af said:
Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well..... It could, just not the way he was probably expecting

Pretty cool tut I must say, I'm wondering, could you make it support aswell the Wusb600n v2 ? that's what I'm currently having as usb wifi

added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!

chiragkrishna said:
added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!
Click to expand...
Click to collapse
Oh woow cool, will test this out when I'm home
Hopefully packet injections etc will work ^.^

parker09 said:
What does this do, get you better WiFi connection in terms of speed/stability?
Click to expand...
Click to collapse
Yes, it turns your Wi-Fi into a 1Gb/s power house regardless of the connection you're on.
To test do this:
1 - hook up your dial-up cable and modem/router/whatever
2 - connect your N5 to that network and try to open www.nike.com
3 - if it takes 10m to load, then you're on the correct network, 56k yay!
4 - flash this
5 - connect to your 56k network
6 - ???
7 - www.nike.com loads in 2s
8 - profit
-----
Nice guide OP

Testing it out right now but there seems togo something weird ?
SIOCSIFFLAGS: No such file or directory
I gave the .bin file privs 644 and when trying airodump it says
Gave wlan1 and mon0 for fun a try... but not working

Kill the processes
867
1263
867
These are the problems..

@chiragkrishna
You know man if it works with tp-link tl wn723n ou wn725n?

...

chiragkrishna said:
Kill the processes
867
1263
867
These are the problems..
Click to expand...
Click to collapse
Killed em and the message dissapeared but it's still not working ?
http://puu.sh/b0BBg/18d9bc170b.png <- click the image

Could the alfa awus036h be compatible in the future?

Orderd now the same as OP (TP-LINK TL-WN722N) and we'll see how it goes

Linux android.rules for Shamu

{
"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"
}
Hello everyone,
Does anyone know the proper udev's setting for Shamu 5.0 (LRX21O) ?
When I plug my shamu to my computer (Kubuntu 14.04) :
In normal operation with Debug Mode
A "lsusb" command from my terminal shows me shamu as Mako (Nexus 4)
lsusb said:
Bus 003 Device 015: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Click to expand...
Click to collapse
From fastboot
A "lsusb" command from my terminal shows me shamu as Google Inc.
lsusb said:
Bus 003 Device 016: ID 18d1:4ee0 Google Inc.
Click to expand...
Click to collapse
From recovery (stock), "lsusb" doesn't show anything
"adb devices" doesn't show anything under "List of devices attached"
I didn't find anything on Linux-usb.org/usb.ids or with a search on Google
Edit : If I boot TWRP with command fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
A "lsusb" command from my terminal shows me shamu as Google Inc.
lsusb said:
Bus 003 Device 023: ID 18d1:d002 Google Inc.
Click to expand...
Click to collapse
If I active mtp from TWRP
A "lsusb" command from my terminal shows me shamu as Google Inc. Nexus 4
lsusb said:
Bus 003 Device 026: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Click to expand...
Click to collapse
If i select BP Tools from bootloader.
(Restart Bootloader > Recovery Mode > Power Off > Factory > Barcodes > BP Tools)
A "lsusb" command from my terminal shows me shamu as Motorola PCS
lsusb said:
Bus 003 Device 034: ID 22b8:2ea1 Motorola PCS
Click to expand...
Click to collapse
Here is my current android.rules
android.rules said:
### HTC Desire
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c87", MODE="0666"
### Iconia Tab A500
SUBSYSTEM=="usb", ATTR{idVendor}=="0502",ATTR{idProduct}=="3325", MODE="0666", SYMLINK+="a500"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955",ATTR{idProduct}=="7820", MODE="0666"
### Samsung Galaxy Y GT-S5360Arrow
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
### Google Nexus One
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="4e12", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="4e11", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="4e13", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
### Google Nexus 7 - adb protocol 16 GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e44", MODE="0666", OWNER="kowalski"
### Google Nexus 7 - adb protocol 8 GB version
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="kowalski"
### Google Nexus 7 - fastboot protocol
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0666", OWNER="kowalski"
### Google Nexus 7 - mtp protocol
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e41", MODE="0666", OWNER="kowalski"
### Google Nexus 7 - Recovery
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="kowalski"
### Google Nexus 4 & Nexus 5
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee3", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee4", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee5", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee6", MODE="0666", OWNER="kowalski"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", OWNER="kowalski"
### Android-powered
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="2d00", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="2d01", MODE="0666"
### StarAddict par SFR ZTE Skate
SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="1355", MODE="0666", OWNER="kowalski"
Click to expand...
Click to collapse
Thank you in advance

If I boot TWRP with command fastboot boot openrecovery-twrp-2.8.2.0-shamu.img
A "lsusb" command from my terminal shows me shamu as Google Inc.
lsusb said:
Bus 003 Device 023: ID 18d1:d002 Google Inc.
Click to expand...
Click to collapse
If I active mtp from TWRP
A "lsusb" command from my terminal shows me shamu as Google Inc. Nexus 4
lsusb said:
Bus 003 Device 026: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
Click to expand...
Click to collapse
If i select BP Tools from bootloader.
(Restart Bootloader > Recovery Mode > Power Off > Factory > Barcodes > BP Tools)
A "lsusb" command from my terminal shows me shamu as Motorola PCS
lsusb said:
Bus 003 Device 034: ID 22b8:2ea1 Motorola PCS
Click to expand...
Click to collapse

Flashing any ROM from TWRP or from Bootloader boot.img soft bricks device [Linux]

Hello,
I need to know what I am doing wrong. I unlock my bootloader, then I try to flash CM, but once I
run "fastboot flash boot boot.img" and restart, then phone is bricked. Only vibrates. No logo. This happened on 10.6.A.0.454 android 5.02.
I try android 4.1 rooting with DooMLoRD_Easy-Rooting-Toolkit-exploit, installing XZ-lockeddualrecovery2.8.21 and
then flashed Cyanogenmod and bricked my device.
Also I tried to install this way Resurrection-Remix-LP and bricked my device.
Every time my device is bricked, I enter FlashMod and restore an official ROM.
Can anybody help me?
SOLUTION
I managed to get it working with your help.
This was because of Linux permissions. I had to create a file, (if it does not already exists):
Code:
(sudo) touch /etc/udev/rules.d/99-android.rules
and write to it:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="5193", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="6182", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="adde", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", ATTRS{idProduct}=="0dde", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d001", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="d002", MODE="0666"
After this, I managed to run Fastboot without superuser (sudo) and run:
Code:
fastboot flash boot boot.img
This time device boot to recovery!

unlocking from linux

Ive read several dozen threads and none of them seem to have the same problem.
Note: this is on ubuntu, and a nexus 6 (though I have tried a dozen different phones)
adb devices // can see my device
adb reboot-bootloader // works fine (in boot loader mode now)
sudo fastboot oem unlock // waiting for devices
Everything I try... its always <waiting on devices>
Things Ive tried:
I made sure usb debugging was enabled
Enable oem unlock is checked in dev settings
Its unlikely a driver issue as I compile android apps all the time and deploy them to the device. adb works fine also.
There is a step which can be done where you look up the phone and you add it to a file in /etc and restart udev (ive done that too), but my understanding is sudo fastboot should work just the same.
Have tried a ton of devices always... <waiting on devices>
Read a ton of trouble shooting articles on <waiting on devices> on xdaforums but none seem to fit my problem.
Any help would be greatly appreciated. I need to root devices for development at work.

I would say check drivers but you say you've already done this. but adb can function without proper fastboot drivers.

Maybe I am missing a driver.
I just purged my machine of fastboot, and did sudo apt-get install android-tools-fastboot
Re-running sudo fastboot oem unlock still results in <waiting on devices>
Is there any other driver I need to install?
Is there any way to verify if a running device is in fact in fastboot mode?

It'd look something like this...
{
"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"
}
I'm not much of a linux person so I'm not sure about any additional drivers.

Thanks! Yes It id definitely in fastboot mode then.
Now the question remains... why does it always show <waiting for devices> when I run sudo fastboot <insert any fastboot command>

Not real familiar with the ins and outs of Ubuntu (use Fedora myself) but I've always had better luck running ADB and fastboot as root than trying to use sudo. Also, do you need to be in a special group to use the USB hardware for fastboot, maybe??? Like I said, not real familiar with Ubuntu...
Also, is the USB port a USB 3 port? I've had problems like that on USB3 ports but when I switched over to the USB 2 port on the Lenovo, it worked fine. Also, make sure you have a good USB cable...had one that the DATA IN wire was broken... charged fine, could send out, never got anything back. Had another that came with some Bluetooth headphones that turned out to just be for charging, i.e., only POS and NEG connected on the plug, no data at all - near went crazy with that one because it looked just fine, nice and thick, no markings on it to indicate anything. Finally figured it out when I sliced the plastic cover off because I was so mad and figured it wasn't working anyway...only 2 wires inside! Good Luck!

First, you don't need sudo for fastboot.
Then when you switch to user root, you don't use the same environment, so it's possible the path is different, and you are using a different fastboot. If you type "which fastboot", and " sudo which fastboot" what do you get?
But anyway, why do you need sudo?
Sent from my Nexus 6 running cyosp using Tapatalk

gathem said:
adb devices // can see my device
adb reboot-bootloader // works fine (in boot loader mode now)
sudo fastboot oem unlock // waiting for devices
Click to expand...
Click to collapse
Did you try doing fastboot devices first?

istperson said:
First, you don't need sudo for fastboot.
Then when you switch to user root, you don't use the same environment, so it's possible the path is different, and you are using a different fastboot. If you type "which fastboot", and " sudo which fastboot" what do you get?
But anyway, why do you need sudo?
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
Thanks!
I tried it as user root. Still < waiting for device >
I also tried
# fastboot devices // output: (just an empty line break)
# which fastboot // output: /usr/bin/fastboot
// (as normal user
#sudo which fastboot // output: /usr/bin/fastboot
I am pretty sure I had tested with a brand new usb cable a while back but will acquire another to test it.
Im not exactly sure on the type of cable/port. Its not an old linux desktop

Got a brand new cable and plugged in directly to the front of the desktop linux machine. I can copy files from the phones internal harddrive to my linux desktop so bi-directional communication is possible.
running fastboot oem unlock as root still results in < waiting for device >
Wanted to say... THANK YOU ALL so much for taking the time to help a random internet stranger get unblocked. I need this for work and I need to root 4+ phones but if I cant figure it out today I'm just going to find someone on craigslist to do it for me so I can get back to working on this project.

Maybe your fastboot is outdated. Download the most recent SDK, or even better, use it from the AOSP source. That's what I always do.
But you still shouldn't really need sudo for fastboot.

Have you set up the udev rules in /etc/udev/rules.d/ ? I usually call that file 99-android.rules and put in the necessary USB entries. Also I agree with making sure fastboot is up-to-date.

RMarkwald said:
Have you set up the udev rules in /etc/udev/rules.d/ ? I usually call that file 99-android.rules and put in the necessary USB entries. Also I agree with making sure fastboot is up-to-date.
Click to expand...
Click to collapse
I had them in a file named 70-adnroid.rules
# cp /etc/udev/rules.d/70-android.rules /etc/udev/rules.d/99-android.rules
# service udev restart
still <waiting for devices>
I didnt compile from source but I did freshly sudo apt-get remove android-tools-adb android-tools-fastboot and sudo apt-get install android-tools-adb android-tools-fastboot
Compiling from source seems like a huge pain.

gathem said:
I had them in a file named 70-adnroid.rules
# cp /etc/udev/rules.d/70-android.rules /etc/udev/rules.d/99-android.rules
# service udev restart
still <waiting for devices>
I didnt compile from source but I did freshly sudo apt-get remove android-tools-adb android-tools-fastboot and sudo apt-get install android-tools-adb android-tools-fastboot
Compiling from source seems like a huge pain.
Click to expand...
Click to collapse
I don't think you had to rename it, you could've left it.
What info do you have in that file? Below is what I have, if you have it already I apologize:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0777", GROUP="plugdev" # MTP mode with USB debug on
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0777", GROUP="plugdev" # MTP mode with USB debug on
Top is when booted normally and TWRP recovery, bottom line is when at bootloader.

# All google devices
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
# HTC devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0664", GROUP="plugdev"
# Motorola devices ## This is the device I am currently working on, but as I said I have over 10 various version nexus devices I need to root
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"
# Sony Ericsson devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
# NVidia Tegra 250 development board
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0664", GROUP="plugdev"
# Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0664", GROUP="plugdev"
# Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", GROUP="plugdev"
# LG devices
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0664", GROUP="plugdev"
# Pantech devices
SUBSYSTEM=="usb", ATTR{idVendor}=="10a9", MODE="0664", GROUP="plugdev"
# Huawei devices
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", GROUP="plugdev"
# Nook color
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0664", GROUP="plugdev"
# Acer devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0664", GROUP="plugdev"
# FOXCONN
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0664", GROUP="plugdev"
# GARMIN_ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="091e", MODE="0664", GROUP="plugdev"
# SHARP
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0664", GROUP="plugdev"
# ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0664", GROUP="plugdev"
# KYOCERA
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0664", GROUP="plugdev"
# QUALCOMM
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0664", GROUP="plugdev"
# OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0664", GROUP="plugdev"
# NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0664", GROUP="plugdev"
# PMC
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0664", GROUP="plugdev"
# TOSHIBA
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0664", GROUP="plugdev"
# SK_TELESYS
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0664", GROUP="plugdev"
# KT_TECH
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0664", GROUP="plugdev"
# ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0664", GROUP="plugdev"
# PHILIPS
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0664", GROUP="plugdev"
# K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0664", GROUP="plugdev"
# Pegatron
SUBSYSTEM=="usb", ATTR{idVendor}=="1d4d", MODE="0664", GROUP="plugdev"
# Hisense
SUBSYSTEM=="usb", ATTR{idVendor}=="109b", MODE="0664", GROUP="plugdev"
# Amazon Kindle
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0664", GROUP="plugdev"
# Nikon
SUBSYSTEM=="usb", ATTR{idVendor}=="04b0", MODE="0664", GROUP="plugdev"
# Intel
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0664", GROUP="plugdev"
# Cellon
SUBSYSTEM=="usb", ATTR{idVendor}=="283b", MODE="0664", GROUP="plugdev"
# TCL
SUBSYSTEM=="usb", ATTR{idVendor}=="1bbb", MODE="0664", GROUP="plugdev"
# TeleEpoch
SUBSYSTEM=="usb", ATTR{idVendor}=="2340", MODE="0664", GROUP="plugdev"
# MTK
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", MODE="0664", GROUP="plugdev"
# HP devices
SUBSYSTEM=="usb", ATTR{idVendor}=="03f0", MODE="0664", GROUP="plugdev"
# OPPO devices
SUBSYSTEM=="usb", ATTR{idVendor}=="22d9", MODE="0664", GROUP="plugdev"
# Xiaomi devices
SUBSYSTEM=="usb", ATTR{idVendor}=="2717", MODE="0664", GROUP="plugdev"
# Razer devices
SUBSYSTEM=="usb", ATTR{idVendor}=="1532", MODE="0664", GROUP="plugdev"
# Archos devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0e79", MODE="0664", GROUP="plugdev"

I noticed your mode is 0777 so I switched 22b8 ti 0777
That didnt help either

I was having issues pushing files but then it just started working, and stops when it wants to, sometimes in the middle of a transfer. I'm using Xubuntu 15.10
Sent from my Nexus 6 using Tapatalk