yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] alin.c.mihalea:
#HELP #NEEDED

I have been waiting like 5 mins with this last line and it does not seem to be happening anything. What is it doing? Is it ready or should I be waiting still?

Is it safe to proceed to "fastboot oem lock", as in the guide?

C:\SDK\platform-tools>fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bhz10r.img
target reported max download size of 536870912 bytes
sending 'bootloader' (4602 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.172s]
finished. total time: 0.345s

C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s

C:\SDK\platform-tools>fastboot flash radio C:\bullhead\images\radio-bullhead-m8994f-2.6.32.1.13.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.308s]
writing 'radio'...
OKAY [ 0.932s]
finished. total time: 2.241s

C:\SDK\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s

C:\SDK\platform-tools>fastboot flash boot C:\bullhead\images\boot.img
target didn't report max-download-size
sending 'boot' (11493 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s

C:\SDK\platform-tools>fastboot erase cache
< waiting for any device >
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.080s]
finished. total time: 0.081s

C:\SDK\platform-tools>fastboot flash cache C:\bullhead\images\cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.067s]
sending 'cache' (5688 KB)...
OKAY [ 0.199s]
writing 'cache'...
OKAY [ 0.113s]
finished. total time: 0.382s

C:\SDK\platform-tools>fastboot flash recovery C:\bullhead\images\recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (12545 KB)...
OKAY [ 0.335s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.551s

C:\SDK\platform-tools>fastboot flash system C:\bullhead\images\system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.571s]
sending sparse 'system' 1/4 (516666 KB)...
OKAY [ 12.314s]
writing 'system' 1/4...
OKAY [ 8.482s]
sending sparse 'system' 2/4 (523957 KB)...
OKAY [ 12.530s]
writing 'system' 2/4...
OKAY [ 8.916s]
sending sparse 'system' 3/4 (506010 KB)...
OKAY [ 12.270s]
writing 'system' 3/4...
OKAY [ 9.317s]
sending sparse 'system' 4/4 (411562 KB)...
OKAY [ 9.840s]
writing 'system' 4/4...
OKAY [ 6.865s]
finished. total time: 81.120s

C:\SDK\platform-tools>fastboot flash vendor C:\bullhead\images\vendor.img

Why the error in boot.img? Should it be this way?
[Nexus 5X General] ulxerker:
no, you should see a progress when flashing vendor, too.

also, the error when flashing boot.img isn't normal.

what is your purpose, going back to stock including re-locked bootloader? which rom do you come from and which buids are you trying to flash?

anyway, you might want to repeat the procedure from the beginning.
[Nexus 5X General] alin.c.mihalea:
So, before this, I had Android 7 OTA, but it messed with the camera ("Can't connect to camera") and so I decided to flash a stock image of Marshmallow -6.0.1 (MTC20K).

My purpose is to try Marshmallow again, maybe the problem regarding the camera will disappear.

So, if I want to repeat the procedure from the beginning, how should I proceed? Is it bricked now? I still have my phone opened in Fastboot Mode and connected to the PC. Will it boot back to Android 7 if I reboot it?

*sorry for being numb, didn't do this before.
[Nexus 5X General] ulxerker:
don't reboot, it won't make it. just try to re-flash all images according to the OP if you are still in bootloader.
[Nexus 5X General] alin.c.mihalea:
I have tried re-flashing the images.

I get this message when trying to flash the radio file:
[Nexus 5X General] SlimSnoopOS:
Why do you have a file path of "\bullhead1" in this post, but \bullhead" in your prior post?
[Nexus 5X General] alin.c.mihalea:
I have downloaded again the Marshmallow image and unzipped it in another folder, so that is why I changed the path.
[Nexus 5X General] mr_gourav2000:
Hi friends,

I have some problem -

I successfully unlock bootloader, and also flash twrp.

After that when i boot system and again come to recovery, its stock.

So why it is stock recovery?

Again i need flash twrp and running recovery fine.

But after going system and then recovery, it is not twrp, it is stock.

Please help.
[Nexus 5X General] paulga:
nexus 5x

android 6.0.1

rooted following the Guide

everything works except the microphone in video chat...

making/ receiving calls functions well. Saying "OK google" wakes up the phone as usual. But, the microphone apparently does not work, because the other party cannot not hear my voice.

