I have rooted KF HD 8.9 with the default amazon rom am trying to update the rom to the CM11
I am trying to follow the tutorial http://forum.xda-developers.com/showthread.php?t=2128175]
I can connect using adb devices and see my device but the following command "fastboot -i 0x1949 getvar product" or "fastboot -i 0x1949 reboot" does not work. The only thing i get is "< waiting for device >" message.
The device is rooted and i can get it to show the fastboot prompt on the KF by using adb shell su -c "reboot bootloader" commands. I have attached the device manager status when the KF gets into fastboot stage
{
"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"
}
Can anyone suggest how do i get past this.
Update the drivers for the device with the triangle to the ones in my signature. So download drivers from my signature, extract them somewhere, right click that device, hit update drivers, and point it to where you extracted mine.
Personally I would use this tutorial for what you are trying to achieve, but the downside is if you somehow don't see the check box above the red warning text and check it off then you will have a nice red screen on reboot and if you think its hard to get fastboot working right now well wait until you have to update that driver in a 3 second time frame. Then again Linux makes it way easier because of how it loads up drivers, so that's an easy way to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Tried the driver in your link before posting this thread and it did not seem to work for me.
I am going to try the linux option.
stunts513 said:
Update the drivers for the device with the triangle to the ones in my signature. So download drivers from my signature, extract them somewhere, right click that device, hit update drivers, and point it to where you extracted mine.
Personally I would use this tutorial for what you are trying to achieve, but the downside is if you somehow don't see the check box above the red warning text and check it off then you will have a nice red screen on reboot and if you think its hard to get fastboot working right now well wait until you have to update that driver in a 3 second time frame. Then again Linux makes it way easier because of how it loads up drivers, so that's an easy way to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Its also possible you have a composite device that need to be removed first, only way to know is to look at each composite USB device's vid number and see if it is 1949, if that's not the case then maybe you have a vid and pid I haven't added to my drivers. But yea go for and Ubuntu 13.10 live CD/USB, makes things really simple, you just boot it up, install fastboot from the Repo's, and run the command with device off and then plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk
I tried it with Ubuntu and it did not see to work.
adb devices was returning my device
fastboot devices was not returning anything.
Is there a specific way to install the driver on linux. I just downloaded the android sdk and unzipped it and the adb command was returning my device right off the bat.
stunts513 said:
Its also possible you have a composite device that need to be removed first, only way to know is to look at each composite USB device's vid number and see if it is 1949, if that's not the case then maybe you have a vid and pid I haven't added to my drivers. But yea go for and Ubuntu 13.10 live CD/USB, makes things really simple, you just boot it up, install fastboot from the Repo's, and run the command with device off and then plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Interesting, well Linux has the driver built in, so there's not need to install anything, did you say you had adb access in fastboot mode???
Sent from my Amazon Kindle Fire HD using Tapatalk
In Linux adb does not work if i put the device in fastboot mode using adb sudo command.
Does it have anything to do with device itself. I know it is unlocked , because i managed to get play store on it, but is there a chance it is not fully unlocked
stunts513 said:
Interesting, well Linux has the driver built in, so there's not need to install anything, did you say you had adb access in fastboot mode???
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Let's use the term rooted, unlocked has a different meaning that will never apply to the kfhd... Anyways um so your saying if you "adb reboot bootloader" and it goes into fastboot it doesn't get recognized by Ubuntu when running the command "fastboot -i 0x1949 getvar product"? By the way there's a much easier way to install the adb and fastboot command by running this in a terminal, though if your are on a live CD you might wanna run "sudo apt-get update" first before running this. In a terminal you can just run "sudo apt-get install android-tools-adb android-tools-fastboot", way smaller and you don't have to add anything to the system paths for anywhere usage.
Sent from my Amazon Kindle Fire HD using Tapatalk
Yes your statement is accurate. Any suggestions on what i can try?
stunts513 said:
Let's use the term rooted, unlocked has a different meaning that will never apply to the kfhd... Anyways um so your saying if you "adb reboot bootloader" and it goes into fastboot it doesn't get recognized by Ubuntu when running the command "fastboot -i 0x1949 getvar product"?
Click to expand...
Click to collapse
I have a full install not a live boot version, so i will try your suggestion of apt get so that it gets installed in the path.
stunts513 said:
By the way there's a much easier way to install the adb and fastboot command by running this in a terminal, though if your are on a live CD you might wanna run "sudo apt-get update" first before running this. In a terminal you can just run "sudo apt-get install android-tools-adb android-tools-fastboot", way smaller and you don't have to add anything to the system paths for anywhere usage.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
When it goes into fastboot unplug it and plug it back in, then post back the last few relevant line of your dmesg along with the results of running lsusb.
Sent from my Amazon Kindle Fire HD using Tapatalk
Looks like dmesg has some error statements after i put it to fastboot mode. Not sure what it means
[ 457.028880] usb 3-3: >device descriptor read/8, error -71
[ 457.148762] usb 3-3: >device descriptor read/8, error -71
I have attached the complete output in the attachments including a lsusb -v output
lsusb output
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 007: ID 1949:0008 Lab126
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 001 Device 003: ID 13d3:5188 IMC Networks
Bus 001 Device 004: ID 03eb:8417 Atmel Corp.
dmesg output
[ 336.727802] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 336.727815] usb 3-3: >New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 336.727820] usb 3-3: >Product: Jem-PVT-Prod-04
[ 336.727824] usb 3-3: >Manufacturer: Texas Instruments
[ 336.727827] usb 3-3: >SerialNumber: 5FA2000040002FFF
[ 336.728560] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 336.728572] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 339.209337] usb 3-3: >USB disconnect, device number 3
[ 349.330783] usb 3-3: >new high-speed USB device number 4 using xhci_hcd
[ 349.357003] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 349.357013] usb 3-3: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 349.357016] usb 3-3: >Product: Kindle
[ 349.357018] usb 3-3: >Manufacturer: Amazon
[ 349.357020] usb 3-3: >SerialNumber: B0C9100424870NEP
[ 349.357628] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 349.357639] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.548583] usb 3-3: >USB disconnect, device number 4
[ 391.913265] usb 3-3: >new high-speed USB device number 5 using xhci_hcd
[ 391.935540] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 391.935547] usb 3-3: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 391.935551] usb 3-3: >Product: Kindle
[ 391.935554] usb 3-3: >Manufacturer: Amazon
[ 391.935556] usb 3-3: >SerialNumber: B0C9100424870NEP
[ 391.935871] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935878] usb 3-3: >ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935884] usb 3-3: >ep 0x83 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935890] usb 3-3: >ep 0x3 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 452.776441] usb 3-3: >USB disconnect, device number 5
[ 456.872640] usb 3-3: >new high-speed USB device number 6 using xhci_hcd
[ 457.028880] usb 3-3: >device descriptor read/8, error -71
[ 457.148762] usb 3-3: >device descriptor read/8, error -71
[ 457.364566] usb 3-3: >new high-speed USB device number 7 using xhci_hcd
[ 457.382406] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 457.382415] usb 3-3: >New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 457.382421] usb 3-3: >Product: Jem-PVT-Prod-04
[ 457.382425] usb 3-3: >Manufacturer: Texas Instruments
[ 457.382429] usb 3-3: >SerialNumber: 5FA2000040002FFF
[ 457.383102] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 457.383118] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
Well that is interesting, it seems Ubuntu saw it in fastboot mode, not sure what was with the descriptor errors, those are usually bad because it can't retrieve the vendor is and such but it seems to have done that, lab126 is the kindle BTW so it showed up in lsusb as well. Its late and I don't wanna get on my laptop to check something so I'll just ask, are you plugged into a USB 2.0 or 3.0 port? Just wanna mention USB 3.0 and fastboot don't mix well.
Sent from my Amazon Kindle Fire HD using Tapatalk
It was connected to USB 2.0. BTW once in fastboot mode , adb devices also does not work.
stunts513 said:
Well that is interesting, it seems Ubuntu saw it in fastboot mode, not sure what was with the descriptor errors, those are usually bad because it can't retrieve the vendor is and such but it seems to have done that, lab126 is the kindle BTW so it showed up in lsusb as well. Its late and I don't wanna get on my laptop to check something so I'll just ask, are you plugged into a USB 2.0 or 3.0 port? Just wanna mention USB 3.0 and fastboot don't mix well.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Adb isn't supposed to work with fastboot. I don't see why fastboot isn't picking it up, as long as any fastboot command has the "-i 0x1949" parameter it should run the fastboot commands, I mean Linux is picking it up in fastboot so this is odd.
Sent from my Amazon Kindle Fire HD using Tapatalk
Found this info in another thread would this mean that i have a version of kindle on which fastboot has been disabled.
Would it make sense to try the commands to load the TWRP?
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
http://forum.xda-developers.com/showthread.php?t=1850038
*The stock bootloader has been updated by Amazon to not display anything with "fastboot devices" and you can only enter one fastboot command at a time before you have to shut it down and start it up again. I have come up with a dirty workaround to deal with it so if you have a stock bootloader and get "Device Offline", just try to select one of the options anyway. The script will hopefully get you through it.
*32bit libraries are necessary for this to work. The script will detect whether you are running 32 or 64 bit and download the 32bit libs if necessary. The problem with this is Ubuntu is no longer supporting ia32-libs and they may or may not download when needed. It's best to use a 32bit system or create a 32bit LiveUSB to avoid any problems, although I've never personally had any problems downloading them.
That article is about kf1's, you have an HD 8.9, and they never had fastboot disabled in them, only the hdx's did and it wasn't to the point where you couldn't get into it. I wouldn't mind trying to fix this remotely with something like team viewer, but even a ssh might work.
Thought I'd mention I would a posted this sooner but my kindle went nuts and i couldn't access xda for some reason.
Sent from my Amazon Kindle Fire HD using Tapatalk
Do you have suggestions on what you want me to try. I am quite well versed in software development, but this is too specific to be in my area of expertise. So if u give me some hints i might be able to figure it out
stunts513 said:
That article is about kf1's, you have an HD 8.9, and they never had fastboot disabled in them, only the hdx's did and it wasn't to the point where you couldn't get into it. I wouldn't mind trying to fix this remotely with something like team viewer, but even a ssh might work.
Thought I'd mention I would a posted this sooner but my kindle went nuts and i couldn't access xda for some reason.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
At this point I am getting low on advice. Its being seen in fastboot but yet not working with the fastboot command, I'm either going for user error or bootloader malfunction at this point but I could be wrong. If indeed thenbootloader is malfunctioning, you could reflash the bootloader from adb if you can still get adb access, it would just be a simple matter of pushing it to the sdcard, md5sum-ing it to verify integrity, then dd-ing it to the right partition, probably with bs=1 option, as I have noticed people with hard bricks that used the soldering method had to pass bs=1 or it wouldn't work. If you can still get adb access and want to attempt doing it I will post the actual commands you will want to run.
Sent from my Amazon Kindle Fire HD using Tapatalk
I finally figured got flashboot to work and managed to get CM11 on it.
I think it was a user error , not really understanding how flashboot really worked.
I feel so stupid eating up so much of your time, especially considering i am a IT person myself.
I really appreciate all your help.
stunts513 said:
At this point I am getting low on advice. Its being seen in fastboot but yet not working with the fastboot command, I'm either going for user error or bootloader malfunction at this point but I could be wrong. If indeed thenbootloader is malfunctioning, you could reflash the bootloader from adb if you can still get adb access, it would just be a simple matter of pushing it to the sdcard, md5sum-ing it to verify integrity, then dd-ing it to the right partition, probably with bs=1 option, as I have noticed people with hard bricks that used the soldering method had to pass bs=1 or it wouldn't work. If you can still get adb access and want to attempt doing it I will post the actual commands you will want to run.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
No problem, I tend to do that in other fields sometimes too. Still learning about the porting process for ROMs.
Sent from my Amazon Kindle Fire HD using Tapatalk
Related
Hey all,
So I was using my KF just fine with hashcode's AOSP Jelly Bean rom. That rom was on there for more than a month and then suddenly ,as of yesterday, adb refuses to connect. Fastboot on the other hand works just fine.
I'm running Debian Squeeze on and old Thinkpad R51. Both adb and fastboot binaries are in my PATH, and my 51-android.rules looks as follows...
Code:
# Amazon
SUBSYSTEM=="usb", ATTRS{idVendor}=="1949", MODE="0666", GROUP="plugdev"
# HTC
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
# Lenovo
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666", GROUP="plugdev"
# Motorola
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
Running "adb kill-server" and then "adb devices" does not show the device at all. I switched to the jandykane rom and it's still the same. I'm currently in the stock amazon 6.3.1 rom and still I get nothing. I did a full /cache /data /system /sdcard wipe after installing each rom. Running "lsusb" I get...
Code:
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 040: ID 1949:0006 Lab126
Bus 001 Device 002: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And running "dmesg | tail" (only posted what is shown after I plug in the KF), I get...
Code:
[ 8851.136202] usb 1-4: new high speed USB device using ehci_hcd and address 40
[ 8851.269079] usb 1-4: New USB device found, idVendor=1949, idProduct=0006
[ 8851.269090] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8851.269099] usb 1-4: Product: Kindle
[ 8851.269106] usb 1-4: Manufacturer: Amazon
[ 8851.269114] usb 1-4: SerialNumber: 1CDE000600000001
[ 8851.270544] usb 1-4: configuration #1 chosen from 1 choice
[ 8851.277370] scsi29 : SCSI emulation for USB Mass Storage devices
[ 8851.284978] usb-storage: device found at 40
[ 8851.284986] usb-storage: waiting for device to settle before scanning
[ 8856.290243] usb-storage: device scan complete
[ 8856.290897] scsi 29:0:0:0: Direct-Access Amazon Kindle 0001 PQ: 0 ANSI: 2
[ 8856.295474] sd 29:0:0:0: Attached scsi generic sg3 type 0
[ 8856.316198] sd 29:0:0:0: [sdc] Attached SCSI removable disk
I am able to do adb commands just fine on a Droid X2. The DX2 is shown in the device list and I can successfully send commands. I've used the same cable for both the DX2 and the KF. I've tried another working cable and still nothing. I can successfully use adbWireless to send commands. I even went as far as clean installing Debian Wheezy and setting up the udev rules for adb/fastboot access, and still no success.
Is there anything I can try to fix this problem. What could cause fastboot to work but not adb. My best guess is that it may be hardware failure.
Oh and one last thing, In hashcode's jelly bean rom, I was able to mount the sdcard partition when connected via usb to my computer. I could browse the drive and everything. It also works on the stock amazon 6.3.1 update.
Also, I've been using an adb and fastboot binary that has been compiled with the Amazon device id included in the source code (0x1949). I've been using those binaries for the longest without any problems but I don't know if they could have caused any hardware damage.
I noticed as well some changes in device id's . Make a backup and flash this http://forum.xda-developers.com/showthread.php?t=1778010 see if your adb doesn't again work just out of curiosity
Edit: some have complained about not having adb access after flashing JB but this I believe only existed on windows on Linux that should not have become a problem because of static drivers.
The problem seems to be my Thinkpad. I have no idea what happened to it considering USB mass storage mode and fastboot work perfectly fine. I've now plugged the KF to my desktop and I can see my device and am able to send commands via adb just fine. That's weird.
Stranger things have happened I would think more common to have no fastboot and have adb but yes that's strange
Hi everyone,
I am not a developer, i searched for finding how to make motorola xoom WIFI to connect with Huawei LTE 4G E392,
But i didn`t find.
So please if someone can help developing.
Here is what i found
zerox981 said:
This is the way I get my dongle (Vodafone K4605) working with the latest TeamEOS nightly wingray (84 atm ).
Tools I use:
WinSCP - http://winscp.net/eng/index.php
SSHdroid - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroid&hl=en
putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/
1) Download the latest development overlay from this thread:
http://forum.xda-developers.com/showthread.php?t=1513490
2) Delete the drivers you don't need from the zip file. (xoom_dev_overlay_v4.zip\data\local\lib\modules\).
For my needs it's enough to keep only the option.ko and usb_wwan.ko.
3) Flash the dev. overlay.
4) Install pppd, usb_modeswitch and chat binary
Now you need to install pppd, usbmodeswitch and the chat binary the kernel is missing. You can google them or use my 3gdongle.zip file with my configs.
Run sshdroid so you can ssh to your android device (or use adb shell etc.).
Connect to your andrid device with putty.
Then run
Code:
sysrw
so you can write to your system folder.
Copy the contents of the zip file in the root folder using WinSCP.
Add the execute permission on
/system/xbin/chat
/system/xbin/usb_modeswitch
/system/bin/pppd
/system/etc/ppp/ip-up
/system/etc/ppp/ip-down
(using WinSCP or with chattr via ssh)
5) Plug the dongle to your windows machine & using Vodafone windows application disable pin authentication. (You can let it enabled but you have to modify the gprs-connect-chat i guess).
6) Disable the CD-ROM mode (I think it's not required because we are using usb_modeswitch, but i did it a long time ago and I'm too lazy to enable it back).
Under Control Panel->Phone and Modem look in the Modems tab. There should be the COM port written in the "Attached To" column.
Using putty & connection type serial connect to your modem and disable the CD-ROM mode using the command
Code:
AT^SETPORT="A1;1,2,3"
You can also check if your modem is responding with the AT command (it should write back OK).
Using te ATI command you should get the modem information back.
ex:
Code:
Manufacturer: Vodafone (Huawei)
Model: K4605
Revision: 11.113.21.00.11
IMEI: 353148040378952
+GCAP: +CGSM,+DS,+ES
OK
7) Plug the modem into your android device. You can check if the necessary moodules are loaded with lsmod:
Code:
sh-4.1# lsmod
option 13380 0 - Live 0xbf016000
usb_wwan 8789 1 option, Live 0xbf00d000
8) Check the dmesg or use lsusb to get your devices vendor and product id
dmesg>
Code:
[ 1903.631599] usb 2-1: new high speed USB device number 3 using tegra-ehci
[ 1903.689362] usb 2-1: New USB device found, idVendor=12d1, idProduct=14c1
[ 1903.689606] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 1903.689739] usb 2-1: Product: Vodafone Mobile Broadband (Huawei)
[ 1903.689970] usb 2-1: Manufacturer: Vodafone Group (Huawei)
[ 1903.695541] scsi1 : usb-storage 2-1:1.0
[ 1904.701649] scsi 1:0:0:0: CD-ROM Vodafone CD ROM (Huawei) 2.31 PQ: 0 ANSI: 2
lsusb>
Code:
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 003: ID 12d1:14c1
9) Switch usb mode using usb_modeswitch and the config file for your device. In my case it's 12d1:14c1.
Code:
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
If the switch was succsessful you should see the correct productid now (in my case 14c6):
Code:
sh-4.1# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 005: ID 12d1:14c6
10) optional - K4605 or other unrecognized devices
After the modeswitch you should see your device under /dev/ttyUSB*. But with the K4605 we don't because option.ko doesn't know our device. So we need to call
Code:
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
and our device appears.
11) check if modem is responding:
Code:
cat /dev/ttyUSB0 & echo AT > /dev/ttyUSB0
You should get an OK.
12) Set the config files. If you installed my 3gdongle.zip file you will find my config files under /system/etc/ppp .
You have to edit the gprs-connect-chat file and the peers/gprs file.
I will not go into detail about this config files. There is a lot of information about it on xda forums and google should be your best friend too .
bonus) I use this scripts to enable and disable internet via my 3G dongle using the scriptmanager app (https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en)
01_init3g.sh - Run it after plugging the 3g dongle to your android device (k4605 specific)
Code:
# My modem Vodafone K4605 is unknown to option.ko so we manually add it
# you can delete this line if your modem is recognized by option.ko
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
# switch modes with usb_modeswitch
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
02_connect via 3g.sh - Connect to the internet (you have to wait 10-20sec after using init because the modem has to initialize first)
Code:
#!/system/bin/sh
#save old route & primary dns
OLDROUTE=`/system/xbin/netstat -r | /system/xbin/grep default | /system/xbin/awk '{print $2}' | /system/xbin/head -n1`
OLDDNS=`/system/bin/getprop net.dns1`
/system/xbin/echo $OLDROUTE > /data/ppp/ppp0.route;
/system/xbin/echo $OLDDNS >> /data/ppp/ppp0.route;
# just some logging for debugging. Can be removed :)
/system/bin/log -pw -t zeroxPPPD "OldRoute: $OLDROUTE"
/system/bin/log -pw -t zeroxPPPD "OldDNS: $OLDDNS"
#connect to the internet
pppd call gprs
03_restore wlan.sh - Disconnect the 3g dongle & restore WLAN
Code:
#!/system/bin/sh
# restore the old route & primary dns (you can extend the script to add the secondary dns..
OLDROUTE=`cat /data/ppp/ppp0.route | head -n1`
OLDDNS=`cat /data/ppp/ppp0.route | tail -n1`
/system/bin/setprop "net.dns1" "$OLDDNS"
/system/xbin/route add default gw $OLDROUTE dev wlan0
# delete the settings file
/system/xbin/rm /data/ppp/ppp*.route
Click to expand...
Click to collapse
here is the link for it (http://forum.xda-developers.com/showthread.php?t=1494891&page=4)
It's also in the latest source (http://git.kernel.org/?p=linux/kern...b;hb=9334c4c16e6fa80dc55865897337b49c1753f33b)
I also found this (https://github.com/DerArtem/huaweigeneric-ril).
PLEASE DEVELOPERS TAKE A LOOK INTO IT, if possible fro the source please build a kernel patch or script
thanks to zerox981
I have KFHD 8.9 v8.3. I am having problems getting fastboot working. I have read threads that there are specific "fastboot drivers" and then I have seen other threads where fastboot drivers are a part of the Kindle Fire drivers installed by ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe. No matter what I do I am unable to get "fastboot -i 0x1949 getvar product" to work. At one point I had it rooted with validation from suchecker, still couldnt get fastboot to work, but factory restored to 8.3 to validate steps and instructions and it is a nogo at the moment.
Any help would be appreciated.
So, is your device rooted or not? Your post in another forum seems to contradict what you are saying here.
Liek Soupmagnet said are you positive that your device has root access? If so, I would try wipe the drivers and start from scratch.
As far as I know and it worked for me, fastboot drivers are loaded when you install Android SDK on your PC. See picture bellow.
However in case you need the fastboot drivers you can download here: https://docs.google.com/folder/d/0B4lZEJI5lYeMdzJobG5jSk9QSEk/edit?pli=1 as referenced here: http://forum.xda-developers.com/showpost.php?p=34589184&postcount=6
These ADB drivers worked for me: http://forum.xda-developers.com/showthread.php?t=1890413
For Kindle drivers and Amazon drivers for Windows 8 (if the case),please take a look here: http://forum.xda-developers.com/showthread.php?t=2185402 however I did need not need them.
Is your Kindle showing up when you type the command ADB Devices cmd/terminal window?
I hope it helps.
soupmaget,
I responded to your PM and I said I would try the SoupKit tonight. Calling me out in forums doesn't help you or me and dont know why you keep doing that. I am trying many things but it boils down to the same specific commands. I have even tried the below downloads manually grabbing the commands and typing them in manually.
Last night I refreshed my env following the amazon tutorials step by step. I finally got root by running Root_with_Restore_by_Bin4ry_v25 twice and then Kindle_Fire_Utility_v0.9.6 rooting via recommended option twice. ADB does work, I can "adb reboot", "adb shell" push files, mv files, etc. SUCheck validates I have root.
When I continue to hashchodes TWRP and 2nd bootloader tutorial it states that "you should have working fastboot drivers" which to me means that there is a separate download/driver to install for it to work. I know fastboot.exe is included in the ADK and tried using the other tools for getting fastboot working but its not working.
I do run these with administrative rights....
D:\android\sdk\platform-tools>adb devices
List of devices attached
B0CA060424841KF0 device
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
rwideman said:
So technically this thread is specific to rooting and can be closed as I am passed rooting now and on to fastboot issue...
Click to expand...
Click to collapse
You are blowing my mind right now with your refusal to be helped. Why are you so hell bent on making this difficult for yourself? You have a $300 device that doesn't work and you're being resistant to someone who can most likely help you get it working again. Why? I don't get it...
From what I gather in your various posts, your device is rooted but you cannot access fastboot via the traditional method of entering "fastboot -i 0x1949 getvar product" in the terminal and powering the device up.
Assuming you have a usb/adb/fastboot connection problem with your Mac, you can use SoupKit, but only in certain VMs. But if you have had a previous connection with either fastboot or adb, that probably isn't the case.
Theres a good chance that you can install the Android Terminal Emulator, enter 'su' to gain root privileges and enter "reboot bootloader". That should boot your device into fastboot so you can enter fastboot commands. But, as I told you before, if there is a usb connection problem, and you cannot send fastboot commands to your device, you will be stuck in fastboot. If you have another non-Mac computer available to you, it would be best to boot it into Linux and install soupkit to make sure that doesn't happen. BTW, that is nearly verbatim to what I told you via the first PM.
Are you looking at the timestamps of my postings? Things change over time....
Did you read my PM response? I will try SoupKit tonight, I mentioned this after you told me to try it.
Thank you for your efforts.
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
FYI #3, In the professional world it is better to stick to non-psychologist bashing, what someone is and is not doing/thinking/acting, and sticking to the issue at hand. I have been in the IT world for 15 years and troubleshooting is my day job (windows, vmware, SAP, *nix, .net, java, j2ee, storage, UCS, routers, switches, nexus, cloud automation, orchestration, etc). Professionalism frowns upon psychologist speak.
rwideman said:
My wife took the MBP for the night so I tried 2 old laptops with win7 x64 on them. copied over files and installed the kindle drivers as normal, got KFHD working with adb and then fastboot sits at the prompt waiting just like on my other env, even installed latest jdk 6 and nogo. I am SOL for the day so I will have a drink or 2 tonight and take one of those old laptops to work and install ubuntu 12.10 tomorrow and try again.
Thanks for the help.
FYI, I tried installing the terminal emu and runing "reboot bootloader" with a few fastboot command tries and nogo. I was able to hold the power button and get it to shut off once I got to fastboot mode.
FYI #2, under my previous env with vmware workstation 9 running unbuntu 12.04 in a vm I could not get fastboot to recognize the device but adb was recognizing it perfectly. Trying native ubuntu tomorrow.
Click to expand...
Click to collapse
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
I think I have the same problem. twrp installed on my device, but no OS running, and it can't be recognized on my computer, said driver incorrect, tried so many times, but can't get adb and fastboot work without driver supported. Don't know how to do.
soupmagnet said:
You're most likely looking at a driver issue. You might still be able to get them working in Windows. What did you use to install your drivers? Did you use an install package or did you do it manually?
Click to expand...
Click to collapse
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
rwideman said:
I used these instructions:
https://developer.amazon.com/sdk/fire/connect-adb.html
using ...\sdk\extras\amazon\kindle_fire_usb_driver\KindleDrivers.exe
I tried a few different driver sets/packages by different places on the XDA threads but they all ended up being the same driver or detected the KDFHD89 exactly the same.
Click to expand...
Click to collapse
When it's in fastboot, do you see anything show up in the device manager?
soupmagnet said:
When it's in fastboot, do you see anything show up in the device manager?
Click to expand...
Click to collapse
Unfortunately no. I haven't had time doing linux with soupkit yet.
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
jonahy said:
I had exactly the.problem still can't get fastboot too see my kindle8.9.
used amrzon driver from sdk.
Adb devices is fine i see the kfhd serial number. .but once use fastboot cmd waiting for device then.never boot in fastboot mode. just boot back to lock screen .This is rooted 8.9 with 8.3 os.
maybe i should do a factory reset.
in order to install a 2nd bootloader and tw-recovery u have to have a rooted kindle hd8.9?
Click to expand...
Click to collapse
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
soupkit Folder Empty out
soupmagnet said:
Yes, you have to be rooted to install the 2nd bootloader and TWRP. I put together the SoupKit so people with driver issues such as yourself can use Linux without much trouble because it is 100 times more reliable than Windows. You should look into it. You can use RootPlus to get root but don't use it to install the 2nd bootloader on 8.3.0 or you will be bricked, likely permanently. But you will be able to use fastboot without any problem to do it manually.
Click to expand...
Click to collapse
Hi Thank you for the direction.
I made a Ubuntu 12.10 usbkey booted
then copied ur soupkit folder on desktop Run install.sh ( have to go into permisions check the allow excute)
Run in terminal then terminal show 2 " closed then all the file in soupkit is gone..ha.
didnt see option 1 and 2.
Then i try in Ubuntu termal do abd and fastboot but same as in window 7 KFHD89 just boot into lock screen.
(adb devices it can see devices though
Setting up android-tools-adb (4.1.1+git20120801-1) ...
[email protected]:~$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9100425160LG8 device)
fastboot not
([email protected]:~$ sudo apt-get install android-tools-fastboot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
android-tools-fastboot
0 upgraded, 1 newly installed, 0 to remove and 337 not upgraded.
Need to get 48.6 kB of archives.
After this operation, 129 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ quantal/universe android-tools-fastboot i386 4.1.1+git20120801-1 [48.6 kB]
Fetched 48.6 kB in 0s (105 kB/s)
Selecting previously unselected package android-tools-fastboot.
(Reading database ... 161214 files and directories currently installed.)
Unpacking android-tools-fastboot (from .../android-tools-fastboot_4.1.1+git20120801-1_i386.deb) ...
Setting up android-tools-fastboot (4.1.1+git20120801-1) ...
[email protected]:~$ fastboot -i 0x1949 getvar product
< waiting for device >
I was thinking maybe its the Root_with_Restore_by_Bin4ry_v26 mess up somthing? I know my KFHD is rooted it by, but if i load any app need root never show the window ask me if i allow this app in superuser massege.
anyway any tips abot that soupkit Folder Empty out issue?
(just got this tablet last friday, good device so far but put a recovery on it seems a bit harder then my other tablets...But hey I guess thats part of fun too right? )
Thank you in advance.
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Installed 2ND-BOOTLOADER
soupmagnet said:
I think you're confused in how fastboot works. The device must be in fastboot (display says fastboot) in order for fastboot commands to work. There was no need to install android tools. There's a possibility that in doing so you may have made things worse, but we'll see...
Since you have access to adb, try the following command to boot into fastboot:
Code:
adb shell su -c "reboot bootloader"
This, of course, assumes your device is already rooted.
[Edit:] Also, to access Root Plus after installation, enter "rootplus" (without quotes) in the terminal.
Click to expand...
Click to collapse
Great! Got Installed the 2nd bootloader and recovery .
adb shell su -c "reboot bootloader" boot device to fastboot mode.
thanks a lot! SoupMagnet.
Share steps:
D:\sdk\sdk\platform-tools>adb devices
List of devices attached
B0C9100425160LG8 device
D:\sdk\sdk\platform-tools>adb shell su -c "reboot bootloader"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 getvar product
product: Jem-PVT-Prod-04
finished. total time: 0.006s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/boot of=/sdcard/stock-boot.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.939 secs (8933554 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.937 secs (8952623 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/dev/block/platform/omap/omap_h
smmc.1/by-name/system of=/sdcard/stock-system.img"
1814528+0 records in
1814528+0 records out
929038336 bytes transferred in 116.782 secs (7955321 bytes/sec)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-boot.img
2794 KB/s (8388608 bytes in 2.931s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
3008 KB/s (8388608 bytes in 2.723s)
D:\sdk\sdk\platform-tools>adb pull /sdcard/stock-system.img
3004 KB/s (929038336 bytes in 301.978s)
D:\sdk\sdk\platform-tools>adb push stack /data/local/tmp/
571 KB/s (4096 bytes in 0.007s)
D:\sdk\sdk\platform-tools>adb shell su -c "dd if=/data/local/tmp/stack of=/dev/b
lock/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,rw ext4 /system"
D:\sdk\sdk\platform-tools>adb shell su -c "mv /system/etc/install-recovery.sh /s
ystem/etc/install-recovery.sh.bak"
D:\sdk\sdk\platform-tools>adb shell su -c "mount -o remount,ro ext4 /system"
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-
8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.026s]
writing 'bootloader'...
OKAY [ 0.045s]
finished. total time: 0.075s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.3.0
.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.455s]
writing 'boot'...
OKAY [ 0.567s]
finished. total time: 1.030s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 flash recovery kfhd8-twrp-2.4.4.0-r
ecovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.454s]
writing 'recovery'...
OKAY [ 0.567s]
finished. total time: 1.029s
D:\sdk\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.004s
D:\sdk\sdk\platform-tools>
FIXED
soupmagnet,
Finally had time to install ubuntu 12.10 on my laptop. I used soupkit for KFHD89 and root-plus from the same posting you had. This worked like a charm. rootplus' version of the play store actually worked compared to other versions I had installed, same for youtube and a few other google apps.
I will toy with TWRP tomorrow. Just glad I got normal google apps installed now.
Tried a few methods for getting root, none of which worked. I'm running a d851 with d85120g software. Ubuntu as my desktop. Here's a step by step pulled from various sources.
1. Put your phone in developer mode. Go to settings-->about phone. Click on build 8ish times until you see "you're a developer"
2. Go to settings-->developer options-->enable USB debugging
Now we need the desktop to recognize the phone
3. In your favorite text editor, you'll need to create a text file named /etc/udev/rules.d/51-android.rules
4. Copy this line into the file and save it:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
(Source here)
5. In a terminal:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
6.
Code:
sudo service udev restart && sudo killall -9 adb
6a. Get this file and
Code:
sudo chmod a+r ./qcdlcomm.py
from that directory. (Source)
Next steps are modified from here.
7. Download and extract the zip file: http://bit.ly/1Ln9FKB .
7a. Move qcdlcomm.py to wherever you extracted the above file.
8. Connect your phone. At some point you can choose your USB connection type. Reports state it only works with PTP mode (v. MTP), but I didn't try MTP.
9. Terminal:
Code:
adb devices
You should see your phone listed. Then, in the same directory as the files from step 7:
10.
Code:
adb push ./busybox /data/local/tmp && adb push ./UPDATE-SuperSU-v2.46.zip /data/local/tmp
Now you want to get in download mode.
11. Unplug and turn off your phone, then hold volume up as you plug the cable back in. You should see "download" or something on the screen.
Next steps taken from here.
12.
Code:
ls /dev/ttyUSB*
Make note of the devices. You'll try the highest device number first in a few steps.
13.
Code:
sudo rmmod cdc_acm && sudo rmmod usbserial
You'll get an error if there's anything else using usbserial. If so, sudo rmmod that module, then rerun
Code:
sudo rmmod usbserial
14.
Code:
sudo modprobe usbserial vendor=0x1004 product=0x633e
15.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*< ./root
Replace the device with the output from step 12. Something should happen here. (BTW, at some point the phone screen says "flashing firmware" or something. There's a progress bar. It never moves past 0%"
16. Type "LEAVE" at the hash prompt that's left. At this point, your phone may not reboot. If not, type "exit" (or ctrl+c) and disconnect your phone. Then reconnect the phone.
17.
Code:
ls /dev/ttyUSB*
again. You may have lost a usb device. If so, repeat:
18.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*
with the next highest device from above.
19. Type "LEAVE" again. Device should reboot. You should have root.
Some of this from memory, so if anyone has any suggestions, LMK. Hope this helps someone.
Good
Sent from my SM-G361H using Xposed Modules
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
slow64 said:
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
Click to expand...
Click to collapse
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
nola mike said:
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
Click to expand...
Click to collapse
I notice my product ID differs from yours. Is this unimportant? I have been really wanting to get root on this for a while now, and this is the most promising looking aggregation of all available information I've found so far.
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
nola mike said:
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
Click to expand...
Click to collapse
I was thinking I'd just substitute my ProdID in the necessary locations.
dmesg:
Code:
[11036.082260] usb 3-2: new high-speed USB device number 10 using ehci-pci
lsusb:
Code:
[~]$ lsusb | grep LG
Bus 003 Device 010: ID 1004:631d LG Electronics, Inc. Optimus Android Phone (Camera/PTP Mode)
Sounds good, keep us updated.
Well, just got my third d851, running v30e firmware. Now doesn't work, getting stuck at step 15. When I plug in in download mode, the phone switches to the "firmware update" screen before I do anything. This is the dmesg output.
Code:
[ 6277.744082] usb 1-1: new high-speed USB device number 28 using ehci-pci
[ 6277.893938] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6277.893944] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6277.893948] usb 1-1: Product: LGE Android Phone
[ 6277.893950] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6277.893953] usb 1-1: SerialNumber: LGD8511199581b
[ 6277.894874] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6277.894890] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6277.895019] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6277.900634] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6277.900638] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6277.900641] usbserial_generic 1-1:1.2: generic converter detected
[ 6277.900827] usb 1-1: generic converter now attached to ttyUSB0
[ 6534.787683] usb 1-1: USB disconnect, device number 28
[ 6534.791136] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 6534.791175] usbserial_generic 1-1:1.2: device disconnected
[ 6550.456114] usb 1-1: new high-speed USB device number 29 using ehci-pci
[ 6550.605565] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6550.605571] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6550.605574] usb 1-1: Product: LGE Android Phone
[ 6550.605578] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6550.605581] usb 1-1: SerialNumber: LGD8511199581b
[ 6550.606530] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6550.606559] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6550.606720] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6550.612943] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6550.612948] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6550.612951] usbserial_generic 1-1:1.2: generic converter detected
[ 6550.613624] usb 1-1: generic converter now attached to ttyUSB0
Nexus has no OS installed. I can't load ROM in TWRP because tablet doesn't show up on PC. I tried Windows 10 and Ubuntu 18.04, different usb cables. Device is physically detected (fastboot works) but no "disk" (filesystem).
mt12345 said:
......no "disk" (filesystem).
Click to expand...
Click to collapse
Perhaps there is no filesystem indeed? Boot TWRP 3310, connect and check from your PC if you get similar output:
Code:
adb shell mount
/dev/block/mmcblk0p30 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
adb shell df -h
/dev/block/mmcblk0p30 26.4G 6.0G 20.4G 23% /sdcard
If not, then you need to format data and then MTP will show it.
If yes, then check with http://www.uwe-sieber.de/usbtreeview_e.html for the following:
Code:
Child Device 1 : Nexus 7 2013
DevicePath : \\?\usb#vid_18d1&pid_4ee2&mi_00#7&27f930b&0&0000#{14480d3f-7a47-4a75-aaef-b14f56397153}
KernelName : \Device\00000102
Device ID : USB\VID_18D1&PID_4EE2&MI_00\7&27F930B&0&0000
Class : WPD
Child Device 2 : Android Composite ADB Interface
DevicePath : \\?\usb#vid_18d1&pid_4ee2&mi_01#7&27f930b&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}
KernelName : \Device\00000103
Device ID : USB\VID_18D1&PID_4EE2&MI_01\7&27F930B&0&0001
Class : AndroidUsbDeviceClass