yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] stmims1124:
Sorry for the late response. What build version were you coming from? Did you wipe or only flash like the boot/system/vendor/radios? I came from the DP2 and I heard there was issues for some folks so I did a clean install coming from the DP to the official 7.1.1. Tested this out for a while, flashed EX kernel for a bit, and tested it out again for a few hours today after you posted your comment. I haven't had any issues w/ radios or reception at all.

I don’t doubt you’re having issues, but just because 2 people have the same issue w/ reception doesn’t mean that it’s definitely modified boot.imgs. It’s DEFINITELY NOT decryption. In that thread you mentioned flashing the stock boot.img to fix it. Did you flash the boot from that ROM or from the Google factory image? That ROM’s boot.img has forced encryption disabled as well. In the off chance that my boot.img w/ dm-verity removed gave you this issue, then why not just use the my link for the one that only has encryption disabled?
[Nexus 5X General] Xami:
I was coming from DP1 but I wiped everything, now I'm on EX kernel but I haven't decrypted, what should I do?

tried clean flashes many times with modified boot img yesterday and signal kept dropping each time

I flashed stock 7.1.1 boot img in order to fix it AND I tried using the one that doesn't have dm verity removed, with clean flash everytime I flashed "On;y forced encryption disabled boot img" phone doesn't go past firt boot, stuck on bootanimation.
[Nexus 5X General] stmims1124:
I'm not certain what's causing the problem for you yet, but I can tell you my steps for installing (I wipe this phone a lot lol). If you're looking to decrypt the phone on the official 7.1.1, first back up everything you can becasue it is going to wipe the phone completely. If you're ok with wiping it, then download the NMF26F boot.img w/ decryption disable & dm-verity disabled in the OP (I even downloaded it from my own link this last time, I know it works).

You can just flash the full NMF26F factory image using the flashall.bat, then as soon as it finishes flashing hold the volume down button to boot into the bootloader...don't even bother letting the phone boot for the first time (it encrypts upon that first boot). Then flash my boot.img, fastboot format userdata, fastboot format cache, then flash TWRP in fastboot (flash TWRP twice actually), then boot it up. You should be just fine.
[Nexus 5X General] Xami:
Just did exactly what you said except the flash all it wasn't working I don't know why kept saying boot.sig recovery.sig not found, flashed manually everything then flashed your boot then formatted userdata then formatted cache and now phone is stuck on google logo where it shows a lock unlocked that bootloader is unlocked

apparently system.img isn't flashing after showing sending system sparse for 5 times it then says data too large send failed or sth

did that all again flashed your boot and now its stuck on bootanimation

EDIT: formatted data in twrp this time, phone booted up. Thank god its decrypted and radio is working fine as well
[Nexus 5X General] stmims1124:
I would love to know what caused that. I'm really glad to hear you got it working.
[Nexus 5X General] Xami:
well flashed everything manually then formatted userdata and cache which caused something wrong, then erased everything, flashed again only system and vendor and your boot and cache. then went into twrp and formatted userdata from there and booted right up, thanks for the help man
[Nexus 5X General] WhatNameIsntTakenyet:
Thanks for uploading. The build number 95D91L should read N5D91L, correct?
[Nexus 5X General] stmims1124:
You are abolutely correct...thank you for catching that. It is the second update for November, N5D91L. I've fixed the typo in the OP. My apologies for any confusion.
[Nexus 5X General] Xoib:
Using your boot image NMF26F 7.1.1 only because I need dm-verity disabled (and not being rooted).

Works perfectly! Thank you very much! I wish I had known this thread earlier though.
[Nexus 5X General] stmims1124:
Happy to be of assistance ;)
[Nexus 5X General] stmims1124:
New January security update was released today (N4F26I). I should have the new boot up at some point this evening.

http://source.android.com/security/bulletin/2017-01-01.html
[Nexus 5X General] melphoi:
Sorry for taking you back few pages back, but I interested in your post about the warning messages, and by coincidence I realized that there are 3 type of warning messages.

I like to flash some roms just to give them shot on my daily usage, then flash back to stock using factory image.

But never I face the yellow warning one, each time I unlock the bootloader it always give the orange one.

Did u get the orange one when you unlock the bootloader in stock ?

My steps when back to stock is flashing all the image (except userdata) then lock the bootloader.

