Related
I'm not the Author, the author is wzsx150 from LR.TEAM
WZSX’s TWRP is well-known as the Chinese version of TWRP due to the language default is in Chinese. However, you can switch to English within TWRP user settings it's easily. switched. You can follow the instructions on this link to change the language to English: https://miui.blog/any-devices/lr-tea...inese-english/
Xiaomi 8's LR.Team customized version of Twrp
Automatically decrypts data, Includes root functionality, clear the power-on password, multi-function restart.
Disclaimer: I have installed it and for me it works fine. However, it is not guaranteed to work for you especially if you currently have encryption. Use at your own risk
If you need help flashing TWRP : Follow instructions here: https://miui.blog/mi-8/flash-twrp-root-mi-8/
Downloads
Latest
Version for Miui 11 Android 10/Q : https://www.androidfilehost.com/?fid...26312261636230
MD5: 2f5f2e7dc8f32b5a999828c9370b7de2
Version for Miui 10 or 11 Android 9/P : https://www.androidfilehost.com/?fid...26312261636232
MD5: 4681f9bd6367f934218da71fd528e39b
Old Versions
TWRP-3.2.3.1-FireDance-Edition (English) ( img)
TWRP 3.2.3-1208 (English) ( zip - img )
TWRP 3.2.3-1110 (English) ( zip - img )
TWRP 3.2.3-1110 ( zip - fastboot - img )
TWRP 3.2.3-0918 (zip - fastboot - img)
TWRP 3.2.3-0908 (zip - fastboot - img)
TWRP 3.2.2-0703 (zip - fastboot - img)
TWRP 3.2.2-0611 (zip - fastboot - img)
TWRP 3.2.2-0609 (zip - fastboot - img)
Changelog (Google Translated)
2018.11.10 update Contents:
1. Update the new rom that supports the official Android 9.
2. Update and optimize some functions
3. Increase the option to restart after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. Uncheck the box and you can not restart. After the automatic upgrade, some operations are performed to prevent twrp from being overwritten, etc.
4. Update the built-in root to magisk 17.1, and fix the problem that the module cannot be brushed. Other features are also updated and optimized
5. After the new version of the system root, restarting the system requires manual installation of the magisk app, the official system problem, this can only be so
. 6. If Kami may need the root system or remove the dm check operation.
7. Prevent the functions covered by the official rec: root system, signature boot, remove dm check, cancel forced encryption, etc.
2018.9.8 update:
1. Support the official Android 9.0 system, including automatic decryption data
2. About data decryption, this may not be particularly stable now, sometimes need to reboot into the system and then restart Twrp can be decrypted.
If the new version of twrp is not supported, you can try to use the old version of
2018.8.6 update:
1. Update twrp 3.2.3 source code
2. Built-in magisk16.7, temporarily build this version first
3. Optimize data decryption problem, fix some problems
4 Support the new version of miui10 data decryption
5. Decrypt the plaintext display input password, easy to check whether the password input is correct
6. Update to try to repair the decryption data scheme, set the lock screen password to the machine, enter twrp need to enter the lock screen Password, otherwise you cannot temporarily decrypt data.
7. After brushing in twrp, the first time you enter twrp may restart once. This is normal. If you restart repeatedly, or you can't decrypt data, please give me feedback on Weibo.
8. Regarding data decryption, this may not be particularly stable now. Sometimes you need to reboot into the system and restart into twrp to decrypt.
If the new version of twrp is not supported, you can try to use the old version of
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
arifqur said:
Thanks. I was already using the EN version you posted in the Dogsly(that may be wrong) thread.
Great job
Click to expand...
Click to collapse
@gulp79 is to thank for the English version
mikefallen said:
@gulp79 is to thank for the English version
Click to expand...
Click to collapse
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
gulp79 said:
if you want to add to op, this is the img version of TWRP-3.2.3-1110-XIAOMI8-EN-wzsx150
(with a minor modifications of prop.default, and also with chinese language, in previous version chinese was removed, btw english is set as default).
https://mega.nz/fm/M4oDgLxA
Click to expand...
Click to collapse
that link doesn't seem to work for me, just redirects to the home page of mega
mikefallen said:
that link doesn't seem to work for me, just redirects to the home page of mega
Click to expand...
Click to collapse
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
gulp79 said:
try this
https://mega.nz/#!MwQn3IgR!UmuuBk1OScPrHi_HUO1zA_Da0df3nexfrrWGEBGjJPg
Click to expand...
Click to collapse
yup added to OP Thanks!
Help!!!
It works for mi 8 miui 10.0.3.0 global?, i cant figure out how install the eu rom, in the twrp show me only folders encrypted :C, somebody knows how ?
Looks like you will have to format Dara partition in recovery by typing yes
So, boot the img and then flash the zip for TWRP to stick permanently?
Can't use gapps Aroma installer using twrp .. any ideas ?
could this twrp support amora installer
could this twrp support amora installer?
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
in twrp go to file manager, data, system and delete locksettings file. reboot and you're good to go again
Hi!
Help me, please!
I can't exit from recovery mode on MI8
cyaneo said:
On my MI 8, i restored a previous backup made with twrp, now the device does not accept my 4-digit password so I can't login to my phone!
please help!
Click to expand...
Click to collapse
Go into recovery mode, format internal memory.
---------- Post added at 06:24 AM ---------- Previous post was at 06:22 AM ----------
Coolesha said:
Hi!
Help me, please!
I can't exit from recovery mode on MI8
Click to expand...
Click to collapse
You need to format your device.
bahuy2003 said:
Go into recovery mode, format internal memory.
Click to expand...
Click to collapse
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
cyaneo said:
ok, but doesn't this delete all my settings & personal files (aka reset to default)?
Thank you!
Click to expand...
Click to collapse
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
bahuy2003 said:
If you device can't reboot, you can flash eu or global rom, format again and reboot system.
Click to expand...
Click to collapse
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
cyaneo said:
Hu? never wrote it doesn't reboot etc. - It reboots, everything seems to be OK - I "just" can't login after restore a backup....
so, again: does "format internal memory" reset my phone, delete setting or personal files? If so, how does this solve the problem? After a fresh EU ROM install, everything works fine like a new install does.
Click to expand...
Click to collapse
Flash this zip in TWRP and your login password would be deleted, which by the way gets jumbled up after a restore.
This is the new thread for Pie & 10 TWRP Recovery 3.3.1-x
Feature list:
- Pie stock ROMs are fully decryptable with this TWRP, either protected with secure startup or without :good: OREO encrypted userdata is not decryptable with 3.3 . However, if you're on encrypted oreo and update to pie stock, either via zip or kdz, crypto gets migrated and you're good to go in terms of access to your encrypted data with 3.3. So, with this recovery, the urgent need for flashing no-verity-opt-encrypt zip isn't really there anymore
- everything working: backup & restore even with encrypted userdata, no matter if it's from oreo or pie. If you restore a backup containing an encrypted userdata, you'll need to format userdata before, for crypto removal. But only when coming from another encrypted ROM, otherwise you can just restore, boot up (it will use the encryption settings you"ve set up) ; decryption; time & dat; mtp; adb; installing of ROMs and zips in general; themeable; .........
- Possibility to leave out lockscreen settings when restoring a backup (sometimes you were forced to delete them manually, otherwise no login into your restored ROM possible -.- You can bypass this with this. Note: lockscreensettings ≠ encryption pin/pw/pattern.)
- Time and date is shown correctly, independent of /data. This should work after a few boots of ROM and TWRP, TWRP needs to get the data once and later on it will then be calculated from persist's settings file.
- modem image support: backup, restore, flashing of modem images either taken directly from kdz or diskdump. Same for OP partition (not present on USA and some others possibly)
- For removing encryption completely you can now do it as already known, via format userdata. Crypto is removed with it now again.
- busybox instead of toolbox/toybox, for better zip compatibility as it looks for now
- Pie 3.3.1-x: compiled with full 9.0 TWRP sources
- capable of installing every ROM and zip files
- some extra partitions (see below)
Don't forget your timezone settings after flashing. Also there are some extra partitions you can mount/backup/flash/explore, like LAF, persist-LG and OP configs. There's the thought of some people to flash TWRP as a second copy to LAF partition to be on the sure side when it comes to ROM switching or sth like that. You can do this, anyway it's not really recommended (by me and some others) because you'll lose download mode, but you now have the option.
For extra partitions: Some of them are needed for decryption (modem / persist-lg (drm)), some are for VoLTE (OP), time is stored on /persist/time (and /data/vendor/time), modem should be known and the LAF partition should be known already too (described above).
For decryption: it works as it should. Therefore it is a little bit tricky to restore a backup of a ROM which had encrypted userdata, when you'd installed any other ROM in between. There are some points to remember when restoring, a little guide is available in old thread's third post (https://forum.xda-developers.com/showpost.php?p=77839649&postcount=3), and some tipps too.
Some instructions:
How to flash?
If starting fresh with an unmodified phone, this thread should help you installing it
When you already have TWRP installed, you can flash this recovery from within TWRP:
- Copy the new image file to one of your phone storages
- Tap "Install"
- Tap "Install image" button, located down right
- Locate your downloaded image and select it
- Select "recovery" from the list which shows up then
- Install; and reboot to recovery after installing immediately, don't use it for any other tasks until rebooted pls, as it may not function. Things can go bollox when phone wasn't rebooted to recovery after installing.
And of course you can flash it via fastbootmode. Reboot to bootloader (adb reboot bootloader; when magisk is installed, you can use magisk manager => module => menu on the top right => reboot to bootloader. You can reboot to recovery from there too) and then:
fastboot flash recovery <twrp-image-name.img>
How to (re)boot to TWRP?:
If your phone is rooted:
- Magisk has options to reboot to different targets like bootloader or recovery, but this menu is a little bit hidden: you can access it by starting Magisk.Manager, going to the "Module" menu, tapping on the three dot menu on the top right. Then select your target
- If a terminal emulator is installed, open it, type "su" followed by enter and type "reboot recovery"
- You can do the same with an adb shell, open a shell and type the commands from above, they're the same
- There also are apps for rebooting to recovery or other targets. Just search around in PlayStore
- The good old "button dance" When phone is powered off, press the volume down key and power button at the same time. When a first sign of life is seen on display, immediately release the power button, but just to instantly press it again. A menu will show, which wants you to do a factory reset: do it You have to confirm this two times, and afterwards TWRP will boot without performing a factory reset. TWRP is compiled with a flag which recognizes this procedure and hinders the bootloader to pass the command for factory resetting.
This time no optional version of TWRP is available, it's "one for all". This TWRP works for every V30 model, and only for them. I removed vendor partition too btw, there isn't any active development about that, so it's useless and only confuses ppl. DataImage function is available.
If you want to use data_image, system_image or internal storage included in data backup, first check your filesystem on your external sdcard. It needs to be capable of writing big files, which isn't the case with fat/fat16/fat32. You need exFAT (for stock) or ext4/ntfs (only available with custom kernel and/or AOSP based builds).
CHANGELOG:
February 23rd, 2020, TWRP 3.3.1-2:
- corrected blocksize for formatting crypto related partitions
- included timezone data, maybe helps some ppl with time still not showing correct; should speed up time calc
- used pre-compiled full mke2fs and e2fsdroid binaries
- enabled ntfs experimental support (rw in kernel, NTFS_3G flag in twrp / ofox)
- minimal tweaks
- enabled F2FS and NTFS support
January 1st, 2020, TWRP 3.3.1-1:
- Formatting problem solved, TWRP now removes crypto as it should when user initiates a data format
- small fixings like checkbox layout in restore menu
- Moved a LOGERR to LOGINFO: "E: Unable to decrypt FBE device". Couldn't get rid of it with our needed config...
Dec. 30th, 2019, TWRP 3.3.1-0:
- initial first version
- almost everything working like in 3.2 oreo TWRP
- Formatting your device doesn't remove crypto from disk, so a "fresh" (formatted) userdata gets disturbed by old security lock
DOWNLOADS:
Nougat, Oreo and Pie capable 3.3.1-0 TWRP, but decrypting support only for PIE (AOSP untested, stock confirmed):
Download links below (always the latest and newest only; one version for all):
File name: TWRP-JOAN-3312_2020-02-23.img
MD5sum: 2fd78a606b65274977f1cd63080d5f23
MAIN Download: MEGA, TWRP-JOAN-3312_2020-02-23.img
As always: Use it at your own risk! You are the one who changes stuff on your phone, I'm not responsible for anything which happens to your phone. TWRP is powerful, be careful at what you do with it :good: And it just works.
All you need to compile this yourself:
[url]https://github.com/seader/android_device_lge_joan-twrp[/url]
[url]https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni[/url]
[url]https://github.com/seader/android_kernel_lge_msm8998[/url] (not really needed as a prebuilt kernel is used)
[url]https://github.com/seader/bootable_recovery-twrp[/url] (copy of twrp recovery with the stuff added. Pie is "encrypt-9.0" branch. omni's android-9.0 branch almost fully compatible, beside not being able to remove crypto (dirty hack, sry )
Much appreciated for your hard work. Twrp after all is the base for all customization
Thanks!
sure, enjoy it
btw, is there someone with oreo encrypted...? would be nice to know if it's decryptable with this new twrp too, and we therefore only need this one (and the other one can be archived...?)?
which is spoken very early, there's a lot left to do for 3.3 running really flawlessly. but, of course, this will be continued and being further worked on :good: starting right now xD
@ChazzMatt: it will take a while until wtf can be updated with this new one here. this is in an late beta stage, it works but has some quirks left. nothing that can destroy a phone but this twrp isn't fully working at this point of time and therefore not possible to use "in productive threads".
Everything works as well as the previous stable recovery.
I have tried:
1. backing up and restoring ROMs
2. Flashing, ROMs(stock pie and aosp Q), kernels and other mods.
Big thanks ??
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
kanehun said:
In my case time is still not correct, I have to choose a different timezone compared to actual.... When booted up normally, it is correct.
Click to expand...
Click to collapse
it needs some boots and reboots to recovery. after setting up everything it showed in twrp as it should :good: i'll add the tzdata back, a registry of all timezones, used for calculation of time, maybe it helps.
Time zone is beyond screwed up, 3 hours off without DST. Also, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
ldeveraux said:
, I'm on Oreo and it's asking for the decrypt password to access internal SD.Going back to 3.2.3-7.
Click to expand...
Click to collapse
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash JohnFawkes Root Checker disabler,
Reformat data (where you type yes),
Reboot to recovery from within TWRP,
Flash Magisk AGAIN,
Reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
ChazzMatt said:
Try using the Pie compatible Decryption Disabler and then Reformatting data...
Have you tried flashing the @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) before reformatting?
Flash Magisk,
Flash Pie-compatible encryption disabler,
Flash Root Checker disabler,
reformat data (where you type yes),
reboot to recovery from within TWRP,
flash Magisk AGAIN,
reboot phone.
See this post: https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
_____________
7. MORE TWRP ACTIONS - Now turn off data encryption and install essential items… all in TWRP:
(This is not a "menu" in TWRP, it's merely a list of what you NEED to do before booting to the OS)
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Install the Magisk zip. (This is to give the encryption disabler root privileges)
d. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
e. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
f. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
g. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
h. Re-flash the Magisk zip again. (This is to make sure, due to Pie changes.)
i. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
Click to expand...
Click to collapse
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
:victory: thank you seadersn!
ldeveraux said:
No, that's an insane amount of hassle for no apparent gain! I'm just sticking with the older TWRP [emoji6]
Click to expand...
Click to collapse
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
We needed new Encryption Disabler and we needed new Root Checker Disabler and we needed to flash Magisk twice.
The order of steps had to be rewritten besides new files.
Those have been in effect ever since EU H930 got Pie. Works on Oreo AND Pie bootloader unlocked KDZ.
drewcu said:
Were you already on a decrypted ROM using the older version of TWRP? Trying to figure out if the same encrypted internal storage situation will happen to me if I bother to try this Pie version of TWRP. Just would stick with Oreo TWRP if it's going to be this whole hassle to upgrade.
Thanks!
Click to expand...
Click to collapse
I'm on the TWRP flashable US99820H, so no clue
ChazzMatt said:
It's the exact steps people have to do when installing TWRP to work with bootloader unlocked Pie KDZ.
Those have been in effect ever since EU H930 got Pie.
Click to expand...
Click to collapse
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
ldeveraux said:
I'm on the TWRP flashable US99820H, so no clue
I guess. I don't have Pie and don't plan on updating soon. I don't even know what the decryption password was all about. My TWRP was working fine, I've learned one thing with Android: if it ain't broke...
Click to expand...
Click to collapse
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
drewcu said:
Any TWRP flashable ROM was likely decrypted and is similar to my situation (except I'm on Pie VS99630c). Sounds like upgrading to TWRP 3.3.1 Pie is more hassle than it's worth and I'll stay put.
Thanks.
Click to expand...
Click to collapse
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
ChazzMatt said:
Sure. I'm still on stock rooted Oreo firmware, also.
But those two new files, different order of steps work with both Oreo AND Pie Bootloader Unlocked KDZ with 3 2.3.7 -- whereas the older method and (with original decryption and root check disabler files) were in place before Pie.
WTF has always had decryption and root check disabler files and reformat of data to install TWRP.
What's different now is newer files to be effective on Pie KDZ as well as different order of steps -- as well as flashing Magisk at the beginning and again at the end.
I am hoping those files and steps also work with this new TWRP 3.3.1.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
ChazzMatt said:
Those files and steps I posted work with all Pie KDZ on 3.2.3.7. If they don't work on this 3.3.1 that's strange.
Click to expand...
Click to collapse
it's only formatting data switched to "fastboot -w" (reformats cache and data) or "fastboot erase userdata" (reformats data). both remove eventually present encryptions. everything else works like in the default wtf recovery :good: and that's really an enerving point... i want to simply format my userdata in twrp and not have to switch to fastboot...
formatting now works :good:
drewcu said:
I am on John Fawkes' Pie VS99630c TWRP flashable ZIP using TWRP 3.2.3.7. The concern is whether upgrading TWRP to 3.3.1 is as simple is flashing the IMG file within TWRP 3.2.3.7, or whether we'll have to reflash multiple things in a whole list of steps. If it's the latter, then why not just stay on TWRP 3.2.3.7 which seems to do everything we need in terms of flashing Pie ROMs?
Click to expand...
Click to collapse
it's the first: flashing image easily. only thing is, as described above, removing encryption requires fastboot. atm not possible to do this in recovery as usual. therefore nod suitable for wtf thread, but for anybody else, especially the ones who have pie installed and want to acces their data in twrp when encrypted. i'll test oreo decryption compatibility soon, zip needs downloading time lol
oreo decryption compatibility not given with 3.3 but: you can easily migrate from encrypted oreo via fw zip to pie, it adopts the storage encryption then and 3.3 is able to unlock :good: i've got a solution for 3.3 not being able to remove encryption: i keep a copyof 3.2.3-7 image on external sd and install it when formatting needed xD then back to 3.3 and good to go.
workaround no more needed, working now
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
zgfg said:
Why don't you install Magisk by patching Boot image from Magisk Manager and flashing the patched image from Fastboot.
Just for Magisk, you don't need (to bother with) TWRP
Click to expand...
Click to collapse
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Tom403 said:
Won't that replace my recovery with the stock one?
I'd like to keep twrp
Click to expand...
Click to collapse
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
zgfg said:
You flash the patched Boot image from Fastboot, so Recovery (and other partitions) remains the one you have currently installed.
Also, just patching in Magisk Manager does not affect either Recovery, Boot (Vendor, etc)
When patching Boot image by Magisk Manager make sure you take the options:
-Preserve ADM dm-verity: YES
-Preserve force encryption: YES
-Recovery mode: NO
Click to expand...
Click to collapse
Ok, I'll do that then
Thanks for the help ?
Tom403 said:
Ok, I'll do that then
Thanks for the help ?
Click to expand...
Click to collapse
For the Boot image you have to patch boot.img extracted from zip/recovery package of your stock ROM
But you can also backup Boot partition by TWRP and then let Magisk Manager patch the backup boot.emmc.win file
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
goo. said:
Is it safe to assume that Tom403 didn't find any love at the end of the encrypted rainblow? I JUST WANT to verify, This IS the same situation that used to be remedied by deleting locksettings.db and a files with .key extension?? No such luck for anymore, wow, what a setup for future-screwing your users Google!! Dicks
Click to expand...
Click to collapse
Okay, I may have found a lightbulb somewhere in the tunnel that may be whats required for others as well to unencrypt when deleting .keyfiles is no longer an option having version greater than PIE. It's in the form of in a recovery log from a recent, perhaps backup attempt, that states the version of Orange Fox recovery I had (11.0) and also says fbe encryption in use and info like the following that looks very promising... I'd really appreciate if someone that knows more than me to let me know if I'm on the right path and guide me in if so... heres part of the LOG that gives me hope --
ased Encryption is present
e4crypt_initialize_global_de
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
calling retrieveAndInstallKey
Key exists, using: /data/unencrypted/key
Using SoftwareWrappedKeymaster1Device from Google for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default
Determining wrapped-key support for /data
fbe.data.wrappedkey = false
Added key 90117251 (ext4:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 866183642 (f2fs:72f7ca8ad834ad5d) to keyring 322439018 in process 546
Added key 321684719 (fscrypt:72f7ca8ad834ad5d) to keyring 322439018 in process 546
contents mode 'aes-256-xts' filenames 'aes-256-heh'
Wrote system DE key reference to:/data/unencrypted/ref
e4crypt_ini
Thanks in advance for any help with this
Tom403 said:
Hey everyone,
After updating to the last stable version of xiaomi.eu I wanted to reflash magisk but when I boot into recovery I'm not asked for any password yet my data is still encrypted.
I tried running #twrp decrypt password in the terminal but it fails.
Has anyone here encounter the same problem?
Click to expand...
Click to collapse
thanks for the terminal command
EMUI 8 Stock ROMs:
3.2.1-0 by pretoriano80 (with data decryption on Android 8 )
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
EMUI 8 Custom ROMs:
3.2.1.0 by Catuva21:
https://mega.nz/#!JlkRVY7b!Hz0QTmbgmMNeCaU-PmVRBGKsdd9pslmWNkOZpE6I8ZA
3.2.3-0 by Askuccio
https://mega.nz/#!h9903SqS!aRXc9x6Kuz_GclVy_3ZExCLDSdnp7Ee8VIgfqOG9x8k
Chinese ROMs (inc. KangVip):
3.2.1-0
https://mega.nz/#!sp0UyCDR!bq10MAyh0sddUCPi0zecQzrmLfCESFvNlCiQ3vkPMqI
EMUI 9.1 Stock ROM & Custom ROMs:
3.2.1-0 GAGUGA Edition
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
EMUI 9.1 Custom ROMs:
3.4.0-0-emui9_eR by @S_mak
https://mega.nz/#!B8kWgJDC!_hj7xkTzF9Uj66wKjtrWPHEV5Dbkk7Q256tuiKg7FQU
On [A12], [A12.1] GSIs use 3.4.0-0-emui9_eR .
Do you mean you can install these over erecovery partition?
adamfirari said:
Do you mean you can install these over erecovery partition?
Click to expand...
Click to collapse
These TWRPs allow you to install any compatible TWRP over eRecovery.
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
TureX said:
Hi!
Is there a recovery that is able to make a full backup (modem nvm ecc..)?
Click to expand...
Click to collapse
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
HI!
Which vendor are you using? And which twrp shared are you using? Does lineageos 16 official boot keeping twrp installed?
Thanks in advance
wax_77 said:
hi all,
addonsu.zip works?
my output trying to flash via twrp
...
Installing su addon...
set_metadata: Error on lstat of "/system/addon.d/51-
addon.su": No such file or directory
Updater procedd ended with ERROR: 7
Error installing zip file '/sdcard/Download/addonsu-
16.0-arm-signed.zip'
...
twrp seems work fine, i can flash los and gapps without problem...
thank you
Click to expand...
Click to collapse
Hello,
I successfully installed the addonsu-16.0-arm64 using
TWRP
You have to enable root in Developer options. Works fine...
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Fjord1 said:
Hi there,
which TWRP can I use to downgrade to Oreo via HuRupdater?
Thanks.
Click to expand...
Click to collapse
3.2.1-0 by pretoriano80 .
Note: If you don't have the required files stored somewhere, then it's just an academic question - Firmware finder is ďead.
-Alf- said:
Firmware finder is ďead.
Click to expand...
Click to collapse
It makes me sad...
And what about dload method?
Fjord1 said:
downgrade to Oreo
Click to expand...
Click to collapse
Fjord1 said:
dload method
Click to expand...
Click to collapse
you will get absolutely no success, it may even brick your phone.
Hi all. I am trying to recover content from a MediaTab T5 with a Damaged screen (no picture). I've managed to install these recoveries and reboot into them. However none of them provide an adb interface for shell access, only a virtual usb cd rom drive appears. How can I obtain recovery adb access? I need to enable USB debugging and push adbkey...
Anyone have any clues how I can work around this please. Is patched boot img the only way forward?
OK good news I Successfully booted into recovery and have adb access. I think the key was to power on with vol+, but WITHOUT the USB cable attached. If USB cable is attached then it tries to boot to system regardless
-Alf- said:
Hello,
I never use Nandroid backup, so I don't know. Test it and let us know
Click to expand...
Click to collapse
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Mahad Habib said:
hi, I was just wondering incase something goes wrong, can you link me some thread or guide to go back to stock firmware (I do have the full firmware files)
Click to expand...
Click to collapse
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
-Alf- said:
I'm not sure I fully understand your question :
- go back to stock from custom ROM?
- what full FW do you have?
Click to expand...
Click to collapse
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Mahad Habib said:
yes that's my question.
the one I have is
"Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.144(C185) Firmware Android 8.0.0 EMUI 8.0.0"
I know this works because I used it to downgrade.
Click to expand...
Click to collapse
Yes, you can revert to stock flashing this Service ROM , if yot are running EMUI 8. For EMUI 9.1 use Service ROM 9.1.0. This process will erase all your data and lock the BL again!
Or, simply flash SYSTEM.img extracted from Service ROM using Huawei
update extractor. This procedure will not erase your data ,bootloader remains unlocked etc.
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
hopeless_bricker said:
Hey Alf,
Were you able to flash any of the recoveries over the erecovery?
The 3.2.1-0 GAGUGA Edition has a built in option but it didn't work for me, no failures but when I hold down vol + I still get erecovery. I tried flashing 3.4.0-0-emui9_eR by @S_mak to erecovery_ramdisk but got a command not allowed.
PRA-LX1 on a C432 base, got CAOS11 system and Magisk in recovery. Since the recovery partition is occupied by Magisk having TWRP on erecovery would be ideal.
Thank you for your posts, they've been useful.
Click to expand...
Click to collapse
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
hopeless_bricker said:
Since the recovery partition is occupied by Magisk
Click to expand...
Click to collapse
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
(Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP),
- Copy TWRP file to the SD card, and also copy to card Stock Recovery_ramdisk.
- Enter TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- Go back, find Stock recovery_ramdisk file, (or magisk-patched recovery_ramdisk on EMUI 9) , mark Recovery, swipe. Reboot system.
P.S.: as far as i know the PRA-LX1 hasn't received an upgrade to Pie (correct me if I'm wrong) , so i don't understand
Click to expand...
Click to collapse
I got it wrong, it's a ANE-LX3! Mixed up with my other phone, sorry. In principle that method works, thank you. I didn't get to actually test it because it seems the Magisk recovery overrides the boot procedure so it always boots to recovery automatically.
Handy but I can't boot into the erecovery with the button combo now.
P.S.: I'm having issues with audio device switching. If I get a phone call with headphones inserted it routes to the speaker and I can't change it. If I remove the headphones then the mic doesn't work. I also have a bit inconsistent connection over bluetooth, sometimes it is connected but still plays over the speakers. I have the Huawei switch method enabled in the phh options. Did you experience this?
Hello,
I flashed the latest Lineage recovery and LineageOS20 on my Google Pixel 5, and I'd like to disable encryption on the data partition. Is there an ADB command I can run, or file I can flash to achieve this? I also have Magisk 26.1 flashed.
I use this phone for a development project and encryption is getting in the way.
Thanks!
I'm surprised no one knows.
I wanted to go the TWRP route of formatting the data partition, but I can't get TWRP to boot when running Android 13. I need to be on Android 12 to boot TWRP successfully, but being on Android 12 means I can't flash LineageOS20 (requires Android 13), a real catch 22.
Otherwise, does anyone have a link to the latest LineageOS19.1 for Redfin? The link is broken on the LineageOS website and I can't locate that zip file on any other website.