Database Users

[Q] G2 soft brick!! nooooo

Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana

I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it

djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.

Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app

So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind

What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app

access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...

well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.

[HELP][SM-N900W8] Can't connect to ADB

May I just ask what could my problem be?
I am encountering some issues with ADB.
When the phone is turned on, it says it is offline.
So when I try to connect it through ADB via Recovery, its offline status is gone and ADB cannot detect my device.
I confirmedt his using code: adb devices
Does anyone know how can I connect it to ADB?
What I already did:
- Installed Samsung Drivers Completely
- Enabled USB Debugging on GALAXY Note 3

delete the drivers , install kies for note 3 connect the phone , when it is detected in kies and go to tools and look for reinstall drivers
disconnect and reinstall the drivers from kies then you will be good to go with adb ..
ALTHOUGH i dont understand adb its like they torture us adb works when it wants to specially in windows.

fahadali2315 said:
delete the drivers , install kies for note 3 connect the phone , when it is detected in kies and go to tools and look for reinstall drivers
disconnect and reinstall the drivers from kies then you will be good to go with adb ..
ALTHOUGH i dont understand adb its like they torture us adb works when it wants to specially in windows.
Click to expand...
Click to collapse
hey mate, still no response from adb during recovery mode . .

trevourlance27 said:
hey mate, still no response from adb during recovery mode . .
Click to expand...
Click to collapse
Did you try twrp ,with adb shell ? Might be issue with your recovery.
Sent from my SM-N9005 using Tapatalk

fahadali2315 said:
Did you try twrp ,with adb shell ? Might be issue with your recovery.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
well for now i don't want to have root access nor trigger knox . .
i've tested other note 3's and when i try to connect them to adb with pure stock, they respond
any possible ways without changing recovery to twrp?
(ill plan rooting next time because the device is still new) but yeah thanks for the ideas

[Q] softbrick

hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian

honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
I apologise for potentially getting your hopes up, but I am in the exact same situation. I am very much interested in this thread.

Google 15 second adb drivers xda. You probably need to get adb and fastboot setup for the pc to recognize your device. In order to fix it you'll meet to use fastboot or adb commands
Sent from my Nexus 5 using XDA Free mobile app

honorguard said:
hello,
I have recently been playing with roms and stuff on my n4. (did it on other devices, and never had any problem i couldnt fix)
but right now I kinda screwed up so bad, that I need some help.
I kinda wiped all the data on my phone from the cwm recovery.
and I'm stuck with this situation:
I can boot to bootloader + recovery
I can't boot to any rom (because there is none)
I can't connect to any pc because they won't recognize he's there (forever alone... ) (and yes i've tried all kinds of drivers)
I can't connect with adb because I can't turn on usb debugging mode.
So right now I'm stuck
I've come to the conclusion that i probably need to use fastboot fix this, but like I said before, no computer will recognize my n4. (not showing up in device manager)
also tried about 6 different usb cables - no luck
different computers ( ubuntu - mac - windows) - no luck
So is there any smart guy out there who can help me?
greetings, Julian
Click to expand...
Click to collapse
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk

nicknc said:
You need to delete all your driver files from your pc and start over.
There is no reason for you to not be able to connect via fastboot.
Find a clean win7 machine and start over, installing the fastboot drivers before connecting your phone.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Going to try that now.

Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?

Ihsahn_ said:
Hi both
I've tried installing the drivers but whilst the drivers claim to have installed correctly, my phone is still not recognised by my computer in Device manager. I've tried uninstalling all previous drivers before trying this.
Before we go on - should I be trying to connect my phone to the computer when turned off, in bootloader or in recovery?
Click to expand...
Click to collapse
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
The phone needs to be on, doesn't matter if it's in fastboot or recovery. You're going to need to use fastboot do I'd try it there
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.

Ihsahn_ said:
Hi
Is fastboot essentially bootloader? I've tried in the initial bootloader menu and I've tried having clicked 'start' from the bootloader.
In the bootloader it tells me fastboot is enabled, btw.
Click to expand...
Click to collapse
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?

jd1639 said:
When you're in the bootloader you can run fastboot commands. With your device plugged into the pc, from a command prompt opened on the same folder as fastboot.exe, run the command fastboot devices. Does fastboot return your device info? If so you're good to go running fastboot and flashing a factory image
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Not at the moment. I have had this appear in the past but this is the point I'm trying to get back to. Unfortunately I can't work out how to get it to appear here. My device is in the bootloader.
---------- Post added at 10:23 PM ---------- Previous post was at 10:13 PM ----------
Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.

