Related
I'm trying to understand the Android Boot Process and the new additional security measures/restrictions put in place by the device manufacturers.
So far I've read through these posts on XDA, Lineage OS Blog and some others. I've understood some and still confused about others.
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
[INFO] BOOT PROCESS: ANDROID vs. LINUX
Qualcomm’s Chain of Trust
Android Boot and Recovery Images
Dissecting the Android OTA Update System
I've flashed custom ROM and TWRP on my old phone but it didn't have the new security measures in place and I didn't bother about encryption then (The entire files on the device is accessible from the recovery).
I have some doubts about the encryption and other stuff.
1) When we are running with the stock recoveries, user files are inaccessible(because those stock recoveries don't provide that function).
How can I keep my files safe while using TWRP or similar recoveries?
ie How does FDE work with the custom recoveries?
2) I've read about some users complain that FDE got triggered after firmware upgrade. In such cases what key does it use?
3) I've read on Google's website that it allows users to boot with custom keys. Is that enough for 'Certified Status' on Google Play.
4) What all modifications trigger SafetyNet?
I understand that modifying /system triggers it, so using custom kernels would trigger it Right?
Kindly help me out. I'm sorry for any mistakes.
Bump
Bump
Bumped
Did somebody try the Beta/Dev Rom for the Poco F2 Pro? How it is?
Looks like in 2 weeks Google will release stable Android 11.
about Android11
it is unstable for now,some bank apps are crashed,and system is constantly reboot itself,however,you can enjoy new GPU driver.
Using for a while on China Developer ROM. There are no crashes or performance issues, but for me biggest deal breaker is that DJI Go 4 app isn't working at the moment. I hope they update it soon to work with Android 11.
Does the beta come with A/B partition for seamless updates? I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
(Currently, we're on an A-only partition with MIUI12 & Android 10)
You could easily answer my question by installing Treble Check (from KevinT.) on the Play Store. The app checks which partition system is used on the device (currently says "Seamless System Updates Unsupported" with Android 10).
Eidenz said:
Does the beta come with A/B partition for seamless updates? I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
(Currently, we're on an A-only partition with MIUI12 & Android 10)
You could easily answer my question by installing Treble Check (from KevinT.) on the Play Store. The app checks which partition system is used on the device (currently says "Seamless System Updates Unsupported" with Android 10).
Click to expand...
Click to collapse
I have EU ROM Android 11 Beta weekly 20-08-20 installed. Treble Check says Only A partition, Seamless System updates Unsupported".
Alrighty, thank you.
I hope this will be in the first release of Android 11 in September. They are planning to make a virtual A/B partition for all devices.
Eidenz said:
I heard Android 11 will require devices to be in an A/B partition system, which would come handy for OTA updates on rooted devices.
Click to expand...
Click to collapse
AFAIK only devices launched with Android 11 are required to adopt it's new features like A/B partitions and enforced background processes handling.
Thats why we will not get it.
{
"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"
}
Team Win Recovery Project [aka TWRP] is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
***
Hi there,
This is the unofficial build based on the official TWRP sources for the POCO X3 Pro !
WHAT'S WORKING ? [Everything +++]
- Backup/Restore
- Encryption support : all A11 custom roms
- adb sideload
- fastbootd : for flashing GSI builds and other stuff ! (advanced users only ++++)
- flashing special images
- switch between custom roms without any issue
- miscellaneous : OTG, brightness & vibration control
INSTALLATION PROCEDURE [First Time]
- Unlock your bootloader
- Enable ADB from MIUI Settings > Developer options
- Plug your USB cable to your Windows PC and type :
adb reboot bootloader
then :
fastboot flash recovery <twrp-xxxx>.img
fastboot reboot recovery
. For MIUI users Only :
After a long investigation, i find out that the command " fastboot boot <twrp-xxxx>.img " is no longer working in Android [11] to avoid overwriting TWRP by the Stock MIUI Recovery. Because the code to do this wicked job after every reboot is inside the stock "init" binary.
So to finally stop this mess :
(after doing)
fastboot reboot recovery
Flash Magisk (rename it to .zip) in TWRP menu ... This will overwrite the original "init" with the Magisk one ... That's All !
This workaround should work for all devices with android 11 oem software pre-installed ! (tested on my oneplus 8 too)
DATA BACKUP & RESTORE PROCEDURE
- Create your backup in the internal storage, for faster process.
- Transfer the created "TWRP" folder to your PC/Micro-SD/USB Stick ... for future use & emergency !
- To restore "Data" again, just do the simple "wipe" before or restore on the fly !
If you do "format", your encryption files will be lost and you can't restore your "data" again, unless you boot to the system then reboot to TWRP to do the simple wipe again and restore !
TOOLS [must read +++]
. TWRP Universal Script
. Google Essential Pack
. LOS 18.1 SafetyNet Fix
. GCam Fix : AOSP 11 / OSS 11
. Scoped Storage Disabler [11]
DOWNLOAD
Here
XDA : DevDB Information
TWRP, Tool/Utility for the POCO X3 Pro
Contributors
@gringo80
Source Code
1 : https://github.com/TeamWin
2 : Prebuilt
Version Information
Stable Release : 2021-11-24
Initial Release : 2021-11-10
Reserved
Update 2021-11-24 : Highly Recommended
- fstab update
- keymaster fix : decrypt without error
Update 2021-11-22 :
- gatekeeper fix : unlock & decrypt with patterns
Update 2021-11-19 :
- split prop.default to show the true name of the device when connected : vayu or bhima
- update fastbootd : now it's fully working as a stock recovery +++
- general code cleanup
- improve the overall stability & performance +++
- ramdisk : use LZMA compression
Update 2021-11-10 :
- initial release
- fstab : reworked from scratch
- simplified decrypter script (no useless stuff, please)
- support added for fastbootd & adb sideload (all credits go ... to me !!!)
- use the official xiaomi blobs (prebuilt untouched : dtb, dtbo & kernel) ... for optimal performance and stability (from Global 12.5.5.0)
[What does it mean in english, please ?]
Stock Recovery Core with TWRP UI !
I tried this version of TWRP in the hope that it would handle the encrypted /data partition.
ADB doesn't appear to be working.
The menu on the bottom right of the screen returns the following error message(s)
Android Rescue party trigger! Possible solutions?
[...]
The reported problem is `--reason=init_user0_failed`
E: Unable to decrypt FBE device
Click to expand...
Click to collapse
I also tried ADB Sideload to load a ROM which got the same error on TWRP and an error on my PC:
adb: failed to read command: Success
Click to expand...
Click to collapse
and Sideload then stopped.
I don't have such issue ... make sure you are using the latest adb & fastboot binaries /or use the one in the link (OP) !
THREAD CLEANED
Hi! Just dropped in to do a little cleanup. The thread owner doesn't want discussion regarding/sharing of other TWRP images, kindly respect that and keep the posts on-topic. Additionally, if something isn't working, please try and share as much information as possible so that the developer can look into it.
I'll also take the opportunity to remind everyone of Rule 2 of the Forum Rules, which needs to be adhered to at all times, at all the places, here on the forum:
2. Member conduct.
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
2.5 All members are expected to read and adhere to the XDA rules.
Click to expand...
Click to collapse
Please consider this notice as a friendly reminder to keep it civil, on-topic and refrain from responding to posts that you think are offensive or hateful. Just report if you feel something isn't right and let us take care of it for you, so that we can make your experience on the forum better. Report, not reply should always be the mantra.
Regards,
shadowstep
Forum Moderator
New Update
[OP]
Hi, I just installed your TWRP via Image direct to recovery partition, rebooted to system, rebooted to TWRP and now I am stuck on "decrypt data". I have to use my pattern for user 0, but it fails with "Pattern failed, please try again". When I enter my pattern, it says "Attempting to decrypt FBE user 0...." and then it fails. I can "cancel" it, so I am in TWRP right now. I can't do a backup for "user 0" (my only user) because I can't decrypt it.
TL;DR: I can't decrypt the data partition for user 0 with the pattern, it fails.
cavinrocks said:
Hi, I just installed your TWRP via Image direct to recovery partition, rebooted to system, rebooted to TWRP and now I am stuck on "decrypt data". I have to use my pattern for user 0, but it fails with "Pattern failed, please try again". When I enter my pattern, it says "Attempting to decrypt FBE user 0...." and then it fails. I can "cancel" it, so I am in TWRP right now. I can't do a backup for "user 0" (my only user) because I can't decrypt it.
TL;DR: I can't decrypt the data partition for user 0 with the pattern, it fails.
Click to expand...
Click to collapse
wich rom are you using ?
are you using a mod ?
I am using the MIUI by xiaomi.eu 12.5.5 stable
A fix is coming in the next build !
Thanks
Thank you for your work!
New Update
[OP]
Now the data encryption works, the pattern is accepted. Thank you very much!
Spoiler: Error 255 in createTarFork
When I try to do a backup, I get:
Error 255 in createTarFork() process
But I had this error already with the old TWRP, so I know it is not the fault of your recovery. Iam still looking for a solution only, so no worries.
Solved with deleting the /data/extm Folder nevermind.
cavinrocks said:
Now the data encryption works, the pattern is accepted. Thank you very much!
Spoiler: Error 255 in createTarFork
When I try to do a backup, I get:
Error 255 in createTarFork() process
But I had this error already with the old TWRP, so I know it is not the fault of your recovery. Iam still looking for a solution only, so no worries.
Solved with deleting the /data/extm Folder nevermind.
Click to expand...
Click to collapse
Never create a backup with password/pattern/fingerprint !!!
New Update Highly Recommended
[OP]
Please download the latest build from 2021-11-24 ... there was an error in the previous build !
Cheers
A12 support planned?
StimuL99 said:
A12 support planned?
Click to expand...
Click to collapse
When official A12 comes out !
The thread was cleaned and some posts were removed. Please be respectful towards each other and stick to the topic of development.
Thanks,
Funk Wizard
Forum Moderator
In this new version, on Poco X3 Pro, after installing rom it does not ask confirmation to reboot Goes directly.
PD: decrypting DATA still does not work, right? https://forum.xda-developers.com/t/rom-miui-21-11-24-eliterom-a11-miui12-6-for-poco-x3-pro.4270633/ used.
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator
Dear members,
Which partitions have to copy to save backup related to IMEI number, data of modem, bluetooth, fingerprint, and other important system partitions on OnePlus 8 phone? I mean safety before flashing custom ROMs and possibly returning to the factory system Oxygen OS 11 in case of failure.
I am asking for your possible suggestions,
thank you.
OnePlus 8 Pro 256GB Device
OOS 11.0.10.10
TWRP 3.6 installed
Magisk 23.0 installed
Hello
To try to help you, I can tell you what information I was able to recover about backups before flashing roms other than OOS provided OTA by OnePlus.
It is necessary to back up, at least, the following partitions:
- Boot
- DTBO
- Recovery
- Super System (system_ext product vendor system)
These four partitions seem to be essential to operate the device if the custom rom is not suitable.
If you perform a "Nandroid" backup with TWRP, you can, as a precautionary measure, backup all partitions and restore them together as well and you will have an exact reproduction of all files, presentations, settings, apps and their data , etc
It is advisable to remove any password or unlock pattern to unlock the device before performing the backup.
Finally, I found a site that explains the different partitions for Android 11 but the names of these partitions seem not to be quite the same for OOS 11
Overview | Android Open Source Project
source.android.com
I don't know if my information will be useful to you.
I will be interested in what you can learn about this subject of safeguarding.
Best regards,
Thank you for the response and your help.
I have the same device.
It seems that there is also an issue such as the persistent partition, the loss of which may cause problems with the fingerprint unlock function. In the same forum section, users requests this partition after losing it after using the MSM tool.
It is not entirely clear to me which partitions in OnePlus 8 contain the IMEI number, modem data, bluetooth, etc. I found a hint after installing the Partitions Backup by wanam app, where the essential partitions for the backup copies are marked in color.
These are:
- MDM1M9KEFS1, MDM1M9KEFS2, MDM1M9KEFS3, MDM1M9KEFSC, MODEM_A, MODEM_B, MODEMDUMP, MODEMST1, MODEMST2
However, when it comes to a copy of Nandroid from TWRP, they are listed there:
metadata, Data (excl. storage), Boot, EFS, Modem, Persist, Recovery, VBmeta and Super.
There are 2 questions: 1. Which of these partitions to include in the OOS backup 2. What is safer to use: fastboot mode or TWRP?
Best regards
Hello
I am happy to share with you my "meager" knowledge regarding the OnePlus 8 Pro device and TWRP
With my old devices (LG G3, Samsung S7, Edge), I used LineageOS roms a lot because it was a way to have the latest versions of Android, up to the equivalent of Oreo (Android 8)
To perform the backups with TWRP, I selected all the partitions and I also restored all the partitions: I then had a strictly operational and identical device at the time of the backup.
Since buying the OnePlus 8 Pro, in the fall of 2020, I have only installed Magisk, which gives access to the Root of the device and all OTA versions of OxygenOS, up to the current one: 11.0. 10.10
I have available Magisk installation links for rooting and lossless OTA update installations of Magisk.
I hadn't used TWRP because the latest versions weren't suitable for OnePlus 8 and Pro or T series beyond OxygenOS 9.
On the official TWRP website, the links for version 3.6 do not bring a file.
You have to use the XDA link
[TWRP][3.7.0-13][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA 3]
TWRP for OnePlus 8 and 8 Pro TWRP is an open source, community project. TWRP development is done by a large support community with many people who are willing to answer questions and help people with their devices either through our IRC...
forum.xda-developers.com
To get to the TWRP file download link in version 3.6
OP8/8PRO TWRP - Browse /beta_builds at SourceForge.net
sourceforge.net
For my part, I downloaded the "twrp-op8-3.6.0_11-infected-b5.img" file which has since been updated to version twrp-op8-3.6.0_11-infected-b7.img ago 10 a.m. as of this writing.
I installed the file as indicated on the thread:
fastboot flash recovery_a twrpname .img
fastboot flash recovery_b twrpname.img
Then, I was able to restart the OnePlus 8 Pro in Recovery mode (rather slow loading) and I then performed my first full “Nandroid” backups by selecting all the boxes (see screenshots)
For the moment, I stopped there: I did not dare to restore these backups, to find out if the device worked in a completely identical way, before launching a custom rom other than the original roms provided by OnePlus: I was unable to find any threads relating to "Nandroid" backups of the OnePlus 8 series.
On the other hand, I never used the MSM tool and I always did the backup/restore with TWRP which I was used to, I never did with fastboot commands, except for installing TWRP 3.6.
Above all, I have never tried to modify the partitions of the devices, old or current. My knowledge is nil in this area, especially with the new “dynamic” scores!!
I've tried app backups with "adb" commands but haven't been able to restore app-related data like I can with the "Swiftbackup" app discussed below.
Finally, so far on the rooted OnePlus 8 Pro, for my app backups, I use the "Swiftbackup" app.
Swift Backup - Apps on Google Play
A simple, fast and smart backup solution for Android smartphones
play.google.com
which works perfectly identical to "Titanium Backup"): this last application has been obsolete for several years and is no longer updated for the latest versions of Android (9 and beyond)
This "Swiftbackup" app performs a backup / restore of all installed apps WITH their data, locally and / or on the cloud, with or without system settings and apps on the condition of having a rooted device.
For my SMS, MMS and call log backups, I use the SMS Backup and Restore application: https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore
To tell the truth, I don't really need TWRP but I'm curious and I wanted to see the possibilities brought by TWRP 3.6, only suitable for OxygenOS 11.
This is where my knowledge is that I share with you.
The version of OOS 12 should arrive during the 1st quarter (already released in India) but it will be necessary to wait for the version of TWRP which will be adapted to the latest OS from OnePlus.
I remain of course at your disposal to continue to exchange about TWRP, within the limits of my knowledge!!
Best regards,
Thanks for your message. However, I'm afraid that is not exactly what this thread was about.
Regards
I have an in2017 running on 10.5.22in55cb. Any idea how to root? I tried twrp and that failed. Have not been able to find a boot.img either. Thanks.
C:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
This is mostly based on Ungeskriptet's work on TB-J716F. Many thanks to his work. Additionally thanks to the devs of twrpdtgen utility which is very useful for obtaining some very helpful information about the device from a stock recovery image.
The recovery is currently flashable and functional. You may refer to the flashing guide for J716F to flash the recovery on this device as the procedure is the same.
The following stuffs were tested working: Decryption (A11 only), Backup, Wiping, Touch, Fastbootd, MicroSD card.
Other functionalities should behave similar to TB-J716F TWRP.
Not working stuffs: Vibration, busybox (haven't really checked but should be similar to TB-J716F).
Device tree: twrp_device_lenovo_Q706F
UPDATE (Jan 14, 2023): Updated builds of TWRP 3.7.0 for Android 11 (A11) and 12 (A12).
twrp-Q706F-A11-3.7.0-r2: This is for Android 11 GSIs. Can only reliably decrypt Android 11 /data partitions.
twrp-Q706F-A12-3.7.0-r2: This is for Android 12 GSIs. CANNOT decrypt Android 11 /data partitions. Need further testing for Android 12 /data partitions.
Neither build can decrypt Android 13 /data at the moment. If security is not a concern for your use case, you may consider using a tool such as DFE-NEO to disable force encryption of /data. This will enable TWRP to access your /data partition under all circumstances and will save you the hassle of having to back up the entire /data partition when going back and forth between different GSIs.
The updated build contains many more options that can be backed up in case needed. Additionally, some parameters necessary for decrypting A12 /data has been added. Unfortunately, from current feedbacks, it seems decryption is only possible if not using any lock (PIN, Pattern, or Password). Also, with these parameters, it is now possible to make A12 TWRP determine the lock type of A11 /data partition, but it cannot be decrypted even with the correct credential provided.
EXPERIMENTAL: I've added a nuclear option for /data backup, the "Data Image" option. This will back up your /data partition as a whole regardless of its content. You need a large enough external SD card for this option to work, as TWRP's "Enable Compression" doesn't appear to do anything for emmc backups.
!! WARNING !! - Before backing up the entire /data partition, BE SURE TO REMOVE ANY SCREEN LOCK, as after restore, while your system will boot, YOUR CREDENTIALS MAY NOT BE ACCEPTED ANYMORE! YOU WILL LOSE ACCESS TO YOUR USER FILES.
The resulted backup would depend on the size of your internal storage. In my case, the data partition was about 230GB in size, and the whole backup process as well as digest creation took about 2.5 hours in total.
Backing up of the entire /data partition is still experimental, and make sure to check that you're backing up to an external storage if you checked the "Data Image" option!
Spoiler: Old Changelogs
Apr 9, 2022: A second version has been uploaded, using blobs from TB-Q706Z_S212073_220222_ROW. The recovery's decryption mechanism appears to work okay. Haven't tested other stuffs but I don't think there would be too much difference compared to the initial build, which was based on PRC blobs.
Still using the Q706F product name. Not sure if the same recovery can be used as-is on a Q706Z (5G variant).
UPDATE (Jul 7, 2022): I'm uploading two new builds. Both builds can now mount the MicroSD card.
UPDATE (Dec 3, 2022): I've made two builds of TWRP 3.7.0 for Android 11 (A11) and 12 (A12).
twrp-recovery-Q706F-A11-3.7.0-r1: This is for Android 11 GSIs. Can decrypt Android 11 /data partitions. Decryption of Android 12 /data is unlikely.
twrp-recovery-Q706F-A12-3.7.0-r1: This is for Android 12 GSIs. CANNOT decrypt Android 11 /data partitions.
TESTING NEEDED (A12): As of TWRP 3.7.0, support for decryption of Android 12 /data is considered formal and should in theory work in most cases. I'm still using Android 11 GSI so I cannot test this myself, so users who are on Android 12 GSIs can test whether it's possible to decrypt your Android 12 /data partitions with the A12 build.
Spoiler: Development Notes
The recovery kernel and the vendor libraries I used for the device tree were dumped from my own device when I first started experimenting with phh-AOSP GSI, though I think files from the ROW image should also work on all devices. My device was on ZUI 13.0.437_211106 PRC at that time, but I'm using ROW kernel and vendor now since they work correctly on GSI.
Some main issues encountered during porting:
- Touchscreen input was rotated by default, that I have to add some configuration parameters to correct it.
- Decryption didn't work initially. Apparently Q706F used some different parameters compared to J716F according to fstab.qcom from my device's vendor image.
In overall, Q706F is not too much different from J716F as they use the same SoC and most of the internal configurations are identical between the two (so very few changes were made to the configuration files during porting).
I currently don't use MicroSD card on this device at the moment, but from what I saw in the recovery, it doesn't appear to expose /dev/block/mmcblk* like most devices, even after I inserted one. I'm not sure where I should use to access the SD card device.
UPDATE (Jul 7, 2022): It seems the tablet does expose the MicroSD card as /dev/block/mmcblk0p1, and I could already mount it via command line using default options to begin with. As a result, adding formal MicroSD card support turned out to be easier than I thought.
UPDATE (Jan 14, 2023): Everyone has been very helpful. Looks like twrp.flags is the right place to add partitions meant to be backed up. In order to make backups as complete as possible, a lot of partitions have been added thanks to everyone's effort.
Great to see some development many thanks.
I tried to flash gapps_full_11.0 downloaded from https://opengapps.org/,but it says partition space is insufficient , and I have already build a full aosp11_r48 system.img along with allocating about 4000M capacity to system partition. Weird
ZTE AXON 7 said:
I tried to flash gapps_full_11.0 downloaded from https://opengapps.org/,but it says partition space is insufficient , and I have already build a full aosp11_r48 system.img along with allocating about 4000M capacity to system partition. Weird
Click to expand...
Click to collapse
Are you using a non-vndklite GSI? It's not trivial to mount system r/w with such GSI. You need vndklite GSI for that, or simply grab a bgN variant (g denotes gapps included).
Wait... which ROM are you using exactly? AOSP11 r48? I don't recall seeing any ROM development for this tablet.
Actually I built aosp for my lenovo tablet p12 pro
{
"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"
}
ZTE AXON 7 said:
Actually I built aosp for my lenovo tablet p12 pro View attachment 5504739
Click to expand...
Click to collapse
Will you be publicly releasing this ones it's all working?
Dang I just stumbled onto this, didn't realize someone had already put in the work to get twrp, but I have already updated my p12 to the latest build. Any chance of updating decryption to the most current build? I assume this will be the last android 11 build while they work on 12L. I personally won't ever be updating this device to 12 due to the major stepbackwards in ui google is taking so having a final twrp on the last 11 build would be great.
DaConcho said:
Dang I just stumbled onto this, didn't realize someone had already put in the work to get twrp, but I have already updated my p12 to the latest build. Any chance of updating decryption to the most current build? I assume this will be the last android 11 build while they work on 12L. I personally won't ever be updating this device to 12 due to the major stepbackwards in ui google is taking so having a final twrp on the last 11 build would be great.
Click to expand...
Click to collapse
Sorry for a late response. Which build are you currently on?
I'm not sure how decryption works with updates but things are indeed more complicated after taking encrypted /data into consideration.
Maybe I can consider tailoring the TWRP tree against a newer ROW build when I have time, but I won't be able to do in-depth tests myself as the current build configuration on my device is quite stable that I don't want to change it in the near future.
A second version has been released using TB-Q706Z_S212073_220222_ROW blobs.
It decrypts my /data just fine, as I'm currently using Android 11 GSI. Looks like the vendor or other components don't really matter for decryption as long as the system is still on Android 11.
Simply put, until TWRP formally supports Android 12, it's not possible for TWRP to decrypt /data partitions created by Android 12.
I am actually still on TB-Q706F_S212017_211231_ROW. OTA doesn't play nice after rooting so haven't had a chance to update yet but I will so I can give it a spin.
LSS4181 said:
A second version has been released using TB-Q706Z_S212073_220222_ROW blobs.
It decrypts my /data just fine, as I'm currently using Android 11 GSI. Looks like the vendor or other components don't really matter for decryption as long as the system is still on Android 11.
Simply put, until TWRP formally supports Android 12, it's not possible for TWRP to decrypt /data partitions created by Android 12.
Click to expand...
Click to collapse
Just curious how does the stylus play with a GSI? does all the pen funcionality work ok?
DaConcho said:
Just curious how does the stylus play with a GSI? does all the pen funcionality work ok?
Click to expand...
Click to collapse
You can just pair the Precision Pen through Bluetooth.
I'm not sure about vendor-specific features, but basic functionality (as a pointer device) should work okay.
LSS4181 said:
A second version has been released using TB-Q706Z_S212073_220222_ROW blobs.
It decrypts my /data just fine, as I'm currently using Android 11 GSI. Looks like the vendor or other components don't really matter for decryption as long as the system is still on Android 11.
Simply put, until TWRP formally supports Android 12, it's not possible for TWRP to decrypt /data partitions created by Android 12.
Click to expand...
Click to collapse
Just updated to the latest build and flashed the V2 of twrp. I am getting stuck on the TWRP splash screen after booting to recovery
Disregard, just reflashed Magisk and gave it a minute and its solid now. Thanks for building!
Worked great on the US version of the P12 Pro. To unlock the bootloader on the US version all that was needed was "fastboot flashing unlock" which brought up the unlock bootloader prompt. Flashed magisk without issue.
Worked great on the XiaoXin Pad with ZUI.
What I did:
Full backup (all part-s)
Full restore
Restore only super.
Flashing modified RW super (due to unsucceful flashing modified RW super via fastboot) via Install -- Install img
Full backup using OTG USB disk.
All this working beautiful. Many thanks to creator!
Added two new builds. One for Android 11, the other is a testing one for Android 12. SD card should be working now.
I only tested the Android 12 one briefly without flashing. It seems the Android 12 build cannot decrypt my Android 11 /data partition, and is a bit bigger in size compared to the Android 11 one. Only the Android 11 build decrypts my /data at the moment, and I've successfully flashed it into my device.
Need someone who's on Android 12 GSI to test whether it's possible to decrypt Android 12 /data. However, according to the README of the minimal TWRP manifest's A12.1 branch, that decryption is still WIP and may only work when screen locks (password/PIN/pattern) are disabled.
TWRP v3 for A11 works with SD cards, tested on ZUI.
SD card has exFAT file system.
Many thanks to the author from me.
TWRP for A12 is not working with A12 Global firmware (TB-Q706F_USR_S410033_2208041209_Q00050_ROW)
The tablet stuck on Lenovo logo.
Can you try to fix this ?
Works for rooting Lenovo P12 Pro with magisk
Android: 12
Model: TB-Q706F
Build #: TB-Q706F_S410033_220804_ROW
Software Version: TB-Q706F_RF01_220804
Decryption of /data doesn't work, SD card mounting doesn't work in TWRP, works fine once booted.
Edit:
make sure to disable automatic software updates in the updates section and disable applying updates on reboot in the developer settings. Otherwise you might end up semi-bricked (black screen on boot) if it tries to update on it's own, and the only way to fix it is to restore the stock recovery and factory reset and start over.
A late update. I've put up two TWRP 3.7.0 builds. One for Android 11 and the other for Android 12.
Added some more partitions that could be backed up. Many thanks to @f1tm0t for the changes.
I also updated the vendor blobs in the Android 12 build to TB-Q706F_USR_S410033_2208041209_Q00050_ROW just in case, but from the looks of it the vendor of this more recent stock FW still says Android 11, despite the system image is indeed Android 12, so this change may not be immediately necessary.
Need Android 12 users to test whether decryption works now, as since TWRP 3.7.0 support for decrypting Android 12 /data partitions is now formal.