Database Users

galaxy sII Backtrack5 and Usb Host

Hi I've been working on adding support for usb host support in backtrack 5 running on a chroot session.
The ultimate goal is to be able to use a usb wifi adapter for pentesting, as the interal wifi doesnt support layer-2 or packet injection.
i created the usb host cable,by jumping pin 4 to 5, and was able to power my device by splicing in DC power to the cable.
i'm having issues with busybox in the chroot session. i have ver 1.9 running on the android OS but it seems like there are missing modules in backtrack. NO LSUSB!! grr
i just cant get it to give me any output what so ever
#lsusb
#
. But i know the chroot session reads the host device (OTG). running dmesg (full output attached):
[ 3881.112070] max8997_muic_usb_cb: usb mode=3
[ 3881.112087] otg_power_cb: otg power = 1
--
[ 3881.114323] usb usb cable = 3
[ 3881.114348] usb Enable usb LDO.
[ 3881.114396] max8997-charger max8997-charger: max8997_disable_charging: disable charging
[ 3881.114536] usb check ldo vcc_d(192)
[ 3881.114704] usb check ldo vcc_a(192)
[ 3881.114889] otg_dbg: in s5pc110_otg_drv_probe()::00075
[ 3881.114900] => s3c_otg_drv_probe
[ 3881.115115] otg_host_phy_int : USBPHYCTL=0x1,PHYPWR=0xa40,PHYCLK=0x7,PHYTUNE=0x819b3,USBCFG=0x0
[ 3881.266334] s3c_otghcd s3c_otghcd: S3C OTGHCD
[ 3881.266406] s3c_otghcd s3c_otghcd: new USB bus registered, assigned bus number 2
[ 3881.266463] s3c_otghcd s3c_otghcd: irq 135, io mem 0x12480000
[ 3881.268360] max8922-charger max8922-charger: max8922_enable_charging: disable charging,TA
[ 3881.496575] hub 2-0:1.0: USB hub found
[ 3881.496598] hub 2-0:1.0: 1 port detected
[ 3881.496618] otg_dbg: in root_hub_feature()::00477
[ 3881.496625] => case SetPortFeature -USB_PORT_FEAT_POWER
[ 3881.497347] otg_dbg: in s5pc110_otg_drv_probe()::00175
[ 3881.497358] => OTG HCD Initialized HCD, bus=C110 OTG Controller, usbbus=2
[ 3881.498518] usb otg host : registered
[ 3881.498530] host_notify: ndev name=usb_otg: from state=0 -> to state=1
[ 3881.499742] usb change mode ret=0
--
[ 3883.372113] otg_dbg: in root_hub_feature()::00483
[ 3883.372126] => case SetPortFeature -USB_PORT_FEAT_RESET
[ 3883.432171] otg_dbg: in otg_handle_interrupt()::00087
[ 3883.432182] => Port Interrupt
[ 3883.432192] otg_dbg: in process_port_intr()::00271
[ 3883.432203] => port enable/disable changed
[ 3883.502695] usb 2-1: new high speed USB device using s3c_otghcd and address 2
[ 3883.522370] svn usbdev_open, skip usb_autoresume_device
[ 3883.522488] svn usbdev_open, skip usb_autosuspend_device
[ 3883.524055] hub 2-1:1.0: USB hub found
[ 3883.524407] hub 2-1:1.0: 4 ports detected
[ 3883.534375] max8922-charger max8922-charger: max8922_is_charging: charging state = 0x1
[ 3883.762482] usb 2-1.1: new high speed USB device using s3c_otghcd and address 3
[ 3883.784996] usb 2-1.1: device v0bda p8187 is not supported
[ 3883.785068] host_notify: ndev name=s3c_otghcd: from state=0 -> to state=5
[ 3883.805674] hub 2-1:1.0: unable to enumerate USB device on port 1
--
[ 3932.353319] usb_port_resume = 1283, 4
--
[ 5492.343091] usbsvn_request_resume:run time resume
[ 5492.343107] Host USB : Resume
[ 5492.422261] usb_port_resume = 1283, 4
[ 5492.422906] usb 1-2: svn L0 p.s=1
i have the driver for the device (alfa network ,AWUS036h) and it is supported in linux.
i was able to build the driver in the chroot session, but since it is an ARM distro, will the driver even work.
any help would be awesome.

