yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] ulxerker:
sorry to hear that. try to do a factory reset in bootloader and start to re-flash factory image from the beginning as mentioned in the thread. I tried to help, but I'm out of ideas now as well.
[Nexus 5X General] sfhub:
There is an orange message that says your software can't be checked for corruption. That is because you unlock the bootloader.

[IMG="Yellow Warning"]http://www.androidauthority.com/wp-content/uploads/2015/07/android-orange-warning.png[/IMG]

There is a red message that says your software *IS* corrupt. That one is because your system or vendor partition got modified, most likely in his case if he saw the red corrupt message it is because the system partition got mounted read/write by TWRP because it asks you if you want to mount read/write upon first boot.

[IMG="Red Warning"]http://www.androidauthority.com/wp-content/uploads/2015/07/android-red-warning.png[/IMG]
[Nexus 5X General] Pouyafathi1991:
I use 4636 code in nexus 5x and my radio band swich on usa band . How to change radio band . Iam from iran . Please help
[Nexus 5X General] jgve:
It is the red message that I got after installing SuperSU. The phone rebooted, I got the red message, black screen with Google on it showed up and it was stuck there and didn't do anything else. So if I want to start over, do I just flash the factory image just like I did earlier? Or do I do something else where I have to run something TWRP?
[Nexus 5X General] sfhub:
There are 2 separate issues.

You are getting the red message because something in the /system or /vendor partitions changed. It doesn't necessarily mean anything is corrupt, just the signature no longer matches which could be caused by as little as 1 byte change. For example if you mount the /system partition read/write, the dates might change and will trigger the warning, but the system partition should still be fine for booting.

The second issue is you are getting stuck on the boot process.

That could be caused by erasing the user partition but not reformatting or it could be caused by a corrupted or damaged /user partition. There is something wrong with the user partition.

The first issue isn't necessarily critical, but if you wanted to get rid of the red corrupted error message and replace with the orange warning message that corruption can't be checked for, flash the system.img and vendor.img.

If you want to fix the second issue, do

fastboot erase user

fastboot format user

Keep in mind if you format the user partition, you'll also lose the root you installed earlier, but not sure if you even got to the stage where you could have used root or it immediately had boot problems.

If you want to keep it simple you can flash the factory image you downloaded earlier and it will take care of everything for you.
[Nexus 5X General] jgve:
I reflashed to factory image. I decided not to do anything with the phone snymore. I am getting the orange message in startup. How do I lock the bootloader and is it safe to do that now?
[Nexus 5X General] sfhub:
If you are absolutely sure you have the factory image in its entirety (ie you flashed the entire factory image, not pieces of it manually) then it is safe to lock your bootloader. If you aren't sure, then it is best to leave unlocked until you are as it could be difficult to unlock again in some situations.

you just type

fastboot oem lock

while your phone is in bootloader mode and connected to your PC.
[Nexus 5X General] Androloid:
I have stock rooted 6.0.1 with unlocked bootloader. I want to try Android N preview. How do I proceed?

Послато са Nexus 5X уз помоћ Тапатока
[Nexus 5X General] VOLTAGEROCK:
Why in the heavens does rooting and flashing ROMs seem so complex on this device?

Compared to all of my other Nexus devices, I'm actually worried I'll mess something up.

I've had the 5x since November and still haven't rooted it!

I haven't had time to read all 800+ posts so could some of you say if this process was somewhat difficult?

Sent from my annoying Nexus 5X
[Nexus 5X General] ulxerker:
its very easy and you're done in 2 minutes if at all.
[Nexus 5X General] Radsen:
You have to enter here https ://www .google .com/android/beta and activate your device. If you have stock I think it will go perfectly but lets wait to see what other people say.

Enviado desde mi Nexus 5X mediante Tapatalk
[Nexus 5X General] VOLTAGEROCK:
I downloaded all the files and i was at the point where I simply click mouse to get started, but I held back!

Ok, thanks for reassurance.

Sent from my annoying Nexus 5X
[Nexus 5X General] :
I agree with [MENTION=6809086]ulxerker[/MENTION]. Just read the instructions thoroughly and you should be fine.
[Nexus 5X General] Androloid:
Should I lock bootloader first? Does flashing SuperSu 2.65 patch boot.img - is it still stock? Android N is OTA update, can I take OTA while been rooted?

