yashsingh1/xdaforums huggingface dataset:
[Nexus 5X General] stmims1124:
I'm honestly not entirely certain if you'll be able to do OTA's with the boot.img being modified, but I suppose it's possible (because of all of the modifications I had on my 5X, I literally never once actually did an OTA...I always flashed stuff through fastboot and TWRP). However, assuming you were successful in taking an OTA, when you do the update it will of course install the new firmware's boot.img, then it will encrypt upon first boot. It's new boot.img is totally stock, so when it first boots up after installing it will force encryption.

So, my suggestion would be to totally avoid allowing/accepting OTA updates and instead flash the new update manually. You can download the full factory image firmware directly from Google and install everything manually through fastboot. There's a way to manually flash everything without wiping your data, and as long as you flash my boot.img instead of the one built in, it should never encrypt.

My memories a bit foggy on the exact method required for you to manually flash without losing data, but I do recall it entailing editing the included flashall.bat file in the factory image using a text editor like Notepad++. I may be wrong, but I think you edit the line containing “fastboot -w update” by just removing the -w . It's just been so long that I've had to do it, so don't quote me on that - I suggest doing a quick search through the XDA 5X forums, or even just a Google search, as there are a metric f**k ton of posts with instruction to flash the Nexus factory images without loosing data.

With regards to installing the boot.img itself, there's two possibilities here.

Option 1:

Download the new factory image from Google and extract it. In it, there is a second zip (...image.zip). You'll have to extract this "image" zip within, then replace it's boot.img with mine. You'll then repack (re-zip) this "image" zip. This way, when you click the flashall.bat it flash everything including my boot.img, and keep your data.

Option 2 (probably easier, but will require precise timing):

Flash the factory image (again using the method to keep data), and the very millisecond it's done installing, DO NOT LET IT BOOT...immediately do the button combo to get back into the bootloader (fastboot mode), and flash my boot.img. You have to get it right back into the bootloader immediately after the update has been installed, because if you let it boot it will encrypt, which would then mean you'll end up having to reinstall the decrypted boot and wipe data all over again. I can't stress this enough - After the update has been installed, don't let it boot up! Get it right back to the bootloader and flash the modded boot.img.

I hope this helps...and sorry for being so long winded!
[Nexus 5X General] hmillos:
I would really appreciate that :D

Also thanks for the procedure, i'm going to learn it for future emergencies
[Nexus 5X General] stmims1124:
No worries. Here's a link to the 6P's boot.img for 8.0 - forced encryption is disabled as well as dm-verity. Should be just fine, but be advised, I have absolutely zero ways to test this...****, I don't even have my 5X any more. But yeah, should be good.

Angler 8.0 modded boot.img
[Nexus 5X General] stmims1124:
How did that boot.img play out for you...did everything work ok?
[Nexus 5X General] hmillos:
Yes, it worked, although I think the problem was the twrp that i was flashing, after flashing boot image a tried again to flash twrp and the result was the same, ended up flashing twrp 3.1.0.0 instead of 3.1.1.0 and it worked, so maybe i had a corrupt file or the latest version has problems with Oreo. Anyway thank you for your help.
[Nexus 5X General] horeabeni:
Modifed boot.img for Nexus 6P works like a charm

I also used the Nexus 6P modified boot.img and can confirm that it's working perfectly.
[Nexus 5X General] stifmaster81:
the rom oreo with the decrypted September patch is somewhere? since the first page is not
[Nexus 5X General] stmims1124:
Google has only released the one factory image for Oreo, and it is in the OP. One factory image, so only the one boot.img.

Edit: It seems Google can't get their s**t together with the September patch. I'm trying to find it. It's not on their regular page, but a few people seem to have gotten an OTA update.

Edit#2 9/13/17: Google's released the factory image finally, so I'll have the new boot.img uploaded in the OP in a few hours, after I get home from work.

http://www.droid-life.com/2017/09/12/pixel-nexus-september-security-patches-started-think/
[Nexus 5X General] stmims1124:
The OP now has the September update.
[Nexus 5X General] Banan PL:
What's difference between disabled forced encryption and disabled force encryption with disabled dm-verity?
[Nexus 5X General] PESEZZZ:
OPR4.170623.006 8.0 Sept. not working. Both of them. Red dm-verity always
[Nexus 5X General] zurik:
You tried to format internal data to decrypt?
[Nexus 5X General] stmims1124:
While I cannot test myself as I no longer have a 5X, from what I've been told my .imgs are working fine. What steps are you using to flash? There's no info in your post to help trouble shoot...we need details to help you.
[Nexus 5X General] crazyates:
OPR4 works for me. I wiped everything, used fastboot to flash stock OPR4 system, vendor, radio, bootloader, and then this boot.img. Booted into TWRP to install magisk and ElementalX. Everything works great.
[Nexus 5X General] rcmpayne:
[MENTION=2999113]stmims1124[/MENTION], Thanks for the images. We have an edge case where we need to get adb mode enabled in OOBE and I came across this page. I tried to manually modify a boot image, but it didn't work so I then tried yours and lastly I tried modifying your images however, I still can't get it to work. What is occurring is once adb is enabled in the boot image and you go to OOBE, adb shows "unauthorized" and it seems the trust screen does not occur in OOBE mode so you can't accept it.

