Database Info

[Q] Could not mount /data ! Phone Stuck!

I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?

Ensifolk said:
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Click to expand...
Click to collapse
Clean fastboot install :/ Solved the issue for me

try and format cache. If still no luck, fastboot flash cache cache.img

rootSU said:
try and format cache. If still no luck, fastboot flash cache cache.img
Click to expand...
Click to collapse
Can I still fastboot even if I have no USB debugging enabled? The phone will interact with the commands normally? ( Since as I mentioned before I flashed the ROM only to check out and played with no settings at all, didnt know this is going to happen )

Ensifolk said:
Can I still fastboot even if I have no USB debugging enabled?
Click to expand...
Click to collapse
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.

rootSU said:
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
Click to expand...
Click to collapse
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe

Ensifolk said:
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Click to expand...
Click to collapse
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it

rootSU said:
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
Click to expand...
Click to collapse
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )

Ensifolk said:
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Click to expand...
Click to collapse
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.

rootSU said:
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
Click to expand...
Click to collapse
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
EDIT: I renamed the extracted file to .zip and extracted again, now I have the files displayed on that page...Trying to figure out now how to flash the cache.img

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Extract it again.

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Its a .tar file. Extract it again

...

I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
I think you'v nothing to loose by flashing the whole factory image. If /sdcard can't be mounted in this situation, I think that's because you did (or a toolkit) did something wrong and break it. I don't think that you'll be able to save anything.
(It's my point of view. Maybe somebody else has an idea ?)

rootSU said:
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Click to expand...
Click to collapse
I cannot mount /data even after flashing cache.img - Hence I think I am dead by this stage and I can no more recover whatever I have on the phone. Factory image flashing then ?

Yep, I would

And there we go, I did it, phone back to life. Thank you guys ! A LOT! Appreciated ! pretty much !
Allow me to recall the scenario : I was on Slimkat, decided to try Mahdi Rom ( CM Based ), Backup before flashing, flashed, wanted to revert back. And this can't mount /sdcard there. No idea what could be it...
What recovery you guys recommend me to use ? - Lesson I learned today? I should know how to use fastboot and ditch the Toolkit galore.

Well, seems that you did'nt do anything wrong. Maybe a problem with the rom or something else occur.
Next time, maybe, do a backup and, then, copy it to your computer
For the recovery, I use CWM 6.0.0.4

Unable to mount Data issue

Hi, I have had this issue for a while now where my custom recovery looses the ability to mount data, this is the message I get,
E: could not mount /data to set up /data/media path. When the problem occurs which can be going into to recovery from any custom rom I just reboot the phone again which has always rebooted ok, but I am worried that it may not reboot ok some time in the future breaking my phone.
I have tried all 3 custom recovery's so I don't think it's a recovery problem, anyone have any ideas what the problem may be.

Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk

rootSU said:
Usually a problem with /cache. Wipe it a few times or fastboot flash stock cache.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, can I fastboot flash stock cache.img on any rom ?

maxal said:
Thanks, can I fastboot flash stock cache.img on any rom ?
Click to expand...
Click to collapse
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk

rootSU said:
Yeah, any ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.

maxal said:
Ok I have just done fastboot flash stock cache.img and I get a failed (remote: partition table doesn't exist) any idea what is wrong now.
Click to expand...
Click to collapse
fastboot flash cache cache.img
Tapatalk-kal küldve az én Nexus 5-el

maxal said:
fastboot flash stock cache.img
Click to expand...
Click to collapse
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk

rootSU said:
This wasn't the command. This was me telling you what to do. As you're already rooted, I expected you would know the command. See @bitdomo posted.
Please read up about fastboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks fastboot command worked that time. I normally use adb and fastboot commands but I have never had to use cache.img command before, Thanks again :good:

Update: I tried what rootSU said but it didn't resolve my problem so I tried one last thing which was to flash a factory image using the LG Flashtool and so far every thing seems fine. So should anyone else have the same problem that I had with their recovery give the LG Flashtool ago. Should my original fault reoccur I will post an update.

For what it's worth, I had the same issue as the OP. I didn't want to flash the .tot, because my computer was being weird(it said COM41 was in use, because I already used the LGFT for my G2, didn't want to risk it). Basically I just RMAed it, because all fixes were failing. Using e2fsck, flashing stock cache, etc. I could temporarily fix it by flashing a factory image, but when I flashed a new ROM, it would happen again. So if it keeps happening, just send it back. :good:

I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.

maxal said:
I would like to add to what Koopa777 said that flashing a factory image was just a tempory fix as I tried this several times, but so far so good the data issue has not re occured since I used the LG Flashtool.
Click to expand...
Click to collapse
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:

Koopa777 said:
Cool, I'll keep that in mind in case the new one gets it. Could you try something for me though? PA 4.2 BETA 5 always set it off for me. It booted fine, but the recovery was always borked when I rebooted into recovery. If your's survives that, I think that it could definitely be the fix. :good:
Click to expand...
Click to collapse
No problem I will test PA 4.2 beta tomorrow for you.

I had the same problem on an installation of a kernel that didn't boot atop a CM rom. When it bootlooped, I went into recovery and found the infamous could not mount /data. I tried rootSU's recommendation about wiping cache several times and flashing a cache.img but it didn't work for me. I was about to do the whole factory stock image thing (and thus wipe my sdcard) when out of desperation to avoid that, I tried something that surprisingly succeeded. The following steps are for a newbie but presupposes a working knowledge of how to use adb and fastboot commands.
1. Download and copy a known stable ROM's zip file into your SDK's platform-tools, renaming it ROM.zip
2. Boot you phone into (TWRP 2.7.0.0) recovery
2. Choose ADB sideload in Advanced
3. From your computer's DOS prompt in the SDK platform-tools directory, type adb sideload ROM.zip
When it's done sideloading, it will flash
4. Choose reboot system
It will boot and get a series of FC's of android process and dialer
5. Hard reset into bootloader (hold down the power button until screen goes off (in like 7 secs) immediately hit vol-down) and choose recovery
Voila! Rebooted into recovery for me with data mounted as normal. No need to flash factory images!
Hope this helps and good luck!

I know that this thread is nearly a year old, but just wanted to report that my phone soft bricked when I flashed a kernel (without flashing the rom). TWRP (2.8.5) was unable to mount data, storage, /data/media. When I went into TWRP/Advanced/File Manager there was nothing in the sd card. After an ADB flash cache cache.img it was still the same. I decided to follow the @reeper000 post and it booted into the ROM i flashed (Slim Lollipop version) and it came up with only a couple errors. I was then able to go into TWRP and restore a nandroid backup and all is fine. I was sooooooo close to erasing data/restoring to a factory image!!!!!! THANKS, @reaper000!

Glad all well. I had 2 nasty surprises yesterday. First I flashed a nandroid
, only one I had. It kept going past 100 %on loading the data. Went to 300%! I'd one rom with Gapps I'd not tried so I thought saved.. Aghhhhhh Noo when it came on said playstore support missing. Had to tap like mad to get it off the screen in between putting my acc in. 2 hours later it linked and downloaded the missing file. Thank god. Then my baseband went! I was at my wits end. Decided I'd nothing to loose with a factory reset which fixed it. Good job as the new battery came today! Now I test backups and have two different ones

Help me please ......

Good morning everyone
I need a help from you
I tried to install the latest official version of MIUI but failed so i tried to install an older version but stuck on installing....... so i rebooted my N5 to install a backup but now i can't access my sdcard ( error mounting) ?, i have an important things that i need to save, Any solution for not losing those things? ?? Because if i try to bring my N5 back to stock rom, i will lose everything. So please help me
Thanks in advance

hearts king101 said:
Good morning everyone
I need a help from you
I tried to install the latest official version of MIUI but failed so i tried to install an older version but stuck on installing....... so i rebooted my N5 to install a backup but now i can't access my sdcard ( error mounting) ��, i have an important things that i need to save, Any solution for not losing those things? ?? Because if i try to bring my N5 back to stock rom, i will lose everything. So please help me
Thanks in advance
Click to expand...
Click to collapse
You still have a custom recovery, right? Boot in it, and connect your phone to your PC. You need adb installed for this
Using adb push to copy a ROM on your sd-card from your pc, and install it normally
adb push <location to rom.zip> /data/media/0
or you could use adb sideload
adb sideload <rom location>

To make adb work you need universal naked usb drivers.
If you have windows 8 or 8.1 turn off driver signature enforcememt.
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
To make adb work you need universal naked usb drivers.
If you have windows 8 or 8.1 turn off driver signature enforcememt.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Not true! I'm using adb with windows 8.1 and USB drivers from the android SDK without any problems or workaround needed.
Sent from my Nexus 5 using Tapatalk

yak84 said:
Not true! I'm using adb with windows 8.1 and USB drivers from the android SDK without any problems or workaround needed.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Then they eventualy updated the drivers. Thanks for the update!
Tapatalk-kal küldve az én Nexus 5-el

abaaaabbbb63 said:
You still have a custom recovery, right? Boot in it, and connect your phone to your PC. You need adb installed for this
Using adb push to copy a ROM on your sd-card from your pc, and install it normally
adb push <location to rom.zip> /data/media/0
or you could use adb sideload
adb sideload <rom location>
Click to expand...
Click to collapse
That unfortunately did not work so i had to return to stock rom and everything was erased.
Thank you all for your kind help:highfive:

hearts king101 said:
That unfortunately did not work so i had to return to stock rom and everything was erased.
Thank you all for your kind help:highfive:
Click to expand...
Click to collapse
Same happened with me yesterday...had no choice but to factory flash it and even the imei no was not there(cache partition) but good thing was that I took the complete backup a day before only so just got saved.

Bricked my nexus 5 bootloader..

Hello guys
A friend of mine was flashing some roms to try and when tried purity, the phone went inot a black dead screen
Recovery was working,but bootloader gave only black screen and no fastboot commands were working/accepted
THe, maybe for miracle, after reflash a cyanogen rom, the rom has booted and is working.. but sstill no bootloader
He was on stock 4.4.3 before the flashes
Someone can provide me a solution to restore the bootloader or,at least, fastboot commands??
He use TWRP recovery
thanks

bootloader its there , since its the one who starts the kernel/recovery,its more low level than kernel, it controls the buttons etc... .
for some reason its failing to boot into fastboot mode, try using adb reboot bootloader (looks weird to do, but on early nexus 7 2k12 bootloader there was some problems that doing this would do the trick, also do it while system is running or in recovery), if still goes black screen, re flash bootloader using dd comands in the recovery(there is a thread to fix no bootloader things, look at it)

I don't know if it is the case. But it could help you...
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-images-lg-t2713833

erto90 said:
Hello guys
A friend of mine was flashing some roms to try and when tried purity, the phone went inot a black dead screen
Recovery was working,but bootloader gave only black screen and no fastboot commands were working/accepted
THe, maybe for miracle, after reflash a cyanogen rom, the rom has booted and is working.. but sstill no bootloader
He was on stock 4.4.3 before the flashes
Someone can provide me a solution to restore the bootloader or,at least, fastboot commands??
He use TWRP recovery
thanks
Click to expand...
Click to collapse
If the rom was not working and the bootloader just showed black screen and didnt accept fasboot commands, then how on earth you entered recovery to flash cm11?
Because there is only 2 ways to enter recovery:
1: From bootloader you select "reboot recovery"
2: you have a working android and and do the adb reboot recovery command.
Can you tell me how you enter to bootloader? If you press all the buttoms when the phone is on state then the phone goes to qualcomm's download mode, and show a black screen. If you were doing that then now try to press only the volume_down and power buttoms to enter bootloader mode (or fastboot mode)
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
If the rom was not working and the bootloader just showed black screen and didnt accept fasboot commands, then how on earth you entered recovery to flash cm11?
Because there is only 2 ways to enter recovery:
1: From bootloader you select "reboot recovery"
2: you have a working android and and do the adb reboot recovery command.
Click to expand...
Click to collapse
Yeah... I want answers.

DVTeixeira said:
Yeah... I want answers.
Click to expand...
Click to collapse
But I need answers first
Tapatalk-kal küldve az én Nexus 5-el

This is the tread
that opssemnik mentioned http://forum.xda-developers.com/google-nexus-5/help/how-to-fix-bsod-bootloder-t2763370
it could help.

Extract the bootloader file from the factory image and flash it using the secondary bootloader (volume up and down + power).

[Q] FAILED (data transfer failure (Too many links))

Hi, I was trying to flash stock 4.4.3 to my Nexus 5 using this method. Something happened and now it won't boot up past the "Google" splash screen with the padlock.
I decided to try using Nexus Root Tool v1.8.3 to flash it, using Back to Stock > Current status: Soft-Bricked/Bootloop. I saw that there is an older thread where someone had a similar issue, but I'm still fairly new (I'd say intermediate level) at this stuff and I don't understand what they're saying and I'm on the verge of freaking out because I do everything through my phone.
I can still access the Bootloader and Recovery, so I believe there's hope, but I keep trying over and over again and the command line keeps spitting out errors, then fastboot crashes. Please help! :crying:

I tried method #2 in this guide on XDA, and fastboot picks up my phone, but some of the commands are failing, stating "FAILED (command write failed (Invalid argument))" or "FAILED (command write failed (No such device or address))" or the error mentioned in the thread title.
After trying it, my phone is still bootlooping.

seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order

175
meangreenie said:
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
Click to expand...
Click to collapse
I tried
Code:
fastboot format userdata <directory>\userdata.img
and it failed (you can see it in the 2nd screenshot in the 2nd post). Don't I need to be rooted to be able to flash a custom recovery? I'd successfully unrooted before this mess occurred.
What's .tot flashing about? I'm willing to try that if flashing custom recovery is a lost cause.

you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.

Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el

meangreenie said:
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Click to expand...
Click to collapse
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
bitdomo said:
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.

Also, in case it's important, TWRP showed this (see attachment):

Dalae said:
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Click to expand...
Click to collapse
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.

bitdomo said:
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
meangreenie said:
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
Click to expand...
Click to collapse
Okay, thanks. I'll try the LG Flashtool. If I have any questions, I'll ask here. Either way, I'll post results.

I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?

Dalae said:
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Click to expand...
Click to collapse
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el

bitdomo said:
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Ah, alright. Thanks! I don't really care that it's not the original, as long as it doesn't have any undesirable effects. And, just for the heck of it, here's what was in the log regarding the original and the result:
[15:46: 7] 11. device factory version = LGD820AT-00-V10a-NXS-XX-OCT-09-2013-KQS81M-USER-32G+0
[15:46: 7] 12. device factory out version = LGD820AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-XXG+0
I installed the 4.4.3 OTA and it went smoothly. I'm free to unlock my bootloader, root, and install custom recovery now, correct?

nice to see your up and running
yes. now you can unlock and root
just one thing to watch out for, after running the unlock command you must let your phone fully boot once. this is because the original recovery is needed to complete the process during boot up.
then your free to install a custom recovery and flash a root zip, supersu by chain fire recommended by me. then when booted install and run busybox from the playstore

Great, thanks! I rooted using NRT, which installed BusyBox Free for me.
Sent from my Nexus 7 using Tapatalk

I have been getting this kinda crap on my Nexus 7 2013 and Nexus Player when I upgrade between OS Versions.
The Fix is to open up the system update ZIP file, extract the individual partitions and flash SYSTEM.img manually
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I think it has to do with a Fastboot memory limitation or something. It could be an older version, but it seems it just can't flash everything at once. If you separate it out and flash each one separately, it works fine.