Database Users

TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Lenovo Tab 4 Plus with and without LTE and both 8 and 10 inch versions (TB-X704L/F, TB-8704X/F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Download
TWRP for TB-8704X/F (8 inch plus): AndroidFileHost
TWRP for TB-8704V (8 inch plus Verizon): AndroidFileHost (provided by @3m1k)
TWRP for TB-X704L/F (10.1 inch plus): AndroidFileHost
TWRP for TB-8504X/F (8 inch): AndroidFileHost (touch input may only work after connecting mouse)
TWRP for TB-X304L/F (10.1 inch): AndroidFileHost
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.3-0-<your-filename>.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Backup at least system and boot partitions. Choose "System Image" for the system partition backup. Keep this backup for OTA updates.
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Writable System Partition
Some mods and root apps require write access to the system partition. By default the system partition is read-only to prevent any modification. Please note that if your system partition is modified in any way it needs to be restored to its original state before a system update (OTA) can be applied.
@dywersant has created a Magisk module here to achieve write access
@KreAch3R has updated the Magisk module to the latest version here
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000037) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000037) for the update to succeed.
Credits
@wonderfulme - for testing the 8" version
@Teddy01 - for testing the 10" version
@3m1k - for providing the 8" Verizon version
TeamWin
Source
TWRP Manifest: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Device Tree (TB-8704X): https://github.com/Matshias/twrp_android_device_tb_8704x/tree/android-7.1
Device Tree (TB-8704V): https://github.com/3m1k/twrp_android_device_tb_8704v
Device Tree (TB-X704L): https://github.com/Matshias/twrp_android_device_tb_x704l/tree/android-7.1
Device Tree (TB-8504X): https://github.com/Matshias/twrp_android_device_tb_8504x/tree/android-7.1
Device Tree (TB-X304L): https://github.com/Matshias/twrp_android_device_tb_x304l/tree/android-7.1
Changelog
v3:
Update to TWRP 3.2.3-0
v2:
Update to TWRP 3.2.1-0
v1:
Initial Release

TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): no longer needed. Final version in first post

matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
I can test the 8 inch tomorrow. Thanks for building this btw.
---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\

w0rdie said:
Wait, these builds are for the Plus variants only? They will not work with ZA2B0009US, correct? :\
Click to expand...
Click to collapse
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.

matshias said:
ZA2B0009US = TB-8504F so you can take the build for Tab 4 8 (TB-8504X/F) and hopefully it will work out of the box.
Click to expand...
Click to collapse
Just landed there myself. I'll give it a go tomorrow morning and update this post.
Thanks again.

I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:

boza12 said:
I have tested on X304L work perfectly.
Only one thing when i'm on power via usb TWRP still turning off screen in 2min and seems that all operations are put in wait state until screen turned on again.
:good:
Click to expand...
Click to collapse
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?

matshias said:
Thanks a lot for testing. I moved the TWRP to the first post.
In the TWRP settings you can switch off whether the screen goes off or not. Are you sure TWRP halts processing while the screen is off?
Click to expand...
Click to collapse
Yes It does - it happened to me last night also.

EggZenBeanz said:
Yes It does - it happened to me last night also.
Click to expand...
Click to collapse
Can you send me the logs (dmesg output and /tmp/recovery.log) after it happens?

Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup

EggZenBeanz said:
Yes sure.
Is anyone able to make available a system image. I deleted my original back up after the update then messed the root up. I now getting setup app crash and can't get passed setup
Click to expand...
Click to collapse
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.

matshias said:
Download the factory image for your tablet from the Russian Lenovo forum (lenovo-forums.ru) . In there you will find a fragmented system image. You have to puzzle it together with a script according to XML file in the Image directory. If you wanna flash via fastboot you will have to convert it with img2simg to sparse format. You can also use dd command line TWRP with the raw image file. If you tell me your exact model number I can also upload what you need.
Click to expand...
Click to collapse
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?

EggZenBeanz said:
Thanks! That would be awesome if you could. I think I may brick it if I do what you suggest! My model is
TB-X704L/F (10.1 inch plus) could you include the boot image too?
Click to expand...
Click to collapse
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.

matshias said:
Is it TB-X704L vor F? This is an important difference.
The boot image you can find as can be flashed in the factory image. You can start with this. When I have time I'll prepare the system image. Not sure when that is though.
Click to expand...
Click to collapse
Thanks!!!! Confirmed TB-X704F

