debugging UART3 (ttyMSM2) in gen2 - Blade General

Could somebody answer this question. The ZTE Blade has a serial connector at the back, also see http://android.modaco.com/topic/325947-rs232-on-the-blade/ .
I've seen some old kernel logs, http://pastebin.com/YWtjyRhQ, on a gen1 where ttyMSM2 is found and intialized.
[01-01 00:00:00.470011] [1: swapper]msm_serial: detected port #2
[01-01 00:00:00.470011] [1: swapper]msm_serial.2: ttyMSM2 at MMIO 0xa9c00000 (irq = 11) is a MSM
[01-01 00:00:00.470011] [1: swapper]msm_serial: driver initialized
Click to expand...
Click to collapse
On my device, which is winflashed to GEN2, so i can't test this hypthesis myself unfortunately, i can't get my device to find this serial port. I have a feeling ZTE didn't just disabled fastboot they also disabled this UART3 port, which is a true shame as i want to use this port to display the printk messages to debug some stuff. Question, did ZTE disable UART3 and is it possible to get the port working again..
To test it, you'll need a kernel where config_serial_msm=y and you should see if ttyMSM2 is seen.

Have you tried talking to wbaw? I think he knows tpt stuff quite well

Can answer my own question now, 2.6.32 makes the serial port work..

Related

A70 + 3G USB = not enough bus power