I believe easiest and safest way is to return to full stock first.
[Nexus 5X General] alfick3:
No, don't lock the bootloader. No you can't take the OTA while rooted. When I decided to get the DP3 I went back to full stock; I downloaded the latest M firmware and fastboot flashed it. Then I signed up for the Beta program and got my N OTA. This was closer to a month ago now and I haven't looked back since.
[Nexus 5X General] sfhub:
Not a good idea because if something goes wrong it'll be more effort to fix.

The default systemless install does patch boot.img. The system install modifies system partition. Either way it isn't stock anymore.

For normal OTAs returning to stock is best, but the Android N OTA is shipped as a full OTA rather than differential OTA. That means you can be on anything and it'll just overwrite what you have. In the worse case that it was a differential OTA, it won't break anything, it'll just complain some integrity check failed. So if it were me, I would just make sure to have stock recovery installed, then accept (or sideload) the OTA.

If it is the same effort to flash complete stock vs just recovery then you can do the former, but for me, flashing stock recovery is less effort than extracting the images and flashing individually if you wanted to preserve user.
[Nexus 5X General] yurkennis:
Looks like the June 2016 OTA update changed structure of files significantly:

boot.img

bootloader-flag-clear.txt

bootloader-flag.txt

bootloader.aboot.img

bootloader.cmnlib.img

bootloader.hyp.img

bootloader.imgdata.img

bootloader.keymaster.img

bootloader.pmic.img

bootloader.rpm.img

bootloader.sbl1.img

bootloader.sdi.img

bootloader.sec.img

bootloader.tz.img

file_contexts

META-INF

radio.img

system.new.dat

system.patch.dat

system.transfer.list

vendor.new.dat

vendor.patch.dat

vendor.transfer.list

Any changes to the update application procedure?
[Nexus 5X General] sfhub:
The "step 9" you are referring to is talking about the factory TAR file (meant to be flashed from Bootloader using fastboot)

You have listed files from the OTA, meant to be installed using Recovery.

The formats have always been different.
[Nexus 5X General] lilfarlee:
when i try to backup my stock rom it tell me i have 0MB of internal storage. How can i backup my Stock??
[Nexus 5X General] sfhub:
If you left the user partition encrypted, did you verify that TWRP was able to mount it?
[Nexus 5X General] maiflys:
Android Support Library?

I downloaded the current SDK but in the manager under extras I can't find the android support library. If I allow the viewing of obsolete packages I see that there is an obsolete library though. Is it OK to use that one?
[Nexus 5X General] lilfarlee:
I don't want to install the OTA June 2016 update right I have to do it manually or something right??
[Nexus 5X General] SlimSnoopOS:
I have only had SDK Tools and Platform Tools installed on OSX and haven't have any issues flashing .img's after several months. I think you'll be fine.

If rooted, use TWRP 3.0 to install boot, system, vendor .img's then flash SuperSU. Alternatively, follow step 9 of the guide.
[Nexus 5X General] lilfarlee:
If rooted, use TWRP 3.0 to install boot, system, vendor .img's then flash SuperSU. Alternatively, follow step 9 of the guide.

Do i want to download the OTA image or the factory image?? also how do i know which one is the latest? im currently on MTC19T there are links for MTC19Q and MTC19V.. does this go alphabetically??
[Nexus 5X General] SlimSnoopOS:
I prefer flashing factory images with fastboot but that's my preference. You can install the OTA image via TWRP. Either way works. You will need to flash SuperSU after updating.

Usually, usually OTAs are alphabetical but that is not always the case. For instance over the last few months, the first three letters of OTAs went "MMB" Nov to February, "MHC" in March/April, to "MTC" in May. That said, MTC19V is the June OTA.
[Nexus 5X General] Davirus849:
What If I dont have Android?

LG support send me back my phone from repair without the original box, without the charger, without the cables, AND without Android.

