Develop Bugs

March 2016 Updates Bug

My recent apps button is no longer working. And when I go to Developer Options, I see Developer Options are not available for this user. Anyone else seeing that?

I installed MHC19J first and that was the incorrect version. I then flashed MMB29V and then the problems above started. I couldn't access quick menu, the recent apps button didn't work, and Developer Options showed as not available for this user. I just did a factory data reset and that seemed to get everything working again, but always a pain to have set everything up again! Damn Google! :-/

Probably due to you flashing the wrong image before flashing the correct one. Had no such problems after flashing this morning
Skickat från min Nexus 5X via Tapatalk

I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V

granets said:
I too am on MHC19J , but why is it the wrong image? I actually find my phone working rather well with it, but I guess I will have to wipe and install MMB29V
Click to expand...
Click to collapse
Only do that if you are not rooted etc. If you use TWRP recovery and are not prompted for a password when booting into recovery, then you have the right image. It does work, the problem is trying to use Custom Recovery to flash SuperSU. Check that thread below.
https://www.reddit.com/r/nexus5x/comments/49e0ij/601_mhc19j/

I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.

no issues here on 19J. modified boot image here

bobby janow said:
I just flashed the J image. Installed TWRP 3.0 and got the pin code request. Cancelled it, mounted OTG, flashed SuperSU 2.68, and Osmosis busybox. Rebooted and all looks great. Restoring from Titanium now and Android Pay still works. It really looks like only TWRP needs to be updated. Haven't flashed a kernel yet, I'll let this one settle in for a few days.
Click to expand...
Click to collapse
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?

mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
I'm sorry I don't know. I haven't decrypted in quite some time now. I also haven't used xposed in a long time either. I don't ever format userdata or flash the userdata.img unless I absolutely have to. I'm encrypted, systemless, 2.68 SU and twrp 3.0. I'm leery to do anything now until twrp gets fixed for the J build. Although I might flash a J kernel via OTG if there comes one.

mickey4mice said:
Was your data/storage encrypted before flashing J version? I'm on stock rooted(systemless, v2.6x beta), data/storage DEcrypted, xposed isntalled, TWRP v3.0.0.0. Does flashing J version automatically re-encrypt data/storage?
Click to expand...
Click to collapse
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Unless something has changed, you will be encrypted after first boot (same for prior releases). You'd need to sideload and flash SuperSU before booting since TWRP 3.0 currently cannot access internal storage on MHC19J.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?

mickey4mice said:
I always flash google images sans userdata for every monthly security data, my decrypted data/storage has never re-encrypted itself after first boot before I flash systemless SU via TWRP. But those were done with TWRP v2x, has anything changed with TWRP 3x in this regard?
Click to expand...
Click to collapse
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk

i had some trouble so i clicked the flash all batch file. Anyone know how to root this build? i cant get super su zip file i transfer to show up in twrp. The file is there but twrp doesnt see it.

SlimSnoopOS said:
Are you booting into system or booting into TWRP from bootloader after flashing the monthly factory images?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.

Bump

Dominicano2 said:
I was wondering if someone could direct me on how to put Supersu.zip into the /cache as from what I have read so far it is possible to root on mhc19j you just need to move Supersu there as it is not encrypted.
Click to expand...
Click to collapse
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
They likely used "ADB push" command to move SuperSU from their computer to the /cache directory.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu

Dominicano2 said:
Thanks could you tell me what I am doing wrong I started abd and I do the following command adb push supersu.zip /cache/ and it comes back with Permission Denied
edit: Never mind I booted into twrp with fastboot boot and once there I did the adb push and was able to install Supersu
Click to expand...
Click to collapse
Sweet, glad you got that figured out

How is the new update in terms of making the phone better?

gvsukids said:
How is the new update in terms of making the phone better?
Click to expand...
Click to collapse
Seems like the lag pulling down the notification window that happened time to time is gone. Feels a little snappier but will need a week of up time to know for sure.
Notice that the "keep WiFi on during sleep" setting for "never" still doesn't work on the 5x. Also still have an audio bug that duplicates the source a second behind on Bluetooth when a notification is received which is disappointing.

How to OTA update your ROOTED Nexus 5X

**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.

ionut15 said:
**When i will get all of the information needed,i will edit this thread and make it as simple for reaching the objective for everyone,as possible.**
Recently i got an OTA update for my nexus 5x device,a security patch form june 2017.
I`ve rooted it with this tutorial: https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
My question is: In order to install that OTA i need to follow "11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)" section from Heisenberg`s tutorial or this "9. How To Update To A New Build Of The Stock ROM" section of the same tutorial?.On the "9. update the build of a stock rom" it says no data will be wiped yet this statement of google offical site still concerns me : "Warning: Installing this factory image will erase all data from the device. While it may be possible to restore certain data backed up to your Google Account, apps and their associated data will be uninstalled. Before proceeding, please ensure that data you would like to retain is backed up to your Google Account."
So what`s the safest way to OTA update your rooted device?Please provide some explanations.
Click to expand...
Click to collapse
It is very simple actually. Here's a quick lesson for you to try out. Download any factory image then examine the flash-all.sh script inside the zip. Find the line command that begins with "-w." This command will cause the entire phone to be wiped when the script is executed, as Google highlights.
You can edit and remove the entire -w line to leave your internal storage intact. However, TWRP will be replaced because this script installs each partition including the stock recovery.
I don't believe my guide could be any clearer. Manually entering the commands for each partition, as my guide states, does not wipe the device. With fastboot, the primary ways to wipe the device are: executing the flashall script for a factory image, flash the userdata.img, issue fastboot format userdata, or lock/unlock the bootloader.
Follow my guide to update
Sent from my Nexus 5X using Tapatalk

@SlimSnoopOS thank you,very clear response

ionut15 said:
@SlimSnoopOS thank you,very clear response
Click to expand...
Click to collapse
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Also, make sure to flash root and any other mods BEFORE booting up once you update.
My pleasure! That's why this great place exists and I'm always happy to pass on information that I've learned.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk

I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.

crazyates said:
I always followed this guide here: http://elementalx.org/how-to-install-android-monthly-security-updates/
Here's the quick summary:
Download the newest factory update for your device
Extract all files
Update system boot vendor bootloader radio
Flash whatever root and/or kernel you want.
Wipe cache/dalik
Reboot
Worked like a charm, and only took me ~10 or so minutes once I knew what I was doing.
Click to expand...
Click to collapse
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?

ionut15 said:
Can i ask what are the cons of not doing so? I would flash the factory img that will lead to replacing custom recovery with the stock one and cancelling my root.After flashing it,i asumme that my phone will boot up,so i need to power it off again and proceed to install recovery and root again via adb.How can i install them before the phone will be booting up?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk

ionut15 said:
in the tutorial provided by @SlimSnoopOS at point "11" it says to enter these commands in adb cmd "fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img" but i didn`t get the cache file with the factory.img.So i just skip erasing the cache then flashing it or i have to download from somewhere else?
Click to expand...
Click to collapse
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).

crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you,managed to update the security patch and works just fine.
Sent from my Nexus 5X using Tapatalk

crazyates said:
Cache doesn't matter. In TWRP, if you "wipe cache", it just formats the /cache volume, which is all you'll ever need to do. There should be no need to manually flash anything into the cache volume (it rebuilds itself automatically).
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
It is just a time saving step. If you manually install each partition excluding recovery.img, you can still boot directly into TWRP from bootloader to flash root and now TWRP will persist. This is more relevant on Nougat and newer, this didn't happen on Marshmallow.
Installing a OTA/factory image will always override every partition including TWRP recovery. But if you manually install each image except recovery, upon booting into the phone the stock recovery will replace TWRP. To get root now you will need to: boot into bootloader, flash TWRP, then boot into TWRP to flash your mods afterwards. Make sense?
Please do not erase cache. Skip this step when using Nougat and newer. I have to update this part of the guide.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you again for your time and devotion.You cleared off all of my doubts.Furthermore i hope someone who's in my situation could find this topic helpful.
Sent from my Nexus 5X using Tapatalk

If you want install OTA updates while your device is rooted, use Flashfire.

AFK269 said:
If you want install OTA updates while your device is rooted, use Flashfire.
Click to expand...
Click to collapse
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk

ionut15 said:
its a straight-forward method,unfortunately my system partition was changed and flashfire can't flash ota.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Then flash factory images with adb fastboot commands

device got corrupted

so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
Did you do a full clean flash of the April factory image with wiping userdata intact?

ilal2ielli said:
Did you do a full clean flash of the April factory image with wiping userdata intact?
Click to expand...
Click to collapse
i did dirty flash but it went to android recovery and from there i did the factory reset beacuse it was not booting

Prattham said:
i did dirty flash but it went to android recovery and from there i did the factory reset beacuse it was not booting
Click to expand...
Click to collapse
Your data was already wiped, so you should just go all the way and do a clean factory image flash. It'll probably fix it.

Cleaned flashed on both slots and worked
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Cleaned flashed on both slots and worked
Click to expand...
Click to collapse
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash

elliwigy said:
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash
Click to expand...
Click to collapse
That makes sense
Sent from my Google Pixel 2 XL using XDA Labs