I have 3G usb dongles:
Huawei E1550
ZTE MF100
And this two dongles writes in dmesg:
Code:
usb 2-1: new full speed USB device using musb_hdrc and address 6
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=12d1, idProduct=1001
usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-1: Product: HUAWEI Mobile
usb 2-1: Manufacturer: HUAWEI Technology
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: rejected 1 configuration due to insufficient available bus power
usb 2-1: no configuration chosen from 1 choice
Code:
usb 2-1: new high speed USB device using musb_hdrc and address 5
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=19d2, idProduct=0016
usb 2-1: New USB device strings: Mfr=2, Product=1, SerialNumber=0
usb 2-1: Product: ZTE WCDMA Technologies MSM
usb 2-1: Manufacturer: ZTE,Incorporated
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: rejected 1 configuration due to insufficient available bus power
usb 2-1: no configuration chosen from 1 choice
usb_modeswitch works ok.
It`s fail for Archos 70 IT (8Gb) device?
As it is stated everyewhere, the A70 only outputs 100mA and that doesn't seem enough for those sticks.
So get yourself a usb Powersupply and try again.
Moved to general as not android development
For what it's worth I have got the USB dongle to work with my Archos 101.
I guess this would be one of the reasons to choose a 101 over a 70
Hi i realise this is an old topic but i dont wish to start a new thread if theres already one here.
Im using a 16gb PNY flash drive in my archos 101, latest firmware and it isnt recognising it? iv formatted it every which way and it just wont do.. am i missing something i should have checked? you say you managed to get it working?
Any help appreciated!
Thanks alot.
Sibere just released a Kernel that provides 200mA
Try it
Hey lennb, thanks for the reply. Got another question, im already running SDE and the solution in Ardatdat's thread with a mix of kernals and intframfs.. How would i flash this kernal over that? or instead of it? Im a bit new to the android dev/hack world and i dont wanna brick it hehe.
Any help appreciated!
Thanks
Just do it like you flashed artadats kernel
Boot>>Volume - Button>>Recovery System>>Developer Edition Menu>>Flash Kernel and initramfs
Then just connect your Archos to your pc and copy the two files. Then press ok on archos.
Thanks again Lenbb, iv done a search in the forum trying to find the kernel and the only upload iv found so far to do with the usb hack had to be used in junction with sauron(sp?) kernel, is there a all in one tutorial im missing for this gen8 kernel or is it a case of searching through the posts and compiling it all?
Also, this may sound stupid: Does the flash drive have to be formatted to ext3 to be recogised by the Archos? Iv just thought about any other ways i could try and make this work and found a post on the Archos site saying the android uses ext3... if thats the case i might just slap myself for the over sight!
Any help greatfully appreciated!
Thanks!
Okey, sorry but i dont understand your first question...
Nope it doht have to be ext3, it also can be fat32 and if you have urukdroid you can also host ntfs devices!
haha sorry, im trying not to sound to needy! In basic i was just seeing if theres a all in one thread for the walkthrough of flashing with this usb hack? and cheers for clearing the ext3 question for me!
Nufan1121 said:
n basic i was just seeing if theres a all in one thread for the walkthrough of flashing with this usb hack?
Click to expand...
Click to collapse
What do you mean? Flashing a Kernel is always the same way
___
Edit:
Thank you for giving me the 2. Part of my thanks bar
Aha no worries! you deserve it. Im using the urukdroid 1.0 install method at the moment because i remember in the post i found the usb hack in that it could be use alongside it. Do i have to completely reformat my archos before i flash again?
Im also a bit confused about how to install the new firmware to the sd card? so that i can actually root this thing.
Nufan1121 said:
Do i have to completely reformat my archos before i flash again?
Click to expand...
Click to collapse
Nope, you dont have to do this
But you could joyn sibere (the developer of that kernel) and me at Urukdroid Developement Thread with discuss about this At the moment we want to set the limit up to 500 mA to support HDDs
I will do just that. Im not sure its the right thread but it wouldnt let me post because of my low post count =/. Just one last confusion and i will leave you to your excellent work! haha. Iv got urukdroid 1.0 up and running... but then i realised that sibere's download contained another Zimage and infram. Do i just flash those over the top of urukdroid already installed, or do i completely uninstall my developer edition, then mix sibere's zimage and infram with the urukdroids installer and start again?
Sorry if im not being clear!
Many thanks!
Nufan1121 said:
I will do just that. Im not sure its the right thread but it wouldnt let me post because of my low post count =/. Just one last confusion and i will leave you to your excellent work! haha. Iv got urukdroid 1.0 up and running... but then i realised that sibere's download contained another Zimage and infram. Do i just flash those over the top of urukdroid already installed, or do i completely uninstall my developer edition, then mix sibere's zimage and infram with the urukdroids installer and start again?
Sorry if im not being clear!
Many thanks!
Click to expand...
Click to collapse
Just flash over the top.
msticninja said:
Just flash over the top.
Click to expand...
Click to collapse
Yep, its the Urukdroid 1.1b3 Kernel Just with the Usb modifactions
And you just need 10 Posts to post at the Developer Section
Haha, ill have to hurry and get them then! I installed urukdroid to a 2gb sd yesterday, and was happy with the results apart from a few force closes of some apps and unability to use the market? im not if thats something i did wrong or if its a bug on my archos... I guess ill have to learn more about these divices before i start jumping in and modding them. I flashed the usb kernel imagge and infram over the top of urukdroid's but it didnt give me usb access... im thinking about just buying an adapter untill a simple (for me hehe) guide comes out.
Cheers again =]
Ho well I can post my kernel here too
Is it possible to Flash this usb hack if you are not running uruk?
Currently i am running Chulri root and Harfainx's system memory hack?

ADVICE/SUPPORT : UVC Camera on Samsung Galaxy Tab 10.1- No device Node??

HI,
I am trying to interface the UVC Camera to the Samsung Galaxy Tab 10.1(GT-7510) , but I am not able to see the device node getting created in the shell( I have installed the Linux terminal Shell Application) and rooted the device using this Video .Can somebody plz tell/advice how I can achieve it and access the device Node or at-least get it created.
Following is the log on dmesg :
usb 1-1 new high speed USB device using tegra-ehci and address 97
hub 1-0:1.0 unable to enumerate USB device on port 1 ,
usb 1-1:device v0ac8 p3420 is not supported
On My Laptop I get this output on Dmesg :
[12307.364237] uvcvideo: Found UVC 1.00 device Venus USB2.0 Camera (0ac8:3420)
[12307.366108] input: Venus USB2.0 Camera as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input14
[12308.537059] usbcore: registered new interface driver snd-usb-audio
also i can see the camera getting blinked on connection which proves that it is getting the power-supply and getting connected with the system.
I think there is a support for UVC USB devices in the kernel (not sure) otherwise I am ready with the Kernel For Samsung Tab 10.1 (GT-7500 (Higher Version: GT-7510)) from here .(GT-P7500_MEA_Opensource.zip (requires Login).
Plz assist.
Rgds,
Softy
You seem to know a bit about what you're doing. I'm not really familiar with this device. I did a search and did not find anyone who has don't this yet. The first priority is to get a Linux device in /dev/ folder. This is generally handled by a device driver and a udev rule. Try the newer kernel if you can. The android 4.0 ics has a Linux 3.x kernel. See if switching to ics helps. Try compiling a custom kernel with all modules. Once you have a device, try using SSH or sftp from your desktop under Linux to stream from that device with vlc or another media player.
Do you have any examples of this device in use on mobile Linux? It may require writing an entire kernel driver.
HI,
Yes that is the same line of thinking for us as well.We are trying to compile the kernel and load it .- Ongoing
I believe only the zImage is the one which is to be flashed.But I am little scared to do this.Couldn't find the instructions to loading the Zimage even though I can compile one.
Rgds,
Saurabh
softy007 said:
HI,
Yes that is the same line of thinking for us as well.We are trying to compile the kernel and load it .- Ongoing
I believe only the zImage is the one which is to be flashed.But I am little scared to do this.Couldn't find the instructions to loading the Zimage even though I can compile one.
Rgds,
Saurabh
Click to expand...
Click to collapse
Flash it with Heimdall, even if it won't work you will be still able to get into download mode of bootloader (which you aren't supposed to flash) and reflash the kernel with stock one.

USB to LAN : Trendnet TUE2-ET100

Hi everybody,
Like video said, I'm noob !
I come from french and surely I'm not the better englishman of france, but I need you and I try to resolv my problem :=)
I have iconia a500, and go with it in holidays.
In my room, only RJ45 for internet, not WiFi... And my lady NEED internet ^^
That's why I try to use this device.
But, when I try to use it... It doesn't works :=/
I've seen that with taboonay it can works but it's rom for 3.2 and I am in 4.03...
Here my configuraiton :
CWM-based Recovery v5.5.0.X(thor2002rorev1.7)
Flexreaper 5.1
I use Trendnet TUE2-ET100 for network adaptator.
Have we one rom who can help me plz ?
I wait your help if it's possible.
Thank you.
Hi,
Nobody can help me ?
It would be probably better to just buy simplest access point out there and use it as a bridge between ethernet cable and wifi . You don't even need router functionality if the tablet will be the only device used. Just buy AP, configure it and just connect the cable to the RJ45 socket and voila.
You will probably need to connect AP to the PC with a cable to configure it but you need to do this only once. You need to configure the wifi name and security (preferably WPA2 PSK).
Hi,
Thank you for you answer !
Can we resolv problem without AP ?
The reason it's that we go to hotel and I bagage is full... xD
With USB analyser software (or application), I can see one information about my LAN adaptator... But it doesn't works when I try to use it.
I don't know if one other kernel can help me or if it's with other custom ROM...
Thank you very much for your help and your solution !
But if we have other possibility it's ok for moi :=)
Merci ;=)
Try the following:
Reboot the tablet (do not connect ethernet adapter yet)
In the terminal emulator display run dmesg (you can dump it with dmesg > /sdcard/dmesg1.txt for comparison)
Connect adapter
Run dmesg again and check for differences at the end (dump it with dmesg > /sdcard/dmesg2.txt and then compare both files).
This will tell if the kernel itself is recognizing the device properly as a networking device. If it doesn't then you need different kernel or kernel module for the current one for this device.
If the device is recognized and the proper kernel module is loaded and still no connectivity then one of the following can be true:
The device doesn't send request to acquire IP from DHCP (dhcp client in the rom not configured to support other devices than the built-in ones).
The device receives the IP, but the routing is not being set so the connection is not set as a default route.
The Android itself doesn't recognize the new interface and apps cannot start the connection using Android API (OS thinks it is offline).
Unfortunatelly I don't know much about how the networking on the application level works in Android and I don't have any USB ethernet adapter to do some tesing myself. I would need to ask some friends if they have one.
Very thanks to your help and sorry for this.
Below results dmesg after plug usb adapter.
Usb 1-1: new high speed usb device number 2 using tegra-ehci
Usb...: new usb device found, idVendor=0b95, idProduct=2,
Usb... : new usb device strings: mfr=1, product=2, serialnumber=3
Usb... : product: ax88772
Usb... : manufacturer: asix elec. Corp.
Usb... : seriaonumber xxxxxx
We can see that android see usb device.
But, when i made <ifconfig>, i can see only the wlan0 interface, no eth0 or other...
Maybe i have to mount it ?
Thanks for your help.
No, you don't mount network devices .
It seems that the tablet is not loading any kernel module for this device. I've done some searching and this device requires usbnet and asix modules to be loaded. I have checked if I have those module in my a500 (running CM9) and I don't have any of them.
I think that you would need to build your own kernel with proper modules to gain support for this adapter.
OMG xD
Build my own kernel
ok ok, let's go, I have already help my father to build house, I can did it !
...
Is it difficult to build kernel ? ^^
Are there any tutoriel for this ? or I need help of xda's members ?
Like other post, thank you for your interest and your help.
Sorry to make you spend time on my case
I'm sorry but my knowledge about compiling kernels is limited to PC Linux. I've never crosscompiled kernels for ARM architecture. It shouldn't be that hard. I think that you will need the Android SDK to do that. Search the dev forum.
I've been thinking about the module itself and you probably don't even need to compile whole kernel. You just need the kernel header files for the kernel you are using and you can probably compile the module alone and then just copy it to device. But you need to ask someone that is more knowledgable in this area than me.
hello, have you managed to build module for ICS or jellybean?
i have the same USB LAN adapter (i'm french too ^^)
Hope to have a positive reply!!!
thanks

[Q] Kernel serial console

Hi guys,
I'm looking for a way to read the kernel output during the boot process. I've already tried recompiling the kernel with/without FIQ_DEBUGGER, KGDB_SERIAL and SERIAL_SAMSUNG (_DEBUG), as well as setting the kernel console in the cmdline to every possible /dev/tty* port without any success.
I also tried echoing in every available serial port and use a digital analyzer on a breakout-microusb board to monitor the output. But all of the tty devices seem to be disconnected from the USB port. There are a lot of hints on the internet for other devices, but the most of them use a dialer to get into the service menu (e.g. for smartphones: http://forum.xda-developers.com/showthread.php?t=1515570) or a jig-cable with a resistor between ID and GND (http://redmine.replicant.us/projects/replicant/wiki/SamsungSerial). Both approaches failed on my Nexus 10.
I got no clue what to do next, so I would be very appreciated for any hints or new ideas.
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
EniGmA1987 said:
I dont know much about kernel debug code stuff, but there is this command to see kernel messages in real time:
-adb shell watch "dmesg | tail -40"
Does that display things during bootup?
Click to expand...
Click to collapse
Thanks for that, but as far as I know the ADB daemon is started only after the kernel initialization. I can read the dmesg after Android is booted, but it doesn't help me to debug problems if the kernel panics.
I think I need some kind of a correct serial cable to read the kernel (and bootloader) output, but I couldn't find any working method for N10.
Did you have any luck with your case?

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

Categories

Resources