Database Develop

Lenovo Z5s Update to ZUI 11.5 (Android 10)

Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.

Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.

{
"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"
}

carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier

jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!

links not works

vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.

Thank you very much

Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.

thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number

sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?

galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!

vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one

Install global via fastboot, all is included or in qfil ROM is all in zip file

vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again

i tired and failed again

galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably

carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it

hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?

galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot

[Android 11][Recovery][A715F]TWRP 3.5.1 [ianmacd]

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.1_10-A11_2b1_ianmacd.img
twrp-a71-3.5.1_10-A11_2b1_ianmacd.tar
Multidisabler zip by Ianmacd
VBMeta disabler
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
17/03/21: Release for Android 11 BL
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71

reserved 1

reserved 2

Sorry for the delay, this TWRP should work perfectly with Android 11 BL

Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!

@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/

donkeyman1234 said:
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
Click to expand...
Click to collapse
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.

ban.codrut said:
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
Click to expand...
Click to collapse
I haven't used the Link to Windows feature, I don't really have a good understanding of what you mean.

ShaDisNX255 said:
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
Click to expand...
Click to collapse
I took a shot of log.

I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?

viktor92 said:
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
Click to expand...
Click to collapse
Yes, you must format and flash multidisabler.

Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working

Pupet_Master said:
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Click to expand...
Click to collapse
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.

ShaDisNX255 said:
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
Click to expand...
Click to collapse
Thanks Friend

I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert

Nobby52 said:
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Click to expand...
Click to collapse
Yes, you have to go back to the main menu

Thank you, I'll try it again.
Norbert

Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert

Nobby52 said:
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Click to expand...
Click to collapse
What ROM are you trying to root?
Are you Rooting with Magisk or Super SU? Do you install SUper SU App or Magisk Manager after?
About the reset, did you flash the multiboot disabler after flash the root zip file?

I root the original Samsung Stock Rom. "A715FXXU3BUB5_A715FOXM3BUB6_DBT". I followed the instructions here exactly.
First unroot and debug mode
1.) download mode
2.) with Odin TWRP + VBMeta-Disabler
3.) TWRP started, wipe, then yes, then back to install, Multidisabler.zip flashed.
4.) restarted
That was it
I don't have a Super_SU or Magisk installed
greeting
Norbert

General [TWRP] [venus] Fixed TWRP Chinese Recovery for Mi 11

There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
I made a small mod to fix this.
Now it has default language by default (English) and that button was removed.
That jerk did not upload the sources, the changes were made only in the xml files, so there should not be any new bugs
Installation is the same as in original thread
Archive is .7z, but xda didn't allow this extension so i renamed it to .rar
Before and after
{
"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"
}

megapro17 said:
There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
I made a small mod to fix this.
Now it has default language by default (English) and that button was removed.
That jerk did not upload the sources, the changes were made only in the xml files, so there should not be any new bugs
Installation is the same as in original thread
Archive is .7z, but xda didn't allow this extension so i renamed it to .rar
Before and after
View attachment 5401889View attachment 5401891
Click to expand...
Click to collapse
Just a suggestion, why you don't share this file or put the link of this thread in the other thread, it will be useful for more people.

SubwayChamp said:
Just a suggestion, why you don't share this file or put the link of this thread in the other thread, it will be useful for more people.
Click to expand...
Click to collapse
Hmm, okay

megapro17 said:
Hmm, okay
Click to expand...
Click to collapse
Usefull, i'm here because of the link on the other thread
Thanks for your version !

megapro17 said:
There is afwul closed source twrp made by xinkid520. It has very dangerous bug, if you switch slot your device will be bricked, and the only way to repair is paid authorized account (btw do not pay more than 15$ whatsoever, it's a ripoff).
Click to expand...
Click to collapse
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .

Pikaone41 said:
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .
Click to expand...
Click to collapse
However you will agree it's a good fix for prevent mistake/issue

Can this twrp flash China dev rom pro? rom file larger than 4Gb

Pikaone41 said:
False ! the first time i try twrp, i switch the slot and yes my device was bricked. I just flash the engenering rom and reflash a global rom. my phone is working without paid .
Click to expand...
Click to collapse
How did you flashed engenering rom? I tried it, it required authorization anyway. Maybe your device wasn't completely bricked, not in 9008 mode?

Hi, I can't seem to copy any roms to my Mi 11 with TWRP, windows refuses to even start to try and copy and when i try to copy from my note 20 it gets to 99% and then fails?

skyler13 said:
Hi, I can't seem to copy any roms to my Mi 11 with TWRP, windows refuses to even start to try and copy and when i try to copy from my note 20 it gets to 99% and then fails?
Click to expand...
Click to collapse
flash from usb otg. this twrp is bad

Hi, how can I change to this fixed recovery from the original? Any mini tutorial?
Thanks in advance

neo9596 said:
Hi, how can I change to this fixed recovery from the original? Any mini tutorial?
Thanks in advance
Click to expand...
Click to collapse
From your actual TWRP > Install > (on bottom right) install image > choose new twrp > Reboot > Recovery
or from adb like the first time :
Code:
fastboot boot twrp-venus-fixed.img

Oh, so easy! Thanks. And I need to select inject again or no?
Thanks for your time

megapro17 said:
flash from usb otg. this twrp is bad
Click to expand...
Click to collapse
yeah i've already tried that but twrp doesn't see the usb otg for some reason, managed to fix it after an hour of searching. the method adb push rom.zip /sdcard didn't work but someone suggested adb push rom.zip /data and this has allowed me to copy the rom to my phone and flash it now.

Has anyone tried out this person's twrp
GitHub - LittleTurtle2333/android_device_xiaomi_venus-twrp: TWRP device tree for Xiaomi Mi 11
TWRP device tree for Xiaomi Mi 11. Contribute to LittleTurtle2333/android_device_xiaomi_venus-twrp development by creating an account on GitHub.
github.com

Pho3nX said:
From your actual TWRP > Install > (on bottom right) install image > choose new twrp > Reboot > Recovery
or from adb like the first time :
Code:
fastboot boot twrp-venus-fixed.img
Click to expand...
Click to collapse
What image to flash should i choose then 'Boot' ?

Development [RECOVERY] TWRP for ZenFone 8

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Click to expand...
Click to collapse
Images
Prerequisites
Unlocked Bootloader
Click to expand...
Click to collapse
Installation instructions
Fastboot Install Method:
You will need the platform-tools from the Android SDK on your computer. Find the Android command line tools section on the page linked and install the SDK tools package. From the SDK Manager, download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on their computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
Code:
fastboot boot twrp.img
Now you are booted into TWRP, but it is NOT permanently installed. To install it permanently, use the "Flash current TWRP" option in the Advanced menu. This will install the currently booted TWRP permanently to both slots. NOTE: If you were previously rooted, you will need to re-install the root apk/zip as the TWRP install will overwrite it!
Alternate Installation Method (requires prior TWRP installation, or if fastboot booted into TWRP already, start at step 3):
TWRP Image Install method:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed.
Download the latest version of TWRP appropriate for your device/firmware
Reboot to TWRP
Hit Install and tap the "Install Image" button in the lower right
Browse to the location of the TWRP image on your device and select it
Select "Install Recovery Ramdisk" from the partition list and swipe to flash
(Optional) If previously rooted, re-install root apk/zip, as the TWRP install will overwrite root.
Click to expand...
Click to collapse
Device Changelog
Current version: 3.6.0_11-0:
Initial version
Click to expand...
Click to collapse
Older Device-specific versions:
3.5.2_11-2:
Add vendor_boot to partition list
3.5.2_11-1:
Update super and qti_dynamic partitions size
Click to expand...
Click to collapse
Click to expand...
Click to collapse
TWRP Official Change Log
Downloads
Download
Latest Official versions
Sources
TWRP
Device tree
Kernel source
Click to expand...
Click to collapse
Known Issues
Device-specific
USB-OTG not working
Battery Status not working
TWRP Upstream
Android 12 decryption only works if no password/PIN/pattern is set (i.e. only default password)
Click to expand...
Click to collapse
Bug Reporting
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
{
"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"
}
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
Click to expand...
Click to collapse
Additional Help/Support
Live support is available on Zulip.
Click to expand...
Click to collapse

mine

I'll take 2

Maybe 3 to be safe

Thank you for this! Great to see a twrp thread

Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?

Captain_Throwback said:
USB-OTG not working
Click to expand...
Click to collapse
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!

dron39 said:
Is it temporary? Or at the moment it can not be fixed?
P.S. Thank you for your release!
Click to expand...
Click to collapse
It seems you asked the same question twice, but the answer is that the OP has the current status. If there are any changes in the future, it will be updated.

Undead_Son said:
Pinch me, I must be dreaming!
Edit: it works, but how to enter it again?
Click to expand...
Click to collapse
Once you're booted into TWRP, you can use the "Flash current TWRP" option under Advanced to install it permanently. If you were rooted, you'll then have to re-flash the root apk/zip.

Captain_Throwback said:
If you were rooted, you'll then have to re-flash the root apk/zip
Click to expand...
Click to collapse
What is partition to where it should be flashed?
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
And each time after firmware update we will need to reflash twrp, correct?
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?

dron39 said:
What is partition to where it should be flashed?
Click to expand...
Click to collapse
I don't understand your question. When you flash the root apk/zip, it'll take care of flashing where it's supposed to go. You don't have to worry about any partitions.
dron39 said:
You wrote that we will need to reflash root (.apk or .zip). But what if I have also custom kernel installed (Kirasakura) ?
Click to expand...
Click to collapse
I don't know about custom kernel, but you can always flash it again after you re-flash the root zip to make sure it persists if you're unsure. Flashing it again won't hurt anything.
dron39 said:
Shuld I "permanently" install recovery on stock kernel or it doesn't matter ? I just want to clarify, because as far as I understand magisk patches boot.img ?
Click to expand...
Click to collapse
It's up to you whether you want to install TWRP permanently, but the instructions focus on fastboot booting. I'm not sure how Magisk is relevant here, as that has no effect on TWRP.
dron39 said:
And each time after firmware update we will need to reflash twrp, correct?
Click to expand...
Click to collapse
Yes, but if you install the update in TWRP, you can choose the option to "Automatically install TWRP after zip" to keep TWRP if you have it permanently flashed.
dron39 said:
And I haven't found information about our device on twrp.me (Devices->Asus). Will you add it there later?
Click to expand...
Click to collapse
This is a prerelease version. The Android 11 TWRP tree hasn't been officially released. The ZF8 page will be there once the release is official. There's already a markdown patch ready for that time.

What does "unable to locate storage device" mean?

Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper

HyperCriSiS said:
Hi,
I unlocked my device with the asus unlocker and rooted succesfully.
But when I try flash TWRP with fastboot I get:
Sending 'boot.img' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Has anybody an idea whats the issue here?
Regards,
Hyper
Click to expand...
Click to collapse
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.

Captain_Throwback said:
Are you sure you're in bootloader, and not fastbootd? Also please confirm that you're attempting to fastboot boot as per the OP instructions.
Click to expand...
Click to collapse
Yes, I was in fastbootd
Thank you so much, it is working very well

New test version uploaded. Thanks to @micky387 for his help with the TWRP tree!

With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"

HyperCriSiS said:
With newest version MTP does not work anymore.
I deleted the device and the new detected device name is different. It was "Zenfone 8" before and now "Asus_I006D"
Click to expand...
Click to collapse
I changed absolutely nothing related to MTP, and it continues to work fine here.
The device name in TWRP was always ASUS_I006D. If you happened to connect the device to your PC in Android first, then that's probably why it showed up as "ZenFone 8". But when you deleted it the TWRP default got set as the name.
Can anyone else confirm whether MTP is working for them on the latest version? If you're using Windows, it's possible some update broke something on your end.

Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.

HyperCriSiS said:
Yes, Microsoft often messed with the MTP drivers. In the device manager I deinstalled everything related to the Zenfone and reinstalled, but still does not work.
TWRP throws some errors. Maybe this is the issue? I also reinstalled it again.
Click to expand...
Click to collapse
That looks very broken. But a screenshot is very unhelpful to determine root cause. The OP makes it clear that logs are required to get assistance. So please provide a recovery log and logcat so that I can review the problem.
Is Android working okay? Seems like something else is going on there. Did you install anything? I'm going to need more details of how exactly you got to this point.

How To Guide [GUIDE] Root OnePlus 10R

DO THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE IF ANYTHING HAPPENS TO YOUR DEVICE.
Also, Please note Unlocking bootloader will wipe your data, so make sure to backup your important data.
This guide can aslo be followed to root OnePlus ACE just make sure to use OnePlus ACE's boot.img.
Click to expand...
Click to collapse
Prerequisites -
You have the latest adb, fastboot, Oneplus & MediaTek drivers installed.
You have the latest platform tools.
STEP #1 - UNLOCKING THE BOOTLOADER
1. Download Platform Tools, extract it in C drive.
2. Enable OEM Unlocking & UBB debugging from developers' options.
3. Connect your device to PC, and open cmd in the platform tools folder by typing cmd in the address bar.
4. Run the following command and approve USB debugging prompt on your device. [If you are not getting an output then update your adb drivers]
adb devices
Click to expand...
Click to collapse
5. Run the below command to boot your phone into fastboot mode. After running the command you'll see a black screen with fastboot mode written in very small font.
adb reboot bootloader
Click to expand...
Click to collapse
6. Run the below command to check if your device is getting detected in fastboot mode or not.
[If the command is not giving any output/ is waiting for device then you need to update your fastboot drivers]
fastboot devices
Click to expand...
Click to collapse
7. Run the below command to unlock the bootloader. [I know it's not 'fastboot oem unlock']
fastboot flashing unlock
Click to expand...
Click to collapse
8. Run the below command to reboot your device after unlocking
fastboot reboot
Click to expand...
Click to collapse
9. Setup the device and perform the above Step2 again.
STEP #2 - EXTRACTING BOOT.IMG
10. I have written the steps to extract the boot.img in the below xda thread. Its always recommended to extract boot.img yourself.
[10R Only] Find already extracted boot.img here:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Or follow this below guide to extract it yourself:
[GUIDE]How to extract img(boot.img, etc...) from payload.bin using payload-dumper-go.
For 10R only: I have uploaded a few of the extracted boot.img, before extracting if you want you can look for the required boot.img here: https://www.mediafire.com/folder/kyn2p5mhde7nn/boot.img 1. Download and extract payload-dumper-go. 2...
forum.xda-developers.com
Click to expand...
Click to collapse
STEP #3 - PATCHING THE BOOT.IMG
11. Install lastest Magisk manage apk(V24 or above) and transfer the extracted boot.img into your device's internal storage.
12. Launch the Magisk Manager app and tap on the Install button next to the “Magisk is not installed” message.
13. In the next popup that appears, tap on Install followed by Select and Patch a File.
{
"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"
}
14. Now browse to the stock boot.img file and select it.
15. Magisk will now begin patching the file, which should take a few seconds only. Once that is done, you should get an “All Done” message.
16. Once that is done, head over to the Downloads folder and you should see the magisk_patched.img file.
STEP #4 - FLASHING PATCHED BOOT.IMG
17. Transfer the magisk_patched.img to the platform-tools folder on your PC.
18. Again, reboot the phone to fastboot mode and run the following command to flash the patched boot img -
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
If the above command is not working, execute following commands:
fastboot flash boot_a magisk_patched.img
Click to expand...
Click to collapse
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
19. Reboot the device and check the status on the Magisk manager app.
20. Done. Cheers!!!

Hi, I've replied to you in a thread and found out that my phone is an OnePlus Ace with OnePlus 10R rom. I have no problems with it except for Netflix not having widevine L1. My idea is rooting the phone with Magisk and using the safetynet module to hide it from Netflix, which I don't know if it'll work or not. But since my phone is Ace with 10R rom, I presume the bootloader is already unlocked. I've looked through the OnePlus OS Update telegram channel you provided but there's no rom for my model - CPH2411

rafaelgirotti said:
Hi, I've replied to you in a thread and found out that my phone is an OnePlus Ace with OnePlus 10R rom. I have no problems with it except for Netflix not having widevine L1. My idea is rooting the phone with Magisk and using the safetynet module to hide it from Netflix, which I don't know if it'll work or not. But since my phone is Ace with 10R rom, I presume the bootloader is already unlocked. I've looked through the OnePlus OS Update telegram channel you provided but there's no rom for my model - CPH2411
Click to expand...
Click to collapse
If you are not getting on the Telegram channel you can download Oxygen Updater from playstore and download the firmware from there. It's a 3rd party app.

yashaswee1708 said:
If you are not getting on the Telegram channel you can download Oxygen Updater from playstore and download the firmware from there. It's a 3rd party app.
Click to expand...
Click to collapse
Thank you, the app worked, but turns out the bootloader was locked. If I unlocked is there a way to lock it back? And if so, will it bootlop if using this patched boot image?

rafaelgirotti said:
Thank you, the app worked, but turns out the bootloader was locked. If I unlocked is there a way to lock it back? And if so, will it bootlop if using this patched boot image?
Click to expand...
Click to collapse
You can not lock the bootloader and keep root.
If in future you want to unroot & lock the bootloader then you can try this command. Note this will wipe all your data -
fastboot flashing lock

Okay, just rooted the phone, the root works. But not for my purpose of having Widevine L1 on Netflix. Actually Netflix isn't showing on Play Store anymore, even with safetynet fix. I'm gonna unroot and lock bootloader again. Thanks for the help!

With ColorOS, I don't manage to patch the boot.img in Magisk. Can any kind soul upload the patched img file for me or tell me a way around this? Thanks
(I see there is an alternative in Chinese, but haven't find it useful https://www.coolapk.com/feed/359951...d=2398107&shareFrom=com.coolapk.market_12.4.1 )

i9o said:
With ColorOS, I don't manage to patch the boot.img in Magisk. Can any kind soul upload the patched img file for me or tell me a way around this? Thanks
(I see there is an alternative in Chinese, but haven't find it useful https://www.coolapk.com/feed/359951...d=2398107&shareFrom=com.coolapk.market_12.4.1 )
Click to expand...
Click to collapse
Are you extracting the boot.img from the exact same firmware version you are currently on?

yashaswee1708 said:
Are you extracting the boot.img from the exact same firmware version you are currently on?
Click to expand...
Click to collapse
Thank you very much, that could actually be the problem indeed.
The phone updated to the last ColorOS firmware and I wasn't able to retrieve the repository of the OS versions. So I downloaded the only one I could find, from the Telegram OnePlus ace group. It could be a slightly older version.
It's annoying that I cannot find the repository of all the versions.
The Chinese H2OS web site was nice. I couldn't find the equivalent one for ColorOS...

I keep on not being able to find the link where to download the latest ROM.
https://yun.daxiaamu.com/OnePlus_Roms/ this is a repository not completely up to date, since the A20 version is missing...

i9o said:
Thank you very much, that could actually be the problem indeed.
The phone updated to the last ColorOS firmware and I wasn't able to retrieve the repository of the OS versions. So I downloaded the only one I could find, from the Telegram OnePlus ace group. It could be a slightly older version.
It's annoying that I cannot find the repository of all the versions.
The Chinese H2OS web site was nice. I couldn't find the equivalent one for ColorOS...
Click to expand...
Click to collapse
Yeah. You need the boot img for the exact same version. And you need to patch everytime after a new update. Try searching here - https://t.me/OnePlusOTA

i9o said:
I keep on not being able to find the link where to download the latest ROM.
https://yun.daxiaamu.com/OnePlus_Roms/ this is a repository not completely up to date, since the A20 version is missing...
Click to expand...
Click to collapse
https://t.me/OnePlusOTA here too last post was of A.18

Not up to date but who wanti it
ColorOS & OxygenOS
一加OnePlus Ace - 一加手机官方ROM - 一加手机官方ROM下载
本站提供一加全机型ROM下载，包括一加Ace 2V、ACE2、Ace/10R、一加10 Pro、9Pro、9RT、9R、8T、8 Pro、一加8、7T Pro、7T、7Pro等全系一加机型的升级全量包、降级包、9008线刷救砖包等各种官方和原厂ROM，全部资源完全免费，不限速，无需登录
yun.daxiaamu.com