Some success!
I finally got lsusb to recognize the devices. after many many recompilation of busybox,turns out it was a binding problem between the android and the chroot session.
i ran in terminal emulator: ($mnt = the chroot mount point)
#mkdir -p $mnt/dev/bus/usb
#mount -o bind /dev/bus/usb /$mnt/dev/bus/usb
and now in the chroot session:
[email protected]:/#lsusb
Bus 002 Device 002: ID 05e3:0608 Genesys Logic, inc USB-2.0 4-port HUB
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1519:0020
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
as you can see i plugged in a usb hub to power the device, just to test.
i'm going to be working on compiling the driver.
hopefully beaple to use the aircrack suite soon on my phone.

Two cheers for you mate. Hope you bring in something soon.
Sent from my GT-I9100 using XDA Premium App

Driver
I'm trying to compile the RTL8187 driver for the ARM architecture . I've never done this sort of thing, so any advice on kernel modules would be greatly appreciated.
i'm using the ARM toolchain from :
http://www.codesourcery.com/sgpp/lite/arm/portal/[email protected]=lite
compiling with the i19100 kernel source compiled by XDA members (not the tar files from samsung).
If anyone has any experience with Cross compiling, any help would be awesome.

Holy crap i hope u get this running.
I would love to have bt4 on my phone
I hope u make a full how to guide once u r done
Great work

Boom! Awesome stuff

Zionator said:
Holy crap i hope u get this running.
I would love to have bt4 on my phone
I hope u make a full how to guide once u r done
Great work
Click to expand...
Click to collapse
bt5 is already avalible for i9100
http://forum.xda-developers.com/showthread.php?t=1162662

more good stuff
i've finally got the driver compiled for ARM without it spewing Piles of errors.
now i've actually got to test them.
2 modules:
ieee80211.ko
rtl8187.ko
these would either be loaded in android OS with "insmod" in the init.rc file, so it's loaded on boot. Or in the backtrack 5 chroot session.
now i've got LSUSB working and displaying Some connected devices, however devices such as usb keyboards and My Wifi card are not displayed (the Usb host port is displayyed though)
From the reading i've done i'm pretty sure this is due to a vendor permissions issue.
in a file simmilar to this:
/etc/udev/rules.d/50-android.rules
now i havnt been able to find this file on my phone. or simmilar.
this file allows the types of vendors allowed to connect.
an example command to be added:
Code:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666", NAME=="android"
When i run lsusb on my ubuntu virtual machine, with the card plugged in i get:
Bus 002 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
so i'd have to add a line like this :
Code:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bda", MODE="0666", NAME=="Realtek"
so in short, If ANYBODY knows where a vendors permission file resides, please post something.
sweet thanks

HUGE!
O MAN i had no IDEA i'd get this far, i've never even used linux that much untill i got this phone!
so as it turns out the permission issue with pretty well ALL devices is very prevalent
you have to allow android OS to connect to specific vendors, i've tested it woth sevral keyboards.
the vendor codes can be found here
HTML:
http://developer.android.com/guide/developing/device.html
but here they are
Code:
Company USB Vendor ID
Acer 0502
ASUS 0b05
Dell 413c
Foxconn 0489
Garmin-Asus 091E
Google 18d1
HTC 0bb4
Huawei 12d1
K-Touch 24e3
KT Tech 2116
Kyocera 0482
Lenevo 17EF
LG 1004
Motorola 22b8
NEC 0409
Nook 2080
Nvidia 0955
OTGV 2257
Pantech 10A9
Philips 0471
PMC-Sierra 04da
Qualcomm 05c6
SK Telesys 1f53
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
Toshiba 0930
ZTE 19D2
so an example of this.
i have a lenovo usb keyboard that i want to use.
so log in as root, create file /etc/udev/rules.d/51-android.rules, and add these line:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="17EF", MODE "0666", NAME=="lenovo"
so in bash:
Code:
su
mount -o remount,rw system /system
mkdir -p /etc/udev/rules.d/
cd /etc/udev/rules.d/
echo SUBSYSTEM=="usb_device", SYSFS{idVendor}=="17EF", MODE "0666", NAME=="lenovo" > 51-android.rules
THIS can be applied to any usb device, so far as i;ve tested. if you cant find the vendor codes in the table, you can get them by plugging the device into a linux box and running lsusb and it's the first set of digits so
bus ### dev ###: ID <this one>:blah "some company"
i'll put together a full tutorial up since NO ONE HAS PUT ONE UP AS FAR AS I"VE SEEN. this would add support for pretty well android devices with OTG host mode!!

