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.

My VZW Pixel XL won't boot into TWRP to root - help!

Hey all, just got my 128GB VZW Pixel XL, unlocked the BL via dePixel8 and so far I love the phone, but cannot figure out why TWRP won't even boot for me to obtain root. I've now tried fastboot boot twrp.img with both TWRP RC1 and Alpha 2 .img's on NOF27B and cannot get TWRP to boot at all - I get a bootloop of sorts with TWRP's main screen rapidly flashing on and off, which persists until I do a hard reboot. This is also the case when I tried it on the Android O Dev Preview. Anyone know why this is happening or have a fix?

Did you download the latest platform tools directly from Google and then try again? They are available as a separate download now without needing to download the SDK. Don't use the minimal ones that were floating around

aholeinthewor1d said:
Did you download the latest platform tools directly from Google and then try again? They are available as a separate download now without needing to download the SDK. Don't use the minimal ones that were floating around
Click to expand...
Click to collapse
I'm fully updated on that front. Fastboot itself works just fine, it's specifically TWRP that won't boot at all.

EDIT: Sorry, on second thought FlashFire requires root, so what I posted wouldn't work. I don't remember this sort of thing being reported in the TWRP threads, so I might also try starting with a new install to see if the same thing happens.

StrizzMatik said:
I'm fully updated on that front. Fastboot itself works just fine, it's specifically TWRP that won't boot at all.
Click to expand...
Click to collapse
No idea but I'd it were me I'd start from scratch. Flash a factory image with fastboot so you are completely back to square 1. Go through initial setup and then enable a passcode in the settings. Then try TWRP again.

aholeinthewor1d said:
No idea but I'd it were me I'd start from scratch. Flash a factory image with fastboot so you are completely back to square 1. Go through initial setup and then enable a passcode in the settings. Then try TWRP again.
Click to expand...
Click to collapse
Updated my ADB / fastboot files and got it running no problem. Thanks again!
Sent from my Pixel XL using Tapatalk

Anybody have any more ideas on this other than what is mentioned. I have the latest platform-tools installed and the latest adb. I've flashed the latest 8.0.0 factory image. I've got no PIN or password setup, but I've tried it with that as well. All I get every time I do "fastboot boot path/to/twrp.img" is the flash TWRP bootscreen, but it nevers loads up. If I go back to bootloader and choose recovery, I get the android no recovery installed screen. This is driving me nuts already!

sharkie405 said:
Anybody have any more ideas on this other than what is mentioned. I have the latest platform-tools installed and the latest adb. I've flashed the latest 8.0.0 factory image. I've got no PIN or password setup, but I've tried it with that as well. All I get every time I do "fastboot boot path/to/twrp.img" is the flash TWRP bootscreen, but it nevers loads up. If I go back to bootloader and choose recovery, I get the android no recovery installed screen. This is driving me nuts already!
Click to expand...
Click to collapse
Have you tried:
1. setting up pin
2. Putting TWRP.img in the platform-tools folder
3. opening command prompt
4. Fastboot boot TWRP.img

Homeboy76 said:
Have you tried:
1. setting up pin
2. Putting TWRP.img in the platform-tools folder
3. opening command prompt
4. Fastboot boot TWRP.img
Click to expand...
Click to collapse
Having the same issues I've unlocked already but I can't get it to boot the twrp.img. I've set a PIN already, and updated sdk with no dice. It just flashes the twrp startup screen over and over. Found it I'm golden now.
UPDATE: Here you go if anyone gets stuck like I did:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896

StrizzMatik said:
Hey all, just got my 128GB VZW Pixel XL, unlocked the BL via dePixel8 and so far I love the phone, but cannot figure out why TWRP won't even boot for me to obtain root. I've now tried fastboot boot twrp.img with both TWRP RC1 and Alpha 2 .img's on NOF27B and cannot get TWRP to boot at all - I get a bootloop of sorts with TWRP's main screen rapidly flashing on and off, which persists until I do a hard reboot. This is also the case when I tried it on the Android O Dev Preview. Anyone know why this is happening or have a fix?
Click to expand...
Click to collapse
Are you using this TWRP: twrp-3-1-pixel-bootable-mod.img

How to Root Using SuperSU and TWRP on Oreo OPR6 Official Release

After a bit of trial and error, I managed to find a combination of files and actions that allowed me to successfully root my 64GB Pixel C on 8.0.0 by installing SuperSU via TWRP.
Steps:
Perform a clean installation of the official release, found here
Use the unofficial 3.0.0 TWRP release found in this thread (direct download link here) and boot to recovery ("fastboot boot [TWRP filename].img") - the latest official 3.1.1 TWRP did not work, either via flashing or booting
ADB sideload SuperSU 2.82SR3 found in this thread (direct download link here)
Hope this helps!

Stuck at TWRP after
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?

Jeff Z. said:
Flashed the TWRP from the link and side loaded the SuperSU, now my Pixel C is stuck at TWRP on reboot, any idea ?
Click to expand...
Click to collapse
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk

MadManMoon said:
The only thing I can think of is to reflash the stock recovery using the downloaded factory image. Seems like it was flashed, not simply booted into TWRP.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks. My problem was my pixel kept booting to TWRP even selecting to boot the system, kind of strange. I think I missed your first step, the pad was OTA updated to 8.0 from 8.0 Beta release. I will try again with flash the factory image of 8.0 first.

Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.

NitroSS said:
Anyone else able to root their pixel c tablet on Oreo with success? I'm thinking about trying it with the original posters guide. Just thought I'd see who else has been able to make this work.
Click to expand...
Click to collapse
Still works for me as of the September 2017 update. About to try it again with the October update.

It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.

CatThief said:
It's driving me absolutely mad. I just got a brand new Pixel C today. It's updated to the latest Oreo but nothing else has been installed yet. I unlocked the bootloader and copied the SuperSU zip file onto the device via USB file transfer from my PC, then I set up a password. I'm booting (not flashing) TWRP because all I want is root.
When I'm prompted for a password in TWRP I'm told it's invalid. I also tried "default_password" and that's invalid, too. I looked all over for a solution and found a modified TWRP that doesn't prompt for a password but it won't decrypt the internal storage.
I'm really pulling my hair out here. I can't figure out why it's working for some people and not others.
Click to expand...
Click to collapse
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.

Huffy1 said:
Try format userdata, then boot straight into twrp
Command is "fastboot format userdata"
You also have to flash SuperSU while in twrp to stop the tablet from encrypting again.
Click to expand...
Click to collapse
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.

CatThief said:
I'm confused about "stop the tablet from encrypting again". I know TWRP needs to decrypt the data partition to access it, but are you saying encryption won't be re-enabled when I reboot the system? I had to ask because it sounds strange that installing the SuperSU zip would mess with encryption.
Click to expand...
Click to collapse
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up

Huffy1 said:
If everything goes to plan yes.
You can encrypt again if you wish through settings once the tablet is booted up
Click to expand...
Click to collapse
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?

CatThief said:
Does this mean when I flash the factory images for the monthly updates and need to root the device again that I'll be wiping all userdata each time?
Click to expand...
Click to collapse
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.

Huffy1 said:
No just use flashfire to update and keep root, it won't encrypt the tablet. You can still boot official twrp as well after using flashfire to update as your tablet shouldn't encrypt.
Click to expand...
Click to collapse
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.

CatThief said:
Is removing encryption something everyone is doing, or is it just a workaround for the people who can't get TWRP to work? I never ran into anything like this before.
Click to expand...
Click to collapse
Use FDE then and it reportedly works.

Huffy1 said:
Use FDE then and it reportedly works.
Click to expand...
Click to collapse
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?

CatThief said:
Just curious though, is this a standard prerequisite for using TWRP and rooting *all* Pixel C devices?
Click to expand...
Click to collapse
Don't know, only telling you what I did cause I had the same problem as you

Well I'm finally rooted. I didn't change the encryption, just tried a different method and after several tries it finally worked. I used adb sideload inside TWRP after canceling the password screen. Odd that it took several tries, though, to get through it without generating errors. We'll see how it goes next month.

I have had a lot of trouble with rooting Oreo...
I started out trying to use Magisk but gave up after many attempts. Every version, and every kernel I tried resulted in booting to recovery and not system. I could have tried the ADB method but I actually want to have TWRP so I didn't try that.
By the time I tried SuperSU my factory image had had an OTA and many apps & files installed so I can't say my system is "clean" but I have Fastboot flashed the stock boot image many (many) times to recover from whatever Magisk does to the kernel. I never looked all that hard for this unofficial TWRP people talk about so I used 3.1.1-1. At some point I converted to File Based Encryption because it is so much nicer to use, and so TWRP cannot decrypt my internal storage, but the workaround is to put zips and images on a USB drive. It also does not ask for a password. So far so good, I have my workarounds. I do also have this weird error where TWRP cannot unmount the system but I can flash kernels without problems. I have chosen to keep system read-only for superstitious reasons. I think it will fail if I look at it funny sometimes lol.
From this state I flashed the latest SuperSU and it booted! So I do have root. I still would like to try Magisk for the modules but it seems this isn't ready. However, my trusty old terminal app hangs at the su command... and several kernels will crash my tablet... so it's "working" but there is more to do. And literally just now I see I have an OTA. lol.

I followed the original instructions and got rooted with the latest version of Oreo. But, TWRP still wouldn't flash correctly without causing boot loops.
I finally got it resolved by using the original instructions, then loading the Official TWRP app from Google Play. I used the app to flash twrp-3.1.1-1-dragon.img.
Everything is working properly now. I have 8.0.0 (OPR1.170623.032, Nov 2017) loaded and rooted, and the Pixel C will boot into TWRP and see the encrypted data.

