I cannot unlock my bootloader. I have a Nexus 16 wifi with 4.2.1 and no other hacks or mods applied. Bone stock.
When attempting this through the Nexus root toolkit or Nexus 7 tool kit or through a fastboot command line device says unlocking now but does not reboot afterwards. When manually rebooting device is not unlocked. I will also add that my device is encrypted through the software provided on the device. Also I cannot factory reset the device through the UI or through the bootloader. Again it says it's doing these tasks but upon boot up I am still asked for my storage unlock password and the device is still back the way it was pre wipe attempts.
Other strange behaviors indicating a wipe attempt are random reboots, Andriod OS process consuming > 40% of my battery. Also device installs the same app updates every time I reboot or if the device reboots on it's own.
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
No dice
duffieldj1 said:
I would try un encrypting your device and then try to factory reset and then when you go to unlock the boot loader do not do it through the tool kit instead download android SDK and then unzip the download and then go SDK -> platform-tools and then once inside that folder hold the shift button and right click in the blank space in that folder and then click open command window here, also be sure you have correctly installed the nexus drivers from within the tool kit and then put your nexus in fastboot mode and connect it to the computer and then in the command window type a adb OEM unlock and then follow what it says on the nexus
Sent Via Nexus 7
Click to expand...
Click to collapse
Unfortunately the only way to un-encrypt device is to reset it to factory spec again which it will not do no matter the method tried. The drivers are correctly installed via the toolkit. The tool kit shows that device serial number. I have installed the SDK and have tryed that method via fastboot 'fastboot oem unlock'. I then follow the directions on device and press the power button. Device is stuck at 'Unlocking now.....' However nothing happens. It does not automatically rebooot or wipe device. When I push the power button the device boots normally as if nothing had happened. Also bootloader is still locked. If I can get it unlocked I think I should be able to wipe it.
Output from command:
C:\Users\Scot\Downloads\adt-bundle-windows-x86\adt-bundle-windows-x86\sdk\platfo
rm-tools>fastboot oem unlock
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 31.029s
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
bftb0 said:
Sort of sounds as if the $64,000 question is whether or not the "device encryption" is doing it's job, or whether it has a back door.
I can see why people might actually want the behavior you are describing - so long as Google was making it abundantly clear that such behavior was part of the bargain.
I don't know the answer - looking around ATM.
Click to expand...
Click to collapse
Wondering too if this is an unintended consequence of encrypting the device. So now that it is encrypted if the device is lost or stolen it's no good to anyone as there is no way to reset it back to a functional device. There has got to be a way to around this. I travel quit a bit for work and that is the only reason I chose to encrypt was in the event it was lost or stolen.
I have an RMA number open with Asus in the event that this cannot be figured out. Really though it is not a hardware issue, it's definitely software related.
[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"
SOLVED!
So I went ahead, tried flashing the stock recovery, no joy (no recovery menu at all - just a bad-android image). After a while, tried flashing CWM touch (via Toolkit) - and now it's working. So, everything seems good now.
----------------
UPDATE 5 - PARTIALLY SOLVED:
So, after the last couple of things, I began to suspect bad hardware, as I alluded in those updates. And I was right.
But... it wasn't the hardware you might have thought.
It was...
(this is embarrassing)
The USB cable.
Yes, the USB cable. It was the wild variations in recognizing the fastboot mode that made me suspicious. Replaced the USB cable with another one and... stability, achieved. Unlock, root, recovery program and SU program all went without a hitch. In fastboot mode, for the first time, the device serial number shows.
HOWEVER - things are not perfect. The recovery mode from the bootloader still gives the bad-android icon.
I just used the toolkit to reflash stock recovery back to the device. This completed rapidly, without error. I then tried the recovery option in the bootloader, but again, no joy.
So at this point, I point a finger partly at the tools used to flash this - they claim there is no problem, yet the flash doesn't take at all, and no error is given. As a sometimes firmware developer, I'm used to flash being followed up by a checksum or other test to verify success of the flash. Is that not being done (shame, if not). If it is, then apparently the flash works, but the software being flashed doesn't? The stock recovery???
Any ideas on how to get this back? I just did the full unlock, which wiped all user data, and proceeded from there. I now have a solid connection, but don't really know how to get things back.
Perhaps I need to manually reinstall 4.2.2?
----------------
UPDATE 4:
So, on a lark, from fastboot in Android, I selected the "Recovery" option - it starts to boot that, then gives the Android with red triangle and exclamation point. So, looks like the recovery was toasted.
This was a brand new device earlier today. It has been completely wiped twice, and none of this has gone away. Seriously: bad device?
-----------------------
UPDATE 3:
So, I thought I'd try the direct approach, as outlined here:
http://forum.xda-developers.com/showthread.php?t=1741395
Device is in Fastboot, Device Manager shows it as ok.
I run fastboot flash recovery <file> -- and IMMEDIATELY get "fastboot has stopped working" - that's right, a hard crash in fastboot. And this is repeatable.
Am I wrong in thinking this looks more and more like a driver problem? I note that fastboot is recognized as a device maybe half the time - the other half, it gets an exclamation point in Device Manger. All I do then is restart the bootloader using the bootloader menu, and usually it fixes right up. But that's obviously a huge red flag, as the device should be recognized every time.
Is this a defective Nexus? The only thing that seems dicey is anything relating to fastboot/bootloader (which is, however, unlocked - or at least it says it is).
----------------
UPDATE 2: Using the "restart bootloader" in fastboot results in slightly worse non-recognition of the device. When I do that, I get a straight "USB Device Not Recognized" from windows - the device manager doesn't even show "Android Phone" as a class of device in this case.
---------------------
UPDATE 1: I found the thread talking about missing entries in the INF file. I added these, and got a somewhat, but not entirely, stable recognition of the Nexus 7 when in fastboot mode. Basically, sometimes it is recognized, other times it is not. By "recognized", I mean that the Windows Device Manager shows the device as "Android Bootloader Interface", with no indication of a problem (which it only does in fastboot mode - it shows as a composite ADB device when booted normally).
However - it seems it fails to recognize fastboot about half the time, although it seems that that is related to reboots - that is, a fresh boot, then going to fastboot through adb seems to work. But restarting fastboot manually fails to be recognized (Windows shows a bang by the "Android Bootloader Interface", and says the device "failed to start").
So, using 4.3.5 Nexus 7 toolkit, I tried to unlock the bootloader. Windows recognized fastboot mode, but the process errored out anyway, after maybe 15 seconds, saying "Too Many Links" - the same error as before.
Again, brand new 32gb wi-fi-only Nexus 7, with 4.2.2 update and the most basic configuration only (dev mode, usb on, etc.)
Any ideas?
-------------------------------------------------------
ORIGINAL
So this is a new, out of the box nexus 7. The only setup has been to connect to wifi, update to 4.2.2, and enable developer mode and USB debugging.
Running latest paid-for toolkit - Update 29 Feb 13, version 4.3.5
Just about everything requires the insecure fastboot, but every time I try any operation that attempts it, I get:
Booting into fastboot mode
downloading 'boot.img' ...
FAILED <status read failed <Too many links>>
I basically can't do anything - in this case, I was trying to backup.
It is being done on 64-bit win7 system that had drivers, and worked for another nexus 7 a couple months ago. But, just to be safe, I uninstalled the drivers, rebooted, and installed.
However, I see this on the home page of the toolkit:
FASTBOOT MODE [If serial shows, drivers are installed]
List of Devices attached
ADB Mode
List of devices attached
<numeric code> device
From this, it seems I should expect the word "serial" to show up if the drivers are installed?
I then unplugged the Nexus, refreshed the menu, and both Fastboot and ADB show no devices.
I then plug in the nexus - I get the usual two tone "device attached" sound, no warning or error message from Windows.Checking the Windows device manager, I see a section "Android Phone" with the entry "Android Composite ADB Interface". There are no unknown devices, which would seem then that drivers are working.
So, another refresh of the main menu, and again, I see, under ADB MODE, a single device ID number, and the word "device".
I don't know what to make of this. Apparently, per the "if serial shows" message in the main menu, drivers a NOT installed. But according to Windows, they are.
This perhaps matches the fastboot failure.
Should I see "serial"?
In any case, what do I do to get the drivers to work properly if they aren't?
And if they ARE working, then what is wrong with fastboot?
At this point, I think the toolkit is broken, and worked a couple months ago.
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Erik.Leach said:
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Click to expand...
Click to collapse
I've since figured that out. There was nothing at all, when in fastboot mode, only ADB. But then I found the thread describing two missing INF entries. I added those, updated the driver, and now the fastboot mode (which wasn't even recognized by windows) is now ok in the Device Manager. However, in the main menu, it shows, literally, "??????????" instead of a serial number - that is, there are question marks instead of serial number, Following that, a few spaces and then "fastboot".
Apparently, there are still inadequacies in the driver as relates to very, very new models running 4.2.2 (which this is).
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Erik.Leach said:
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Click to expand...
Click to collapse
Interesting. I did re-flash the stock recovery, and could get that without the android image.
stickplayer said:
Interesting. I did re-flash the stock recovery, and could get that without the android image.
Click to expand...
Click to collapse
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Erik.Leach said:
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Click to expand...
Click to collapse
Thanks! Next is trying to put 4.x on a Samsung Vibrant.
Hi folks,
I've browsed a number of other threads looking for an answer, and tried a number of methods but I feel like further attempts without asking for help are going to be shots in the dark. The issue I'm experiencing is really strange to me, as the device will boot all the way into the OS before rebooting itself after a few seconds. This is my friend's tablet, and I assumed it would be fairly straight forward for me, but that was an incorrect assumption. All apologies if there's a clear cut answer to this solution posted somewhere, I spent quite a lot of time between reading threads here and various search results before finally swallowing my pride and posting here.
Anyway, what the device is doing: It reboots within seconds of booting up to the lock screen (which is responsive to input sometimes, but not others). When it is responsive, I can unlock the device, but I'm not able to do much else before it reboots. As far as I can tell, ADB debugging is not turned on, but "adb devices" returns the device SN when in recovery/sideload mode.
I am able to access fastboot without issue, which displays the following:
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SIGNING - not yet defined
LOCK STATE - LOCKED
Click to expand...
Click to collapse
I can issue a "fastboot oem unlock," which will bring up the unlock confirmation screen. Here, one of two things will happen.
It will either drop back to the fastboot screen with "Unlocking now......" displayed in the upper left corner of the screen and do nothing, or start the bootloop described above. On the PC side, I get "FAILED (remote: ()"
In recovery mode, it says "Android system recovery <3e> KTU84P." and I'm able to push files via adb sideload (though I had to install Koush's universal ADB driver) . I tried applying the signed-nakasi-LRX21P-from-KTU84P zip, which made it all the way to "patching system files," before rebooting, so I thought I was going to be in good shape, but the bootloop returned. I've also tried sideloading nakasi-ktu84p-factory-76acdbe9.tgz, as well as the image-nakasi-ktu84p.zip from inside the .tgz, but I get "E: footer is wrong, E: signature verification failed."
Even trying a data wipe/factory reset from recovery mode doesn't seem to do a thing, despite it claiming to wipe the cache and data partitions.
Anyway, I'm optimistic considering the tablet is booting (or at least kind of before rebooting). I've tried both the Nexus Root Toolkit (on two different win7 machines) and even went so far as trying it all manually via what they're now calling Android Studio and its dependencies. I'm wondering if either a) there's some kind of image that doesn't require the bootloader to be unlocked (as I was hoping would be the case with the above reference signed LRX21P/Lollipop update zip), or b) if I'm missing something in my attempts to get the bootloader unlocked.
Any thoughts or considerations would be greatly appreciated. I'm not sure what to try other than starting from scratch at this point.
Thanks!
Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.
Hey guys!
I've been scouring these forums for two days now making sure my specific issue hasn't been discussed and, from what I've seen, I've won some sort of "annoying issue" lottery.
I was handed a Nexus 7 (ME370T) a few days ago and told "if you can fix it, it's yours."
I can get to the bootloader no problem but not the actual OS. Here's the data from the bootloader:
Fastboot Mode
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - xxxxxxxxx
Signing - not defined yet
Lock State - Locked
Long story short, I've installed the Android SDK and when I plug the tablet into my PC, I can see it as "Google Nexus 7 Bootloader Interface"
When I use fastboot devices, it sees the tablet just fine.
When I use adb devices, it doesn't see the tablet.
I've tried fastboot oem unlock and I get a FAILED (remote: (Unknown error code)) error.
I can run the unlock feature through the Nexus Root Toolkit but it reboots to a black screen (my device manager sees it as "Asus Transformer Prime APX Interface")
When I finally get the thing rebooted to the bootloader (manually powering off and then back on), it's still locked.
I have no idea if USB Debugging was turned on or not. I keep reading that, to flash a partition to a new file, the bootloader doesn't need to be unlocked but every single time I try to fun fastboot, i get Failed, Bootloader is locked.
Am I nuts? I know I'm new to this but I'm fairly certain I've done everything right! You guys seem super knowledgeable and I hope you can help me out!
Thanks!