matshias said:
TWRP for Tab 4 8/10 without "Plus"
I built TWRP for both devices and need testers. Here are experimental versions:
Tab 4 8 (TB-8504X/F): twrp-3.1.1-0-tb_8504x_testing1.img
Tab 4 10 (TB-x304L/F): twrp-3.1.1-0-tb_x304l_testing1.img
Click to expand...
Click to collapse
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)

On my Tab4 8 the touch is also not working with this image.
I think the following lines from dmesg.log are showing, that the touch driver ist not loading:
<4>[ 1.323216] [HXTP] Himax common touch panel driver init
<4>[ 1.323221] [HXTP][ERROR] himax_common_init failed, compare_tp_id = 1

w0rdie said:
The twrp-3.1.1-0-tb_8504x_testing1.img flashes and boots fine but there is no touch input.
Logs: https://www.dropbox.com/s/vo2dvi4frpsf9hf/logs.zip?dl=0
(I connected a mouse via USB and got SU flashed)
Click to expand...
Click to collapse
Do you have the TB-8504X or TB-8504F? Very strange that the touch driver won't load. if you have the F variant then maybe it has a slightly different hardware in which case I'll have to compile separate TWRP for this variant. Can you extract me your stock boot or recovery image and send it to me? I'd then build TWRP with the kernel from your tablet and we'll see what happens

EggZenBeanz said:
Thanks!!!! Confirmed TB-X704F
Click to expand...
Click to collapse
Here is the system image in sparse format for fastboot flashing: MEGA

matshias said:
Here is the system image in sparse format for fastboot flashing: MEGA
Click to expand...
Click to collapse
Amazing, thank you so much. All worked and back to normal. I'll root again with the screen off and provide logs

Sorry if this is off topic, but is there a way to convert the Chinese versions of the Tab 4 / Plus to the Global rom? I'm thinking of getting one from China when I'm there but the lack of Google Play support is a major deal breaker.

Why no root yet ?

First off I am not criticizing the amazing XDA developers here, and all the people that help make root and ROM's happen.
This is aimed at Essential the company themselves
I was under the impression the Essential Phone was sort of like a Pixel, or Nexus, or OnePlus type of phone. Meaning running a near stock Android OS, an unlocked device, easily rooted. For example when a new OnePlus phone is released, root is out super fast. But the reason the Essential Phone has not been rooted yet is because of Essential holding back the factory images on us still. I guess I have to ask why would Essential do this ? I thought they touted this phone as a open platform, very similar in idea to the old Nexus line ?
The Essential Phone has been out 2 months now, and the important files for rooting still have not been officially released to the public yet ? What's up with Essential holding back so long ?

https://ibb.co/mgaVcb Mine ist rooted

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Last I read was the boot image that was pulled didn't enable root with magisk and hadn't seen anything more from it. Did you have to do anything specifically?

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Interedasting.
It'd be great if you could provide further proof/instructions.
Thanks a bunch.

There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either.
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
*Found the thread here:
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583

kchino said:
There was a thread about someone working on LOS earlier this week but now I don't see it. Can't remember the user's name but he said that he had TWRP (no touchscreen though) working on the ROM, and posted some screenies of it booted and invited anyone who wanted to develop to his Discord. The same person was over on the /essential thread too on reddit too but now I don't see that thread either. Maybe it was a Larp ¯\_(ツ)_/¯
The Essential staff did an AMA over there yesterday too but noone asked about releasing the source code to my knowledge. I'm not sure what's going on. They'd sell more phones if people knew they are ROM friendly.
Click to expand...
Click to collapse
Pretty sure the staff that did the AMA was just the design staff, not software staff. As soon as the files are released it will take about a day I bet for root. I remember seeing a thread on reddit that you are referring to as well. I think the people who can root it won't until the files are released. One **** up and they have a very expensive brick.

Thanks for the replies. So any idea as to when this source code image files will get released from Essential ? What's their holdup ?

Agreed, dicey proposition with no factory images.

We have devs working on it. Root has been achieved and there's a TWRP build but the touchscreen doesn't work you have to use a mouse to navigate. Also, there's no factory images yet to go back to stock in case of a problem. Once they iron out the issues I'm sure someone will release a guide.