Is it posible to flash latest Oreo stock factory image https://developers.google.com/android/images ryu-opr1.170623.032-factory-020f1cf9.zip using stock TWRP or do I have to side load it ?
I'm getting a Invalid zip file format error in TWRP when I try and flash it

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"?

[Official] [Recovery] TWRP for daisy

Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, the instructions to do that are here. You will lose your data and you'll have to set up your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb reboot bootloader
3. fastboot boot twrp-daisy-3.2.3-0.img
4. Hit "Cancel" if you're prompted for a decrypt password
5. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
6. Run the install in TWRP to permanently install TWRP across both slots
7. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
, Guava.

adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!

tutankpusch said:
adb says "adb: usage: push requires an argument" after using first command.
thanks for the effort though!
Click to expand...
Click to collapse
Oops - ad "/sdcard" to the end of that command. Missed that. I'll update the OP.

I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!

KezraPlanes said:
I can't get past decryption, but I'll wait for a fixed version. Thanks for going to all this trouble!
Click to expand...
Click to collapse
Decryption is a Xiaomi issue...what do you mean by fixed version?

d1ngh said:
Decryption is a Xiaomi issue...what do you mean by fixed version?
Click to expand...
Click to collapse
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X

d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...

KezraPlanes said:
So there's no fix? I can't have my phone secure at all? I thought this was a bug lol
TWRP encryption is how I ended up killing my Note 4X
Click to expand...
Click to collapse
Try adb push while TWRP is booted. It should get you past the pre-load issue.

actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
but it seems everything is working fine

brunoliveh said:
How to install de TWRP inside TWRP.. im not finding the file.
And I used the command adb push...
Click to expand...
Click to collapse
When you're in the TWRP UI tap "Install" and select the twrp file you pushed (if you used the command above it should be in /sdcard)

tutankpusch said:
actually there was an error when installing twrp.zip from twrp:
"E:recv error un uevent
Unable to find partition for path '/cache'"
Click to expand...
Click to collapse
There isn't a cache partition on A/B devices, that error is fine.

d1ngh said:
Hi all,
We've worked with TeamWin to get an official release of TWRP for daisy released, and here it is! We're sponsoring continued development of TWRP for daisy and other devices, so reach out to me if you have any questions.
I have to thank Dees_Troy & TeamWin for putting in the effort to make this available for us - donate here to support them directly.
So, without further ado, here's the download link. Here's a link to the source.
Please make sure you're on the factory image. If you aren't, download the files here and run flash_all.sh, then go to recovery and factory reset. You will lose your data and you'll have to set yup your phone again.
1. Enable developer options (your bootloader should still be unlocked)
2. adb push ./twrp-installer-daisy-3.2.3-0.zip /sdcard
3. adb reboot bootloader
4. fastboot boot twrp-daisy-3.2.3-0.img
5. Run the install in TWRP to permanently install TWRP across both slots
6. Reboot (you can reboot afterwards to TWRP to verify it is there)
Thanks all - and feel free to post your experiences, questions, comments, and concerns.
Click to expand...
Click to collapse
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory

brunoliveh said:
using the updated command
failed to copy './twrp-installer-daisy-3.2.3-0.zip' to '/sdcard': couldn't create file: Is a directory
Click to expand...
Click to collapse
If there's already stuff there you'll need to specify the filename as well

Great news!
-Is full encryption working?
-I don't want to loose magisk... how can i preserve it?

d1ngh said:
Try adb push while TWRP is booted. It should get you past the pre-load issue.
Click to expand...
Click to collapse
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know

KezraPlanes said:
Hey, that worked! And decryption works after a reboot. But now it's boot looping into TWRP? Did I lose all my data or is there a way to make it boot back into what was installed?
If I have to reinstall it's fine, but I'd like to know
Click to expand...
Click to collapse
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.

d1ngh said:
That doesn't sound good. Did you factory reset after installing twrp? If so you will have lost data but the ROM should still be there.
Click to expand...
Click to collapse
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Edit: Hooking up USB and I can access storage. Copying stuff over just in case.

KezraPlanes said:
I didn't. I was checking the file system and all my files are there. The ROM is the one who's gone lol.
Can I flash a GSI and have it working again?
Click to expand...
Click to collapse
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.

d1ngh said:
I've been able to install TWRP before a GSI with relative ease but I couldn't get it to boot properly (phh-treble). I've also been able to install TWRP after a GSI and it works just fine. What GSI are you using? I might be able to test it out pretty quickly.
Click to expand...
Click to collapse
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.

KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Switch active slot
---------- Post added at 09:23 PM ---------- Previous post was at 09:23 PM ----------
KezraPlanes said:
I was using stock Android, just with Magisk. Didn't factory reset because I wasn't using a GSI and thought it wouldn't be a problem.
I'm asking if now I can just flash a GSI and have the phone up and running again. It seems storage and everything is there and working fine.
Click to expand...
Click to collapse
Try to Switch active slot