elliwigy said:
typically with that error means your device is failing verification, dm verity, or both. you probably had it disabled but when u dirty flashed it wrote fresh re-enabling dm verity/verificationso when u modified the device with twrp it was corrupted..
next time try to disable verity and verification on both slots and u might avoid a clean flash
Click to expand...
Click to collapse
How to disable on stock ROM?

pa.pn2 said:
How to disable on stock ROM?
Click to expand...
Click to collapse
if u are unlocked you can do it with fastboot and the vbmeta.img from the stock rom your on..
fastboot flash vbmeta_b vbmeta.img --disable-verity --disable-verification
fastboot flash vbmeta_a vbmeta.img --disable-verity --disable-verification
fastboot reboot
Theres also a file or two probably floating around if u can find it that can be done from root terminal or root shell.. the binary is called avbctl.. i cant recall the commands but if u find it and push to your device just type avbctl and it should list the commands.. its something like avbctl --disable-verity avbctl --disable-verification.. this binary will also let you check if they are already disabled or not..
theres also a zip floating around if u can find it.. this zip is flashed in twrp and will disable them for u
keep in mind if u are not unlocked u probably wont even have the disable commands showing in fastboot.. also, you only really need to disable them if u are getting corrupt errors or boot loops.. of course theres also a chance u have another issue entirely but in my flashing craze majority of time for me disablimg fixes my boot issues after flashing firmwares

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
I've had this happened quite a few times it's usually when I go from custom ROM back to stock when I go to update my new month. Almost every time restore a stock backup in TWRP gets me out of it. And if that doesn't work I try flashing stock image to both slots without the w. I'll try disabling that verity thing next time though if I can't get it to work

So, tried flashing resurrection Rom. Had some issues. So, ran a Deuce with latest full stock like I always do. After the flash, getting "Your device is corrupt. It can't be trusted and may not work properly." Now in fastboot can't even run Fastboot commands from computer. Not responding at all to anything
Any ideas?
Edit:
did some more troubleshooting.
Ran from the zip download:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
Then set the fastboot slot a active.
Then was able to boot recovery.img and then reboot.
Somehow the slot must have been changed/corrupt and wouldn't work? Anyway, all working now.

Prattham said:
Cleaned flashed on both slots and worked
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Hi Pratham,
Could you please help me for this?
My phone got stuck in GOOGLE logo and also showing corrupted status on starting.
I just critical unlocked my phone and its happening.
How to do clean flash ?

navi_j said:
Hi Pratham,
Could you please help me for this?
My phone got stuck in GOOGLE logo and also showing corrupted status on starting.
I just critical unlocked my phone and its happening.
How to do clean flash ?
Click to expand...
Click to collapse
Oh so you got a corrupted mssg as well
Here it is
Just download the factory image
And flash it
You will lose all your data but it will work
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Oh so you got a corrupted mssg as well
Here it is
Just download the factory image
And flash it
You will lose all your data but it will work
Click to expand...
Click to collapse
Or he could edit the flash-all, removing the -w to save his data.
Or even flash just the vbmeta image and see if that removes the corrupt message on boot.
No need to resort to the extreme solutions right off the bat!

rickysidhu_ said:
Or he could edit the flash-all, removing the -w to save his data.
Or even flash just the vbmeta image and see if that removes the corrupt message on boot.
No need to resort to the extreme solutions right off the bat!
Click to expand...
Click to collapse
Well that didn't worked for me i had to clean flash so that's why i said it
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Well that didn't worked for me i had to clean flash so that's why i said it
Click to expand...
Click to collapse
But it might work for him/others, so just saying it's probably quicker and more efficient to try less drastic options first.

Prattham said:
so i was on april update with magisk and all
i went into twrp and wiped data and cache and tried to reboot back to system
it got stuck in bootloop so i decided to dirty flash the stock image again, and when i tried to boot it , it went to android recovery saying that my data maybe corrupted and i need to wipe my entire device
so i switch slot and went to slot a and dirty flashed april update, still no luck so i wiped my device when it prompted me and it booted back
so now i wanted to install magisk and booted twrp and twrp booted but i didnt installed anything and just rebooted to system
and it didnt booted and now i get a prompt saying my device is corrputed before that unlocked bootloader prompt and it is not booting
any help please
Click to expand...
Click to collapse
This has happened to me a few times and what i did was boot into bootloader mode and flash the factory image to start over fresh. I know it sucks losing everything but for me it was the only thing that got me up and running again, not even restoring a backup worked

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Phone unrooted itself

This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?

My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.

ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?

DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.

ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.

I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.

Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.

DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on