Hello and thanks in advance.
A while back I had the wild idea of rooting my Kindle Fire and installing an Android OS. Well I did just that...
I used Kindle Fire Utility to install the drivers on my Windows 7 x64 computer and was able to recognize my device. I was able to root, install FireFireFire (v1.4a), and TWRP (I believe it was 2.2.x.x).
Then I was able to transfer ROMs over usb and boot those using TWRP with no problems. The ROM I used was Hashcode's 4.2 JellyBean, if I remember correctly. Everything worked exactly as planned.
Well, after a while I had another bright idea that I would see if any updates for my software were out there. I do not remember exactly what steps I took from there to do that, but lets just say, now I'm stuck.
Currently I have my Kindle Fire with FireFireFire v1.4a and TWRP 2.5.0.0. My device turns on normally and attempts to boot in normal mode, but gets stuck saying "booting..." at the bottom, I assume because there are no ROMs on the device. I figure I should be able to just transfer over a ROM and boot in normal like I did before, but I am unable to get my computer to "completely" recognize my device.
I say "completely" because when I plug in my usb to my device with the device on and in recovery (I tried with both mount on and off in TWRP) it will not detect, but with the device on the FFF main screen (blue Kindle Fire screen where you can select your boot option at the bottom by pressing the power button) it is detected by my computer and shows this in Device Manager:
*Android Phone
- Android ADB Interface
As soon as the device goes to "normal" or "recovery", the device is immediately removed from the Device Manager list. I have reinstalled drivers several times to no avail.
I figured if I was able to get the device connecting again enough to transfer ROMs I thought i would try and go back stock (without root/FFF/TWRP) and attempt to start over, unless of course anyone would have any better suggestions. I would appreciate anything, thanks again.
While booted into TWRP, make sure the hardware IDs listed reflect those that are in your android_winusb.inf
Can you please elaborate on where the listed ID's are located from within TWRP?
I partly understand the android_winusb.inf and it is as follows:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
QtipForPrez said:
Can you please elaborate on where the listed ID's are located from within TWRP?
I partly understand the android_winusb.inf and it is as follows:
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Click to expand...
Click to collapse
While TWRP is booted, go to the device manager and find your device. Go to its properties (right-click) and select the "Details" tab. The rest should be self explanatory.
The device is not visible with TWRP booted. I was able to get the device to become visible while holding down the power button on the main boot screen while cycling through the boot options.
Anyway I got the ID's and they are:
USB_Install, USB\VID_18D1&PID_0100&REV_0100
USB_Install, USB\VID_18D1&PID_0100
I don't know where to put them exactly in the android_winusb.inf. I read through your thread http://forum.xda-developers.com/showthread.php?t=2179748 again, but i am still unclear on exactly what I should do.
I've tried adding the ID's into the file, unistalling and installing the drivers many times, but I seem to not be doing it correctly.
QtipForPrez said:
The device is not visible with TWRP booted. I was able to get the device to become visible while holding down the power button on the main boot screen while cycling through the boot options.
Anyway I got the ID's and they are:
USB_Install, USB\VID_18D1&PID_0100&REV_0100
USB_Install, USB\VID_18D1&PID_0100
I don't know where to put them exactly in the android_winusb.inf. I read through your thread http://forum.xda-developers.com/showthread.php?t=2179748 again, but i am still unclear on exactly what I should do.
I've tried adding the ID's into the file, unistalling and installing the drivers many times, but I seem to not be doing it correctly.
Click to expand...
Click to collapse
Those are the hardware IDs for FireFireFire. You need to be booted into TWRP to get the right ones.
Try unplugging the device from the USB and plugging it back in to see if that helps.
Well just by you telling me to unplug and plug back in the device was able to mount in TWRP and accomplish what i was trying to do. I was able to flash 4.2.2 and it booted up. There was no need for the ID's in my case. The device and drivers were installed and working correctly the whole time I guess. I'm just too much of a noob to get it to mount. Thank you so very much.
Related
ok, I lost root and then fastboot wouldnt recognize my device because in the sdk there wasnt the galaxy nexus figured into the setup.inf file in the drivers folder. I typed this in between the ns4g and the nexus 7
;Google Galaxy Nexus
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E30
%SingleBootLoaderInterface% = USB_Install, USB
\VID_18D1&PID_4E30&MI_01
%SingleBootLoaderInterface% = USB_Install, USB
\VID_18D1&PID_D001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%CompositeAdbInterface% = USB_Install, USB
\VID_04E8&PID_6860&REV_0216&MI_01
computer asked to restart...yes. upon reboot I went to device manager, uninstalled android 1.0 and did a hardware scan. BAM!! installed! went to fastboot, reflashed su and recovery...good to go!
make sure you look up your hardware id in device manager BEFORE you edit the file to make sure you type the correct numbers replacing the ones above if you have to!
Doesn't belong in Development. There is no development here this is just an FYI or a general "guide"
Sent From My Toro+ via RED Tapatalk
oh, I thought I was in general...
JediNinjafication said:
oh, I thought I was in general...
Click to expand...
Click to collapse
LOL its alright i reported it to be moved you should be fine.
I can't find anything when not using phone. I stare at xda screen on computer and am all..duh..where'd it go.. so excited to have root again!
So I have my Kindle Fire rooted, with TWRP 2.2.2.1, FFF 1.4A and the latest version of CM 10 w/ SGT7 (9/05). Using KFU 0.9.6 when I attach my Kindle to my computer the ADB status is offline, while the drivers on my computer recognize it as an "Amazon Kindle Fire" and if I look in the properties I see "Amazon File-CD Gadget USB Device", "USB Mass Storage Device", and the drive it's recognized as "M:\" for me. No matter how often I attempt to reboot my computer, the Fire, or uninstall the drivers and install the drivers manually (either through the install drivers.bat or adding
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
and
0x1949
to android_winusb.inf and adb_usb.ini respectively.
However when I reboot my Fire into recovery, it's recognized as Online. Any help with getting it recognized when regularly booted up?
Sounds like a ROM issue. The new builds of CM10 have a PID of 0004 for some reason, rather than 0006.
Why it wouldn't affect recovery, though, I couldn't tell you.
Damn, alright. Thanks, at least I can always transfer a new ROM over and flash it when I need to. Hopefully they'll get it fixed soon.
Just use recovery to send adb commands.
soupmagnet said:
Just use recovery to send adb commands.
Click to expand...
Click to collapse
Right, I'm using it. I installed JandyCane and it's working just fine now. However I find I'm missing much of what I liked in the other ROM. Ah well, time to explore ROMs! Thanks for your help!
I added these 2 lines to the already long list of ids saved the win_usb file then reinstalled the driver now adb works
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
As title suggests, prior to rooting the Kindle and flashing JB 4.4.2 I was able to access the Kindle via the ADB. Now when I plug in my kindle it detects the Kindle as a Portable Media Player and Device Manager shows Amazon Kindle Fire under Other Devices with a yellow exclamation as well as under Portal Devices with no excalamation (I believe this is the Portable media Player).
I have tried to follow the same steps prior to rooting to get it connected to the ADB but when I attempt to install the drivers from the Android SDK after updating
android_winusb.inf
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
and adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
When attempting to install the driver via 'Update Driver' in device manager. I am getting a "Windows could not find driver software for you device"
When booting into TWRP the driver that loads is connected to the ADB.
Any help would be much appreciated.
Thanks,
Jmack
http://forum.xda-developers.com/showthread.php?t=2179748
its pretty early in the morning and all i want to do is sleep, so i got to apologize for possible typos and lazy writing, and whats even worse is that im a complete noob on the android platform, so please bear with me. (hi, im the new guy btw)
anyways, i fu'd my "su" up by resetting after rooting and now i cant sideload the ota in recovery mode to fix it.
what i do:
get ouya into recovery (adb reboot recovery) and select "something something from adb"
(sorry, its really, REALLY early and i ran out of coffee)
the screen then gives me the message:
Now send the package you want to apply to the device with "adb sideload <filename>"...
and thats the point where im stuck, after typing "adb sideload RC-OUYA-1.0.346-r1_ota.zip" it just tells me: error: device not found.
i also tried "adb install RC-OUYA-1.0.346-r1_ota.zip" but that just gave me the same error with the message "- waiting for device -" below.
also adb doesnt recognize the ouya in recovery mode (adb devices gives me an empty list) but DOES recognize the console out of recovery.
i can also still boot it up and play with the settings, the only issue is that sometimes wifi just randomly refuses to work (and i dont have any games installed so i cant test that)
its not really important but,
what i did:
i sucessfully finished the [how to] adb sideloading superuser-access tutorial by ty collum (not the wireless part)
and then i tried booting CWM (the one click batch thing) which gave me the "OUYA!" screen (just like in recovery mode) so i made a factory reset, after which i couldnt access su anymore. (which again is why i want to sideload the ota, to start over.)
thats all i can think of for now, if someone needs more infos just ask, apologies again for being a little inconvenient, but im really tired.
sincerely smokey.
EDIT:
nobody has even the slightest clue what could cause this? drivers, missing librarys, a bug in the sdk, nothing?
just reinstalled windows 7 ultimate x64 (had to do it anyway) and going to retry the procedure now, reporting back once im done.
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
EDIT
at this point you can simply continue the driver installation tutorial
Click to expand...
Click to collapse
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.
THANKS!!!
iAmSmokey said:
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.
Click to expand...
Click to collapse
you are a legend, i was having the same issue with x64, i just did a system restore to back up right before I started all this jazz. through hours of researching, regarding how to reset my drivers from the MTP USB device, to click ALT+Sysrq+i for a solid half hour. this post with the the slight alter in code was the final touch to being able to sideload. my OUYA is now back up and running! THANKS!
You can also append the line, you don't have to replace it.
Like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001
[/B]
Btw thanks mate!
I was setting up adb to fix the wifi on hashcodes 4.3 rom.....after i got it set up i tried to run it but it wouldnt run adb shell fix-mac.sh without being in the platform-tools folder....(yes my drivers are installed) and it asked for root#otter when i entered the command....supersu is set to allow commands from the computer and i dont know what to do...i dont want to switch roms...and yes i just reinstalled my drivers (they werent working before).Can anybody tell me whatt to enter in after that or a way around it?
Go to developer options and enable Android Debugging. On your computer does it come up Android Composite ADB Interface? If not it is likely that modifications will have to be done to the win_usb.ini file and the driver reinstalled. Also when it is fixed you should see a prompt on your kindle screen to allow ADB from your computer specifically. Here is where you can find answers to resolve most issues with ADB http://forum.xda-developers.com/showthread.php?t=2179748 .
Thepooch said:
Go to developer options and enable Android Debugging. On your computer does it come up Android Composite ADB Interface? If not it is likely that modifications will have to be done to the win_usb.ini file and the driver reinstalled. Also when it is fixed you should see a prompt on your kindle screen to allow ADB from your computer specifically. Here is where you can find answers to resolve most issues with ADB http://forum.xda-developers.com/showthread.php?t=2179748 .
Click to expand...
Click to collapse
His thread isn't relevant as I installed the drivers (it said the drivers were adb composite interface) via windows update and I used android SDK for other things..my kindle does show up in adb devices and I do have USB debugging right now...I don't have access to my backup laptop right now (my backup laptop has everything on it and runs windows xp) and my main laptop is how can I word it.....dead so I can't check what it shows up as
Jacobloveskindles said:
His thread isn't relevant as I installed the drivers (it said the drivers were adb composite interface) via windows update and I used android SDK for other things..my kindle does show up in adb devices and I do have USB debugging right now...I don't have access to my backup laptop right now (my backup laptop has everything on it and runs windows xp) and my main laptop is how can I word it.....dead so I can't check what it shows up as
Click to expand...
Click to collapse
So what are you doing? You have me confused and I can resolve about 90% of driver related issues. I could always look then it doesn`t have to be guessing game .
Thepooch said:
So what are you doing? You have me confused and I can resolve about 90% of driver related issues. I could always look then it doesn`t have to be guessing game .
Click to expand...
Click to collapse
I was just saying I'll check if it says adb composite interface when I plug it in into my backup laptop in the morning
Jacobloveskindles said:
I was just saying I'll check if it says adb composite interface when I plug it in into my backup laptop in the morning
Click to expand...
Click to collapse
Ahh got ya.
Thepooch said:
Ahh got ya.
Click to expand...
Click to collapse
Well when I plug it in it shows up as this: http://m.imgur.com/7d3tIdJ but in device manager it shows this: http://m.imgur.com/GlQZLnS
I'm running windows xp pro 32-bit and my kindle is (you know) on hashcodes stock 4.3 ROM and I'm trying to issue the WiFi fix command
I have superSU installed from recovery and usb debugging enabled...although i don't think it matters it has cotr recovery installed
Jacobloveskindles said:
Well when I plug it in it shows up as this: http://m.imgur.com/7d3tIdJ but in device manager it shows this: http://m.imgur.com/GlQZLnS
I'm running windows xp pro 32-bit and my kindle is (you know) on hashcodes stock 4.3 ROM and I'm trying to issue the WiFi fix command
I have superSU installed from recovery and usb debugging enabled...although i don't think it matters it has cotr recovery installed
Click to expand...
Click to collapse
No it doesn`t matter that you have COTR installed I see that is shows up as android adb interface that is the incorrect facet of a multi-faceted driver. it is appear as if the device is in fastboot. It needs to read Android Composite ADB Interface. Right click where it sad Android ADB Interface select update driver then point it to the driver folder in KFU. XP is inherently difficult to make this happen several things need to be in place to force it to work because it refuses often to install a driver that is Unsigned. Right click on Android ADB interface select properties, then hardware id. Make sure the correct VID and PID matches are in the android_winusb. ini .
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
If not add them, then click save make sure there is a copy of this in your .android folder as well as a copy of the adb_usb. conf with is line inside 0x1949 then reinstall the driver by pointing it to the driver do not allow Microsoft to help you with the update it is pointless simply just direct the installation to the driver folder skip searching update and it may install. Sometimes you must uninstall then reinstall to get it right. As you can see there is alot more to it. If it comes up with this code
Code:
0123456789 offline
instead of
Code:
0123456789 device
when you
Code:
adb devices
your not there yet so keep trying or let a pro in there to help you fix it . Watch for the prompt on your kindle screen to allow adb specifically from your computer. Good luck.
Thepooch said:
No it doesn`t matter that you have COTR installed I see that is shows up as android adb interface that is the incorrect facet of a multi-faceted driver. it is appear as if the device is in fastboot. It needs to read Android Composite ADB Interface. Right click where it sad Android ADB Interface select update driver then point it to the driver folder in KFU. XP is inherently difficult to make this happen several things need to be in place to force it to work because it refuses often to install a driver that is Unsigned. Right click on Android ADB interface select properties, then hardware id. Make sure the correct VID and PID matches are in the android_winusb. ini .
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
If not add them, then click save make sure there is a copy of this in your .android folder as well as a copy of the adb_usb. conf with is line inside 0x1949 then reinstall the driver by pointing it to the driver do not allow Microsoft to help you with the update it is pointless simply just direct the installation to the driver folder skip searching update and it may install. Sometimes you must uninstall then reinstall to get it right. As you can see there is alot more to it.
Click to expand...
Click to collapse
I used the found new hardware wizard to reinstall the drivers from kfu because those drivers didn't install for me this was before...and yes the kfu drivers said they were unsigned.I also have the android SDK installed if that helps...you are confusing me....before I had the drivers installed it showed up as mtp...I'm not in fastboot I'm in the ROM when I plug it in.....please help me..not..be..confused
Jacobloveskindles said:
I used the found new hardware wizard to reinstall the drivers from kfu because those drivers didn't install for me this was before...and yes the kfu drivers said they were unsigned.I also have the android SDK installed if that helps...you are confusing me....before I had the drivers installed it showed up as mtp...I'm not in fastboot I'm in the ROM when I plug it in.....please help me..not..be..confused
Click to expand...
Click to collapse
I can fix your problem not your confusion best you let me show you. PM sent unread your private messages.
Thepooch said:
I can fix your problem not your confusion best you let me show you.
Click to expand...
Click to collapse
K.show me :cyclops::good: (I'm bored right now...sorry)
Jacobloveskindles said:
K.show me :cyclops::good: (I'm bored right now...sorry)
Click to expand...
Click to collapse
Unread your private messages.