While my steps for going on custom rom are : flashing vendor > the rom > gapps > kernel > root.

I never tried your modified boot.img yet, but maybe you can enlighten me about this warning message.

Thanks in advance.
[Nexus 5X General] stmims1124:
I made a mistake when I wrote that originially. The orange notification is normal, and happens when the bootloader is unlocked-unfortunately we are all just stuck with that until it's relocked. So to answer your question, yes, it is the orange notfiication. I haven't actually seen the yellow waring in real life, but it says your device has loaded a different operating system. I have only seen the red warning the first day I had this phone, when something went wrong, I think during the process of flashing some kernel...I can't remember what it was specifically that caused it though.

If you follow the link beofre the warning ( g.co/ABH ), it takes you to a page about "verified boot" that explains the warnings a little bit.

https://support.google.com/nexus/an...5899302271929-3366571412&p=verified_boot&rd=1
[Nexus 5X General] smohanv:
This is very very handy. Thanks.
[Nexus 5X General] stmims1124:
For whatever reason Google took a few days to get the new Beta preview up for the 5X, but it is rolling out today via OTA and the factory image is available online now, for any crack flashers out there. Assuming that there hasn't been too much changed within the boot.img, I'll have the new one up for NPG05D late in the day today. I've read on one or two sites that this update includes the Pixel's fingerrpint gestures in the "moves" menu (I'll believe it when I see it on my phone). Other than that just bug fixes, and I'm sure their will be a few new bugs (this is the first beta, after all).

https://developer.android.com/preview/download-712.html
[Nexus 5X General] suku_patel_22:
Waiting for your update. Thanks for doing it every single release
[Nexus 5X General] stmims1124:
You are most welcome. The new boot.img was uploaded a couple nights ago...You can find it at the bottom of the OP.
[Nexus 5X General] rmead01:
any chance you take custom requests? I dont know how to compile kernels but I'm searching the the stock 7.1.2 with just audio tweaks commited in. The stock aux output is so low, using custom kernels to bump the gain by 1 but I really want to run the stock kernel on this beta.
[Nexus 5X General] stmims1124:
I will do some research and see if I can figure it out. I still have a lot to learn, but I don't imagine it will be too terribly difficult. I'll let you know if/when I get it figured out.
[Nexus 5X General] stmims1124:
March Security update .imgs are now up in th OP
[Nexus 5X General] ScumDroid:
Any reason im still seeing that irritating DM verity triangle after flashing? Is it because bootloader is still unlocked?
[Nexus 5X General] stmims1124:
As long as you the bootloader is unlocked, you will always get that notification and there is just no way around it. I miss the old Nexus days where we didn't have to screw around with boot.imgs to flash kernels on like and there wasn't any damn warning notifications, simply the little unlocked padlock logo at the bottom of the Google screen on my Galaxy Nexus.
[Nexus 5X General] ScumDroid:
Yeah mate. Its annoying. Thanks for replying.
[Nexus 5X General] suku_patel_22:
As usual we wait for your update ?
[Nexus 5X General] vanpra:
How do you disable dm-verity in the boot.img just out of interest?
[Nexus 5X General] stmims1124:
I got you ;) New developer preview (NPG47I) imgs are uploaded - links are at the very bottom of the OP. Now, about this surprise Android 0 release...I know people have not been able to successfully root it as of yet, but maybe the boot.imgs are not too different and I'm hoping it'll be easy to keep decrypted. I'm not going to rush that into the OP until I know everything's working right.

Edit: Don't forget to hit thanks fellas!
[Nexus 5X General] stmims1124:
Once the boot.img file has been extracted (like with the Android Image Kitchen I have linked in the OP), It's simply editing 2 lines. Within the ramdisk folder resides the fstab.bullhead file (file system table). Lines 6 & 7 are edited so that everything after the word "wait," in both lines is deleted. It's super simple, and I can't take any credit for any of this. [MENTION=5317224]Tigerstown[/MENTION] showed me what to do, I simply just do it for any new firmware to make it easy for people who want stock kernels and want to keep decrypted and/or dm-verity disabled. See below-

From this:

/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1,inode_readahead_blks=8 [B]wait,verify=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata[/B]
/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,barrier=1,inode_readahead_blks=8 [B]wait,verify=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata[/B]

To this:

