yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] efrant:
What kind of backup are you looking for? Are you looking to back up the "firmware" so that you can go back to fully stock? If so, then there is no need as this is a Nexus device and the factory images are already available here to take you back to fully stock. If you are looking to back up your apps, settings and app data, then you need to use TWRP or ADB backup. To use TWRP, you need an unlocked bootloader and unlocking the bootloader wipes all your data (but doesn't make you "non-stock"). ADB backup works irrespective of the bootloader lock state, but it is easier if you can use TWRP rather than ADB. Here is a pretty good write-up on ADB Backup -- note that it was written quite a while ago when the feature wasn't fully implemented in ICS, so while it works now on JB/KK/MM, you may see users in the thread saying it didn't work as intended. In any case, ADB backup is mostly useful to backup your app data just before you unlock your bootloader. Once your bootloader is unlocked, you can easily backup with TWRP.
[Nexus 5X General] Corbula:
Thanks.

I don't really care about backing up apps and settings (could I not just use Helium or Titanium, I don't know I've never used them before). It's mainly the firmware, the bootloader state, root, stuff like that so I can put it back to an as new state like it's just come out of the box. Just for the purpose of warranty and just starting fresh if I mess something up.

I know you can unlock the bootloader and still have warranty but I think I'm right in saying that if you flash a custom rom or kernel then that voids the warranty? So I just want to have a failsafe as such.
[Nexus 5X General] efrant:
Helium yes (it's essentially based on ADB backup with a GUI and some other features). Titanium no, as it requires root.

In that case, you have no need for a backup. As I mentioned, the factory images ARE your backup. Most non-Nexus devices require a backup because the OEMs don't provide them for you. Google does, so a stock backup is really not relevant.
[Nexus 5X General] Corbula:
Ah ok cool.

I think I will unlock the bootloader and maybe root it so it's ready for any custom rom or kernel in the future. It's good to know the just using the factory images will get me back to stock. One question, if you use the factory images from Google to get back to stock, will you start getting OTA updates or would you have to do something else too?
[Nexus 5X General] efrant:
A few points:

1) Yes, if you are using the factory images from Google, you will receive the OTA update notification and you can then proceed to install it. That said, not everyone gets the notification at the same time. That's why threads like this exist, so when one person gets it, they can post the link to the file, and then everyone can download it and install it (using ADB sideload).

2) Unless a custom ROM specifically disables the OTA update service, then you will get a notification on a custom ROM, but you won't be able to install it -- it will obviously fail if you try to install it, as you are not stock.

3) Generally speaking, the updated factory images will be posted before you get the OTA update notification. So, once the new update is announced, and the updated factory images are posted, there is no need to flash back to the previous-version factory image and wait for the OTA notification -- just flash the already-updated factory image.
[Nexus 5X General] :
How do I know should I use bullhead-mdb08l-mboot or bullhead-mdb08m-mboot?
[Nexus 5X General] reddv1:
Go to setting>about phone and scroll down to see the Build Number.
[Nexus 5X General] neinfricatu:
Could anybody please tell me if my phone is still encrypted if in settings-security appears encrypted? It is reporting correctly or not?

I have used this tutorial to unlock the bootloader, install twrp 2.8.7.2, root and installed a custom rom but everytime I reboot to recovery it decrypts data. I am guessing it force encryption when i reboot the device everytime?

Thank you!

Later edit: I have solved it by format data and flashing chainfire boot image.
[Nexus 5X General] JaCh0o:
Hello,

Can I ask you to provide bullhead-mdb08m-mboot-systemless.img with Encryption ON ??

Changing polices and replacing files is a bit beyond my capabilities.
[Nexus 5X General] reddv1:
I can but Encryption is optional with bullhead-mdb08m-mboot-systemless.img. you can check if you are encrypted or not by going to Settings>Security and under encryption, if you are encrypted it will show Encrypted greyed out , if not it will show Encrypt phone. You can press on Encrypt phone to encrypt your phone.
[Nexus 5X General] bsbharath1987:
I'm wondering if this is a placebo effect or have anybody noticed a much improved battery life (especially better dozing) after decrypting?
[Nexus 5X General] JaCh0o:
If I do that after rooting I get stucked on colorful loading bubbles

Wysłane z mojego Oppo Find 7 przy użyciu Taptalka
[Nexus 5X General] reddv1:
Yeah, the phone is encrypting on the loading screen. You have to wait up to an hour for the phone to encrypt.
[Nexus 5X General] mungbeans:
What version of M are the posted version of the rooting software compatible with?