honorguard said:
But my problem is that fastboot Will never work if my pc wont even know my n4 is there (and also with adb/fastboot devices golving no response Either ) or am I wrong here?
Click to expand...
Click to collapse
Did you do a clean install?
Have you used a different USB cable? Some cables are charging-only, with no indication otherwise. Internally damaged cables can also turn into charging only cables. Ironically, I just replaced one hooked into my daughter's phone today that would only charge intermittently.
There is no reason that wiping partitions in recovery would prevent your phone from being recognized by your PC at all.
Try a clean install of the drivers on a fresh pc with a different cable.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
Ihsahn_ said:
[Brief update - I think. My computer began installing the drivers again, but told me the device suddenly 'disconnected'. I think it's a hardware issue and that the port isn't seated properly. I'm going to replace the USB port and see if that helps.
Click to expand...
Click to collapse
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk

nicknc said:
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
[/COLOR]
This is typical when you connected the phone to the PC before installing the drivers. Windows will sometimes install a generic driver when you hook up the phone, preventing it from detecting the need for adb and fastboot drivers
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.

If it Works with that cable please give me a headsup
Verstuurd vanaf mijn ST25i met Tapatalk

Ihsahn_ said:
I tried uninstalling all drivers, including in USBDeview before running 15 second drivers then trying to connect my phone in fastboot/bootloader mode, with various cables and various ports. Nothing happened!
I've bought another USB cable which should be arriving soon. I've also bought a new charging/USB port to replace that inside the phone.
Click to expand...
Click to collapse
OK.
Sent from my Nexus 4 using Tapatalk

Well, I had similar issues when I bought this phone (coming from a HTC one s) connecting to fastboot.
What I did was:
Delete all drivers related to adb/fastboot/android (use a software to completely clean the files).
Booted my phone into fastboot mode.
Connect to PC and wait for windows to show the new hardware dialog.
Install the correct drivers (which i had downloaded and extracted) using the dialog box.
Profit.
Sent from my Nexus 4 using XDA Free mobile app

The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk

honorguard said:
The onlY difference is that the new hardware dialog doesnt come up
Verstuurd vanaf mijn ST25i met Tapatalk
Click to expand...
Click to collapse
Did you try on a different PC, installing the adb and fastboot drivers before connecting the phone for the first time?
Have you tried a different USB cable?
Sent from my Nexus 4 using Tapatalk

A brief update
I remembered I have a second Android phone knocking around. I plugged this in with one of the cables from earlier - perfect installation with all drivers, etc. This has further convinced me that the hardware of the USB port on the phone is the issue.
Thanks for all help - I'll update again if the hardware change works, or doesn't.

ok, ive installed a new windows and installed all the drivers and then i connected the phone.
Nothing.
i'm getting desperate here..

[HOWTO] How to restore frimware on your device + Amazon Frimware

So if you been messing around with your fire and got to the point that it wont want to get past the loading screen or something or you may have messed up during the root process you can use these steps to restore your Fire
MOD EDIT: THE FIRMWARE LINKED HERE IS NOT SAFE AT THIS TIME, LINK REMOVED AND THREAD CLOSED.
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.

I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:

Darkside1984 said:
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Click to expand...
Click to collapse
Try installing ADB drivers in Device Manager while the Fire is in recovery. If you do it correctly, when you do ADB Devices, it should come up as Sideload.
Sent from my KFFOWI using Tapatalk

Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522053820.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)

sd_shadow said:
recheck device manager, drivers are not correct, Fire should be listed adb composite interface, when in recovery mode
Click to expand...
Click to collapse
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Looking for a miracolous hard factory reset...
EDIT: I see that the battery is low. Does this have something to do with Recovery troubles?

i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Darkside1984 said:
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Click to expand...
Click to collapse
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
Darkside1984 said:
I see that the battery is low. Does this have something to do with Recovery troubles?
Click to expand...
Click to collapse
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.

sd_shadow said:
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
Click to expand...
Click to collapse
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...

Darkside1984 said:
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Click to expand...
Click to collapse
try
Code:
adb version
---------- Post added at 12:38 PM ---------- Previous post was at 12:38 PM ----------
should get
Code:
Android Debug Bridge version 1.0.32
Revision d15680a64678-android

sd_shadow said:
try
Code:
adb version
Click to expand...
Click to collapse
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?

Darkside1984 said:
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Click to expand...
Click to collapse
try link in my Using adb post

Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!

Darkside1984 said:
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Click to expand...
Click to collapse
great
care to post some details about what worked?
Drivers version?
adb method?
Sent from my KFFOWI using Tapatalk

after side loading I needed to switch off the device and restart in order to start the final "Installing the latest software"-sequence

sd_shadow said:
great
care to post some details about what worked?
Drivers version?
adb method?
Click to expand...
Click to collapse
Sure!
I deleted my adb folder and follow the steps in your thread here. So it got the right adb version (1.0.32) and I finally could sideload properly the bin file. I think that the point is that PC just recognizes the Fire (as ADB composite) when you are into 'adb sideload' option, not in the recovery main menu.

5th Gen Kindle Fire - MT65xx Preloader problems
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.

hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238740
[HOWTO] How to restore firmware on your device + Amazon Firmware

hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.

fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
Following your comment, I ran the .BAT while watching Device Mgr. Prior to running it, I had the Android device apparently successfully installed. It had its own folder in Dev Mgr without any [!]. Running the .BAT, that disappeared and Android migrated down to Other Devices. It's now next to the same Unknown Device that I haven't been able to update drivers for.
I tried pointing both to the latest_USB_drivers zip from Shadow's recommended thread. According to Win7, it's 'unable to install' from that unzipped folder or any of the others I've pulled from various threads.

fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk

sd_shadow said:
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
With the Fire disconnected, I booted to recovery (Volume Down + Power) and got a list. Not knowing what to pick, I chose the Bootloader option. It started to boot in FASTBOOT mode. Plugged it in, went to Dev Mgr. Both Android Device and Unknown Device showing in Other Devices. Pointed the Android Device driver to the latest_USB drivers from your other thread. Windows says unable to install your Android. Tried same thing with Unknown Device. Unable to install.

Nexus 6P not showing in Device Manager in Recovery Mode

Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!

asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?

Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.

asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.

Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .