yashsingh1/xdaforums huggingface dataset:
[Thinkpad Tablet General] joeblowma:
Thanks to everyone commenting in this thread, haven't had a rooted android since my nexus 7 so it was a (tiny) bit of a learning curve going in without starting at a custom recovery compounded by the changes that have been made to make rooting less attractive (ie: breaking app installation for things like netflix).

One thing I wish I had known going in on this device not already mentioned... hopefully someone else sees this that needs it:

fastboot flashing unlock

rather than fastboot oem unlock or fastboot oem unlock-go which were the "easy" answers via google. Tried too many drivers thinking that was the issue despite fastboot devices showing the tablet no problem.

Left with a question. Everything seems to be working great, but I'm getting the 5s "you are unlocked" delay at boot which is no big deal, I can manage ARM microcode if I ever want to try to fix that in lk.img.

What I'm finding truly annoying though is a persistent silent notification about a serial port being enabled and affecting performance. Did I mess it up in simply skipping touching verity/vbmeta, as far as I know the engineer binaries aren't present so that isn't an option to disable it, did I somehow manage to get a boot.img that is debug enabled (I used boot.img not boot-debug.img)... or is this persistent notification yet another cost of having root?
[Thinkpad Tablet General] hugehead83:
For sure, it would be nice to kill that serial port notification on mine too.
[Thinkpad Tablet General] el7145:
It's pretty simple, definetly a very annoying message...go to settings, apps, see all apps, click the 3 dot menu at top right, show system, go to android system, notifications, turn off developer messages
[Thinkpad Tablet General] el7145:
I believe I used the thread here on xda-developers for the previous m10 plus 2nd gen...the bootloader unlock instructions there were accurate, and they state if "fastboot oem unlock" doesnt work use "fastboot flashing unlock"

Your right though, not any walkthroughs for our actual 3rd gen m10 plus, although this thread seems to be a great starting point now, but usually you cant get someone to read pages, lol
[Thinkpad Tablet General] joeblowma:
Hah, that'll teach me... I completely forgot about the 3 dot menu to get to system stuff. Brilliant, suppressed and thanks! Still curious why it happens and if there is some actual option to just disable it that the engineer tool should be able to write, but not seeing it is "good nuff".

I think I ran into it from some random magisk guide for something else entirely, probably a samsung or something, the m10 and other lenovo ones I arrived at through google just had the "oem unlock-go" variants. Never mind getting someone to troll through pages in a forum... a paragraph of instructions seems to be a challenge for a lot of people to follow most days.

Problem to save for future frustration: what to do when the next OEM update arrives...
[Thinkpad Tablet General] okaraosp29:
i bought rebranded version of this tablet. Moto Tab G62 TB128FU and currently running lenovo's latest ROM. but i'm not able to unlock the bootloader, unlock command is failing. which drivers you used?

I cleaned all previous ADB and fastboot drivers and fresh installed the latest.

ADB/fastboot devices comand is working yet im getting this error.

fastboot oem unlock

FAILED (remote: 'unknown command')

fastboot: error: Command failed
[Thinkpad Tablet General] hugehead83:
Fastboot flashing unlock

OEM unlock command has been depreciated for 7 years or so.
[Thinkpad Tablet General] okaraosp29:
i used both commands that other users mentioned above but it's no use same error
[Thinkpad Tablet General] hugehead83:
Do you see your tablet listed after a "fastboot devices" command?
[Thinkpad Tablet General] holmesmalone:
Use this link for resources in the States. (Search "lenovo lsma" in your favorite search engine for other appropriate links).

support.lenovo dot com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa

Install and run the LSMA, and interrupt the process as necessary to retrieve the files before the scripts delete them from the file folder it establishes at installation.

I think this is where I found the correct fastboot drivers. Ensure you have the correct drivers, cross reference Device Manager, and the "fastboot devices" command.

adb reboot bootloader
fastboot devices
fastboot flashing unlock
or
fastboot oem unlock
[Thinkpad Tablet General] okaraosp29:
Sorry i didn't understand, which files are we talking here? And where's the location?And at which point I should interrupt the process could you please explain in little more detail? This is my first time with moto/Lenovo BL unlock. And BTW my device name is TB128FU not 125 does that make any difference?

BTW i ran commands through LSMA location but got error as well

