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]
Related
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
I have combined the OnePlus 3 and OnePlus 3T TWRP threads into a single thread for the unified build.
Please visit:
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I apologize for the inconvenience.
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3T, Tool/Utility for the OnePlus 3T
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3t
Version Information
Status: Stable
Current Stable Version: 3.0.3-1
Stable Release Date: 2017-01-16
Created 2016-11-26
Last Updated 2017-01-22
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
ghettopops said:
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
Click to expand...
Click to collapse
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
jcadduono said:
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
Click to expand...
Click to collapse
So that means it doesn't use that new layout which includes dual A/B partitions right? If the only benefit of dual partitions is seamless updates, I guess the traditional layout is fine or even better.
Edit: Both this TWRP thread and the Tyranus kernel thread came out pretty quick, and seem very well documented and professional compared to some of the other Non Nexus device threads. I'm impressed. I just hope the threads stay uncluttered. Thank you.
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
someone0 said:
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
Click to expand...
Click to collapse
Done. Should now default to f2fs on data wipes as well. (redownload, I didn't change the version number)
Yes that is an option.
ghettopops said:
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Click to expand...
Click to collapse
No, separate recovery partition means you can flash kernels and recoveries separately. It means recovery isn't part of the system boot image, which is an idiotic design of the Pixel phones that is hurting custom development for them. See example:
OnePlus 3T (and every other sane device):
boot partition = system boot image
recovery partition = recovery boot image
result = you can use twrp to flash custom roms! any issues = just try in twrp again!
Pixel:
boot partition = boot image with recovery ramdisk that loads system (???)
boot_a partition = the same thing as boot partition (??? again)
recovery partition = nowhere to be found
result = flash a bad custom rom? say goodbye to twrp!
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
charlieb620 said:
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
Click to expand...
Click to collapse
need recovery.log ... i'm guessing this is happening due to changing default partition type for data from ext4 to f2fs, might need to change it back
in the meantime, setting default back to ext4....redownload (again)
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
jcadduono said:
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Click to expand...
Click to collapse
Woah! Now official nethunter? I can test this Monday when I get the device. I would be surprised if we got copperhead OS too.
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
charlieb620 said:
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
Click to expand...
Click to collapse
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
someone0 said:
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
Click to expand...
Click to collapse
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
jcadduono said:
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
Click to expand...
Click to collapse
{
"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 ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
charlieb620 said:
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
Click to expand...
Click to collapse
That screenshot seem like somebody is trying to run adb from within the android shell. I would just
'adb shell'
'su'
'cd /sdcard' or /tmp or whichever directory that's writable.
then run whatever command you need from there. Having another DOS windows open up is also a good idea. That way, one window is always running shell, and another is just DOS. so no confusion and no need to keep exiting shelf and get back in.
Fails to decrypt data. Here is logs from 3t 128gb model.
Black screen
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
hawki said:
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
Click to expand...
Click to collapse
How did you get root (superSU) installed w/o twrp?
BTW, you may have the same problem I had earlier, which is the stock OS is on version 3.5.1. You need to follow the instruction again, and flash recovery and boot into twrp.img After that, patch your OS to the latest via OTA, I think you need to re-root again after that.
just to be clear. Since I am already rooted am I just flashing twrp and swiping for Mods?
This is the LeEco Le Pro 3's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
I didn't try it yet
But Thank you for your work,
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
It is compatible for the lepro3? I used it before for oneplus2.
meuhmeuh51 said:
It is compatible for the lepro3? I used it before for oneplus2.
Click to expand...
Click to collapse
Yes, it's completely compatible, i have tested it on my leeco le pro 3
mauronofrio said:
Yes, it's completely compatible, i have tested it on my leeco le pro 3
Click to expand...
Click to collapse
ok I will try
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently
Sent from my SM-P600 using XDA-Developers Legacy app
mauronofrio said:
Someone have tried my Tool All In One for Leeco Le Pro 3?
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Click to expand...
Click to collapse
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
Can I go back to completely stock with this tool kit? I have the 727 model with a custom ROM currently<br />
<br />
Sent from my SM-P600 using XDA-Developers Legacy app
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
no
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
kaivorth said:
Think I just bricked my Le Eco Pro 3. Dragged the ROM into the root system of my X727 I was going to flash, Lineage 13
Enabled USB Debug
Unlocked Bootloader
Flashed GS Custom Recovery
Wiped Everything
Went to Flash the ROM, and nothing showed up...
I rebooted, and now I think the stock recovery re-installed itself, and there is no ROM present because I wiped everything.
Help
I just get a flicker of the Le Eco Boot Screen, then it shuts off. Can't get into ADB or Recovery.
Click to expand...
Click to collapse
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
kaivorth said:
Thankfully I fixed it.
Flashed an aboot file, and all a sudden, Lineage 13 started up. You cannot believe how psyched I was. I was on eBay looking at my next phone, and all angry that I messed up my perfectly good phone.
I don't think this tool had anything to do with it. I was unforunate enough to wipe my phone before I went to install the ROM, and it wiped the ROM too. When it restarted, it had nothing to boot too. Just used Fastboot to flash the aboot file, and sideloaded the ROM and flashed away
Click to expand...
Click to collapse
Had the same issue and same fix for my attempt into unlocking bootloader and installing custom recovery and rom.
Did you also flash the 5.8.0.19 aboot file? I'm wondering if flashing a newer one is a good idea...
Sent from my LEX727 using Tapatalk
Very good tool thank you very much Mauro
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
The twrp 3.1.0 is better no matter the dev
Wortelstok said:
Thanks Mauro, it helped me install Omni ROM.
Question, I had two TWRP versions to choose from, I installed the latest 3.02. Is it useful to update the TWRP with e.g. the 3.1.0 from Darkobas?
Click to expand...
Click to collapse
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
mauronofrio said:
Maybe yes, in the next Tool update i will update all recovery available, for now you can flash it through Manual Mode
Click to expand...
Click to collapse
Thank you for all your effort for our Le Pro 3 :good:
Does this unlock bootloader with the current us version 21s?
I try using this Tool ALL in One on the Le Pro 3 but unable to unlock the bootloader as it displayed
"FAILED <remote: oem unlock is not allowed).
I already checked "ON under the OEM UNLOCKING" and "USB debugging" is "ON" also under the Developer Option before turning off the phone and boot it (volume down + Power) into Fastboot Mode.
Please help. Any advise is appreciated.
coolmaster121 said:
Can you get to fastboot? Power button + vol up? If you can you can probably flash a chinese bootloader and then try booting again
Sent from my LEX727 using Tapatalk
Click to expand...
Click to collapse
fastboot should be vol down
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
{
"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"
}
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
Click to expand...
Click to collapse
How does your phone show up under device manager?
marmeak7 said:
I got a new OnePlus 3 for my dad and the device showed OTA update for august 21. I tried installing it but it showed signature verification error and the OTA could not be installed. Then I tried sideloading the update via adb but the process stops at 47%.
It displays message saying "Total xfer: 1.00x"
I have installed the latest version of adb but to no success.
Help me out guys. Thanks.
Here is the snippet of the error shown by adb
View attachment 4281534
Click to expand...
Click to collapse
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Puddi_Puddin said:
How does your phone show up under device manager?
Click to expand...
Click to collapse
Device Manager lists the device as ONEPLUS A3003
DJBhardwaj said:
Try switching the port. The error you mentioned is either due to an incomplete download or an unstable USB connection. Give a try to both.
Click to expand...
Click to collapse
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
demonoid phenomenom said:
Dunno for sure but for xiaomi devices you have to unlock your bootloader (for some reason) in order to flash/ota update your phone , plus additional info would be helpfull ,like current ROM you are running
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
I am on stock OOS with Marshmallow 6.0.1 and I am trying to update it to OOS 4.1.7 released on august 21st and I got the device just two days ago. I tried updating via OTA and it presented me with signature verification error and while trying to sideload the OTA, I ended up with the error mentioned above.
marmeak7 said:
I did try switching the ports and I also tried three different zip files just to be sure but the result is still the same. I even tried switching cables but it did not work
Click to expand...
Click to collapse
Have you tried flashing the full ROM zip file via stock recovery?
DJBhardwaj said:
Have you tried flashing the full ROM zip file via stock recovery?
Click to expand...
Click to collapse
The stock recovery does not have the option to flash zip files or am I not seeing the option?
marmeak7 said:
The stock recovery does not have the option to flash zip files or am I not seeing the option?
Click to expand...
Click to collapse
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
DJBhardwaj said:
Do you know the process to flash recovery via fastboot?
Here is the latest recovery image: http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
You will need to use the command: fastboot flash recovery recovery_op3.img
Then reboot into stock recovery to see if an update option for internal storage/local is available. I have a OnePlus 5, so I am not sure if this is specific to the device or just because there's an older recovery version installed.
Click to expand...
Click to collapse
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
marmeak7 said:
I have already tried updating the recovery via fastboot but fastboot was not able to update the recovery as well it displayed an error while flashing via fastboot. I was using the latest recovery available from OnePlus
Click to expand...
Click to collapse
Oh.. How about installing TWRP and then flashing the ROM through that?
DJBhardwaj said:
Oh.. How about installing TWRP and then flashing the ROM through that?
Click to expand...
Click to collapse
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help ?
marmeak7 said:
I guess that is the last resort for me now. I was skeptical about unlocking bootloader since it is my dad's device but I have no option left now.
Anyways thanks for your help
Click to expand...
Click to collapse
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
DJBhardwaj said:
No. Don't worry, unlocking the bootloader is rather a very good choice. Unlocking the bootloader is totally different than root. So, in case you find yourself in such situations, an unlocked bootloader can allow you to do a lot.
Make sure that you take a complete backup of your device first. It will also wipe the internal storage.
Click to expand...
Click to collapse
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
demonoid phenomenom said:
plus ,you dont void your warrantie , thanks oneplus!!
Enviado desde mi ONEPLUS A3000 mediante Tapatalk
Click to expand...
Click to collapse
Exactly, all courtesy of OnePlus. Not all OEM offer this liberty.
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
info2shail2010 said:
Ok here is the Solution with 100% work.... (Same happened to me also)
Formating some times breaks file system of storage...
So
1. Install Twrp by Blue spark 3.1.1 (you can give a try to official TWRP)
2. Go to wipe and then Repair partitions
3. Repair System partition and Storage partition (it will delete all your data so keep a backup.. I would suggest repair each and every partition using Twrp Repair)
4.Farmat again
5. Your Welcome!
Click to expand...
Click to collapse
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
marmeak7 said:
Sorry for the late reply but I am going to try this right now.
Thanks for the help :angel::angel:
Click to expand...
Click to collapse
Just in case you run into a brick...?..I did once so I found this thread handy
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
So i encountered this problem a while back, after doing some digging and analyzing adb, i came to the conclusion that adb could only address memory in 32bit on pc, so it couldn't handle the size when sideloading the extracted OS with STOCK recovery. If you want to still do it with stock you will have to do some digging around in forums, i found a software that modded the program to be able to use 64bit memory access. cant give you the link though since it was a while back.
Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"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"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.
Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.
regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple
still works like a charm
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit
Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?
Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.