I've tried rooting MDB08M with the mdbo8m boot img , SuperSU2.52, TWRP2.8.7.2 but am getting stuck in a boot loop. Any suggestions why its not working for me?
[Nexus 5X General] teapea:
TWRP is asking for a password to decrypt. I'm using 2.8.7.2 - it then can't mount sd so it can't find any files to flash.

What have I done wrong?

Also - tried to reboot as at this stage everything else went fine - but stuck at the loading screen with the 4 colourful google logo animation. Been like it for 30 mins now.

EDIT: All sorted now, seems that a factory reset in TWRP was needed. After that it all sprang into life. Most odd.
[Nexus 5X General] Nomelas:
anyone know how to fix the boot up image after unlocking the bootloader. I'm talking about the warning stating "your device cannot be checked for corruption. please lock the bootloader" ?
[Nexus 5X General] joetheshmo:
I think I saw somewhere on here there is a replacement for that message but you cannot get rid of it. I just ignore it.
[Nexus 5X General] PiousInquisitor:
http://xdaforums.com/nexus-5x/themes-apps/tool-change-bootlogo-images-imgdata-tool-t3240052
[Nexus 5X General] PiousInquisitor:
[MENTION=4153349]Heisenberg[/MENTION] I would like to suggest an addition to your guide. In the Quick Tips section you could add that you can enter the bootloader and recovery while connected to the computer via adb. You know the commands... I hope.

adb reboot bootloader

adb reboot recovery
[Nexus 5X General] Heisenberg:
That's not a bad idea, yes I know the commands, I'll add them now.
[Nexus 5X General] yldlj:
Do you need to flash the modified boot.img before flashing recovery.img
[Nexus 5X General] berndblb:
No you don't. Read the OP again - it's outlined clear as can be.

[MENTION=4153349]Heisenberg[/MENTION] Great guide! Thank you! Just what I needed to get me up to speed on a new device. Jeez, the Nexus is easy compared to the other Android devices I have had!

Love your avatar! LOL

But you have the better user name :D
[Nexus 5X General] PiousInquisitor:
The guide does say a prerequisite for flashing recovery is a modified boot image. Read it again.

I didn't though, as it doesn't make much sense to me.
[Nexus 5X General] berndblb:
You're right, it does say it in the prerequisite - my bad. My understanding is that you need the modified boot image for root - not for flashing the recovery. And that is where flashing the boot.img shows up in [MENTION=4153349]Heisenberg[/MENTION]'s instructions....
[Nexus 5X General] blackrome0:
Probably a little bit off topic, but I'm using wugfresh's NRT updater and i can't seem to get TWRP or busy box to function. I can't install busy box. It force closes after it fails to install. I tried updating to 124.1 but that didn't work, I also uninstalled and installed again from the playstore but that didn't work.

I also can't reboot into TWRP, unless I reboot through the NRT updater.

If I try to reboot normally without the updater, then I get the red warning message saying my phone is corrupt, followed by the green android robot with a red warning triangle coining out of it's stomach.

I'm running MDB08L

What I'm doing wrong?

Thanks
[Nexus 5X General] perusmuro:
Try BusyBox On Rails. And try flash only TWRP nothing else.
[Nexus 5X General] spc_hicks09:
Anyone successful in rooting WITHOUT access to a PC? Still waiting on my Type C to USB A cable so I can't connect to my PC yet.
[Nexus 5X General] queerquirks:
I plan to root and have xposed installed, currently I'm rather confused with the traditional vs systemless method.

1) Will you get an Ota update on a rooted stock rom and is it advisable to update?

2) If it doesn't boot after the update, is it as easy as flashing back to stock and re rooting assuming there's a modified boot image for that new build number?
[Nexus 5X General] berndblb:
Not that I know of. If you bought the cable anywhere but Google, you better check if it is build to USB C specs. There are a lot of bad cables out there. The majority USB C > A on Amazon are not build to standard and could fry your PC's USB port

https://docs.google.com/spreadsheet...V4-eP_sfNVNzbA/htmlview?usp=sharing&sle=true#
[Nexus 5X General] Novocaine88:
I've literally just finished doing this as of 5 minutes ago via NRT. I went from fully locked and unrooted etc.. followed the guide to the T. Unlocked successfully - got the orange warning message upon boot (not a problem), then rooted - got the red warning message (again no problem). The only problem I'm having is getting busy box to install. It doesn't force close or anything - just fails to install. I'm downloading Titanium Backup now as I heard this has an install busy box feature.

Other than that, I've had no problems. Did you make sure to follow the TWRP steps of selecting the two files to flash (I forget the name)? That to me was the only bit that didn't have clear instructions (they were possibly slightly outdated with the current version of TWRP)
[Nexus 5X General] spc_hicks09:
1) As far as I know, you will still get the notification, but install will fail.

2) Yes it's as simple as flashing the factory image, take the OTA, reroot.
[Nexus 5X General] AdrieW:
Total Newbie

Hi all.... I just got my Nexus 5x with the Google Fi service and I noticed that now I can't load webpages that are run on javascript (for work) and have java plugins. I used to be able to see those sites on my Samsung Galax S4 until the last update...

Since I'm a total newbie, I wanted to ask if anyone can point me in the right direction.

- Major: is there a way to root the phone to be able to load java webpages, plugins, and flash plugin? If so, what do I need?

- Minor: I don't care for the keyboard; is there a marshmallow version of the Samsung keyboard yet? (It wouldn't install the Lollipop version when I tried that) or do I need a special root for that as well?

Thanks for any help you guys can give me.

Baseband Ver: M8994F-2.6.28.0.65

Build Number: MDB08L
[Nexus 5X General] EricG90:
Can't help you with the major problem but for the minor try swiftkey if all your after is a better typing experience!
[Nexus 5X General] Smac7:
So android pay does not work with rooted phones right? If the bootloader is unlocked and i install a custom rom but unroot in supersu will android pay work?
[Nexus 5X General] sdxda:
I followed the steps. Got into TWRP. Told it I want to reboot and it asked me to install root. I said yes. Then I rebooted. Then the phone has been on the little circle animations at boot for like 10+ minutes. It is supposed to take this long?
[Nexus 5X General] joetheshmo:
If you didn't flash a modified boot img it could be encrypting your phone which takes a while.
[Nexus 5X General] sdxda:
Thanks for the quick reply. I didn't see a step for flashing a modified boot image. Isn't the phone encrypted to begin with? I was planning to check root on stock rom and then reboot and flash pure nexus. Do I need to flash a modified boot image at some point? I don't really understand what a modified boot image does.
[Nexus 5X General] joetheshmo:
It is encrypted to begin with but if you wiped data with twrp then it removes encryption. Modified bootimg will take off forced encryption as well as a few other things I can't think off of the top of my head relating to selinux
[Nexus 5X General] sdxda:
thanks! I didn't wipe any data, at least not intentionally. I'd like to keep the encryption so I guess it's okay. I'm still waiting.. going to have to leave it on overnight.. hope it works out.
[Nexus 5X General] berndblb:
You need to flash the modified boot image if you want root. Look at Heisenberg's guide again and read the prerequisites under "How to root your stock rom".

It's a standard feature in TWRP that it offers to root if it detects you are not. But TWRP doesn't know that you need that modified boot.img on this device with MM. TWRP is developed for a multitude of devices and this feature does not work as usual on this phone. Just reboot the phone, flash the boot image in fastboot and then flash SuperSU in TWRP.
[Nexus 5X General] joetheshmo:
Thanks for the clarification! I rooted before the updated twrp came out that could decrypt so I've always used the modified boot img but it was my understanding that you didn't need it after the twrp update.
[Nexus 5X General] Heisenberg:
There's definitely a step for flashing a modified boot.img, if you had followed the instructions properly while rooting you shouldn't have been able to miss it. You also shouldn't have accepted the prompt where TWRP offered to root for you, as far as I know the version of SuperSU that it flashes is outdated and incompatible. As [MENTION=4968172]berndblb[/MENTION] pointed out you need to follow the instructions; flash the modified boot.img and the correct version of SuperSU. We are in a guide thread here, did you not actually read the guide?
[Nexus 5X General] ishu07x:
nice

its the best:D:good::good::)
[Nexus 5X General] yldlj:
How come the guide says prerequisites for twrp you need the modified boot.img?? Isnt it just to root?
[Nexus 5X General] Heisenberg:
That's an error on my part, thanks for pointing it out. Apologies, it's been fixed now.
[Nexus 5X General] sdxda:
I went back to stock and started fresh. I did section 1 and section 2 (twrp-2.8.7.2-bullhead.img). Rebooted and rom was fine and so is TWRP. Then went to install a custom rom section. Finished that section and pressed reboot on twrp and twrp said no OS installed. I'm guessing I need to do section 3? In other words simply wiping data in TWRP is not enough, you need to format data section as well?