Also i noticed in BL mode it shows

BOOTLOADER VERSION -

BASEBAND VERSION -

as empty
[Thinkpad Tablet General] okaraosp29:
yes

And in BL mode it shows

BOOTLOADER VERSION -

BASEBAND VERSION -

as empty
[Thinkpad Tablet General] holmesmalone:
When you install the Rescue and Smart Assistant (LSMA as it is known) it will create files and folders at C:\ProgramData\RSA. (You may have to unhide this folder). Under RSA\Download you will see this folder hierarchy. See first image.

Monitor this program's process as it runs through the Rescue sequence. You must intercept the program before it installs the ROM onto your tablet and copy it to another location on your disk. The program will delete the ROM once it runs and your efforts will be thwarted. I learned this through trial and error. Cannot recall exactly what point I interrupted the process. I have another tablet arriving by the end of the week. I will post again after I do this to the new tablet.

Unlocking the bootloader is done in the Windows console. Drivers will be installed at C:\ProgramData\LMSA\drivers. Fastboot driver installation must be verified in Device Manager. To insure the correct driver is selected on must select "Browse my computer for drivers" and on the next page, "let me pick from a list . . . " and direct Windows to the specific driver via the Have Disk button and the Browse button.

Minimal ADB and Fastboot helps with ADB but you should add ADB to Environmental Variables in Advanced System settings. If you need a tutorial, it's here: https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
[Thinkpad Tablet General] okaraosp29:
ROM files i alredy have backed up, apart from that only tools folder has QFil_V3.zip all other folders are empty
[Thinkpad Tablet General] holmesmalone:
Look here for drivers:
[Thinkpad Tablet General] holmesmalone:
The correct drivers are located here: C:\ProgramData\LMSA\drivers\ADBDriver

These will appear after running Rescue and Smart Assistant, selecting Rescue and following the steps indicated.

The correct fastboot command is: fastboot flashing unlock
[Thinkpad Tablet General] okaraosp29:
i did what you said but still no luck. its not detecting amd64 folder files as drivers. can you send me your drivers in a zip?
[Thinkpad Tablet General] holmesmalone:
I have Test Mode enabled, and didn't consider it may be linked to your problem with adding driers.

Go to this page and follow option two:

How to Enable or Disable Driver Signature Enforcement in Windows 10

How to Enable or Disable Driver Signature Enforcement and Test Mode in Windows 10

www.tenforums.com
[Thinkpad Tablet General] okaraosp29:
just tried this no luck. I think MOTO has made sure the device stays unlockable. your device name is TB125FU right? mein is 128. may be 128 is not unlockable or may be moto version of this tab.

do you have any other suggestion for me to try?
[Thinkpad Tablet General] holmesmalone:
This may help:

https://tweakdroid.com/bootloader/lenovo-tab-m10-plus-3rd-gen-tb128fu/

What response do you get when you type "fastboot devices" in the console?
[Thinkpad Tablet General] okaraosp29:
I've seen and followed these kinds of websites they just chage device name for perticular brand and make it a seperate article instead of personally testing it.

on fastboot devices command it lists the connectected devices.

as i said apart from unlocking command every other ADB/FASTBOOT commands work.

Please send your driver in a zip ill try that
[Thinkpad Tablet General] holmesmalone:
Lenovo unlock tool.rar

drive.google.com
[Thinkpad Tablet General] okaraosp29:
i ment driver files.

are you in ARES telegram grp?
[Thinkpad Tablet General] holmesmalone:
I am in no telegram group. The google drive link is for the TB128FU

You may find this forum helpful:

https://4pda.to/forum/index.php?forums=581&topics=1047797&act=search&source=pst&query=bootloader&__cf_chl_tk=3yUS9yzdaRRZWt6An8vLgVAWPobHNPLYZeDQ8tXD2HY-1669141035-0-gaNycGzNCNE
[Thinkpad Tablet General] zippy411:
I created a Root guide for my Lenovo M10 Plus 3rd Gen (TB125FU)

It is located here

Lenovo M10 Plus 3rd Gen Root Guide (TB125FU)

Notice! This process also completely resets your tablet! Backup all files and information. This is just me documenting my process for rooting my tablet. I am not responsible for any damage or lost information due to the process changing, errors...

xdaforums.com
[Thinkpad Tablet General] nemo081:
Hello everyon

