Database Users

adb device not found ubuntu 10.10

I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?

4nic8 said:
I am fairly new to linux so I could be missing something simple but when I type adb devices i get a blank reply. It doesn't say "no devices" or anything, it just doesn't show anything. But if I run adbwireless from my phone, i can run adb connect ip adress :5555 and connect just fine. I have also noticed that the only time ubuntu will see my phone at all is if usb debugging is off. I'm not sure if those two are related or not. any suggestions?
Click to expand...
Click to collapse
WORKS FOR EPIC 4G!!!!!
This worked for my BH2 but it may need some tweaking on the rules file to make it work, but I will double check it when I get home.
After downloading the SDK, I moved the adb to the (in my pc is like this) ~/android/tools/ folder and ran the chmod a+rwx adb command.
After this, I took the rules file (attached) and I moved it to the /etc/udev/rules.d/ folder (logged as root). After doing this, I ran the following commands:
su [then placed the password]
chmod a+x 51-android.rules
chown root:root 51-android.rules
Once done, I restarted the PC and its working 100%, I ran the lsusb command to confirm the connection of the device and then a ./adb devices an I got positive return!
Note: Attachment updated!

Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App

4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I will tune the Rules file and test and let you know. Most of the time, when it doesn't work, its the rules file who has the problem.

4nic8 said:
Thank you for the suggestion. I ran the commands as you said, using the 51-android.rules that i already had and i still get a blank response when running
Adb devices.
However, since running those commands, its mounting my sd on the desktop with or without usb ebugging. So the commands you provided did fix something, just not adb!
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.