EDIT- NVM. I did a reboot and rom was fine. I guess its just a bug in twrp.
[Nexus 5X General] NPuter:
You need to flash a modified boot image if you want to decrypt the stock rom, correct? (Wouldn't the data partition just encrypt upon boot with the stock boot image after formatting it?)
[Nexus 5X General] Evo_Shift:
Yep. I accidentally made that mistake and didn't realize it until my entire phone was setup. I thought the decrypt instructions meant if you used a new enough version of TWRP you don't need to flash a modified boot img. The TWRP message only refers to the formatting.
[Nexus 5X General] sn0warmy:
Flashing MMB29K factory image over MDB08M

I figured this would be the best place to ask this, since it applies to the OP's instructions for flashing the factory images...

I am already familiar with using Fastboot commands to flash a factory image. However, I've never tried flashing a factory image over an existing one without wiping any user data. I'm currently running the stock untouched (and not rooted) MDB08M image. Now that the MMB29K image is available, I'd like to flash that. But ideally I'd like to do it without wiping all my current apps and data.

To do this, can I simply flash the MMB29K system.img (and vendor.img, if necessary) and wipe caches? Or is the process more in depth than that?
[Nexus 5X General] joetheshmo:
If you're not rooted why not wait for an ota update?
[Nexus 5X General] sn0warmy:
Because if the process is as simple as flashing the new system.img file and wiping caches it will take 1 minute and won't require any waiting.
[Nexus 5X General] joetheshmo:
Go for it and report back :)
[Nexus 5X General] AJ:
does the boot.img for rooting MDB08M works on MMB29K ?

or should we wait for a new image ?
[Nexus 5X General] Scarchunk:
I've done this same thing successfully and plan to follow this process for upgrading but I'm waiting on an updated rooted kernel and cataclysm mod. Looks as though the bootloader and modem were also updated with 6.0.1 so I'd flash those as well as the system/vendor/boot images.
[Nexus 5X General] jackdubl:
Also, you should answer no to root in twrp.

---------- Post added at 07:09 PM ---------- Previous post was at 07:06 PM ----------

That's what I do. Flash system.img, vendor, radio(if there is one), and cache. If the previous boot image still works, that's it. Otherwise, you'll also need to flash a new modified boot.

---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------

Can anyone report if the previous modified boot image works with the 6.0.1 build?
[Nexus 5X General] noolis:
Yes.For me works perfectly!
[Nexus 5X General] Scarchunk:
I would imagine that Chainfires newer betas of SuperSU would work fine with the stock 6.0.1 kernel. Version 2.60 and up autopatch the boot.img for root. However I'm waiting on Cataclysm so not testing at the moment.
[Nexus 5X General] solara1973:
His systemless root with the latest SuperSU autopatches the boot.img? I was reading the instructions on systemless root and it says you have to flash the boot.img that he supplies, then flash SuperSU via TWRP? So do you even need to flash the boot.img that he supplies for his systemless root?

http://xdaforums.com/showpost.php?p=63197935&postcount=2
[Nexus 5X General] Scarchunk:
Well I haven't tested but that's how I read it. Read the post with 2.60/2.61 beta attached. He states there that they autopatch the boot image so I take that as meaning you no longer need to flash a boot.img and that it patches the existing kernel.

I have quite a few mods applied via Cataclysm that I don't want to lose or I'd test it myself and let you know.
[Nexus 5X General] bobby janow:
That's not how I read it. I think what he now does is script the boot.img install as a flashable zip which not only installs the boot.img but flashes systemless root as well, i.e the supersu portion. At the same time the script will make a backup copy of your current boot.img file and put it somewhere. Where I don't know but somewhere withing twrp perhaps.
[Nexus 5X General] AJ:
sadly the camera doesn't work after flashing the root boot.img of MDB08M on MMB29K ,

anyone else ?
[Nexus 5X General] Itachisasuke:
same here ;_; I need regular root for AdAway. Its the only reason I haven't gone systemless yet.