i am looking for a way to root this tablet. It arrived 2 days ago, so it's still clea

I guess I'm in the right thread from the titl

Can you give me a guide on how to root? (I already searched on the internet but none of the guides worked)

Note: I have no intention of changing ROMs (maybe later) for the moment I have to use apps that need root

Thanks to anyone who replies
[Thinkpad Tablet General] nemo081:
Sorry, I missed the last message. I try to follow the instructions
[Thinkpad Tablet General] jazzh:
Great thread.
[Thinkpad Tablet General] joeblowma:
Well, I knew it would happen eventually... I'm on

TB125FU_S000118_220927_ROW (Sept 27 2022)

I see

TB125FU_S000139_221208_ROW (Dec 8 2022)

exists now, anyone familiar with a sane way to update while rooted, preferably without trashing userdata?

When I unlocked the bootloader I was given the impression unlocking the would disable OTA updates and that there is no way to re-lock so I pulled the zip with LMSA. The few discussions I've seen on older Lenovo tablets suggest if the system partition is untouched (which it should be with this root method?) you can simply restore the original boot.img and update.

I wish they published the changelogs somewhere so I could just see if there was anything substantial fixed like the previous build fixing things like netflix when reader/color modes were used. I almost wonder if I should just switch to a GSI of lineage or similar, though I suspect I'd lose more than I'd gain and... it could wind up being an epic multi-day trainwreck too.
[Thinkpad Tablet General] zippy411:
You can relock the bootloader. IT WILL WIPE ALL DATA AGAIN!

I gave root instructions here; https://xdaforums.com/t/lenovo-m10-plus-3rd-gen-root-guide-tb125fu.4524945/

To unroot you just reverse a couple steps.

Put the original boot.img (Make sure it is the boot.img of the same version ROM) in the Minimal ADB and Fastboot Tools folder on your computer

Navigate to this folder, right click and launch a Command Prompt

Plug in the tablet to your computer

Type “adb reboot bootloader” this should reboot your tablet into fastboot

When the tablet reboots into fastboot type “fastboot flash boot boot.img”

When you see the transfer is complete type “fastboot flashing lock” read the instructions on screen which will tell you to press the volume up button (volume button closest to power button) to lock bootloader. Press the volume up button.

Type “fastboot reboot” which will restart the tablet
[Thinkpad Tablet General] GuyInDogSuit:
You can download the update and install, but don't reboot. Instead, go to Magisk, and do a direct install again, THEN reboot. Though sometimes you are required to unroot before even installing/downloading the update, but that's rare. This will ensure you retain root after updating, without wiping your data. Hopefully I got to this in time.
[Thinkpad Tablet General] joeblowma:
You did! Thanks!

I've been ignoring the update notifications for at least a couple weeks now, which was a nice surprise considering all the warnings when I rooted said OTA wasn't going to be an option. It's telling me the update is far smaller than a full system flash (76MB) but I was concerned the magisk patched bootloader would either block install or get wiped so I keep putting it off.

Having set up this tablet 3 times since I got it, I wasn't looking forward to doing it yet again. Plus when I first went to root it there was a pending update that hadn't been issued to me via OTA yet, so I tried to update with the recovery flash tool thing which did have the latest version and it just... wouldn't, it'd connect for about 2 seconds then I'd get the usb exit sound from windows. Little faith at this point that tool would help if there were boot issues.
[Thinkpad Tablet General] GuyInDogSuit:
Glad to hear I did.

I can't even get the tool to recognize mine, so I've put off rooting or even unlocking the bootloader. So I am also wary of doing any modifications. Sigh.

It says to enable USB debugging, and to "always allow," both which I've done, but no change, there. It's fair to say that their recovery tool is at least a bit faulty, it seems.
[Thinkpad Tablet General] zippy411:
I've had the issue of my device not being recognized before if using an inferior aftermarket usb cable. This may not be your issue but it might be worth trying a couple different cables or usb ports.
[Thinkpad Tablet General] GuyInDogSuit:
I have quite a few, but have only tried maybe two, as that had crossed my mind. I might need the specific one that came with the tablet, if that IS the case.
[Thinkpad Tablet General] joeblowma:
Tried multiple USB ports (my PC has USB3 on a separate onboard controller, so tried both controllers), front and back of the machine "Just In Case", the bundled USB cable (which I've used to do file transfers multiple times with no issue since) as well as the only other A to C I had around. Never changed what was going on. It does recognize it for me, it just drops connection any time it tries to do anything other than that.
[Thinkpad Tablet General] GuyInDogSuit:
Welp, something odd happened after not using the Tab for a couple days, and the next time I picked it up, it had booted into recovery. I was able to reboot it into Android, but it would always inevitably reboot, and go to recovery, after a random amount of time (usually less than 2 mins). So I tried recovering it with the tool (which actually recognized it) but apparently it failed or something, because now it only boots to fastboot. I CAN get into recovery, but it says "last installation failed, rebooting now might fail" or some such. I've tried multiple times to "recover" but it never seems to work. Any ideas?
[Thinkpad Tablet General] GuyInDogSuit:
Great.... now it won't turn on anymore. :c
[Thinkpad Tablet General] HansDampfi:
Hello Everybody

my first post.

I have a understanding Problem. I use the guide from Zippy411. At the Point of RSA Row load i have no idea what should i do.

My Firmware Version on Tablet

TB125FU_S000118_220927_ROW

The Download

TB125FU_S000139_221208_ROW

in the guide it says that, it is necessary the download version of boot.img is the same as on the Tablet yet.

i cant find the 220927 at the internet. Is it save to do that:

Recover to

TB125FU_S000139_221208_ROW

Restart

Load

TB125FU_S000139_221208_ROW

again and extrakt the boot.img

Magisk

Have Fun!?

or

Has some one else the boot.img from

TB125FU_S000118_220927_ROW?

THX

Greetings
[Thinkpad Tablet General] aboulafia1901:
Hello ,

Normally ,if you update your tablet ,you receive directly the last update (then 221208) but you may update with RSA .
[Thinkpad Tablet General] HansDampfi:
ok thanks

i update first and than, i catch the boot.img again.

is ist possible to root the device with the actually version? has some one else test that?
[Thinkpad Tablet General] joeblowma:
Didn't work unfortunately, gets to "optimizing apps" in the updater (clearly it didn't even get that far) and fails/resets the update screen without telling me any reason.

It's an incremental update and not able to apply the delta, looking at logcat I'm seeing

01-25 09:47:40.764 1155 1155 E update_engine: [ERROR:partition_writer.cc(608)] Unable to open ECC source partition boot, file /dev/block/platform/bootdevice/by-name/boot_a: No such file or directory (2)
01-25 09:47:40.768 1155 1155 E update_engine: [ERROR:delta_performer.cc(883)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
01-25 09:47:40.773 1155 1155 E update_engine: [ERROR:delta_performer.cc(888)] Expected: sha256|hex = A1630EFBAD35D30DB89BCC940E010F567DD212E244869ABDAAEE1B3DBD721BB6
01-25 09:47:40.777 1155 1155 E update_engine: [ERROR:delta_performer.cc(891)] Calculated: sha256|hex = CEC9B0A50F760A997089B474AD49457806BEC986F03D878A6BAD7B25DB007073
01-25 09:47:40.782 1155 1155 E update_engine: [ERROR:delta_performer.cc(902)] Operation source (offset:size) in blocks: 0:2452
01-25 09:47:40.786 1155 1155 E update_engine: [ERROR:partition_writer.cc(513)] source_fd != nullptr failed.
01-25 09:47:40.790 1155 1155 E update_engine: [ERROR:delta_performer.cc(969)] partition_writer_->PerformPuffDiffOperation( operation, error, buffer_.data(), buffer_.size()) failed.
01-25 09:47:40.794 1155 1155 E update_engine: [ERROR:delta_performer.cc(201)] Failed to perform PUFFDIFF operation 0, which is the operation 0 in partition "boot"
01-25 09:47:40.798 1155 1155 E update_engine: [ERROR:download_action.cc(222)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
01-25 09:47:40.806 1155 1155 I update_engine: [INFO:delta_performer.cc(217)] Discarding 2195441 unused downloaded bytes
01-25 09:47:40.854 1155 1155 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.

So presumably it's trying to patch slot A into slot B with a delta patch and the boot partition doesn't have the correct hash for the patch. I'm not actually sure which bootloader should be on there, or how to get it in place so I can "restore" it via magisk but I have a few leads in other threads here on that to try.

D'OH! Did you try taking it for dinner, getting it flowers and say nice things to it? I hear that works... on TV anyway. Hope it's not a hardware failure and you can use one of the flashing tools to resurrect it.
[Thinkpad Tablet General] HansDampfi:
If I understand correctly, you have the same problem as me. The version in the rescue program is higher than that in the tablet. You have performed the update and now nothing works. This sucks for me. I hope there is some solution and someone can help. I don't want to run my tablet unrooted.
[Thinkpad Tablet General] joeblowma:
Sort of, I guess. Basically I installed magisk via flashing a pre-patched boot image and thus had no backup of what was initially in the flash. Apparently, what I have isn't what it expects and thus it won't install the update at all. It's still working fine though, I just keep getting an update notification and can't update.

I guess my understanding now is I should have used fastboot to boot the patched image instead of flash it (no idea if that would have worked, but it seems right) and then used that booted root to patch the flash via magisk installer direct patch which would have retained the original data.

I tried using LMSA to recover it to the version it gives me access to, and it connects then nearly immediately drops the connection. Looking into the files, I see C:\ProgramData\SP_FT_Logs\SP_FT_Dump_01-27-2023-05-43-59\QT_FLASH_TOOL.log has this:

01/27/2023 05:44:18.377 FlashTool[11744][3308][D]: ConsoleMode::ConsoleModeEntry::Run(): Exception: err_code[8502], err_msg[PMT changed for the ROM; it must be downloaded.
Please select "Format All + Download" scene and try again](..\..\flashtool\ConsoleMode\ConsoleModeEntry.cpp,205)

Which seems to be a serious bug on lenovo's part - the update that we download to recover doesn't have the same scatter/flash map as what ships on the tablet and thus will never be able to recover this tablet with their own recovery tool.

Not sure what to do at this point. I know how to get around this with SP_Flash_Tool_v5.2136_Win (though given the above lenovo issue how can I really even trust this firmware package?), but it won't fix lenovo's issue because this is still the same problem I had when it was still locked and stock, as well the version I had at that time was also with the same scatter as the current version.
[Thinkpad Tablet General] GuyInDogSuit:
NEVER flash the patched boot.img directly, boot it instead. I learned that the hard way. Though in my case it wasn't this tablet but rather another device from a while back. Thankfully I still kept the original boot.img (and payload) and was able to fix that.

Is your device bricked? Sounds like you have the same problem I do, that the tool isn't working on recovering your tablet either? Mine kept rebooting from Android into recovery, so I tried to recover it, and it failed spectacularly. Meaning it doesn't do anything but boot into fastboot, every time, after every recovery attempt. I mean, what good is a RECOVERY TOOL, if it fails at that, amirite?
[Thinkpad Tablet General] joeblowma:
Yeah, too bad absolutely none of the info I was following even mentioned that.

Not bricked, still working fine just unable to update. I could (likely, and maybe you too) use the mfg tool to format the partitions (except boot) and write the image, all from powered off (these tools expect the machine to be off then connect usb and it takes it from there) and then flash the most current firmware, but as I said it does not fix the problem normal lenovo customers will have - that they issue an updated image for recover with resized partitions or an incorrect scatter file (my guess is the scatter, though the logcat did mention partition resizes when parsing the diff descriptor) that their own tool is unable to use.

The recovery tool failed to work when I wanted to update it from TB125FU_S000090_220805_ROW to TB125FU_S000118_220927_ROW (aka: on a fully functional and not yet unlocked tablet) before the OTA was issued (took 2 more weeks after I tried) and the same error appeared in the mtk tool's log (their RSA uses mtk's tool in the background, delivered as an password encrypted compressed file that is extracted on demand and wiped after).

I fed boot.img from TB125FU_S000118_220927_ROW to magisk to get a patched image, and then flashed that to root (followed multiple sets of instructions, had problems with the flash command, never saw any boot command).
[Thinkpad Tablet General] GuyInDogSuit:
Oof. Good thing you weren't stuck with a bootloop or otherwise paperweight device.

Could you explain more in detail what this mfg tool process would be? It might be the only thing I can do at this point to save this oversized, flat brick.

--snipped--

I was able to grab that mtk tool, after it was extracted but before wiped, but I've no clue how to use it.