Database Info

How To Flash Custom 6.0.1 Roms On Locked Bootloader That Cannot Be Unlocked

The easiest method to obtain root or unlocks or update or downgrade unlocked bootloaders can be found below they were updated December of 2021​
EMMC 15 Unlocking Bootloader
2022_VZW_EMMC_15_ AIO_Tool To Unlock_Bootloader+Install_TWRP And MM_QL1_Rooted_Rom Works On Any Version Bootloaders_MM_LL_KK-Reactivation Lock Remover
This Process Will Root Phone Unlock Your VZW EMMC 15 Chipset Bootloader Install TWRP Recobery And Imstall Latest QL1 Stock Rom . Downloads S5_Root_Tools_2023.7z EMMC_15_Rom.zip -- Stock QL1 6.0 Directions For Unlocking Stock Phone I would...
forum.xda-developers.com
EMMC 15 Updating Unlocked Bootloaders Or Downgrading
2022_VZW_EMMC_15_Chipset For Unlocked Dev BL To Downgrade To LL_KK Or Upgrade To MM_And Keep Unlock Bootloader
This Process Will Update Or Downgrade Your VZW EMMC Chipset DEV Aboot Bootloader Unlocked S5 To Marshmallow 6.0 Lollipop 5.0 Or Kitkat 4.2 or 4.4 Root And Unlock Instructions Can Be Found Here EMMC 15 Rooting And Bootloader Unlocking EMMC 11...
forum.xda-developers.com
For Rooting EMMC 11 Phones
2021_VZW_Locked_Bootloader_EMMC_11_Rooted/NonRooted_Roms_With_Safestrap_MM_LL_KK
This Process Will Install On The EMMC_11 Locked Bootloader Verizon S5 Marshmallow QL1 Stock Rom NonRooted With Safestrap. Lollipop PB1 Stock Rom Rooted With Safestrap. KK Rom Rooted With Safestrap What This Does This gives you the ability to...
forum.xda-developers.com

Downgrade Files
Any Prerooted PB1 Rom
PB1_Firmware_With_PB1_Bootloader_CAUTION.zip
Place rom and PB1_Firmware_With_PB1_Bootloader_CAUTION.zip on phone
Wipe Data/System/Cache
Flash Rom
Flash PB1_Firmware_With_PB1_Bootloader_CAUTION.zip
your done. You dont need to worry about safestrap zip because you will be rooted again

Weird.....so we'll have a we can flash any Custom MM Rom......but it won't be Rooted. Progress!

Stupifier said:
Weird.....so we'll have a we can flash any Custom MM Rom......but it won't be Rooted. Progress!
Click to expand...
Click to collapse
Always need root just to install custom roms . If we can install roms without root , then we don't need root anymore ( I am still lost ). Now I can wait for custom 6.1 roms.

Its not ideal but at least you dont have to go through the whole reroot process each time you want to change roms. And you can still flash zips etc in safestrap.

Reserved

Can we run and use apps which require ROOT access?
I'm a bit confused though. Don't custom ROMs come pre-rooted???? So wouldn't flashing a custom ROM which is pre-rooted....... remain rooted?

Stupifier said:
Can we run and use apps which require ROOT access?
I'm a bit confused though. Don't custom ROMs come pre-rooted???? So wouldn't flashing a custom ROM which is pre-rooted....... remain rooted?
Click to expand...
Click to collapse
Probably no . It says by @jrkruse the flashed Roms got no root !

Stupifier said:
Can we run and use apps which require ROOT access?
I'm a bit confused though. Don't custom ROMs come pre-rooted???? So wouldn't flashing a custom ROM which is pre-rooted....... remain rooted?
Click to expand...
Click to collapse
alin919 said:
Probably no . It says by @jrkruse the flashed Roms got no root !
Click to expand...
Click to collapse
You cannot have a rooted MM rom with locked bootloader because to have root requires a custom kernel which locked bootloaders cannot flash. It doesnt matter if the rom is prerooted or not! Stock Boot.img means no root. You cannot run apps that require root with these roms All this method does if give you some options the biggest option being the ability to flash zips. and change roms with out having to odin back to stock pb1 then reroot then. Try the stock MM rom I posted. Once installed you can flash a debloatzip or a knox removal zip or delete apps from safestrap with the built in file manager If you dont like you can always downgrade back to PB1