1. Modify your images to include

ro.secure=1 to ro.secure=0
ro.adb.secure=1 to ro.adb.secure=0
ro.debuggable=0 to ro.debuggable=1
persist.sys.usb.config=none to persist.sys.usb.config=adb

2. Flash the image back to OOBE and start the device in OOBE

3. Open cmd and try adb devices

List of devices attached
01e********a46 unauthorized

Do you know how I can disable verify/auto trust an adb connection in this case without having to accept the prompt?
[Nexus 5X General] rcmpayne:
Looks like i missed adding "setprop ro.adb.secure 0" to init.rc. After doing this on first boot to OOBE, i am prompted to allow the adb connection WOOT!
[Nexus 5X General] stmims1124:
Hey there, just getting on to XDA after a long day to see this. I'm intrigued. May I ask what the end goal was?

Somewhat unrelated note - I miss having a Nexus. :crying:
[Nexus 5X General] rcmpayne:
End goal was to run some setprop commands to enable debug logging and capture logcat of a android for work enrolment flow( used by companies that what to enroll and control devices on a emm server)
[Nexus 5X General] paradoxiumwind:
Since i'm going to do a full format install anyway, should I install one of these? why would I want to use any of them, can anyone say why? does using them stop you from doing anything worthwhile?
[Nexus 5X General] stmims1124:
I started out using them when the 5X was newer and there was a noticeable performance improvement without encryption, although these days Google's mostly straightened that out in real world usage (I stayed decrypted, personally). I started disabling dm-verity in them because some users needed it for some mods to stick, while sticking with the stock ROM & kernel. Also, these were used by folks who had their motherboards repaired by LG after the infamous bootlooping issue...LG was sending phones back purposely blocking bootloader unlocking (w/ the nasty side effect of not being able to play DRM media, ie Netflix, Play Movies) and these are used in the process to temporarily unlock the bootloader so users could still modify their phones and do what they want with them. I just kept uploading them every month because there seems to be people out there needing/wanting them.

Edit: It will not stop you from doing anything. Just know that if you do flash this and decrypt the phone, if you just take a regular OTA the phone will encypt when it first boots up.
[Nexus 5X General] engelchenstg:
Is there a forced encryption disabled of the November update?
[Nexus 5X General] stmims1124:
The November update is now uploaded, link in the OP. Can't update the title of the thread to reflect the new update... It would seem that XDA's editing options are somewhat broken for me.

Anyway, sorry for the delay.
[Nexus 5X General] Swimmercool:
Where is boot with disable forced encryption/dm-verity on OPR6 8.1 DP2? :(
[Nexus 5X General] stmims1124:
It's up now, at the very bottom of the post
[Nexus 5X General] Swimmercool:
Thanks bro :good:
[Nexus 5X General] Swimmercool:
Where is boot with disable forced encryption/dm-verity on OPM1.171019.011?
[Nexus 5X General] PityOnU:
Looking for this as well! WIping and flashing my phone today so would love to see it up soon - especially since it wipes all your data....
[Nexus 5X General] Swimmercool:
take it: https://drive.google.com/open?id=1l_1wONFgVMEgEAyyKpwtBsg6T8Tbxd0Z
[Nexus 5X General] Matoxxi:
where you've found that ?
[Nexus 5X General] Swimmercool:
i maked it myself. Work stable :good: I didnt want to wait and maked it myslef
[Nexus 5X General] stmims1124:
Thank you for helping these folks out. I truly appreciate it. I hate that I'm always a little late with these. Life just...keeps happening. Anyway, 8.1 is uploaded. As always, I don't have a 5X anymore so I have no way of testing, but all should be well.
[Nexus 5X General] Swimmercool:
all right, man ;) no problem. Thanks for your work :good:
[Nexus 5X General] Matoxxi:
used it for almost 24h and it works perfectly
[Nexus 5X General] kain144000:
Thanks [MENTION=2999113]stmims1124[/MENTION], for not only providing the modified boot.imgs for as long as you have, but also providing the instructions for disabling dm-verity and forceencrypt.

Edit: Should have mentioned in-post that the files attached are Feb 2018 opm5.171019.015. Just noticed title doesn't show in-app (xda).

forceencrypt disabled
[Nexus 5X General] kain144000:
Modified Nexus 5X boot.imgs for opm5.171019.015 (Oreo 8.1, Feb 2018), cont...

forceencrypt & dm-verity disabled
[Nexus 5X General] kain144000:
bump
[Nexus 5X General] gregkow:
Compilation number on my nexus 5x is opm3.171019.014. (security pack 05 Feb 2018) Can I use boot.imgs from first page corresponding to previous build (OPM3.171019.013)?
[Nexus 5X General] kain144000:
If you go ahead and update to the latest, Feb 2018 opm5.171019.015, I've modified the boot.img in the two posts preceding yours (prior to my :: bump:: ).
[Nexus 5X General] Xoib:
Newest boot.img for opm5.171019.015

Only DM-Verity disabled.
[Nexus 5X General] stmims1124:
I've been on vacation for the past week without a computer this week. Naturally I've managed to time it for when Google releases an update. I'll be back in two days and I'll of course post to the OP. Thanks for uploading this for everyone
[Nexus 5X General] stmims1124:
Thank you sir!
[Nexus 5X General] :
Many Thanks

Thank you for continuing to crank out new modified images with each months release! You rock! :good:
[Nexus 5X General] kain144000:
OPM3.171019.016, Mar 2018
[Nexus 5X General] kain144000:
[Please remove; updated post below...]
[Nexus 5X General] kain144000:
OPM2.171019.029, Apr 2018
[Nexus 5X General] kain144000:
OPM4.171019.016.A1, May 2018
[Nexus 5X General] kain144000:
OPM6.171019.030.B1, Jun 2018
[Nexus 5X General] kain144000:
OPM6.171019.030.E1, Jul 2018
[Nexus 5X General] ErrOzz:
Hello!

Do I understand correctly that I can lock the bootloader after flashing this kernel, and there will be no problems with Google Pay?
[Nexus 5X General] kain144000:
OPM6.171019.030.H1, Aug 2018
[Nexus 5X General] kain144000:
Opm6.171019.030.k1
[Nexus 5X General] kain144000:
OPM7.181005.003, Oct 2018
[Nexus 5X General] kain144000:
OPM7.181105.004, Nov 2018
[Nexus 5X General] Madfysh:
OPM7.181205.001, Dec 2018

incase someone still need this.

p.s. currently using forceencrypt_disabled_dm-verity_disabled, I didn't test forceencrypt_disabled
[Nexus 5X General] bigrck:
Hello all, a BIG THANKS for maintaining those alternate boot.img :)

I'm just starting to play with one Nexus 5X with unlock state broken (NO RPMB), and this boot.ini save my life and let me install TWRP correctly into one user data partition unencrypted !
[Touch CDMA General] bobo12345:
Has anyone had any luck with the wm6voip.cab file mentioned here:

http://xdaforums.com/showthread.php?t=299950

I can't get it to work - no Internet Calling on my Today screen.

Also, all the clients I've tried: Skype, SJPhone, X-lite, Fring, etc. - I can hear the other party, but they can't hear me. Any suggestions? Thanks
[Touch CDMA General] mbote:
that sounds like problem with NAT. If you're running your own server, ensure you have enabled NAT support on both the server and the client.
[Touch CDMA General] ambush276:
i would like skype to work??? is there any install instructions i can have??
[Android Software/Hacking General [Developers Only]] GuestD0025:
I'm trying to create a backup of the partitions on a Google Pixel C device running CyanogenMod 13 using make_ext4fs. This fails when backing up the /data partition:

# df

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/block/mmcblk0p7 25396556 6235888 19160668 25% /data

# make_ext4fs -l 25396556K -s userdata.img /data

Creating filesystem with parameters:

Size: 26006073344

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 32768

Label:

Blocks: 6349139

Block groups: 194

Reserved block group size: 1024

error: build_directory_structure: unknown file type on misc/wifi/sockets/wpa_ctrl_511-1

