Database Users

Already Rooted Moto X Pure 2015 (KitKat) - Upgrade to Marshmallow, How?

I'm sure this issue is affecting lots of people and is probably buried deep within another thread.
I have a Moto X Pure 2015 that I purchased about a month ago. I then successfully rooted the phone (LP5.1.x)
Yesterday I got notification on my phone of OTA Update available.
I attempted to download and install this update and then I ended up in a (TWRP) Teamwin bootloop, with the Teamwin screen flashing overAndoverAndover and could not turn off or reboot my Moto.
Eventually I got out of the bootloop by doing a hard reset and reinstalling my last backup from TWRP.
---- NOW ---
Please explain in simple language and exact steps how to take an already rooted Moto X Pure 2015 running KitKat and upgrade to Marshmallow. Make it simple, like you're explaining this to a 5 year old.
Please provide more information than "flash a new zip through TWRP." This is for newbies like myself who can follow step by step instructions, but we need each step.
Thank you for any assistance!

You're running KitKat? Wowee! :lol: I think you mean Lolipop!
Anyway, if you have TWRP installed I think the simplest way is to flash one of the update Zip's, I think there are some in the dev section.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Pick one of these which best suits your needs, and install it.

OOPS! Yes, I meant I'm running Lollipop!

Okay, HOW does one 'flash' a new zip onto the phone and into TWRP?
Do I connect the phone to my computer?
Seriously, need to be given simple steps that show how to do this.
Remember, there are a lot of noobs reading this and when you say "flash the new file and install with TWRP" that means pretty much nothing.
Simple step by step, please.

lottanookie said:
Okay, HOW does one 'flash' a new zip onto the phone and into TWRP?
Do I connect the phone to my computer?
Seriously, need to be given simple steps that show how to do this.
Remember, there are a lot of noobs reading this and when you say "flash the new file and install with TWRP" that means pretty much nothing.
Simple step by step, please.
Click to expand...
Click to collapse
If you download one of the MM roms from the development thread you can download it directly from your phone. If you're not sure how to flash a rom/file using TWRP you'll probably want to do a lot more research on the process before you screw anything up. Do you have adb/fastboot working on your computer in case anything were to go wrong?

How did you get root to start with?
Step 1: download zip
Step 2: boot into TWRP
Step 3: connect phone to computer
Step 4: move zip to internal storage
Step 5: flash zip
Step 6: say no to TWRP rooting the ROM
Step 7: read up before performing any risky actions like rooting and flashing OTA's
Sent from my XT1575 using Tapatalk

It's simple, unroot, update, what's hard about that? If you're struggling with that, you probably shouldn't be messing with phones in the first place

If you want complete stock marshmallow, then follow these steps:
This is ONLY for the XT1575
Please read all steps before attempting anything.
1. Back up
You will lose all user data with the method I am giving you.
Back up everything, make one in Titanium Backup (save it to a computer or sdcard too) and make a TWRP backup (boot into recovery, select backup and swipe the slider)
2. Download the stock file from @gokart2 's thread
Expand the 6.0 section and then expand "XT1575 stock unrooted TWRP backup". Download the file named "6.0 stock unrooted.zip".
UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3. Boot into TWRP and select "restore". Navigate to the 6.0 stock unrooted backup, select it, then swipe the slider to restore the backup file to your phone..
4. Let the restore finish, then once finished reboot the system. You will get a prompt from TWRP asking if you want to install SuperSu. DO NOT INSTALL IT.
5. Let the phone boot up (It will take some time, possibly even a half hour) then set up Marshmallow .
6. Redownload TItanium Backup and restore your old Titanium Backup, but use caution. I only restored the "User Apps +Data", restoring system data could not go well.
7. Enjoy your new Marshmallowy experience!
7a. If you want root, the method right now is Chainfire's systemless root. Read extensively on systemless root before attempting. But here's a link to Chainfire's thread for systemless Marshmallow root.
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
Jay794 said:
It's simple, unroot, update, what's hard about that? If you're struggling with that, you probably shouldn't be messing with phones in the first place
Click to expand...
Click to collapse
It;s a little more complicated because if he had modified any other system files while he was rooted, he must restore completely to stock before updating if he wanted to use the OTA update

>asking if you want to install SuperSu. DO NOT INSTALL IT.
Ok, what happens if you do say 'yes' to install SuperSu?
That's what roots the device, yes?
The reason I'm asking for drop dead simple instructions is because many (perhaps most) of the threads manage to skip steps -or- assume the user already knows what each step is. I created this thread for those who root their device, then don't think about it further, don't install ROMs, don't do anything other than have a rooted device, but then when it comes time to install new (OTA) software update months later, don't remember what to do or how to do it because they did it once on their Moto and that was it.

lottanookie said:
>asking if you want to install SuperSu. DO NOT INSTALL IT.
Ok, what happens if you do say 'yes' to install SuperSu?
That's what roots the device, yes?
The reason I'm asking for drop dead simple instructions is because many (perhaps most) of the threads manage to skip steps -or- assume the user already knows what each step is. I created this thread for those who root their device, then don't think about it further, don't install ROMs, don't do anything other than have a rooted device, but then when it comes time to install new (OTA) software update months later, don't remember what to do or how to do it because they did it once on their Moto and that was it.
Click to expand...
Click to collapse
No, TWRP has not been updated to work with rooting marshmallow. It will not install the correct superSu. You must flash chainfires new systemless root supersu if you want root, but even then the root is systemless. Meaning there are some root apps that do not work with systemless root.
The beauty of systemless root is that it doesn't touch /system so if you do a factory reset, root is removed. That way all that needs to be done for an OTA update is factory reset or remove root via another method.
Sent from my XT1575 using Tapatalk

I tried this method and got MM installed, however I could never get any networks to show up to finish the install process. I rolled back to 5.1.1 for now.
I guess my next step is to roll back to stock and try it that way unless someone has a suggestion.

Research! And then do this
I do agree that you need to do more research before even starting a project such as this, and in general if you plan to play with modding your device in any way! You can't always expect step by step instructions and you really shouldn't be messing with anything at all unless you have a decent understanding of how things work. We are all "noob's" at first (or most, at least) so it's totally understandable for someone to ask for help--but it's also a bit impolite to come in demanding step by step guides, considering most (presumably) of us learned how to do most stuff by searching and reading through forums. TL;DR: Make sure you do your research before you start a project!!
That said, there is a fairly detailed and easy enough to follow guide by reformedmusings over at: https://reformedmusings.wordpress.c...ure-2015-to-android-6-0-marshmallow-on-linux/
I am actually in the middle of the process now and things seem to be going smoothly. You can do everything from a windows PC, just ignore "sudo" as that is a linux/unix command... The easiest way to copy stuff to your internal SD is to connect (with device in MTP mode) to your PC and copy files to your devices SD card from File Manager or whatever (root directory).
I hope this helps!
Update: It seems to have worked fine! I was able to update to marshmallow, though I actually chose to copy the update image to my PC and ADB Sideload instead of upgrading from SD Card because I couldn't find the file and the screen wouldn't scroll. Root seems to work fine, also. I didn't reinstall xposed and Android Pay seems to be working with root (as some have noted)--I think Android Pay will stop working if xposed is installed (or even the new dialer).

How to Root Honor 8 FRD-L09 (NOUGAT 7.0 EMUI 5.0 With Bluetooth, NFC, system apps)

I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
I have only tested this with the device: (Honor 8 FRD-L09)
If anyone got this working on other devices please leave a comment so I can add it to this list for other people to see.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this with OldDroids TWRP or with surdu_petrus TWRP: Link(36.2MB) and Link(24,2MB)
1- Flash OldDroids or surdu_petrus TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid, surdu_petrus and phhusson

thierrybla said:
I had been struggeling myself alot with this but after looking everywhere I collected pieces of information all over XDA and fixed it.
Since all the information is scatterd around everywhere I thought it would be good to make a complete piece here.
So here it goes:
1- First you need to be have an unlocked bootloader.
2- Flash via fastboot the new TWRP with decryption support Here
3- Download two files:
a- update.zip Link (1.5G)
b- update_data_full_hw_eu.zip Link(1.05G)
4- Flash these two files using TWRP (a then b)
5- Reflash TWRP (using fastboot)
Finally, to root, you need to flash this patched prerooted boot.img B378 root boot image (from SD card): Link(15.8MB)
You can do this only with OldDroids TWRP: Link(36.2MB)
1- Flash OldDroids TWRP
2- Select "Install" -> Click "Images" -> Go to External SD and select your rooted_b378_boot.img
3- When it asks where to install click boot.
4- Then reboot and install phh's superuser from the playstore (its the only superuser that works for now)
5- Install JRummy's Busybox Installer and install to /vendor/xbin
Done!
Note: To get AdAway working, go to Preferences, then scroll down to "Target hosts file" and set it to "custom target". Then set Custom target to "/vendor/etc/hosts"
If you have any questions feel free to send me a message I had much trouble with it too.
Credits to: morpheus302, Atarii, OldDroid and phhusson
Click to expand...
Click to collapse
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM

omartins said:
Hello!
Can you please specify for which variants of the FRD is this valid?
Thank you
RM
Click to expand...
Click to collapse
I have only tested it on the FRD-L09
I can't say for sure if it works on the others, I'm sorry.
If you got this working on a different device please let me know.

Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?

david320te said:
Quick Question: I have installed normal TWRP 3.1.0.0, every time i want to install the newest SuperSu Beta, it resets TWRP completely. Is your guide also going to work for me, or do i have another problem?
Click to expand...
Click to collapse
Yes SuperSU doesn't work as far as I know you need Phh Superuser.
But if you already have nougat 7.0 B380 you can just begin at the boot.img installing step and it should work for you too.
Good luck!

Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The difference is that the TWRP that I linked can flash .img 's
wich you need to flash the boot.img
Try to get back in TWRP and start at step 1 just do the whole guide then your phone should boot again

david320te said:
Ok, but you linked "twrp-3.1.0.0-eva", i've installed "twrp-3.1.0.0-frp" - do you know, where the difference is?
Edit:
Well, something has gone wrong. Doesn't boot...stays on that screen forever...i tried restoring the backup i took while the system was read only with TWRP
Click to expand...
Click to collapse
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Q: Why does booting take so long?
A: Because of the decryption process which need to finish
its work before twrp tries to access /data partition.
Click to expand...
Click to collapse
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.

N01tra said:
The "twrp-3.1.0.0-eva" is for the Huawei P9, the "twrp-3.1.0.0-frD" is for the Honor 8.
And first boot after TWRP install can take longer that usual:
Try flashing the pre-rooted boot.img via fastboot command line.
Worked for me.
Code:
Copy the pre-rooted boot.img to the adb/fastboot directory
(have usb debugging enabled etc etc, connect phone to computer)
Start a cmd box
adb reboot fastboot
fastboot flash boot rooted_b378_boot.img
reboot device.
Click to expand...
Click to collapse
You are right it is for P9 but it worked for me regardless though :fingers-crossed:

david320te said:
I can boot into TWRP no Problem, as i said, i restored the backed up image (somehow after a factory reset, the stock apps as well as the keyboard was gone, i could not type in my wifi password) in TWRP, but it sat for about 10 Minutes on that screen when i turned the phone off.
I do not have very good Broadband, so i will start at the first step, installing the update files, linked in the first post.
Click to expand...
Click to collapse
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot bootloader),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.

N01tra said:
Yeah.. A FactoryReset seems to be a big "no no" after flashting TWRP as it will delete the keyboard and other stuff.
I was in that situation and restored a TWRP backup which got me back to booting into android, but somehow the Camera and LED (flashlight) didn't work.
Restoring an older and a complete backup did not help. Flashing the Update files did not help.
Eventually I ended up following the Honor 8 Rollback steps; going from Emui 5 (android 7) back to Emui 4.1 (android 6).
That also means the Bootloader is locked again, so you'll have to re-unlock it again (if you still have the code, you can use it again).
My steps after the Rollback:
- OTA updated back to Emui 5,
- Factory reset (BEFORE installing TWRP) and reboot.
- Enabled USB debugging,
- Unlock bootloader,
- Flashed TWRP and immediately after that I booted into recovery and rebooted,
- Rebooted to Fastboot (via adb reboot fastboot),
- Fastboot flashed that pre-rooted b378 boot.img and rebooted,
- Installed Phh's root.
Click to expand...
Click to collapse
I had the same as you describe here but I fixed it by flashing the 2 files I posted up here (a and b)

After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/

david320te said:
After doing it step by step as described in the first post, it worked I also flashed the P9 TWRP, just to make sure. It works! But i already miss Resurrection Remix from my Mi4c...
However, does this mean TWRP Backups are useless? :/
Click to expand...
Click to collapse
I'm glad to hear it works! :highfive:
TWRP backups never worked for me I always just flash it clean and then have titanium backup do the rest
Have a nice day

Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.

fourcc said:
Hi,
maybe what I am going to ask sounds silly but as I am a kind of newbie hope you will forgive me
Why do we have to install a prerooted 378 image instead of a prerooted 380 Image. Aren't we on 380?
Where does this 378 image come from? Until now I only saw Nougat's 360 & 380 Roms.
I am already on 380 but my root doesn't seem to work properly so I wanted to give a try to thierrybla's OP's post but I don't know if to follow his instructions by using OldDroids TWRP to install his suggested prerooted 378 Image or instead by using OldDroids TWRP to install the other thread's Prerooted 380 img.
What shall I do if I'm already on 380 but would like to try thierrybla's procudure so see if I finally get a well-rooted 380 rom?
Any help would be appreciated.
Click to expand...
Click to collapse
Hey,
Your question is not stupid I can see why you are confused but everytime I tried to root or preroot something it didn't work for me I also run 380 and once I tried the prerooted 378 made by atariii it worked so there is no reason te be skeptical because I was in the same situation as you and this worked for me just give it a try you won't be disappointed

Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!

fourcc said:
Thanks for your quick answer!!!
Ok, so I understand it is safe to install prerooted 378 image while being on nougat's 380. Thanks, I will try it right now!
Click to expand...
Click to collapse
Tell me how it went !
Goodluck!

Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!

fourcc said:
Hey thierrybla, it worked beautifully! Thanks!
The only thing I did different is too install the prerooted image with Fastboot instead of the Oldroid Twrp.
I was afraid of messing my good working TWRP setup and decided to try what N01tra user suggested.
It worked like a charm! Thanks again!
Click to expand...
Click to collapse
that's fine too I'm glad it worked good for you!
Have a nice day!

[Guide]How to get an update if unlocked and rooted, but otherwise on stock EMUI

I just bought the Honor 8 and immediately unlocked and rooted it via Magik. Of course not long after that, I get a notification that there is an update available. You obviously cannot update the phone by simply pressing the "update" button since we have a non-stock recovery. I did a fair amount of research to find out how I could get the update and I wanted to share what I found. All of this information is out there already, but generally speaking it is spread out in many different threads. Hopefully these directions can help someone else.....
First, the usual disclosures.....
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this GUIDE
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
1) Make a NANDroid backup using TWRP: if the new update locks the phone, you will need this backup to restore data after unlocking it
2) Unroot your phone: honestly I did not do this step myself because I simply didn't think about it. The update process worked for me without unrooting but I am also using Magik which doesn't alter the system files. To ensure success I would definitely recommend you unroot. You will have to reroot the phone after the update regardless if you unrooted or not, so you aren't saving any steps by keeping root at this point. If you have used a different root method besides Magik, you must unroot prior to attempting an upgrade.
3) Obtain stock recovery.img file: the update won't work with TWRP as your recovery, so we need to flash the original Huawei recovery to replace TWRP. If you already have a copy of the stock recovery skip to step 4. If you are like me you don't have a copy of the stock recovery image on hand and we will need to extract it from the stock ROM image. Using a computer (not your phone) download the stock ROM image for your device. This website seems to have a list of recent versions and it is where I downloaded the L14 B389 version that I used.
Download the Huawei Update Extractor software and unzip the folder on the computer. Open the HuaweiUpdateExtractor app and use the software to extract the "Recovery.img" file. Here is a Youtube video showing how to do this. Please note, although the video shows several files being extracted you only need to extract the "Recovery.img" file for our use. Move the stock recovery image to your ADB folder so you can flash it in step 4.
4) Flash the stock recovery image: use the stock recovery file and flash it to recovery using the same instructions as you used to flash TWRP in the first place. If you need a refresher, look at section 2 (parts 1-5) of the first post in this thread. Just make sure you substite the name of the stock recovery image instead of the TWRP.img
5) Reboot into system
6) Install Update: go to the Settings - System Update menu on your phone. In the upper right corner, click on the three dots and it will bring up a menu where you can choose "Download latest full update". Click on this. This will start the update process by downloading the full ROM and not just the smaller update package. For me the package size was approaching 2gb, so make sure you are ready to handle that size transfer. After the download is complete, start the update process. I was nervous at first, but everything went fine. If for some reason the update fails, I would reboot and try again. I did have one failure, but I cannot explain if it was a bad download, or something I did wrong (like not unrooting the phone prior to attempting the update). It worked fine the second attempt.
7) Reboot: the phone will reboot and you should check the status to make sure you are on the latest version.
8) Flash TWRP recovery: I read where people said full updates would lock your phone and you would have to start from scratch unlocking it (and therefore wiping all data). This was not the case for me and this update using this method. I was simply able to flash TWRP again. You should be a rock star at flashing recoveries by now so get to it and flash TWRP again. If your phone is locked, then read the note at the bottom of this post.
9) Reboot into system
10) Flash Magik zip: reboot into recovery and flash Magik zip to get SuperSU.
11) Install Magik modules: reboot into system. Reinstall any Magik modules you use as they don't get carried over from the previous installation.
12) Enjoy your updated phone
If for some reason the full update did lock the phone, then you will need to unlock it again before you can flash TWRP. You have already done this before, so use whatever method was successful for you. Obviously this will fully wipe your phone. After flashing TWRP and Magik, I would make a backup of that raw "stock" image just in case this next step doesn't work. After making the backup, you can try to restore just the data partition of the NANDroid backup you made in step 1 (click restore in TWRP, select the backup made in step 1 but deselect everything except the "data" partition before starting the restore process.) I have never done this, but I have read it will recover all your data (apps, etc) without affecting the system partition and therefore it won't mess up the upgrade. I would not recommend doing this if going from Marshmallow to Nugget or Nugget to Oreo however. In those cases, it is better to simple start fresh and redownload all of your apps.