Currently on the Nexus 6P, that's getting bad. I really want the Essential phone, but only if root comes out for sure, also ROM's would be great.
Otherwise I may just wait for the OnePlus 5T announcement, and if it's $500 go that route instead. At least the 5T will have good development

Z-Fire821 said:
https://ibb.co/mgaVcb Mine ist rooted
Click to expand...
Click to collapse
Man how did u root?? I really wanna root

I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."

Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Can you provide the file for TWRP and boot img?

drocny87 said:
Can you provide the file for TWRP and boot img?
Click to expand...
Click to collapse
Just join the Discord Server and load it from there.

Z-Fire821 said:
I rooted with this Guide from the Discord Server from bmg1001: "In order to flash Magisk, you'll need the Magisk zip, TWRP, the stock boot image, and A USB OTG MOUSE (used to control TWRP for the moment). Boot into the stock recovery and perform a factory reset, then reboot into the bootloader. You need to flash TWRP via "fastboot flash boot twrp-mata.img". Once flashed, you need to boot into TWRP via the bootloader menu. When you boot into TWRP, move the Magisk zip and stock boot image into the phone's storage. Then, flash the boot image within TWRP, then flash Magisk."
Click to expand...
Click to collapse
Thanks
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
Z-Fire821 said:
Just join the Discord Server and load it from there.
Click to expand...
Click to collapse
What's the link to it?