Im stuck with this (see pictures)
[Nexus 5X General] SlimSnoopOS:
Well, send it right back.
[Nexus 5X General] Davirus849:
I wish I could, but I dont have the time or the money to send it back to US, I live in Mexico.
[Nexus 5X General] Meandi51:
Is OP still safe to work on virgin 5x having latest security patch level June installed. I am conerned because of "jgve" (#808) messed up and post #820 deals with changes in June update?
[Nexus 5X General] SlimSnoopOS:
OP is up to date and any issues are user specific or device specific and needs to be warranty replaced. This does not need to be updated monthly. Post #808 is device specific. Post #820 was already discussed and was a misunderstanding.
[Nexus 5X General] Meandi51:
Ok... Will let you know my experiences when done. Device will be delivered on Monday ;)
[Nexus 5X General] maiflys:
So I'm a complete noob. I successfully unlocked my bootloader. Then I got to the part of installing TWRP. I got it installed and rebooted the bootloader. Then I accidentally pressed the power before I could open the recovery, so the phone started. I then unplugged the phone so I could go back into the bootloader. But when I tried to open the recovery I got the black screen with the little android opened up with the red triangle. (which lasted for few minutes before phone started again) Does this mean I didn't succesfully get TWRP in? Should I try to flash the recovery again?
[Nexus 5X General] alfick3:
Yes, flash TWRP again
[Nexus 5X General] maiflys:
I just checked the md5 and it's different. What should I do? I've tried re downloading and doing the 3.0.1 version of TWRP too but I keep getting the wrong md5
[Nexus 5X General] sfhub:
Just reflash TWRP.

Then prior to first boot, boot into TWRP (ie boot into recovery directly from bootloader menu)

Then flash SuperSU.

If you boot using stock untouched boot.img it will overwrite your TWRP with stock recovery.

Once your boot.img is modified by SuperSU for root, then that won't happen anymore.
[Nexus 5X General] VOLTAGEROCK:
I guess living in Mexico negates time and money?? Ship it back.

Something went awry with your phone that I've never seen before.
[Nexus 5X General] lilfarlee:
So i flashed the boot, system, vendor .img's and when i try to boot into recovery i get an android on his back with a red "!" then when i reboot the phone it says " ANDROID SYSTEM there's an internal problem with your device. Contact your manufacturer for details." I hit ok and all seems to be working fine other then i now dont have root access.

Where did I go wrong???

update i reflashed the recovery with twrp and reflashed superSU but i still get the android system error message..
[Nexus 5X General] SlimSnoopOS:
Reflash the vendor.img that matches your rom base, which I presume is MTC19V
[Nexus 5X General] Meandi51:
restoring NANDROID with enabled lock screen security

succesfully did it acc. the OP.

Installed PA, open gapps nano and the SU 2.74 beta - all fine.

Just one more question regarding NANDROID backups.

I have read there are issues restoring them, when there is any display lock (fingerprint, PIN,...) enabled.

