Database Users

Upgrading Rooted (TWRP+SU) PE 1575 from 5.1 to M. Need Advice + I have a guide

Hello,
Now before you ask, I've been doing a lot of research though searching threads and post. I'm actually going to post everything I found so far. On my first attempt of getting Marshmallow a few weeks ago, I downloaded the OTA and installed it. BIG mistake as I had TWRP and stock update didn't know what to do. I had to use CLARK to go back to stock then restore my phone back to Lolipop. Then I had to fix my Wifi Issue. After that I started doing a lot of research.
Here's all of my research links:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
Already Rooted Moto X Pure 2015 (KitKat) - Upgrade to Marshmallow, How?
Marshmallow and root -pg 2
MXPE on the way. Root after getting M update? (POST #18)
I need some input on people who have already went though this. So, this is what I'm getting:
1) Flash/Update to TWRP twrp-2.8.7.1-clark.img
2) Download "XT1575 stock unrooted TWRP backup" (from the first link). UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3) Reboot into Recovery. Backup, then Restore the "XT1575 stock unrooted TWRP backup" image
4) If TWRP ask to install SuperSU, DON'T INSTALL
5) Let the phone boot back up and setup Marshmallow.
NOW, in order to Restore your apps+data with Titanium Backup, your phone has to be rooted. Currently, your phone is not rooted so you have to do the following:
6) Download 2.62 supersu and move it to internal/external SD.
7) Reboot into Twerp.
8) Install 2.62 supersu
9) Reboot
10) Test Titanium Backup and you should be OK.
Now, has anybody used this method or a similar method? I think this is possibly a correct method. Also reading that there's no need to use the seamless root since you can use supersu 2.62.

Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.

lafester said:
Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.
Click to expand...
Click to collapse
But if it doesn't update the modem, I could just flash that on there though TWRP right? NON-HLOS.bin?

If I can get some more feetback, it would be great. I'm going to attempt in one more day. If everything goes good, I want to make a quick guide since it's hard to find concrete guides for this situation.

[GUIDE] Apply OTAs with a custom kernel installed (flashfire) (no TWRP)

I will not be responsible if you blow up, brick, or anything goes wrong with your device
Here is how to apply OTA's to the Google pixel xl (first gen) with a custom kernel installed​
Prerequisites
You need to have your phone rooted with magisk
Flashfire from play store
kernel flashable zip (ElementalX, Franco Kernel, Kirikisura, etc.)
Magisk zip
An OTA from the Google website (search Pixel XL ota) or from your phone
Steps
Have your OTA ready (downloaded or the update screen is showing)
(If OTAs work on your phone, stay on the update screen, do not download or install it)
Import Magisk zip, kernel, and OTA on your phone
Open Flashfire and grant superuser
You have to have your files in the proper steps
Update OTA zip with restore stock boot and recovery checked
Kernel Installer
Magisk zip file
Ever root Disabled
Reboot normal
Click the big red flash button
You are done !!!
Note: If you want TWRP, you have to use a computer to install it
Note #2: Flashfire will detect an OTA on your phone and download it if you have an update screen on your phone. Again do not install the update normally
I give credit to Chainfire and topjohnwu for making these amazing softwares

Any chance to get more detailed steps?

kingbri said:
I will not be responsible if you blow up, brick, or anything goes wrong with your device
Click to expand...
Click to collapse
@kingbri, any chance to get more detailed steps please?

This guide is outdated, use TWRP to update as flashfire does not work properly on 8.1

[PSA] You CAN flash 5.0.1 with an unlocked bootloader

This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.

Hi, thanks for the tutorial. I am in the same state as your initial state and would like to give your solution a try. When you mentioned to wait for 10-15 minutes, exactly what happens on the phone during that time, ie. mutiple reboots, or boot animation, etc? I just want to know what to expect during that time.
Thanks again!

First backup & copy it to pc.
Flash codeworks recovery. Flash the rom. Flash codeworks recovery again. Reboot to recovery. If it's ok, reboot to system. System should charge in about 2 minutes, no more!
Set the phone for 2,3 minutes. Reboot to recovery & flash Magisk. For some users 14.6 works, for others 15.0. Here the man says, 15.2.
If one version of Magisk fail, you need to do it all again and when you rich to Magisk, try other version.

ToucanSam said:
This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.
Click to expand...
Click to collapse
was your phone encrypted?

What did you see during the wait?

Once the phone reboots, it's just the usual OnePlus loading logo. The red and white box with ball going around it. For a few minutes.

