Database Users

Updating To MM from LP (Moto X Pure)

So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!

I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?

I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".

superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error

Is there no way to upgrade from LP to MM without a wipe?

superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?

Why would you want to update without a wipe? You must like sluggish performance

i have no wifi after this

No WIFI either
I ended up with no WIFI after following these steps also.

is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?

skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?

So the last three posts complain of no wifi yet people keep using this method?

The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.

ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.

lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps

Are you unlocked?

ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs

So is this safe or not?

lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment

BLOD 8.1.0 (OPM2.171019.029, Apr 2018) fix

[DEPRECATED] no longer working on due to real life issues. [DEPRECATED]
Please feel free to use my post and work on it yourselves, sorry.
Nexus 5x BLOD fix (OPM2.171019.029)​
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
​02/05/2018 - Updated method and added custom ROM method.
​01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
​3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
​4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
​6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
​6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
​11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
​11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
​13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.

Rooting info & Google pay fix
Rooting info & Google Pay fix​Flashing Magisk after ROM will allow you to have root privileges and will also allow you to use
Magisk: it's HERE

My phone has bootloader locked. Is it needed?

lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Unfortunately, it is required so that you can flash the images. If you can't turn the device on then try the steps linked below;
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Goto the "*If your phone is bootloader locked/OEM locked:" section, I had the same issue and freezing my phone for 15 mins worked great.
Might work for you to

could you please fix the link to the Modified Lineage OS ROM.
thank you

deoneR said:
could you please fix the link to the Modified Lineage OS ROM.
thank you
Click to expand...
Click to collapse
Fixed it sorry for the wait; was busy with college etc.

if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?

deoneR said:
if i do all your steps for the second method i always get a reboot to TWRP after ~ 3mins
what am i doing wrong?
Click to expand...
Click to collapse
Try following method #1 first, then If you want; flash the custom ROM etc.
The custom ROM I provided works for me so I'm not 100% sure why it's not working. Trying the first method may help :|

lollazzo said:
My phone has bootloader locked. Is it needed?
Click to expand...
Click to collapse
Freezing did not worked for me , I put mine the oven and heated it to about 60 Grad Celsius.
That even gave me enough time to back up my data .
however, is back to live because of this tread.
Thanks.

This is the clear and simple instructions that always make things work first try! Thank you so much!

For June 5th security update I managed to work with those instructions, works perfect with making my own 4 core boot image and recovery.
http://aurelio.net/articles/nexus-5x-bootloop-fix.html

First fix that actually brought my phone back to life
Wow, amazing job, thank you very much! I tried many other methods to fix my device, and some allowed me to boot back into my phone, but I encountered errors like my wifi died etc. So I thought it was the end for my device and it turned into a very expensive USB flash drive lol. I don't know how your fix differs from the other ones on xda ( I used the first method), but it worked for me. So thanks again!

Something happened to my phone today. Its running 8.1 Pixel rom with the bload fix applied. All of a sudden my phone turned off today after running fine from so many months with blod fix. Now it doesn't boot. Google logo and turns off. Not even recovery is working (TWRP 4 core, patched). Can anyone suggest what's wrong?

Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)​
I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
A huge thanks to @XCnathan32 for the original fix!
The steps below will wipe all data from your device!
For Rooting Information and Google Pay fix, see 2nd post.
Changelog
​02/05/2018 - Updated method and added custom ROM method.
​01/05/2018 - Updated TWRP from version 3.1.1.0 to 3.2.1-0.
What does this do?
There are two versions;
The first process will install the 'newest' stock version of Android onto your device; it will then install a custom recovery, and finally flash the updated boot.img file.
The boot.img has been modified slightly to only use 4 out of the 6 cores on the processor, this fixes the overheating issue with the Nexus 5x devices.
The other version is similar except using a custom version of Lineage OS.
Instructions
For detailed instructions and more info please visit the original thread.
Please make sure to have all of the downloaded file ready.
First Method - Stock Image
1. Boot into fastboot mode.
2. Extract factory image zip file and go into its directory.
3. With the phone in fastboot mode and connected the computer, open 'flash-all.bat'.
​3a. Let the process finish; the device will reboot.
4. Go back into fastboot mode.
​4a. [optional] you may wish to flash a custom recovery. If so move into the directory where you have the custom image downloaded. follow step 6a and type in
Code:
fastboot flash recovery [filename].img
5. Now move into the directory in which you downloaded the boot.img file.
6. Once inside; shift-right-click in the file manager and select 'open in powershell' or 'open in cmd'
7. Once the command window has opened: type in
Code:
fastboot flash boot boot.img
8. Now reboot the device!
Second Method - Custom ROM
1. Boot the device into fastboot mode
2. Download the ROM [linked below].
3. Download the GAPPS package [linked below].
4. Download Magisk [linked below].
5. Download the stock factory image; this is important as it contains the newest version of the bootloader, radio and vendor images, which is needed for Lineage to work [linked below].
6. Extract the stock factory image and go into it’s directory.
​6a. There should be a file called ‘flash-all.bat’ - double-click to run it (Make sure phone is plugged in and in fastboot mode!).
​6b. Let the process finish; the device should reboot.
7. Once the device has rebooted, again make sure it’s in fastboot mode.
8. Now download the custom version of TWRP; go into it’s directory then shift-right-click and select ‘open with cmd’ or ‘open with powershell’.
9. Then type the following:
Code:
fastboot flash recovery [filename].img
10. Once that process has finished (it should only take a sec), boot into recovery mode by selecting it via the volume up & down keys; the using the power button to select.
11. Once in recovery;
​11a. Copy and paste the ROM zip archive, Magisk and the GAPPS package to the phone. You should be able to view your phone in the file explorer. If not please install the adb & fastboot drivers.
​11b. Once done; go to ‘Install’ -> the select the zip file you transfered. It will now ask you to confirm, drag the bar across to accept the flash.
12. The ROM will now be flashing; leave it until it is done!
13. Once that process has finished; go back into the install section.
​13a. Now you need to flash the GAPPS package.
14. Once the GAPPS has finished flashing; you now need to flash Magisk. This allows you to root your device and use services like Google Pay.
15. Now reboot!
If all is good then the device will reboot. You should see a boot animation (This can take up to 30 mins, so please wait!), after you should now see the android setup process.
Downloads
The fixed boot image can be downloaded from here.
The factory image: please make sure the version you are downloading matches the updated boot images'. It can be found here.
Modified Lineage OS ROM (boot image updated to the fix); it can be found here.
Magisk -> here.
GAPPS -> here. (Download for ARM64).
A fixed version of TWRP created by @XCnathan32 and updated by me to work with the 4-core boot image. Download Here.
Disclaimer
I will not be held responsible for anyone that decides to proceed with the steps listed above. If there are any issues please post them below with as much detail as you can. I will try my best to answer them, but I do have real-life stuff to deal with.
The original mod was not created myself! I have simply updated it.
Click to expand...
Click to collapse
With the second method, I flash all the files separately, and when I reboot it, the bootagement of Lineage OS started, but it got stuck, how do I fix it?

Dragon's Fedora said:
Nexus 5x BLOD fix (OPM2.171019.029)​​I recently purchased a Nexus 5x from ebay; it had the BLOD issue and, after many days I managed to fix it.
So I have decided to update the boot image to the 'latest' android factory image; this will allow people who have applied the patch to use a later version of Android or a custom ROM.
Click to expand...
Click to collapse
Good job! Works great for me and my similarly acquired device. Easy to read and follow write up too!
For others who may have done something weird like myself during the flash all process. The only issue I had initially was getting a boot and recovery sig not verified error message (or something like that). Worked around it by extracting the zipped image-bullhead-opm file and copying my fastboot files within the folder then fastboot flashing recovery, system and vendor manually. Then everything per steps explained worked as described. This is probably a common, well known error and fix to the BLOD Nexus 5X owners but I've just had this crazy device 2 days.
Thanks again!

Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora

only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.

Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.

Dragon's Fedora said:
Whilst the issue is caused by the hardware; it's actually the software that causes the BLOD. The phone tries to use the 6 cores, but when it detects two of them failing it reboots the device. You can try use other; newer vendor images BUT you must make sure to change the boot.img file within the vendor zip folder.
Click to expand...
Click to collapse
there is a modified rom that is not stock to boot with the 4 cores, and flashed this boot and the recovery fixed and my nexus is restarted every 5 seconds I would appreciate your help and read many post and I think there is no solution

only4dank said:
Used 2nd method and worked perfectly.
Phone has been on non-the-less for a solid 3 hours and battery is stable (had really bad battery drain before, and the system was locking up and freezing and unresponsive as well 2-3 weeks before the BLOD.
I had also previously tried to flash a few other newer 8.1 roms after getting this BLOD, however phone crashed several times during installation and returned to BLOD and was unable to return to TWRP/recovery.
Glad the phone is back to life. Thanks a bunch for the modified rom, TWRP link, and guide!
On a side note, do you feel it is safe to try to flash other vendor images + roms + kernels now... or will the device go back to BLOD. From what I understood this is hardware issue, not software? @Dragon's Fedora
Click to expand...
Click to collapse
Which version of gapps did you use?

GAPP error 70 HELP

I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.

Yurodd said:
I was messing around and deleted google play store, now none of the google apps works. I went a head to download gapps and tried sideloading it. It showed me the error, then i downloaded the pico version and also fix my system partition. It says i have 140mb of free space in that partition. I tried sideloading pico again and still the same error.
Click to expand...
Click to collapse
You're probably going to have to flash your phone back to stock to re-gain all of your apps.

Zachisimo said:
You're probably going to have to flash your phone back to stock to re-gain all of your apps.
Click to expand...
Click to collapse
So flash the rom again? is that going to wipe my phone?

Dark Nightmare said:
This is a basic write up to convert your bootloader unlocked T-Moilbe OnePlus 6T to the International Version firmware via fastboot flashable firmware files.
Contents:
-Disclaimer
- Full Device Backup - Precautionary - Optional, but Recommended.
-Firmware Versions and Flashing Instructions
-Rom Sources
-MSMDownloadTool
-FAQ's
-Additional/Optional Tools
-Credits
Disclaimer:
Like any other form of modding, there are risk involved, we have a near flawless option to recovery by use of the MSMDownload linked at the end of this post, but like with any form of modification, you are solely responsible for what is done to your device and you accept all risk involved, should something go wrong, for the most part, recovery is fairly simply, no matter how bad we screw up, thanks to OP.
Instructions to a full device backup:
1. Download the zip below and extract it to it's own folder
2. run cmd.exe while in fastboot mode and run the following commands:
3. Once twrp boots, run the backup.bat script included, it will backup all partitions on your device, including your efs.
4. zip all of the image files and store it somewhere safe.
Backup: https://androidfilehost.com/?fid=11410963190603855581
For Users Looking to Flash to Firmware versions 9.0.4-9.0.5
FLASHING STEPS
Requirements:
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Flashing Process
1.. Whichever full rom zip you choose, extract its contents. (In my case I used the 9.0.5 full zip)
2. In each zip file you'll find images.zip as well as others_flashall.zip, extract both of them into the same folder/directory as the rest of the original zip file.
(Optional, download the modded flash-all-partitions-fastboot.bat file at the end of the thread, it includes the reboot command to auto reboot when done flashing)
Attached Below is also a flash-all-partitions-fastboot.sh script for Mac OS users (Note this script will not wipe your device, so if you need to wipe, run the ./fastboot -w command in fastboot manually)
All bat files, images and adb files should all be in the exact same folder, no subfolder(s)
3. Now boot into fastboot using either the vol+/vol- and power key combo or via adb using the following adb command .
4. Once in fastboot run the bat file called flash-all-partitions-fastboot.bat
9
5. When asked, I would advise typing 'Y' for yes to format the device. (wipe only if you're converting for the first time)
The sparse header error is completely normal.
6. Upon completion, the script should pause and say press enter to continue, it will not reboot your device...
WAIT UNTIL NOTHING ELSE IS HAPPENING AND ITS NO LONGER FLASHING ANY FILES
At this point, hit power and reboot.
All done!
Firmware Version 9.0.6
Requirements
1. Bootloader Unlocked T-Mobile OP 6T
Unlock Processs Can Be Found Here: https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-version)
2. OOS Stock ROM of your choice: all necessary zip files are included in the rom file.
3. PC/MAC/LINUX
Steps to Flash
Note: Modded fastboot flashing script attached at the end with the reboot command included, also attached is a script for MAC users, mac script will not wipe your device, wipe manually if you need to using
ROM Sources
Mauronofrio's Thread
T-Mobile 9.0 FULL Fastboot ROM
Saythis' International Firmware 9.0.6
Recovery - MSMDownloadTool
If for some WEIRD reason you brick, have a HW mismatch, etc, or you just can't boot go to this thread -> MSMDownloadTool - T-Mobile 9.0
OPTIONAL Steps
Root is available via two Options below:
- OnePlus Rooter
- Manual Root Using a Patched Boot Image
Automated Process
Luckily There are devs looking to make things simpler:
More an automated tool to carry out this process, go to the thread below:
https://forum.xda-developers.com/oneplus-6t/how-to/rom-oxygen-os-9-0-6-fastboot-windows-t3870170
WARNINGS!
-Advisable you disable automatic updates in developer options upon boot if it is enabled.
-Do not attempt to update using the OTA files, so far we've had one softbrick due to it and said user was unable to boot into fastboot to attempt any kind of recovery.
-ALSO DO NOT FLASH WITHOUT THE FILES IN THE FOLDER, IF YOU DO YOU WILL END UP WITH A SOFTBRICK
-If you get either dump mode or fastboot bootloop check your downloaded rom file to make sure its complete, unzip again and flash again
FAQ
Q. Will this enable dual sim functionality?
A. Dual sim functionality works, volte, Wifi calling and vvm.
Q. Can I take OTA's like a regular device?
A. No, sadly.
Q. What about when a new update comes out?
A. Once a fastboot flashable ROM is made, you can update using the steps above, using the new ROM files.
Q. What if I brick or have a HW/SW mismatch?
A. Use the MSMDownloadTool to recover.
Q. Do all the features work?
A. For the most part, there are minor bugs, but they aren't consistent, so can't really say.
Q. Is this a full conversion?
A. Somewhat.
Q. Do I have to wipe everytime I update?
A. No, wiping may only be necessary for conversions, no wipe needed to update.
Q. Do I have to root everytime I update?
A. Yup, sadly.
Q. Do I have to convert to a specific version?
A. Nope, you can convert to any version.
if any edits are suggested, I'll include them.
Credits:
@mackentosh for testing and unfortunately bricking using the OTA File
@Velrix for being the second successful tester, among others.
All the other users who've been testing/contributing to testing
I'll add names when I get to comb through the threads.
@Dameon87 for the correct ROM source link of the unpacked ROM with batch files.
@Krunk_Kracker for the disable auto updates image
Thanks to @Addiso for the Stock T-Mobile Backup images
@mauronofrio for the scripts and for hosting the Rom zip @hartleyshc for testing and confirming full dual sim functionality.
@Saythis - for the 9.0.6 FULL ROM Zip
Click to expand...
Click to collapse
I would follow this guide. Than choose Y when asked to wipe data. If you want to choose N let me know how it goes. But the easiest way is going to be to start from fresh using this guide by @Darknightmare.

upgrade to Android Q & keep twrp and data

Ok here's what I did. To keep my data and twrp when upgrading from "P" to " Q".
1. I downloaded the OTA zip file.
2. Extracted it on your phone.
3. Edit the "Flash-all.bat" file
A. Delete "-w" from one of the last command lines.
B. Add "reboot-bootloader"
"fastboot boot twrp-3.2.3.1-marlin.img"
C. Hit "save"
C. Both the above command lines should be right
before the line "echo press any key to exit"
4. Add the twrp.img to the folder with the above extracted contents.
5. Edit "flash-all.sh" to read the same as you have just edited the "flash-all.bat" file. And then hit "save".
6. Compress the extracted file so as to create a .zip file again.
7. Move this .zip file to your PC.
8. Plug up your phone to your PC and make sure android debugging is active.
9. On your PC extract the .zip file you just created.
10. Make sure you have the twrp installer zip on your phone.
11. Go into the extracted .zip file and double click the "flash-all.bat" windows batch file and sit back and wait.
12. When it finishes it will boot up. 1 out 3 times I tried this it booted then immediately rebooted to the stock recovery with an error saying that my data may be corrupt and if I see this message again then perform a factory reset. And gave me to options "try again" and "factory reset". I clicked "try again". It then booted normally.
13. Power off your phone.
14. While holding vol down press and hold power button for a few seconds and then release the power button but NOT the vol down button. This will put you in bootloader mode.
15. Once in bootloader mode it will then boot twrp.
16. Once once twrp loads click install then navigate to the folder you put the twrp installer.zip and flash the installer. 17. Hit "reboot system"
18. Sit back and wait.
19. All your data will remain on the phone. All your settings stayed the same.
***********NOTICE ***********
1. YOUR BOOTLOADER MUST BE UNLOCKED. IF YOU DONT KNOW HOW TO DO THAT THEN YOU SHOULDNT BE ATTEMPTING THIS. ESPECIALLY IF YOU ASK ME HOW TO UNLOCK YOUR BOOTLOADER.
2. I TRIED THIS 3 DIFFERENT TIMES WITH THE SAME RESULTS. I will post pics of the step by step process later. Just wanted to go ahead and get this out there so those of you who know your way around an android could do it.
3. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
I AM NOT RESPONSIBLE FOR YOU F'ING THIS UP AND NOT FOLLOWING INSTRUCTIONS TO A "T".
4. THIS IS RISKY BUT IF YOU FOLLOW INSTRUCTIONS CAREFULLY YOU SHOULD HAVE NO ISSUES.
Im also posting a pic of my about phone to show I am indeed on "Q" and that this worked for me.
Hope you enjoy
Be patient I'll have step by step screen shots posted in a little bit of the process. To maybe make it easier to understand.

Could this work for official android 10

Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?

Did you try flashing magisk?
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.

All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).

sinkoo1979 said:
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
Click to expand...
Click to collapse
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10

johnblundon said:
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
Click to expand...
Click to collapse
no wipes
Flashed through fastboot.
Steps:
flash bootloader
reboot to bootloader
flash radio
reboot to bootloader
flash system
flash vendor
reboot to system
I was missing OTA function in settings.....
it work for me but can't guarantee it will work for everybody. Best way is to try it.
flashed q beta and went back to pie customs roms by flashing bootloader, radio, and vendor (before official q was released). Have to download all apps but internal storage stayed intact.

salpsuc said:
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Click to expand...
Click to collapse
You're welcome. And sure you could do that I would imagine. May be easier but then I would be explaining a method I did not actually try. And that would suck if by chance some ones phone caused world's to collide. I would feel pretty bad about that. Unless the end result was Nancy pelosi shutting up and resigning.

rahil3108 said:
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
Click to expand...
Click to collapse
I did not have root after flashing twrp.... Seems like, looking back, that I tried and seems like it may have said "successful" but it didn't stick upon reboot. But I imagine it's neither here nor there cuz y'all prolly have root by now...

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