jrkruse said:
You cannot have a rooted MM rom with locked bootloader because to have root requires a custom kernel which locked bootloaders cannot flash. It doesnt matter if the rom is prerooted or not! Stock Boot.img means no root. You cannot run apps that require root with these roms All this method does if give you some options the biggest option being the ability to flash zips. and change roms with out having to odin back to stock pb1 then reroot then. Try the stock MM rom I posted. Once installed you can flash a debloatzip or a knox removal zip or delete apps from safestrap with the built in file manager If you dont like you can always downgrade back to PB1
Click to expand...
Click to collapse
That what i thought , this is better than nothing for use with locked bootloaders . Thanks :good:

So has anyone tried it

jrkruse said:
So has anyone tried it
Click to expand...
Click to collapse
I am downloading now, I just got home.

jrkruse said:
So has anyone tried it
Click to expand...
Click to collapse
my wife's computer crashed so i have not i even went to local library and i was now allowed to download there so i have to wait until i get my wife's computer out of shop.
Sent via mobile Verizon S5

@jrkruse How does this work?
Based on my knowledge from reading this, it seems that the kernel finds the checksum of the system partition and then only boots if it is unmodified.
Shouldn't modifying the system partition in the slightest bit throw this checksum off?
Also - modified kernels CAN be flashed on locked bootloaders - just not via Odin. They only won't boot though >.>

jrkruse said:
So has anyone tried it
Click to expand...
Click to collapse
Perfect instructions @jrkruse , thank you ! Is working , it took me 11 minute to boot . Now lets see if everything is working wright .

alin919 said:
Perfect instructions @jrkruse , thank you ! Is working , it took me 11 minute to boot . Now lets see if everything is working wright .
Click to expand...
Click to collapse
So far everything is looking good , i will run today marshmallow to check it out . Tomorrow i will try to downgrade to pb1 to see if working .

Will this method work with FF? Haven't used SS since my SG4 days.
Sent from my SM-G900V using Tapatalk

I got one to try. I have tried it so I know it works
Download this rom
Download my Patch
In safestrap do a manual wipe. Wipe Data,WipeCache,Wipe System
Install Rom
Install patch
This rom Does not flash system.img so you dont need to install safestrap it will stay installed
After patch is installed wipe data and wipe cache and install MM Bootloader zip
Reboot it will take 15 to 20 min to boot
Now you will Have A Note 5 port with working theme support

Hollywood67 said:
Will this method work with FF? Haven't used SS since my SG4 days.
Click to expand...
Click to collapse
No

hey what can i do im on the MM firmware but i flashed something and now my phone just stays at the samsung logo with a blue led light what can i do it wont but up past the samsung logo screen

SAFE rooting to HUAWEI MATE 9

hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all

one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting

Thx to reply. Like the others i wanna root to have root apps in my phone ,

Thx . Wanna have apps requires root in my phone . That simple

You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+

super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action

nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.

ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!

I failed install su however still waiting for any updates

nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?

ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!

FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.

Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk

FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD

ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310

nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.

mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
 @st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.

mr. ante0 ..... u r the man , thank you so much

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

Can Oreo android 8 firmware be rooted on s8 exynos? G955FXXU1CRAP

HI Guys, I have installed the G955FXXU1CRAP at my s8+ but when I try to flash twrp with odin it get status fail and the phone says that installation of custom binaries are not allow (OEM LOCK and RMM STATE: PRENORMAL).
Did you tryed to install Twrp and root G955FXXU1CRAP? How you solve this bootloader lock?.
thanks in advance.
Alex.

In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.

This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -

Well, thank you so much for that information guys. I did not know it.

Geekser said:
This has been said a bunch of times throughout the S8 Plus threads - but I will give it to you again.
your phone is locked - y ou will not be able to flash anything until you pass the 168 hour (7 day) period. When you do get to that point, you can flash twrp, root and or flash a custom rom. Whatver you do, before you reboot your phone, flash the file you find at this thread: https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 It will make it so you don't have to do that again. Your phone will not get locked again and the RMM State will be NORMAL - instead of Pre-normal.
That is the only thing you can do. And it is important to remmeber to flash the RMM Fix before you reboot (after flashing twrp, SuperSU/Magisk and or a Custom Rom. If you don't flash that file yoiu will be very likely locked again for another 7 days as soon as you reboot.
The link above has a much better explanation but I hope this helps you and anyone else reading this that has the same problem.
Good Luck. (I have been waiting for 4 days so far - I have three days to go -
Click to expand...
Click to collapse
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.

cyborgium said:
Could you please be more detailed on the steps I should take for not being locked again?
I'm about to flash Oreo and I want to flash TWRP and Magisk manager after those 7 days but I don't know in what order I should do it all, when I have to flash that RMM aswell.
Click to expand...
Click to collapse
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22

Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..

Geekser said:
Go here and read what the say about the RMM State fix - should explain everytihng https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol

cyborgium said:
Take a look at this screenshot though. I installed the CRAP build less than a day ago and when I first went into developer options, OEM unlock was already enabled. I'm REALLY confused right now..
Click to expand...
Click to collapse
Go into download mode (Power, Bixby and Vol Down) when you are in download mode, you can see what the RMM State is - it will either say NORMAL or PRE-NORMAL.
If yours says NORMAL - then you go can go ahead and flash TWRP via ODIN. If you are having flash issues at this point, ask in the TWRP Thread and you should be able to get some help.
However, if you are PRE-NORMAL in download mode, then you are locked and won't be able to flash anything until you pass the 7 day period.I think the 7 days begins on the date you flashed your current firmware.
YOu can be in PRE-NORMAL and still see OEM UNLOCK. BUT if you are pre-normal and you see OEM UNLOCK you cannot flash until your RMM State changes to NORMAL.
I hope that helps.

xxxrichievxxx said:
Not sure if you know the answer to this but do we have to flash this every time we reboot on a custom ROM or flash this every time we flash a custom ROM?
I have 8 hours left until the lock is lifted on mine lol
Click to expand...
Click to collapse
Yes, the RMM Fix must be flashed after you flash TWRP or after you flash a custom rom, everytime. UNLESS the rom has the RMM Fix baked into the rom - some do - some may not. Won't hurt to fllash it just in case, everytime.

Thanks again for the rapid response but, I'm identifying an issue with the storage on this firmware g955fxxu1crap. My phone exynos g955f has 64 gb of internal storage, but after this upgrade it shows only 16 gb of internal storage.
Did get this same error , how you solve it?
thanks in advance.
Ale3385

josegon30 said:
In order to root you have to flash TWRP and for that OEM must be unlocked. You have to wait 7 days with the phone on (without reseting) to get capable of unlock OEM in developer options, due to a new security issue with Samsung.
I'm in the same situation. 4 days and 10 hours left.
Click to expand...
Click to collapse
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.

Psyscope said:
What happened after your seven days were you able to flash twrp and stay rooted in Oreo with Oreo bootloader and modem? Have you tried flashing the new Oreo Bl & Modem? Curious if the seven days is going to be mandatory for people with new phones that want to root them on Oreo.
Click to expand...
Click to collapse
After 7 days I could perfectly flash TWRP and root, no big deal. If you go into download mode and see RMM STATE: PRENORMAL then you can't flash. I guess all new phones with 8.0 since January are pre-normal, but I'm not sure.

Ive seen in the other thread that you could flash the entire nougat stock rom (nov 2017 perhaps) which will allow you to bypass the rmm and then flash TWRP and custom ROM? Could anyone confirm this workaround?

S7 edge SM-G935F remove root/ back to stock

Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks

Vinni777 said:
Hello all, i have some questions. I owe model S7 edge SM-G935F.
On weekend i tried to flash it and install TWRP and Magisk Manager - manaed to install it and play a round.
Now changed my mind and want to get back to official firmware which i was using before. At the moment i can access TWRP ( i wiped everyting) , but if i boot to system it just stays in ODIN dowload mode ( probably because i wiped everyting)
Before work today i left downloading official rom with latest security patch. After work will flash on official ROM.
After flashing do i need to enable/disable any settings inside phone to receive latter OEM updates? Can i lock bootlader? Or it will be locked automatically when i flash stock firmware.
Thanks
Click to expand...
Click to collapse
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader

kpwnApps said:
No. If you flash full firmware you will receive oem updates again. You need to unlock developer settings and disable oem unlock to lock bootloader
Click to expand...
Click to collapse
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.

Vinni777 said:
Thanks for reply. Will do today.
Can i flash using latest odin or i need patched version?
I know its rookie questions, but i was allready stressed to go work without phone as i run out of time yesterday.
Most important for me to get OEM updates and be able use Sam Pay and Etc.
Click to expand...
Click to collapse
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void

kpwnApps said:
You need to get the latest odin version because of the lz4 format of the firmware files. Unfortunately you cannot use sampay and knox again because of tripped warranty void
Click to expand...
Click to collapse
Thanks mate. I managed yesterday to flash on latest software and everything works perfectly apart Sam Pay and Sam Health Offcourse android pay and etc works fine.

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers