Database Info

[Recovery] Official TWRP for the Xiaomi Mi MIX (lithium)

Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
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, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"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"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.

Great Work
Now Xiaomi MI MIX is the greatest device we can have atm

@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this

development is starting , great work OP

agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono

Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.

Wow, a thousand thanks.

I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?

mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own

jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse

mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse

Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app

cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi

just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.

knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve

:good::good:

wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.

does anyone know if using TWRP manager will work to install TWRP after you have unlocked?

jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too

OTA update for F1f

A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"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"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.

Now I wish I can unroot my phone, lol

You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?

You can extract recovery.img from the ColorOS zip.

If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?

This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.

kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?

MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you

MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)

Deleted

kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.

wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete

Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota

wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?

Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader

wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work

Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware

wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23

How to re install the original recovery :crying:

[RS988][RECOVERY][OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988 [05/21]

{
"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"
}
Thank you @shunjou for helping RS988 to go official!
This is the official support thread for TWRP for RS988.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, report them here.
Click to expand...
Click to collapse
Downloads:
Builds may be downloaded from the TWRP website.
Production builds: twrp.me/lg/lgg5rs988.html.
Test builds will depend on the current version of TWRP. For example, for v3.2.3.0 : http://build.twrp.me/twrp-3.2.3-0-rs988.img
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou
Source Code: https://github.com/TeamWin/android_device_lge_rs988
Version Information
Status: Stable
Created 2018-06-14
Last Updated 2019-06-11

Reserved?

Encryption not working for Linage 15.1

If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
Click to expand...
Click to collapse
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.

djskribbles said:
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
Click to expand...
Click to collapse
Hey @djskribbles,
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Also, you'll be better off if you use Magisk instead of SuperSU. Flash Magisk before LineageOS, because the script used to flash it automatically wipes the /system partition, which is where SuperSU, for example, makes its changes to enable root access.

NextDroid said:
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Click to expand...
Click to collapse
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.

shunjou said:
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
Click to expand...
Click to collapse
All right, that's great to hear! I'll admit, I wasn't sure when I made that second comment... it had been a while since I'd heard anything on stock encryption.
I actually just finished cooking up a fix for Oreo encryption from work on the G6... I'll head over to zl1 if it doesn't work out.
We'll see what happens... --fingers crossed--

On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?

Awkydee said:
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Click to expand...
Click to collapse
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.

NextDroid said:
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
Click to expand...
Click to collapse
Yippie! Flashing now!

can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev

bmanuelangel said:
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Are you referring to stock? Hopefully you won't need to re-lock the bootloader. When a .kdz package is published, hopefully @Unscedeo will make one of his COMPLETE INSTALLERS for it, and you could just flash it.

Hmm, I ought to keep up with this thread a bit more...
I've made some updates today and created a test build. Here is the link for anyone who wishes to test: http://build.twrp.me/twrp-3.2.3-0-rs988.img

Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html said:
* Fix selinux issues during formatting - dianlujitao
...
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Click to expand...
Click to collapse
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?

Ascii3 said:
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
I have been very busy for the past couple of months, but the G5 hasn't left my mind... I use it every day I'll see when I can update TWRP and my other builds.
Thanks for keeping us updated, @Ascii3!

NextDroid said:
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
Click to expand...
Click to collapse
Maybe, if I have some time, myself. It is looking like something for August 2019.
NextDroid said:
I have been very busy for the past couple of months...I'll see when I can update TWRP and my other builds.
Click to expand...
Click to collapse
I am glad to see that you your are still around.
NextDroid said:
Thanks for keeping us updated, @Ascii3!
Click to expand...
Click to collapse
Sure.

Ascii3 said:
Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
I can and shall answer this question that I posed before:
TWRP allows for both RAW and file-based backups. Usually, however, the GUI provides few items for RAW backup; there is typically a backup option for "System Image" which is a RAW backup.
@NextDroid - I noticed that more recent versions of your TWRP do not have the System Image backup option despite it being in your older TWRP 3.2.3-0 build. The System Image backup functionality from TWRP 3.2.3-0 seemed to work OK. Did you deliberately exclude the "System Image" backup option? I the option missing for good reason?

[ROOT] [UNLOCK] [ANE-LX1/L01/L21] [Stock EMUI 8/9] P20 Lite

Today I will be giving a tutorial on how to root the Huawei P20 Lite using STOCK ROM (ANE-LX1 ANE-L01 ANE-L21)
If you need bootloader unlock code
----------------------------------------
You can use dc-unlocker but, only if you can rollback to 8.0.0.146 or lower (i was on 8.0.0.46 when i used dc-unlocker).
You can try to use PotatoNV, but that will require testpoint access (haven't tested yet).
You can use HCU client with a 3day account pass, which is quite expensive (I have not actually tested this yet).
Rollback EMUI 9 to EMUI 8
-----------------------------
This is where my frustrations with this phone began.
You can try to use dload method, but in my experience this DOES NOT WORK when you're on EMUI 9.
It will just give you an error about incompatible version, every time.
Forced dload was also a complete bust for me, 24 hours wasted
I was finally able to rollback from HiSuite 11. I was on 9.1.0.200 when I had the option to rollback and it rolled me back to 8.0.0.163.
From 8.0.0.163 I could use normal dload to rollback further until I could use dc-unlocker.
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there. It's less bloated and feels smoother. I have not received the option to rollback after I re-upgraded to 9 since. And I have not found AANNYY method to rollback to 8 since then, I pretty much gave up and stayed on EMUI 9.
EMUI 8
---------
copy magisk23.zip to sdcard
flash twrp to recovery_ramdisk.img
Code:
fastboot flash recovery_ramdisk "twrp-3.2.1-0.img"
EDIT: ***NEW official TWRP version*** TWRP 3.6.2.0_9-0
Code:
fastboot flash recovery_ramdisk "twrp-official-3.6.2_9-0-anne.img"
Code:
fastboot reboot recovery
Once in twrp install the magisk23.zip file.
This will patch the boot.img from recovery_ramdisk.img with magisk v23
Reboot -> System
Once in android you will get the usual magisk app, open and allow to perform additional tasks like installing the manager app.
Pretty straight forward
EMUI 9
---------
While still on stock firmware, update your android to the highest possible firmware (HiSuite or on phone -> Settings -> System ....)
1. When your back in android power off phone.
2. Go into fastboot (USB cable plugged in -> Power + Vol Down)
3. Flash twrp into recovery_ramdisk
Code:
fastboot flash recovery_ramdisk twrp-3.2.1-0.img
Code:
fastboot reboot recovery
Now In TWRP
4. Install Image -> twrp-3.2.1-0.img into eRecovery partition
5. Install Image -> magisk23_patched-ane.img into Recovery Partition
6. Reboot -> Recovery
Note: So booting into recovery mode gives you a ROOTED environment and System Mode gives you NON-ROOTED.
EDIT: *** With the new TWRP 3.6.2.0_9-0 you will have to boot into recovery (by holding Vol Up + Power till the screen comes on) every time you boot the phone or it will boot into normal system where the root environment isn't present ***
That's it. Now you should have root access.
You can still use twrp, but you have to access it like you would access eRecovery. So from power off (coldstart) -> Hold Vol Up while plugging in the USB Cable, continue to hold Vol Up, till you get the twrp logo.
Caution: This overwrites eRecovery, this can be dangerous, as eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore. This is due to fastboot not being able to flash eRecovery. You can only flash eRecovery from twrp. This is particularly dangerous if your data partition gets corrupted, this can happen when formatting data through twrp 3.4.0 and above. When your data partition is corrupt, twrp will freeze on the loading logo, leaving you no way to flash the original eRecovery.
Note: I think you can flash the eRecovery_ramdisk.img over the normal recovery_ramdisk in case of a brick situation. Though I haven't tested that idea yet, im just planning on going that route if I run into such a scenario. The eRecovery is particularly usefull as it can recover almost any situation by using wifi to download a stock rom and full flash that entire rom.
This way is robust, no need for key combo's when restarting the device etc.
All Downloads (GDrive):
Gdrive
After the root, you might find yourself needing safetynet attest pass.
This can be achieved by:
1. Open Magisk and setup MagiskHide ( Search on XDA if you don't know how to do this )
2. Magisk Modules -> Install Riru
3. Magisk Modules -> Install from storage -> Select safetynet-fix-v2.1.0.zip
note: If PropsConfig is installed, remove it first and reboot
If you need to use Smali then it's once again kinda straight forward.
1. Copy /system/framework to sdcard (anywhere u can copy it from)
2. Copy the framework folder onto pc
3. Open SmaliPatcher.exe -> Select the framework folder -> select patch options and patch
4. Copy the created magisk module zip file onto sdcard
5. Install magisk module -> Magisk -> Modules -> Install from storage
Hope you have a smooth experience rooting this device.
External links:
Tested custom recoveries from -Alf-
Source of rooting and flashing information by -Alf-
Credits:
@-Alf- for the magisk patched image. I only repatched his recovery_ramdisk from magisk v21 to v23
And also for the twrp recovery 3.2.1-0 GAGUGA Edition

RESERVED

gh0stza said:
And I have not found AANNYY method to rollback to 8 since then,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85379393
gh0stza said:
eRecovery is the only thing standing between you can a hard brick if twrp wont boot anymore
Click to expand...
Click to collapse
there is one more thing - Service ROM aka 'full stock ROM' & dload method
gh0stza said:
your data partition gets corrupted, this can happen when formatting data through twrp.
Click to expand...
Click to collapse
Can happen only with TWRP 3.4.0 and above.
Regards

No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL

gh0stza said:
No matter what I did, dload failed, I must have downloaded 30 roms and tried every which way with dload. Nothing worked!!!!!
dload only worked on same EMUI. So nope sorry dude dload was a no go for me. Maybe it works for someone else, which is why I mentioned it.
And yes, TWRP 3.4.0 and above. I was using a twrp(3.5.2_9-0) from official twrp repository for ANE-LX1 when I formatted my data partition. However, that's not the point.
Someone else is absolutely BOUND to fall into this trap too, and as I said that TWRP came from the official chain.
So my only intention is to warn the next guy who might just be using that version or for whatever other reason twrp doesn't start anymore. I'm just saying - BE CAREFUL
Click to expand...
Click to collapse
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/

-Alf- said:
this is why we have this article here: https://forum.xda-developers.com/t/recommended-and-tested-twrp-recovery.4199099/
Click to expand...
Click to collapse
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks

gh0stza said:
Shiet dude, 3 full days rooting this device and I didn't come upon this post once. Now I'm gonna have to try to downgrade again with HuRUpdater and that twrp.
That's a nice post - thanks
Click to expand...
Click to collapse
What is your regional variant?

-Alf- said:
Oreo and Pie Stock & Custom ROMs:
3.2.1-0 by pretoriano80 (data decryption on Android 8 ) - on Pie use this TWRP e.g. if you want to downgrade to Oreo via HuRupdater.
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Click to expand...
Click to collapse
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
I plan on using the HiSuite downloaded firmware ANE-LX1 8.0.0.163(C185) with HuRUpdater.
Current folder stucture:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\ANE-L01_hw_meafnaf\update_full_ANE-L01_hw_meafnaf.zip
Planned folder structure after renames:
ANE-LX1 8.0.0.163(C185)\full\update.zip
ANE-LX1 8.0.0.163(C185)\full\update_all_hw.zip
ANE-LX1 8.0.0.163(C185)\full\HuRUpdater_0.4.zip
Then flash HuRUpdater_0.4.zip in twrp 3.2.1-0 by pretoriano80 like the quoted text suggests?
Am I getting this right?
PS: The twrp I am using now -> 3.2.1-0 GAGUGA Edition (Also the one in my download hyperlink)
EDIT: I am on 9.1.0.355(C185) now. But, it is still trying to give me OTA update of the exact same build, so dunno what thats about

gh0stza said:
The twrp I am using now -> 3.2.1-0 GAGUGA Edition (
Click to expand...
Click to collapse
Read carefully bro: https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-85380241
You need 3 .zip files - update, hw and data
{
"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"
}

gh0stza said:
Are you saying I should try to use this TWRP to use HuRUpdater to downgrade to 8?
Click to expand...
Click to collapse
Bingo!

Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone

gh0stza said:
Then I have a problem.
Not one single downloaded firmware anywhere gave me 3 files. It's always just the update.zip (or update_sd.zip for dload) and the hw update.
How can HiSuite flash that firmware then? I just need to flash this 163 rom. But nothing works
***EDIT***
Know what, doesn't matter. I'm pretty fed up with this phone and how Huawei implemented this phones partitioning style and just everything.
I mean where is Odin for Huawei? And just how they withdrew support to get unlock code, limited fastboot command etc.
Just everything about huawei....
I got my ANE-LX1 to a stable root with everything I need working perfectly, so Imma call it a win and move on.
But, you've been great dude and basically almost all useful information I got either came from you ( @-Alf- ) or XDA, so thnx everyone
Click to expand...
Click to collapse
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.

-Alf- said:
Try this way out...
Flash via dload
https://androidhost.ru/1lsA
and try downgrade via HiSuite.
Click to expand...
Click to collapse
Ok, download started
First thing tomorrow morning, even though I just got everything just right with EMUI 9.
You think it's worth it?

gh0stza said:
I made the mistake of upgrading to EMUI 9 after I unlocked my bootloader. My advise: if you can manage to get to 8, stay there.It's less bloated and feels smoother.
Click to expand...
Click to collapse
gh0stza said:
You think it's worth it?
Click to expand...
Click to collapse

dunno how to respond to that....
I'll keep it in my back pocket, when i'm bored some time this week I might try it.
Else screw it, to hell with you huawei.
PS: Still better then the LG G6, which is unrootable (short of opening it up) due to the total inablility to get unlock code.

so do we run this to keep the stock eRecovery?
Install Image -> twrp-3.2.1-0.img into eRecovery partition
coz i got stuck in a situation where the phone would boot to twrp only and nothing else, somehow managed to get back to stock

khal_nayak said:
Install Image -> twrp-3.2.1-0.img into eRecovery
Click to expand...
Click to collapse
this is only necessary if you want to have both Magisk root and TWRP on board at the same time. (on EMUI 9.1 ramdisk is
included in the recovery_ramdisk).
If you don't need TWRP, just flash magisk_patched_recovery in fastboot mode.

ok but i was trying to remove bloatware i caused the rom to bootloop and then tried factory reset from twrp and now other than twrp nothing boots, where can i get factory image from to get it back to working?
all i need is root with magisk and want to keep the stock erecovery.
if there are better custom roms with volte etc all working then im willing to try it out

khal_nayak said:
tried factory reset from twrp
Click to expand...
Click to collapse
That was not a good idea. On Huawei phones, you can only perform a factory reset from stock recovery.
khal_nayak said:
where can i get factory image from to get it back to working
Click to expand...
Click to collapse
Depends on your build number - model, EMUI version, region variant (Cxxx). What is your b.number?
khal_nayak said:
custom roms with volte etc all working
Click to expand...
Click to collapse
All Treble GSI ROMs on Huawei have common bugs - no VoLTE, no offline charging, no native call recording...

since now i can only boot to twrp and fastboot mode how do i know the model and region?
i bought the phone as nova3e in UAE and currently was on emui 9.1, if i can just get the erecovery back then can make it download the firmware and flash it

[RECOVERY][UNOFFICIAL] TWRP 3.7.0_12-0 for Galaxy A42 5G [2023/01/24]

{
"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"
}
Unofficial TWRP 3.7.0 For Galaxy A42 5G
Disclaimer
Code:
*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 features included in this recovery before flashing it!
*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.
Features:
Android 12 support
Decryption support
What's not working:
You tell me.
Downloads:
A42 5G: Download
Changelogs:
2023/01/24
Updated to TWRP 3.7.0 with A12.1 trees.
Fixed decryption.
Click to expand...
Click to collapse
2022/07/27 (Re-uploaded)
Fixed OTG.
Fixed Vibration.
Support NTFS.
Use LZMA to compress image.
Click to expand...
Click to collapse
2022/07/20
Fixed MTP.
Fixed Temperature display
Updated Kernel
Click to expand...
Click to collapse
How to install
Make sure your bootloader is already unlocked and OEM unlock is enabled, otherwise the installation will fail.
Download and install Samsung Drivers
Download the latest *.tar for your phone
Download Odin, from example from https://downloads.corsicanu.ro/samsung/
If not done before, flash disabled VBMeta with Odin in AP or CP slot (originally posted here).
Turn off your phone, connect it to PC and reboot to download mode by holding down Volume up, Volume down and power button at the same time.
Open Odin and check if your device is detected, then untick "Autoreboot" in its settings.
Put the tar file you downloaded into the AP tab
Click start and wait for the installation to finish, Odin will show PASS
Now hold down Power button and Volume down for about 10 seconds to force reboot the device
Immediately after the screen goes black release the keys and hold down Volume up and Power button at the same time until you enter TWRP (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning)
If you properly followed all the steps you should now see the TWRP menu.
I HIGHLY recommend to flash multidisabler and services disabler right after you enter TWRP to disable forced encryption and stock recovery restoration.
If you're scared of doing something wrong, you can also follow the steps in this video
Donations
DONATE To Me
Sources:
A42 5G: https://github.com/TARKZiM/twrp_android_device_samsung_a42xq
Kernel: https://github.com/TARKZiM/android_kernel_samsung_sm7225
Credits:
TeamWin
@Velosh for the original TWRP trees
@Simon1511 for A52 device trees.
@corsicanu for updating multidisabler for A12 and providing download links for Odin, USB drivers, etc
Everyone else involved

Screenshots

I'm currently working on LineageOS 19 for this device, stay tuned.

tarkzim said:
I'm currently working on LineageOS 19 for this device, stay tuned.
Click to expand...
Click to collapse
GOOD NEWS
LineageOS 19 booted and running on A42 5G, check out here : THREAD

New build released
Fixed MTP.
Fixed Temperature display
Updated Kernel

New build released
Fixed OTG.
Fixed Vibration.
Support NTFS.
Use LZMA to compress image.

Why is my phone stuck on file analysis while flashing twrp? I tried flashing vbmeta disabler on both AP and CP slot

awesomellama3 said:
Why is my phone stuck on file analysis while flashing twrp? I tried flashing vbmeta disabler on both AP and CP slot
Click to expand...
Click to collapse
The .tar file of latest twrp build is corrupted, I just uploaded a new one.
Please try to download it again.

Oh thank you! I thought something was wrong with my phone, haha... atleast if anyone bought this phone for modding doesn't have this issue anymore.

I'm a bit of a paranoid person myself, and I was wondering if my phone is compatible with this. In your LOS ROM for the A42 5G, you specified it needs to be an a42xq, however my phone is specified as an a42xqeea, and not just a42xq. I paid a lot of money for this phone, but I really want to install a custom recovery, so a response would be appreciated.

Vuraniute said:
I'm a bit of a paranoid person myself, and I was wondering if my phone is compatible with this. In your LOS ROM for the A42 5G, you specified it needs to be an a42xq, however my phone is specified as an a42xqeea, and not just a42xq. I paid a lot of money for this phone, but I really want to install a custom recovery, so a response would be appreciated.
Click to expand...
Click to collapse
If you are able to unlock the bootloader, and prepared stock firmware before flashing, I will suggest you to try this.

tarkzim said:
If you are able to unlock the bootloader, and prepared stock firmware before flashing, I will suggest you to try this.
Click to expand...
Click to collapse
Bootloader is unlockable, just checked. The device is still running on stock firmware, I don't get what you mean by "prepared stock firmware before flashing", is there a way to backup the firmware before installing TWRP?

Vuraniute said:
Bootloader is unlockable, just checked. The device is still running on stock firmware, I don't get what you mean by "prepared stock firmware before flashing", is there a way to backup the firmware before installing TWRP?
Click to expand...
Click to collapse
There are some firmware download websites for samsung devices, you can find them and download the firmware for your device model.

tarkzim said:
There are some firmware download websites for samsung devices, you can find them and download the firmware for your device model.
Click to expand...
Click to collapse
Hello again, I was preparing to donwload everything and install TWRP today, until I noticed that this was intended for an SM-A426U, I have an SM-A426B, are you sure this will not brick my recovery in any way?

Vuraniute said:
Hello again, I was preparing to donwload everything and install TWRP today, until I noticed that this was intended for an SM-A426U, I have an SM-A426B, are you sure this will not brick my recovery in any way?
Click to expand...
Click to collapse
My device is exactly the SM-A426B and well tested.
As I said, if you have stock firmware files, you could restore everything if you want, including recovery partition.
So it won't brick your device.

tarkzim said:
My device is exactly the SM-A426B and well tested.
As I said, if you have stock firmware files, you could restore everything if you want, including recovery partition.
So it won't brick your device.
Click to expand...
Click to collapse
Thanks, downloading firmware and odin right now. I will report the results when done.

Hello I am glad that I found this ! I did the whole procedure and probably I have done something wrong in the last step . It boots into the stock recovery and not twrp ? I missed something ?

New build released
Updated to TWRP 3.7.0 with A12.1 trees.
Fixed decryption.

Does it support Android 13?

gud device can play many games in very high grafic