Database Users

[CLOSE THREAD PLEASE]Flash Modded ROM Through MI-Flash Tool!!

****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******
Use Android Image Kitchen to decompress and Recompress.
Unzip the whole Kitchen and ROM files through 7 Zip * mode.
Copy the "boot.img" to the Android Kitchen Unzipped Folder.
Follow the following steps:
Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)
Step 2. Open the file "fstab.qcom" via notepad / notepad++.
Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).
Step 4. Open default.prop via notepad / notepad++.
Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).
- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.adb.secure=0"
These enable OEM Unlock over Server and over Developer mode.
c. "ro.debuggable=0" to "ro.debuggable=1".
This turns on USB Debug.
d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"
This turns on ADB mode.
e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".
One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).
- Save the file. Do not change the file extension.
Step 7. Recompress these files back through repackimg.bat."
A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.
You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.
Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.
These steps take no more then 5-6 minutes, and are pretty easy.
Happy Flashing.
N.B.: I have attached the Android Kitchen File here.

Is this equivalent to unofficial unlock or the official one?

BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
Actually None. I mean not the official, nor the unofficial one.
I am on unlocked bootloader myself.
These are the steps I did to unlock my bootloader.
I have even rooted my RN3QC within 10 days from purchase.
I just wanted to unlock and have even custom TWRP 3.0.2-2.

can miflash just flash the boot.img?

meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
Nope, I tried, and it went to bootloop once and second time to mi logo.
The easiest way to install the boot.img and the recovery.img are:
If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.
Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done.
And if you want to flash boot.img, then flash through TWRP. That is the easiest method.
Safe and no bricks.
N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.

Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !

NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.

vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:

So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.

kraatus90 said:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
Click to expand...
Click to collapse
R3S it should not work, and as you confirmed it does not work.
Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.
They have changed the method to unlock on MM, so this apparently is only for LP.

vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.

abihary said:
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure

vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.

abihary said:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
Click to expand...
Click to collapse
Any day welcome.

For kenzo or hennessy?

zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo

zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.

What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.

MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.

vdbhb59 said:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
Click to expand...
Click to collapse
So you are back to a locked bootloader when you moved to 6.9.9?
And for doing that you just flashed the fastboot tgz file in edl mode?
Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?

[FIX][OP3/OP3T] DM-Verity warning fix. Works on 4.1.0!!

Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
1- Download the 4.0.2 firmware and the firmware of your current version:
OP3T files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5XzNCRVVwUVYzRms
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs[/URL]
Oxygen open beta 3:[url]https://drive.google.com/open?id=0Bzko1towAti5d3BtOEtXdk9hVTA[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5NzU5b3lDaEZfZ3M[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M[/URL]
OP3 files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5eXpXOXRUcXRoeXc
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WEtoYXd0NW1qUVk[/URL]
Oxygen open beta 12:[url]https://drive.google.com/open?id=0Bzko1towAti5aVVvNkIwTURjaE0[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP the firmware of your current OOS version.
And you are done! :highfive:

Migdilu said:
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
1- Download the two files:
[url]https://drive.google.com/open?id=0Bzko1towAti5Uld0cWp1YWdfLXM[/URL]
[url]https://drive.google.com/file/d/0Bzko1towAti5LXFUbEJwYUFFbGc/view?usp=sharing[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
Click to expand...
Click to collapse
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??

kunal1540 said:
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
Click to expand...
Click to collapse
Exactly, I'm uploading a new file correcting that. But don't worry, you flashed the 4.0.3 firmware. Thanks for the report!

Worked for me as well. Thank you.

thanks worked at my 1+3T.

working for me also on A3010.
thanks.

Please add
Code:
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");
as first line in your updater-script which prevents bricked devices.

Nice to see it's working!
sniperle said:
Please add
as first line in your updater-script which prevents bricked devices.
Click to expand...
Click to collapse
I'll check that later, thanks!

I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.

done it with 4.0.2 rooted and without succes

Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.

nitramcek said:
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
Click to expand...
Click to collapse
You did something wrong. Do you have 3 or 3t?

nitramcek said:
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
Click to expand...
Click to collapse
Its on oneplus 3t forum.. Can you boot to booloader?

madmax28011980 said:
done it with 4.0.2 rooted and without succes
Click to expand...
Click to collapse
Just do step 3 and 4 if you are on 4.0.2 or older. Now flash 4.0.2 firmware and then do 3 and 4 and you are done.

off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.

Migdilu said:
Its on oneplus 3t forum.. Can you boot to booloader?
Click to expand...
Click to collapse
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.

nitramcek said:
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
Click to expand...
Click to collapse
I'm sorry. Make a thread on oneplus 3 forum explaining that you accidentally flashed 3T firmware, maybe someone has a solution for this.
EDIT: Take a look at the unbrick guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

Snappiestjack said:
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Click to expand...
Click to collapse
Not sure what/if I've done wrong TBH... still, I had the message

