Database Users

Firmware?

Hi all.
I am going to flash LilneageOS 15.1 on my brand new A1.
We all know it DOESN'T contain any firmware blob (I mean, the stuff that usually drives the baseband modem, the wifi, the touch screen and so on) so I'd need to be sure I am on the latest one before flashing the ROM.
I've been unable to find here a "firmware only" release, also because in a few threads the word "firmware" is used as "ROM".
Is there anyone willing to point me to the proper post?
Please, be patient with me as I'm new to the Xiaomi world, but not new at all with Android and custom ROMs and recoveries.
Thanks in advance.

Hi, I recently flashed Lineage OS 15.1(Latest version) coming from Stock 8.1 August Update.
I suggest you follow the guide on the Mi A1 Lineage OS wiki which I followed and also use GApps(this survives OTA updates or something) provided by Lineage OS maintainer in his thread + 17.x magisk.
However ok Google does not work from Google App, assistant, maps, etc but the mic works fine.
I have seen people say flashing 8.1 May Beta modem(firmware available here) fixes the issue - see attached image - although I haven't tried it myself.
Hope you have no issues with Lineage OS, it's a bit complicated to flash on this device as it is A/B partition. Ok Google hotword is the only problem I have faced which is outweighed by the many essential features Lineage provides over stock.
If you need additional help please ask, because I myself found it tough to flash initially.
Edit: Having flashed stock GApps zip I also had the issue of camera FC, which was fixed by installing this camera through Magisk, which I will recommend anyway for better photo quality.

I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.

Uqbar said:
I have just started the process with TWRP recovery by following the LineageOS wiki up to step no.5.
The device is not booting to recovery but rather to system. So I am stuck here.
Click to expand...
Click to collapse
Have you already done fastboot OEM unlock?

iG0tB0lts said:
Have you already done fastboot OEM unlock?
Click to expand...
Click to collapse
I am strictly following the official wiki. Could it be a problem with the A/B partitions?

Uqbar said:
I am strictly following the official wiki. Could it be a problem with the A/B partitions?
Click to expand...
Click to collapse
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.

iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Yes, I did the unlock.
What you say deviates from the original wiki.
I am now updating the system so maybe I get the latest firmware.
I will try again soon after.

iG0tB0lts said:
If you have already done the
Code:
fastboot oem unlock
then reboot to bootloader(Hold Volume Down + Power) and once again do fastboot boot "recovery.img". That will get you into recovery mode.
Click to expand...
Click to collapse
Nope. It doesn't reboot, even if the command line says it did.
I have found something about this problem, but am really puzzled as the official wiki isn't mentioning anything about A/B slots.

Fastboot not working anymore after the android 10 beta update

Hi xda Community,
I updated to the android 10 a week ago or so. Today i tried to downgrade to 9.0.1.7 cause the beta is way to buggy for me.
My problem is, that I can't use fastboot anymore like it was before. For example, I cannot boot via 'fastboot boot' method into recovery.
Every time I try to boot something I get FAILED (remote: unknown command)
C:\adb>fastboot boot twrp-3.3.1-1-fajita.img
downloading 'boot.img'...
OKAY [ 0.665s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.681s
Does somebody have a fix for this? Due the lack of TWRP, I cannot downgrade or don't now how to downgrade nor to install magisk.
Thanks in advance and have a great new week y'all

Correct me if I'm wrong, but this command will no longer work with Android Q due to Google new partition scheme.
You can check this thread out: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 - it contains fastboot roms of Android P, which you may flash, according to tutorial.
You may also try a local update method with the rollback package (https://www.getdroidtips.com/rollback-android-10-q-pie-oneplus-6-6t/).
Note that this will, unfortunately, wipe your data.

fastboot flash boot twrp.img should do the trick.

Cats_PJs said:
fastboot flash boot twrp.img should do the trick.
Click to expand...
Click to collapse
That will flash the recovery image but it won't be decrypted at all. I tried that and had to wipe my phon.

fogame said:
That will flash the recovery image but it won't be decrypted at all. I tried that and had to wipe my phon.
Click to expand...
Click to collapse
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.

Cats_PJs said:
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.
Click to expand...
Click to collapse
Lol after spending all day I decided to go back to pie. Now to get play store certified again without locking the bootloader.

Magic Stick said:
Correct me if I'm wrong, but this command will no longer work with Android Q due to Google new partition scheme.
You can check this thread out: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 - it contains fastboot roms of Android P, which you may flash, according to tutorial.
You may also try a local update method with the rollback package (https://www.getdroidtips.com/rollback-android-10-q-pie-oneplus-6-6t/).
Note that this will, unfortunately, wipe data.
Click to expand...
Click to collapse
- Is their a way after this to get magisk working without fastboot boot twrp.img?
Cats_PJs said:
fastboot flash boot twrp.img should do the trick.
Click to expand...
Click to collapse
- Is their a way to only boot up twrp instead of install twrp?
Cats_PJs said:
Was just responding to op on the correct command to flash twrp in Android 10.
https://forum.xda-developers.com/showpost.php?p=80639099&postcount=2856
That is the method I followed to upgrade, worked perfectly, it did wipe data. Decryption does work.
Click to expand...
Click to collapse
Do I get updates for android 10 with this version when it releases?
Thanks in advance y'all

deaddevil2299 said:
- Is their a way after this to get magisk working without fastboot boot twrp.img?
Click to expand...
Click to collapse
Sure, you flash a patched boot img, with fastboot. Look into the Guides and News section you'll find what is needed. Either in 9.0.17 thread ( not renamed yet) or in How to keep twrp and Magisk thread
I don't see the point of having twrp for now, especially with the trick necessary to have decryption working.
It has been said millions time that updates work perfectly with or without twrp, with or without Magisk

Striatum_bdr said:
Sure, you flash a patched boot img, with fastboot. Look into the Guides and News section you'll find what is needed. Either in 9.0.17 thread ( not renamed yet) or in How to keep twrp and Magisk thread
I don't see the point of having twrp for now, especially with the trick necessary to have decryption working.
It has been said millions time that updates work perfectly with or without twrp, with or without Magisk
Click to expand...
Click to collapse
I'm just wondering why their isn't any fastboot version mentioned in my fastboot mode. Looks a bit broken.
I think I wait till their is a stable way to root.
Thanks for the answers

Working Custom ROM (GSI) For Onn 8 Inch?

I really need help with finding a good custom ROM for my ONN 8' inch tablet. It is already rooted and has TWRP recovery installed. Thanks in advanced.

I really like Pixel Experience, I have a Pixel so I guess it makes my life easier with the same UI. Bliss worked well too for me. I've read that Havoc is good but I haven't used it.

razredge said:
I really like Pixel Experience, I have a Pixel so I guess it makes my life easier with the same UI. Bliss worked well too for me. I've read that Havoc is good but I haven't used it.
Click to expand...
Click to collapse
Do you think you can send me a link with the ROM download and instructions on how to install it? I have TWRP and root access so don't worry about that. Pixel or Bliss.

antoinejr1111 said:
Do you think you can send me a link with the ROM download and instructions on how to install it? I have TWRP and root access so don't worry about that. Pixel or Bliss.
Click to expand...
Click to collapse
Here's a full list.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
I think you can find the flashing instruction in this sub-forum. Just look around. I think it's in How to Unlock by tek3195 but I'm not sure.

razredge said:
Here's a full list.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
I think you can find the flashing instruction in this sub-forum. Just look around. I think it's in How to Unlock by tek3195 but I'm not sure.
Click to expand...
Click to collapse
Which one should I download?

https://github.com/EnesSastim/Downloads/releases/download/2019-08-24/PixelExperience_Plus-9.0-arm64_ab.7z
Honestly if I were you I'd read up a bit before attempting to flash a GSI. Do you know the difference between A and A/B? Do you know you need a copy of your vbmeta?

razredge said:
https://github.com/EnesSastim/Downloads/releases/download/2019-08-24/PixelExperience_Plus-9.0-arm64_ab.7z
Honestly if I were you I'd read up a bit before attempting to flash a GSI. Do you know the difference between A and A/B? Do you know you need a copy of your vbmeta?
Click to expand...
Click to collapse
I know what type of devices my tablet is, but I do need a "vbmeta.img"
I know how to flash it though.

I tried to install Pixel Experience but it wont go past the Google Logo help!
https://github.com/EnesSastim/Downl...19-08-24/PixelExperience_Plus-9.0-arm64_ab.7z

antoinejr1111 said:
I tried to install Pixel Experience but it wont go past the Google Logo help!
https://github.com/EnesSastim/Downl...19-08-24/PixelExperience_Plus-9.0-arm64_ab.7z
Click to expand...
Click to collapse
When on that boot logo use adb to iissue the following command: adb shell setprop debug.stagefright.ccodec 0
After booted up and you make it through setup make sure to modify build.prop manually and add debug.stagefright.ccodec=0 to the end of the file so you dont need adb every reboot.
Sent from my SM-G975U1 using XDA Labs

jwarrior319 said:
When on that boot logo use adb to iissue the following command: adb shell setprop debug.stagefright.ccodec 0
After booted up and you make it through setup make sure to modify build.prop manually and add debug.stagefright.ccodec=0 to the end of the file so you dont need adb every reboot.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I know this is old but I have the same issue with one thing different. I followed everything I needed to from here: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
I was rooted with Magisk but they say that shouldn't matter. I have the same device BTW, android 9. Unlocked bootloader and can flash in fastboot, twrp and even SP flash tool.
So I boot to TWRP, do a factory reset and reboot back to twrp and flash the GSI you linked to. everything goes great...no errors nada. It boots to the letter G, but in a few seconds it says to enter the password to access the device (it's encryption). Reboot to fastboot, flash vbmeta from stock, reboot and same thing. Reboot to twrp and format the data (removes encryption). Reboot system again and this time i hear the PC acknowledge its connected once the device boots to the letter G, but no ADB or storage access and just hangs on the big letter G. So I reboot to twrp, ADB works. I pull the build.prop and add the recommendation above and remount the device using ADB remount and pushed it back to system. Reboot and again, boots to the letter G and hangs there.

razredge said:
I really like Pixel Experience, I have a Pixel so I guess it makes my life easier with the same UI. Bliss worked well too for me. I've read that Havoc is good but I haven't used it.
Click to expand...
Click to collapse
My Onn 8" is A-only. Pixel Experience requires an AB-partitioned phone.

DragonFire1024 said:
I know this is old but I have the same issue with one thing different. I followed everything I needed to from here: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
I was rooted with Magisk but they say that shouldn't matter. I have the same device BTW, android 9. Unlocked bootloader and can flash in fastboot, twrp and even SP flash tool.
So I boot to TWRP, do a factory reset and reboot back to twrp and flash the GSI you linked to. everything goes great...no errors nada. It boots to the letter G, but in a few seconds it says to enter the password to access the device (it's encryption). Reboot to fastboot, flash vbmeta from stock, reboot and same thing. Reboot to twrp and format the data (removes encryption). Reboot system again and this time i hear the PC acknowledge its connected once the device boots to the letter G, but no ADB or storage access and just hangs on the big letter G. So I reboot to twrp, ADB works. I pull the build.prop and add the recommendation above and remount the device using ADB remount and pushed it back to system. Reboot and again, boots to the letter G and hangs there.
Click to expand...
Click to collapse
So I figured it out. If you are doing this from stock, you will have to grab the vbmeta image from the firmware then boot to fastboot and erase a few things. first start by erasing the system. When done, you have to flash the vbmeta image to vbmeta with option --disable-verity. then flash vbmeta again and use option --disable-verification. whenever you flash an image, even when flashing TWRP to its recovery, you have to flash vbmeta and disable verity and verification before and after flashing. This tablet is encrypted in boot, recovery, system, cache and userdata. Vendor seems to not need manual flashing. Miss disabling verity/verification before and after on any of those, the tablet will hang at the boot logo forever. In some cases I managed to get it to still boot, only to have the systemUI and other apps crash within minutes because they could not store data.

$cronos_ said:
My Onn 8" is A-only. Pixel Experience requires an AB-partitioned phone.
Click to expand...
Click to collapse
AB here...weird.

[KB2007][C41][OOS12]OnePlus 8T+ 5G ( T-Mobile )stock boot, magisk patched boot and mod recovery

Attached with this post are :
+ Stock boot of OOS12 ( C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Magisk patched boot of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007)
+ Modded stock recovery of OOS12 (C41) for Oneplus 8T+ 5G (T-Mobile KB2007) with ADB enabled, security disabled, ability to debug enabled and allow mock location by default.
Just flash in Fastboot mode as usual!

Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!

bookofjoshua said:
Hi! I'm not very up-to-speed. I just restored my phone to TMO android 11, I was running PixelExperience and I have run the EU rom, what post should I look to for "flash...as usual". I'm not sure what the normal process is. Thanks!
Click to expand...
Click to collapse
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.

LinhBT said:
I don't really understand your question but these files are for OnePlus 8T+ 5G Stock OOS12 C41 only, so if u r on A11, then these files are no use for u bro.
Click to expand...
Click to collapse
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.

bookofjoshua said:
It says "just flash in fastboot as usual". I don't know what "as usual" means. I wasn't looking for info on using them with my phone, just what I need to look at for the flashing procedures as I have seen several different methods and requirements,.
Click to expand...
Click to collapse
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!

LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon

kevinco1 said:
So by using those fastboot commands you'll be able to root the KB2007 if you are running 12 as long as your bootloader is unlocked as well as SIM unlocked? That's my current situation right now and was looking go root sometime soon
Click to expand...
Click to collapse
True, if you are on OOS12 C41 ( TMO ) to be specific, then u can use the magisk patched boot image from my post to root your device using normal fastboot commands as mentioned!

LinhBT said:
Ah, what I mean by "flash in fastboot as usual" is : just flash those files in fastboot mode with fastboot commands which is used to flash boot.img recovery.img.....etc. In this case, are "
+ fastboot flash recovery recovery.img
+ fastboot flash boot boot.img
or you may input option like :
+ fastboot --slot-all flash boot boot.img ( to flash boot.img into both boot slot A/B )
Just that, my friend!
Click to expand...
Click to collapse
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore

bookofjoshua said:
Thank you! I appreciate you taking the time to clear that up for me, and actually type the commands. I was originally flashing Roms to get access to my 5G radio, as I'm using it on Verizon towers, but after applying the latest update my phone connected to 5G so I may not even need it anymore
Click to expand...
Click to collapse
There's a guide to enable 5G and/or VoLTE for KB2007 also in our forum. But since u did it, congrats

I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?

works beautifully

heyChristo said:
I just got this device yesterday. Already sim unlocked and requested the bootloader unlock code. Since it's only day one, I haven't flashed the euro firmware/rom yet. Is it worth upgrading it to 12 and then simply rooting it. I don't mind running stock for a while, but I hear 12 is really that bad. Obviously it can't be too bad if you are using it. I am just hesitant on installing the update. What are your thoughts?
Click to expand...
Click to collapse
not bad so far just more security . disabled pinch out hidden menu.. had to create code and use dialer to access hidden menu. i fastbooted this and now rooted have not tried recovery yet im afraid actually

So I converted mine to the EU version and then to the global version and updated to 12 via OTA. However I could not find the file prior to flashing so I couldn't pull it to the PC. Obviously I lose root on that full update. Can I flash this boot image to restore root or will that brick the device?

For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image

Hey. Thanks for all your work. I'm rooted on stock kb2007. My OTA update to 41 is not working. Would flashing these before asking the system to update fix it, or are these for after you unroot and allow the update. I think the unroot is where I'm having trouble. I uninstalled Magsik and wiped cache for google play. The OTA still won't work. I'm sure there is every note on XDA about this, but I thought I'd ask here because I think I'm so close.

droidgreg said:
For those that want the latest C42 update with September security, find attached the stock boot image as well as the magisk patched image
Click to expand...
Click to collapse
you wouldnt have the last android modem img for android? thx in advance. i forgot to safe modem via msm tool before i converted to global smh

The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online

kevinco1 said:
The real question is where can obtain the original firmware for C42? Haven't been able to find it anywhere online
Click to expand...
Click to collapse
There is no 100% confirmation that C42 was released as a full update and not incremental on C41.

If I'm already on Android 12, C41 unrooted than I don't need to do any other flashing except the magisk patched boot image from the post to root my device using normal fastboot?
What is the purpose of the modded stock recovery?

MustangLife03 said:
What is the purpose of the modded stock recovery?
Click to expand...
Click to collapse
The main reason is enabled adb access.
Having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
Though there is unofficial TWRP for A12 which makes stock adb enabled a bit obsolete in this case.
But anyway thanks for LinhBT for compiling it.

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