megabiteg said:
FIXED!!!! download this file and it will work 100%!
Also, please follow my instructions above in the same order.
Click to expand...
Click to collapse
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(

4nic8 said:
thank you for the suggestion dude, but i think that actually took me back a step, now my sd wont mount anymore. i had a 51-android.rules file already and i deleted it. maybe i will just have to still with adbwireless =(
Click to expand...
Click to collapse
mmmm..
I've tested this with several other friends that use Ubuntu 10.10 and it works fine for them. Are you following step by step on my OP?
Also are you on a desktop or laptop? Please note that while you have USB Debugging on the option to mount your SD card will not be prompted.
If your using a Desktop, please refrain of using front side USB ports. If you need additional help, let me know, I'll be glad to help you getting it working.
send me what the lsusb command dumps if you can, that can help me tweak the rules file for you.

Thanks! after some trial and error..the zip file in the first post worked for me!
FYI, you can just run this command instead of restarting your computer:
Code:
sudo udevadm control –reload-rules; sudo reload udev; adb kill-server; adb devices

Same problem
Hello, I have the same problem, adb don't detect my tablet. I do it from my laptop and this is the lsusb exit:
[email protected]:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 007: ID 18d1:0001 Google Inc.
Bus 001 Device 002: ID 174f:a311 Syntek 1.3MPixel Web Cam - Asus A3A, A6J, A6K, A6M, A6R, A6T, A6V, A7T, A7sv, A7U
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~$ adb devices
List of devices attached
[email protected]:~$
Click to expand...
Click to collapse
Is it possible that the integrated webcam generates the conflict? how can I disable it on Ubuntu 10.10?
Thanks

One thing I've noticed is that my phone will come right up (with debugging turned on) on certain usb ports but won't on others. Might be worth trying different USB ports just to see if it makes a difference.
Was this way on both my desktop and my netbook (both running Ubuntu 10.10).

Thanks flatspin, I have tried all my 4 usb ports without luck.

Solved, I forgot to put the tablet on adb mode at boot time.

how can i root my nexus 7 without using pc

I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help

Jim Omar said:
I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help
Click to expand...
Click to collapse
Pretty sure there's a way because you could flash a recovery if your boot loader is unlocked and there's a tool to root your device just look in the android development section of the nexus 7
Sent from my HTC Sensation using xda app-developers app

Yes it is. But no matter how, you got to use a pc to unlock your bootloader 1st.
Sent from my Nexus 7 using Tapatalk 2

Jim Omar said:
I can't connect my nexus 7 to any PC because my USB port is broken SO is there any chance I can root my device (boot loader is already unlocked)
Please help
Click to expand...
Click to collapse
What pc do you have?

Wrong forum.

jcollier said:
Wrong forum.
Click to expand...
Click to collapse
Moved to correct one...

What you need is a "root exploit" that can be executed from the normal OS. (For instance kernel exploits).
Under the presumption that a root shell can be obtained you can simply use a "dd" command to write the raw partition for the recovery. The way this normally works is that you run an exploit from a terminal emulator, and if the exploit succeeds (gains root privilege) it exec's a root shell. From there it's a single command ("dd") to writing to the root-owned block device (e.g. recovery partition) with a replacement recovery image file.
The problem with devices whose manufacturer provides an easy route to flashing - e.g. an "unlocked" or "S-OFF" bootloader (as with the Nexus 7) - is that nobody bothers to go looking for root exploits for that device; they just take the course of least resistance for rooting, and move on to ROM building, customization, or other tweaking... they don't spend time looking for yet another rooting method.
I guess what I am saying is that you are probably on your own & need to figure out how to use a NDK (or similar) cross-compiling toolchain to compile native binary exploits and attempt to use them.
Note there is a recent exploit for a JellyBean device: the Moto Atrix HD - an Arm v7 (Snapdragon MSM8960) processor. I don't know what the root-exploit binary ("pwn") does in that case - it is possible that it leverages a recent kernel exploit. It is also possible that the same exploit has already been patched in the kernel on your tablet.
good luck

OK.... but what about wireless adb ?

Jim Omar said:
OK.... but what about wireless adb ?
Click to expand...
Click to collapse
AFAIK that requires root

You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Sent from my Nexus 7 using Tapatalk HD

Jim Omar said:
OK.... but what about wireless adb ?
Click to expand...
Click to collapse
What about it? At best that gets you an unprivileged shell on an unrooted device - the same result as using a terminal emulator. (If you get wireless adb to work, it might be convenient for transferring files or side loading non-market apps, but really nothing that can not be accomplished with other means, e.g. emailing yourself zipped-up files)
korockinout13 said:
You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Click to expand...
Click to collapse
How exactly does that overcome a damaged USB port on the N7?
@Jim Omar
How are you charging the device - using a dock?

Yes I change the device using a dock

korockinout13 said:
You could use another Android device that supports USB otg and has the arm fastboot binary installed.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Could you please explain further
---------- Post added at 05:37 AM ---------- Previous post was at 05:27 AM ----------
How can I do that " use another Android device that supports USB otg and has the arm fastboot binary installed."

Mashhoor Itayem said:
Could you please explain further
---------- Post added at 05:37 AM ---------- Previous post was at 05:27 AM ----------
How can I do that " use another Android device that supports USB otg and has the arm fastboot binary installed."
Click to expand...
Click to collapse
Sure... the Nexus 7 supports USB-OTG, so using a USB-OTG cable the Nexus 7 can connect to and charge other devices. Since the adb binary is included in android, the Nexus can send adb commands over USB to other devices just like a pc would. It doesn't have fastboot support by default, but you can simply add a fastboot binary to /system/bin/. To get it, do a search for "arm fastboot binary" and place it in your device's above directory. Once installed correctly on the host device, it will be able to send fastboot commands to connected devices.
Sent from my Nexus 4 using xda premium

OTG stuck Nexus
Hi, your solution would be perfect if my N7 (2012) were not stuck in OTG mode! Is there a way to switch modes?
Thanks in advance!
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - 015d15b4f85c0611
SIGNING - not defined yet
LOCK STATE - UNLOCKED

HUAWEI Ascent Mate 7 Unlock & Recovery/Root & ROM Update

HUAWEI Ascent Mate 7 Unlock & Recovery/Root & ROM Update​
Note: www.LeHarbour.com is not responsible for the accuracies of the updates here. You are at your own risk if the device malfunctions and cannot be recovered. Please follow our blog on www.LeHarbour.com. When you paste the updates to other site, please reference to our blog.
1. Preparation
>Download package: https://drive.google.com/file/d/0B2wyI9E11DldY2FweGMtVDM4YUE/view?usp=sharing (Thanks our friend for uploading and storage).
>Install adb1.3.exe (Press “Y” and “Enter”)
>Install AdbDriverInstaller.exe
>Install Driver DriverSetup.exe
>Copy SuperSU_2.20.zip to internal storage or external SD card.
>Copy the folder MT7 to D: driver
2. Get Unlock Code
>For Chinese models (i.e., MT7-TL00, MT7-TL10, MT7-UL00, MT7-CL00), get the unlock code here: http://www.emui.com/plugin.php?id=unlock&mod=detail
>For Non-Chinese models (e.g., MT7-L09), you can write to HUAWEI directly [email protected]. Copy the following to your email:
Title of Email: 华为解锁
Email Content: 您好！请提供解锁码。机器的产品型号是MT7-L09，产品S/N号是（Insert S/N），产品IMEI/MEID号是（Insert IMEI/MEID），产品识别码是（Insert Product ID）。谢谢！
>Once you hear back from HUAWEI, you can use free translation service.
3. ADB Unlocking
>Connect the device to computer
>Setting – About phone – Build number click it for 3-5 times
>Setting – Develop options – USB debugging enabled
>Disconnect the device – Connect the device to computer authorize the Developer Mode
>WIN+R – CMD – D: – CD MT7 – adb devices (show something like Y9KF0923F898343 device)
>adb reboot-bootloader
>fastboot devices
>fastboot oem unlock ######(the unlock code)
>fastboot reboot
4. CWM/Factory Recovery & Root
>Run.bat
>Flash the recovery
>Enter the CWM recovery mode
>Install zip SuperSU_2.20.zip – Reboot the device – Open SuperSU – Reboot – Root Done!

ROM Updates
ROM Updates​
International TL10 ROM. Tested work on Chinese MT7-TL10. Comes with complete default Google APPS and no other HUAWEI APPS.
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
However, the support of International MT7-TL10 will have a delay compared to the Chinese version. Your choice!

@azoznet submitted this easy method for getting the unlock code for MT7-L09. Thanks to our Saudi forum member!
Quote begins:
First go to the following page
Huawei Product ID Generator.rar
download Huawei Product ID generator down and starting this.
Product Model selects Huawei Y300-0000 from her and give in your IMAI Product IMEI of your mate 7 L09
Next, you go on
EmotionUI - Unlock Bootloader
Scroll down and Click on the hook, and then click Next
On the next page you do the following
Product type: Smartphone
Product model: Huawei Y300-0000
Product SN: serial number of your Mate 7
Product IMEI / MEID: IMEI of your Mate 7
Product ID: your number from the Product ID generator
Then you give the Captcha and sends all off.
Now at the end of your unlock code should be generated

Hello,
thanks for the post !
But I am stuck right at the beginning. AdbDriverInstaller requires the device to be connected. If I connect it, it is only detected by the software if I use 'Hisuite' mode from the USB menu. And then the drivers would not install saying that drivers are not compatible with win8.1 x64. I'll try on a win7x32 tomorrow and post update.
thanks

@glycero Yes, try it on WIN7 or download a compatible ADB driver for WIN8. Let us know how it works.

device rooted !
I used this universal driver for adb : I am not allowed to post external links so just search for adb windows 8 and the first reply in Google is fine.
If others are willing to follow the above instructions, bear in mind that the SuperSU application provided is in Chineese.... You may prefer another one.
Great, thanks

here is the link : https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH for universal ADB

@glycero Thanks!

Can someone tell more how looks android after rooting ? What about updates ? What we get , what have we lost ? Cheers!

Thank you!
Very simple and works great on my L09!
---------- Post added at 07:07 PM ---------- Previous post was at 06:13 PM ----------
SignumOne said:
Can someone tell more how looks android after rooting ? What about updates ? What we get , what have we lost ? Cheers!
Click to expand...
Click to collapse
The appearance of Android don't change, you only can run apps that need Root permissions. If you want to update you can flash the factory recovery and root again after update.

Video-tutorial
First I wanna thank you all for this guide.
Second, if someone could just upload a video guide to youtube.
A step by step tutorial.
I think this will help everybody.
Thanks

Did you try root your L09 on Windowds 8.1 x 64 ? I had some problems on this platform.

If you guys have a specific question, please describe it in detail and we and other xda members may solve that for you. We, LeHarbour.com, will not be able to standby in this forum 24x7, but we will definitely check this periodically.

SignumOne said:
Did you try root your L09 on Windowds 8.1 x 64 ? I had some problems on this platform.
Click to expand...
Click to collapse
I had problems before with Windows 7. Not for this phone but with some other phone. But my windows XP desktop saved me.
So, yah Windows XP is better for rooting and other stuff.
Sent from my Coolpad 9976A using Tapatalk

SignumOne said:
Did you try root your L09 on Windowds 8.1 x 64 ? I had some problems on this platform.
Click to expand...
Click to collapse
We perform root on WIN7 X64. Maybe check the proper ADB drivers for WIN8 X64.

SignumOne said:
Did you try root your L09 on Windowds 8.1 x 64 ? I had some problems on this platform.
Click to expand...
Click to collapse
I did it on my windows 8.1 x64 laptop without problems. I only used the files in the package.

stefan038 said:
I did it on my windows 8.1 x64 laptop without problems. I only used the files in the package.
Click to expand...
Click to collapse
+1
... send from hell... hahahaaaa...

Hi,
Did you try the drivers I provided on the first page? It worked fine for me on Win8.1 x64?
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

SignumOne said:
Did you try root your L09 on Windowds 8.1 x 64 ? I had some problems on this platform.
Click to expand...
Click to collapse
at which step do you have issues ?

Just got it today. Managed to root it as per the tutorial.
But just to highlight. If you have 1 of the chinese models, you will have to use the Chinese Page to generate the unlock code.
http://www.emui.com/plugin.php?id=unlock&mod=detail
Also, the superuser app in the attached is in Chinese.
I have modified the zip with an english version should you require it.

[Q] Need help/info. Bricked G2 and Linux Fix method.

OK I really need some help and info here. Ive done some searching around on here and other sites, and found what seems to be the only method to fix my phone ... http://forum.xda-developers.com/showthread.php?t=2582142 ... I feel fairly confident that I can accomplish this method. Although im not running ubuntu but rather kali.
My device had the vzw-vs980-27a.kdz and rooted by stumproot.apk. and the other morning verizon pushed the lollipop ota and now my phone is stuck in the secure boot error fastboot. It fits all the signs as described in the fix it post.
Questions:
1. Since i was on 27A and the files provided in the link only go up to 24A, I was wondering if I could use the 24A image files or will they further break my phone?
2. I was able to find a 27A bootstack zip via https://www.androidfilehost.com/?fid=95916177934539347... the only thing is the bootstack files in the zip are .bin files and the instructions call for .img files.
are these two interchangeable? if not can i use the 24A to fix my phone or can some one direct me to a link where i can find the 27A .img files.
Any and all help and input are greatly appreciated.

REALLY NEED HELP!
I cant get my linux system to recognize the phone but when i plug it into a windows system it recognizes it as a unkown device. but i cant upate the driver to a adb driver or fastboot driver
and i cant even turn the phone on or off no matter what button config i try

anyone?

a.perkins89 said:
Although im not running ubuntu but rather kali.
Click to expand...
Click to collapse
It shouldn't matter that you're running Kali instead of Ubuntu. As long as you have the required files: /bin/ls, /sbin/gdisk and /bin/dd you're good to go. You can confirm the location of the binary commands by running the whereis command followed by ls, gdisk, and dd respectively.
If you're having trouble mounting your device or getting it recognized, consider using a more user friendly environment like Ubuntu. Kali is great for forensics and pen-testing but using it to communicate with your phone probably isn't the best choice, it may have missing dependencies.
a.perkins89 said:
I was able to find a 27A bootstack zip via https://www.androidfilehost.com/?fid=95916177934539347... the only thing is the bootstack files in the zip are .bin files and the instructions call for .img files. Are these two interchangeable?
Click to expand...
Click to collapse
Yes they are. Rename all the .bin files to .img and continue from there.
Good luck!

a.perkins89 said:
REALLY NEED HELP!
I cant get my linux system to recognize the phone but when i plug it into a windows system it recognizes it as a unkown device. but i cant upate the driver to a adb driver or fastboot driver
and i cant even turn the phone on or off no matter what button config i try
Click to expand...
Click to collapse
Plug your phone in and type "dmesg" in linux. Paste the output on pastebin.com and link it here.
I'm suspecting you are in a QH USB 9008 error. First of all - dont panic. I have successfully recovered from a 9008 error - but it is a longer process (and it may involve you paying someone 30$).
But first, let us confirm.

I have this problem too, my PC wont recognize that its a phone connected it reads "Unknown Device" on WINdows but when i plug it in the computer with Ubuntu it reads nothing. no 9008 error nothing at all. What do i do? do i have to replace the usb port? cant i just use someone elses same exact usb rig and flash and put my old one back? my current one only works if i clean it with alchohal wait 10 minutes to dry then i plug it into my pc and it detects and if i dont then my pc wont see that theirs something connected to it.

d00lz said:
It shouldn't matter that you're running Kali instead of Ubuntu. As long as you have the required files: /bin/ls, /sbin/gdisk and /bin/dd you're good to go. You can confirm the location of the binary commands by running the whereis command followed by ls, gdisk, and dd respectively.
If you're having trouble mounting your device or getting it recognized, consider using a more user friendly environment like Ubuntu. Kali is great for forensics and pen-testing but using it to communicate with your phone probably isn't the best choice, it may have missing dependencies.
Yes they are. Rename all the .bin files to .img and continue from there.
Good luck!
Click to expand...
Click to collapse
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
sandys1 said:
Plug your phone in and type "dmesg" in linux. Paste the output on pastebin.com and link it here.
I'm suspecting you are in a QH USB 9008 error. First of all - dont panic. I have successfully recovered from a 9008 error - but it is a longer process (and it may involve you paying someone 30$).
But first, let us confirm.
Click to expand...
Click to collapse
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.

a.perkins89 said:
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.
Click to expand...
Click to collapse
Please plug your device into the USB slot and type the following,
Code:
lsusb
Please reply with the output.

d00lz said:
Please plug your device into the USB slot and type the following,
Code:
lsusb
Please reply with the output.
Click to expand...
Click to collapse
Bus 003 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated HP HD Webcam
Bus 003 Device 003: ID 0781:5530 SanDisk Corp. Cruzer
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

a.perkins89 said:
Bus 003 Device 006: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 003 Device 004: ID 04f2:b230 Chicony Electronics Co., Ltd Integrated HP HD Webcam
Bus 003 Device 003: ID 0781:5530 SanDisk Corp. Cruzer
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Looks like your device is getting detected at least.
Code:
Bus 002 Device 097: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Please confirm this by unplugging your device and running lsusb again and comparing the output.
I urge you to stop using Kali for this and try Ubuntu btw .

yes, when i unplug the phone from the machine and run the command again. Qualcomm no longer shows up, and of course, comes back upon re-attaching

a.perkins89 said:
Thank you, I was kind of thinking they were interchangeable, just didn't want to assume and possibly screw the device up some more.
Ok, here it is.. pastebin.com/CH6HqSCT.. Once again thank you for any help you can offer.. This really couldn't have happened to me at a more inconvenient time... I literally just had to get on the search for a new job and dropped my resume' at like 20 places within the few days before my phone dying.
Click to expand...
Click to collapse
Code:
[ 173.880606] usb 2-1: New USB device found, idVendor=05c6, [B]idProduct=9008[/B]
[ 173.880619] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 173.880625] usb 2-1: Product: QHSUSB__BULK
[ 173.880629] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 173.881813] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 173.882151] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB0
Unfortunately, you are in QH USB 9008 mode . so now you are in a more complicated way to recover. I suggest you first read this http://www.reddit.com/r/Android/comments/2p8ju4/xpost_rlgg2_the_lg_g2_is_unbrickable_a_story_of/
Then I suggest you download the TOT files and KDZ files for your phone - please be VERY careful in choosing your TOT and KDZ.
Then I also suggest to download the KDZ extractor in python form . Then extract the image files from the KDZ by running
Code:
python KDZFileTools.py -f ../D80110A_00.kdz -x
python DZFileTools.py -f kdzextracted/D80110a_00.dz -x
So now, you have 3 things - TOT file, KDZ file and extracted image files. Also you need to open the back cover of your phone and figure out how to disconnect the battery (it is a small button like thing). Very easy stuff. All of this is a pre-requisite to unbricking your phone.
Now you have two choices - pay someone to connect to a Windows computer (search for tungkick on this forum) or to use this. I would say, use the second one first ... and then decide to pay or not. FYI - when I unbricked, I didnt have access to the second tool so I had to pay Tungkick.
Hope this helps.