Your steps doesn't include wipe and format data. Was your phone in a decrypted state?
ToucanSam said:
This post is solely for documentation that it's possible to flash the update without relocking.
It is in no way intended to suggest that you should do it this way. Please follow the recommended steps when upgrading your device.
No one is responsible for your device but you.
On that note, I've flashed my OP5 without relocking the bootloader using TWRP from codeworx.
My initial phone state:
Unlocked, latest 4.5.15 OOS, official TWRP for Cheeseburger, Magisk 15.2
The steps I followed were:
Download FULL 5.0.1 update
Download TWRP by codeworx from XDA
Backed up data via TitaniumBackup (and move to somewhere else in case of failure)
Reboot to Recovery
Flash 5.0.1 from TWRP (DO NOT REBOOT)
Flash TWRP by codeworx (Install image, choose file, select recovery)
Reboot
Wait.
Wait longer.
Seriously, like 10-15 minutes.
Use 5.0.1.
Flash Magisk 15.2 (15 and 15.1 may cause bootloops. Don't risk it)
At no point was my bootloader relocked.
Again, this is NOT the recommended way to flash this update.
If you are upgrading, please follow the recommended steps to complete your upgrade.
Click to expand...
Click to collapse

Another soft bricked Moto g4 plus XT1642

Hi all,
So I am new to the game, I had an old(ish) phone and attempted to root the device. As some of you might have read on here before, I failed, I thought I had followed all the correct steps. I used the following steps as a guide: (from the unlockr). After attempting to install supersu I was left with a black screen. I can however access my recovery mode in bootloader, the thing is that bootloader is the only thing I can access. I cannot access my moto g4 plus via USB on windows, but for some reason I can access both internal and external memory on a mac. I can see the supersu version, my TWRP etc. I was wondering if someone could help me out, I know this has probably been posted before but I have not been able to find a possible solution as of yet. Thanks in advance

Is your device running stock Nougat (7.0) firmware? If so, then attempting to root on the stock Nougat Motorola kernel may result in a black screen and failure to boot, which appears to be what you've experienced. What those guides generally fail to mention (as they're quite old) is that rooting on the G4/Plus running Nougat requires flashing a custom kernel before you root. Failure to do so appears to trip the anti-rooting measures built into the stock kernel. A more recent guide that I've used for a stable root on a G4 Plus is this https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 Bear in mind you do not need root to flash custom ROMs whatsoever, just TWRP.
If you can still access TWRP, you may have a way out. One thing to try is to flash a custom kernel onto your device - ElementalX is a good choice. https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 for ElementalX v2.0.1 for stock . Download the kernel to your computer, ensure your device is connected to your computer and booted to TWRP, and copy the custom kernel to your device. Try to flash the kernel and then see if your device boots.
If your device still fails to boot, you could try flashing the stock kernel from your backup (you did make a backup before rooting?) or if you're running a more recent OS build, I've uploaded the Feb 2018 and April 2018 security patch stock kernels here: https://drive.google.com/drive/folders/0B-GUyOfb8OgzcUl1NUtHYWNIR2M To flash this in general:
a)Download the kernel boot.img to your device.
b)In TWRP, tap Install.
c)Tap Install image at the bottom of the screen.
d)Navigate to where you downloaded the boot.img and select the image file.
e)Target the image to boot (not recovery).
f)Flash, and wipe cache.
g)Reboot and see if that works.
If those don't work, restore your backup if you made one or you may have to re-flash your stock firmware - you do not have to re-lock your bootloader or wipe your device with this re-flash of the stock firmware.
Does your Windows computer have the correct Motorola USB drivers installed on it? https://support.motorola.com/uk/en/drivers

Strange OTA behaviour after installing Magisk

After a long time I finally decided to upgrade to PIE (stock).
The latest official Fastboot ROM I could find is from May (V10.0.9.0) - so this is what I used to install.
Everything went fine, and as expected I was prompted for an OTA upgrade to August which I performed. The Build number become ...V10.0.12.0
Afterwards I installed Magsik (V19.3) via Boot to TWRP - also with no problem.
But surprise: I was prompted for another OTA-upgrade this time to July2019, and the Build number shows V10.0.9.0 !
Ok, I uninstalled Magisk to get this upgrade done, but the upgrade failed..
Went back to re-flash the Fastboot ROM for May and .. and ... and the story repeated.
Any idea what's going on?

I would reflash whole ROM with the latest official Fastboot ROM again (do not forget to remove bootloader lock command from the flashing script or you'll lose your data) and flash Magisk from TWRP. For the OTA update follow this guide, you don't really need to mess up with TWRP more than once https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md.
One thing to keep in mind - do NOT allow system modifications in TWRP as it will mount system partition as R/W and prevent future OTA updates to install. If you allowed it somewhere in the past (or you don't remember) - delete TWRP settings from /sdcard/TWRP and pay attention on the first boot of TWRP.