I reflashed op3t recovery i then reflashed oxygen 4.0.2 but still getting the error then i flashed twrp 3. and then the su after that i have flashed your 4.0.2. Img and gave the fastboot commands still the error is there maybe i do something wrong! The weird is that when i enter twrp it asks me for a pattern... Should i remove security locks from oxygen 4.0.2 and try again! Anyway.. Goodnight for now.

It's worked!!!
thx a lot!!!

LineageOS 7.1 for SGP771

Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
Code:
su
echo 1 > /sys/module/qpnp_smbcharger_extension/parameters/start_id_polling
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
[STRIKE]https://www.androidfilehost.com/?fid=745425885120730219[/STRIKE]
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
------------
Some screenshots:

Oh. You need also replace wifi calibration file here: /system/etc/firmware/wlan/bcmdhd/bcmdhd.cal and reboot
It's forgotten to be added.
Updated fixed version at yandex disk.

Thanks for this. It is exactly what I am looking for and I hope my tech skills are up to the task.
BTW, this link comes up "404 not found. Can't find it!"
https://www.androidfilehost.com/?fid=745425885120730219
Would you have another we can try?

Thats because kv123 removed version with wifi buggy.
Use my mirror link or this.
https://www.androidfilehost.com/?fid=817550096634767960

alex009988 said:
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
https://www.androidfilehost.com/?fid=745425885120730219
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
Click to expand...
Click to collapse
Hi, could you please add some screenshots?

Ok. Added to the top.

need rom for SG712 please...

Thanks for sharing. SGP712 build would be great

Charsher47 said:
Thanks for sharing. SGP712 build would be great
Click to expand...
Click to collapse
Kv123 told me that he's gonna build the rom for 712 too.

I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.

kv123 said:
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
Click to expand...
Click to collapse
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...

Phil_Libra said:
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Click to expand...
Click to collapse
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.

alex009988 said:
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
Click to expand...
Click to collapse
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.

Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265

Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
Sorry if I have missed something obvious, but are you attempting to flash LineageOS? In which case I am confused as to why you are flashing the Sony Rom 32.A.2.33?
For my part I am gearing up to attempt the LineageOS install but would like to have a backup copy of the Sony firmware in case it goes wrong.
Assuming you installed an English version, which one did you select from here:-
https://xpericheck.com/device/SGP771

Indeed, if you try something especially unchecked, better to have a backup.
But you also need to have last sony rom(any of android 7.0) in order to update bootloader and have last twrp working.

alex009988 said:
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Click to expand...
Click to collapse
Androplus‘ recovery need a modified boot.img so I wonder if the same as the recovery in yandex disk?
And recovery from https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265 is the same as Androplus’ recovery.

Ok. If you've done everything right I guess 712 dosent work with 771 recovery. I'll tell about it to kv123 and you can say it on your own on 4pda.

Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.

Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
alex009988 said:
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Click to expand...
Click to collapse
I'm seeing the same results. Tried the same recoveries to no avail.

[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......

11.0.8.8 Rooting Issue

I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?

Remove oos native call recorder module if you have it, if not just remove all modules.

MrEvilPanda said:
I am on the latest 11.0.8.8 EU version. I had patched the boot.img using magisk 23 app, but when i try to flash the patched boot.img using adb fastboot, keep getting "com.android.phone" crashes. Need to flash stock boot.img to get the sim cards working. Any suggestion to get root ?
Click to expand...
Click to collapse
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..

dladz said:
Have you been on my guide mate?? It's all laid out for you..
Don't flash anything, you want to boot first as this is not permanent.
Stable 23 is the correct version..
Click to expand...
Click to collapse
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.

MrEvilPanda said:
I am on the stable 23 version. Disabling the native OOS call recording module solved the issue. @gsser Thanks mate.
Click to expand...
Click to collapse
Ah yes, always disable Magisk modules prior to upgrading firmware.
As they may not be compatible, this is also in the guide.
Glad you're up and running mate
Nice one

So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??

Arksuga said:
So idk if this is the correct place to post questions but i have a OnePlus 8 pro 11.0.8.8IN11BA, i want to root it, but i can't find the stock rom for this version. Can anyone help me??
Click to expand...
Click to collapse
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

galaxys said:
Hi, see this thread:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):

Arksuga said:
Thank you so much!!!! So now in order to root it i should unlock the bootloader, and then patch the IMG i downloaded with the magisk manager app, connect the phone to the PC with USB debugging on, reboot in fastboot mode, and type on the windows command thing this ( the commands in the image attached ):
Click to expand...
Click to collapse
Yep I've got guides for unlocking the bootloader and rooting in the guides sections.
Both called as such accordingly.
Tbh there are a few guides all should be fine.
Just read through the root guide.
Unlocking the bootloader it's easy.
Code: fastboot OEM unlock
Agree on phone.
Rooting:
Obtain patched image
Fastboot boot Magisk patched
Don't flash it, just wait for boot then open Magisk and click install / direct install.
Again this is all in the guides.