sandys1 said:
Code:
[ 173.880606] usb 2-1: New USB device found, idVendor=05c6, [B]idProduct=9008[/B]
[ 173.880619] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 173.880625] usb 2-1: Product: QHSUSB__BULK
[ 173.880629] usb 2-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 173.881813] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 173.882151] usb 2-1: Qualcomm USB modem converter now attached to ttyUSB0
Unfortunately, you are in QH USB 9008 mode . so now you are in a more complicated way to recover. I suggest you first read this http://www.reddit.com/r/Android/comments/2p8ju4/xpost_rlgg2_the_lg_g2_is_unbrickable_a_story_of/
Then I suggest you download the TOT files and KDZ files for your phone - please be VERY careful in choosing your TOT and KDZ.
Then I also suggest to download the KDZ extractor in python form . Then extract the image files from the KDZ by running
Code:
python KDZFileTools.py -f ../D80110A_00.kdz -x
python DZFileTools.py -f kdzextracted/D80110a_00.dz -x
So now, you have 3 things - TOT file, KDZ file and extracted image files. Also you need to open the back cover of your phone and figure out how to disconnect the battery (it is a small button like thing). Very easy stuff. All of this is a pre-requisite to unbricking your phone.
Now you have two choices - pay someone to connect to a Windows computer (search for tungkick on this forum) or to use this. I would say, use the second one first ... and then decide to pay or not. FYI - when I unbricked, I didnt have access to the second tool so I had to pay Tungkick.
Hope this helps.
Click to expand...
Click to collapse
I can't seem to get the tool to work. Iv downloaded a . tot file from storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2FVerizon%2FTOT+Method%2F.. and when trying to run the first step the tool program stops responding

