Develop Bugs

Unable to mount partitions after flashing TWRP on Nexus 7 (2013, WiFi, flo)

I just bought this device a week and I haven't even rooted I wanted to install Cyanogenmode and follow through the instructions and flashed TWRP through fastboot commands from Windows7 using Minimal ADB and Fastboot [8-28-15].
I got the TWRP recovery but I am not sure what have I done wrong, when I am in the TWRP recovery, it does not show any partitions so I am unable to install any ROM on it.
I have also tried to use this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562 when I flash the given recovery from fastboot commands from this thread, the recovery get stuck with bootloop. So then I restored it back to the original TWRP 2.8.7.0.
So at this point now I can only access bootloader and the recovery which does not show partitions.
At this point Is it possible for me to go back to the stock ROM somehow? Please advice. Otherwise I might be able to return it because I have only bought it few days ago.
SOLVED: To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/androi...s/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/dev...o_20150630.img
This allowed TWRP to work.
Thanks to Batfink33 and lynnux

You can follow this guide to flash the newest factory image: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/. You should just download the latest factory image from: https://developers.google.com/android/nexus/images?hl=en the one in the guide is outdated.

Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.

lynnux said:
Join the club, I did the same thing you did with the same results(even flashing the multirom twrp after flashing the regular one, and getting the recovery bootloop). I happened to find the same instructions theminikiller posted above after pulling my hair out trying to figure out what went wrong.
This post http://forum.xda-developers.com/showpost.php?p=62275723&postcount=558 explains what's going on. If you do the above and then flash the multirom twrp it should work fine, it did for me. I also reformatted system in adb after erasing everything, not sure if that was necessary or not.
Click to expand...
Click to collapse
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.

Batfink33 said:
Did the multirom TWRP work for you? I get a bootloop in TWRP when I flash that multirom TWRP posted.
Click to expand...
Click to collapse
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).

lynnux said:
It worked for me, but only after erasing everything via adb and reflashing all the stock images. I got the bootloop when I flashed the regular twrp first, then the multirom twrp. Also, I'm using the most recent multirom twrp from June (I believe).
Click to expand...
Click to collapse
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!

Batfink33 said:
Yay, it works for me now. I had to install the stock ROM using adb then flash the multirom TWRP. Thanks!
Click to expand...
Click to collapse
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice

a4abbas said:
Thanks for your replies here. Could you please give me the link to the multiroom Recovery that had worked for you? Also did you installed Cynageon mode after getting the mutliroom TWRP working? Please advice
Click to expand...
Click to collapse
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.

Batfink33 said:
To get TWRP to work, I flashed the original stock ROM from here https://developers.google.com/android/nexus/images?hl=en using adb. I then flashed this TWRP multirom https://s.basketbuild.com/filedl/de...//multirom/flo/TWRP_multirom_flo_20150630.img
This allowed TWRP to work.
Click to expand...
Click to collapse
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice

a4abbas said:
Is it required to enable Developer options at some point of flashing it successfully? I am in China and here the google is blocked i bought this tablet and I can not get through the first screen that ask me to connect the wifi (no option to skip it unless i connect to wifi) then after loading it gets error message that it is failed to connect to internet. So just understand that I can not goto the device options right now. So is it possible to flash cynagonmode rom without enabling developer option. Please advice
Click to expand...
Click to collapse
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.

theminikiller said:
No, it's not required. Just turn off your device. Then to boot into the bootloader hold volume down + power button until it's done booting. From there you can follow other guides to unlock the bootloader and installing custom recovery and Rom's.
Click to expand...
Click to collapse
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?

a4abbas said:
I have tried to do it. But the device is not being recognized with the ADB tools on my PC. Any ideas? Could it be because of the USB debugging option?
Click to expand...
Click to collapse
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.

theminikiller said:
When you are in the bootloader it doesn't matter if you have USB debugging enabled or not. It could be a problem with your driver's.
Click to expand...
Click to collapse
You must be right, it make sense.

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

Official TWRP recovery has been added for Le Pro 3 zl1

http://www.androidpolice.com/2017/0...eco-le-pro-3-android-one-4th-gen-xiaomi-mi-6/
Here is the link to the TWRP recovery for this device: https://twrp.me/devices/leecolepro3.html
I download the recovery image file and flash it via TWRP app that I downloaded from the google play store. It works good.

I went back to complete stock, non root, lock boot loader, same as new phone. Can i install this and still be able to use Android pay and other stock stuff like HD calls.....?

sweetboy02125 said:
I went back to complete stock, non root, lock boot loader, same as new phone. Can i install this and still be able to use Android pay and other stock stuff like HD calls.....?
Click to expand...
Click to collapse
As I understand it you cannot have a locked bootloader when using TWRP. Correct me if I'm wrong anyone.

WhiskerBiscuit76 said:
As I understand it you cannot have a locked bootloader when using TWRP. Correct me if I'm wrong anyone.
Click to expand...
Click to collapse
Correct
Disclaimer - although theoretically feasible, relocking it after flashing twrp is a sure way for a common user to brick their device

You can unlock bootloader and install TWRP. But, I think you can't use android pay, because of google safetynet. Correct me if I'm wrong.

crazy1990 said:
http://www.androidpolice.com/2017/0...eco-le-pro-3-android-one-4th-gen-xiaomi-mi-6/
Here is the link to the TWRP recovery for this device: https://twrp.me/devices/leecolepro3.html
I download the recovery image file and flash it via TWRP app that I downloaded from the google play store. It works good.
Click to expand...
Click to collapse
Thanks a lot for your brother advice, it helped me a lot to be able to update to the latest version. Thanks, let's keep running 100% ... Regards.
Note: I am using a translator in case my inlges is not understood ...:good:

I have a question, what is different in this twrp instead of the old one? What's new? Or what features it brings?
Thanks

motanel_pufos said:
I have a question, what is different in this twrp instead of the old one? What's new? Or what features it brings?
Thanks
Click to expand...
Click to collapse
good. One difference would be that you no longer have flashes on the screen !! A part that feels much softer to do the swipe ... !!

When I'm trying to install the twrp.img in recovery mode TWRP it ask select partition to flash image - boot, system image, recovery.
Which is the right one.
Thanks

motanel_pufos said:
When I'm trying to install the twrp.img in recovery mode TWRP it ask select partition to flash image - boot, system image, recovery.
Which is the right one.
Thanks
Click to expand...
Click to collapse
Flash twrp.img to recovery partition

amdol said:
Flash twrp.img to recovery partition
Click to expand...
Click to collapse
do you have twrp for le pro3 elite x722? or it use same twrp?

TWRP 3.2.3-1 for Pixel 2 XL

Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/

Reserved!

Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?

Hurray for progress!

fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478

This makes me smile. Thanks Troy and TeamWin!

Thanks Dees_Troy and Team for getting this started!

Things are looking up, thanks guys!

Awesome to see action with this phone! Thanks!!

You da man

sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.

Nice! Great to see the progress

Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324

sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?

cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs

Great to see...this is the start!

I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.

bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?

I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!

chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs

[Q] Can't access to TWRP Recovery

Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.

RegularSam said:
Hi guys, sorry if posting another thread about this problem, but I haven't found anything useful for my case. The problem is I can't boot in recovery. I flash the TWRP img (latest version but I also tried with others) and the process goes without problems, then I DON'T reboot the system or even power off the phone, I directly send the command via command line (adb-fastboot) or via phone to go to the recovery. It seems to work at first look, but before the recovery starts the phone reboot and goes in OS. Now, could the problem be related to the BLOD bug of this devices? I applied the 4core fix for my OS version (January security patch) but I also seen that on the XDA thread they uploaded the 4core version recovery img so maybe the problem is due to this bug which prevent me from enter in the recovery, probably I'm just saying a bunch of stupid things.
Last information: the only way I managed to enter in TWRP recovery was by doing this on fastboot:
fastboot flash recovery recovery.img
fastboot boot recovery.img
But now even this method won't work.
Thanks in advance.
Click to expand...
Click to collapse
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hmm, wait, maybe I didn't catch what you were sayin, with "try to look your bootloader" you meant "try to LOCK your bootloader" right?
Because yesterday I've made root with Magisk, if I try to lock the bootloader I risk to brick the phone, isn't it true? Thanks anyway for your reply.

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found the trick. I applied from fastboot the two commands that I mentioned:
fastboot flash recovery recovery.img
fastboot boot recovery.img
Only difference? I didn't run the Command Prompt as administartor, as I did yesterday (I also tried before this operations using PowerShell without success), WOW. Now before reboot the phone I allowed the modification to the partition in TWRP recovery, I saved logs from kernel and recovery and I'm trying to make a backup. I will tell you the results.
Yesterday I've also tried to flash the recovery by using Flashify without success, just sayin.
EDIT:
After rebooting the stock recovery returned. I hate this thing. I've also renamed this two files:
recovery-from-boot-p
install-recovery.sh
It didn't work.

jd1639 said:
What happens if you try to look your bootloader, fastboot oem lock, and then boot back into the bootloader. Is it locked? Or does it stay unlocked?
Click to expand...
Click to collapse
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.

RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse

Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.

CazeW said:
Or, as you are already rooted, you could just try flashing TWRP from the official TWRP app. That should make it stick.
EDIT: Just noticed that you've already tried with Flashify. You could still try with the official app but if that doesn't work, do what jd1639 said.
Click to expand...
Click to collapse
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?

RegularSam said:
I've already tried with the official app and unfortunately I had no success. Anyway, as I said before, by locking again the bootloader couldn't occur a bootloop due to the root?
Click to expand...
Click to collapse
Locking the bootloader will not cause a boot loop if you're rooted. The reason I asked what happens when you lock the bootloader is that the 5x had had issues with the emmc going bad. A sure sign of that is the bootloader not staying locked after locking it and booting back up.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
RegularSam said:
Any thoughts? Sorry if I ask but this problem is stopping me from go further with modifications on my device, I would like to install the ElementalX kernel.[/QUOTE
From the bootloader boot recovery (twrp), fastboot boot twrp.img. Then flash supersu in twrp. Then boot back into the bootloader and flash twrp, fastboot flash recovery twrp.img. Twrp should stick then. Note: twrp.img is the full name of the twrp image file you're using.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Seriously, this thing is driving me crazy. Tried to go with your suggestions but I can't boot in the recovery, no way. I have also flashed the original recovery and the tried to get in with fastboot boot twrp.img, no success. I can't figure out why I have this problem.
EDIT: great, now even flashing the stock recovery doesn't work, the phone reboot every time I try to get in any recovery. I have no words.
EDIT 2:
GUYS, I think I've found the solution. As I said in the main post, I was thinking that maybe the problem was due to the BLOD bug, in fact the common twrp.img that you can find on the twrp page uses all the 6 cores of the Nexus 5X causing the rebooting which I mentioned. Now, I found this version of twrp 3.1.1 which is modified to use 4Cores, thanks to the user XCnathan32 and his thread about BLOD bug: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199.
Now it seems like the TWRP Recovery is stick to the phone and I'm really happy to say that. Thanks for all your support, you were very patient!
Click to expand...
Click to collapse