ROOT
Guys, if you truly, truly want to root your device, follow these steps. Just remember, I am not responsible if you end up bricking your device (and neither are the main developers currently working on TWRP and Lineage). YOU ARE RESPONSIBLE FOR WHAT YOU DO ON YOUR OWN DEVICE! (also this probably voids warranty btw)
THESE INSTRUCTIONS ARE FOR NMJ20D.
Now, one more thing. Remember, this TWRP build is very much in alpha stages and there are some major bugs with it, including no touch support and no crypto. Also, when I rooted, I had to use my USB OTG Mouse in order to maneuver around TWRP, but with this method, hopefully anyone can do it, without the mouse. The boot.img I will provide is the NMJ20D boot.img with the patches that Magisk puts in when you install it, so it's not exactly stock. Also, you might need to factory reset your device via the stock recovery (and make sure not to boot it back up until after you flash Magisk) just in case, since TWRP is buggy with crypto atm.
You can find a dump of NMJ20D here, in case you need to fix a bootloop (due to a bad Substratum theme, etc...) -- (you'll likely need only boot_a.img and system_a.img (within the system_a.zip).
If you wish to return to stock in order to accept OTAs, feel free to flash the unofficial factory images here and, should OTAs still fail, you may be required to wipe your data, which can be done via "fastboot -w". (Side Note: I believe the script included within the unofficial factory images also flashes the firmware to both partitions, so if your fingerprint sensor is seemingly absent or not working, this might actually fix it, as it has for some custom ROMs on the Essential.
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course, your bootloader must be unlocked.
1. Reboot your Essential into fastboot mode. Once in fastboot mode, flash TWRP via
Code:
fastboot flash boot twrp-mata.img
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type
Code:
adb shell twrp sideload
and then
Code:
adb sideload magisk.zip
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
Code:
fastboot flash boot boot_a.img
4. Now reboot! You should now have root and stuff via Magisk!

Appreciate the root guide, guess I can pick one of these up now to play around with. Awesome!!

[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk![/QUOTE]
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..

shooterlgk said:
[
Anyways, lets get started!
Make sure to download Magisk v14.3 and the alpha build of TWRP. Also, make sure to grab my boot.img with the Magisk stuff in it. And of course,
2. Then, from within the fastboot menu, go to "recovery mode" and select it. After TWRP has booted up, type and then
3. Once Magisk finishes installing completely, reboot back to fastboot. Now that you're back in fastboot, flash the boot.img I provided via the good ol' command
4. Now reboot! You should now have root and stuff via Magisk!
Click to expand...
Click to collapse
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..[/QUOTE]
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?

bmg1001 said:
I followed the whole guide, got to the side loading, and I couldn't get magisk to side load..
Click to expand...
Click to collapse
What happens when you attempt to sideload Magisk? Does the adb sideload prompt on TWRP pop-up correctly after running "adb shell twrp sideload"?[/QUOTE]
I should of took a picture cuz I can't remember but it does give me an error tho ..I'm gonna retry when I get home from work but I literally sat there for almost 3 hours attempting to root to no success

Need backup img for tb-x304f

Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:

AlmogEd said:
Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:
Click to expand...
Click to collapse
They don't have images like Google devices, but flashable firmwares.
http://lenovo-forums.ru/files/category/287-lenovo-tab4-a10-tb4-x304l/ has it, second from the bottom, underneath all the OTAs. Double check that you got the 4F and not the 4L one.
I don't have this device so I cannot help you with it if you have issues, nor can I say this will work for you. I also really don't profess to be any kind of an expert so do ask in one of the other Tab 4 threads if needed... but I do have the TB-8704F & have restored it to stock several times and I would assume the devices to be identical in process so I can give you a guide if needed! The general path is:
Download the zip and extract it
Download and install Xiaomi Mi Flash (some say to use QFIL but it often throws up errors and sometimes requires flashing in multiple passes, when Mi Flash doesn't)
Plug your device into your PC
Put your device into Emergency Download Mode, easiest way for you is probably to first reboot to TWRP which you luckily already have installed
In TWRP go to Advanced>Terminal>type Reboot EDL
Open Mi Flash and it should see your device. Click Select, open the images directory in your extracted firmware and it should detect the flashing process XML
Click Flash, then leave everything to complete
I will warn you that you will lose everything on your device. There's no way around this that I know of, nor would I suggest it anyway. Just back up everything before doing the restore.
+ Good luck! But honestly I'd first weigh up whether you really want to update to 8.1 since you're already on a perfectly-working device. They already pushed the OTA once and had to retract it because of the amount of serious errors it had - but that's your call entirely.

AlmogEd said:
Hi I have tb-x304f.
I installed TWRP to get root access and by mistake I deleted my backup and now I can't update to 8.1.
So can someone give me backup img?
Thanks :good:
Click to expand...
Click to collapse
bro help me unlocked the bootloader yesterday and flashed recovery but then decided to downgrade the system with system sparse image in fastboot mode provided by o.p. of rooting thread, but now it is not booting up just showing lenovo logo and in fastboot mode again

[ROOT][TB-X505X] Rooting Lenovo Tab M10 TB-X505X

This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".​3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.​Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.​That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.

Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.

Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.

But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.

Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.

ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.

Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you

Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?

jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f

Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..

tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there

Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?

Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/

cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.

Thanks bro. I found what I needed..

Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?

Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.

Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......

How To Guide Development for the Cricket Dream 5G

For starters, there's no thread for this device and I wasn't sure where to put it.
Secondly, me and a friend have been tinkering around with the Cricket Dream 5G and have successfully unlocked the bootloader and obtained root access. Unlocking the bootloader was the easy part. Anyways we've made a full device backup before rooting. I have a magisk patched boot.img. Just unlock the bootloader, flash the patchedboot.img and install magisk. There you go, you have root
WARNING
DO NOT FLASH A MODIFIED SUPER.IMG IT WILL BRICK YOUR DEVICE You can, however modify your system, like removing or adding apps.
I bricked mine because I flashed a modified super img. It's stuck in preloader. Still learning this dynamic partition scheme, it's weird
Full backup on Google drive currently, gonna be moving to mega=>
https://mega.nz/folder/UARQCD6I#8CSNy43GWo6XjEKk_mlldw
Links below, all links are thru mega
Original boot=> https://mega.nz/file/JBAhHSTQ#Aw-GQQ6-StdNAhLsu0vdonNDXcBo4wXI8xEalQ99X2Y
Original boot is in bin format but magisk recognized it and patched it.
Patched boot.img=> https://mega.nz/file/hEJjlaxI#e2DdzvNkq1421uESaSQR4ZP_-CHvt6I_IDCEpyYDZqA
And an app for the magisk modules, not my work, only sharing=> https://mega.nz/file/VAQR0ARI#IUT42ycW5bbb8xVSDhDthREJzr1GEd5WHW0xZbkE8Ts
Also, relocking the bootloader after flashing the patched boot img, it will say there's no OS installed. It's still there. Just unlock it and it'll boot. Not sure why. I believe it's the secure boot being on
Just send a message on here if links are broken
If enough people are on this maybe we can get a working twrp
Update: twrp available here => https://forum.xda-developers.com/t/development-for-the-cricket-dream-5g.4414603/
If anyone uses gpay, unlocking the bootloader will break it. But I know a workaround if anyone wants it.
@Welkwo is behind the twrp process.
My post is just a guide, really.

Thank God! I have numerous phones but for some reason, I have my main number through a sim card thast's unfortunately tied into this phone.. I have been searching online for the stock firmware for this p;hone for a long time with no conclusive results, so upon my search for it this morning, I came acrfoss your post and I almost craped my pants. Thank God.. noot for the almost crapped pants, but for the efforts of you and your friend.. Thank you so much.

We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g

Is it not completely slow as **** to you?! It's nowhere near what my OnePlus 5T , Redmi Note 8 nor Motorola Ace One can do nor did I expect it to be but God damn it's just super slow to me..
By the way should I flash boot_a and boot_b in fastboot because when I did the first time when I booted back up it kept making Google framework stop responding

Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
Nevermind.. I retract m yprevious statement.. I just got root and I'm blown away at the sactual speed of this phone. It's such a night and day fgucking difference betweeen having root and not.

Sorry I've been absent. My work has me drained and I've bricked my dream 5g. I messed with my super partition and it is stuck in preloader.
Also I only flashed the boot for the current slot via fastboot

We need to create a scatter file, not quite sure how. Any help is appreciated

yooo... are you guys just needling the scatter to make a twrp recovery?

DrScrad said:
yooo... are you guys just needling the scatter to make a twrp recovery?
Click to expand...
Click to collapse
Honestly I'm not sure. My friend is behind the twrp process. We got one to boot but it don't recognize the partitions so it won't even boot to the os.
Do you have a scatter file? If so please share and I'll also attach it to the op if I have permission, lol

I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did

Josephdbrewer25 said:
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Click to expand...
Click to collapse
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com

lopestom said:
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah. Your point? That's the friend working on twrp

No TWRP file?

DragonPitbull said:
No TWRP file?
Click to expand...
Click to collapse
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com

Josephdbrewer25 said:
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Click to expand...
Click to collapse
I not need that. but anyone need permission access.
Josephdbrewer25 said:
Yeah. Your point? That's the friend working on twrp
Click to expand...
Click to collapse
Okay. But the DT in the github is your.
I need access of DT for help and if you or users need help about TWRP improvements. Looking my post about collaborator.....
UPD: I donwloaded your bot_a.bin (I need time for donwload super...img file) and I'm working with that to process informations & simple DT. I prefer collaborator than creating new DT in the github. But if I not receive any answer here so i go create new DT in the github and compiled TWRP file for anyone test.
The question now is: Who is the tester?
UPD1: super_backup_2022-03-10_02-34-47.img from MEGA is not good. 3 times trying donwloading file..... Can you put that as zip file in the GDrive?
UPD2: The super.img file was downloaded.
I need some informations from device. But at this point I'll write in the TWRP Cricket Dream 5G thread. .
If someone can put informations so answer in that thread.

Not sure if I should post here or at the TWRP thread but I think I've fixed the problem with being stuck at preloader after flashing modified super img. I got it to work by flashing the modified super img, locking bootloader and unlocking bootloader.
Can someone else also verify that this works?
Edit: Nvm I've been flashing the wrong super img

UPDATE: TWRP IS NOW AVAILABLE FOR THIS DEVICE.
See this post: https://forum.xda-developers.com/t/twrp-for-cricket-dream-5g.4418963/post-86858605

Kinda new to this, but I have a problem I am hoping someone knows about...I unlocked bootloader then i entered the fastboot flash command ...my phone died, as in shut off, power button does nothing, plugging it in to the computer does nothing, and charging does nothing. Thoughts? I'm assuming its dead? Thnx for listening lol
correction, i entered fastboot reboot fastboot

You know what? IT'S ALWAYS SOMETHIN'! I just got a Cricket Dream 5G for free (promo) and the bloody thing won't read a Micro SD card unless it's formatted to Fat32. Which means the largest card it'll use is a 32gb card. I mean WTH? I've never seen anything like this. If I put in a card formatted to exFat or NTFS it says it's corrupted. A Fat32 card is fine. Anyone else run across this? Just another X-File conspiracy against me.

so...no one knows anything??? anyway to fix this??? i noticed when plugged into computer it makes the connecting noise followed by disconnect noise a few minutes later, and button combos seem to change the timing of said noises but nothing shows up under adb or fastboot devices....help!!!!!