I have a Nexus7 (2013) and the OS was deleted. I want to use NexusRoot Toolkit to unlock the bootloader to re-install the OS. Everytime I try to unlock it, it comes to the screen, and when I use the volume buttons to press yes and press the power button, it just freezes and won't do anything. I can't install Android if the bootloader is locked, and it will just freeze when I press yes. How do I fix it? I have the right drivers and it does recognize it. I only have until tomorrow to fix it.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[Q] I can't unlock the Nexus 7 (2013) bootloader?
- Thread starter sean100v
- Start date
-
- Tags
- nexus 7 (2013)
Madbat
Android Expert
You have a brick my friend. There are a lot of these at the moment. Happened to most people on 5.0.2. If you updated to 5.1.1, it doesn't seem to happen, well no reports of it yet. But a lot of people who stayed on 5.0.2 have reported that type of brick. So far the only solution has been to replace the mother board.
You said the os got deleted? If that just happened randomly, then that is the type of brick that was lighting up xda about a month ago. Sorry to be the bearer of bad news bro.
You can start reading about it here
Hi guys,
I am in the same boat. I simply cannot unlock my bootloader on Nexus 7 2013 wifi with "fastboot oem unlock" command. My tablet just freezes when i trigger that operation. I have tried android one toolkit and nexus root toolkit 2.0.5 and notthing... every help appreciated here. I have done a lot of chocking on the forums and the issue seems to be unresolved.
I am in the same boat. I simply cannot unlock my bootloader on Nexus 7 2013 wifi with "fastboot oem unlock" command. My tablet just freezes when i trigger that operation. I have tried android one toolkit and nexus root toolkit 2.0.5 and notthing... every help appreciated here. I have done a lot of chocking on the forums and the issue seems to be unresolved.
Madbat
Android Expert
Do you have the adb drivers set up properly?
Hi Madbat,
Thank you very much for the reply. I think my drivers are all right. I am using Windows 10 x64 pro and when i run cmd (as an administrator) and hit "fasboot devices" I have got response (device ID). I can reboot bootloader from cmd (fasboot) or from Nexus Rootkit tools. Based on that I assume that my drivers (I have pulled the drivers from here: http://developer.android.com/sdk/win-usb.html ). My windows manager recognizes device as "android device > Android Bootloader Interface" (driver version 11.0.0.0) date 28/08/2014 provider google, Inc .
Back to ADB, I don't have opportunity to turn off debugging because OS is not starting. ADB cannot see the device from CMD. Therefore I am just using fastboot. Oh...and of course "recovery" is also not starting - when i go there I am getting "google login screen". I have tried to upload the TWRP or different bootloader with Nexusus root kit (application is establishing connection with N7, check drives, fastboot connectivity... pushes the image fine, reboots bootlader... and it still comes back at locked and the same version 04.05). I don't know the history of this N7, i have received as it is (locked and signed bootloader fl0 04.05) and I am really keen to fix.
I have read yesterday that some users has fixed that by taking the back cover and pressing the connection tapes... Seemed like a long shot. I have given it a go and .... nothing.
From my perspective the key would be to find out how to unlock bootloader.
Thank you very much for the reply. I think my drivers are all right. I am using Windows 10 x64 pro and when i run cmd (as an administrator) and hit "fasboot devices" I have got response (device ID). I can reboot bootloader from cmd (fasboot) or from Nexus Rootkit tools. Based on that I assume that my drivers (I have pulled the drivers from here: http://developer.android.com/sdk/win-usb.html ). My windows manager recognizes device as "android device > Android Bootloader Interface" (driver version 11.0.0.0) date 28/08/2014 provider google, Inc .
Back to ADB, I don't have opportunity to turn off debugging because OS is not starting. ADB cannot see the device from CMD. Therefore I am just using fastboot. Oh...and of course "recovery" is also not starting - when i go there I am getting "google login screen". I have tried to upload the TWRP or different bootloader with Nexusus root kit (application is establishing connection with N7, check drives, fastboot connectivity... pushes the image fine, reboots bootlader... and it still comes back at locked and the same version 04.05). I don't know the history of this N7, i have received as it is (locked and signed bootloader fl0 04.05) and I am really keen to fix.
I have read yesterday that some users has fixed that by taking the back cover and pressing the connection tapes... Seemed like a long shot. I have given it a go and .... nothing.
From my perspective the key would be to find out how to unlock bootloader.
Madbat
Android Expert
Ooohhhh. So this tab is not booting system or recovery? So when you try to unlock bootloader it just stalls at " wiping user data"? If yes, that is bad news my friend. You have yourself a brick. It happened to a percentage of nexus 7's on lollipop 5.0. I may be wrong, be sure to reply with what errors you get when you attempt unlock. But if this is the case, the only way people have been able to fix it is a mother board replacement. I hope I'm wrong, but it sounds like someone sold you a lemon scented brick. Check my post a couple posts back for a link about the problem to see if it sounds familiar.
. Thanks for the reply.