Database Users

[Q] Alright, I give up! Ubunutu/ADB woes...

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"

[Build Jelly Bean AOSP] Galaxy S2

To compile Jellybean on Ubuntu I'm going to first give you steps to set up your computer to get this thing rolling. Also note that this appears to be a development preview source code.
This is the base how you build it for our device, it will be updated daily if fixes are made
Running into an error, make sure to write what the problem is.
Thanks List:
koudd For helping me out wih errors/Pointing me to right direction
stormtroopercs For Helping Me out/point to right direction
MemoryController Helping US, with errors while compiling,
Kalgecin for helping me fix my errors/pointing me to right direction
dastin1015 For his brilliant Tutorial which this is based uppon: Here
Krizp0 for pointing out that i missed to credit dastin1015 for tutorial which this one is based uppon!
princescar for pointing out that the java jdk was wrong
Note: The source download is approximately 6GB in size. You will need 25GB free to complete a single build, and up to 80GB (or more) for a full set of builds.
1) You need the following:
-JDK 6 if you wish to build Jellybean.
Code:
$ sudo apt-get install sun-java6-jdk
if you got any problem go: https://github.com/flexiondotorg/oab-java6 or to developers website: http://www.oracle.com/technetwork/java/javase/downloads/index.html
-Python 2.4 -- 2.7, which you can download from python.org. Or:
Code:
$ sudo apt-get install python
-Git 1.7 or newer. You can find it at git-scm.com. Or:
Code:
$ sudo apt-get install git-core
-Android SDK:
Download the SDK here: http://developer.android.com/sdk/index.html
Extract the SDK and place it in your home directory.
I renamed my SDK to android-sdk to make it easier to navigate to.
Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
Add these lines at the bottom of the file:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Find your .profile file and add this at the bottom of the file:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
$ android
2) Install required packages. 64-bit (recommended)
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
in this case we only need Samsung USB (If your building for other devices such as LG you can add thoose too!)
Code:
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
6) Initialize the repo:
Code:
$ mkdir WORKING_DIRECTORY (Note the WORKING_DIRECTORY can be named whatever you wan't just don't use a name with spaces!)
$ cd WORKING_DIRECTORY
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r1
6.1) For people who have already done a repo init:
Code:
$ cd WORKING_DIRECTORY
$ repo init -b android-4.1.1_r1
$ repo sync
7) When prompted, enter your real name and email address.
8) Gather the files:
Code:
$ repo sync
This is not nessesary to do now, this is more a check to see if anything is working properly! (if you know everything is working skip to how to add a device to the list!)
Code:
9) Compiling: [CODE]$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
10) Issue:
Code:
$ lunch
11) Pick your poison.
12) Now issue (The '#' is the number of cores your processor has plus 1, ex. I have a dual core processor so I type 'make -j3':
Code:
$ make -j#
[/CODE]
~How To Add A Device To The List~
1) Find the github for your device you wish to add. In this tutorial we use GalaxyS2
2) Now navigate to the location you are going clone the device tree to:
Code:
$ cd WORKING_DIRECTORY/device
$ mkdir samsung
3) Clone the github device tree from remote to local: in this case i clone the git to non existing folder, this folder will be created if you write etc galaxys2 after the git tree.
Code:
$ git clone git://github.com/cleaton/device_samsung_galaxys2 galaxys2
4) Now navigate into the folder:
Code:
$ cd galaxys2
5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.
Before Doing Step 6 Make sure you use latest CM9-Nightly or else you may not getting all files!
Click to expand...
Click to collapse
6) Extract Device Proprietary Files:
Code:
$ ./extract-files.sh
7) Navigate back to your home directory for building:
Code:
$ cd ~/WORKING_DIRECTORY
Now before doing an buld/evensetup.sh compile, make sure you have the exynos4.mk file its located in hardware/samsung
if you don't have any samsung folder in the hardware folder make sure to clone one from: git clone git://github.com/cleaton/android_hardware_samsung.git -b jb-dirtyfix hardware/samsung (don't use cyanogenmod samsung_hardware as its doesn't have updated drivers!)
8) Prepare To Compile:
Code:
$ source build/envsetup.sh
Or:
Code:
$ . build/envsetup.sh
9) Get your list of devices:
Code:
$ lunch
10) Pick your poison.
11) Now compile:
Code:
$ make -j#
Or for a flashable zip:
Code:
$ make -j# otapackage
~FIXES~
If you are running into issues such as:
Code:
Which would you like? [full-eng] 5
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
Device shooter not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for shooter not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:209: *** No matches for product "full_shooter". Stop.
** Don't have a product spec for: 'full_shooter'
** Do you have the right repo manifest?
What you need to do is to edit your blob to match the PRODUCT_NAME to the file name. For example with mine I have full_shooter.mk therefore in this file I need to have PRODUCT_NAME to match it. Whatever error it is looking for you just need to change the PRODUCT_NAME line to match what the error shows.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you run into issues with Java being the incorrect version here is the fix:
Make sure Java 6 JDK is installed by typing in:
Code:
$ java -version
Open the file main.mk in build/core and delete this line from the java error code section:
Code:
$(error stop)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Change all references in your device repo from frameworks/base to frameworks/native

Are you sure Java Open SDK will do this???

Credit the author?
http://forum.xda-developers.com/showthread.php?t=1762641

princescar said:
Are you sure Java Open SDK will do this???
Click to expand...
Click to collapse
done
Krizp0 said:
Credit the author?
http://forum.xda-developers.com/showthread.php?t=1762641
Click to expand...
Click to collapse
ah yes sorry forgot edit; fixed

Didn't you post this before and it got closed?
My bad, it was for compiling, same rule still applies mate. http://forum.xda-developers.com/showthread.php?t=1764296&highlight=build+jellybean
EDIT: This just looks like a straight copy and paste anyways...?

As to reference with this thread I will also lock this thread.

Trouble rooting on ubuntu

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

[Q] [HELP] D802 bricked after OTA Update

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

Adb over network problem

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.