Can anyone confirm this :( and I have to disable lockscreen before backing up by NANDROID ?

Or is it safe to handle it as usual ?

Thanks a lot !
[Nexus 5X General] charlestek:
Disabling Encryption and using Google FI Project

The pricing for trying FI is unbeatable. I understand that the data stream is always encrypted as FI moves between Sprint, T-Mobile and public Wi-Fi and theoretically it probably shouldn't have any relationship

with decrypting the the device's store. However I wonder if the FI implementation might not work because of some incompatibilities with disabling device store encryption?????
[Nexus 5X General] NexusMel:
Twrp

Hi everyone. I rooted using this method on Marshmallow and then move to Android N. I'm trying to get root back but I lose Twrp whenever I restart my phone. It'll show "No command" with the red exclamation mark. What am I doing wrong? I can't get to Super SU zip.
[Nexus 5X General] Meandi51:
Anyone did figure out?
[Nexus 5X General] Zackptg5:
This has been mentioned numerous times in this thread and others. Issue still exists. Either delete screen lock before backing up or after restoring backup, delete data/system/locksettings.db in twrp
[Nexus 5X General] SlimSnoopOS:
Boot right into TWRP after flashing, don't restart into the rom. If you are encrypted, TWRP will not work on Android N developer previews. Run this command in fastboot:

Fastboot format userdata

The above step will erase EVERYTHING from your phone. Then fastboot flash TWRP and boot into TWRP. Transfer SuperSU over and flash.
[Nexus 5X General] NexusMel:
Thanks Slim. It's been a long time since I've messed with root and such so I'm sorry for the noobishness. But can you elaborate a little more on transferring Super SU over? I had thought I would need to restart the phone to put the Super SU zip on the phone to locate it in TWRP.
[Nexus 5X General] SlimSnoopOS:
From a computer, open terminal and use ADB Push while in TWRP. On Windows, I think you can drag and drop the file over when the device is in TWRP. Might have to mount the file system first. I use OSX so I use ADB Push.

Edit: If using ADB Push, place SuperSU zip in the same folder as your ADB folder. The command would be: ADB Push /path/to/SuperSU/zip /path/on/your/phone and is case sensitive.
[Nexus 5X General] sfhub:
What snoop said.

Further, dead android is the image overlay for Stock Recovery. When you boot Android before installing root, it will overwrite your existing recovery with stock recovery.

Solution is to boot into TWRP and install root, prior to first boot into Android after an OS update.
[Nexus 5X General] NexusMel:
I'm getting device null not found when trying to use adb push
[Nexus 5X General] sfhub:
Did you accept the PCs RSA key on the phone's screen (popup dialog)?

If you don't get that option to accept keys, are you using recent adb or older one?
[Nexus 5X General] NexusMel:
I didn't get that option. I'm pretty sure I'm using a more recent adb.
[Nexus 5X General] sfhub:
What does "adb devices" say?
[Nexus 5X General] NexusMel:
Sorry I'm having a rough time with this. Can I get back to marshmallow somehow from Android N? The OTA won't work. I get an error there.
[Nexus 5X General] sfhub:
I've lost track of what you are trying to do.

Are you trying to apply an OTA to get back to MM or N?

Most OTAs you really receive over the air are differential OTAs, meaning they can be only applied over a specific version of software, for example MTC19T -> MTC19V

However, the Android N OTAs you receive from signing up for the beta are FULL OTAs which can be applied over any version. Also the OTAs you download from Google's factory image site are FULL OTAs which can be applied over any version.

I suggest you use stock recovery if that is what you are trying to install, but you still need to get your computer communicating with your phone, which it seems you are having trouble doing because it says null device.

That was what I was trying to help you resolve.
[Nexus 5X General] gbru2505:
I'm new to the 5X having come from the nexus 4 and 5. I've been running Pure Nexus, latest TWRP, rooted. It's all great. I'm unable to update to the latest build because TWRP is not seeing the zip files. It's seeing older files. Why would that be? I undid my security options whilst preparing to update - removing pin and fingerprint locks. It'sobviously to do with encryption, but why was I able to install Pure Nexus without difficulty, but not upgrade?
[Nexus 5X General] Psychofrantics:
Guys I need some help. Sorry for being dumb though.

I want to use flash-all.bat file for flashing factory images. Cn any one point me to a proper guide for setting system variables path for adb and fastboot
[Nexus 5X General] sfhub:
You don't really need to set any path. The tools have compiled in defaults for where they store their config files and flash-all.bat sets up whatever path it needs.

I usually just copy adb fastboot and the adb*.dll files into the directory that has flash-all.bat You can also put them somewhere in your PATH. Then you can run flash-all (but usually I remove the -w in the .bat file to preserve user data)

You can find just the 4 files you need in this post:

http://xdaforums.com/nexus-5x/general/psa-fix-adb-doesnt-winxp-t3403955
[Nexus 5X General] ulxerker:
try to adb sideload your zip. for this, connect your phone with your PC and go into TWRP -> advanced -> adb sideload. on your PC issue "adb sideload xxx.zip" in a terminal/command prompt, latest adb tool required. if this also doesn't help please ask in the Pure Nexus forums for specific support.
[Nexus 5X General] erikalin:
[MENTION=4153349]Heisenberg[/MENTION] Thanks for a thorough and clear guide. Some things with this device are new to me, so I'm grateful for the beginners' guide. I'll admit it. ;) Thanks again for the solid guide. Cheers.
[Nexus 5X General] Heisenberg:
Glad that you find it helpful :)
[Nexus 5X General] ScOgLiO9:
Hello there

I just got a brand new 5X, but unfortunately, it seems like I got a software-faulty unit: at first boot I was greeted (after a first boot animation) with an "encrypting" procedure which will simply not end (i.e. it endlessy gets stuck on that screen with "time remaining: 00:00").

I tried to turn the phone off and back on, with the result that I get asked for a password which I presumably had to first input after encryption, so I'm stucked. (Note: after this, I performed a factory reset, to no avail: getting again the "encrypting loop")

So, before sending the device back for substitution (and have to wait...) I want to give a flash a try.

I installed all the necessary SDK tools and tried the procedure. The problem is, I don't have access to Android from the phone and therefore to developer settings -> "fastboot flashing unlock" or "fastboot oem unlock" won't work .

Any idea on how to solve this problem (i.e. basically, unlock the bootloader without access to Android)?

