Database Info

[HOW-TO] Root Nokia 8 with Systemless Magisk

Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"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"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!

Reserved

Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader

2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?

Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader

I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?

contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!

On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?

For everyone with unlocked bootloader, this is the method to root without TWRP !

Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...

Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately

As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?

شرا

Twrp and Android 10. Fastboot flash recovery command failed even though bootloader is unlocked

The only command prompt that seems to be working is fastboot flash boot twrp.img but when I type fastboot flash recovery the flash fails. I use Minimal ADB and Fastboot command prompt. The latest version too. I downgraded my android 11 to 10 successfully. I have no problems rooting magisk through ADB but why can't TWRP permenantly stick? How can I force it to stick as my main recovery no matter what rom I flash?

Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.

This guide shows you how to get TWRP to stick:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

P4a doesn't have a recovery partition anymore, recovery is part of the boot.img. That's why the fastboot cmd fails.

UltimateGamer83 said:
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
Click to expand...
Click to collapse
You can't flash recovery on this phone. It's part of boot.img. Put the TWRP.img file in your internal storage of your phone. Flash the TWRP temporarily first. Fastboot boot TWRP.img. When TWRP boots, click install, then select install image. Choose your TWRP file and select install Ramdisk. Swipe to flash. TWRP will then be installed permanently. You must also be using a custom kernel with TWRP compression support because the partition is not big enough and must be compressed otherwise you will run into issues like TWRP freezing or touch screen issues.

I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?

I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.

UltimateGamer83 said:
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
Click to expand...
Click to collapse
Yes, if you flash magisk boot img it will replace TWRP. Flashing the zip is the way to go. Glad you got it working.

UltimateGamer83 said:
I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10.
Click to expand...
Click to collapse
I've move your thread out of development, for which it doesn't qualify.
And I assumed your consent and edited the thread title.
In order to edit a title, click the "Edit" button of your OP and you'll see the title at the very top, which you're able to edit:
Spoiler: Screenshots
{
"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"
}
Regards
Oswald Boelcke
Senior Moderator

UltimateGamer83 said:
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
Click to expand...
Click to collapse
I'm curious....you said you are on Android 10, but then you mentioned above installing an OTA update.....I thought all the currently available OTA updates are only for android 11?

My 10 cents worth. Magisk kills fastboot and adb in MY armor x5 mt6765, in 10_Q, so had no choice but to load boot-debug.img just to 'test'.
Try an android 9 bootloader designed for them 'super' .img's, this is the only way I could LOAD magisk, only to find what I read here.
Also note, in 10_Q, the gsi ability found in dev options dissapears when magisk is flashed, so I cant flash gsi, never mind use fastboot or adb.
Thank you.

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery

How to Downgrade Android Version in Samsung Devices if Device is in Higher Binery​View attachment Samsung-Logo-MSP.webp​
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers
Note :-​
Samsung binery is impossible to downagrade. ​This method will do install old stock as a custom rom (signature removed stock rom). So this method only can downgarde android version. ​This method cannot downgrade modem or radio or bootlooder such as (aboot,lk,non-holes) like critical images. if you try that it will dead your device​
Click to expand...
Click to collapse
Not Tested in All Devices. So I Don't know this method is working for all samsung devices. Proofs are at the end. You Have to try and tell
What you need​
Latest binery of stock rom that you need to downgrade​
Bootloader Unlocked Device​
Lz4 Unpacker​
Simg2img.exe​
Hxd​
Android Image kitchen​
Odin​
7zip​
Windows Computer
​If you have super.img device shipped with Android 10 or Android 10+​You must have unlocked bootloader​If your device cannot use magisk this method will not work for you. (A20s user cannot do this) ​
1. Unlock your device bootloader​2. Download the Latest binery of stock rom that you need to downgrade (samfw)​3. Extract the whole Ap.....tar.md5​Get all boot.img.lz4 recovery.img.lz4 super.img .lz4(vendor.img.ext4.lz4 and system.img.ext4.lz4)​
{
"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"
}
4. Convert .lz4 to img​Grag and drop lz4 file to lz4.exe​​5. Then Patched the boot.img with magisk and unpack and repack recovery.img using android image kitchen (aik)​6. Then paste simg2img.exe to where converted super.img located.​
7. Then open cmd from there and type simg2img super.img super.raw​then you will get a super.raw​
8. Open HXD and grag and drop super.raw to hxd​​9. Then CTRL+F and search all the U number of the firmware you downloded​According to me it is U4​
9. Then Find a phases like this and fill all phases with zero bytes (there should be more than one)​
10. Then Save it and remove the super.raw.bak​11. Then Rename the super.raw to super.img and make tar with 7zip including patched boot.img recovery.img and super.img​12. Flash it and Format data​
Patched vbmeta is not essential due to magisk patched boot.img​
If you Have System.img and Vendor.img Device Shipped with Android 7 8 9​​1.Do all the steps untill number 6​2.Then convert system.img.ext4 and vendor.img.ext4 to raw by open cmd then, simg2img.exe system.ext4.img.raw and same to vendor​3.Open both System.ext4.img.raw form Hxd and Countinue with step 9​4.Then save Both vendor and system and delete the .bak files​5.Then rename system.img.ext4.raw to system.img.exe4 and vendor.img.ext4.raw to vendor.img.ext4​6.Then Convert to Lz4 by open cmd and lz4 -1 system.img.ext4​7.Then Make tar using Magisk patched boot.img and repacked recovery.img and system.img.ext4.lz4 and vendor.img.ext4.lz4​8. Flash and wipe Data​
Patched vbmeta is not essential due to magisk patched boot.img​​Proof Tested Devices,​
Samsung Galaxy M01 (Qualcomm)
Downgrade Android 12 to android 10 (u4 to u3)
Samsung Galaxy A71 Qualcomm
Android 13 to Android 10 (U8 to U3)
Updates​
Some users said they cannot flash super.img in a51 and s20 exyons version. May be this method will not work for exyons. I dont know that need to test more
Downgrade success for s20 fe 5g qcom using this method
Still not tested on MTK
Video Tutorial​
Remove Signature from Super or System/Vendor​
Downloads​Hxd
This method also can use for update android version without upgrading binery version.​

Interesting.. I'll try it when I get back my pc

tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding

oznear said:
tested in my samsung a52 5g. Downside is, on-screen fingerprint sensor always not responding
Click to expand...
Click to collapse
Try with replace vendor/firmware from u4 stock (dosent depend on android version)

Hi, If I flashed it through Odin, do I still need to supply the BL, CP, CSC? Thanks in advance.

A10 -> A9 9 on SD S10: the flashing itself works but device's now stuck on booting - cannot get to A9 recovery

jq555888 said:
Android 10 -> Android 9 on snapdragon S10: the flashing itself appeared to work but device's now stuck on booting - cannot get to Android 9's recovery for some reason which I suspect is due to a different partition layout (device's shipped with Android 9); tried to erase userdata with Android 10's recovery but still can't get it to finish booting. Any ideas?
Click to expand...
Click to collapse
You used latest version of android 9?

smiley9000 said:
You used latest version of android 9?
Click to expand...
Click to collapse
Yeah - this was last version of A10 - A9

jq555888 said:
Yeah - this was going from G9700ZHU4DTL2 (last version of Android 10) to G9700ZCS2ASJU (last version of Android 9)
Click to expand...
Click to collapse
stuck in android boot animation?

smiley9000 said:
stuck in android boot animation?
Click to expand...
Click to collapse
yes! it's like the startup screen

jq555888 said:
yes! it's like the startup screen where it usually says the phone's model (with the text "this phone is not running official software"). it's the one after pressing the side button, but not the "SAMSUNG" screen.
Click to expand...
Click to collapse
enable usb debugging and try to get logs

smiley9000 said:
enable usb debugging and try to get logs
Click to expand...
Click to collapse
thank you! any way to achieve this by modifying the official A9 rom?

jq555888 said:
thank you! any way to achieve this by modifying the official A9 rom?
booting to twrp for A9 also fails not sure if it's a parition problem but A10 twrp works
Click to expand...
Click to collapse
maybe due to kernel

hello ! i have a problem with Android image kitchen , when i click repackimg.bat he say me
Fichier introuvable
Paramètre incorrect.
Android Image Kitchen - RepackImg Script
by osm0sis @ xda-developers
Packing ramdisk (as root) . . .
Windows sudo required but not found.
*** Reinstall Android Image Kitchen, then add ***
*** sudo.exe to your antivirus exceptions! ***
Error!
how can i fix this pls?

Thanks for taking the trouble to make this thread @smiley9000
Anyone tried this on s10e exynos variant with android 12 - downgrade to android 10 ?

Question Can someone post a list of the pixel 7 pro partitions in fastbootd

Can someone post a list of the pixel 7 pro partitions in fastbootd? Im having issues with getting my device working properly cuz some of my partitions are missing and im not sure.. do both slots have to have the product, vendor, vendor dlkm system dlkm etc? im just not sure which partitions need to be on the inactive partition

PochiRaccoon said:
Can someone post a list of the pixel 7 pro partitions in fastbootd? Im having issues with getting my device working properly cuz some of my partitions are missing and im not sure.. do both slots have to have the product, vendor, vendor dlkm system dlkm etc? im just not sure which partitions need to be on the inactive partition
Click to expand...
Click to collapse
I apologize in advanced for not answering your question directly....
But I'm guessing you may be having issues because you attempted to flash the factory image and are bootlooping or not loading the OS; and you had made sure to use the latest version of platform-tools.
I'm guessing this because the latest version of platform-tools (version r34+) has an established notorious bug that doesn't allow it to reboot into fastbootd mode to flash the rest of the partitions that can only be flashed there -- which seems to be the case for you.
If this is your case, you should be able to successfully flash the Full Factory image using the last platform-tools version that did not have said bug -- version r33.0.3. You can find a post to be able to download it below...
Using that version of PT, it should be able to flash all the necessary pertinent partitions and you should be up and running. Be sure to remove the "-w" from the flash-all file or your phone will be completely wiped and returned to stock. I don't imagine you need to flash it to both slots as you only need one slot stable to boot from; but if you wish, you could always reboot back to bootloader, switch slots, and run the flash-all on that slot -- just be sure to not try to boot into the OS from that slot until you've run the flash-all on it; lest your issue indirectly affected it and you may run into some problems.
Good luck and hope this helps...
June 20, 2023 TQ3A.230605.012.A1 Verizon/MVNOs / June 13, 2023 TQ3A.230605.012 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Pixel 7 Pro [Cheetah] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com

Is that bug specific to Windows?
I used r34.0.1 on Manjaro Linux without any issues...
I even use "android-sdk-platform-tools-34.0.1-1" from AUR as the provider for adb and fastboot instead of the complete Android Studio...

kodabmx said:
Is that bug specific to Windows?
I used r34.0.1 on Manjaro Linux without any issues...
I even use "android-sdk-platform-tools-34.0.1-1" from AUR as the provider for adb and fastboot instead of the complete Android Studio...
Click to expand...
Click to collapse
It is specific to that all version after 33.0.1. It doesn't allow the phone reboot to FastbootD. There for the partitions that need to flashed in fastbootD cannot occur.

I have personally used it to flash fastbootd images for the Radioactive kernel. No issues encountered using Linux.
I just tested it again:
Code:
adb reboot fastboot
It rebooted to fastbootd as expected. It's a Lineage fastbootd from when I tried Lineage 20. If it's not just a Windows thing, maybe it's how the stock fastbootd interacts.
{
"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"
}

The issue with any adb/fastboot version r33.0.3+ has more to do specifically with the flashing Google's Full Factory images (flash-all) than it is specifically in booting into fastbootd. This also explains why flashing kernels or other specifics still work. For complicated reasons, when running the fastboot "update" command, when needing to flash into the fastbootd mode for flashing certain images/partitions, it fails -- only really following through with the fastboot update protocol than merely just booting into fastbootd.
Most likely, the reason why all the partitions are corrupted/invalid/wrong that's supposed to be flashed in fastbootd for the OP is because of this reason. I'm jumping to that conclusion; but it makes sense.
Also, it is easier to download platform tools directly from Google's developer's site than downloading it as part of a package or taken from Android Studio or other. You can find it here (for Windows, Mac, & Linux): https://developer.android.com/studio/releases/platform-tools

[CLOSED] I can't install TWRP Custom Recovery on my Xiaomi Redmi 10 (selene). How do I do that?

Hello everyone, I want to install TWRP Custom Recovery on my Phone. But, when I tried some videos, all of them aren't working. But why?
I tried the following:
fastboot boot recovery.img (resulted: FAILED (status read failed (Too many links)))
fastboot flash recovery recovery.img (resulted: FAILED (remote: This partition doesn't exist))
I tried also,
fastboot flast boot recovery.img (resulted: bootloop)
I checked many comments, most of them saying that it doesn't work, others say that there is no recovery partition
Now my recovery partition is gone, leaving only to restart instead.
So, is there something I can do about it? Is there a solution for this problem that I'm facing? Looking forward to replies.
My phone is a Xiaomi Redmi 10 (non-2022 edition), codenamed selene.
And this that I am using is the unofficial TWRP (ver 3.6.1).
Thank you.
Update: Nevermind, the recovery is there. Regular Xiaomi recovery.

dasdsad1 said:
Hello everyone, I want to install TWRP Custom Recovery on my Phone. But, when I tried some videos, all of them aren't working. But why?
I tried the following:
fastboot boot recovery.img (resulted: FAILED (status read failed (Too many links)))
fastboot flash recovery recovery.img (resulted: FAILED (remote: This partition doesn't exist))
I tried also,
fastboot flast boot recovery.img (resulted: bootloop)
I checked many comments, most of them saying that it doesn't work, others say that there is no recovery partition.
Now my recovery partition is gone, leaving only to restart instead.
So, is there something I can do about it? Is there a solution for this problem that I'm facing? Looking forward to replies.
My phone is a Xiaomi Redmi 10 (non-2022 edition), codenamed selene.
Thank you.
Click to expand...
Click to collapse
Please respond quickly.

Xiaomi.eu post:
Couldn't install TWRP recovery on Redmi 10.
Yo guys, I have a feeling about this, but TWRP Can't. Be. Installed. On. My. Redmi 10? Because I said so. So, I wanted to install TWRP, but there was a problem. See, I tried tens of hundreds of videos, but to no avail. Tried commands like: fastboot boot recovery.img fastboot flash recovery...
xiaomi.eu

On which rom is the phone(Android version) and which Twrp(link)?

NOSS8 said:
On which rom is the phone(Android version) and which Twrp(link)?
Click to expand...
Click to collapse
MIUI Global 13.0.10 Stable (SKUIDXM)/Android 12, Indonesian region ROM
TWRP link: https://unofficialtwrp.com/twrp-3-6-1-root-redmi-10/?amp#google_vignette
Model: Redmi 10 (codename selene, non-2022 version), 21061119DG

From UNofficialtwrp.com

Tried various tools. XiaoMiTool V2 said unknown error, XiaoMiFlash.exe is only for flashing ROMs, and REDMI 10 2022 (SELENE), only for MIUI 12.5 (from TAPIN RECOVERY INSTALLER).

Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?

NOSS8 said:
On which rom is the phone(Android version) and which Twrp(link)?
Click to expand...
Click to collapse
I bought the device over a year ago.

NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
Just a moment

NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
Already did, but still not working.

And the phone won't restart?

NOSS8 said:
And the phone won't restart?
Click to expand...
Click to collapse
It restarts to Stock ROM.

Tried different ports, cables, disabled driver signature enforcement, CMD and PowerShell, many restarts, but still the same error that I am occurring.
{
"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"
}

NOSS8 said:
Are you sure of the version?
SELENE 21061119AG, 21061119AL, 21061119BI, 21121119SG, 21121119VL, 22011119TI
Not sure this TWRP works on A12, did you flash the VBmeta as shown on the link?
Click to expand...
Click to collapse
flashed different vbmeta.img

Download PlatformTools and put the Twrp in the folder and run all your commands from this folder.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You must flash the VBmeta corresponding to the installed rom

My PC:
Device name: DESKTOP-K3DHSR3
Processor: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz 2.40 GHz
Installed RAM: 16.0 GB (15.9 GB usable)
Device ID: EC895DCA-D7C0-41EF-A114-8C0CD8F42698
Product ID: 00330-50316-52505-AAOEM
System type: 64-bit operating system, x64-based processor
Pen and touch: No pen or touch input is available for this display
Manufacter: Lenovo

NOSS8 said:
Download PlatformTools and put the Twrp in the folder and run all your commands from this folder.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You must flash the VBmeta corresponding to the installed rom
Click to expand...
Click to collapse
O.K.

dasdsad1 said:
O.K.
Click to expand...
Click to collapse
I'll let you updated in a short moment.

I did, the vbmeta flash worked, but still no response on the fastboot boot twrpredmi10.img or any TWRP img.
Complete log: