Database Users

Completely going stock again (except keeping the bootloader unlocked).

Hi, I have been using official CM13 for about a week now so I have the following things installed in my phone.
>CyanogenMod 13 (official)
>Cyanogen Firmware
>TWRP 3.0.2-2 F2FS (3.0.M-4)
I want to go completely stock again (temporarily until CyanogenMod has VoLTE support) but I have no idea where to start.
I would like to flash
>Stock Xiaomi Recovery
>Latest stable MIUI global.
And remove Cyanogen firmware and install stock Xiaomi MIUI firmware.
I would like to know how and where do I start.
Thank you very much!

I think MiFlash would be the best option, I think it does exactly what you're asking for (it flashes every partition including boot, radios, etc). You can can choose to erase everything, even internal storage, and make your phone as it originally came. I'm not sure it would relock the bootloader, I don't think it will.. Either way, if you unlocked officially you can always unlock again.
Only thing I'm not sure about is if you can install through fastboot or EDL only

I need to know this too

MiFlash using EDL should do the trick

do you have previous mi backup in twrp??

If you are officially unlocked bootloader, no need to enter edl mode. Miflash work from fastboot mode too.

anuneanu said:
If you are officially unlocked bootloader, no need to enter edl mode. Miflash work from fastboot mode too.
Click to expand...
Click to collapse
What if its unlocked unofficially?

naturist said:
What if its unlocked unofficially?
Click to expand...
Click to collapse
Well, i don't know since I'm unlocked it officially.
But it should work, just don't flash the emmc_ appsboot.mbn file. Need to edit the batch file.
Or just use the save twrp.

Root Xiaomi Mi A2 Using Magisk (Simple Guide)

To Root your Mi A2 you will have to first unlock its bootloader, follow all steps correctly to gain root access on your Mi A2 device,
NOTE : All data will be wiped during bootloader unlocking, so make sure to backup each and every thing on your device.
first of all enable developer option & then enable OEM unlocking & USB debugging,
Now setup adb and fastboot drivers on your laptop/PC,
Now connect your Mi A2 (on state) and allow USB debugging popup.
now boot into fastboot mode (power off and press & hold volume down + power key simultaneously)
now connect your mi a2 to your laptop/pc,
now run fastboot oem unlock it will unlock the bootloader and reboot your device, also will wipe data,
now again setup the device and enable developer option, enable OEM unlocking, enable USB debugging, and connect to allow usb debugging.
now once again boot into fastboot mode (as described above), and connect your mi a2 to your laptop/pc
now download august months (V9.6.10.0.ODIMIFE, August 5 2018.) patched_boot.img (dont use if you are on any other month patch) use that months patched_boot.img file only.
now put the patched_boot.img to adb folder.
now again open the command or powershell window, and run fastboot boot patched_boot.img
it will boot your device, now just download the Magisk manager apk and install it.
open magisk manager and click on install, then direct install (recommended),
it will now download the magisk zip file and flash it at its own, after its done simply reboot your Mi A2 and voila we have successfully rooted our Mi A2.
let me know if you have any issues following this tutorial.

This should be in the guides section as this is nothing development related

Benjamin_L said:
This should be in the guides section as this is nothing development related
Click to expand...
Click to collapse
thanks, but how can i delete this post?

androwide said:
thanks, but how can i delete this post?
Click to expand...
Click to collapse
Report it and let the mods do it

Will this void my warranty? If yes, then does "unrooting" bring back my warranty?

pratyush2173 said:
Will this void my warranty? If yes, then does "unrooting" bring back my warranty?
Click to expand...
Click to collapse
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.

Benjamin_L said:
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.
Click to expand...
Click to collapse
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)

pratyush2173 said:
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)
Click to expand...
Click to collapse
Xiaomi does not stand above european law so not really. But as I said, depends where you live of course. A modified boot image should do no harm still.

Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?

estetico said:
Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?
Click to expand...
Click to collapse
It will overwrite the patched boot image so you'll have to update the patched boot image for each update

Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
are you sure? If the OTA has check for modified system partition it will fail.

munchy_cool said:
are you sure? If the OTA has check for modified system partition it will fail.
Click to expand...
Click to collapse
I didn't have a chance to try it yet so I can't be sure. Will test when the September update drops

Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?

veeru1saini1 said:
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?
Click to expand...
Click to collapse
Most likely the last yes.

I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.

Yaroray said:
I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.
Click to expand...
Click to collapse
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot

T4Ump said:
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot
Click to expand...
Click to collapse
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?

Yaroray said:
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?
Click to expand...
Click to collapse
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.

T4Ump said:
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.
Click to expand...
Click to collapse
Twrp just does not work properly currently. It will be supported in the near future

Benjamin_L said:
Twrp just does not work properly currently. It will be supported in the near future
Click to expand...
Click to collapse
Yea, i know. I tried first day when i got mobil, twrp root etc.

Magisk W/ Android 11 on OnePlus 8 Pro

Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!

Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot

How do I get Magisk 21.0 to install through Magisk Manager?

You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly

CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.

You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt

CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.

Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.

akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB

Here is the exact size.

Problem uploading image

I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??

dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!

imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted

CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot

rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.

akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot

dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.

rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.

[GUIDE] Simpler Way to Get Rid of T-Mobile USA Branding

For those who only want custom roms - an easier way to convert from T-Mobile USA. You don't need to flash system/product/vendor partitions. No restoring modem to get signal, data will work on first boot after you install a custom rom.
This could be easily done on Linux and Windows too. I don't recommend flashall. Just do it manually. For this discussion, I am converting T-Mobile to Euro:
1. Get T-Mobile MSM package from HERE. Get Euro package (for converting) from HERE
2. Flash T-Mobile MSM (you can't transfer the MSM package via flash drive, as some files will be corrupted and you won't be able to start the package. Just download straight, unzip and execute the exe. file)
3. Boot, enable OEM unlock (you'll have to connect to the internet for a few minutes) and unlock bootloader (get unlock bin from Oneplus)
4. Once unlocked, boot again, connect to PC, enable Developer options, enable ADB. Open terminal and execute adb command:
Code:
adb reboot fastboot
You will get into 'fastbootd' recovery, but that's how it should be. Your fastboot commands will be accepted.
5. Now, unzip the downloaded Euro version, go to that directory, open terminal and execute manually the following commands separately (just copy and paste a single command from the code below) followed by pressing 'enter', i.e. paste the command, press enter, paste the next command, press enter. Watch the terminal to make sure that each command went through:
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash modem modem.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
6. Once done, don't reboot in system. Instead, reboot into bootloader. From that, follow directions to install a custom rom. If Lineage, for example, flash their recovery first (fastboot flash recovery...), then boot into that recovery. Don't flash their 'copy partitions' files. Instead, just install the latest release via 'adb-sideload' (factory reset before or after flashing is required). Then boot into System normally. Your phone will have normal IMEI/Baseband and it will be listed as IN2013.
This is only for those who want custom roms. No stock OOS updates, which vendor is not needed any way, as all custom roms for Oneplus 8 provide their own vendor.

How to Unlock Oneplus 8 tmobile Bootloader without unlock token​

farhansaeeddnp3021 said:
How to Unlock Oneplus 8 tmobile Bootloader without unlock token​
Click to expand...
Click to collapse
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.

optimumpro said:
Short answer - Forget it, for good. Here is the long one:
Tmobile branded Oneplus 8's bootloader is tied to a key generated based on the unique numbers, which in turn, are tied to your device's unique IMEI. This is why it is a 2 step process: first, you generate a sequence of 2 long numbers on the phone. Second, you send those numbers together with your IMEI to Oneplus. Only after that, you get the token, which could only work on your phone.
This is why, at Oneplus online store, unbranded Oneplus 8 is $100 more expensive than the branded one. The latter is software crippled, and on other sites, the difference is up to $200. You get what you paid for.
Click to expand...
Click to collapse
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.

farhansaeeddnp3021 said:
thanks for replay. recently i unlock oneplus 7t pro Mclarn without unlock token. so that why i was thinking about it.
Click to expand...
Click to collapse
That's because there is a modified MSM tool for Oneplus 7 with a removed device name check. That enables you to flash global firmware on any Oneplus 7 variant. This is not possible on Oneplus 8.

Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)

aikattx said:
Hi. Im on oxygen os 11.0.4.6IN55CB. do i need to downgrade to TMO android 10 before proceed with this? My device is TMO unlocked and bootloader locked (I don't mind about the bootloader, i can unlock it anytime)
Click to expand...
Click to collapse
No. You don't. The tool already includes the downgrade software.

Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues

FoxyDrew said:
Why did you link to and suggest the Euro version of this ROM? The global version is recommended if converting from T-Mobile and should be used instead. Also creates a discrepency from the title of this thread, you did not make a guide on how to convert to global, you made a guide on how to convert to the European version.
to be fair tho shouldn't really cause issues
Click to expand...
Click to collapse
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.

optimumpro said:
You are right, but as you said, there would be no difference in the outcome, except that your phone will show IN2013 instead of IN2015.
Click to expand...
Click to collapse
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha

FoxyDrew said:
That's not the ONLY difference, the differences there are will probably be imperceivable in daily use however. Honestly only brought it up because I saw the title of the thread and the a link to the euro ROM and was a tad confused for a sec
Edit: "or Euro" I actually audibly laughed when I saw that, that's great. Great tutorial man haha
Click to expand...
Click to collapse
All right. Thanks for a very useful comment. Ha-Ha!

optimumpro said:
All right. Thanks for a very useful comment. Ha-Ha!
Click to expand...
Click to collapse
Ouch you seem salty lol, I could say the same

FoxyDrew said:
Ouch you seem salty lol, I could say the same
Click to expand...
Click to collapse
That's because you seamed to sound sarcastic. "Great guide, ha-ha"

optimumpro said:
That's because you seamed to sound sarcastic. "Great guide, ha-ha"
Click to expand...
Click to collapse
oh no that was genuine lol

FoxyDrew said:
oh no that was genuine lol
Click to expand...
Click to collapse
All right. My apologies. Sometimes it's difficult to figure out intentions on the internet.

Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.
Has anyone seen this before?

ManlyP0tato said:
Hi and thank you so much for this guide! I'm having a problem with flashing the global rom, it tells me flashing isnt allowed for critical partitions, despite having done both the unlock (fastboot menu confirms it) and fastboot oem unlock_critical.View attachment 5426977 Has anyone seen this before?
Click to expand...
Click to collapse
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.

optimumpro said:
Step 4: adb reboot fastboot
This has to be done on a live device with adb enabled, connected to PC and typed on PC terminal. As a result, you are not rebooting into fastboot, but in recovery with fastboot commands enabled.
Click to expand...
Click to collapse
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader.
this is the screen I'm getting, is this fastboot with recovery or only fastboot?
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.

ManlyP0tato said:
Thanks for your reply!
Is this the difference between fastboot and fastbootd?
Despite using the command and going into fastboot I still can't seem to make it work, even selecting recovery mode in fastboot only brings me back here. I of course installed a fresh MSM version beforehand and unlocked the bootloader. View attachment 5426993 this is the screen I'm getting, is this fastboot with recovery or only fastboot?
View attachment 5426995
Before reaching fastboot though it takes me to the oneplus language select screen, then gives me the option to wipe, fastboot or recovery, maybe it has something to do with this?
Thanks again for your time.
Click to expand...
Click to collapse
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.

optimumpro said:
Wrong action. You'll never be able to flash critical partitions from fastboot, i.e., the screen in your picture. After executing the adb command in step 4, your phone will enter recovery (not fastboot) and you must stay there. Nowhere my instructions say reboot to fastboot. So, stay in recovery and execute all further commands from your PC.
Edit: Yes, that's the difference between fastboot (your screen shot) and fastbootd, which is Recovery with fastboot commands support.
Click to expand...
Click to collapse
Ooh! I see I misunderstood that, it works just fine from the recovery screen!
I tried flashing the entire global rom because I don't want a custom rom but I just got a qualcomm crashdump mode . Currently using MSM to fix that. Is it even possible to use the global rom with the Tmobile model? Otherwise I'll just use Lineage.

Custom Rom / rooting Options vor TB-125FU (Lenovo Tab M10 Plus 3rd Gen)

Hey everyone,
I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU. Are there any recommendations like compatible GSI roms or TWRP/magisk?
Thanks in advance for your help!

You should just be able to install matiek form my understanding

I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.

holmesmalone said:
I need some information, too. Bootloader unlock is different. Device doesn't respond to bootloader commands with Minimal ADB Fastboot 1.4.3.
Click to expand...
Click to collapse
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?

art99 said:
I just got an tb125fu
Bootloader unlock was no problem, maybe it works for you now with the latest versions?
Click to expand...
Click to collapse
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.

holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
I installed corvus os gsi on it. i have no custom recovery.

peteonu said:
I installed corvus os gsi on it. i have no custom recovery.
Click to expand...
Click to collapse
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.

holmesmalone said:
TWRP is convenient, but not absolutely necessary. Would like a Lineage rom though.
Click to expand...
Click to collapse
Agreed. I've been looking into compiling TWRP myself but this is all new to me. The only device with TWRP with this chipset is the Redmi 9. I've compared both boot.img's and they are both setup differently. If I had more knowledge ont he subject I could easily achieve this I believe.
If I have time I'll compare Gen 2 vs Gen 3 boot.img's, that may help understand the folder and file structure better.

holmesmalone said:
The issue I had, and resolved, was the lack of the latest fastboot drivers. Gained root with Magisk successfully.
Click to expand...
Click to collapse
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks

el7145 said:
What process did you use with magisk to gain root after bootloader unlock? was it as simple as installing magisk manager and flashing root through the manager?
Thanks
Click to expand...
Click to collapse
The same process worked for me.

holmesmalone said:
The same process worked for me.
Click to expand...
Click to collapse
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)

el7145 said:
How did you obtain the boot.img to patch??? I cant find the stock firmware anywhere, and im not clear on pulling the stock boot.img (getting permission denied errors when attempting via adb)
Click to expand...
Click to collapse
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.

holmesmalone said:
Select and download your preferred rom. Then unzip the rom and in the unzipped folder select the boot.img file and use it.
With some devices and roms, under some circumstances, the vbmeta.img file can and should be used. If I can recall correctly, Magisk will specify.
Click to expand...
Click to collapse
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet

el7145 said:
ok, so ur just pulling the boot img from one of the GSI roms...im just trying to pull the stock boot img...do you happen to know where one can download the stock firmware for this device, this is my 1st lenovo tablet
Click to expand...
Click to collapse
LMSA. https://pcsupport.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
Use this tool. Install and explore the file and folder structure it creates. Interrupt the process before it flashes your tablet for it will erase the files you need from your computer if you don't. Use trial and error here.

Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.

el7145 said:
Since the original question was about root, Ill keep this going
I was able to download the most recent ROM from Lenovo rescue which was super simple, it downloads the ROM first and wont start the flash till you click the button. I did retrieve the stock boot.img, patched it, and flashed it, rebooted and had root. Heres where the many hours of fun started...I realized my wifi wasnt working (good sign something was messed up during flash). I realize the ROM downloaded from the Lenovo Rescue was newer then my old ROM. So I had flashed the newer boot.img over the old ROM (not good). I went back to Lenovo rescue to actually make use of the rescue and flash a full ROM. After completion I became stuck in fastboot mode. I could boot to recovery but not system and every restart or shutdown and restart would go straight to fastboot.
I did try to manually flash the ROM using what i thought was the right files and order (using flashinfo.txt as the order and MT6768_Android_scatter.txt for the partition names for each image). Everything flashed successfully, but upon reboot I was still stuck in fastboot mode. I tried everything I could think of and even ran the Lenovo Rescue a few times.
After many hours, I came across this command for fastboot..."fastboot set_active a" which finally allowed me to boot into system. I assume this tablet uses the A/B slot partitions, but I think they only make use of the A for boot? Thats my thought
So next is too try to patch the correct disc.img for my current rom (which is the latest from Lenovo Rescue) and flash again making sure to flash to the boot_a partition and hopefully everything goes like it should
Hopefully that command helps someone save many hours if they find themselves stuck in fastboot mode while rooting and/or flashing.
Click to expand...
Click to collapse
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?

Siege9929 said:
I'm trying to solve the fastboot issue but I can't find fastboot drivers for the tablet. Have any suggestions?
Click to expand...
Click to collapse
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized

el7145 said:
im assuming in device manager, you have a yellow exclamation by "Android"? you need the mediatek drivers.
Go here https://developer.android.com/studio/run/oem-usb
scroll down, dont make the misake of clicking on "Lenovo", you are clicking on the section labeled "MTK" download the zip, go to device manager and manually update the driver, once updated fastboot should work
at cmd run "fastboot devices" to make sure your device is recognized
Click to expand...
Click to collapse
Manually selecting the "Android Bootloader" driver fixed it. Thanks!

I just got my TB125FU to replace my 7-year-old Google Pixel C on its last legs.
Its Hardware ID is USB\VID_0E8D&PID_201C&REV_0100
I found a pack of Mediatek drivers here.
It's a bloated pack, so I extracted just the files needed for the TB125FU and attached to this post.
Once installed, my tablet appeared with a "fastboot devices" command.
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.

hugehead83 said:
I have also had good luck with the latest firmware for Motorola/Lenovo devices here.
Click to expand...
Click to collapse
just an fyi: thats not the most recent firmware, the lenovo rescue tool had the latest, which at the moment for my device a few days ago was TB125FU_S000118_220927_ROW