Does anybody know what might be the cause of this error?
[LeEco Le Pro3 Questions & Answers] Veidas:
Hey guys, im looking for opinions about leeco and their smartphones, maybe some owners of previous devices? Long story short, i currently own nexus 6p, its a fricking awesome device, but i kinda grew bored of it, and battery life is not that great. I dont want to spend extra money on new toy, but by selling 6p i should get atleast 300euros, and for this money i have few options. Its either le pro 3, mi 5s plus, or 100euros extra for mi note 2. I pretty much know what to expect from xiaomi, but im completely clueless about leeco. Is there any development? I looked around forums of older devices, and they seem pretty dead :( I dont expect same level of development as nexus, but having few options, like miui or cm would be great, cause im already sure i couldnt stand stock rom lol. Also what about customer support? So any input is welcome, also any recommendations of above devices, thank you and sorry for long ass post lol
[LeEco Le Pro3 Questions & Answers] fuzz_33594:
Currently, the bootloader of the US version of the Pro3 cannot be unlocked. There is a lot of negative comments about that on the forum. [http://forum.le.com/us/index.php?threads/unlock-bootloader.3682/

There is a positive first impressions post on the LeEco Pro3 XDA site. I'm conflicted - getting my phone tomorrow.
[LeEco Le Pro3 Questions & Answers] noobsgs2:
I have Le 1 PRO, to be honest it is a gamble. The devices are good but the support is terrible. If someone is not porting AOSP/CM to these devices they will have a very short life.

Le 1 series suffered some major faulty design problems in term of GPS/Wifi and so on. We moved to 6.0.1 only when series 2 came out.

Probably Le 3 series will receive n7.1.1 only after Le 4 series (if any) will be announced/sold, in the meantime you will have countless of useless update (clearly not on the camera since it will be too good).

I've seen some work on Le 2 series, hopefully there will be even more on Le 3 series.

As of now i'm not 100% regretting my choice (270 euros 1.5 years ago for Le 1 Pro) but it is literally a for-geek phone.
[LeEco Le Pro3 Questions & Answers] taphius:
If you just want a top-spec phone to use at a great price the le pro 3 fits the bill.

If you want to tinker, probably any other unlocked phone will work better unless they decide to unlock the bootloader.

I've got no regrets so far for $299 us
[LeEco Le Pro3 Questions & Answers] dr4stic:
If you get bored, but then also want the option of cm, I'm not sure how getting a new device will help you. You can have CM or miui now. And CM isn't exactly a grand departure from AOSP/CAF. It's relatively barebones android. Most phones these days are almost identical slabs. If you're gonna use the same OS as you had before, all you're really changing is the shape. Also, the Nexus is going to be your best bet for tinkering. Nexus or Pixel.

As for support, from what I understand LeEco isn't great when it comes to that. Whatever fashion you receive your device in, expect it to change VERY little. It also doesn't help that reports are popping up that the north american venture is coming up very short. Makes me believe they'll be pulling up stakes and going back to China. With the Pro3 currently locked, I'd say avoid it. If you want a toy phone to tinker with, the S3 might be a better choice. It's cheaper, already unlockable (or so people are reporting, I don't actually know myself), and if it receives any development, then it should be interesting. If you get it for $150, it isn't too much of a gamble.

If I were in your position, I'd steer clear. Especially if you were in the US on T-Mobile and can qualify for a Pixel half off through their promotion. At least that way you'll get wifi calling and some top-notch cameras. Either that or an Oppo. Since you're in europe, I don't know what the alternatives are. At least the chinese version is unlockable (the x720) but there's still the matter of development. And I think that'll be unlikely since CM development usually comes to US models.
[LeEco Le Pro3 Questions & Answers] noobsgs2:
I don't understand why you keep saying the bootloader is locked though, there is a user on this forum that had it unlocked on x727, LeTV also is officially stating on lemall site that the bootloader is unlockable

http://xdaforums.com/showpost.php?p=69507812&postcount=20
[LeEco Le Pro3 Questions & Answers] Veidas:
That option in developer menu does NOTHING. China model can be bootloader unlocked, us model no.
[LeEco Le Pro3 Questions & Answers] Peter-C:
Did you try "fastboot oem unlock" in bootloader? That option just allow you to unlock via fastboot mode.
[LeEco Le Pro3 Questions & Answers] noobsgs2:
Ask directly there to him, im just reporting what i read.
[LeEco Le Pro3 Questions & Answers] benjmiester:
I've seen several folks in the US version discussion thread report that does NOT work, or -go command version either. So far Leeco are being dicks and not allowing it. Maybe an OTA will change that, and they just didn't want it being unlockable right away... No idea yet. I don't really mind the software that much, it's pretty nice, performs well and battery life is excellent expecially standby. But not even having root is quite a deal breaker. I'd return it just on that news but I don't have more money to replace it with anything else since I broke my X Pure that I was going to sell to offset the Pro3 price. Guess I'm stuck waiting for root and roms that so far looks like will never come. Still a great phone though, even signal and GPS are great which were my biggest concerns about it.
[LeEco Le Pro3 Questions & Answers] Veidas:
How is the camera? After 6p im quite spoiled lol. I understand that in bad lightning its complete crap, but how about daylight photos?
[LeEco Le Pro3 Questions & Answers] ericerk:
Pretty crap.
[LeEco Le Pro3 Questions & Answers] benjmiester:
Yeah, not as good as a 6P for sure. It's like most cheaper cameras... Still great in bright light. Indoors not great. Low light, pretty bad. I've seen worse on more expensive phones though. It's better than my X Pure's camera.
[LeEco Le Pro3 Questions & Answers] Jason kiDD:
This phone is great. So far so good. Coming from a GS5
[LeEco Le Pro3 Questions & Answers] Citroon:
Well like everyone else have said so far, the x727 can't be unlocked.

the x720 is quite another story, im sitting with TWRP, rooted and with xposed along with all the other great stuff.

The phone is outstanding quality, full metal unibody and all that jazz.

The Camera is uhm there? but it's overall not the best performer, you can take some nice shots in daylight but that's about it.

i installed a custom version of EUI to remove the bloatware, and i'm currently rocking the leaked pixel launcher on top, so far so good.

The only other rom for this phone is MIUI, which is having some issues (atleast for me) with 4g LTE, it just locks itself onto 3g and HSPA+ :D

My dream is a CM based rom sometime in the near future.
[LeEco Le Pro3 Questions & Answers] Veidas:
Okey so after a lot of doubts i finally pulled the trigger. Stumbled upon a deal i couldnt resist. Aliexpress seller offers full coverage of tax and vat, dhl or dpd shipping, and 240£ for 32gb silver, and 260£ for 64gb gold. I bought 32gb one as i dont need lot of memory. Now the waiting game begins lol. Thanks everyone for imput
[LeEco Le Pro3 Questions & Answers] androFRUST:
Wow that's a pretty sweet deal. Care to share the link? :)
[LeEco Le Pro3 Questions & Answers] Veidas:
http://s.aliexpress.com/I3myqEjU

Vat and tax offer applies to europe and russia only i think
[Huawei P9 Lite Questions & Answers] TheOneWhoSpeaks:
I was thinking. What if :

1.I unlock my bootloader and root my phone

2.Add multi window , double tap to wake and draw gestures

3.Put the stock recovery and unroot

4.Lock the bootloader using the ToolKit.

Is it possible ?

Like....to lock the bootloader and have those features installed without any problems?
[Huawei P9 Lite Questions & Answers] CyberBuddha:
Theorically, if you use elevated privileges to change components/files of the os, then you drop the privileges (unrooting - relocking) this shouldn't be an issue. But bear in mind if you apply edits that run through privilege elevation constantly and you remove that capability you won't able to benefit of your mods.
[Huawei P9 Lite Questions & Answers] TheOneWhoSpeaks:
Update :

Locking the bootloader when i apply those mods, the phone gets locked( red allert)
[LG V20 Questions & Answers] martinm123:
I have an issue I'm hoping someone can help me with. I'll try to keep it brief.

I rooted my phone, successfully, but in the process the phone app mysteriously disappeared, not sure why. I download the stock apk's from 'theandroidsoul.com/download-lg-v20-stock-apps/, and dropped the phone app into the system app directory, set the permissions, and rebooted. Yes, I know that was probably pretty stupid to try.

Anyway, I can't access the UI as the constant, endless crash caused by com.android.phone. Phone OS is done, so I attempted to get into recovery, re-flash, no big deal.

In previous LG phones, to access recovery via the hardware buttons, you had to go through a menu that made it appear your phone would be factory reset, but wouldn't, and bring you to TWRP after selecting 'yes'. Except with the V20, it actually does reset your phone. USB debugging, disabled now!!

So I can't find out how the hell to access recovery from the hardware, USB debugging is disabled so I can't adb push recovery files, can't access UI, and every fastboot command I run returns 'remote:unknown command', probably due to the USB debugging authorization being revoked.

I know I got myself into this mess, I tinkered too much, and I realize it was an amateur move.

My question is, how can I get out of this? Can't use LG flashtool as I don't have relevant .dll. Can't access recovery (so far; I've tried 50x). Can anyone help? Do I just need to wait for LG to release TOT / KDZ files?
[LG V20 Questions & Answers] martinm123:
One clarification - when I select the option to factory reset via the hardware button menu - TWRP actually performs the wipe. So its on there. It just resets it and reboots. I can't get into TWRP!