/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1,inode_readahead_blks=8 [B]wait,[/B]
/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,barrier=1,inode_readahead_blks=8 [B]wait,[/B]
[Nexus 5X General] Aragur:
Any boot.img for Android O Developer Preview 1?
[Nexus 5X General] stmims1124:
Yup, I've been testing out O today. I'll have it uploaded this evening when I'm home from work.
[Nexus 5X General] zurik:
I flashed recently the modified boot with forced encryption disabled, but in Security section in Settings and in Encryption says that is encrypted... I flashed via TWRP first time, but with luck to have the red warning that device is corrupted and stuck at bootloop. (Thanks god that is not a HW issue but my fault :angel::angel: )
[Nexus 5X General] stmims1124:
I flashed it coming from a clean install of 0 without any issues. Did you format userdata after you flashed the boot.img? You have to format it to decrypt it. Also, I personally suggest using fastboot to flash it, however I've never had an issues with TWRP. That being said, Android O is new territory and I'm sure not everything is going to work the same, like root for instance.
[Nexus 5X General] zurik:
I used stock boot[.]img (factory image) and flashed over TWRP the decrypted boot[.]img and caused corruption for some unexplained reason. Then I reflashed factory image again with this time using the modified boot. And then I checked into security section that says is encrypted like stock. There's no second option to change password, like that I have bought from tech shop and turned on for first time. (I don't know if when I flash the modified boot[.]img change the "encrypted" to "Click to encrypt") I am using 7.1.1 M4F26T boot[.]img
[Nexus 5X General] Xdevillived666:
Will this allow us to flash zips in twrp on O?
[Nexus 5X General] rekids:
Flashed the modified boot and a custom kernel for the NPG47I (DP2) w/ forced encryption and dm-verity disabled, can use root explorer to add or remove files as well as rename is /system and sub folders but permissions won't change or copy over.

Thought that was part of the dm-verity? Is there something else that is preventing this?
[Nexus 5X General] stmims1124:
The 7.1.2 official is up
[Nexus 5X General] stmims1124:
So sorry - work has been killing me and I've been away from XDA for a bit. That's strange...I have yet to have any issues adjusting anything in system folders. Were you able to figure it out?
[Nexus 5X General] rekids:
Was able to change in terminal from recovery, but root explorer still can't change permissions for anything in the system folders.
[Nexus 5X General] Xoib:
7.1.2 (N2G47O, May 2017) with dm-verity disabled

I did the boot.img for 7.1.2 (N2G47O, May 2017) with dm-verity disabled : Link

MD5 : f0b382572bd5c4e30a1f292f5c086dc4
[Nexus 5X General] kurtafterjim:
Hi and thanks for all!

Some weeks ago I've installed the version N2G47F 7.1.2 and follow all steps, without problem. Last week i received the security update, but when the system try to intall it, it crash. And now, at every reebot, the update starts and crash.

Is there a way to resolve?

Thanks
[Nexus 5X General] mgy1912:
Hi, thank you for the great work. I wanted to know if this thread will be updated with the next images. I use those as the only way to get root permissions on my 5x and I'm waiting for May build with forced encryption disabled. Thanks again!
[Nexus 5X General] agarciagonz:
No cache file

Hi

I have downloaded de factory image N2G47F 7.1.2 and there is no "cache" file.

Should we flash everything as usual but without the cache file?

Thanks
[Nexus 5X General] Xoib:
I did the May build with dm-verity disabled, next builds I will do also one with forced-encryption disabled (now that I know someone is interested).
[Nexus 5X General] mgy1912:
Thanks for the link, but as I read on the OP the boot.img with dm-verity disabled will cause SuperSU to crash when flashed, and I'm looking for that modified boot.img only to have root permissions on my Nexus 5X. I tried to unpack a stock boot image in order to modify it by myself, but I'm still trying to figure out what I really need to change to disable the forced encryption. Can you help me with that? I'm pretty curious on how to do it
[Nexus 5X General] stmims1124:
Hello everyone. I am so very sorry I've been away from XDA for so long...please forgive me. I won't get into my boring life details, but everything's cool now and I'm back online. My sincerest apologies to anyone in need of answeres or updated images. That being said, I just uploaded images for May's firmware (N2G47O), as well as for the new O DP2 (OPP2.170420.019) - as always, there are both boot.imgs that simply have forced encryption disabled then you can also find ones with both forced encryption disabled and dm-verity removed. You;ll find them in the updated OP.

I hope I didn't screw anyone or piss anyone off by being gone for a bit.
[Nexus 5X General] stmims1124:
Thank you for stepping up and helping out during my little hiatus. THANKS!
[Nexus 5X General] stmims1124:
What I said in the OP was that going from an img that only has encryption disabled to one that also has dm-verity disabled will causes SuperSU to fail when the SuperSU zip script gets to patching sepolicy.

To disable forced encryption, all you'll need to do is unpack the stock boot.img from the factory image and edit just one word (using perhaps Android Kitchen Kitchen, if you're using Windows). Aside from the Android Image Kitchen (link and credit in OP), you'll need a text editor...something better than notepad - I suggest Notepad ++.

Drag the stock boot.img file pulled from the factory image over "unpacking.bat" within the Android Image Kitchen folder. This will automatically unpack the boot.img. Once it's unpacked, open the newly created ramdisk folder, and locate the fstab/bullhead file. Right click on this file and select "Edit with Notepad++".

To disable forced encryption, you are literally changing only one word. In the 8th row down, locate where it says forcefdeorfbe. All you have to do here is change this word to encryptable.

Original:

readahead_blks=8 wait,check,[B][COLOR="Red"]forcefdeorfbe[/COLOR][/B]=/dev/block

To this:

readahead_blks=8 wait,check,[B][COLOR="Red"]encryptable[/COLOR][/B]=/dev/block

Afterwards, simply click save in Notepad++ and exit. Go back to the Android Image Kitchen folder and double click "repacking.bat", which will repack (compress) the boot.img and it's ready for use. Of course, for encryption to now ACTUALLY be disabled, you'll have to flash this in fastboot, and assuming you aren't already decrypted you will have to follow it with the "fastboot format userdata" command, as well as "fastboot format cache". Without the userdata wipe the phone will encrypt itself upon first boot. Of course it's a pain the ass because it wipes all user date, unlike a regular wipe in TWRP, but it is what it is.
[Nexus 5X General] stmims1124:
I am so incredibly sorry for being absent so long. New boot.imgs are up! 7.1.2 May security patch and the Android O DP2 are up in the OP.
[Nexus 5X General] stmims1124:
I've been away from XDA for a bit so I know my response is extremely late, but figured I'd check in. Is your phone stock other than (obviously) having an unlocked bootloader or this modded boot.img? Even something as simple as having TWRP installed will make it fail. I don't think dm-verity being removed would casue it, but to be honest I'm not 100% certain. I strongly suspect your phone was not stock, in which case installing an OTA isn't going to work. Aside from using fastboot to flash just parts (or all) of the factory image, you're only other option in this case would be like Flahfire or Flashify.
[Nexus 5X General] stmims1124:
Super, suuuuppperrrrrr late...but they're now up in the OP! Life intervened recently which led to me not being on XDA for a while, but I'm back for good. Up until this month I was uploading these imgs the very same day Google released factory images. I still plan on updating the very same day Google drops the factory firmware images for future updates. I will not allow such a delay to occur again.
[Nexus 5X General] stmims1124:
Another month passed, another security update in the OP
[Nexus 5X General] Aragur:
When will O DP3 be ready?

Or do you have any guide that i can port it by myself?
[Nexus 5X General] stmims1124:
It's up now ;)
[Nexus 5X General] kurtafterjim:
Hi, thanks for your response. What do you mean with "your phone was not stock" ?

I don't understand if I can update via OTA when my phone have unlocked bootloader.
[Nexus 5X General] UszkiX:
What gives me forced encryption?

Wysłane z mojego Nexus 5X przy użyciu Tapatalka
[Nexus 5X General] stmims1124:
I'm not quite sure I understand your question exactly. The phone encrypts itself upon booting for the first time - these files can just help you prevent that.

In unrelated news, there's a new update in the OP-N2G47Z July security update.

I no longer have a Nexus 5X, but Android O hasn't changed anything for the purposes of this thread and the modification is so small, so I shouldn't have a problem continuing the thread. I'll keep it going as long they update the phone, if people are using these.