ok i got that figured out, now im stuck on the second step.. when i try to test ap and emmc i get a serial port open message... dont know wgat to do, and i cant really understand the steps in the second image of the guide

a.perkins89 said:
ok i got that figured out, now im stuck on the second step.. when i try to test ap and emmc i get a serial port open message... dont know wgat to do, and i cant really understand the steps in the second image of the guide
Click to expand...
Click to collapse
I suggest you ask on http://forum.xda-developers.com/lg-g2/general/tool-unbrick-lg-g2-qualcomm-9008-board-t3072073 - I'm not really sure what is the way to use this software.

Multitude of hurdles trying to get bootloader unlocked

Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
I had android-tools-fastboot and adb installed. The phone has developer options and USB debugging turned on.
I started the phone in fastboot(volume down + power), I see the droid bot with the 'hood open' It states to connect the USB cable. I have the USB cable connected to a USB 2.0 port.
Phone states that the USB is connected. From the computer's log:
[Thu Dec 27 11:13:50 2018] usb 1-1: new high-speed USB device number 10 using ehci-pci
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device found, idVendor=22b8, idProduct=2e80
[Thu Dec 27 11:13:50 2018] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Thu Dec 27 11:13:50 2018] usb 1-1: Product: Fastboot potter S
[Thu Dec 27 11:13:50 2018] usb 1-1: Manufacturer: Motorola Inc.
[Thu Dec 27 11:13:50 2018] usb 1-1: SerialNumber: ZY224G4BVW
So it is seeing it.
When I run sudo adb devices(ran with and without sudo) all I get is "List of devices attached" with nothing listed.
Did some searching(most of the posts are about WIndows) and found this
I implemented those rules and restarted the services, but the permissions never changed. - and yes I changed OWNER= to my username.
So I say, let's try Windows. I have a Win10 machine here. I first go here to download the driver, but when I click on either link at the bottom of the Windows column(32bit or 64bit) It sends me to a page that states "There has been an error with your request." If I click the Mac link, it starts a download. Could you try to test the download link?
I contacted Moto about this and the reply was that I needed to be using Chrome. I have tried FF, Chrome, Opero, IE and Egde. I have tried it from home, work and mobile data, all with the same result.
Could someone help me out here? These pretzels are making me thirsty!
Thanks!

Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.

