Database Users

Bootloop Help ASAP Please!

I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!

Infuser86 said:
I have a new rooted and unlocked Nexus 7. I flashed a kernel and can't get past the nexus boot screen. My battery is about dead. What do I need to do! I have the tookkit, but I can't get it to do anything! Please help! My battery is almost gone!
Click to expand...
Click to collapse
And I don't have any backup ROMS or kernels to flash...

Infuser86 said:
And I don't have any backup ROMS or kernels to flash...
Click to expand...
Click to collapse
Battery just died. I could not turn it off. Everytime I tried to, it booted right back up. I was in recovery, but as I said, I have no roms or kernels to flash. I tried to mount the device, but was unsuccessful. I clicked mount system and nothing showed up on computer. Couldn't click mount sd card.
Someone please help me.

Always make a back up... we'll starting now
Let it charge, try again to get the proper kernel and flash in recovery. If it won't let you mount SD to transfer, extract the boot.img from the ROM you were using and flash via fastboot.
fastboot flash boot boot.img
fastboot reboot
See what happens
Sent from my Nexus 7 using xda premium

Can you please explain how to do that? I am new to the Nexus. I can get into Fastboot and then recovery. But how would I flash via flashboot. I do not see that option.

Edit

I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium

demkantor said:
I do suggest reading up a bit on android or you are bound to find yourself in these situations. Also try and stay away from toolkits, you would already know what to do if you weren't using them
Download rom of choice to computer
Extract the boot.img from the .zip
After you charge nexus a bit, plug into computer and boot into bootloader
Open command/terminal on computer in the same location the boot.img is and type
fastboot devices
If you get 'waiting for device' you need to download the proper drivers, and or need to change directories to where fastboot.exe is located on PC, or just make sure you download everything from the platform-tools in the sdk and I recommend changing the path in environmental variables to include adb/fastboot
If you see your serial number proceed
fastboot flash boot boot.img
fastboot reboot
this should replace the kernel causing your boot loop with and all is well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?

Infuser86 said:
Learned that the hard way! So if I download the ParanoidAndroid ROM, just extract it and get the IMG file?
Click to expand...
Click to collapse
Took the img from the ROM and fastbooted it and it wrote, but tablet won't load past Google screen...

So the only thing you did to cause it to get stuck originally was flash a kernel? If that was it and then Fashing the right kernel doesn't work and recovery won't let you Mount to put a ROM on SD, I would flash one of the official full ROM updates through fastboot.
There are a bunch of them posted here just grab one and flash it and she what happens
Sent from my Nexus 7 using xda premium

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.

Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit

Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?

Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.

efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?

Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium

not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium

exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command

In twrp, it keeps saying starting adb sideload feature

i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!

Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"

Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2

Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium

efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

[Q] Boot Loop (CM Recovery)

First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...

So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk

newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu

1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.

Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.

Nexus 4 (4.4.2) not mounting after unlocking bootloader

Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!

go to settings/storage open 3dots menu /usb computer connection. if nothing is selected that is why your phone doesn't connect. select mtp an problem solved.
if it's not that i cannot help you except suggesting to reinstall android from scratch using wug toolkit.

wasabitobiko said:
Nexus 4 running 4.4.2 bootloader version MAKOZ30d
I used Wug's root toolkit to unlock my bootloader but after reboot into fastboot, neither my windows 7 machine nor my linux mint machine will mount the phone without MTP turned on. I can run adb commands while MTP is on but drivers fail to load if mtp is off.. So now I have an unlocked bootloader and am unable to complete the rooting proces..
Any help is much appreciated.
Cheers!
Click to expand...
Click to collapse
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?

acejavelin said:
You can't "mount storage" in Fastboot mode.... what exactly are you trying to do?
Click to expand...
Click to collapse
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..

wasabitobiko said:
Trying to finish the rooting process by using adb.. by "mount" I mean get access in fastboot from either of my computers. Didn't have this problem with my other N4.. when I plug the phone into my computer while in fastboot and try any adb commands.. I get <waiting for device> nothing... It seems like the adb drivers aren't loading while in fastboot. I'll try to back things out using the toolkit again..
Click to expand...
Click to collapse
OK, so your fastboot commands are not working, that would likely be a driver issue? If you do
Code:
fastboot devices
and get a result, then keep going, if you don't, use one of the driver options in Wugfresh's toolkit, follow the instructions TO THE LETTER...
If you are just trying to get root and are unlocked, download the latest SuperSU.zip (to your phone preferably) from http://download.chainfire.eu/supersu and openrecovery-twrp-2.7.0.0-mako.img then start phone in Fastboot mode and enter:
Code:
fastboot boot openrecovery-twrp-2.7.0.0-mako.img
this will start TWRP on your device WITHOUT flashing it.
If the SuperSU zip file is on your phone, just use TWRP's Install button and navigate the file and flash it, then reboot and enjoy.
If the SuperSU zip is on your PC, then in TWRP go to Advanced, and start ADB Sideload, give it a few seconds for it to be recognized by your PC, you should be able to enter
Code:
adb devices
and get a result of SIDELOAD back, then enter:
Code:
adb sideload UPDATE-SuperSU-v1.94.zip
Or whatever the current SuperSU zip file is named. Then reboot and enjoy, your rooted!

Remember that adb commands only work in android and custom recovery NOT in fastboot mode.
Sent from my Nexus 4 using XDA Free mobile app

Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
Ok.. If I can't run adb commands from fastboot, how do I enter that command in fastboot?
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
ADB sideload is a special mode that recovery can be placed into, it only allows the "sideload" command to be used. Fastboot is different, it uses the fastboot.exe program and fastboot mode on the android device to allow a limited list of features to be used.
I don't know what you are using for a rooting guide, but basically the end result is to flash SuperSU via recovery, that is all that is really needed.
Sent from my Nexus 4 using Tapatalk

Well, basically if your boot loader is unlocked and you have a custom recovery installed just download the latest superSU zip to your SD card. Reboot into recovery, install SuperSU, reboot. Alas, you're rooted.
Sent from my Nexus 4 using XDA Free mobile app

That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
If you unlocked your bootloader your drivers should be working fine. If you rebooted your phone now you'd see it works fine. Next step in rooting is to flash custom recovery. Download a custom recovery, I recommend latest version of TWRP, then flash the recovery image. 'fastboot flash recovery recovery.img' (replace recovery.img with whatever .img file you are flashing.
Once custom recovery is installed you can boot into it to flash supersu. If using TWRP it will prompt you to root when you reboot it.

Thanks.. And please don't take offense to this but re-read the thread. Ever since I used wug's rootkit to unlock the bootloader, neither my pc nor linux machine will recognize the Nexus 4. When I plug it in I get a usb error "device failed to load".. When I look at the device mgr it's listed as unknown device. Btw.. I've restarted both my phone and machine multiple times to no avail.
Sent from my Nexus 4 using XDA Free mobile app

Unknown device? Youve probably installed no or wrong fastboot drivers.
Sent from my Nexus 4 using XDA Free mobile app

wasabitobiko said:
That's the problem.. No custom recovery installed.. Still working on the driver issue.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Google tool 15 second adb xda
Sent from my Nexus 5 using XDA Free mobile app

UPDATE: It looks like the micro usb port on the phone is fried... had been charging fine until today. I'll keep you posted. Thanks for all the help. Does anyone know if this is a relatively easy fix?

Update: Fixed..
Replacing the usb port on the Nexus 4 is super easy. Thanks for the help guys. Everything's working and root has been achieved.

Nexus 7 2012 WiFi Hard Bricked or Soft Bricked?

Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca

Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs

Sam Nakamura said:
Hard to understand you actually... but boot to bootloader and fastboot flash the TWRP, use MTP to copy over what you need to flash and go ahead, in case you never used fastboot check Google there're plenty of guides out there, good luck...
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?

lucafict said:
Hello everyone, I would need to understand if my Nexus 7 2012 WiFi is definitely Hard Bricked or not.
The other day I installed Slimkat ROM and had the error 7 during installation...
I like it better: In Nexus it's root and it unlock with the Recovery CWM, which start with the sequence of Volume Down- Power On keys. I have done the wrong not to do before installing a backup with the Recovery CWM and now I am in the situation of having the Nexus that normally light up on the Google logo and if I start shooting, it is not copied on the sdcard the right ROM, unable to install anything. I seem to have read that I had installed the TWPR Recovery instead of an external USB with an OTG cable, which is impossible with the CWM.
This is my question: Is there any way to copy files to the SDCard? If I don't see the Nexus in ADB, can I install TWRP Recovery up the CWM? (for use the USB/OTG performance)
Thanks for the help and congratulations for the forum ...
luca
Click to expand...
Click to collapse
Tried with Nexus root toolkit ?
twrp better than cwm

lucafict said:
Thank you so much for your answer. But I installed CWM Recovery and I can not access to Nexus in fastboot or adb, so I can not install the Recovery TWRP. I've tried both with MAC OSX and Windows, but the Nexus is not seen by the system. Exist an alternative method for flashing the recovery TWRP without using fastboot or adb?
Click to expand...
Click to collapse
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs

Sam Nakamura said:
Bootloader is not Recovery nore ADB, it's independent from those!
Boot up by holding power & volume down till you have the bootloader screen (picture attached), if you see it plug it in your (windows) computer and check "fastboot devices", there then fastboot flash TWRP image...
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.

lucafict said:
Attacched my Fastboot page, but nothing... no devices show with “fastboot devices” command.
Click to expand...
Click to collapse
Have you another device at hand to check weather fastboot is working with a different device, just to make sure that your fastboot environment is working properly...
Sent from my OnePlus 3T using XDA Labs

Yes, with another Nexus 7, if I connect it to pc, the device is show in section device list of pc. I think the problem is that this Bricked Nexus in fastboot not start the usb driver...