Database Users

[How To] Upgrade Rooted JULY Developers Preview to Official 5.2.2 Release

[EDIT Oct. 25] Here's what I did--cleaned up and corrected for bootloaders--to install the official 5.2.2 update (build date September, 2015) on myrooted tablet running Developers Preview, build date July, 2015.This is only for those who rooted and installed the dev preview before the upgrade/downgrade troubles. It let's you keep all your stuff.
Few important things:
If you don't reset/wipe in TWRP you can keep most of your stuff, including homescreen layout, play store and all apps. However . . .
Google framework, account manager, contact sync and calendar sync get deleted with the update.
I didn't flash Gapps and got bogus insufficient space error [130 Mb free] when I tried later. Restoring framework fixed everything, but it may be best to flash new Gapps (although that can cause problems when update doesn't completely wipe /system, like this one). Up to you.
Oct 26 Update: Based on reported "insufficient space" flashing Gapps--plus testing and researching contacts and calendar--I suggest not flashing Gapps but simply backing up Google services framework before you upgrade and restoring it after. The other google system apps that get deleted don't seem to be needed; if you want to sync Google contacts & calendar on the Fire you can add your google account(s) in Settings, same as on any Android. If you don't want Amazon's stock calendar or contacts, get another from the Play Store. I've updated the instructions to reflect this.
.
HDXposed module is no longer needed for working Play Store.
Xposed Framework: The update doesn't support the version we used with the July dev preview. You must either flash the latest version or flash the uninstaller if you don't want Xposed anymore.
Stock launcher now = com.amazon.firelauncher
Home key now defaults to stock launcher until you pm disable it. (No prompt anymore)
Backup Google Services Framework.
Turn off wifi (airplane mode) and plug in.
Download the zips:
* September 5.2.2 update (thanks @Hariiiii !) and rename extension from bin to zip.
update-kindle-full_ariel-20.5.2.2_user_522053520.bin: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
* Latest Xposed Installer or Uninstaller from here: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Installer = Xposed-v74-sdk22-arm-by-romracer-20150911.zip
Uninstaller = xposed-uninstaller-20150911-arm64.zip
* Gapps (if using)
tk_gapps-modular-pico-5.1.1-20150920-signed.zip: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
* 5.2.0_stock_recovery_only.zip
Attached to bibikalka's lollipop post: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Get latest SuperSU apk (?) Don't know if it's required, but I installed it.
- SuperSU 2.52 Beta: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
Follow Step 1 of @bibikalka's guide to temporarily install TWRP and while in TWRP:
a. Flash the update
b. Flash Xposed (installer or uninstaller)
c. Flash 5.2.0_stock_recovery_only.zip
d. Choose boot to recovery and install SuperSU when TWRP prompts you.
Confirm you're in recovery, then boot to system and press Exit at "Welcome to Fire OS 5!"
In OS, see if SuperSU is still managing root access. If it's not or you want to update, install the new SuperSU apk and update binaries.
(Wait to reboot unless you can't get su access at next step.)
Block OTA:
a. Disable dcp or otaverifier (whichever you prefer)
b. Rename system/priv-app/devicesoftwareota/devicesoftwareota.apk extension to apk_
Restore Google Services Framework and reboot.
Turn on wifi and sign in to playstore.

Thanks for the guide!

deleted

putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
As far as I understand from my experience of going from unrooted september 5.2.2 to rooted 4.5.3 to rooted september 5.2.2, it should work fine if you go via that route.

putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
This is only for rooted tablets. Follow the steps Hariiiii describes here. There are guides for what he did.

[How To] Upgrade Rooted Developers Preview to Official 5.2.2 Release
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
I order a replacement. What i have to do to have fire os 5 final with root, play store and other launcher?
Thanks

You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.

Could we possibly get a video tutorial on how to do this?
(May be easier for some.)

Ooh, I don't do video and doubt anyone will for this, but that would be kind. You can pm me with questions.

I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.

Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too

bibikalka said:
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Hdxposed is not necessary

cm11noob10 said:
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Click to expand...
Click to collapse
Think we have some confusion. I'll need to make this clearer: This guide is only for people who already have the rooted developer preview--people who did the downgrade/upgrade using the July build. There is no longer a way to use the developer preview to gain root; the latest version (September) ends up causing bricks, as you learned the hard way. Fortunately, it looks like the official 5.2.2 update that Amazon is now OTA distributing can be successfully used in the downgrade/upgrade operation. I'm sure guides for that will be out soon.

Then I'll look for a guide on that and go from there.
Thx for the replies.

bibikalka said:
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Good feedback, thanks. HDXposed is indeed not needed, which of course means Xposed isn't required. If you don't install the new Xposed, though, I suspect the old, non-working one will stay on system even with factory reset. Your thoughts?
(Edit: NVM. Yes, they'll still have old Xposed, so will need new.)
Yeah, Gapps <sigh> It's such a personal thing. (Thinking about how to handle.)

DoLooper said:
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Click to expand...
Click to collapse
But my first time i update and i didn't flash 5.2.0 recovery and work perfectly and i haved root. This mean that it isn't necessary flash 5.2.0 recovery?
Enviado desde mi SM-N910F mediante Tapatalk

davigar said:
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
Click to expand...
Click to collapse
I'm looking into this again. When you flashed "5.2.0 recovery" which zip did you use, 5.2.0_stock_recovery_only.zip or 5.2.0_stock_recovery_uboot.zip? Thanks.

I flashed 5.2.0_stock_recovery_uboot.zip

davigar, you got the developer preview in order to downgrade to OS 4.5.3 and root, is that right? If not, what OS were you on and how did you install it?
EDIT: @davigar Wait a minute--did you not root? Did you just use this tutorial to install the update and that's when you forgot recovery? This will make a difference. Thanks.

I upgrade my kindle to developer preview then i downgrade to 4.5.3, root and upgrade it to 5.2.2 developer with gapps. I followed the newbie friendly tutorial when i bought it. Sorry for my english [emoji16]
Enviado desde mi SM-N910F mediante Tapatalk

issue with flashing supersu

i have been following instructions from http://androiding.how/root-moto-x-pure/
i have everything correct once in flash the latest supersu my device freezes at the boot image of moto.

If you're running MM make sure to use a systemless root.
I can vouch for the 2.62 version working on this phone. It is the only version I've tried.
Versions above 2.62 did not work, although I've seen some discussion in the forum that 2.67 is ok.

I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
That looks like a really old tutorial, and some of those links may be way out of date.
The bootloader unlock process hasn't changed (since we're pretty much just using Moto's official method), but you'll probably want to grab current versions of TWRP (3.0.0-1) and SuperSU (either 2.65 Stable or 2.67 Beta), IIRC.
Might also be simpler to use a tutorial here on XDA.
Edit: Don't quote me on this, but some older versions of TWRP may not work properly on the MM bootloader. So it could be that the minimum recommended version of TWPR (for 6.0) is newer than whatever is linked to from that old tutorial, which could explain your issue. If that's the case, updating to a newer TWRP via Recovery or Fastboot might just fix your problem.

Mejilan said:
I'm on stock MM and am running the traditional root version of SuperSU 2.67.
No issues here.
Click to expand...
Click to collapse
So you simply flashed SuperSU 2.67 via TWRP and you have fully functional phone and root?
Interesting, as it does not appear to work for everyone...

Yup. I'm not interested in engaging with the systemless root since it's still so experimental and early. I prefer going with a more stable experience.
Titanium Backup and Xposed are part of my bread and butter software environment. If root were broken, I would damn well know, right? Heh.
Gotta have my GravityBox and Enable Ambient Display...
A few weeks ago, I ditched TruPure and followed a Fastboot-heavy guide in order to restore my phone to stock 6.0. Was a pain, but I powered through.
Then I unlocked my bootloader again (with the same code Motorola provided to me months ago), and flashed TWRP 3.0.0 via Fastboot (later updated to 3.0.0-1 via TWRP itself).
Finally I booted into recovery and flashed SuperSU 2.67 beta and Xposed v80. Installed SuperSU Pro from the Play Store, and have been good to go since.
I'm pretty sure that I've been using SuperSU 2.67 for quite some time now, both on TruPure (up to 2.5 before I ditched it) and on stock MM.
I've been updating SuperSU more or less as quickly as Chainfire has been releasing Beta updates, as I'm pretty sure he's been focusing on MM compatibility fixes in recent months.
I didn't realize there were any issues with flashing (though I think TruPure has SuperSU baked in).

i have latest twrp, i didnt bother with the supersu step, but im currently having issues getting turbo charge to work on any rom i tried...

I flashed 2.66 after running commands in terminal to make root systemless & my phone booted normally.
Sent from my Moto X Pure Edition using Tapatalk

D802 any root methods are not working!

hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance

1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.

zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.

so any advice anout that problem?

you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable

Screenshot https://i.imgur.com/6IcIvJx.jpg

slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9

zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?

Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.

zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro

Need Help Flashing Lineage 16

I really try to do stuff on my own without having to make other people repeat themselves a million times but this process is just so complicated and confusing that it's giving me a headache.
My goal: Be able to boot up LineageOS 16.
Code:
httpsforum.xda-developers.comnote-4snapdragon-devrom-lineageos-16-0-t3900807
It says it requires MM firmware and TWRP 3.2 or higher.
I have the retail 900V Note 4.
So far I have managed to downgrade to 5.1.1 and unlock the bootloader. (It says MODE: Developer)
From there I was able to install TWRP 3.0.2.
But now what?
Right now I have a phone that won't boot because there is no OS on it.
1. I can't get Odin to flash any other TWRP besides the 3.0.2 version. Odin just freezes halfway through and never completes. I'm assuming this might be because I'm not on an unlocked MM build yet. Currently still on LP.
2. I'm unsure how to get root back once I upgrade to a MM build. (I only have access to WiFi atm and this guide says it will disable it.)
Code:
https://forum.xda-developers.com/note-4-verizon/development/howto-bootloader-unlock-upgrade-to-t3398144
Any help is greatly appreciated.

I'm no expert so some of the things I'll suggest may not work.
As a first thought have you tried installing Lineage from TWRP 3.0.2
I'd suggest
1. downloading the OEM MM ROM from Sammobile and install that first so at least you have an OS to start with.
2. after setting it up install the official TWRP App update to the latest version of TWRP
3. ensure SuperSU is on the internal drive although I've not had problems installing it from a MicroSD and install it from TWRP Recovery. You should now have a rooted phone on the latest version of TWRP
4. put the Lineage ROM on the internal drive although again I've not had problems installing from a MicroSD (although it does take longer) and after 'Wiping' the system (it should tell you what steps are required from the Lineage guidance) install it.
5. After setup you will probably have to install SuperSU again or Magisk assuming there's no trace of SuperSU left on the system.
Hopefully someone will jump in and comment if I've missed something obvious or got it all wrong. Although I've rooted all 3 of my SM-N910Fs and SM-N910C at least once and installed various ROMs I don't consider myself particularly knowledgable. So far I've not bricked any of my phones or Tablets.

I really appreciate the reply.
Currently I am trying to flash 5.1.1 stock onto the phone and Odin just freezes about 25% into system.img.ext4
I have tried a dozen times.
I believe what makes my phone so difficult to flash is the stock bootloader is locked.

On Android 7.0 Stock, rooted, and wanting to upgrade to... something.

Currently:
Android 7.0 (rooted and unlocked)
XT1687
Build NPNS 25.137-93-18
Magisk + Youtube Vanced module
TWRP 3.3.1 (latest as of this post's date)
I read in a forum topic somewhere that I need to upgrade to the above build first before upgrading to Android 8.x+, but I can't find it anymore. I see these stock downloads and I'm wondering if I should go that route - OPS28.85-17 (Android 8.1 Oreo), but I don't do this very often and I'm always worried I'll brick my only phone. My questions are thus:
Is the OPS28.85-17 firmware a viable upgrade option for me?
If so, am I correct in assuming Magisk/Youtube Vanced work similarly with the new Android version?
Is there a custom ROM you recommend that has a very easy way for me to get Magisk/Youtube Vanced and has automatic/easy updates?
I'm looking for simplicity. I've been through nightmare scenarios with custom ROMs in the past and I just don't have the emotional fortitude to frantically Google boot looping or corrupted backups.
Thanks!

rahlzel said:
Currently:
Android 7.0 (rooted and unlocked)
XT1687
Build NPNS 25.137-93-18
Magisk + Youtube Vanced module
TWRP 3.3.1 (latest as of this post's date)
I read in a forum topic somewhere that I need to upgrade to the above build first before upgrading to Android 8.x+, but I can't find it anymore. I see these stock downloads and I'm wondering if I should go that route - OPS28.85-17 (Android 8.1 Oreo), but I don't do this very often and I'm always worried I'll brick my only phone. My questions are thus:
Is the OPS28.85-17 firmware a viable upgrade option for me?
Is there a custom ROM you recommend that has a very easy way for me to get Magisk/Youtube Vanced and has automatic/easy updates?
I'm looking for simplicity. I've been through nightmare scenarios with custom ROMs in the past and I just don't have the emotional fortitude to frantically Google boot looping or corrupted backups.
Thanks!
Click to expand...
Click to collapse
The latest official firmware from Motorola is
8.1.0_OPS28.85-17-6-2
Here you can get it for every location, also older ones:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
To get Magisk and every module (like YT vanced) working it doesn't matter if you're on a custom ROM or stock firmware.
If you want to stay stock flash the 8.1.0_OPS28.85-17-6-2 firmware for your location as described in that post, root it with Magisk and flash the modules you like.
Btw, YouTube vanced is also available for unrooted devices.

Wolfcity said:
The latest official firmware from Motorola is
8.1.0_OPS28.85-17-6-2
Here you can get it for every location, also older ones:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
To get Magisk and every module (like YT vanced) working it doesn't matter if you're on a custom ROM or stock firmware.
If you want to stay stock flash the 8.1.0_OPS28.85-17-6-2 firmware for your location as described in that post, root it with Magisk and flash the modules you like.
Btw, YouTube vanced is also available for unrooted devices.
Click to expand...
Click to collapse
Thanks.
The instructions in your post mention that the device will be wiped, but the instructions in the website I linked mention only needing to use `adb sideload` and it sounds like there's no wipe involved. Is there a way to upgrade from 7.0 -> 8.1 without wiping my data?

rahlzel said:
Thanks.
The instructions in your post mention that the device will be wiped, but the instructions in the website I linked mention only needing to use `adb sideload` and it sounds like there's no wipe involved. Is there a way to upgrade from 7.0 -> 8.1 without wiping my data?
Click to expand...
Click to collapse
I don't know that sideload method but it seems that it's only updating via OTA update and not with a complete firmware what will cause problems while rooted.
If you want to keep your data just omit the command
Code:
fastboot erase userdata
or delete it out of the flashallO.bat.
Be aware that this can cause problems but a lot of users did it without any problems.