Any news on this ?

So ****tiest week ever
my galaxy s2 stopped working, put it in to charge and it wont turn on. no lights no nothing.
i've tried a usb jig.
no dice.
i phoned samsung to get it repaired to replaced.
i sent it in a week ago and i just got it Rushed back from them saying that since it's not a canadian phone; they cant service it.
turns out it was bought in chile.
i have a 700$ paperweight. isnt that awesome
JDouce said he managed to compile a driver successfully

Damn, that's worst news I heard all day. Any ideas how it happened?

Sorry to hear that ... there must be a way to fix your phone without sending it to Chile

Td8f4, huge thanks for posting your findings.
I compiled kernel modules for my ralink3070, which is the . I even had them loaded with insmod. But it didn't work. dmesg says "this device is not supported".

Any news on this, is this manual written some place?
I tried writing this udev rule, but with no effect so far. I am also running on Galaxy S2, with Lite'ning ROM 6.1 (Android 2.3.4, Kernel 2.6.35-11 ninphetamine 2.0.5+).
Edit: I did not see page 2 of this thread... sorry for your phone Td8f4... but then trying to get the warranty when you re-flashed it... and overclocked it, you have little chances. Good luck anyway.
If anyone get the USB device to actually appear in lsusb, give me a sign, I only get flashdrives and hubs to appear, a serial2usb won't.

I now figured out that the problem was due to CONFIG_SEC_WHITELIST and driver/usb/core/sec_whitelist.h One or the other has to be modified, both have been tested to be working. With the default falues, devices other than a few defined one (HID, cameras, mass storage, hub) won't be connected at all and will not appear in lsusb or dmesg.
The next step once they appear in lsusb and dmesg with a line "usb 2-1: device v0403 p6001 is not supported" is to find which driver is needed and either compile it within the kernel, or compile it as a module and insmod it manually. You have succeeded that step when you get a new line in dmesg from your device driver.
The next step again is to find an application using the driven device (I am at that step now, for a usbserial device)

Hi,
I am currently trying to get the usbserial-module working on Siyah-kernel.
In fact, usbserial and ftdi_sio both load (the same device works fine with those modules on a desktop. Yes, I have compiled them for ARM agains Siyah-Kernel and not just copied them from desktop ;-) ), but s3c_otghcd 'snatches' away the device before I can get a hold of it.
Have a look at my post here:
http://forum.xda-developers.com/showpost.php?p=18299539&postcount=3712
If you can give me any further leads (should "CONFIG_SEC_WHITELIST=n" be enough, and does it break other things, like mouse / hub support?), that would be very much appreciated .
EDIT: Got it working with an external DIGITIZER, I can now watch analog signals with 5 GS/s on my phone... oscilloscope to go!
So "CONFIG_SEC_WHITELIST=n" breaks nothing (thumbdrives still work), but enables a whole world of possibilities.
EDIT2: A nice picture can be seen here:
http://forum.xda-developers.com/showpost.php?p=18328481&postcount=4032

watching this thread with great interest, if the OP has a donate link to go towards a new phone i'm sure plenty of people might contribute

Td8f4 said:
So ****tiest week ever
my galaxy s2 stopped working, put it in to charge and it wont turn on. no lights no nothing.
i've tried a usb jig.
no dice.
i phoned samsung to get it repaired to replaced.
i sent it in a week ago and i just got it Rushed back from them saying that since it's not a canadian phone; they cant service it.
turns out it was bought in chile.
i have a 700$ paperweight. isnt that awesome
JDouce said he managed to compile a driver successfully
Click to expand...
Click to collapse
Depending on how far you want to go to repair it, you can always unbrick your phone. Search for Jtag repair. You can reflash through the built in testing ports.

some new?? galaxy S2 LIVE???

MSM8960 jtag!

This thread was initially started for the purpose of unbricking the HTC evo 4g lte (HTC Jewel) with the possible help of JTAG. But since i was unable to find any corresponding jtag mod/pinouts for any other phone, the thread has been re-titled as MSM8960 Jtag. It would be good if members share there knowledge about possibilities of discovering JTAG locations on newer Snapdragon S4 based chipsets
A short history how the phone was bricked.
Code:
My phone was S-OFF with lazypanda and flashed the OMJ 1.13 stock rooted odex rom. After that i downloaded latest radio from the radio thread and flashed it. However it seems that the wifi gave up due to this, it only showed error. It never turned on, so i tried to flash another previous version radio which seems to be flashed normally without any issues. After this the phone never showed anything, windows detects it as QHUSB_DLOAD. I have tried to use lazypanda evo lte unbricker but it is not able to find the device!
[QUOTE][email protected]:~/new$ sudo ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[/QUOTE]
However the getbrickdevice script which is in with yarrimapirate downgrade thread is able to pick the phone
[QUOTE][email protected]:~/hboot$ sudo ./getbrickdrive.sh
Your bricked phone is accessible at /dev/sdd[/QUOTE]
lsusb output
[QUOTE][email protected]:~/hboot$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 154b:0059 PNY
Bus 003 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root 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 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 046d:c068 Logitech, Inc. G500 Laser Mouse
[/QUOTE]
Now, when i use this command
[QUOTE]sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576[/QUOTE]
It outputs the below results
[QUOTE][email protected]:~/hboot$ sudo ./emmc_recover_new -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdd12 -c 24576
================= emmc_recover 0.3 alpha 2 ==========================
Using chunksize 24576
Messing up with device /dev/sdd12, ARE YOU SURE?
CTRL+C if not, ENTER to continue
Waiting for device.
[/QUOTE]
Running the lanzypanda unbricker shows
[QUOTE][email protected]:~/unbrick$ sudo ./PandaFinder -d /dev/sdd
============ PandaFinder 0.1 ===========
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Bricked device will appear to device node /dev/sdd
ARE YOU SURE?
CTRL+C if not, ENTER to continue
Realnode is /dev/sdd12
Ready to go.
(1) Remove MicroSD card from phone
(2) Connect bricked EVO 4G LTE to usb
Press ENTER when ready
*** Do NOT remove usb cable during process
*** Do NOT press any buttons until PandaFinder requests you to do that!!
******** Press ENTER when you understand this!! Really ********
Lets try unbricking once, before we run it really
Press ENTER to start test
Waiting for device.
- found /dev/ttyUSB1 - OK
Waiting device /dev/sdd12.......
[/QUOTE]
dmesg output
[QUOTE][ 208.362070] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 208.362094] qcserial 1-1:1.0: device disconnected
[ 242.659408] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 242.802505] usb 1-1: New USB device found, idVendor=05c6, idProduct=9008
[ 242.802511] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 242.802514] usb 1-1: Product: QHSUSB_DLOAD
[ 242.802517] usb 1-1: Manufacturer: Qualcomm CDMA Technologies MSM
[ 242.805254] qcserial 1-1:1.0: Qualcomm USB modem converter detected
[ 242.805492] usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
[/QUOTE]
And here it gets stucked forever, previously when the reset command was being sent to the phone, it shows Qualcomm Inc in lsusb output and after some 7-10sec it swtich to Qualcomm QDL. But it only gets stucked onto Qualcomm QDL now.

Please post in the proper sections. This belongs in Q&A not development...

Yep... MOVED to Q and A

Might be better asking here:
http://unlimited.io/support.htm
Sent from my HTC One X using xda app-developers app

Can any1 provide any info on jtag pinouts of this device? It seems that i m not ableto recover the phone unless i jtag it. The riff box supports ressurection for all the msm8960 snapdragon s4 based phones so i think it will be able to recover evo lte also. I asked dexter @ thr irc channel and he said that screwed things up and hence will not be able to recover the device using thr provided method
Sent from my LG-LS840 using Tapatalk 2

You might find something here, these guys are trying to map everything. MSM8960 Info

The NRST pad location is shown in this picture of evo 4g lte motherboard. It would be really appreciated if some1 can help in location the remaining pads as well.
Full size image
http://img221.imageshack.us/img221/1503/cam00068.jpg

Bump, now since the phone is completely dead, m trying to locate the jtag pads on this phone. here is a rough idea for jtag pads. Let me known if any1 is willing to help.
https://www.dropbox.com/s/gbfyaf5aouc27ee/htcevo4glte2.jpg
The pad locations are just assumptions on the basis of regular jtag allocations on various htc phones.

Below are some of the voltage readings which are observed with Riff Box Voltage probe.
https://www.dropbox.com/s/reipjimu8toola4/CAM00068.jpg
http://pastebin.com/ZBw8TFcg
+C= Cable attached.
+B= Battery attached.

funkym0nk3y said:
Below are some of the voltage readings which are observed with Riff Box Voltage probe.
https://www.dropbox.com/s/reipjimu8toola4/CAM00068.jpg
http://pastebin.com/ZBw8TFcg
+C= Cable attached.
+B= Battery attached.
Click to expand...
Click to collapse
which adapter are you using? riff? ort? I was searching for just this because I have a very difficult HTC One xl brick. your thread was the first Google result, and this was the second:
http://www.cdmahosting.com/showthread.php?p=1491
I hope that helps!
at $200, the ort-jtag is a tempting buy, esp. When you see so many tough bricks lately. too bad I don't even know where to start with it... lol

=JKT= said:
which adapter are you using? riff? ort? I was searching for just this because I have a very difficult HTC One xl brick. your thread was the first Google result, and this was the second:
http://www.cdmahosting.com/showthread.php?p=1491
I hope that helps!
at $200, the ort-jtag is a tempting buy, esp. When you see so many tough bricks lately. too bad I don't even know where to start with it... lol
Click to expand...
Click to collapse
I know, in my country i got it for around 100$ (RIFFBOX, thanks to a known person). Riff box new update also supports MSM8960 chipset and so i think once we are able to locate jtag pads, thr isnt going to be any problem.

so in the case of, say, jewel and evita, the soft part of the jtag will be the same (using the right imgs of course) since they are both msm8960, but the connection points will be different because the board layout is different? but, on the other hand, the correct pins will show similar behaviour re: voltage as another msm8960, correct? Hopefully they will not be in the set that seems to hover around 1.8v...
One last question. will the pin voltage behaviour be more or less consistent between chip sets? I'm specifically thinking of the pins that have unique behaviour like 25, 26, 29 on your pastebin.com chart. If so, we might get lucky referring to a somewhat similar, but known chip set.

Hopefully yes, and that might provide help in locating possible known behavior and voltages on other similar phones. But i think this totally depends on the pull up resistors being used by manufacturers? I might be wrong here, maybe more and older hardcore junkies can shed some light on this.

funkym0nk3y said:
Hopefully yes, and that might provide help in locating possible known behavior and voltages on other similar phones. But i think this totally depends on the pull up resistors being used by manufacturers? I might be wrong here, maybe more and older hardcore junkies can shed some light on this.
Click to expand...
Click to collapse
yeah. this seems like an esoteric topic, and google isn't yielding results too easily. perhaps I'm just searching for the wrong thing. jtag is a really broad topic, and I'm unsure what the crucial variables are to narrow the search.
edit: this method seems helpful. take a look, if you haven't already seen it.

Success
Finally able to find all the necessary pinouts.
Thanks to htc unbrick team.

funkym0nk3y said:
Finally able to find all the necessary pinouts.
Thanks to htc unbrick team.
Click to expand...
Click to collapse
did you share these somewhere, or was it like a "for your eyes only" type thing?

At the moment its only for my eyes thing, will update the pinout pic and post here

Update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy.

funkym0nk3y said:
Update
View attachment 1471313
Enjoy.
Click to expand...
Click to collapse
You rock. Hopefully this will help us Evita people out with JTAGing some stubborn bricks.

Evita is already jtagged
Sent from my EVO using Tapatalk 2

[Q] Any way to recover files from S4 with dead screen?

I have an old Canadian Bell based Galaxy s4, with a dead screen. I'd like to try to get files off it, but did not enable usb debugging mode prior to the screen breaking.
Is there any way to access the file system on the phone in this situation? I've done a bit of looking around and can see that I should be able to access it via adb if I have usb debugging turned on, but debugging isn't on in this case.
I have usb connected the phone to my fedora machine and can see via dmesg that it does get detected. I can hear the thing start up, but beyond that I can't see anything else.
Googling around it sounds like I should be able to load a recover kernel, with debugging turned on if I use the right process, but I can't find enough into to get me going.
dmesg output is below just in case it helps...
.....................................................................................
[ 4104.343749] usb 2-2: USB disconnect, device number 6
[ 4180.261104] usb 2-2: new high-speed USB device number 7 using ehci-pci
[ 4180.376385] usb 2-2: New USB device found, idVendor=04e8, idProduct=6860
[ 4180.376390] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4180.376394] usb 2-2: Product: SAMSUNG_Android
[ 4180.376396] usb 2-2: Manufacturer: SAMSUNG
[ 4180.376399] usb 2-2: SerialNumber: ........
Any help is much appreciated!

If you can get a custom recovery on you can use adb without use debugging on. I assume you have an i337m. Try this with twrp http://galaxys4root.com/clockworkmodtwrp-recoveries/
Sent from my Nexus 9 using XDA Free mobile app

If you have a custom recovery plug it up to hdmi thru HML and use the TV for the screen. Hopefully the touchscreen still works. This worked for mine. No lcd but the digitizer was still good.

[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.

Will not boot after forced update through adb

A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).

marcosource said:
A while ago now I tried to update the stock rom with the update that it downloaded ota and repeatedly failed to install.
This in turn ended with the phone not giving any signs of life at all.
Put in uUSB cable to charge, no reaction on display and no charge led.
hold power button, no reaction etc...
I have opened it up, disconnected the battery, waited a while then reconnected with no change.
If I remember correctly (I bought a huawei p20 lite since I needed a working phone and have been using it since), I had unlocked the bootloader and had twrp (spelled wrong?).
Is it a paper weight now or is there any way to get any life into it again?
I do have JTAG programmers if I can find the correct places to connect the leads on the board and also soldering experience on very small things (not bga ic's).
Click to expand...
Click to collapse
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards

Dadditz said:
Hello.
In order to install stock updates you needed stock recovery, it does not work with TWRP recovery.
I'm not a technician but I think, I repeat I think, you f***ed the phone.
Use your tester or take your phone to the service point, maybe the motherboard is gone ..
P.S.: Have you tried first with another cable / charger, both ?
Regards
Click to expand...
Click to collapse
I've tried a lot of things, including other cables, chargers ++
I guess it is dead.. ah well..
Thanks anyway

Have you tried booting to Fastboot?

The Restless Soul said:
Have you tried booting to Fastboot?
Click to expand...
Click to collapse
Can't get any sign of life from it at all.
In linux, if you connect a usb device you see a message with a command called dmesg that gives info about the connected device, there is no reaction when i connect it.
Example when connecting my p20 lite:
[176821.173652] usb 1-6: new high-speed USB device number 18 using xhci_hcd
[176821.326319] usb 1-6: New USB device found, idVendor=12d1, idProduct=107e, bcdDevice= 2.99
[176821.326321] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[176821.326322] usb 1-6: Product: ANE-LX1
[176821.326323] usb 1-6: Manufacturer: HUAWEI
[176821.326324] usb 1-6: SerialNumber: <REDACTED>
[176821.355138] usb-storage 1-6:1.1: USB Mass Storage device detected
[176821.355224] scsi host6: usb-storage 1-6:1.1
[176821.355301] usbcore: registered new interface driver usb-storage
[176821.356740] usbcore: registered new interface driver uas
[176822.386058] scsi 6:0:0:0: CD-ROM Linux File-CD Gadget 0404 PQ: 0 ANSI: 2
[176822.386549] sr 6:0:0:0: Power-on or device reset occurred
[176822.386980] sr 6:0:0:0: [sr0] scsi-1 drive
[176822.386981] cdrom: Uniform CD-ROM driver Revision: 3.20
[176822.387121] sr 6:0:0:0: Attached scsi CD-ROM sr0
[176822.387181] sr 6:0:0:0: Attached scsi generic sg3 type 5
[176822.869111] ISO 9660 Extensions: Microsoft Joliet Level 1
[176822.872240] ISOFS: changing to secondary root
Click to expand...
Click to collapse
And when connecting the p9 lite, there is no reaction what so ever.