Edit: Just loaded the boot.img from the MMB29K build but now it seems like I'm in a bootloop. Going to reflash everything again to confirm it's the modified boot.img from MDB08I/MDB08M causing the camera not to work.

Edit 2: Reflashed System and Boot from MMB29K build which obviously removes system root but the Camera is working again. Looks like we will need a modified boot.img from the MMB29K build for system root to work.

Edit 3: I'd also be happy with a way to get AdAway working on systemless root but at the current state using a simlink and startup shell script is the only way and its a bit messy
[Nexus 5X General] bobby janow:
Camera works on K image and systemless root 2.61

Edit. I just installed adaway and it seems to be working.
[Nexus 5X General] Itachisasuke:
I actually just posted in the SuperSU thread if there was a way to implement the automated boot.img patching utility in traditional root and not just in the systemless root package.

It seems like the camera issue is only a result of trying to use traditional root with previous builds modified boot images.

---------- Post added at 11:45 PM ---------- Previous post was at 10:47 PM ----------

Others are reporting AdAway and TiBU are working on the 2.61 systemless method as well. I am trying it now.

Also if anyone is interested [MENTION=3667193]GROGG88[/MENTION] has a toolset (https://github.com/grogg/mkbootimg_tools) to unpack the boot.img from the latest MMB29K build which will allow you to update the sepolicy file with the instructions found here http://xdaforums.com/apps/supersu/wip-android-6-0-marshmellow-t3219344. You can then repack the boot.img with the modified sepolicy file which will allow the camera to work with traditional root as the newly modified boot.img will be from the MMB29K build.
[Nexus 5X General] reddv1:
Here is the modified boot image for MMB29K

bullhead-mmb29k-mboot.zip (tested working)

The boot image has the following modifications per Chainfires instructions, just like the modified mdb08i boot image:

- patched sepolicy

- disabled dmverity

- disabled forceencrypt

This is for system root.
[Nexus 5X General] rydare:
I flashed everything except boot.img and had the same issue with the camera.

This is fantastic, after flashing this I am able to use the camera and have root. Thank you so much for making it. I was in the midst of trying to make this myself, but couldn't quite figure it out. Is there a guide you use, or could you make one?
[Nexus 5X General] reddv1:
I posted the basic steps for making a modified boot.img in post #177. If you need a more detailed guide, I'll update this post with more detailed steps.
[Nexus 5X General] rydare:
I'm a little confused over the selinux part. I think I am starting to understand though. You create the file by having the correct device attached (so for our 5X we want our 5X attached) and then doing the first command, placing the created selinux file in the tmp directory on the phone. Then you do some magic by doing those commands which modify the file in the tmp directory of the phone, finally you retrieve the modified selinux_out file from the phone to your computer and place it in your new boot.img folder that you will repack after making the fstab modifications and removing that one file.

Does that sound like I get it right? I think the whole selinux bit finally clicked with me while writing this post. Had a tough time understanding that you create the initial selinux file with the first command.
[Nexus 5X General] reddv1:
Yeah that's right, first you get the sepolicy file from the original boot image then you connect the phone, and those commands do some magic and output a new sepolicy file. You replace the old sepolicy file with the new one and do the edits on the fstab file and repack everything into a new boot image.

Also, I think your phone has to be rooted to do those adb commands. Makes you wonder how was the first sepolicy patched with a patched sepolicy? Mind blowing :laugh:! It's the chicken and egg dilemma all over again.
[Nexus 5X General] Confused_Cheese:
Thanks for posting this! Might be worth your own thread in dev? :)
[Nexus 5X General] solara1973:
Can anyone confirm that the systemless root method using the latest SueprSu disables the enforced encryption?

So if I were to go the systemless route, I'd flash the original boot.img, system.img, vendor.img, and boot to Recovery (TWRP). Then I'd flash the latest beta SuperSu,. which would automatically modifiy the boot.img to enable the systemless root with forced encryption turned off?
[Nexus 5X General] Neuromansa:
Hi guys, I don't know if this has already been posted but can anyone please confirm the correct steps to update to 6.0.1 with root and without wiping?

My current system: 6.0 MDB08L with modified boot image and root
[Nexus 5X General] reddv1:
Flash bootloader

Reboot bootloader

Flash radio

Flash vendor

Flash system

Flash modified mmb29k boot image

Reboot into recovery

Flash SuperSU-2.52

Wipe cache and dalvik (optional)

REBOOT

Don't reboot into system until you flash everything.