Thank you for this thread.
Hello sic,
I am having the same issue with my Huawei GR-5 2017 and like you, I have my fair share of researching for weeks now and I was really happy to stumble on this thread.
Before I start with the process, I have a few questions for you. I hope you could help me (even though this thread is half a year ago).
Can you elaborate steps 1 and 2 or could you provide me a link on how to do those?

I got xposed installed im on emui 8 i also tried flashfire but it only turns the phone off.. Ist it eneugh to uninstall xposed? And can i get the recovery img from fullota? And must i restore images in magisk? I will try it without xposed installed. And a theory: is the information abaut bootloader unlock stored in a partition like oeminfo? If it is we could restore oeminfo.

Foolproof way for OTA-update with Magisk installed

Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?

Tiemichael said:
Now that a new OTA is available, and like many others like myself have rooted the A1 with Magisk, I am looking for a foolproof way to update.
Remembering the last (March) OTA, when a lot of people complained about difficult, I wonder if someone has found a good way.
I remember 2 approaches:
1) follow the flow from here: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
or
2) uninstall Magisk completely, maybe even re-lock the phone, and start from the beginning as outlined here: https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
What is your experience or recommendation?
Click to expand...
Click to collapse
Hey!
Following the official Magisk procedure works, at least for me.
You just have to be careful to restore backup image before starting the OTA download and installing to second slot (After OTA) before rebooting.
Reading this thread:
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
I found there’s a lot of confusion (I was confused also and made a few mistakes), but my conclusions are:
- That method is to be used just ONCE in order to gain root, and not every month.
- Always try to use your own patched image if you have the opportunity
- You have to use “fastboot BOOT” and not “fastboot FLASH” when first rooting, otherwise you won’t be able to restore boot image and OTA will fail
- Follow official procedure as a cooking recipe
If you don’t want to root using a patched boot image, you can also use latest TWRP (As of now latest is recovery-3.2.1-2-oreo.img)
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
And boot to TWRP image in order to install Magisk ZIP (did this yesterday and also worked), but the update via OTA method should be the same.
Best regards.

Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me

Keeping phone to stock and not rooting for only one OTA in more than a month? I think its not worth it!!
I always root my phone and when OTA arrives i just flash twrp version of it and root it again ?

Siebenmik said:
Personally I just did this:
1) Uninstall magisk (remember to save modules you want to save etc.)
2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition)
3) Relock bootloader
4) Update
5) Unlock bootloader
5) Booting in new april patched_boot.img
6) install Magisk.
official magisk method didn't work for me
Click to expand...
Click to collapse
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?

I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..

_mysiak_ said:
I'm following the very simple Magisk OTA update guide and I have been able to update system via OTA for several months already. No rocket science there, as long as you don't mess with system partition (e.g. do NOT allow system modification in TWRP), you are good to go. I even used it successfully with custom kernel (Franco kernel)..
Click to expand...
Click to collapse
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?

Tiemichael said:
Are you referring to this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips?
Click to expand...
Click to collapse
Yes, exactly. I didn't have any issue with OTA installation yet.

Tiemichael said:
Just wondering "2) Reflash stock boot.img (march update) via fastboot (in the correct booting partition) " should be identical to "Restore Images" in Magisk Uninstall
I think updating can be done without "locking bootloader " and "un-locking bootloader"
What do you think?
Click to expand...
Click to collapse
I forgot saying that using restore image in magisk didn't work. Even though I didn't flash the patched boot.