what's wrong:confused:
[Nexus 5X General] ulxerker:
thats a known behaviour. after flashing twrp you have to boot into twrp at least once before booting into OS.

follow these steps: flash twrp in bootloader -> boot directly from bootloader into recovery (twrp) -> flash supersu and kernel if you like -> boot into OS

twrp should stick this way.
[Nexus 5X General] hilla_killa:
Ive never heard of only rooting causing any problems unless you messed with something! Of all the phones ive rooted never has only root caused any problems. What exactly did you do?
[Nexus 5X General] sfhub:
If you boot with unmodified boot.img, it will restore stock recovery.

If you install SuperSU it will modify boot partition and as side effect TWRP will stick.
[Nexus 5X General] paulga:
what I exactly did after rooting is installing a call recorder that works.

update: the problem is no more after a reboot.
[Nexus 5X General] paulga:
still no 'root' access

Redmi 3S,

6.0.1 MMB29M

I rooted phone following the Guide and installed SuperSU

some apps that requires root function as intended, e.g. f.lux, a callrecorder

but Droid VNC server says the phone is not rooted

what's wrong?
[Nexus 5X General] Nightshadow931:
How did you end up here with Redmi 3S?

This is Nexus 5X section.

You're using app which was last updated in 2012, so it doesn't support systemless root. Use another app.
[Nexus 5X General] paulga:
it's the same issue with Nexus 5X.

what other VNC server do ppl use?

I'm using VMLite, but I have to connect it to a laptop and run a PC program to start the vnc server every time after the phone ( already rooted ) is rebooted. I already configured VMLite to start automatically after reboot, but this option did not take effect.
[Nexus 5X General] deusfaux:
the SDK folder that has the unzipped files, plus the installed files from SDK manager.exe is quite large.

Can any of that be deleted, retaining the ability to unlock/root/etc in the future?

In the past with my N5 I apparently only ever saved "platform tools" as a standalone folder and continued to use that.

What's the other stuff for?
[Nexus 5X General] Nightshadow931:
Well, it would be the problem for every newer phone, since most of them use systemless root from marshmallow.

I have no idea which to use, but there has to be one which is 'alive', unlike the one you are using.
[Nexus 5X General] SlimSnoopOS:
Have you reflashed again since you last posted? Preferably with MTC20F or MTC20K 6.0.1.
[Nexus 5X General] alin.c.mihalea:
Yes, I managed to flash it with this tool http://www.wugfresh.com/nrt/

So it probably was something I was missing.

I am running MTC20K now. Unfortunately, the problem regarding the camera was not solved after the re-flash.
[Nexus 5X General] SlimSnoopOS:
Hmm, and have you tried reflashing just the vendor.img for MTC20K? It shouldn't still be a problem unless the actual hardware is failing somehow.
[Nexus 5X General] fvisagie:
Do not uninstall, Windows needs separate driver installations for each of fastboot and device mode. It seems recovery mode uses the same driver as device mode.

---------- Post added at 08:58 ---------- Previous post was at 08:47 ----------

A quick off-topic question, which call recorder is that? I'm having audio quality issues with Boldbeast, my previous go-to recorder.
[Nexus 5X General] alin.c.mihalea:
No, I haven't tried that. So, can you please tell me which are the steps I should follow for flashing only the vendor.img?
[Nexus 5X General] SlimSnoopOS:
This file is installed when you run the flash.all, but try it anyway. You would follow section 9 but only run the command for vendor:

Fastboot flash vendor \path\to\vendor.img
[Nexus 5X General] sichosidd:
Hello I have a quick question.

I reverted to stock following the section 9 "9. How To Update To A New Build Of The Stock ROM".

And my question is, because anrdoid 7.1 factory images will be out in a week or two I am wondering if I need to flash it with adb again following these steps or do I get a OTA update and install it through that ?

Thanks.
[Nexus 5X General] SlimSnoopOS:
Need? No. If you are just on the stock rom, you would get an OTA whenever Google decides to slow roll out 7.1 to Nexus devices. If you do not feel like waiting, manually flashing factory images or adb sideload OTA zips may cut out all the waiting.
[Nexus 5X General] sordup:
fastboot not working...

I have just received a replacement Nexus 5x for a rear camera issue on my original 5x under warranty. I have both phones with me. My original one is unlocked and rooted with stock Android 7 image. I have my latest Android SDK Platform tools on my Windows 7 machine. I am wanting to set up the new phone just like my original, of course, with root and all.

With the phone connected to computer and USB debugging and OEM unlocking ticked on, and then going into a command prompt in Platform Tools I can issue "adb devices" and get my new device serial returned and I can issue "reboot bootloader" and the phone reboots into the bootloader. However no fastboot commands work from there on with "fastboot devices" returning nothing and any other fastboot commands hanging on "waiting for device".

All the above being the exact same but plugging in my original phone, I have no issue with fastboot commands with "fastboot devices" returning my serial and all else being normal. So my drivers are therefor good, yes? In fact, I had just used the same computer and fastboot to reinstall Android 7 and root on that original phone just weeks ago in an attempt to troubleshoot my camera issue.

What could be causing this new, same model phone to not connect with fastboot??
[Nexus 5X General] sfhub:
What do you see in

WIN-R

devmgmt.msc

Compare new device and old while in fastboot.

It is possible somehow your system only has the drivers associated with the old device but not new.
[Nexus 5X General] sordup:
When in the Device Manager console while connected to the NEW Nexus 5X and in the bootloader and fastboot inoperable, my device shows up in "Other devices/Android" with a yellow exclamation mark. With the OLD Nexus 5X in the same setup and fastboot operable, it shows under Android Device/Android ADB Interface in Device Manager as normal.

How are my drivers suitable for one Nexus 5X and not the other?? How do I fix this?
[Nexus 5X General] sfhub:
Try right clicking on the "other device" entry for your new phone and ask it to update drivers and choose to get from internet.
[Nexus 5X General] sordup:
Sorry, I should have mentioned that I did that:

When NEW Nexus is plugged in and in fastboot mode, right clicking and choosing update drivers returns "Windows was unable to install your Android, Windows could not find driver software for your device"

In addition, browsing to my <sdk>\extras\google\usb_driver\ folder in order to install from there does not work either.

I don't understand why the driver in this folder works for one Nexus 5X and not another. ??
[Nexus 5X General] fvisagie:
This is probably still caused by the fact that the Google Windows USB drivers don't properly recognise the Nexus 5X device IDs.

What worked for me was - instead of letting Windows automatically search for and install drivers - to select the manual option, and then selecting the correct device name before clicking OK for installation. First connect your working Nexus 5X in fastboot mode and open Device Manager beforehand to make sure of the correct device name. Then replace the 5X with the other in fastboot mode and select your driver manually.

The other option is to use other drivers instead of the Google ones. I don't have the links handy now but this solution was posted a couple of times on this thread.
[Nexus 5X General] sordup:
I got it working.

It was a setting in Windows to allow for driver installation to search online - don't know how that got turned off. But anyway it works.

I am still confused as to why the drivers for one Nexus 5X don't work for another Nexus 5X, all else being the exact same, device name and all! But no worries; I slogged through. Thank you.
[Nexus 5X General] sfhub:
You had it search *from the net* or just on your drives?

The Google USB drivers don't have the proper USB IDs for the 5x.

Windows doesn't have them built in either.

If you have the system search on the net, it will come up with Marshall London Bootloader drivers. These are compatible drivers for a phone made by Marshall London (the music equipment company) Basically almost all fastboot drivers are the same, just with different names and USB IDs so this one will work fine.

If you really think there is an issue with your new 5x (rather than an issue with win10 and/or google usb drivers), post (or just compare yourself) the USB IDs from devmgmt.msc for the old and new 5x.

If they are the same, then this issue isn't with the new 5x.

If they are different, then this issue is with the new 5x.

---------- Post added at 10:29 AM ---------- Previous post was at 10:18 AM ----------

That is why I specifically asked you to choose to update the drivers from the net. The most common reason you might not pick up the drivers automatically from the net is because you marked one of your connections as "metered" because you wanted to disable Microsoft forcing unwanted updates down your throat or because you don't feel like your connection being bogged down by windows update at inopportune times rather than just when you choose.

Well as explained earlier, the real Google drivers don't work for *any* 5x for fastboot mode (which has different USB IDs than adb mode). The real Google drivers *do* work for adb mode on the 5x.

As far as I know there aren't official "signed" drivers for fastboot on the 5x and Win10 doesn't include them built-in, so the simplest way to get "signed" fastboot drivers is to have win10 search on the net for drivers and it will find another phone that shares fastboot USB IDs with the 5x.

I don't think win10 will take drivers it got from the net and apply it to another instance of the phone (unlike what it does with drivers that are local on your drive). I think it will force a search before it will apply network sourced drivers a second time (I am just guessing here, I didn't actually try this to verify) So if you allowed windows to search net for drivers when you initially installed your original 5x, but later on turned off that feature, either intentionally or unintentionally as the result of something like marking a connection as "metered" then that would explain the behavior you saw.
[Nexus 5X General] drvalianto:
[SOLVED] Just need to restart the computer to clear and have more free RAM. use the updated ADB version as recommended in #1 would help do the trick, too.

I was trying "Update To A New Build Of The Stock ROM" to NBD90W, every flashing step was fine except system.img. The error was "cannot load xxxx system.img". When I rebooted the phone, it was still on NRD90R. How can I fix it? Do I need to flash NRD90S first, then NBD90W? Thanks!
[Nexus 5X General] sfhub:
Are you low on space on the PC or the phone? I think for large size images it needs to break up into portions and stage it. The system img is over 2GB.
[Nexus 5X General] SlimSnoopOS:
That's an interesting solution. Thank you for posting that update. I've noticed a few others with the same issue out of nowhere for these last two 7.0 builds.
[Nexus 5X General] sfhub:
Glad you got it fixed.

I don't think ADB version was the issue though. I have several older revisions of ADB lying around and was able to flash 7.0 releases on multiple 5x units without issue.

I suspect the issue is the Android 7.0 images are 300MB larger and they come as ZIP file instead of TAR. That 300MB gets magnified because multiple copies get generated in the process.

When some people open the zip file they'll open inside windows explorer, which then make a temp folder of the unpacked 1.2GB zip file into the temp directory, using extra 2GB. Then when you use windows explorer to unpack the internal zip file to get the system.img, boot.img, etc. it'll make another temporary directory using up another 2.6GB. Then you'll have your copies of the unpacked components, using up yet another 2.6GB. Then adb needs to flash system.img, which is a sparse filesystem so it needs to get expanded and staged, which might use another 3GB.

So I would say to be on the safe side have around 12GB free on the drive that contains your TEMP directory to flash 7.0 zip-based factory images. I don't remember if ADB stages to the TEMP directory or your user profile directory. For most people TEMP and user profile is the same drive letter.

For the tar based released many people used utilities to unpack the tar which just did everything on the fly. In windows explorer it makes a copy of the zip file, which eats up a lot more space on your PCs drive than before.

The sum total of all this is you need a lot of effective free space to flash these zip-based Nougat images. You can reduce the amount of space significantly if you use 7zip or winzip to unpack the zip file rather than windows explorer since it won't create the temporary directories.
[Nexus 5X General] efrant:
If your computer doesn't have a lot of RAM, the trick is to force fastboot to break the system image into smaller bits before sending it to your device. Instead of using "fastboot flash system system.img", you should use "fastboot -S 512M flash system system.img"
[Nexus 5X General] drvalianto:
That's true. After restarting the computer, I gave the original method of fastboot another try and intended to use the latter command if the former still did not succeed. But somehow, everything was fine :fingers-crossed:
[Nexus 5X General] sordup:
Thanks for all the info!

Although my system is Windows 7, as mentioned in my original post, and I did choose the option to update drivers searching "computer and the internet", it took another option that popped up at one point (I know not how or why) to tell it to really go online to check, and this is what worked. To my knowledge, I have not set up my connection as "metered", but I do have Windows Update set to just notify me when updates are available instead of automatically downloading. Is this the possible culprit for the update driver search not defaulting to the internet?

When I compare the driver details of each, now functioning fastboot devices, I get the same driver info.

All is well now. Thanks again!
[Nexus 5X General] sfhub:
I don't think -S affects how much RAM on the PC is used. Unless I am reading the source incorrectly, it limits the size of what is sent to the device. It has the same effect that the Nexus 5x is already doing because the 5x tells fastboot to limit the size that fastboot sends to the 5x (because the 5x has limited RAM)

From what I can tell, fastboot just keeps expanding the system.img sparse file into PC RAM until RAM runs out or the expansion is done. If you start running out of physical RAM on the PC, normally you'll have a pagefile so windows will keep expanding the pagefile, but if that pagefile is on the same drive as the TEMP directory, pagefile might run out of space to expand also. Some people may already have a large pagefile allocated so no expansion is necessary, but others might have a small page file to start.

https://android.googlesource.com/platform/system/core/+/android-7.0.0_r14/fastboot/fastboot.cpp#1535

fastboot flash

https://android.googlesource.com/platform/system/core/+/android-7.0.0_r14/fastboot/fastboot.cpp#959

do_flash

https://android.googlesource.com/platform/system/core/+/android-7.0.0_r14/fastboot/fastboot.cpp#959

load_buf

https://android.googlesource.com/platform/system/core/+/android-7.0.0_r14/fastboot/fastboot.cpp#784

load_buf_fd

https://android.googlesource.com/platform/system/core/+/android-7.0.0_r14/fastboot/fastboot.cpp#748

get_sparse_limit

---------- Post added at 01:26 PM ---------- Previous post was at 01:17 PM ----------

Sorry for missing the part about your PC being on Windows7. I am so used to people with Win10 installs having the fastboot driver problem. I only have XP, Vista, and Win10 boxes lying around. On XP and Vista I can manually manipulate the fastboot drivers to include the USB IDs that are missing and make it work with 5x. On Windows 10 (and I think Windows 7) I'd have to turn off driver signing to get the same drivers to work, so the preferable method is to get signed drivers that will work. On Windows 10 they are supposed to load automatically from network, but I have metered connection turned on (because Windows 10 likes to download tons of stuff in the background which I wanted to prevent) and that had the side effect of also turning off automatic driver updates. I am not sure what turns it off on Windows 7 but apparently there is something that will do so. I think metered connections is something they introduced in Windows8 because people were complaining about the incessant background downloads.
[Nexus 5X General] Nex23:
Question: When i factory reset my phone to install for example a costum ROM, are my TWRP-Backups (Nandroid, EFS) still there ?
[Nexus 5X General] SlimSnoopOS:
Yes, if you factory reset while booted in TWRP. The userdata partition is not touched in this scenario.

No, if you factory reset while booted in Android. The entire phone, including userdata, is formatted in this scenario.

Edit: Good catch [MENTION=1299673]sfhub[/MENTION]
[Nexus 5X General] sfhub:
I think you have the "Yes" and "No" in the wrong sentences.
[Nexus 5X General] capripio:
hey guys my TWRP isn't persistent after I boot into system and then reboot to recovery any help?
[Nexus 5X General] sfhub:
fastboot flash recovery twrp.img

fastboot flash boot boot.img

*FROM the bootloader menu, boot into recovery*

Install SuperSU.zip

TWRP will then be persistent.

If you ever boot a stock boot.img, TWRP will be replaced with stock recovery.

When you install SuperSU, it patches boot.img. Therefore it is no longer stock.
[Nexus 5X General] capripio:
is there any appropriate SuperSU.zip file? or better if you can provide direct link?
[Nexus 5X General] ulxerker:
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
[Nexus 5X General] Svenpa:
Great guide, followed it and everything is working nicely so far.

Just one thing. As soon as I finished installing TWRP, factory reset and did the startup I got prompted about a OTA Nougat update which I can't remove from the notifications. Is it just an amazing coincidence that an update was just released or did something in the process maybe cause it? I'm not going to install it since the guide tells you it's not possible without reflashing stock first, so how do I get rid of it?
[Nexus 5X General] sfhub:
I think probably google play services puts it up but I forget.

You can install it if you want, it'll just fail with no damage. The prompt should go away after you try to install it.
[Nexus 5X General] Svenpa:
Oh nice, I would never have dared to try on my own volition. It rebooted into TWRP and after doing a system reboot from there the notification disappeared. Thanks.

*Edit* It came back after a while again. I'll try and hide the message now that I got root somehow so it's probably not a big issue.