yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] plbelanger:
I don't blame you. I saw this earlier today and never heard of the site personally. I'd rather just wait till something hits XDA and is confirmed working.
[Nexus 7 (2013) General] bagajai:
Stock Recovery

pulled it from /dev/block/platform/msm_sdcc.1/by-name/recovery
[Nexus 7 (2013) General] thesourgin:
I did the hard reboot it still showed the bootloader as being locked. I tried to unlock again and the exact same thing happened.

FAILED (unknown status code)

finished. total time 1.015s

When I get to the screen that says "Unlock Bootloader?", I can choose "no" and it will go back to main bootloader screen. Selecting "yes" causes the tablet to just hang.

Maybe I messed something up... any suggestions?

Thanks
[Nexus 7 (2013) General] gksmithlcw:
When you select Yes, you are hitting your power button to confirm?
[Nexus 7 (2013) General] thesourgin:
Yes. That's when it hangs.
[Nexus 7 (2013) General] darkjedi:
This is going to sound dumb, but are you using a USB3.0 port or 2.0? I had this error with a 3.0 port. Changing to a 2.0 one, fixed it.
[Nexus 7 (2013) General] thesourgin:
That was it! I wouldn't have guessed it made a difference. I guess I should have known better.

Muchas gracias!
[Nexus 7 (2013) General] treoo0_1:
I'm back!

I had my Nexus 7 (2013) early...bought today over lunch, and about 45 minutes later I borked it. That was 1pm. You, KIND SIR, have solved my problem. I'm back and so very grateful. Thank you. :good:
[Nexus 7 (2013) General] dems86:
So I got the bootloader unlocked, and when I adb reboot bootloader and try fastboot flash recovery recovery.img it keeps giving me and error. I have the recovery in platform-tools, any help would be appreciated. When I boot into recovery now it gives me andy with his gut open and a red exclamation popping out, never had this problem before, any help would be greatly appreciated, thanks.
[Nexus 7 (2013) General] treoo0_1:
that's what you get with the original recovery, if you just fastboot into recovery. Maybe re-download and reflash the twrp.
[Nexus 7 (2013) General] dems86:
It is the twrp im trying to flash, I renamed it recovery.

"error: cannot load recovery.img: no error
[Nexus 7 (2013) General] jc monkeyballs:
You don't need to be in recovery to flash TWRP, you need to be in fastboot. Shut down the tablet, then boot while holding the volume down button and power button. Then connect to your PC. Fastboot flash recovery should work fine now.
[Nexus 7 (2013) General] krnchicken753:
Can somebody pull the boot.img?
[Nexus 7 (2013) General] dems86:
i meant fastboot, my apologies. got it to work, i just needed to add .img after .img, lol stupid filename crap
[Nexus 7 (2013) General] GentMAB:
Mine is still giving me that error

Nevermind I got it
[Nexus 7 (2013) General] ejkeebler:
OK I'm the dumba$$

Can't follow simple instructions. Basically I'm stuck at the nexus logo, I can boot twrp and bootloader fine. When I go to install in recovery it looks like lots of empty folders... So open for suggestions :)
[Nexus 7 (2013) General] V8vroom:
Thanks for posting this for the new folks! Standard Android 101 for us vets. ;)

Sent from my Nexus 7²
[Nexus 7 (2013) General] mortzz:
Does Asus allow you to relock the bootloader with fastboot oem lock?
[Nexus 7 (2013) General] Nburnes:
Yes. It is a Nexus device mate.
[Nexus 7 (2013) General] phuduong:
Yes, it is
[Nexus 7 (2013) General] mortzz:
You couldn't relock with the Nexus One.

Thanks.
[Nexus 7 (2013) General] Nburnes:
Didn't know that actually! Only have had Nexus devices since the Nexus S.

Thanks! :highfive:
[Nexus 7 (2013) General] dexgen:
Tried it. THat's the TWRP recovery. :(