https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where to enable secured startup?

Skeuomorphic said:
Where to enable secured startup?
Click to expand...
Click to collapse
create a pattern from security setting and it will prompt to enable secure startup.. just press yes..

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Finally a different answer, I have secure boot disabled maybe this is the reason ending into bootloop for past 3 montly security updates. Will try this for May update.

coolkoushik07 said:
https://github.com/topjohnwu/Magisk/...tallation-tips
This process works every time if you have enabled secured startup.. If secured startup is disabled then you will get bootloop..
Click to expand...
Click to collapse
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....

Tiemichael said:
Where can I find 'secured startup' ?
Sorry, for the maybe stupid question ....
Click to expand...
Click to collapse
Settings->Security & Location->Screen lock->Pattern

This what was working for me just now:
Detailed steps performed 20.4.2018:
Backup Titanium
Backup Magisk Modules
Switch on Secured Booting (e.g. Pin) => not same a normal pin!
Open Magisk
Uninstall Magisk​
Restore Images​
Start OTA update
Downlowd​
Step1​
Step2​
Go Back to Magisk
Install to 2nd slot​
Reboot​
It was working ... very easy!

I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.

I didn't update my phone for a very long time, then I decided to finally go for the latest MIUI on my Mi Max and basically I flashed full new ROM via fastboot & MiPhone.
You can see detailed description here: https://forum.xda-developers.com/showpost.php?p=78050983&postcount=41
I think it should work with other Xiaomi phones too but please correct me if I'm wrong
The only difference is that I had SuperSu before, but maybe with Magisk it's the same to do - also correct me if i'm wrong

quetzalcoatl2435 said:
I can confirm that topjohnwu's official ota tips do work with the Mi A1, but you must have secure booting enabled.
Click to expand...
Click to collapse
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
H.A.L. 9000 said:
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Code:
fastboot boot recovery-3.2.1-2-oreo.img
2. flash magisk unistaller from recovey
3. Update your system
4. Repeat the same procedure to root again your device.
If you are italian and you need any help you can find it here, the serious telegram community.
https://t.me/XiaomiMiA1Italia
Special thanks to @samuele94 and @TheRealajeje from the telegram group.
Click to expand...
Click to collapse

freekarol said:
THERE IS AN ALTERNATIVE WAY.
Advantages:
-100% working. Absolutely no problem with unrooting.
-secure booting doesn't have to be enabled.
Disadvantages:
-Installed modules will be lost. I don't know how to back them up.
---------------------HOW TO UPDATE-----------------------------------------------------------------------------------------------------
When you will receive the update the only thing you need to do is boot twrp, flash magisk unistaller (that you can find here ) and update.
1. type this to boot your recovery (REMEMBER TO COPY THE RECOVERY IMG INTO THE FASTBOOT FOLDER)
Click to expand...
Click to collapse
Yeah, but you need a PC for this. If I need access to a PC every time there's an OTA update, might as well download and flash a full ROM. ?
Official Magisk OTA guide works anytime anywhere, no PC needed.

Complete backup without TWRP?

Hello,
I have recently moved to the A1, really nice so far.
I followed the guide to root using Magisk and got it all rooted and set-up nicely (I think it was this one).
However, I did not install TWRP and now when I was searching the forum, doing a full backup (to be prefectly recovered to the backup point) it always refered to TWRP (or equivalents), yet the installation of TWRP requires me to "go back" to the unrooted device.
I am looking for a solution to create a complete, full backup (same way TWRP does), on the phone in it's current state before I keep doing any other changes.
Help a noob out

TheWhitestOfFangs said:
Hello,
I have recently moved to the A1, really nice so far.
I followed the guide to root using Magisk and got it all rooted and set-up nicely (I think it was this one).
However, I did not install TWRP and now when I was searching the forum, doing a full backup (to be prefectly recovered to the backup point) it always refered to TWRP (or equivalents), yet the installation of TWRP requires me to "go back" to the unrooted device.
I am looking for a solution to create a complete, full backup (same way TWRP does), on the phone in it's current state before I keep doing any other changes.
Help a noob out
Click to expand...
Click to collapse
You can go to Twrp without installing it, just with fastboot, run "fastboot boot twrp.img" on cmd and you can do a backup of your phone on sd card, bootloader must be unlocked.

If you have an unlocked bootloader, you can backup every single partition in the device (and I mean everything, TWRP only does a few) via EDL mode. Search for EMMCDL tool.
If you're willing to wait a few days, I will be releasing a guide for this.