[email protected] said:
Don't worry about
Code:
adb devices
not showing, you will be using fastboot for the unlocking steps. Type
Code:
fastboot devices
and it should show your devices #. You can then follow the steps for getting unlock code and unlock the bootloader.
Click to expand...
Click to collapse
Appreciate the reply.
fastboot devices also returns nothing

TheFlashNewb said:
Don't worry about not showing, you will be using fastboot for the unlocking steps. Type
Appreciate the reply.
fastboot devices also returns nothing
Click to expand...
Click to collapse
You need to install Motorola driver to get device. Here is the link from my gdrive to download it:-https://drive.google.com/file/d/1silF8KibEfODhRt7j0twUNI_GLsnKvOW/view?usp=drivesdk
Then all command will run and you need to enable OEM unlock in developers options. So you can unlock your bootloader.

TheFlashNewb said:
Hi all! I am attempting at the end of this project to have Dirty Unicorns running on my device, but I am having a rough time just trying to get the boot loader unlocked.
1st OS: Ubuntu 16.04
...................................
...................................................
Could someone help me out here? These pretzels are making me thirsty!
Thanks!
Click to expand...
Click to collapse
On a Linux distro, like my Debian, we must add "rules" to udev to make your devices discoverable:
1) create a new file in /etc/udev/rules.d called "51-android.rules".
2)copy the following content:
Code:
#adb mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
#fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="685c", MODE="0666", GROUP="plugdev"
3) Replace 04e8 and 685c with your usb address. Run the command
Code:
lsusb
TWICE!!
The first time with adb debug ON (grab the usb address, the second time in the fastboot mode).
You'll get 2 different usb address.
4) make sure your user is in the group "plugdev".
5) restart udev as root with:
Code:
service udev restart
6) Then try with usual commands:
Code:
adb devices or fastboot devices

1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!

TheFlashNewb said:
1st off I appreciate all of your input and help!
On a third computer with Lubuntu installed I finally got it to work! Had to use sudo (which did not work on the Ubuntu install).
Well here I go, wish me luck!
Just for a refresher:
#1 - Unlock through Motorola(no backup needed - phone has never been used)
#2 - Install TWRP
#3 - Reboot into recovery - if I don't I will have to reinstall TWRP
#4 - Flash ROM(Dirty Unicorns potter), then flash gapps
(Question - Should I use the Gapps package from the OpenGapps website or the one on the Dirty Unicorns page?)
#5 - Have fun!
Thanks!
Click to expand...
Click to collapse
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.

sinchan_nohara said:
You can use opengapps they recommend to use stock gapps as it doesn't have inbuilt AOSP apps. Means it doesn't have dialer , contacts , message , clock , calculator , default browser app.
Click to expand...
Click to collapse
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.

TheFlashNewb said:
Thanks for the reply!
On wiping, which partitions should I wipe before installing the ROM? The phone is currently stock and updated to 8.1.
Click to expand...
Click to collapse
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.

sinchan_nohara said:
Cache , dalvic cache , system and data. But before doing anything take backup of efs and persist and keep it safe somewhere in cloud or your PC or both. It would be helpful in future if by chance you messed up your device and lost IMEI.
Click to expand...
Click to collapse
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?

TheFlashNewb said:
Oh wow thanks! Does the stock TWRP for potter(from the TWRP website) have an option to backup those partitions? I cannot find an answer. V 3.2.3-1-potter
Also, does it need to be rooted in order to backup EFS and persist?
Click to expand...
Click to collapse
Yes twrp has option to backup efs and persist. You don't need root for this.