---------- Post added at 02:53 PM ---------- Previous post was at 02:47 PM ----------

Can someone pull a system.img? Would help a lot of folks with borked devices.
[Nexus 7 (2013) General] gksmithlcw:
http://xdaforums.com/showpost.php?p=44014664&postcount=4
[Nexus 7 (2013) General] PainfulLover:
I get "Access is Denied"

after fastboot oem unlock

all drivers and sdk are up-to-date. Can somebody tell me what am I doing wrong?
[Nexus 7 (2013) General] uknowwhoiam76:
Interesting I had the same issue. fastboot oem unlock worked for me too. Hmmm
[Nexus 7 (2013) General] plbelanger:
What do you mean by after? Was OEM unlock successful? Did you reboot once after the procedure?
[Nexus 7 (2013) General] PainfulLover:
I reboot into bootloader, than "fastboot oem unlock" and in the cmd I get "Access is Denied"

I never get to 'Unlock bootloader?' screen
[Nexus 7 (2013) General] plbelanger:
Hm what if you run cmd as admin?
[Nexus 7 (2013) General] gksmithlcw:
I've heard of problems using a USB 3.0 port. Also, try running your command prompt with elevated privileges for ****s & giggles.
[Nexus 7 (2013) General] PainfulLover:
That's a thought. I am on usb3 and it didn't occur to me to try cmd as admin.

Not enough caffeine...

I will report later.
[Nexus 7 (2013) General] PainfulLover:
ISSUE SOLVED.

USB 3.0 port was causing "Access is Denied" prompt in cmd after "fastboot oem unlock" command.

2.0 port worked like a charm, no need to cmd "as admin"

Thank you gksmithlcw and plbelanger for suggestions. :good:
[Nexus 7 (2013) General] darkjedi:
I mentioned that a few pages back. :)
[Nexus 7 (2013) General] PainfulLover:
You should have mentioned the error message as well ;)
[Nexus 7 (2013) General] gksmithlcw:
Excellent! I'll add that to the OP.
[Nexus 7 (2013) General] RCDuke:
If anyone is having an issue where adb recognizes the device but lists it as 'offline' try using the original USB cable that comes with the N7. I was originally trying to do all this with a spare USB cord I had lying around, and as soon as I plugged in the N7 with the original cord, I got a pop-up regarding "rsa fingerprint of the connecting device". I clicked ok, and adb then showed the device as online.
[Nexus 7 (2013) General] borxnx:
Unlocking not working for me

So I seem to be having trouble here. I have tried unlocking on both Windows 7 and Ubuntu 12.04 to no avail. Apologies in advance for my apparent noobness.

I have the entire Android SDK (including revision 18) installed on both OS's. ADB works fine, but when I try to run a fastboot command, nothing happens. Does the process take several minutes? I've waited two or three, but assumed it wouldn't take that long to prompt for unlock.

Also I have noticed that I don't have a recovery. adb reboot recovery shows a dead android with a red exclamation point and says "No command." I did try to install TWRP before unlocking bootloader (I know, it was stupid, but this is my first device with a locked bootloader). This makes me wonder:

A) Could trying to install TWRP have borked my recovery even if the bootloader was still locked?

B) Do you need a recovery to unlock the bootloader? Or

C) Does anyone know how I can either restore the recovery (if the answer to B is yes) or am I just completely screwed?

Thanks in advance for any help.

UPDATE

Nevermind, I didn't have the bootloader drivers. FML. Apologies for wasting anyone's time.
[Nexus 7 (2013) General] casonswag:
Why does my device say offline on adb ?

---------- Post added at 03:46 AM ---------- Previous post was at 03:43 AM ----------

Im having the same offline prob i tried switching cords but still says offline pls help?