Ps: I have attached both the "encrypting loop" screen and the one of an error I got from the very first time I turned the device on (which I think is a strong signal of the fact that the software is faulty).
[Nexus 5X General] sfhub:
It is strange that you would have the software corrupt message on a brand new phone. Did you get the phone from Google? Usually you only get that if you unlock the bootloader and modify /system or /vendor. The other possibility is your EMMC had some partial failure.

In any event, if you can't unlock the bootloader, try booting into recovery and flashing the FULL (rather than differential) OTA using adb sideload.

https://developers.google.com/android/nexus/ota
[Nexus 5X General] ScOgLiO9:
It seemed strange to me, as well, so I ended up asking for a substitution of the unit.

Anyway, I didn't buy it from the Google Store, but rather from an online store I have already bought from in the past, plus both the phone and the package were sealed, so I think I was unlucky and got a faulted unit.

I tried to flash the full factory image, but with no luck (the prompt telling me I had to unlock the bootloader).

I'll take into account your explanation and try sideloading the OTA, though, in the (hopefully) very unlikely case it happens again with the replacement I will get in a few days, so thanks for that.
[Nexus 5X General] tfly212:
I can't get the PC to recognize the device in bootloader mode. I have done this process with the 6P a number of times with no issues...I updated the drivers and I can see the files on the device but when I boot into the bootloader and try to connect the phone I get three fast beeps (never heard them before but they sound like "this is not working"). If I send the "fastboot devices" message via a command prompt nothing happens. Any suggestions? Thanks
[Nexus 5X General] sfhub:
win-r

devmgmt.msc

make sure there are no unrecognized devices.

fastboot is recognized separately from adb and mtp.
[Nexus 5X General] pixbuf:
This is a great, very complete guide. I followed it and was able to unlock the bootloader, flash twrp and flash SuperSU with no problems. Then I tried to restore data from Titanium Backup. I installed all the apps fresh in Play, and only used TiBu to restore data. Then everything went south. The whole device slowed down, told me I had no SIM, lock screen wouldn't unlock. I rebooted and got the red Device is Corrupt warning. I booted into TWRP, wiped everything (/data, /system, userdata, everything), reinstalled the stock files (using the flash-all script), reflashed TWRP. Still getting the red corrupt warning.

Don't know what else I can do. A few pages back, someone suggested reflashing vendor.img. Think that will help? Any other ideas?

Thanks!
[Nexus 5X General] sfhub:
When you did flash-all script, it already flashed vendor.img

Usually you only see the RED corrupt message if you aren't rooted. The root process turns off the dm-verity check. I am not sure what the RED corrupt message is complaining about if you are rooted and there is no dm-verity check.

Now if you are on stock and seeing that message even just after flashing the stock image, then your EMMC is probably failing.
[Nexus 5X General] Zackptg5:
Follow the OP instructions to return to stock and start over again
[Nexus 5X General] pixbuf:
I reflashed TWRP and SuperSU. Now I don't get the red triangle but when the phone starts I get a "System Message: There is an internal problem with your device. Contact the manufacturer" message. The phone seems to be working OK for now, though.
[Nexus 5X General] pixbuf:
I fixed it. I found this thread and lo and behold I had mismatching lines in /system/build.prop and /vendor/build.prop:

/system/build.prop:

ro.build.fingerprint=google/bullhead/bullhead:6.0.1/MTC19V/2862947:user/release-keys

/vendor/build.prop:

ro.vendor.build.fingerprint=google/bullhead/bullhead:6.0.1/MTC19T/2741993:user/release-keys

I had updated to MCT19V, but apparently the flash-all.sh script didn't flash vendor.img. I reflashed it and now everything is fine.
[Nexus 5X General] sfhub:
Was there some error you missed the first time? It would be surprising if flash-all.sh didn't flash vendor.img because it doesn't even choose which files to flash. It (via fastboot) sends over the system files included in image-bullhead-mtc19v.zip which is common for everyone so more people would have been seeing this error.

Is it possible earlier when you mentioned you read somewhere you needed to reflash vendor.img that you flashed MTC19T instead?

Anyway, glad you got your problem fixed.
[Nexus 5X General] pixbuf:
I just got the phone last week. It came with MTC19T installed. I downloaded MTC19V, and flashed it using the script. The only one I downloaded was MTC19V. The only thing I can think of was that the files in /vendor that were installed when I got the phone did not get overwritten.