Develop Bugs

Installing TWRP after CFAutoRoot?

Hello.
Well I am new to android rooting. I switched over to a Galaxy s6 from apple iPhone.
Ive recently rooted my galaxy (6.0.1 SM-g920p) with CF autoroot. I am attempting to install TWRP recovery, but end up in a bootloop everytime. The error says: RECOVERY IS NOT SEANDROID ENFORCED. Ive gotten out of the bootloop and am back in my phone.
The question is: How do I install TWRP and Xposed without causing another bootloop?
Any help would be greatly appreciated.
Regards.

I had the same problem. Reflash CF auro root to fix your phone. I never got TWRP to work.

Hey,
Yeah ive already gotten myself out of the loop. Im stuck on installing TWRP and xposed.

Clear cache in stock recovery after cfauto wait for that if u havnt seen anything after flash wait.
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
Or just odin twrpis a better bet 3.0.0-1 over stock

Jimmy1life said:
Clear cache in stock recovery after cfauto wait for that if u havnt seen anything after flash wait.
---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------
Or just odin twrpis a better bet 3.0.0-1 over stock
Click to expand...
Click to collapse
Kind of confusing. Could you possibly reword it ?

Sure sorry trying to multitask and help lol. We only used cfauto at the very biggening of the MM update soon as twrp was released in a odin flashable zip or img we no longer need cfauto. Im gonna look for the link to the right twrp its 3.0.0-1 there is newer versions but none have worked. Flash it then once in twrp you are golden
But make sure oem lock is of in settings menu.
---------- Post added at 09:56 PM ---------- Previous post was at 09:40 PM ----------
For sure i tried twrp 3.0.0.2 from official twrp site didnt work. that was the other day but i did find the right one maybe down load the one I think its 3.0.1 but when installed itl say 3.0.0-1. Once i get out work i will check the exact file i downloaded and worked and find the source of it. Its on my computer.

Jimmy1life said:
Sure sorry trying to multitask and help lol. We only used cfauto at the very biggening of the MM update soon as twrp was released in a odin flashable zip or img we no longer need cfauto. Im gonna look for the link to the right twrp its 3.0.0-1 there is newer versions but none have worked. Flash it then once in twrp you are golden
But make sure oem lock is of in settings menu.
---------- Post added at 09:56 PM ---------- Previous post was at 09:40 PM ----------
For sure i tried twrp 3.0.0.2 from official twrp site didnt work. that was the other day but i did find the right one maybe down load the one I think its 3.0.1 but when installed itl say 3.0.0-1. Once i get out work i will check the exact file i downloaded and worked and find the source of it. Its on my computer.
Click to expand...
Click to collapse
Even if I do still have CFAutoRoot on MM, I will still be able to flash TWRP correct?
I tried flashing the newest one (3.0.2 TWRP) and got my phone into another bootloop But I reflashed CFAuto and fixed it.

https://dl.twrp.me/zerofltespr/twrp-3.0.1-0-zerofltespr.img.tar.html
this is odinable twrp3.0.0.1 yes u are fine unless you run into data issues but i used cfauto root for weeks no problems.

Jimmy1life said:
https://dl.twrp.me/zerofltespr/twrp-3.0.1-0-zerofltespr.img.tar.html
this is odinable twrp3.0.0.1 yes u are fine unless you run into data issues but i used cfauto root for weeks no problems.
Click to expand...
Click to collapse
Flashed this file and phone went into the same bootloop. It just says "RECOVERY IS NOT SEANDROID ENFORCING" in the top left hand corner.
I believe it could be a result from using the AP button when inside of the Odin app? Am I supposed to use BL or AP?

Yes AP but unchrck reboot and hold down home power to exit and quickly soon as light blinks off manully hold up +home +power after it days pass to enter twrp if it restarts by odin it wont boot.

Sorry man we might need professional help. Think some people just have problems flashing stuff. I just follow directions. SO RETRY follow the steps they work in the main threads.

Jimmy1life said:
Yes AP but unchrck reboot and hold down home power to exit and quickly soon as light blinks off manully hold up +home +power after it days pass to enter twrp if it restarts by odin it wont boot.
Click to expand...
Click to collapse
I did everything step by step, but my phone still goes into the wierd bootloop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

https://dl.twrp.me/zerofltespr/twrp-3.0.1-0-zerofltespr.img.tar.html. My last effort this twrp is from the 3.0.0-1 thread. flash in Odin.
---------- Post added at 11:20 AM ---------- Previous post was at 11:19 AM ----------
Wait longer when u see recovery isnt enforcing like 4 minutes. manually reboot it into recovery.

Anyone else who can help? My Odin says success but my phone simply wont boot into twrp recovery - as it doesnt even exist. It just sits on the bootlogo. Ive tried forcing it into recovery but nothing works.

try re-instaling twrp via Odin again. Then flash the SuperSU.Zip in twrp to get root.
Edit: just realized @Jimmy1life linked you the wrong twrp.
This one should work
https://dl.twrp.me/zerofltespr/twrp-3.0.0-0-zerofltespr.img.tar.html

Yea its confusing with ones on official site up but not working. Gamepro i tried man. I need to wake be getting on here when im still sleeping. Some of post are not clean and straight forward working on it though. Thanks Good luck with TWRP.

gamepro602 said:
try re-instaling twrp via Odin again. Then flash the SuperSU.Zip in twrp to get root.
Edit: just realized @Jimmy1life linked you the wrong twrp.
This one should work
https://dl.twrp.me/zerofltespr/twrp-3.0.0-0-zerofltespr.img.tar.html
Click to expand...
Click to collapse
Nope 3.0.0 didn't work.
After flashing it via Odin, my phone just sits on the Samsung Galaxy s6 boot screen. Won't go into recovery. @gamepro602

Ok, just Odin back to stock to fix the recovey (backup everything first). Then flash the twrp.
Also make sure you uncheck the auto reboot option in Odin before you flash.

MIUI8-6.6.3 Global alpha & 6.6.27 cn rom

Fastboot rom install with
-miflashtool
6.6.3 GLOBAL Official Alpha Fastboot rom
6.6.3 eu_multi -Unofficial Global rom (install with twrp revovery )
6.6.3 china twrp alpha rom
6.5.31 fastboot rom Download
miui7
6.5.30 Global fastboot rom
6.5.30 Global TWRP rom
7.2.9 Global Stable Fastboot Rom
6.5.20 Global TWRP Beta Rom
install with TWRP (please dont try with system updates>choose packet)

murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks

murattiy said:
6.5.20 global beta
https://drive.google.com/file/d/0B2UMSvqNe0deY0h3YW1aX20wdDQ/view?usp=sharing
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
giardux91 said:
Where did you take it? There is no post in xiaomi official forum. And how to install it over 7.2.4 global?
Thanks
Click to expand...
Click to collapse
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.

shade.sh said:
There is also a official URL: http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
---------- Post added at 13:37 ---------- Previous post was at 13:35 ----------
It should be flashable in fastboot mode or at least in EDL mode with the latest MiuiFlash.
Click to expand...
Click to collapse
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.

giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.

shade.sh said:
You're right... looks like a OTA or something image... i don't have my Mi5 with me to check if you can flash it via TWRP.
Click to expand...
Click to collapse
The strange thing is that this rom doesn't exist on xiaomi forum.

giardux91 said:
The strange thing is that this rom doesn't exist on xiaomi forum.
Click to expand...
Click to collapse
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE

shade.sh said:
There was a thread in the English forum, but was deleted very quick:
http://webcache.googleusercontent.c...94-1-1.html&gws_rd=cr&ei=JaFBV5alFIX7UpfbgOgE
Click to expand...
Click to collapse
I think it's not safe to install it, what do you think about?

giardux91 said:
I think it's not safe to install it, what do you think about?
Click to expand...
Click to collapse
Well, i never had it installed, so i cannot say anything about it... maybe the thread starter could say something about it
We only know its not "official" available.

I flashed it and am using it since yesterday. So far I haven't encountered any issues but I'm kind of put off by the state of their ROMs for this phone currently and hence haven't exactly 'tested' anything out.
The thread on the Chinese forum is still alive but they aren't letting people post it International apparently.
http://www.miui.com/thread-4296538-1-1.html

In case anyone needs info how to install it -> installed it via Updater which brings you to TWRP, after which the devices was decrypting and after it installed as any other update. Took about 20mins. Installed it "over" xiaomi.eu_multi_gemini_6.5.19_v7-6.0.zip
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..