I've moved on to a super locked down carrier branded S8. The S8 is sweet, but no one has been successfully rooted the Snapdragon models as of yet...I do miss having a phone with such active development :crying:
[Nexus 5X General] stmims1124:
The Android preview 4 boot.img is up in the OP. I have not tested them because I no longer have a 5X, but it's so stupid simple to do this and nothing pertaining to this has changed has changed in the fstab file, so it should work just fine.
[Nexus 5X General] robetx:
It's working well...In DP4. Decrypted
[Nexus 5X General] AddieBaker:
Can you please share the method used to achieve this? I'd love to learn this. Perhaps a guide? Thanks.
[Nexus 5X General] stmims1124:
Download Osmosis' image kitchen that's lined in the OP, and download whichever version of the firmware you are using and extract the zip. Then extract the "images" zip within that...that will give you the boot.img and a couple more imgs. Extract the image kitchen, then just drag the boot.img over the "unpacking.bat" file in the image kitchen folder. If you click and drag the boot.img right over the unpacking.bat file, it automatically unpacks the .img so you can do whatever you want to it.

Using a text editor like Notepad ++, you can open and edit the text within the "fstab.bullhead" file, found in the "ramdisk" folder. Take a look at this post to get rid of dm-verity. You remove some of line 6 & line 7...just delete everything after the word "wait" in both lines.

https://xdaforums.com/showpost.php?p=71532221&postcount=71

To remove forced encryption, it's just changing the word in line 8 "forcefdeorfbe" to encrpytable". Save, exit and double click the "repacking.bat" file to repack it all, which will create a new image for you to use.

Edit:You can see the fstab file in Notepad ++ in the attached picture. I've highlighted all that needs to be edited. It's actually really easy.
[Nexus 5X General] pirosoft:
Hi

I can't decrypt my 5x with Rom Resurrection Remix patched August even i flashed first the boot image N2G48C 7.1.2 August

are you sure this boot.img is working ok?

I did..

fastboot flash boot boot.img

fastboot format userdata

fastboot format cache

and reinstallaed the rom, gapps, vendor image

but is still encrypted :(

please help me.
[Nexus 5X General] stmims1124:
I'm so sorry I'm seeing this message so late! I had notifications for this thread turned off somehow. When you install the ROM, the ROM is installing it's own boot.img over the boot image you flashed, and it's not decrpyted. To make sure I was right, I just downloaded the ROM and opened up the boot.img file to make sure, and that's definitely what's happening - in it's fstab file, it says "forcefdeorfbe:", which needs to be changed to "encryptable". You would need to install the ROM, then flash my boot.img, and of course the formatting process (which can pretty much all be done in TWRP, I just never liked the idea of using TWRP over fastboot & adb).

You can also modify Resurrection Remix's file yourself, if you want to stick with it's kernel. My previous post explains the process briefly. If it's bit confusing, you can PM me and I can walk you through it sometime, or I can upload a link of that ROM's boot.img with forced encryption removed.

In other news...ANDROID 8.0 OREO IS HERE. New boot.img is up. Of course, this will only work with the stock ROM until custom 8.0 ROMs are released.
[Nexus 5X General] hmillos:
Sorry for the offtopic guys, but search hasn't helped much... Do you know of a similar thread to this but for the 6P, i need a modified boot after i flashed Oreo and it removed my recovery.
[Nexus 5X General] stmims1124:
[MENTION=5317224]Tigerstown[/MENTION] had a thread for Nougat, but I believe that has been closed, with no updates for O. I'm confident it requires the very same simple method he taught me to make this page. I have some instructions a few posts up that briefly detail how to make one.
[Nexus 5X General] stmims1124:
If you want, I can make one this evening from the new factory image. It won't be for another 9-10 hours. Or I can show you how to do it. In simplest terms, it's changing one word in the fstab file and repacking it back up.
[Nexus 5X General] pirosoft:
Thank you for your kindly reply!

Actually, before you told me this... i replaced the boot.img on the Resurrection Remix .zip file with the boot.img present here on the first post, but It doesn't work.. it goes in bootloop.

I will try to modify the ROM boot.img with the instructions you told me and I will let you know..

Thank you very much for the support. You've been great!

Cheers!
[Nexus 5X General] teodargent:
If I flash the modified boot.img will I be able to receive and install future OTAs? If yes, do I have to reflash the modified boot and wipe the storage everytime I install a new OTA?