EDIT Got everything to work i think i needed to reboot my laptop but im officially unlocked and rooted
[Nexus 7 (2013) General] gksmithlcw:
Glad you got it all figured out.
[Nexus 7 (2013) General] gksmithlcw:
Ha! First step to troubleshooting: reboot! :)
[Nexus 7 (2013) General] fosser2:
Weird I unlocked mine on 3.0 with no issues.
[Nexus 7 (2013) General] gksmithlcw:
Yeah, it seems to be hit and miss on USB 3.0 ports. I'm betting it's a driver / vendor issue and not the technology itself. ;)
[Nexus 7 (2013) General] wad3g:
I'm also having this offline issue. ADB is recognizing the device, but stating it's offline.

I'm familiar with ADB and have been using and rooting Android and Nexus devices for years. I'm using a 2012 MacBook Pro running OS X 10.8.4. I just used ADB on my 1st generation Nexus 7 on this machine last week to flash the stock image and prepare it for resale. I've rebooted both devices (Nexus 7 & MBP), tried using the other USB port, and tried multiple USB cables.

I'm not an Android developer so I don't need to install the full SDK (that I'm aware of). I've been using the ADB Tool .zip you can download for OS X and it's worked perfectly for my Galaxy Nexus and 1st gen Nexus 7. Maybe I need an updated .zip of the new Android SDK/ADB Tool or there's another issue causing this.

Any ideas? Anyone else experience this problem? Any help would be greatly appreciated.

Note: When I mentioned not needing the full Android SDK I didn't mean that as I don't need it as a developer. Who knows what all, other than the root issues with 4.3, has changed so I may need the full SDK now.
[Nexus 7 (2013) General] oneandroidnut:
Did you allow your nexus to accept the pc adb connection?
[Nexus 7 (2013) General] BrianDigital:
I had to update the SDK manager that comes with in the full SDK. Actually to be exact I had to make sure I had api level 18 checked to allow the update to the Google driver to happen.

I did uninstall my previous driver through a device manager while the tablet was plugged in. Not sure how you go about that on osx, but try the full SDK.
[Nexus 7 (2013) General] wad3g:
Yea, I'm thinking I may have to wait. I've downloaded the SDK several times and each time there's no reference to 4.3, still 4.2.2.
[Nexus 7 (2013) General] BrianDigital:
well just trying to clarify, agian I have no idea how this looks on OSX but within the SDK i went into that .exe and had to update everything and then check off 4.3

edit wow ms paint aint was she used to be

must be xda heres a better look http://i.imgur.com/k8IUaRe.jpg
[Nexus 7 (2013) General] sfhub:
Since Android 4.2.2 they added a security feature to the adb connection. Your PC does some RSA authentication with the device. You are presented with a hash on the phone in a prompt to accept. Once you accept, the adb connection is allowed.

If your adb client is not new enough to support this authentication, it will say your device is offline.

On windows, you needed to update platform-tools to 16.0.1 or newer (current is 16.0.2). You don't need to full SDK, just the updated platform-tools. I don't know the specifics of what you need to do on Mac.

This has been confusing for some folks who have had adb set up for a long time, but with older devices, and/or prior to 4.2.2. They have setups that have been working for a long time, so they expect it to work with the nexus 7 2013 as well, but this ends up being their first introduction into the security feature added in Android 4.2.2 (we have Android 4.3)
[Nexus 7 (2013) General] gksmithlcw:
Also, be sure to reboot your PC after installing the SDK and updating if you're still experiencing the issue. A member mentioned previously that this solved the problem for him / her.
[Nexus 7 (2013) General] wad3g:
Yes, I understand I need the updated 4,3 SDK for OS X, which is something I can't seem to find. As for the RSA authentication I've used ADB with this feature implemented various times , including a week ago on my 1st generation Nexus 7 running 4.2.2 where it worked flawlessly.

I know the SDK I'm downloading from Google is not an updated SDK for Android 4.3 for OS X, so maybe they just haven't released this yet. I don't actually need the SDK for OS X, all I need is the platform-tools folder for OS X. Since this is not a PC the adb/fastboot files are not .exe's, they're Unix Executable Files that open/run in the terminal.
[Nexus 7 (2013) General] sfhub:
I don't think you mentioned whether you saw the screen on your tablet asking you to accept the PCs identification, but I assume not.

If you haven't seen that screen, then adb didn't send the information to your tablet.

It could be that you are running a different version of adb now than you were before (possibly different directory or archive from before) or it could be some permission problem where adb cannot read the adbkey.pub file, or something else that would affect whether that RSA identification got sent.

Bottom line, if you don't see the prompt showing up on the tablet, adb likely isn't sending the info and since adb shows your device as offline, we know it isn't a driver problem.

Another possiblity is you are getting the message on your tablet but don't have the screen on so didn't notice you needed to accept it.
[Nexus 7 (2013) General] wad3g:
My apologies, I was sort-of-kind-of trying to answering ~4 people in one. I do get that popup to accept my computer's identification. I also still have the exact directory my ADB worked on my original Nexus 7 (and still works on my Galaxy Nexus). I've also downloaded the new SDK several times to try to get the most recent version, but it's still the SDK for 4.2.2.

I'm not sure what the adbkey.pub file is. Is there something I can do to try to fix permissions on this if it were the case?
[Nexus 7 (2013) General] trssho91:
I can confirm that the Linux drivers/packages in the repo for Ubuntu and Linux mint work perfectly on the new n7. Had this guy unlocked in 30 seconds.
[Nexus 7 (2013) General] jlee08517:
Not sure if offline and device not found mean the same things. but Device not found is what I am getting for some reason.

Also running windows 8.1 with all sdk and etc up to date.

Any suggestion?
[Nexus 7 (2013) General] wad3g:
Offline and Device Not Found are not the same. When the device is reporting as offline it's still being recognized by ADB, you're just unable to execute any ADB commands.

Make sure you have the correct drivers installed. Also make sure you have ADB and your device setup correctly. There are plenty of guides on XDA regarding how to correctly setup your Windows 8 machine with ADB, as well as, what you need to do to your device.
[Nexus 7 (2013) General] sfhub:
So you do get the popup and you have accepted it (checking the box to make it persistent) and adb still says device offline? That is very strange.

Usually you'll get device offline as the error prior to any popup on the tablet. Once it is able to send the RSA authentication it shouldn't be saying device offline because it was able to send info to the tablet, as evidenced by the popup.

adbkey[.pub] is kept somewhere in the the .android directory in your user profile. Probably $HOME/.android, but I'm just guessing since I don't use Mac.

On the tablet, I believe the list of accepted entries is in

/data/misc/adb/adb_keys
[Nexus 7 (2013) General] jlee08517:
I am sure it was just me who had a trouble with adb not connecting well.

After some searching found this link

https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

Taking no credit for work. just wanted to share with everyone who has windows 8 and 8.1 not being able to connect thru adb.

Installed the first installer and it worked like a charm
[Nexus 7 (2013) General] akwingnut:
Sorry

Ok so after reading 11 pages of this I still am unable to still get my Nexus 7 to unlock the bootloader, it was not this hard on my HTC One using the ADB commands. I dont get what I am doing wrong downloaded and updated everything but still keeps coming back as device not found but in the windows explorer it shows the Nexus 7 is there. Help please

-AkWingnut

---------- Post added at 09:58 AM ---------- Previous post was at 09:52 AM ----------

your link worked...
[Nexus 7 (2013) General] jlee08517:
I am glad to hear.

Literally took me a whole day to find that method. And that's the only one that worked for me.
[Nexus 7 (2013) General] Mort:
I can't unlock the bootloader. I get as far as seeing the "Unlock bootloader?" screen on the Nexus, but after selecting "Yes" and pressing the power button, it just hangs. At least for about 10 minutes, then I gave up. Any idea?

Update: It just got worse. After some more tries, "fastboot oem unlock" finally showed a bit more than three dots, but then hung at erasing userdata. After an hour, I rebooted manually. Or better said: I tried to. Now my device is still locked, but also wouldn't boot. I see the boot animation for hours. As it's still locked, I can't even flash the stock. Unlocking the boot loader shouldn't be that hard on a Nexus... :-/

Final update: I managed to get into the recovery menu (is it possible to do it any more complicated? You've got to press power+vol.up for the right duration...) and wipe data managed to get me back to booting. Unlocking is still impossible. As I've got no use for a device without root (esp. without backups), it's going back to Google.
[Nexus 7 (2013) General] gabo_lope:
Ahhh... I was freaking out a little when i rebooted my N7 after I unlockede the bootloader, it seems the tablet was in a bootloop, after turning it off, and on it booted just fine
[Nexus 7 (2013) General] SpecialBrewDaddy:
Hi, how can I lock the bootloader again? Thanks!:fingers-crossed:
[Nexus 7 (2013) General] Pandae:
Very close to the way it's unlocked: fastboot oem lock :)
[Nexus 7 (2013) General] SpecialBrewDaddy:
Thanks Pandea :)
[Nexus 7 (2013) General] jcjoker2008:
How long does rebooting take?

I went through the whole process and my Nexus 7 WiFi (2013) is unlocked and I clicked the power button on start to get into to boot up again and it's on that screen where it has the four colored dots swirling around. Does anyone know how long this should take?
[Nexus 7 (2013) General] bswift916:
I was wondering if you can answer a question for me and help me out?! I dled a bad rom onto my N7 and didn't create a back up. Now I have no Rom to flash. How can I restore one on it?
[Nexus 7 (2013) General] cokey77:
Use wug freshs flashing tool.
[Nexus 7 (2013) General] DaveImagery:
I'm having some kind of problem, where the bootloader is locked, although it shows it as unlocked. I put latest Marshmallow on my Nexus 7 2013, and all was fine. Then Xposed for marshmallow came out, and I was all excited to put it on mine. I installed it on Lollipop no problem. I think somewhere in the process, I screwed something up. No matter what I do, I can't install Marshmallow back on it. Using Wugs Toolkit, I keep getting the error "bootloader is locked". Only thing I can do, is restore a system backup of Lollipop via TWRP recovery. I have system image backups of Marshamllow, but regardless of what version of twrp recovery I use, I keep getting that stupid extracttarfork 255 error., when trying to restore them. Tried doing a full wipe/factory reset, but nothing works. It will only let me put Lollipop back on. HELP!!!
[Nexus 7 (2013) General] _jis_:
It is a known problem: http://xdaforums.com/showthread.php?p=63761276

You should use manual method: http://xdaforums.com/showthread.php?p=63727509
[Nexus 7 (2013) General] DaveImagery:
Thank you, I was going crazy trying to figure this out.
[Nexus 7 (2013) General] trhacker01:
Whether rooting manually or using the previous version of nrt, I ran into a bootloop when rooting. To make it work I had to use beta-supersu-v2.52. I'm assuming the SuperSU (2.46) nrt was using was casing that issue. Anyone else have that issue or know for sure?
[Nexus 7 (2013) General] borxnx:
Yeah, you need 2.52 or higher these days. 2.46 came out back in February, and a whole lot has changed since then.
[Nexus 7 (2013) General] ferjovi:
Update an update

Hello this is the first time that I write in a post, I want to know if I already update my nexus 7 to marshmellow, but through the pc, I don't know the method, I downloaded the fabric version of the os and I followed some steps and then flash all on a .bat file. I had it rooted, but now i saw that it's not rooted any more, and thats ok, I don't wanted rooted. I still see the opened padlock when it turns on. It means that the bootloader is still unlocked I think. Now my tablet works fine but i got a message telling me to update to a newer version (that's only 2 mb) I think that its for some minor corrections. But I've read in another post that if I update my tablet in that via (I think it's called OTA) It might be bricked. Is it True? I want to know if I can do the updates that de OS shows me. I think that for doing that I have to lock the bootloader again. Am I right?

Thank you so much.
[Nexus 7 (2013) General] trhacker01:
I don't have a complete answer, but I know that if its rooted the ota update will fail, but not cause bootloop or anything. Not sure if bootloader unlocked by itself will cause a problem. If u don't want to be rooted anymore, just relock the bootloader then no worries. Btw, yes the update is just bug fixes.
[Nexus 7 (2013) General] ferjovi:
Thank you so you sugest that i can relock the bootleader and then I can do the OTA updates again? thank you and sorry for been so noob hehe
[Nexus 7 (2013) General] yosmokinman:
You don't need to relock the bootloader, and relocking it will not remove root. So if the systems not stock an ota won't work anyway.

You said you've already flashed a factory image so just do that again with the latest version and forget the ota.

I don't know about the ota bricking thing, but otas can cause problems. Imo it's best to just flash the boot and system.img when a new version is released (and bootloader if it changes). You won't lose any data.

If you wan't to take otas a good idea would be to run fastboot boot twrp.img and make a backup before the update. It won't interfere with otas and if there is a problem you can boot it again and restore the backup.
[Nexus 7 (2013) General] mikhailitsky:
Is it possible to unlock bootloader without factory resetting the device?
[Nexus 7 (2013) General] beachfl:
No, by design. Security.
[Nexus 7 (2013) General] k23m:
Unlock bootloader without factory reset

True but there is work-around. Just set the byte at offset 0x4FFC00 to "2" on the aboot/mmcblk0p12 partition. This can be done in the following ways:

on rooted devices run this app

on devices with OS older than mid-2014 use Towelroot and then run the above app

on devices with bootloader released before August 5, 2014, run fastboot boot twrp.img and use dd to patch the offset

use JTAG to patch eMMC memory

use hardware programmer to patch removed eMMC chip

You can probably ignore the last two methods ;)
[Nexus 7 (2013) General] beachfl:
Cool :good:
[Nexus 7 (2013) General] mikhailitsky:
Thanks for the list.

This raises the same question - is it possible to root without factory resetting the device? :) My tablet is running Android 6.0.1, build number MOB30X.
[Nexus 7 (2013) General] k23m:
Of course it is, as long as you find a root exploit for MOB30X, or something like Towelroot for the vintage 2014 Android.

:highfive:
[Nexus 7 (2013) General] Battler154:
Is there a way to open the bootloader without having developer options and usb debugging enabled? Or is there a way to do this via adb command?
[Nexus 7 (2013) General] P.Kosunen:
http://www.android.gs/how-to-enter-google-nexus-7-fastboot-mode/

You can enter fastboot mode with holding buttons, no need for usb debugging.
[Nexus 7 (2013) General] vartanarsen:
Hello i updated drivers, but windows command screen still says ADB not available or somehting like thar
[Nexus 7 (2013) General] ludemon:
Not able to erase userdata

I have a Nexus 7 (2013) that starts only in locked bootloader mode.

Selecting :

'recovery' returns back to bootloader.

'start' goes to white Google logo, but stays there until a button is pressed, then returns to bootloader.

On cmd terminal fastboot oem unlock brings up the yes/no selection screen on the device, but stays there for ever if yes is selected. On the command prompt terminal 'erasing userdata.....' is displayed for ever.

Similarly command fastboot erase userdata or fastboot format userdata ends with 'erasing userdata.....' but no further action.

All other erase commands like fastboot erase cache work okay without error, only erase userdata freezes.

I obviously need to unlock the bootloader to be able to proceed with returning the tablet to normal working condition, but not being able to erase userdata is preventing that.

I have seen many references to this problem on the internet but so far not found a solution that works, so I'm hoping that someone here can help.