Hi there,
it seems as if I have a kinda special situation. After rooting and Installation of CWM-Recovery 6.0.4.4 I did the OTA Update. After that, I have the following situation:
What does:
Bootloop with LG Logo
Entering CWM Recovery
Doing a factory reset (volume down+power)
I have two ROMs on the SD (as zip Files): 1. CyanogenMod 10.x and 2. The original Stock rom. Flashing them has no effect.
What does not:
Boot into System
Download mode
ADB Shell
anything not mentioned
I had it sent back to LG - they say you need to replace motherboard (~270$) but I cannot accept, that this piece of hardware should be really finally bricked.
Does anyone of you overhere have any ideas, how I could recover my mobile?
Thanks!
have you tried this
XxZombiePikachu said:
have you tried this
Click to expand...
Click to collapse
Oh sorry! I was confused with the Recovery. I didn't have the TWRP but the CWM instead.
Sorry!
Juliansss said:
Oh sorry! I was confused with the Recovery. I didn't have the TWRP but the CWM instead.
Sorry!
Click to expand...
Click to collapse
well you can still use adb push to try and push twrp and flash it reboot into twrp and then try terminal inside twrp
XxZombiePikachu said:
well you can still use adb push to try and push twrp and flash it reboot into twrp and then try terminal inside twrp
Click to expand...
Click to collapse
Is there any reliable Step-by-Step-like explanation of how to get ADB to work from CWM Recovery? Is the flashing process to be started from adb?
Thanks for your help! Zombie
Juliansss said:
Is there any reliable Step-by-Step-like explanation of how to get ADB to work from CWM Recovery? Is the flashing process to be started from adb?
Thanks for your help! Zombie
Click to expand...
Click to collapse
as long as you have the android sdk then you just go to the platform tools folder and open a cmd window there(inside platform tools folder shift+right click an empty space), and then you type adb devices as long as your device is appears on the list then you just adb push twrp.zip sdcard/Download just make sure the twrp.zip is inside platform-tools folder then flash within cwm
OK! After some trouble with an empty battery and button pressing confusion I finally took a huge step forward.
what I did:
1. In Ubuntu I "installed" adb
2.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
sudo chmod 644 /etc/udev/rules.d/51-android.rules
sudo chown root. /etc/udev/rules.d/51-android.rules
sudo nano /etc/udev/rules.d/51-android.rules
In nano, I edited the file to this content:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
Code:
sudo service udev restart
3. I finalle got the mobile started in recovery mode (CWM) (not very deterministic behaviour to get there)
4. I plugged in the mobile to the computer and did
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
5. I pressed Thanks on http://forum.xda-developers.com/showthread.php?t=2451696 the one who wrote these two lines.
6. In CWM I chose reboot system.
The Situation is now this: The phone once booted into the System (Stock) and asked questions about gmail and locales. In this progress, the massage popped up "gapps was terminated" or similar. Then phone went of. Now the charging animation (fullscreen) is showing and shows 0% for 15minutes already.
My Question is: How can I now asure, to get back to the really original original stock state/condition of my mobile?
Thanks for your help Zombie once again.
Juliansss said:
OK! After some trouble with an empty battery and button pressing confusion I finally took a huge step forward.
what I did:
1. In Ubuntu I "installed" adb
2.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
sudo chmod 644 /etc/udev/rules.d/51-android.rules
sudo chown root. /etc/udev/rules.d/51-android.rules
sudo nano /etc/udev/rules.d/51-android.rules
In nano, I edited the file to this content:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
Code:
sudo service udev restart
3. I finalle got the mobile started in recovery mode (CWM) (not very deterministic behaviour to get there)
4. I plugged in the mobile to the computer and did
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
5. I pressed Thanks on http://forum.xda-developers.com/showthread.php?t=2451696 the one who wrote these two lines.
6. In CWM I chose reboot system.
The Situation is now this: The phone once booted into the System (Stock) and asked questions about gmail and locales. In this progress, the massage popped up "gapps was terminated" or similar. Then phone went of. Now the charging animation (fullscreen) is showing and shows 0% for 15minutes already.
My Question is: How can I now asure, to get back to the really original original stock state/condition of my mobile?
Thanks for your help Zombie once again.
Click to expand...
Click to collapse
Well if it is booted you should check if download mode works, if it does then the best way to to a state of complete stock would be using back to stock guide in the G2 General Section
Sent from my potato powered LG G3 D800
Related
I CAN NOT get my fascinate to show up in ADB on my machine running Ubuntu 10.10. It shows up with the lsusb command, my android rules udev file has it listed, but it wont show up! My wifes D1 shows up just fine! Any ideas?
BTW, I also went through and followed Gridlocks how-to (awesome write-up, btw), but to no avail. Still no adb for me. :-(
Here are my udev rules, for good measure:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM==”usb”, ATTRS{idVendor}==”18d1″, SYMLINK+=”android_adb”, MODE=”0666″
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
Got it. Permission woes I didn't even think about.
<------Stupid
Alternatively, you could do it like this, if you consistently access the device as one user and don't need systemwide permissions.
Code:
SUBSYSTEM=="usb",SYSFS{idVendor}=="04e8",OWNER="username",GROUP="usergroup"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Click to expand...
Click to collapse
any of you heard bout this? anyway, i need the x8's version of this, like the x8 code instead of the htc verion. could anybody help me with this?
cheers
anybody, please
Here's my 50-android.rules from Linux Mint 9 (Ubuntu 10.04)
Code:
# udev rules for Android-powered devices
#
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", SYMLINK+="android_Acer%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", SYMLINK+="android_ASUS%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", SYMLINK+="android_Dell%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", SYMLINK+="android_Foxconn%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", SYMLINK+="android_Garmin-ASUS%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_Google%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_HTC%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", SYMLINK+="android_Huawei%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor]=="24e3", SYMLINK+="android_K-Touch%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", SYMLINK+="android_KTTech%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", SYMLINK+="android_Kyocera%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", SYMLINK+="android_Lenovo%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", SYMLINK+="android_LG%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", SYMLINK+="android_Motorola%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", SYMLINK+="android_NEC%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", SYMLINK+="android_Nook%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_Nvidia%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", SYMLINK+="android_OTGV%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", SYMLINK+="android_Pantech%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", SYMLINK+="android_Philips%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", SYMLINK+="android_PMC-Sierra%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", SYMLINK+="android_Qualcomm%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", SYMLINK+="android_SKTelesys%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", SYMLINK+="android_Samsung%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", SYMLINK+="android_Sharp%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYMLINK+="android_Sony-Ericsson%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", SYMLINK+="android_Toshiba%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", SYMLINK+="android_ZTE%n", MODE="0666", GROUP="plugdev"
As you can see SEMC's idVendor would be "0fce" (Zero Foxtrot Charlie Echo)
B.Jay said:
Here's my 50-android.rules from Linux Mint 9 (Ubuntu 10.04)
Code:
# udev rules for Android-powered devices
#
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", SYMLINK+="android_Acer%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", SYMLINK+="android_ASUS%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", SYMLINK+="android_Dell%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", SYMLINK+="android_Foxconn%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", SYMLINK+="android_Garmin-ASUS%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_Google%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", SYMLINK+="android_HTC%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", SYMLINK+="android_Huawei%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor]=="24e3", SYMLINK+="android_K-Touch%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", SYMLINK+="android_KTTech%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", SYMLINK+="android_Kyocera%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", SYMLINK+="android_Lenovo%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", SYMLINK+="android_LG%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", SYMLINK+="android_Motorola%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", SYMLINK+="android_NEC%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", SYMLINK+="android_Nook%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", SYMLINK+="android_Nvidia%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", SYMLINK+="android_OTGV%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", SYMLINK+="android_Pantech%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", SYMLINK+="android_Philips%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", SYMLINK+="android_PMC-Sierra%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", SYMLINK+="android_Qualcomm%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", SYMLINK+="android_SKTelesys%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", SYMLINK+="android_Samsung%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", SYMLINK+="android_Sharp%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", SYMLINK+="android_Sony-Ericsson%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", SYMLINK+="android_Toshiba%n", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", SYMLINK+="android_ZTE%n", MODE="0666", GROUP="plugdev"
As you can see SEMC's idVendor would be "0fce" (Zero Foxtrot Charlie Echo)
Click to expand...
Click to collapse
thanks man ( i pressed thanks button dont worry )
i can conttinue with my project now
cheers -wilbso
So this is just to save the people who use Linux and do Android stuff some trouble, it is merely a compiled list of vendor ID's for many phone manufacturers so that ADB and Fastboot can recognize your device.
Note: For other distributions the instructions would be very similar, you would only be swapping out the "/etc/udev/rules.d/51-android.rules" path for one specific to your distro. Consult Google for specifics, but the content of that file can be copied from the download link below and still work.
Instructions (Ubuntu/Ubuntu-based only):
Download this file: 51-android.rules
Open a terminal
Type in
Code:
$ sudo gedit /etc/udev/rules.d/51-android.rules
Open the file you downloaded above and copy and paste the content into the blank file you opened from terminal
Save the file that was originally blank (and now has content) and close it
Back in terminal type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
Now you need to restart the udev service, so try the following commands ONE at a time until one of them works (doesn't give errors). If you'd rather NOT restart udev, you can also reboot for the changes to take effect.
Code:
service udev restart
sudo /etc/init.d/udev restart
sudo reload udev
sudo udevadm trigger
In terminal, either cd to your ADB directory (if not set in your $PATH) and run this
Code:
$ ./adb devices
or if it is in your path, run this
Code:
$ adb devices
Any connected devices should show up
You're done, you can now use adb to connect to your Android device, even if you get a new phone as the definitions in the file cover a large range of manufacturers
Download link: 51-android.rules
I will keep this updated if any new manufacturers show up in the Android market.
Nice....I might just be adding this to Mint. As it sits now only HTC devices show in adb all other devices give me the famous
no permissions ?????? Output. But I only add the HTC vendor. Thanks for sure though
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Nice....I might just be adding this to Mint. As it sits now only HTC devices show in adb all other devices give me the famous
no permissions ?????? Output. But I only add the HTC vendor. Thanks for sure though
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Yup, thats why I keep this file in my dropbox for when I get more devices
And yeah, I remember you said you might be trying out Ubuntu so I just wanted to help out
went from Mint 14 back to Mint 13 today and used this as a 99-android.rules and it worked out for HTC. cant say anything about the rest all i own is HTC. thanks again man
strapped365 said:
went from Mint 14 back to Mint 13 today and used this as a 99-android.rules and it worked out for HTC. cant say anything about the rest all i own is HTC. thanks again man
Click to expand...
Click to collapse
Ubuntu 12.10 recognized my lte on a fresh adb install. I was surprised I had to do no edits since my shift always gave me trouble.lol
Sent from my EVO using xda app-developers app
jesuscash said:
Ubuntu 12.10 recognized my lte on a fresh adb install. I was surprised I had to do no edits since my shift always gave me trouble.lol
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
My Shift MyTouch 4G Slide and G2 all throw fits so this made it super easy not to see
????????? No permissions lol
Sent from my myTouch_4G_Slide using Tapatalk 2
jesuscash said:
Ubuntu 12.10 recognized my lte on a fresh adb install. I was surprised I had to do no edits since my shift always gave me trouble.lol
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Lol it shouldnt by default...
Run:
Code:
sudo gedit /etc/udev/rules.d
And see if its empty or not
I'm thinking that maybe when you install the adb tools package, it creates that file for you....i'm not sure though, I install my adb manually by downloading the ADT_Bundle.tar.gz file
But then again, maybe some phones just work :good:
Sent from my PG06100 using xda premium
strapped365 said:
My Shift MyTouch 4G Slide and G2 all throw fits so this made it super easy not to see
????????? No permissions lol
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
That always drove me nuts.
I used to think a lot of the edits didnt work but I just kept forgetting to kill the server and restart it lol
CNexus said:
Lol it shouldnt by default...
Run:
Code:
sudo gedit /etc/udev/rules.d
And see if its empty or not
I'm thinking that maybe when you install the adb tools package, it creates that file for you....i'm not sure though, I install my adb manually by downloading the ADT_Bundle.tar.gz file
But then again, maybe some phones just work :good:
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Came out empty lol
jesuscash said:
That always drove me nuts.
I used to think a lot of the edits didnt work but I just kept forgetting to kill the server and restart it lol
Came out empty lol
Click to expand...
Click to collapse
Wait the command was supposed to be this, my b:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Sent from my PG06100 using xda premium
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04c5", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="091e", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="109b", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="17ef", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="10a9", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1d4d", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="2340", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0666", GROUP="plugdev"
These are all the devices listed on googles website for ADB, Just copy and paste this into your android.rules.
Well i guess you can paste exactly whats in the file I uploaded....
Sent from my PG06100 using xda premium
CNexus said:
Well i guess you can paste exactly whats in the file I uploaded....
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
That's what I did and it was the first time ever it didn't take an 8 digit vendor number. Like how HTC is 0bb4 my Linux installs always wanted 0bb4 : xxxx ( don't remember last 4 )
Sent from my myTouch_4G_Slide using Tapatalk 2
I think it varies between distros
On ubuntu it just takes a 4 digit one
But to make sure i understood...the 4 digit numbers worked for you or not...?
Sent from my PG06100 using xda premium
strapped365 said:
That's what I did and it was the first time ever it didn't take an 8 digit vendor number. Like how HTC is 0bb4 my Linux installs always wanted 0bb4 : xxxx ( don't remember last 4 )
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
I think the last 4 are device model specific. I dunno.
Sent from my EVO using xda app-developers app
CNexus said:
I think it varies between distros
On ubuntu it just takes a 4 digit one
But to make sure i understood...the 4 digit numbers worked for you or not...?
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
All I ever run is a derivative of Ubuntu. And have for the last year. I wish my Linux machine would boot Ubuntu full but it won't.
Yes sir by far the easiest way to get adb going. It took me no more than 30 seconds
jesuscash said:
I think the last 4 are device model specific. I dunno.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'll have to plug all my devices in a run lsusb again to check. But if I remember right they are. But for some reason my PC needed all 8 before adb would work on any device.
Sent from my myTouch_4G_Slide using Tapatalk 2
Weird. I use 4 digits and adb recognizes the S3 and my shift
Sent from my PG06100 using xda premium
CNexus said:
Wait the command was supposed to be this, my b:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
lol
Hey look, theres stuff in it lol
Sent from my PG06100 using xda premium
CNexus said:
Hey look, theres stuff in it lol
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It doesnt match up with my device's vendor ID and stuff lol
jesuscash said:
It doesnt match up with my device's vendor ID and stuff lol
Click to expand...
Click to collapse
Were you ever able to get this to work?
OK so I have an old laptop running Ubuntu 10.04lts (because it runs best on that laptop) and no other computer. I was trying to root with the guide on the nexus4root website but when I go to unlock the boot loader it doesn't do anything. And I tried running the toolkit from the sticky with wine but no avail there either. Anyone have advice on how to do this, or do I need to bite the bullet and use a friends PC?
(I got the nexus 4 from T-Mobile, and I'm still very new to Linux. I went to college for computer engineering but lost interest in messing with computers)
Sent from my Nexus 4 using xda premium
This might help (not watched it but Google bought it up)...
http://www.youtube.com/watch?v=VfmulWBobTQ
skaroger867 said:
OK so I have an old laptop running Ubuntu 10.04lts (because it runs best on that laptop) and no other computer. I was trying to root with the guide on the nexus4root website but when I go to unlock the boot loader it doesn't do anything. And I tried running the toolkit from the sticky with wine but no avail there either. Anyone have advice on how to do this, or do I need to bite the bullet and use a friends PC?
(I got the nexus 4 from T-Mobile, and I'm still very new to Linux. I went to college for computer engineering but lost interest in messing with computers)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Hey, I have a Ubuntu 12.04 LTS machine and successfully unlocked my N4's bootloader and rooted it, but it shouldn't make any difference. Can you post exactly what the following command (which I assumed you entered, without the $ prompt) outputs:
Code:
$ fastboot oem unlock
Setting up your PATH
Also you need to make sure adb and fastboot executables are in your path. I can help you do that:
Open up .bashrc in your home folder with your favorite text editor (mine's gedit, without the $ prompt):
Code:
$ gedit ~/.bashrc
Add the following lines:
Code:
export PATH = ${PATH}:/home/username/android-sdk-linux/platform-tools/
export PATH = ${PATH}:/home/username/android-sdk-linux/tools/
Note:
You need to put the directory where you installed the Android SDK on your machine correctly. The paths above are just examples in my case and probably won't work for you.
Save and exit gedit. Close every Terminal window you have and open up a new one. Test by typing in (without the $ prompt) with an Android device plugged in and USB Debugging checked:
Code:
$ adb devices
Setting up the udev service
Once you're sure adb and fastboot are in your path, you also need to add the extra udev rules for Fastboot and ADB (in recovery) to work. To do that:
As root, create a file called 51-android.rules and put it in /etc/udev/rules.d/ (again with gedit, without the $ prompt):
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Copy and paste the following contents into the file:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
Save and close the file. Then, run the following commands (without the $ prompt):
Code:
$ sudo chmod 644 /etc/udev/rules.d/51-android.rules
$ sudo chown root:root /etc/udev/rules.d/51-android.rules
$ sudo service udev restart
$ sudo killall adb
Disconnect and reconnect your device (making sure it's in Fastboot/bootloader mode) and run the following command (without the $ prompt) to test:
Code:
$ fastboot devices
I used the video, it was a lot better than the written version they had up on the site. Phone is rooted and I'm downloading carbon rom now. Thanks!
Sent from my Amazon Kindle Fire using xda premium
I'm tried to use adb over network USB tethering for Linux on my PC. I can't use network on Linux only on Windows.
When I enable adb over network settings from debug (I use custom ROM and) it worked until then when I used command: adb tcip 5555. I think I changed the port or something . How can I reset the network/adb to be able to use the adb over network setting again?
Model: i9505 jfltexx
ROM: VRToxin Stable
6.0.1 Marshmallow
My question is how can I use my network phone by USB tethering in Linux?
painx said:
I'm tried to use adb over network USB tethering for Linux on my PC. I can't use network on Linux only on Windows.
When I enable adb over network settings from debug (I use custom ROM and) it worked until then when I used command: adb tcip 5555. I think I changed the port or something . How can I reset the network/adb to be able to use the adb over network setting again?
Model: i9505 jfltexx
ROM: VRToxin Stable
6.0.1 Marshmallow
My question is how can I use my network phone by USB tethering in Linux?
Click to expand...
Click to collapse
Hi painx
The command is adb tcpip 5555.
Do you have the 51 android rules file in /etc/udev?
Art Vanderlay said:
Hi painx
The command is adb tcpip 5555.
Do you have the 51 android rules file in /etc/udev?
Click to expand...
Click to collapse
I don't have the debug report..I don't even know from where should I enabled that because there's no option in debug settings.
painx said:
I don't have the debug report..I don't even know from where should I enabled that because there's no option in debug settings.
Click to expand...
Click to collapse
No I mean on your linux pc. You don't have to do anything on your phone except turn on the adb over network switch. When you installed adb you should have also configured the udev rules. Do you know if you did this?
Art Vanderlay said:
No I mean on your linux pc. You don't have to do anything on your phone except turn on the adb over network switch. When you installed adb you should have also configured the udev rules. Do you know if you did this?
Click to expand...
Click to collapse
I don't think I did that.
painx said:
I don't think I did that.
Click to expand...
Click to collapse
Copy and paste this in your terminal
Code:
cat >/tmp/android.rules << "EOF"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
EOF
sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rules;sudo chmod 644 /etc/udev/rules.d/51-android.rules;sudo chown root. /etc/udev/rules.d/51-android.rules;rm /tmp/android.rules;
After you've done that check the ip address in settings > status
Connect your phone to your pc and run these commands:
Code:
adb tcpip 5555
Code:
adb connect <ip address>
Then unplug your phone and check the connection with this command
Code:
adb get-state
Art Vanderlay said:
Copy and paste this in your terminal
Code:
cat >/tmp/android.rules << "EOF"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0e79", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0b05", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="091e", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="24e3", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2116", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0409", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="2257", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="10a9", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1d4d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0471", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04da", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1f53", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0930", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="19d2", MODE="0666"
EOF
sudo cp /tmp/android.rules /etc/udev/rules.d/51-android.rules;sudo chmod 644 /etc/udev/rules.d/51-android.rules;sudo chown root. /etc/udev/rules.d/51-android.rules;rm /tmp/android.rules;
After you've done that check the ip address in settings > status
Connect your phone to your pc and run these commands:
Code:
adb tcpip 5555
Code:
adb connect <ip address>
Then unplug your phone and check the connection with this command
Code:
adb get-state
Click to expand...
Click to collapse
Which terminal? I guess linux..
I forgot to say I don't use dual boot, I use virtualbox.