yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] Tiveric:
Android 9.0

Magisk 20.4

It was not successful for my tab in first few times even though I remember that I re-installed Magisk after "fastboot flash boot magisk_patched.img".

I didn't really know what to do next, almost give up but in a last try on next few days, it worked.

You should try re-installing Magisk on a beautiful day, pray for it work, good luck :)
[Android Q&A, Help & Troubleshooting] darkfortedx:
I found the solution

---------- Post added at 02:27 AM ---------- Previous post was at 02:25 AM ----------

I found the solution i think, make sure you dont have a memory card set up as internal storage (make sure its set up as portable) Magisk manager was basically installed on my SD card which caused weird things. But as soon as SD card was set as portable violaaa it worked
[Android Q&A, Help & Troubleshooting] havlaz:
sorry for jumping in to the discussion

me too have the tab m8 fhd (2nd gen) and it came only in chainse and not google play.

the store send me a link :

https://drive.google.com/file/d/1RkipnSN4bgsERBzRCHx7DfAad3np_ac2/edit

and with SP_Flash_Tool i flashed and got nice multilanguage and google play.

now i wanted to root the tablet, find your topic here, use the boot.img from the firmware i flashed , did the modded boot img

in android adb devices works, gives me the device number, but in fastboot its not. not writing waiting for device , just jumps to new line.

i understand its a drivers issue.. but my question is -

1) does the bootloader is pre unlocked ? of i need to do something first ?

2) since i flash with SP_Flash_Tool , can i do the same and just replace the boot.img with original, the mark only it and execute ?
[Android Q&A, Help & Troubleshooting] Isrgish:
If you want to use fastboot you will need to unlock the bootloader.

While you device is in fastboot go to device manager and see if there is an item that has a yellow mark on named something like lenovo tTb... Right click on it and update the driver to the adb driver.

AFAIK This should work.
[Android Q&A, Help & Troubleshooting] Carbonskin:
Hi guys,

I received my M8 last week and wanted to root it.

I have followed the instructions for rooting so far and until then everything has worked.

Unfortunately the tablet stays in the status "waiting for device" and I can't get any further here.

The driver is also installed in the device manager. (Win10/2004)

Does anyone here know of any advice or can provide the correct drivers?

Thank you in advance ;)
[Android Q&A, Help & Troubleshooting] gibby_:
So for those who haven't been tinkering in a while, I was driving myself nuts trying to get root on this device...turns out I was using the old bootloader unlock code of "fastboot oem unlock" This device needs "fastboot flashing unlock" Hopefully this saves someone else the frustration I went through! Once you get the bootloader unlocked it's as easy as patching the flashed boot.img file.
[Android Q&A, Help & Troubleshooting] konchog uma:
success on round 2 (after one boot loop soft brick, and flashing the whole firmware, then doing again)

1. click on build number in settings> system 7 times to open dev settings

2. tick OEM unlock & USB debugging in developer settings

3. plug in and get recognized (whatever you have to do wtih your drivers.. i use linux so not sure on all that) with "fastboot devices"

4. "fastboot flashing unlock" and follow prompts

5. after bootloader reset, repeat steps 1 & 2 (minus OEM unlock which is perma-ticked)

6. download latest firmware from lenovo Rescue adn Smart Assistant website, under rescue tab

7. move archive to appropriate folder for terminal work

8. copy boot.img to internal shared storage root, download, wherever you want it

9. install magisk manager

10. give magisk permissions to install

11. (i had to reboot by powering down and powering back up here)

12. using magisk manager app, install magisk and select patch file, patching boot.img

13. move newly generated magisk_patched.img to your computer in terminal-appropriate folder

14. "adb reboot bootloader"

15. "fastboot flash boot magisk_patched.img"

upon reboot, i had root access

however viper4linux (as magisk module) won't work so if anyone has thoughts on that i'd be grateful
[Android Q&A, Help & Troubleshooting] kriegschrei:
These steps worked for me! Thanks for spelling them out.

For step 7, I installed the Rescue and Smart Assistant Windows app (I couldn't find a website with the factory images). The app downloads the files to C:\ProgramData\LMSA\Download\RomFiles\<RomName>

After step 15 I had to do the following:

16. Launch Magisk Manager

17. Allow it to download a Magisk install file

18. Reboot (it booted to recovery automatically)

19. Press power to boot system
[Android Q&A, Help & Troubleshooting] cargodabard:
I must be missing something important that everyone else just knows here.

Where do all the steps below occur? Is there another program I am supposed to have installed and be running?
[Android Q&A, Help & Troubleshooting] konchog uma:
yeah cargodabard, look into installing android tools, (ADB and fastboot) for your operating system. i can't help most people on this one, cause i use only Linux operating systems, but you will need to install those (ADB and fastboot) and use them to interface with your device from your PC
[Android Q&A, Help & Troubleshooting] konchog uma:
Viper4Android working on tab m8 fhd

Nice mate... Yeah good to spell it all out clearly! :good:

---------- Post added at 06:47 AM ---------- Previous post was at 06:40 AM ----------

I got Viper4android working (yaaahh) now my audio is improved 500%

1. Install busybox pro (yes pay 2.5usd for pro or re-install on each reboot lol)

2. In play store turn off play protect

3. Install SELinux switcher app from apk, set to permissive

4. Install viper4android 2.7 from apk

5. Profit like a boss
[Android Q&A, Help & Troubleshooting] cargodabard:
I am stuck because ADB and Fastboot do not see the device.

Windows 10 Device Manager shows the Driver loaded correctly. I was able to get the magisk_patched.img created and transferred without issues.

OEM Unlock and USB debugging enabled, tablet started in Fastboot mode.

I can use the current USB cable to access the tablet and transfer data when not in Fastboot mode so it should be good.

If anyone running Windows has some clues for me, I would much appreciate it.
[Android Q&A, Help & Troubleshooting] Isrgish:
What do you see in the device manager? Can you show a pic?
[Android Q&A, Help & Troubleshooting] cargodabard:
it shows up as a "Android ADB Interface" in Device Manager, but when I type in "fastboot devices" it doesn't detect any and if I try any of the ADB or Fastboot commands it says waiting for device.
[Android Q&A, Help & Troubleshooting] Isrgish:
Did you run "adb reboot bootloader"? Does the the device show in device manager after this?
[Android Q&A, Help & Troubleshooting] cargodabard:
adb reboot bootloader = waiting for device.
[Android Q&A, Help & Troubleshooting] Isrgish:
What does adb devices return?
[Android Q&A, Help & Troubleshooting] cargodabard:
ADB devices does not detect any devices.

Windows Device Manager shows the driver is loaded and functioning correctly. Just nothing from ADB devices or Fastboot devices.
[Android Q&A, Help & Troubleshooting] Isrgish:
Did you enable USB Debugging and then granted authorization?
[Android Q&A, Help & Troubleshooting] cargodabard:
So if I plug it in without putting the Tablet in fastboot mode, ADB sees it just fine.

adb reboot bootloader rebooted the tablet into fastboot

The only thing it shows on the screen is very small down at the bottom: => FASTBOOT mode...

But now neither ADB or Fastboot can see it.
[Android Q&A, Help & Troubleshooting] Isrgish:
Once your in fastboot mode go to device manager and see if your device is listed there.
[Android Q&A, Help & Troubleshooting] konchog uma:
With the tabby in Fastboot mode, what does "fastboot devices" return?

In regular mode, adb devices detects connected devices. In Fastboot mode, fastboot devices is the command to recognize. Afaik if adb reboot bootloader is successful, and you're devices reboots in Fastboot mode, you should be good. But that's just afaik and I haven't used windows in years so maybe I'm missing something. Hopefully we can get you rooted. It took me a few tries but it's def possible lol
[Android Q&A, Help & Troubleshooting] Isrgish:
Very often after rebooting to fastboot (the bootloader) the device isn't recognized on it's own and you need to manually select the drivers.
[Android Q&A, Help & Troubleshooting] konchog uma:
Oh thanks mate... Because android is written in Linux it's so much easier for Linux users to do this stuff than win users. That's good to know, and I'm glad you're here to help
[Android Q&A, Help & Troubleshooting] cargodabard:
After it boots to fastboot mode it shows up in device manager as Android ADB Interface.

I will try tomorrow again to reload the drivers wile connected in fastboot. Pretty sure I did that today while trying different driver downloads but I will try it again.

If I remember correctly the Lenovo Rescue software gave the option to unlock the bootloader so I will reinstall that and try not to goof it up again.
[Android Q&A, Help & Troubleshooting] cargodabard:
Aha!

Turns out the latest version of Fastboot does not like this tablet for some reason.

I noticed that the Rescue software had ADB and Fastboot in it's install directory so I copied it out to an easier place to access and tried it. I had to unplug and replug the tablet in while it was in fastboot mode but as soon as I did that, it found the device and allowed me to flash the updated image.

Rebooting now to verify root.
[Android Q&A, Help & Troubleshooting] Isrgish:
Did you enable USB debugging in settings? This isn't something that Lenovo Rescue Software can do.
[Android Q&A, Help & Troubleshooting] cargodabard:
Yes. When I first started this process.

---------- Post added at 10:46 AM ---------- Previous post was at 10:14 AM ----------

OK now after rebooting a few times to verify, it boots in an Orange State and waits 5 seconds before loading into Android.

However Root Checker Basic says "No Root"

I flashed it again just to make sure, but still no luck.

From here I guess I will just start over from scratch and see if there is something I missed.
[Android Q&A, Help & Troubleshooting] cargodabard:
Finally got it to root after starting from scratch again.

The Steps below are what worked for me using Windows 10.

Note: using the latest ADB/Fastboot was the cause of all of my problems since fastboot refused to detect my device. I had to use the ADB and fastboot that came with the Rescue program and everything went easy after that.

1. Download and Install Lenovo Rescue and Smart Assistant

2. Tap on build number in Settings>System 7 times to enable Developer Mode

3. Settings>System>Developer Options - tick OEM unlock & USB debugging in developer settings

4. Connect Tablet to Computer

5. Download latest firmware from Lenovo Rescue and Smart Assistant using the Rescue tab.

6. Access CMD or Powershell from C:\Program Files (x86)\Rescue and Smart Assistant. (This is so that it uses the ADB and Fastboot that comes with the Rescue program. Downloading and using the latest ADB/Fastboot refused to find the device)

7. In powershell type: "adb reboot bootloader" This will reboot the tablet into fastboot mode.

8. Type in "fastboot devices" and verify a device shows up. If it doesn't, you will have to fiddle until it does. (I had to disconnect and reconnect while the tablet was in Fastboot mode for it to recognize the first time.)

9. Type in "fastboot flashing unlock" and follow prompts on the tablet (Vol+ for mine)

10. Reboot tablet into Android

10. Copy boot.img out of the firmware zip file downloaded previously and transfer it to the downloads folder on the tablet

11. Download and Install the Magisk Manager APK onto the tablet (it's not in the Play Store)

12. Open Magisk Manager on the tablet, Allow it permissions.

13. Power down and back up into Android

14. Open Magisk Manager on the tablet

15. Install Magisk from within the Magisk Manager App, and select the boot.img in your downloads folder. Allow it permissions.

16. Move newly generated magisk_patched.img to your computer in terminal-appropriate folder (I used the C:\ to keep it simple)

17. Access CMD or Powershell from C:\Program Files (x86)\Rescue and Smart Assistant. (This is so that it uses the ADB and Fastboot that comes with the Rescue program. Downloading and using the latest ADB/Fastboot refused to find the device)

18. In powershell type: "adb reboot bootloader" This will reboot the tablet into fastboot mode.

19. Type in "fastboot devices" and verify a device shows up.

20. Type in "fastboot flash boot C:\magisk_patched.img" (If you put the file in C:\) Took 6.4 seconds on mine.

21. Unplug and Reboot Tablet. It should say Orange Status as it boots and pause for 5 seconds before booting into Android.

22. Check for root. (I used Root Checker from the Play Store)
[Android Q&A, Help & Troubleshooting] Qsnail:
Change from Chinese version to international

I have a Chinese version too. Your link is dead. Can you please share it again?
[Android Q&A, Help & Troubleshooting] Isrgish:
For the new Update for this tablet that is Android 10. See This post on Android Enthusiasts for how to root.
[Android Q&A, Help & Troubleshooting] Heyyitsray:
I'm still stuck on step 8 of fiddling until I can discover the device. After getting it to boot in fastboot, it can't find the device. I opened powershell in the Rescue folder and still nothing. I see device manager as an unknown android device with no drivers. I tried different usb ports. What else should I do?

Thanks for any assistance :)
[Android Q&A, Help & Troubleshooting] Isrgish:
Go to Device Manager and right click on the unknown item select Browse My computer for Drivers... Then select Let me pick from a list ... Untick the box Show compatible hardware. In manufacturer select Google (or any other that has the USB drivers e.g. Microsoft). On Model select adb Interface\fastboot interface (Or something similar you find in the list).
[Android Q&A, Help & Troubleshooting] Isrgish:
If you are interested in a ported TWRP for this device, please take a look Here.
[Android Q&A, Help & Troubleshooting] retro5:
I posted this in the other root thread, but thought someone here might want to read it. I was having problems with the device not being recognized in fastboot, but the Rescue does.

I've been unhappy with the android 10 update and hoped to fix some of the problems with root, but the above procedure didn't work.

After some searching, I found the original firmware and downloaded it. With Rescue installed, I let it download the new firmware. I renamed the download folder name and unzipped the old firmware into a folder with the same name as the new firmware.

I ran a rescue and it flashed android 9 back to my M8.

I enabled developers mode and turned off auto update.

It does see some updates to 9, so I will install them, but so far, so good.
[Android Q&A, Help & Troubleshooting] PaulPizz:
Lenovo Tab M8 [TB-8505F] stock firmware can be found

HERE
[Android Q&A, Help & Troubleshooting] retro5:
I found this version - TB-8505FS_S100165_200629_BMP

here - do you have any idea where it fits?

After my M8 got the S100145_2009010959_V5.140 update, the next one was for 10.
[Android Q&A, Help & Troubleshooting] GBAFan:
I hate to be that new guy asking for help, but I recently obtained a Tab 8 FHD and while I love the hardware, Android 10 is just awful on it for me. I saw the earlier post about using the renamed Android 9 firmware and LMSA to install 9 on the FHD, but after trying it unsuccessfully with the two different firmware files I found online I have had zero luck.

I have tried the TB-8705F_S100099_200706_BMP firmware from two different, possibly sketchy sites, since I could not find the official Lenovo release and all other options I could find were pay to DL. So does anyone happen to have a link to any of the Android 9 firmware files that's safe and complete? I know I'm probably asking a lot, but I really like the FHD and I would like to be able to use it properly, and not gimped by Android 10.
[Android Q&A, Help & Troubleshooting] audeo:
Have you looked at this site 8705f ? If you go back a level he also has firmware folders for the 8705N and 8705X. I used one from there with no problems.
[Android Q&A, Help & Troubleshooting] GBAFan:
Thanks so much for the link! I am trying the site, but it is telling me I have to upgrade my upgrade my download package even after selecting the smallest sized file they have uploaded, so that's probably not going to work out in the long run.
[Android Q&A, Help & Troubleshooting] leopard_fist:
You guys think xposed framework will ever be available for this tablet?
[Android Q&A, Help & Troubleshooting] Zero_Shadow:
Which Firmware would be for Android 9 for our device I admit I am confused by the naming convention Lenovo is using for our device. Is it based off the date or something else? I am also interested in downgrading to Android 9 from 10.
[Android Q&A, Help & Troubleshooting] HkQc:
So sad this tablet is not supported by the Room community, it has all the right specs.:oops:

I'm not an expert so is it because of the processor or something else?
[Android Q&A, Help & Troubleshooting] GBAFan:
I honestly have been going with anything dated before the current update/around Novemberish. Still no luck finding working firmware though.
[Android Q&A, Help & Troubleshooting] retro5:
There are 2 different devices being mentioned here, the 8505f, hardware code 6761 and the 8705, hardware code 6762, that have different hardware. But the naming convention is similar.

This was the version on my M8 8505 when I got it. The S100* is android 9.

TB-8505F_MT6761_HW61_S100102_

tb-8505FS-USR-S100145_2009010959 is the last update of 9 before 10 was released.

This is the current version it wants to update to. The S300* is android 10.

tb-8505FS-USR_S30025_
[Android Q&A, Help & Troubleshooting] foureight84:
Are there currently any custom roms for this device? I made the mistake of upgrading to android 10 and it's pretty slow even after factory reset. I've tried disabling a few stock lenovo packages via adb and it seems to help but still more sluggish than android 9.
[Android Q&A, Help & Troubleshooting] Zero_Shadow:
Are you using the Lenovo Rescue and Recover to be able to restore the Android 9 Firmware or using Fastboot commands? Are you getting an error when you attempt the downgrade?

Thanks for that clarification I am indeed using the 8705 model.
[Android Q&A, Help & Troubleshooting] GBAFan:
The rescue tool. It's odd because the process seemingly works fine up until I have to plug the tablet back in, once that happens it instantly goes to 100% completion, but with no visible changes to the device at all. I've used the tool successfully before to restore to the current Android 10 firmware, so I have no idea why it is not working with the firmware I grabbed from the two websites I found it on. Might just be bad firmware?
[Android Q&A, Help & Troubleshooting] retro5:
How big is the folder after you unzip into it? I have several versions and they are all over 3gb, with 24 or 25 files, the largest file is system.img at 2.9gb. Maybe you just got an update and not a full rom?? If you can find an older rom to install, it will get the updates one at a time until the 10 upgrade and you can chose when or if to install them.
[Android Q&A, Help & Troubleshooting] GBAFan:
The only file I have been able to find and download is TB-8705F_S100099_200706_BMP.zip which is 1.59Gb zipped up. I'm not sure if that's an update or the full rom, now that you mention that point. I've looked around and it seems like all the 8705f roms and updates are non-existent aside from paysites, and I would rather not pay to get something that Lenovo should have freely available for people who bought a Lenovo device.
[Android Q&A, Help & Troubleshooting] retro5:
Maybe if you ask in the other M8 thread someone will have a rom. lsrgish has an 8705 and has ported TWRP working with 10, but he might have a 9 rom.
[Android Q&A, Help & Troubleshooting] GBAFan:
Thanks for pointing me toward that thread, I'll ask there and see what happens!
[Android Q&A, Help & Troubleshooting] ricardordz20:
Hey! A little late! I appreciate the detailed guide. I followed all your steps but I am stuck on the Lenovo splash with the orange status. I know I can unbrick it with the device rescue, but I'm not sure why I can't get root acess. Everything works according to your guide except to the part where I have to flash the patched .img file. Would love some help! Thanks!!
[Android Q&A, Help & Troubleshooting] Zero_Shadow:
If you are rooting Android 10 check this post.
[Android Q&A, Help & Troubleshooting] retro5:
You didn't say which device you are trying to root or which android version, that helps us help you.

What's missing from the list is when you get the boot.img from the new rom, also get the vbmeta.img and put them in the same folder.

Also, after unlocking the bootloader #10, when you boot back into the os and go through setup, do a minimum setup, but reenable dev options and turn on usb debug and reinstall magisk.

Then starting with #19 in the list add the 'disable' cmd before flashing the patched img.

adb reboot bootloader

fastboot --disable-verification flash vbmeta D:\dnlds\vbmeta.img

fastboot flash boot D:\dnlds\magisk_patched.img
[Android Q&A, Help & Troubleshooting] ricardordz20:
Thanks, for the tips. I followed the steps and I manged to reboot it. When I use root checker, however it says "root access is not properly installed on this device."

Lenovo TB-8505FS

Android 10.
[Android Q&A, Help & Troubleshooting] retro5:
Did you go back into the Magisk Manager and install the Magisk app?
[Android Q&A, Help & Troubleshooting] m1xmstr:
SOLUTION -- Updated 01/05/2020

######################################################

Are you sick and tired of not having root access on your M8 FHD with Android 10!

Magisk Manager -> Gear Icon

Update Channel -> From Stable to Beta

Now you should be on 21.2 (as of Jan 5 2020).

Now patch the boot.img and the magisk_patched_RANDOM_Letters.img will be 32MB -- Previously I was getting a 10MB patched file!

Then adb reboot bootloader

fastboot devices #Verify your device

fastboot flash boot C:\PATH_TO\magisk_patched_BLAHBLAH.img

fastboot --disable-verification flash vbmeta C:\PATH_TO\vbmeta_disabled.img

fastboot flash boot C:\PATH_TO\magisk_patched_BLAHBLAH.img

fastboot reboot

Now go to Magisk Manager (Mine looked like a default apk icon now), and it will show that magisk is installed on the device, and a prompt will say it needs to install an additional zip or something to the fact.

The device will reboot after you say ok

NOW check for root, and "Bob's your Uncle" a toast appears asking if you want to grant root access.

FINALLY!

I used this mostly blank vbmeta_disable.img (found somewhere on this thread), not sure if a it is needed or if the regular vbmeta.img will work feel free to try either...

#M1XMSTR
[Android Q&A, Help & Troubleshooting] mamba76:
GOOGLE LAVASYNC ------------------------------------ OTG AND CHARGE ))
[Android Q&A, Help & Troubleshooting] jeno1957:
Unlocked Bootloader

According to some posts, when bootloader is unlocked

--tablet goes into Orange State

--waits for 5 sec

--displays message " bootloader unlocked"

Could somebody confirm that above are correct ?

Is this after "unlock" process only or at every boot all the time ?

If permanent, Is there a "fix" for these to have a "normal" looking boot ?

Can a bootloader re-locked by re-flasing original boot.img?

Thank You !