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

[ROM][7.1.2][E6533/53] LineageOS 14.1 [UNOFFICIAL]

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
NOTE
Should you ever face any issues, provide logs (use Google to find out how to gather those). I also need to know what build you're on - hence, you should mention the build number (or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored (and eventually removed). To keep the thread clean, try to use DevDB for real bug reports
KNOWN ISSUEs
None
INFO
This ROM does not use the device trees/kernel from sonyxperiadev. The device tree was made from scratch, and the stock kernel (based off 32.4.A.0.160) has been used.
DOWNLOAD
AFH
SOURCE
LineageOS
Device: LineageOS/android_device_sony_ivy
Kernel: LineageOS/android_kernel_sony_msm8994
XDA:DevDB Information
LineageOS 14.1 for the Sony Xperia Z3+ (E6533/E6553), ROM for the Sony Xperia Z4
Contributors
Quarx, Olivier, cdesai, Myself5, kali-, banmeifyouwant
Source Code: https://github.com/LineageOS/android_kernel_sony_msm8994
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2017-09-03
Created 2017-01-12
Last Updated 2020-07-05

Nice!

nice!! Sounds like you have done an excellent job and I see it's included as an official device tree in lineage repo[emoji1]

any chance to bring it to dual sim version?

feizhel_vandrago said:
any chance to bring it to dual sim version?
Click to expand...
Click to collapse
E6533 is dual sim version

feizhel_vandrago said:
any chance to bring it to dual sim version?
Click to expand...
Click to collapse
It already says it works on both - beware on flashing this though. When I did it I forgot to wipe the data and i ended up with a bootloop (my own fault) but I couldn't even get back into recovery to restore it. It doesn't look like this ROM allows you to boot into recovery (although that could just have been a side effect the bootloop situation - Not sure how though). I had to leave my phone like that till I could flash another boot image from my pc.
Sent from my Xperia Z3+ (AOSP) using XDA-Developers Legacy app

Phantasm4489 said:
It already says it works on both - beware on flashing this though. When I did it I forgot to wipe the data and i ended up with a bootloop (my own fault) but I couldn't even get back into recovery to restore it. It doesn't look like this ROM allows you to boot into recovery (although that could just have been a side effect the bootloop situation - Not sure how though). I had to leave my phone like that till I could flash another boot image from my pc.
Sent from my Xperia Z3+ (AOSP) using XDA-Developers Legacy app
Click to expand...
Click to collapse
i'm sorry, my bad. i'll wait for the stable release then

I'm always getting error 7 while flashing any Custom ROM on my Z3+ (single sim).
can someone please give me the correct version of TWRP. Thanks.

I managed to flash this ROM after changing the 'updater-script' as mentioned here --> https://forum.xda-developers.com/showthread.php?t=2522762
I'm facing an issue that now I'm not able to boot into TWRP recovery. I tried installing the recovery again from fastboot but not able to get into recovery. Any help?

batmobile_bang said:
I managed to flash this ROM after changing the 'updater-script' as mentioned here --> https://forum.xda-developers.com/showthread.php?t=2522762
I'm facing an issue that now I'm not able to boot into TWRP recovery. I tried installing the recovery again from fastboot but not able to get into recovery. Any help?
Click to expand...
Click to collapse
Just try Restarting mobile by pressing Power & Vol- simultaneously. Hold the buttons till the boots into Recovery.

batmobile_bang said:
I managed to flash this ROM after changing the 'updater-script' as mentioned here --> https://forum.xda-developers.com/showthread.php?t=2522762
I'm facing an issue that now I'm not able to boot into TWRP recovery. I tried installing the recovery again from fastboot but not able to get into recovery. Any help?
Click to expand...
Click to collapse
idk for z3+ but maybe there is a bootloader upgrade too which will allow you to boot into recovery with bootloader instead of recovery in boot.

Everything is stable for me, snapchat video rec working aswell, i have no issues except bluetooth but thats an general bug

nailyk said:
idk for z3+ but maybe there is a bootloader upgrade too which will allow you to boot into recovery with bootloader instead of recovery in boot.
Click to expand...
Click to collapse
Also you can try to empty your recovery partition, then kernel will use the builtin one.
If someone can confirm z3+ boot process is the same one as z3.

@Kungencortes, what is bluetooth bug?
You can boot to recovery via, fastboot boot recovery.img.

Quarx said:
@Kungencortes, what is bluetooth bug?
You can boot to recovery via, fastboot boot recovery.img.
Click to expand...
Click to collapse
Cant get bluetooth working bug free dosnt matter wich rom im on, common issue.

advanced reboot menu shows up but not working

Resolved Twrp recovery by holding volume down + power button while restarting and then pressing volume up. Not sure what combination works, but I can get to Twrp!
ROM is fluid and great as a initial version!
Some bugs:
# live display not working.
# lowest brightness too bright.
I'm enjoying the smoothness of stock UI on this almost dead device. Thanks Dev. I'm sticking around on this ROM. :good:

What is necessary to flash this rom?
Which TWRP image and i have to flash?
It is required to flash the Kernel zip "Kernel: LineageOS/android_kernel_sony_msm8994"?
in which order i have to flash the zip Files?

joebusch67 said:
What is necessary to flash this rom?
Which TWRP image and i have to flash?
It is required to flash the Kernel zip "Kernel: LineageOS/android_kernel_sony_msm8994"?
in which order i have to flash the zip Files?
Click to expand...
Click to collapse
https://dl.olivierk.at/ivy/twrp/recovery.img TWRP IMAGE
1. Rom 2. Gapps
http://opengapps.org/
ARM 64 7.1
No need 2 flash kernel.

How to flash the rom
Kungencortes said:
https://dl.olivierk.at/ivy/twrp/recovery.img TWRP IMAGE
1. Rom 2. Gapps
http://opengapps.org/
ARM 64 7.1
No need 2 flash kernel.
Click to expand...
Click to collapse
After i unlock the bootloader and flash the recovery, do i have to wipe system, data, cache ect., or can i flash the rom after i flashed the recovery?

[ROM] [UNOFFICIAL] Lineage OS 14.1 with full OMS for the Shield Tablet

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's the catch, we have Official LOS builds?:
These are home baked builds of LineageOS with full Substratum support. It supports the rootless operations of Substratum as well as all of its features. It will be Pure LineageOS and as such, bug reporting won't work for this one.
All the bugs that you face will either be of LineageOS or if any themeing one than it would be from Substratum. [Well there aren't any as of now]. Builds will be either weekly or daily or as new changes merge in OR depending upon my upload to the server was successful or not.
Frequently Asked Questions
1.1 Q: Can I dirty flash over from official LineageOS?
1.1 A: No, a clean flash is required as their builds are signed with private keys.
1.2 Q: Can you merge ABC feature from XYZ ROM?
1.2 A: No. This is stock Lineage with full OMS support, that is it.
1.3 Q: I have LMN bug, please fix!
1.3 A: Wait till either the Lineage Team or the Substratum team fixes it. Till then live your life dangerously....
1.4 Q: How do I see what is new every release?
1.4 A: https://www.cmxlog.com/14.1/shieldtablet/
1.4 B: https://github.com/LineageOMS
1.5 Q: What root should I flash?
1.5 A: It's up to you, as root is only required for boot animations. There are four options:
SuperSU
Magisk
phh's SuperUser
Lineage's SU
Downloads:
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot. Profit.
Credits:
The Official LineageOS Team
The Substratum Repo Guys
TheMuppet Guys
Many Thanks to:
Steel01: For helping me figure out how to merge.
BitOBSessiOn: The guy who is always ready to help irrespective of time and number of questions.
XDA:DevDB Information
Lineage OS 14.1 with full OMS, ROM for the Nvidia Shield Tablet
Contributors
Mohammad Siddique
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage OS
Version Information
Status: Nightly
Created 2017-07-13
Last Updated 2017-07-13

Hi, recently purchased an already rooted shield tablet
running 7.0
software 5.0
TWRP 3.1.0
I would like to flash without PC (looks fine) is that doable?
I am also unsure if I need to flash a root method after flashing rom and gapps since I am already rooted?
What about any root ad-ons like referenced in the official version?
thanks in advance (thank you button will be hit!)

jlipps75 said:
Hi, recently purchased an already rooted shield tablet
running 7.0
software 5.0
TWRP 3.1.0
I would like to flash without PC (looks fine) is that doable?
I am also unsure if I need to flash a root method after flashing rom and gapps since I am already rooted?
What about any root ad-ons like referenced in the official version?
thanks in advance (thank you button will be hit!)
Click to expand...
Click to collapse
Since you already have TWRP, you can go ahead and flash any rom of your choice, no PC required of course, just download it in your device, and flash via TWRP, for root as mentioned you can flash any zip of your choice to achieve the root, and what root add-ons are you referring to ?

lineage-14.1-20170715-UNOFFICIAL-shieldtablet uploaded to the G Drive with latest OMS patches

Mohammad Siddique said:
Since you already have TWRP, you can go ahead and flash any rom of your choice, no PC required of course, just download it in your device, and flash via TWRP, for root as mentioned you can flash any zip of your choice to achieve the root, and what root add-ons are you referring to ?
Click to expand...
Click to collapse
So do I need to flash a root zip to re-gain root after flashing this rom? I am already rooted so I am confused about this process. And the root add-ons seem to be useful and/or necessary with LOS official roms, there is a download link to add-on zip on page one of Steel01 official LOS thread.

jlipps75 said:
So do I need to flash a root zip to re-gain root after flashing this rom? I am already rooted so I am confused about this process. And the root add-ons seem to be useful and/or necessary with LOS official roms, there is a download link to add-on zip on page one of Steel01 official LOS thread.
Click to expand...
Click to collapse
Yes, to regain root you'll need to flash, and that root addon from LOS page will enable the inbuilt root access which can be found in development settings. If using that then no other is required to flash

Hey man, how would you go about building and merging OMS-7 for your ROM? I've been building myself a nice build of LineageOS for my OnePlus 5 with some extra mods but I haven't found out (properly) how to implement OMS yet.
Any help would be appreciated, thanks.

Interceptor777 said:
Hey man, how would you go about building and merging OMS-7 for your ROM? I've been building myself a nice build of LineageOS for my OnePlus 5 with some extra mods but I haven't found out (properly) how to implement OMS yet.
Any help would be appreciated, thanks.
Click to expand...
Click to collapse
https://github.com/LineageOMS either merge or download,
if you scroll down and see there will be merge script, or the easiest
https://forum.xda-developers.com/apps/substratum/reference-lineageos-substratum-support-t3580276
follow this step, I successfully did that using the third step EasyPeasy
And Good Luck with your build )

Hi!
When I try flashing, it tells me that it needs bootloader version 4.0.0 ... but the only bootloader I can download on from webgeek1234 either give me bootloader version 3.1.1 or 4.0.1 ... so installation fails. Installing LineageOS 13.0 doesn't complain about bootloader...
Am I missing something?

ggravier said:
When I try flashing, it tells me that it needs bootloader version 4.0.0 ... but the only bootloader I can download on from webgeek1234 either give me bootloader version 3.1.1 or 4.0.1 ...
Click to expand...
Click to collapse
Bootloader version doesn't match the stock rom version number. The bootloader it wants is the N or stock 5.0 one. I should probably make that more clear in my post...

Steel01 said:
Bootloader version doesn't match the stock rom version number. The bootloader it wants is the N or stock 5.0 one. I should probably make that more clear in my post...
Click to expand...
Click to collapse
Hi!
OK. So... how can I get, and how do I install the N bootloader on my SHIELD? I didn't see it documented.
Thanks!

It's linked in the opening post to my Lineage thread.

Steel01 said:
It's linked in the opening post to my Lineage thread.
Click to expand...
Click to collapse
Hi!
Here? On th is thread? The only thing I see is :
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
But nothing about bootloader. Another thread maybe?
Gilles.

ggravier said:
Hi!
Here? On th is thread? The only thing I see is :
ROM: LineageOS on the G Drive
GAPPS: use OpenGapps or any of your preferred choice, 7.1 ARM; pico preferred.
ROOT: see above
But nothing about bootloader. Another thread maybe?
Gilles.
Click to expand...
Click to collapse
https://forum.xda-developers.com/shield-tablet/development/rom-lineageos-shield-tablet-t3562839
He clearly mentioned his thread, here it is:
in the downloads section Firmware
doing a stock update to come to Nougat is safe. DL the file and flash via recovery then do a reboot recovery and then retry flashing.

Mohammad Siddique said:
https://forum.xda-developers.com/shield-tablet/development/rom-lineageos-shield-tablet-t3562839
He clearly mentioned his thread, here it is:
in the downloads section Firmware
doing a stock update to come to Nougat is safe. DL the file and flash via recovery then do a reboot recovery and then retry flashing.
Click to expand...
Click to collapse
So I posted on his thread... it doesn't work on my device.

ggravier said:
So I posted on his thread... it doesn't work on my device.
Click to expand...
Click to collapse
You tried flashing the zip? or just extract the blob file from the zip and fastboot flash it, profit.

Mohammad Siddique said:
You tried flashing the zip? or just extract the blob file from the zip and fastboot flash it, profit.
Click to expand...
Click to collapse
I did same procedure as for versions 311 and 420 from webgeek1234 : put the zip on the SD. Boot to TWRP. Use the "install" function to install the ZIP. It works for 311 and 420... but when I do it with version 50... the output of the installation just says "succeded" and after, when trying to install Lineage, it says version unknown.

ggravier said:
I did same procedure as for versions 311 and 420 from webgeek1234 : put the zip on the SD. Boot to TWRP. Use the "install" function to install the ZIP. It works for 311 and 420... but when I do it with version 50... the output of the installation just says "succeded" and after, when trying to install Lineage, it says version unknown.
Click to expand...
Click to collapse
That's why I'll recommend you to go on stock, update to whatever latest version stock is on, then re trying the above process, let us know your results...

Mohammad Siddique said:
That's why I'll recommend you to go on stock, update to whatever latest version stock is on, then re trying the above process, let us know your results...
Click to expand...
Click to collapse
Unfortunately, I can't go on stock. The device is a device that was recalled for the battery issue (but this one's batter never even blinks towards a thermometer when even operating at full speed). So when I got the new device, I had to flash it with a non stock OS.
So I'm running one of the latest builds of Cyanogen before they went ballistic.
And if I go to stock, the machine will be bricked.

ggravier said:
Unfortunately, I can't go on stock. The device is a device that was recalled for the battery issue (but this one's batter never even blinks towards a thermometer when even operating at full speed). So when I got the new device, I had to flash it with a non stock OS.
So I'm running one of the latest builds of Cyanogen before they went ballistic.
And if I go to stock, the machine will be bricked.
Click to expand...
Click to collapse
From the zip you have download extract the blob file, reboot your tablet to bootloader/ fastboot
and run this command
Code:
fastboot flash staging blob
this will update your bootloader to the latest N bootloader by Nvidia and hence the error will also be gone.

[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?

[RECOVERY][OFFICIAL] TWRP for Galaxy A40 [A405FN]

Team Win Recovery Project 3.6.1​
{
"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"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904

Reserved

I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?

My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?

bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.

costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.

ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!

thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!

costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data​
​
Everything working!

Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)

i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:

cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:

Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.

Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...

From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?

ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?

toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733

ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)

xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?

ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.