jemeljsh said:
This rom rewrites recovery to the stock one and decrypts data. I re-flashed twrp recovery but in twrp it asks me for password to access/decrypt the data (the data thats on the phone, such as TWRP backups and other ROM .zip's) ? I have no lock screen/no password on my phone. Tried booting in system and setting lock screen password and using that in TWRP but no luck. Tried "default password" but it does not work. I wan't to restore other version of en.miui rom, but I can't access it via TWRP now. Any ideas for the password or way around? I am too lazy to reflash MiFLash version of 6.4.21 and then copy my TWRP backups onto the phone..
Click to expand...
Click to collapse
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.

murattiy said:
6.5.20 global beta
official rom but boot error official rom rom .official rom link : http://bigota.d.miui.com/6.5.20/miui_MI5Global_6.5.20_e785fae0e6_6.0.zip
my link diffirent and working rom.(changed boot.img)
https://drive.google.com/open?id=0B2UMSvqNe0deU0ZkRHcxNUdFMkE
https://youtu.be/xadfdqTrnjo
Click to expand...
Click to collapse
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.

kamrul.auntu said:
Surprisingly original one works through updater. But in the yesterday morning when nI tried via TWRP it does not worked for me and showed boot.img related error but flashed successfully and device never booted up and stuck on boot logo. Then I flashed 7.2.4.0 again and just for checking I tried to flash manually via updater apps and it works. Unlike other updater ROM this one wiped all data (though I did not have any) and had a clean install.
Click to expand...
Click to collapse
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------
giardux91 said:
But the rom doesn't seem to be fastboot version. Infact I try and it's possible to install it with updater app, but the system says that it is an older version of stable.
Click to expand...
Click to collapse
I had the similar message when going from 7.3.3.0 China to the latest China developer. I would not mind it.

SavageDamage said:
Check over at the MIUI forums, I think someone mentioned this issue and how to fix it. I have locked bootloader so no experience with TWRP on this phone yet.
Click to expand...
Click to collapse
I could not find the solution to get back to 6.5.19 eu.miui rom. Whatever password options I tried within TWRP data would not unlock/decrypt (tried -> password, default_password, default password, "lock screen password/lock screen pin").
To resolve the issue I:
1. copied contents (including made backups with TWRP 3.0.2) of the phone while booted into the system to my pc 2. reflashed MiFLash version of 6.4.21 eu.miui rom via MiFlash in FastBoot;
3. reflashed TWRP to the one version which matched the version of my TWRP backups (3.0.2)
4. while booted into 6.4.21 eu.miui rom copied TWRP backup from pc to the phone
5. booted into TWRP and restored my TWRP backup.
So the test of this rom version costed my 2 hours :laugh:

TheUltrametricSpace said:
this doesn't look like a fastboot ROM!
Just to add details:
Xiaomi names fastboot Roms with "phone_name"_"version"...
like the Mi5 fastboot Roms are: gemini_images_V....
And Mi5 Recovery ROms are miui_MI5...
So if you tried to flash it as a fastboot ROM it's likely to not work.
Click to expand...
Click to collapse
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.

kamrul.auntu said:
@TheUltrametricSpace
I never told that it looks like a fastboot ROM kind of a thing! Looking at the inside of zip file also can indicate that which one fastboot or which one is recovery ROM. BTW, I am still waiting for your comment on another of mine thread where I mentioned you. This is, I am not getting mobile network signal most of the times and get it back network barely. Impossible to use the phone. Please help.
I was just trying to say OP that original one (leaked) worked for me through phone updater rather TWRP. TWRP can flash it but firmware don't have ability to boot the device. That is why I 1st rollback to to Global stable 7.2.4.0 and then update this ROM. Even not seen any verification error in the flashing process. But TWRP presented me error in boot.image which OP mentioned. I think this ROM leaked from any closed alpha/beta tester and that is why updater apps not shows any error. If you try to install 7.2.8.0 over 7.2.4.0 recovery ROM it shows verification error.
Click to expand...
Click to collapse
ja ja, i wrote this in general. Sorry.
Dunno about the other parts you wrote sorry.

Has anyone tried Global Stable 7.2.9?

Is it possible install ufficial rom over xiaomi.eu rom?

[RECOVERY][THEMED] Negalite HW TWRP 3.0.3 | lz4 | f2fs | ubertc | v1.5 | 1/09/17

Welcome To Negalite HW TWRP Recovery!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
lz4 Compression Algorithm - boot speed
f2fs Support
logging enabled(logcat)
fb2png - take screenshots within recovery
compiled using Uber Toolchains
compiled using Negalite HW kernel
many features enabled
Custom Theme
Downloads
Recovery Flashable! Flash From Within Your Current Custom Recovery
negalite-HW-TWRP-3.0.3-v1.5.zip - 1/09/17
Fastboot Flashable! Flash From Within Bootloader Using Fastboot
negalite-HW-TWRP-3.0.3-v1.5.img - 1/09/17
Device Source
https://github.com/Negamann303/omni_twrp_device
​

Reserved...

Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.

imucarmen said:
Nice. Thanks for your work man! I'll try this out and report back if I notice any issues. If you don't hear from me then it's all good!
Is f2fs only for cache, data, and internal storage? Or can it be used on system as well?
[update] I used the flash method and it's running good. Switched cache, data, and internal storage to f2fs and all is running well.
Click to expand...
Click to collapse
Good I set it up for system to do it as well, even though technically it would be pointless since system doesn't write files(unless you manually add to it or flash something to it) . I haven't tested it though
Sent from my SM-G935P using Tapatalk

Updated Recovery To The Latest 3.0.2-1!

I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.

shag_on_e said:
I guess the restore bug may not be present in this watch's system due to no efs partition. I'm wondering if it does affect it at all since it does affect quite a few devices.
Click to expand...
Click to collapse
We are one commit past that issue, it was already fixed
Sent from my SM-G935P using Tapatalk

i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot

samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.

Pkt_Lnt said:
After you flash the recovery, boot to the normal watch running before you boot back to recovery, i *think* that is how I solved it, but it has been some time ago.
Click to expand...
Click to collapse
i tried this multiple times without success

samjoandco said:
i tried this multiple times without success
Click to expand...
Click to collapse
I had to do it about 8 times with the same problem.
Try flashing recovery then back to bootloader with
Code:
fastboot reboot-bootloader
Then manually reboot from the bootloader to recovery.
Sorry, I just don't remember how I solved it

while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?

samjoandco said:
i get a red exclamation when i flash this recovery and then try to reboot into recovery. i am not sure what i am doing wrong. I flashed 2-3 times now with the same result. here is the command i am using
adb reboot bootloader
fastboot flash recovery negalite-HW-TWRP-3.0.2-v1.4.img
fastboot reboot
Click to expand...
Click to collapse
Your bootloader is unlocked?

gwolfu said:
while in bootloader mode, is fastboot boot negalite-HW-TWRP-3.0.2-v1.4.img working?
Click to expand...
Click to collapse
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
Click to expand...
Click to collapse
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked

samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk

samjoandco said:
Success Finally
this command worked. i didnt even have to reboot; in am in TEAMWIN blue screen and everything works now
Thanks for helping me .
---------- Post added at 06:45 PM ---------- Previous post was at 06:31 PM ----------
back to the same red exclaimation mark after rebooting! and boot to recovery.
my bootloader is unlocked
Click to expand...
Click to collapse
download the recovery img boot in to bootloader fastboot flash recovery img.whit the hardver button navigate to reboot recovery tourn long and you will booted in twrp recovery

negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
thanks this worked!
after trying for almost 24 hours, this worked fine. now i can go into recovery from ADB as well as from the reboot prompts within the watch. this is solved for good

negamann303 said:
Fastboot boot temporarily loads the recovery.img. Try doing that then flashing the recovery zip within recovery. Quick workaround for you
Sent from my SM-G935P using Tapatalk
Click to expand...
Click to collapse
yeas was about to suggest just that
well my idea was to boot in TWRP temporary to validate that the recovery image works and then flash it again from recovery
but heck negamann303 was faster then me on this
glad you made it work

Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?

BIade said:
Hey guys
Just got mine YEEEES
Is it possible to dualboot 1.5 & 2.0 via multiROM, dual-boot-scripts or magisk?
Thank you soo much
Cheers
Blade
Also, can I take backups of the current state, to revert to it later?
Click to expand...
Click to collapse
No multirom for us yet. But you can do backup and restore!
BTW, luv Koln my last visit

TWRP 3.2.3-1 for Pixel 2

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!

Hey Dees Troy
sounds good, does it work with DP 8.1 bootloader?

So happy to see it.

Nice

What a joy it is to see this post today. Thank you!!

Thank you! You're a hero.
I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.

Spire42 said:
Thank you! You're a hero.
I'm dying to root my Pixel 2. Does anyone know whether this alpha release of TWRP can be used to install SuperSU (and suhide)? I'm afraid to try.
Click to expand...
Click to collapse
i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.
To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img
i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.

Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.
Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.

deepdvd said:
Code:
fastboot boot twrp-3.1.1-alpha1-walleye.img
I've tried to boot to this alpha on my Pixel 2, and it just sits there and does nothing. I've tried two different cables. If I unplug, it fails, obviously.
Code:
fastboot devices
shows my device and I'm definitely on the bootloader screen.
Any ideas? I re-downloaded the sdk platform tools as well as the latest usb driver to see if that was the problem, but it wasn't the problem.
Click to expand...
Click to collapse
Connected to PC vie USB 3 port?
Try with USB 2 if you have it. I've read people having success with it.

Natakranta said:
Connected to PC vie USB 3 port?
Try with USB 2 if you have it. I've read people having success with it.
Click to expand...
Click to collapse
I tried using a third USB port, and it worked. Thanks! I thought that testing two different ports would have been enough, but apparently the third time's the charm.

deepdvd said:
I tried using a third USB port, and it worked. Thanks! I thought that testing two different ports would have been enough, but apparently the third time's the charm.
Click to expand...
Click to collapse
Sent from my Sony Xperia Z1 using XDA Labs

marc.ientilucci said:
i tried flashing SuperSU v2.82 SR5 and phone would not boot into system. It just kept booting into bootloader.
To get my phone working again, I needed to flash the boot.img from the Pixel 2 Factory image via
Code:
fastboot flsah boot boot.img
i've gathers recovery / kernel logs - however since TWRP boots i will post them in the SuperSU forum.
Click to expand...
Click to collapse
Same issue here, tried with Snoke kernal and get the same problem

Does this mean root is getting close?

stackz07 said:
Does this mean root is getting close?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-2/how-to/how-root-magisk-pixel-2-t3698713

Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------
Dees_Troy said:
Note, this is BROKEN. Decrypt does not work yet and because it does not work, a lot of other things like backup and restore don't work. You can't transfer files with MTP. I have no idea what will happen if you try to factory reset. Basically, a lot of stuff won't work so if you're scared or can't afford to lose data or be unable to use your device, DON'T use this. I strongly recommend that you have the factory images already downloaded and know how to reflash them if needed.
I am not providing a way to permanently flash TWRP at this time. You should use:
fastboot boot /path/to/twrp.img
This will one-time temp boot TWRP so you can do whatever like maybe adb sideload a zip or something.
I am working on decrypt. The Pixel 2 uses a new embedded secure element chip from NXP. Most of the crypto implementation is done in Java and not in native C/C++ so it's going to take a while to convert all of this code and its many layers into something that TWRP can run. Be patient. I'll get it eventually (probably).
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/
Click to expand...
Click to collapse
@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
Anyone out here that can basically decrypt in twrp? Who can see all the folders and backup like me? I can flash a zip from install? Anyone else?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:10 AM ---------- Previous post was at 10:09 AM ----------
@despairfactor can see all the files in twrp and flash from install tab as well as me from my 2 XL?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
FYI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
FYIView attachment 4321138View attachment 4321139View attachment 4321140
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Forgot this. Only did vendor. Will do all later.
Sent from my Nexus 6 using Tapatalk

Anyone willing to reflash magisk via twrp and pull recovery.log immediately after from twrp and upload?????
Sent from my Nexus 6 using Tapatalk

bryantjopplin said:
Anyone willing to reflash magisk via twrp and pull recovery.log immediately after from twrp and upload?????
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Can do after work.
In about 8 hours [emoji6]

Patched Boot.img for v10.30.0 January update

[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
https://mega.nz/#!NUBmnawT!Pgrorx3HWBjPjv_DjeQZVN76VnwzqT1cn0u1U0MzgSA
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
https://mega.nz/#!0EZkXSDB!WYcB8wt1Eu92GZvVTExeaWRN9y1zQBLOjULCuKRHvR8
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
https://mega.nz/#!URYmHIxZ!i77uZQZ2V0aWBRNewxLY1UJPPhuhg2wicowDQMVETo4
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.

thanks a lot, can you provide also an unmodified 10.30.0 boot image?

Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot

pippozio said:
thanks a lot, can you provide also an unmodified 10.30.0 boot image?
Click to expand...
Click to collapse
I can provide an unmodified trwp made boot.img from my phone, thats why i said not to flash the patched boot image, and to only boot from it, twrp backups are .wim, i just changed the .wim extension to .img and patched it. As far as im aware its a normal packed boot.img but renamed .wim for trwp to flash it, ill provide it but use at own risk. https://1drv.ms/u/s!AqlJY73bUA7rholIeKoHAB8o6s94gA .Rename boot.img if your going to flash it.

anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.

anzhaki said:
Yep, a non patched would be also useful. Which Magisk version did you use to patch the image?
Still bootlooping after flashing it.
fastboot boot patched_boot.img
fastboot reboot
Click to expand...
Click to collapse
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.

boe323 said:
I used magisk v18 latest. Unmodified boot.img is in one of the posts. Ive used it so it should be fine, but still its done at your own risk. Im not sure how you will stop it bootlooping, sounds like magisk messed up the install when re applying after OTA.
Click to expand...
Click to collapse
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
boe323 said:
Dont fastboot reboot, just boot from it, if your rebooting then your wiping the temp boot.
Click to expand...
Click to collapse
Unfortunately still bootloops D:

anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.

anzhaki said:
The same thing happened when I updated from oreo to pie using the method to maintain root. If I remember well I solved the problem by flashing stock boot.img with
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
then it should normally boot and after that it should be ok to manually patch the boot image.
Maybe it's better to wait an image extracted from OTA
Thanks anyway
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
Unfortunately still bootloops D:
Click to expand...
Click to collapse
boe323 said:
Try anzhaki's method, he said it works but i cant confirm it as ive never run into problems (touch wood). Dont go making things worse by flashing custom stuff, try using his method and factory reset.
Click to expand...
Click to collapse
I m in bootloop. Anyone help me the pie fastboot image link? Thanks.

There isn't one for v10.0.30.0 at present .

boe323 said:
There isn't one for v10.0.30.0 at present .
Click to expand...
Click to collapse
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.

Is there any inprovements with this ypdate

boe323 said:
[Patched_Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholGl4AULW_tHKaCrg
[TWRP Backup Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholRaoTR_Nvxq7v6kw
[Boot.img]
https://1drv.ms/u/s!AqlJY73bUA7rholJT3zo4rEY9oO0lQ
Be careful as Always, only use this img for booting so you can install magisk direct.
To restore your boot image with trwp:
Unzip twrp and add to root of the sdcard,
fastboot boot twrp daisy zero(sdcard fixed version) and restore trwp backup, don't touch anything else, and reboot by holding power button.
Fastboot boot patched_boot.img to boot phone for direct install of magisk. ALWAYS RECOMENDED.
Click to expand...
Click to collapse
thanks, this boot image solved my bootloop problem

pippozio said:
thanks, this boot image solved my bootloop problem
Click to expand...
Click to collapse
Hi, which one did you flash and with what command?
Nvm, I used the last one.

What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.

Me tio want to update and when i see that people are having troubles. What is the correct procedure for this?

Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mms047 said:
your unmodified boot.img shows 64 mb, it should be 26-27 mb. no?
and can you upload it another server plz?
---------- Post added at 09:22 AM ---------- Previous post was at 09:09 AM ----------
Flashed your unmodified boot.img. no luck, still in bootloop.
Click to expand...
Click to collapse
No , original is bigger, only when you patch it ,it goes smaller, from other ppl who know about this stuff it's just padding

iniro said:
What is the procedure to update ota with magisk? Restore image with magisk, reboot, update ota and then flash modified boot.img?
Thx in advance.
Click to expand...
Click to collapse
I wouldnt try magisk ota method, theres reports of bootloops after OTA, best is to return everything to stock, disabale modules and reboot, uninstall modules and reboot, then uninstall magisk and reboot, any modded hosts need to be stock, audio/soundfx need to be stock, basically anything to do with system should be stock. If you get into any install issues with ota, then download the 10.0.20.0 rom from Mi's website and use flash all except storage, this will keep data and give you a fresh system image.

barumbads said:
Please help me, im rooted at v10.0.2.0 but when i unsintall/revert my boot.img in magisk it say's "store backup does not exist" . i factory reset my phone when i got a problem in substratum . didn't know that it will be remove by doing that, what should i do next? i want to OTA update my Phone.
Click to expand...
Click to collapse
Redo your system image with the rom on Mi's website, use flash all except storage.