Android Nougat on Moto Z (All Unlocked Versions) - Moto Z ROMs, Kernels, Recoveries, & Other Developm

Android Nougat on Moto Z (All Unlocked Versions) - Moto Z ROMs, Kernels, Recoveries, & Other Developm

I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Backup Without TWRP or Unlocked Bootloader (When you're trying to prepare for a bootloader unlock)
http://forum.xda-developers.com/showpost.php?p=69821066&postcount=38
Alternative method :
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
spicial thanks to @papampi
Downloads:Verizon Stock Unzipped: https://drive.google.com/open?id=0ByioJuadKHC6c3BkMnVydDRzQlk
EU Unzipped (WIP) by @erfanoabdi (See Post #17): https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA
Main Verizon Firmware Lolinet: https://mirrors.lolinet.com/firmware/moto/griffin/official/VZW/XT1650_GRIFFIN_VERIZON_6.0.1_MCLS24.246-36-3_cid2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main Verizon Firmware Google Drive: https://drive.google.com/open?id=0ByioJuadKHC6MjJDXzhJSXlBaDA
Downloading Zips from Google Drive
http://forum.xda-developers.com/showpost.php?p=69821121&postcount=39
New Downlaod Link :
Main RETMX Firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Main TELUS Firmware (NPL25.86-30) : https://mirrors.lolinet.com/firmwar..._subsidy-TELUS_regulatory-DEFAULT_CFC.xml.zip
Main RETUS Firmware (NPLS25.86-17-3-8) : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Installation Guide:Download and extract Main TELUS Firmware on PC
Make Sure You have backup of your whole Device [System, Boot, OEM, Data, Internal Storage]
Flash System, Boot, OEM, Fsg, Modem Partitons :
Code:
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
(continue it it has more chunks ...)
fastboot flash oem oem.img
fastboot flash fsg fsg.mbn
fastboot flash modem NON-HLOS.bin
fastboot erase cache
(fastboot erase userdata) (Not Needed But Recommanded)
Boot into TWRP :
Code:
fastboot boot twrp.img
(or flash it)
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to Disable Force-Encryption (Not needed but Recommanded)
Code:
adb sideload UPDATE-AnyKernel2.zip
wait to complete flashing
ROOT : (OPTIONAL)
Follow this Guide : https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
use adb sideload (Advanced -> ADB Sideload) and flash this ZIP from attachments to get systemless Root access
Code:
adb sideload superuser-r259.zip
Reboot
(For Rooted Guys) install phh's SuperUser From PlayStore : https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
(it's working and confirmed on XT1650-03 and 05, RETUS, EU, CN, ...)
ENJOY
After Installing Nougat With This Method You Can take Back to Stock Marshmallow Or Install New CM14.1 Builds This is safest and Easiest Method To Install Stock Nougat on Moto Z
Why not help out XDA and spam click a few ads? (and then close the tabs cuz who really wants to buy stuff from ads lol. Either way, XDA gets money just for you clicking on them )
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673, erfanoabdi
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Stable
Created 2016-11-24
Last Updated 2017-07-16

Updates
Update 5:
Added erfanoadbi's EU port to the downloads list. We need testers!
Update 6:
When I added erfanoabdi as a contributor it reset this post lol. I've fixed it as much as I could though.
Update 7:
The system.data.patch file finished uploading on the Verizon Unzipped Link
Update 8:
Added installation instructions for the EU test to the OP
Update 9:
Added an alternative link for the Verizon firmware as some people were having problems with the first link
Update 10:
Added Google Zip Downloading and ADB Backup Information to OP
Update 11:
EU Test doesn't work
Update 12:
EU Test works now thanks to erfanoadbi's awesome work
Update 13:
Added stuff about Moto Voice error to OP

ADB and Sideload
If you don't know how to sideload, you'll first have to have adb installed on your pc. If you're on Windows, refer to @Snoop05's post here: http://forum.xda-developers.com/show....php?t=2588979 and download the installer for adb and fastboot. If you're on a Mac, refer to @AshtonTS's post here: http://forum.xda-developers.com/show....php?t=1917237. Also, be sure to throw these awesome people some thanks
For my fellow peoples on Linux:
Ubuntu: sudo apt-get install android-tools-adb android-tools-fastboot
Arch Linux: sudo pacman -S android-tools
Red Hat and others: You people are straight up savages and probably already know how to get a hold of it lol.
Open your terminal, the command prompt for Windows users, and cd to wherever the adb binary is (Linux users don't have to do this because it's already in your path, unless you installed it some way other than the package manager). Move the ota.zip to that directory. Enable USB debugging on the Moto (Settings > About Phone > Click Build Number 7 times, then Settings > Developer Options > USB Debugging) and then plug the Moto into your PC. Type "adb reboot recovery" (Mac users type "./adb reboot recovery"), and then wait. (If this doesn't work, look on the Moto and see if there's an authentication dialogue) On the Moto you'll soon see the Android robot lying on it's back and a red triangle above that. The screen will read "No command". Press and hold the power button for 2-3 seconds and then quickly also press Volume up and then release both buttons. On mine I have to do this button pressing thingy a few times, but eventually the recovery menu will come up. When it does, use the volume buttons to go down to the "Apply update via ADB" option and press the power button to select it. Go back to the computer and type "adb sideload ota.zip" (Mac users don't forget the "./" at the front) and it'll start to sideload the zip onto the phone. After that just wait and soon it'll install Nougat. (Ofc now we know that this isn't always the case)

I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted

Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...

Via TWRP it gets stuck as it's expecting the Google folder in META-INF>Com. I added it from the original OTA and it's throwing up Griffin product name errors. Going to try a few things.

H00pyFr00d said:
I imagine the intention is to flash this from stock recovery rather than TWRP? I get E:footer is wrong E:Signature verification failed Installation Aborted
Click to expand...
Click to collapse
Yes, stock recovery is the goal but if you have TWRP then you can use that. Just know that the modem files and stuff are strictly for Verizon, so I wouldn't try to force flash it until I get those replaced.

H00pyFr00d said:
Going to try a few things.
Click to expand...
Click to collapse
Ok great

Shadowdancer123 said:
Stock recovery won't mount either the internal or external storage, and using adb sideload it just says
"unable to load ota.zip"
It doesn't appear to even try to open or verify the file itself, maybe it's too large?
I tried sideloading twrp.zip, just to see if it would do Anything at all, and that file is loaded and rejected (because my bootloader is locked)
I have reteu, not verizon, but I should at least get an error message.
Maybe I just have to wait, they claim to have begun rolling out world wide, but I've been hammering that update button once an hour since monday...
Click to expand...
Click to collapse
To be on the safe side, yeah I'd wait until the official OTA comes out. If you want it early tho that's cool too, just upload your current stock rom and I can play switcheroo on some necessary files.

With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD

Shadowdancer123 said:
With the limited backup capabilities of unrooted android and scarcity of fastboot rom files..
I'm just gonna sit here and click refresh on the update button. XD
Click to expand...
Click to collapse
Lol true. I'm gonna keep trying tho

SoulDJ673 said:
I was encouraged to make a separate thread for this, so I did.
Here we're going to try and port the Verizon Nougat update to all Moto Z phones.
I said I'd upload the code into GitHub to make it easier to change stuff, but that got too confusing so I just used Google Drive lol. Anyway, let's get started.
I'll start by editing the update script in the zip, and I'll need somebody to verify that it works. Just be forewarned that things might break (thus the alpha status). If things break, there are other threads with all the Marshmallow stock zip files, flash that and try again. Make sure to check those threads before you flash though, because if you break your phone and then check those threads to find your zip just to realize that they don't have your zip, then you're screwed. Please, please, please, PLEASE make a backup of your ROM. I'm here to fix problems with this ROM, not to fix your phone because you didn't backup your data.
Now that we've gotten that out of the way, here's the link to download it: null
Just so you know, if you try downloading it before around 13:00 EST, you won't have the full thing. My internet isn't the best, so it's gonna take a while.
Happy Thanksgiving everyone
Update:
Internet Crashed :/
Update 2:
I got most of the ota to upload but not all of it, but now as a wonderful Thanksgiving present I've got more drama in my life :/. I'll take a break for a day or two, hopefully Moto doesn't send out the rest of the OTAs so my attempts are for nothing.
XDA:DevDB Information
Android Nougat, ROM for the Moto Z
Contributors
SoulDJ673
ROM OS Version: 7.x Nougat
Based On: Stock Verizon Nougat OTA.zip
Version Information
Status: Alpha
Created 2016-11-24
Last Updated 2016-11-24
Click to expand...
Click to collapse
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42

I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..

janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Awesome, Thanks a lot.

Needing Only One or Two Small Files
erfanoabdi said:
Hi @SoulDJ673, thanks for working on this project.
could you please give me list of files on this zip? is it contains "system.new.dat"?
could you please only upload "system.new.dat" for me, this shouldn't be heavy too mach
thanks again
_________
Sorry,
i found your uploaded zip here http://forum.xda-developers.com/showpost.php?p=69764157&postcount=42
Click to expand...
Click to collapse
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip

EU Version
janjan said:
I am going to make a flashable zip to night. It will probably work with EU version. Need to investigate..
Click to expand...
Click to collapse
Thanks a lot, it's been hard trying to even think of ways to port this without having any of the devices I'm trying to port it to lol. If it works, throw me a link and I'll put it in the header post and add you as a contributor.

SoulDJ673 said:
Sorry I didn't answer, where I'm at it was around 4 AM and I was too tired to do anything, and also I've been having some issues in my life rn. But, things are better so I'll be more present. For the future though, if you ever just need a small file I just added a Google Drive link with the unzipped ota so that way you won't have to download the whole 1.5GB zip
Click to expand...
Click to collapse
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA

erfanoabdi said:
No problem bro
Thanks
But let me tell you you can't just patch updater-script to make it working on any unlocked devices.
As I see and tested on this zip file, Motorola OTA is working with system.patch.dat which means you have to find head system.img and patch this OTA file on it, I mean all files on this zip is only patchable on "mcls24.246-36-3" system firmware
So you(we) have to patch them on device and make backup of system partition and use it to flash via fastboot or emulate this progress some where else (other rooted device or Android emulator)
So far
I got mcls24.246-36-3 firmware and flashed on my device (everything looks fine)
And I started flashing system.patch.dat and system.new.dat on it but no success
I can verify system patch (very good) but I can't patch it
It seems this is bug of the TWRP I'm going to build google stock recovery without verification check and tell you result's.
I'll upload my works maybe it's useful
main firmware : https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
my zip : https://drive.google.com/open?id=0B3HUyyOqyhD1N3FfQ2YyREhvdDA (waiting for system.patch.dat)
Click to expand...
Click to collapse
Ok awesome, as for the updater-script, I didn't think that'd work but I thought maybe it could be a start. I'm still kinda new to this tbh. Thanks for the info though, it'll help me get better with this kind of stuff. I'm very skilled in Linux but Android is kinda different so it's a bit of a learning curve lol.

nice
papampi said:
Awesome, Thanks a lot.
Click to expand...
Click to collapse
thank you

Installation Guide Added on OP, Please test it

Related

[guide] root for stock lolipop roms without downgrading to kitkat

This guide worked for me. I am using v20i stock rom without any modification. I saw this on web and i want to share it. If you use this guide, it is on your own risk (such as mine)
We will have a rooted lolipop rom without downgrading to any kitkat rom. We dont need to flash bumped twrp for this.
This guide describes for windows users but same method can work with linux. Linux users know how
1- Download this file.
2- Copy zip file to your C:\ hard drive and extract there. It should be like this: C:\g3-root
3- Enter your phone's settings and activate the developer settings (with clicking build number 5-6 times)
4- Enter developer settings and activate usb debbuging
5- Enter the file g3-root and press and hold the shift button on your keyboard and right click with mouse. Select "open command window" or something like this (i am not using english windows)...
6- Connect the phone to your pc with usb cable.
7- Dont let the screen off. If your phone asks you about usb debbuging (trusting the computer), select "remember this" and click "yes"
8- now test the connection... write this into the command window
Code:
adb devices
if you can see your device's serial number, you can start now. If not, check the adb and windows drivers and try it again.
9- push the files which are needed for root with this commands
Code:
adb push g2_root.sh /data/local/tmp/
and
Code:
adb push busybox /data/local/tmp/
and
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
10- Now we will enter download mode of our phone. For this, discoonnect the usb cable, shut down the phone, press and hold the volume up button and connect the phone.
You will see "downloading" on your screen.
11- Now return the command window. Look your computer and verify which port of windows that the phone is connected . Mine is COM6 and i will go on with this way. You must change this with yours(COM1 COM2 COM3 COM4.... etc) . Enter this command (for COM6)
Code:
Send_Command.exe \\.\COM6
12- Next send this command:
Code:
ls
if you see the folders, everything is fine and you can continue.
13- finally we send last command and gonna be rooted
Code:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You can see these lines if rooting is successfull
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Click to expand...
Click to collapse
if not, read and try again.
Now reboot your phone and you can see the supersu app in your application drawer
Good Luck!
I am not responsible of any damage to your phone.
I saw this guide in: http://forum.donanimhaber.com/m_103553600/tm.htm
But the main guide is : blog.lvu.kr/g2-lollipop-%EC%88%9C%EC%A0%95-%EB%A3%A8%ED%8C%85/
credits: these guides

Root is working but the problem is TWRP because is not working its giving error so no flashing other custom rom or mods for now.

Yes root is working fine. I didnt tried twrp or cwm. With this guide, you can use stock odexed and unmodified lolipop rom.

hi guys
New Root Method for LG Devices lollipop
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772

jojobans said:
hi guys
New Root Method for LG Devices lollipop
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Click to expand...
Click to collapse
Same method
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi

agritux said:
Same method
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
evet arkadash

Muhahahah
LG-D855 cihazımdan Tapatalk kullanılarak gönderildi

agritux said:
This guide worked for me. I am using v20i stock rom without any modification. I saw this on web and i want to share it. If you use this guide, it is on your own risk (such as mine)
We will have a rooted lolipop rom without downgrading to any kitkat rom. We dont need to flash bumped twrp for this.
This guide describes for windows users but same method can work with linux. Linux users know how
1- Download this file.
2- Copy zip file to your C:\ hard drive and extract there. It should be like this: C:\g3-root
3- Enter your phone's settings and activate the developer settings (with clicking build number 5-6 times)
4- Enter developer settings and activate usb debbuging
5- Enter the file g3-root and press and hold the shift button on your keyboard and right click with mouse. Select "open command window" or something like this (i am not using english windows)...
6- Connect the phone to your pc with usb cable.
7- Dont let the screen off. If your phone asks you about usb debbuging (trusting the computer), select "remember this" and click "yes"
8- now test the connection... write this into the command window
Code:
adb devices
if you can see your device's serial number, you can start now. If not, check the adb and windows drivers and try it again.
9- push the files which are needed for root with this commands
Code:
adb push g2_root.sh /data/local/tmp/
and
Code:
adb push busybox /data/local/tmp/
and
Code:
adb push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
10- Now we will enter download mode of our phone. For this, discoonnect the usb cable, shut down the phone, press and hold the volume up button and connect the phone.
You will see "downloading" on your screen.
11- Now return the command window. Look your computer and verify which port of windows that the phone is connected . Mine is COM6 and i will go on with this way. You must change this with yours(COM1 COM2 COM3 COM4.... etc) . Enter this command (for COM6)
Code:
Send_Command.exe \\.\COM6
12- Next send this command:
Code:
ls
if you see the folders, everything is fine and you can continue.
13- finally we send last command and gonna be rooted
Code:
sh /data/local/tmp/g2_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
You can see these lines if rooting is successfull
if not, read and try again.
Now reboot your phone and you can see the supersu app in your application drawer
Good Luck!
I am not responsible of any damage to your phone.
I saw this guide in: http://forum.donanimhaber.com/m_103553600/tm.htm
But the main guide is : blog.lvu.kr/g2-lollipop-%EC%88%9C%EC%A0%95-%EB%A3%A8%ED%8C%85/
credits: these guides
Click to expand...
Click to collapse
Finally YES!!! thank you so mu ch. Will try later.

Root plus Custom Recovery, or Root Only?
Hi,
This is interesting and looks a lot easier than the guide I just put up over the weekend: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845.
But I wanted to confirm first, this is purely for rooting only, correct? In other words, if I follow only the steps in this guide I will have root...but I will not be able to install a custom recovery (like TWRP) (same as this thread: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772)?
EDIT: nevermind, one user of the other thread confirmed my question already: http://forum.xda-developers.com/showpost.php?p=59325441&postcount=55. So indeed, this method is for root only, because this method starts with a fully-flashed Lollipop firmware (inclusive of Lollipop version boot stack - aboot.img, sbl1.img, rpm.img, tz.img, etc.).

topet2k12001 said:
Hi,
This is interesting and looks a lot easier than the guide I just put up over the weekend: http://forum.xda-developers.com/lg-g3/general/guide-update-to-lollipop-root-bumpd-twrp-t3048845.
But I wanted to confirm first, this is purely for rooting only, correct? In other words, if I follow only the steps in this guide I will have root...but I will not be able to install a custom recovery (like TWRP) (same as this thread: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772)?
EDIT: nevermind, the OP of the other thread confirmed my question already: http://forum.xda-developers.com/showpost.php?p=59325441&postcount=55. So indeed, this method is for root only, because this method starts with a fully-flashed Lollipop firmware (inclusive of Lollipop version boot stack - aboot.img, sbl1.img, rpm.img, tz.img, etc.).
Click to expand...
Click to collapse
This is a way for rooting from lollipop, and access to fastboot too.
For custom recovery, it needd bump ! , and bump works only with KK bootloader. So for having a custom recovery, we need to downgrade BL first, and inject Bumped recovery + bumped kernel after.
And if we downgrade BL, maybe we need downgrade complete bootstack too (sbl,rpm,tz,dbi,laf) ?

Just to make sure, this works for v20i only or does it work for, say, my v20h too?

6ril1 said:
This is a way for rooting from lollipop, and access to fastboot too.
For custom recovery, it needd bump ! , and bump works only with KK bootloader. So for having a custom recovery, we need to downgrade BL first, and inject Bumped recovery + bumped kernel after.
And if we downgrade BL, maybe we need downgrade complete bootstack too (sbl,rpm,tz,dbi,laf) ?
Click to expand...
Click to collapse
Yup yup, I got it. Thanks. Just wanted to confirm.
Yes, I'm aware also of fastboot ability. Basically, dd if=/dev/zero means "writing zeroes" to whatever partition (in the case of the guide, it's the "laf" partition where "Download Mode" is stored). So, zeroing out the "laf" partition will make the device fall back to standard fastboot - except for the Verizon variant. I think you can do that regardless if you are in Kitkat or Lollipop, since the process is mere deletion of a partition's contents to "force" the device to fall back to fastboot.
Yes, you need to downgrade the entire boot stack. Basically, all partitions will need to stay at "Kitkat" version, and then manually flash ONLY system.img, boot.img, and modem.img (just like the one in my guide). And then, "bump" the boot.img so that you can install a custom recovery. I wrote that in my how-to guide as well.
In my case, I feel uncomfortable not having a custom recovery. I tinker around with my device a lot and have "bricked" it a lot of times but was saved because I have a backup via custom recovery.
I would suggest making it clear that this is for root only (meaning, does not include custom recovery). Very important, because I have seen threads from other users where they got bricked and can no longer restore at all - too bad because they did not have a custom recovery backup.

topet2k12001 said:
Yup yup, I got it. Thanks. Just wanted to confirm.
Yes, I'm aware also of fastboot ability. Basically, dd if=/dev/zero means "writing zeroes" to whatever partition (in the case of the guide, it's the "laf" partition where "Download Mode" is stored). So, zeroing out the "laf" partition will make the device fall back to standard fastboot - except for the Verizon variant. I think you can do that regardless if you are in Kitkat or Lollipop, since the process is mere deletion of a partition's contents to "force" the device to fall back to fastboot.
Yes, you need to downgrade the entire boot stack. Basically, all partitions will need to stay at "Kitkat" version, and then manually flash ONLY system.img, boot.img, and modem.img (just like the one in my guide). And then, "bump" the boot.img so that you can install a custom recovery. I wrote that in my how-to guide as well.
In my case, I feel uncomfortable not having a custom recovery. I tinker around with my device a lot and have "bricked" it a lot of times but was saved because I have a backup via custom recovery.
I would suggest making it clear that this is for root only (meaning, does not include custom recovery). Very important, because I have seen threads from other users where they got bricked and can no longer restore at all - too bad because they did not have a custom recovery backup.
Click to expand...
Click to collapse
@robalm writes in his OP, he uses LP rpm and tz (and cust) in his flashables 20x original fw flzshable zip (i've not verified it was the case)
http://forum.xda-developers.com/showthread.php?p=57223144

6ril1 said:
@robalm writes in his OP, he uses LP rpm and tz (and cust) in his rom (i've not verified it was the case)
http://forum.xda-developers.com/showthread.php?p=57223144
Click to expand...
Click to collapse
Yes, however that is a repackaged firmware (extract everything, root it, and then "bump" the necessary components, and then put it back together as a single flashable zip). That is why it will have root plus "bump" (bump'd boot.img and recovery.img a.k.a. custom recovery). Therefore, those who will download it will no longer have to root it manually. This guide (and mine) are different from repackaged firmwares, in the sense that we are not "pre-rooting" (or "pre-bumping") the firmware. We are rooting (or "bumping") the firmware after installation.

topet2k12001 said:
Yes, however that is a repackaged firmware. That is why it will have root plus "bump" (bump'd boot.img and recovery.img a.k.a. custom recovery). Therefore, those who will download it will no longer have to root it manually. Your guide (and mine) are different from repackaged firmwares, in the sense that we are not "pre-rooting" (or "pre-bumping") the firmware. We are rooting (or "bumping") the firmware after installation.
Click to expand...
Click to collapse
Yes, it seems it's a little different than @autoprime and you propose and i was asking myself if these three partitions were realy needed in this case (flashable zip from kdz exracted) or not.
I should prefer to let them in the bootstack version but maybe i'm xrong.

6ril1 said:
Yes, it seems it's a little different than @autoprime and you propose and i was asking myself if these three partitions were realy needed in this case (flashable zip from kdz exracted) or not.
I should prefer to let them in the bootstack version but maybe i'm xrong.
Click to expand...
Click to collapse
Ah, sorry I misunderstood what you were saying.
I do not know what rpm.img and tz.zip are for. I did read somewhere in XDA that tz.img is for the "radio" (or transmitter?). But I would suggest to keep those files (tz.img, rpm.img, aboot.img, sbl1.img) at "Kitkat version" because there will be a signature mismatch resulting to "certificate verify" or "security error" - if people want to have a custom recovery.
If people will NOT install a custom recovery (they just want root) then they can use this guide. The device will boot fine without the error messages, since recovery.img is Lollipop non-"bump'd" version (so the signatures match).

It should be possible to make a script that flash kk bootstack, bumped recovery and bumped kernel in a one click process, for a LP rooted.

6ril1 said:
It should be possible to make a script that flash kk bootstack, bumped recovery and bumped kernel in a one click process, for a LP rooted.
Click to expand...
Click to collapse
Yes, that's another way of approaching it. Or maybe create a flashable zip from it. But we will still need to instruct users to extract their Kitkat Image files (I don't think all Image partitions are the same for all variants), that's why I find the manual method (like @autoprime) to be a good approach because I personally find it to be more "universal".
One example: the D858HK does not have cust.img.
So for us to create an all-in-one script, zip, or approach, it would be difficult because of the many variants of the LG G3. Maybe if there were not that many variants, I'm sure skilled people like you can have a universal and convenient solution. For now, I still think that manual flashing is more universal.

topet2k12001 said:
Yes, that's another way of approaching it.
Click to expand...
Click to collapse
; -)
Tz trustzone,rpm ressource power managment, sbl secondary bootloader
https://wiki.linaro.org/Boards/IFC6410

6ril1 said:
; -)
Tz trustzone,rpm ressource power managment, sbl secondary bootloader
https://wiki.linaro.org/Boards/IFC6410
Click to expand...
Click to collapse
So that explains why even if the Lollipop versions are included/flashed, they won't cause an issue of signature mismatch. The Image file that causes a signature mismatch when you flash a "bump'd" file is aboot.img (the Android Bootloader). Which explains also in my experiment (prior to discovering it all and creating a thread) why I was initially able to "fix" my issue, following @autoprime's tutorial, when I flashed aboot.img - however, in exchange I lost "bump" status.
So basically, people will need to flash their Kitkat version of aboot.img and "bump" will still work (and will have custom recovery). That is our hypothesis at this point.
This reminds me: in my how-to guide, there was a user complaining about fast battery drain. Maybe if I advise him to flash the Lollipop version of rpm.img, that would help alleviate the issue. I will do an experiment and if this will succeed, I will update my how-to guide. In your case, for this thread's purpose, you may also do an experiment and create scripts.
Nice teamwork.
I don't know what "trustzone" is though. Will it affect signature mismatches? sbl1.img and rpm.img seem to be self-explanatory.
EDIT:
As mentioned previously, it is very dangerous to flash any of the restricted boot partitions such as sbl1, sbl2, sbl3, aboot or rpm. However it is safe to flash any other partition in order to install custom Linux builds and run them.
Click to expand...
Click to collapse
...do we really want people to touch this?

[RECOVERY][YotaPhone2][Lollipop][ROOT]Modified YotaPhone 2 Stock Recovery for ROOT

YotaPhone 2 ROOT with modified stock recovery
NOTE:
Check out the more functional TWRP recovery for YotaPhone 2.
Since not much dev work is happening on the YotaPhone 2, I though I'd kick off by publishing a recovery image that will hopefully allow you to root your YotaPhone 2 device with lollipop, and e.g. make partition backups.
First off: Disclaimer!
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device, and you are likely to void your warranty by doing so. You might even damage or brick your device, so ask yourself if the benefits outweigh the risks, because after proceeding you are pretty much on your own.
What is it?
It's a slightly modified stock recovery that allows to install packages signed with testkeys, plus adb root access and busybox for e.g. shell. That's it.
What can you do with it?
- adb root & shell access (e.g. to manually backup partitions or modify system files)
- install update zips signed with testkeys (e.g. SuperSU) in addition to original Yota Devices software
- root your device
What can it NOT do?
- probably can NOT install unsigned zips (must be signed by YD (like fota update zips), OR signed with standard testkeys)
- no fancy features, just boring AOSP stock recovery as included in stock firmware
- installing of apks/zips only through adb sideload, not from (emulated) SD card
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0, I used firmware 1.39 YMMV with other versions
- Some technical confidence
- USB cable with a PC or laptop on one end
Steps overview:
1) First read the whole post to understand what's going to happen
2) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
3) Unlock the bootloader
4) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
5) Download recovery image: yd201_reco_139_testkeys_v01.img
6) boot the recovery image
7) root the device by sideloading SuperSU,
Unlocking bootloader:
Warning 1: It is currently not known how to re-lock the bootloader. (fastboot oem lock just hangs). This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
Warning 2: on some devices unlocking the bootloader wipes the device clean to factory defaults. I didn't see this happening on my YD201, but be warned, backup first!
On Linux:
Code:
sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
On Windows:
Code:
C:\android-sdk-windows\platform-tools>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
Maybe Windows will install some extra drivers in the process.
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
method 1: Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
method 2: do a
Code:
adb reboot bootloader
You should see a black screen with a tiny white: downloading...
b) boot the recovery image:
On linux:
Code:
sdk/platform-tools$ sudo ./fastboot devices
Should show a connected device in fastboot mode, then proceed:
Code:
sdk/platform-tools$ sudo ./fastboot boot <path>/<to>/yd201_reco_139_testkeys_v01.img
Where <path>/<to>/yd201_reco_139_testkeys_v01.img is the path you downloaded the image file to (e.g. ~/Download/yd201_reco_139_testkeys_v01.img)
On Windows:
copy the yd201_reco_139_testkeys_v01.img file to the folder with fastboot.exe (here assuming C:\android-sdk-windows\platform-tools, and D:\downloads as download location for the img)
* snippet below is fabricated, but you get the idea
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot.exe devices
Should show a connected device in fastboot mode, then proceed:
Code:
C:\android-sdk-windows\platform-tools>copy D:\downloads\yd201_reco_139_testkeys_v01.img . [i]note the dot at the end[/i
C:\android-sdk-windows\platform-tools>fastboot.exe boot yd201_reco_139_testkeys_v01.img
Hopefully you see the screen go completely black after a few seconds, and recovery menu will appear. Like stock recovery, it will show an error (E:Cannot load volume /misc) but you can ignore that, along with the 'error' triangle icon that goes with it.
If booting fails with a signature error, the bootloader is probably not properly unlocked, try again.
Note that this recovery image could be flashed too (I haven't actually tried to flash yet), but if you're cautious (as we are in this post) you can just boot it every time you need it.
SuperSU flashing:
1) download Chainfire's SuperSU flashable zip from this page, filename is:UPDATE-SuperSU-v2.46.zip
2) Assuming you're still in custom recovery, otherwise boot into custom recovery again as outlined above
3) choose "apply update from ADB" from the menu (choose with volume up/down keys, confirm with power key). Recovery now waits for a file.
4) on the connected PC:
on Linux:
Code:
sdk/platform-tools$ adb sideload <path>/<to>/UPDATE-SuperSU-v2.46.zip
on Windows:
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>copy D:\downloads\UPDATE-SuperSU-v2.46.zip .
C:\android-sdk-windows\platform-tools>adb.exe sideload UPDATE-SuperSU-v2.46.zip
5) on the phone you should see SuperSU installing.
6) reboot when done
7) if SuperSU app is not visible in launcher, download & install SuperSU from playstore.
To verify if rooting worked, start SuperSU. If that looks OK, start an app that requires root (like e.g. betterbatterystats) or use a simple checkroot app from the store. Reboot and check again if it persisted.
NOTE: you could also FLASH this image, replacing the stock recovery on the recovery partition permanently (until you flash again). Above we're just BOOTing it once, next time entering recovery in the standard way will just load the stock recovery from the recovery partition). You would use fastboot flash instead of fastboot boot above. Flashing is UNTESTED.
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly.
Q: I don't know how to <backup/adb/download/reboot/flash>
A: Please use the search button, xda forums have lots of info
Q: How can I tell if I'm in stock recovery or modded stock recovery? They look the same!
A: The Droid error icon with the triangle in the centre of the modded recovery screen has some white text (yd201_cr0.1), the stock one doesn't.
Future development
I hope that there are some devs out there willing to work on the YotaPhone 2 in the near future. I'll try to tinker a bit every now and then, but I cannot promise anything as I'm no expert. To enable proper development of custom ROMs and better recoveries (e.g. TWRP) it would be great if Yota Devices released their Kernel sourcecode for the kernel they use in their YotaPhone 2 ROMs. I know they have been asked to release sources before (and they should in order to comply with the GPL license), but so far without response.
Good news is that You Can Help! Please stimulate Yota to publish Kernel sourcecode for YotaPhone 2 through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info::
Mod by: SteadyQuad
Version: 0.1 based on YD stock recovery 5.0 1.39 EU
Thanks to: Yota Devices for a great device, Jeopardy for testing and suggestions, Chainfire for SuperSU
Created: 2015-06-10
Last Updated: 2015-06-20 (added warning about current inability to re-lock bootloader)

As SteadyQuad already mentioned, I can confirm that this method works.
Bye bye Google Newsstand! Goodbye Google Books!
(When uninstalling system apps Lollipop handles a bit differently from Kitkat, and I had to always restart the device after deleting.)
Thank you very much for your effort SteadyQuad.

Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!

zencooler said:
Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!
Click to expand...
Click to collapse
I haven't tried testing xposed yet, but am planning to sooner or later.
Running that custom recovery we do have root level access to everything, so it should be possible to create a backup from there with the help of a computer. Have to look into this.

the recovery download doesn't work.
EDIT : it worked on laptop
How about somebody can compile a TWRP recovery because Yotaphone has posted there SDK ?
So we can make Nandroid backup.

a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it

Gojira-r32 said:
a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it
Click to expand...
Click to collapse
I think if we all contribute to twrp and request them they might make us one
Sent from my YD201 using Tapatalk

Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk

Yes
Fastboot oem lock

Gojira-r32 said:
Yes
Fastboot oem lock
Click to expand...
Click to collapse
If the recovery image is modified don't we flash back to stock before oem lock
Sent from my YD201 using Tapatalk

Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app

dai75 said:
Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app
Click to expand...
Click to collapse
Xposed framework isn't FULLY compatible, but many features already work. See SteadyQuad's thread here

adamo86 said:
Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
I haven't been able to re-lock it when I last tried (fastboot oem lock just hung). If anyone did succeed to lock, let us know! (Gojira-r32: did you actually execute the fastboot oem lock?)

I also failed to lock it back . I wanted to install the new update 1.44 that arrive in France but it failed at the recovery stage. E:Error in cache/update/yota....zip (status 7)
I did a wipe cache partition but not a wipe data as I don't want to lose all my settings. Anyone achieved to install the new Yota update version? And then root?

I just updated to latest update in UK. But I tried Kingo no success still.
Sent from my YD201 using Tapatalk

and the first post with flashing S%U tru modified recovery ?
is this firmware somewhere to download?
still not yet on yota FTP

Has anyone the stock recovery image? Maybe I'll achieve to get the OTA update after unrooting my YD201 with the original stock recovery firmware.

i am doing that right now, unroot, flash stock recovery, i have the OTA 1.1.44 pulled out of phone after download and will try to flash it

stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good

Gojira-r32 said:
stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good
Click to expand...
Click to collapse
Did you try to flash the OTA update via adb sideload in the modified recovery? I'm having the same problem.
Edit: I just tried to flash the update via adb sideload - no joy. I got the following error:
Package expects build fingerprint of YotaPhone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.39:user/release-keys or Yotaphone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.44:user/release-keys; this device has Yotaphone/yotaphone2/yotaphone:5.0/LRX21M/5.0
E:Error in /sideload/package.zip
(Status 7)
I also tried resigning the package with testkeys, but that didn't work either. Same error. So something has changed in the rooting process, because some people in the forum have managed to update normally, presumably on their nonrooted devices.

Lineage OS 13 Port for BLU_Studio_XL_2

:good:
I have cm13 ported over from different Phone (Blu Life_Max) and booting.
already working
1. wifi
2. camera but not video camera
3. bluetooth audio
4. loud speaker audio
5. FM Radio
6. cell in sim1 and sim2 slot, but sim2 only gets H+ speed(5-10Mbps)
SIm1 gets 4G(LTE) speeds on test 50Mbps Both tests with freedomPop
known issue (mostly camera related)
1. videocamera causes camera crash
2. selfie-camera not available **Fixed with V6**
3. panarama shot crashes camera
4. NFC not able to turn on (stock rom did not have NFC, so this may not be possible to work) : next update may remove this **fixed in V5**
V7 -- Hassome permission changes in boot.img that were found in logcat, for "SMI"
still not working videocamera
To install:
1. Must be bootloader unlocked
.
How to Unlock Bootloader via Fastboot
1. Setup ADB and Fastboot on your PC.
2. Enable USB debugging and OEM Unlock on your Android device.
3. Connect your device to the PC with a USB cable.
4. Open a command window on your PC.
5. Boot your device into bootloader mode using the following command:
Code:
adb reboot bootloader
└ You may get a request to authorize USB debugging on the device, accept it.
6. Once your device is in bootloader mode, issue the following command to unlock bootloader:
Code:
fastboot oem unlock
You get a confirmation screen on your device. Press Volume Up button to highlight Yes and press Power button to select it.
This will begin bootloader unlocking process, which shouldn’t last more than couple of minutes.
7. Once bootloader is unlocked, your device will reboot into bootloader mode. You need to boot it into system now using the command below:
Code:
fastboot reboot
During reboot, your device will go through a factory reset and then finally boot into system.
2. Install included twrp(New kernel for recovery allows touchscreen to work)
***PRIOR RELEASES NEED TO USE LOPESTOM RECOVERY TO INSTALL***
Due to different moint point descriptions Future versions(If they come) will use block number moints to be compatible with both
******V-7-Block is compatible with both recoveries
1. make sure developer options is enabled
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Test recovery works for your device
(example commands assume you have the vampirefo version of recovery downloaded to the desktop)
Code:
Fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
4. If recovery boots good, then return to bootloader and flash (commands work from in booted twrp)
These steps are what I find to be best order to prevent the stock rom from replacing the stock recovery on boot.
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
3. If first install. do wipe and wipe system too. If Updating no wipe needed
Sources:
Rom not built for this device Built for Blu Life-Max --no thread to link, sorry
Rom uses the stock kernel, pulled from oem device (studio_XL_2)
keeping a git of files swapped to make rom work
https://github.com/mrmazakblu/BLU_Studio-XL-2_port_from_Life-Max
kernel source for recovery:
https://github.com/mrmazakblu/Blu_studio-XL_2_kernel_source
Other projects for Studio_XL_2:
Reserrection Remix Port
XDA:DevDB Information
blu-studio-xl-2, ROM for all devices (see above for details)
Contributors
mrmazak, Thanks to vampirefo --building donor rom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: BLU-Studio-XL-2--BLU_S0270UU_V09_GENERIC
Based On: Lineage OS
Version Information
Status: Testing
Created 2017-10-30
Last Updated 2017-11-30

New TWPR kernel
Reserved

TWRP touchscreen
new kernel for TWRP allows touchscreen to work when recovery is flashed to device.
thanks to @vampirefo for finding a fix for Life-Max. Same fix worked here too.
New kernel is also put into @lopestom twrp.
Choose either one they both work.

Thanks for porting. I'm looking forward to testing it with my Studio XL2

killer13666 said:
I tried flashing it like you said and this is what happened....
Code:
Installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Update binary zip
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
Target: Blu Studio XL 2
Target: Blu Studio XL 2Check if system is already mounted
Check if system is already mountedcould not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directorymount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system at /system: No such file or directoryRunning backup script for update installsabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
Running backup script for update installs
run_program: child exited with status 127
unmount of /system failed; no such volumeChecking if Data is compatableunmount of /system failed; no such volume
Checking if Data is compatable
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 14 second(s).
Error installing zip file '/external_sd/BLU_Studio-XL-2_port_from_Life-Max-V-7.zip'
Updating partition details...
Click to expand...
Click to collapse
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.

mrmazak said:
Do not know why you have failed to mount /system error could be because you have /system set to be read only.
In install directions it says need to wipe /data
and
also advanvance wipe /system
second error says imcompatable /data == this means you did not wipe data before installing.
Please continue here in the rom thread.
Click to expand...
Click to collapse
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly

killer13666 said:
I figured out what the problem was. For some reason, the recovery image you supplied wasn't mounting the system partition properly. I used a different image and the ROM flashed perfectly
Click to expand...
Click to collapse
please let me know which one worked for you and which one did not.
I think I was using the one marked 3.1.1 (vampirefo) but now I am not sure.
I may do independet testing again on both, but would appreciate your input.
Just confirmed there is a problem with the combination of the update-binary used in these install zips and the vampirefo recovery. The fix can be either i use different update-binary file or you use lopestom recovery.
**EDIT**
Problem was with the my updateer-script. I put fixed install packages up.

Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow

ahnuts72 said:
Thanks for the port my version is v06.0.04.00_generic 16/06/2017
I have a unlocked phone from best buy
I keep seeing everyone say v09 mine has updated twice wondering if it will work on mine or if I need to update somehow
Click to expand...
Click to collapse
I dont see any version of my stock OS that is similar to that number you have.
When I had stock installed, In the settings screen, about phone listed the build version as
Code:
BLU_S0270UU_V09_GENERIC
This port is for Blu_Studio_XL_2 make sure that is device you have.
If you look in the build.prop you will get more information about the device.
if you want to , you can pull the build.prop and post it , so I can see
Code:
adb pull /system/build.prop Desktop\build-prop.txt
then attach the file here.

According to the device in about phone mine is studio xl 2 and that was what the box said when I purchased the phone at best buy

And this one shows the version

And this one shows the version

Wrong pic

ahnuts72 said:
Wrong pic
Click to expand...
Click to collapse
The dates show it is a newer software than what I had, but this should still work, as long as you are still able to unlock the bootloader.

In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb

ahnuts72 said:
In the developer options I have a setting that says oem unlocking allow the bootloader to be unlocked will that work or will I have to still do it from adb
Click to expand...
Click to collapse
here is guide.
https://www.theandroidsoul.com/unlock-bootloader-via-fastboot-android/
the unlocking does do a complete wpe on the data part of the phone. so if you have pictures or music or any files you want to keep , make sure to copy first. Also to be safe , if you have external sdcard in , take it out before doing unlock
****
****
Must complete the unlock as the guide shows includeing the reboot, so stock recovery does its wipe, I t is important part of the unlock.
**
**
after unlocked,
to flash recovery, enable developer options again, enable usb debugging. authorize adb connection to your pc-
Code:
adb reboot bootloader
fastboot boot recovery.img
**recovery.img = "full path to the downloaded recovery"
**example if you downloaded the vampire based recovery and you downloaded to the desktop**
Code:
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
after booted to recovery and it works return to bootloader and flash it to phone. I allways recomend this boot first method to verify it recovery works. You cant be certain every od will work on every device. Better safe than sorry.
select reboot menu from recovery and then select reboot bootloader.
Due to a securety measure android has (recovery-from-boot) when replacing recvoery to need to boot directly to new recovery to prevent the android system from replacing it with stock version. so I use the steps below
Code:
fastboot flash recovery Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
fastboot boot Desktop/recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img
adb wait-for-device
adb reboot recovery
.

Android 6 or 7, plus install questions
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!

Donphillipe said:
Hi, I have rooted several phones but the procedure keeps getting more difficult. I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image .... will it be rooted and if so, what version of Android is bundled? Will the phone then support Xposed and Xprivacy?
From what I can determine, the video camera is not working with your most recent release, V8, is this correct?
Thank you for your assistance!
Click to expand...
Click to collapse
LineageOS 13 is android 6
there is no V8 only upto V7
video recording does not work
Lineage has root built in. Enable it in developer options
I do not know about xposed I not use it
Donphillipe said:
" I see the instructions for installing recovery-TWRP-3.1.1-Vampirefo-studio-xl-2.img but I am curious what is on this image "
Click to expand...
Click to collapse
That image is TWRP recovery only
I have not been working on this anymore.
I have ported "better" Resurection rom based on android 7 , have been using it as a daily use phone for just over a month now
https://forum.xda-developers.com/android/development/-t3699638

I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!

Donphillipe said:
I appreciate your patience with someone who only dabbles in this hobby. When you say that the install image is TWRP only, what exactly does this mean?
I know I have owned several BLU phones and each time I tried to install a high-end recovery tool in the past, the list of supported phones on the recovery software list would never include my BLU device, saying something to the order of the source needing to be recompiled (as I recall) or something to that order which never seemed to happen. So are there additional steps for getting the phone to the point it will take this image other than the steps you outlined for unlocking the boot loader? Or what do I need to be aware of?
Also, do you have a backup of the factory image available in case something goes wrong, with basic instructions on how to recover the phone back to the factory version? Or is there something I can install or do on this phone to create a backup copy on my own?
Again I am sorry to have to ask for what to some appears a simple procedure. I do appreciate your going to the effort when you have already contributed so much with your images. Thank you!
Click to expand...
Click to collapse
The recovery image (TWRP) works for this device.
Yes recovery images, just like android roms are specific to each different device. This one has been edited to work for Studio XL 2
The TWRP is a custum recovery needed to install the custom ROM
The steps are complete, you shouldn't need anything else (need adb and fastboot)
Yes stock recovery image is available. Installing back to stock recovery is same steps as installing custom recovery.
both can be done as described with fastboot. Or both can be installed using SPFT (smart phone flash tool)

[GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye)

Introduction
Hello everyone, this is a guide to assist you with customizing your Pixel 2! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to root. Please feel free to ask any questions if you need clarification. Enjoy!
This information has been distilled from Google's official factory image site and the Magisk thread.
Installing fastboot and adb
Thankfully, Google has provided just adb, fastboot, and systrace as a simple zip file, making this process super easy. You MUST be on at LEAST 26.0.2 for the commands in this guide to work. When in doubt, grab the latest copy and install them using the following instructions.
SDK Platform-Tools for Windows
SDK Platform-Tools for Mac
SDK Platform-Tools for Linux
Windows:
Unzip the folder somewhere on your hard drive.
Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt.
Type the following commands:
Code:
adb --version
fastboot --version
You should see some information appear. If that is the case, you were successful!
Mac/Linux:
Unzip the folder somewhere on your hard drive.
Navigate to that folder with your terminal.
Run the following commands:
Code:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Type the following commands:
Code:
adb --version
fastboot --version
You should see the version information, along with telling you they are installed to /usr/local/bin. If so, you were successful!
Unlocking the bootloader
WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.
On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
In your terminal, type the following command:
Code:
adb reboot bootloader
Run the following command:
Code:
fastboot flashing unlock
Follow the prompts on your device then reboot!
Flashing factory images
NOTE #1: You CANNOT downgrade factory images. Google has prevented users from doing so to keep them safe from vulernabilities that were patched. You should only upgrade or reinstall the current image.
NOTE #2: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.
NOTE #3: Flashing the factory images requires an unlocked bootloader. Flashing the OTA zips does not (but if anything goes wrong, you may not be able to recover without an RMA).
Updating to a new release (factory image):
Download the latest factory image from Google's website.
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.
If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.
Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Updating to a new release (OTA zip):
Download the latest OTA zip from Google's website
Reboot into recovery:
Code:
adb reboot recovery
Hold down the power button and push volume up
Select "Apply update from ADB"
Run the following command from the folder containing the OTA zip:
Code:
adb sideload <zip_name>.zip
Reboot once it is finished!
Clean flashing a factory image (wipe everything):
Download the latest factory image from Google's website
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Installing TWRP
NOTE #5: If you just want to temporarily boot TWRP to flash Magisk and your custom kernel, you can just skip flashing the installer zip in this process.
NOTE #6: TWRP can be unstable at times given the way that security has been set up on this device (lack of decryption, failing to boot, etc).
Download both the TWRP image and zip installer from the official site.
Temporarily boot the TWRP image.
Code:
fastboot boot <path_to_twrp_image>
Flash the TWRP installer zip.
Reinstall Magisk and your custom kernel if you had them.
Reboot and profit!
Common issues
Outdated fastboot/adb: This device requires the latest fastboot and adb binaries to work properly. A lot of common quick adb/fastboot installation guides link to installers that are old. Please manually install the latest using the information at the beginning of the thread!
Using a USB-3.0 or USB-C port: Some newer USB ports do not work with fastboot. Issues manifest as weird errors during a flash. Use a different USB cable/port.
Closing statements
If there are any procedures you would like to see added (like flashing a custom kernel or booting TWRP), I am happy to add them if requested. Also, when requesting help, please be as specific as possible where you get confused. I want this guide to be clear as possible.

Reserved

Reserved

Stuck on this step
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
How do I navigate in command prompt? When I typed flash-all, it said it is not a internal command etc. When I dragged and dropped flash-all into the command prompt, it said C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES>"C:\Users\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025\flash-all.bat"
error: cannot load 'bootloader-walleye-mw8998-002.0059.00.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
error: cannot load 'radio-walleye-g8998-00122-1708311414.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.015s
W/ ( 6448): Unable to open 'image-walleye-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-walleye-opd1.170816.025.zip': I/O Error
Press any key to exit...

You are calling the flash-all.bat out of a differende directory (C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES) therefore it can't find the system image files since they are located under C:\U sers\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025. Make sure you extract your image to that directory, open up a command promt and navigate to it with "cd C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES" and call the flash-all.bat from there.
Check out this for basic command line stuff https://www.digitalcitizen.life/command-prompt-how-use-basic-commands
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
I tried this and it seems the magisk manager isn't able to download magisk on its own at least on my device:
Code:
DownloadManager: [356] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "forum.xda-developers.com": No address associated with hostname
DownloadManager: [356] Finished with status WAITING_TO_RETRY
EDIT: Seems like DNS66 was blocking the download patching was scucessfull now.
This is weird, can't I make 2 posts in a row??

Anybody figure out a solution for flashing when on MacOs High Sierra? Platform tools 26.0 1 was a fix for high Sierra, yet 26.0.2 seemed to have lost that commit, so fastboot doesn't work at all. Wondering if it's safe to use 26.0.1 on the pixel 2

nathanchance said:
Flashing factory images
Click to expand...
Click to collapse
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!

JayBlack_686 said:
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!
Click to expand...
Click to collapse
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

nathanchance said:
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.

JayBlack_686 said:
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.
Click to expand...
Click to collapse
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs

OTA vs factory image
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!

Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help

tango650 said:
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!
Click to expand...
Click to collapse
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
UpGrad3 said:
Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help
Click to expand...
Click to collapse
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.

Thanks @nathanchance for this. I'm not a technical person, but can follow directions. This is the 4th phone that I've rooted following directions of some very smart and talented people here on XDA. I don't do this kind of thing everyday, and am not up on programming or coding or whatever you guys call it now days.
All I ended up doing is taking the OTA from Google to the .025. Then followed the Magisk rooting instructions to get root. I had Unlocked it the first day I turned the phone on, I haven't put my SIM in yet, but will play around with it a little more, and finish setting it up,
Again, thanks for the GUIDE to this Pixel 2 phone.

nathanchance said:
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.
Click to expand...
Click to collapse
That is what i get. I have even flashed the whole factory image to the phone and still get this

@UpGrad3 you need to extract the boot.img out of your zip (walleye-opd1.170816.010-factory-63083164.zip) file and process this one, I'll guess you tried with the whole zip?? Also you can "attach" pictures to the post and not include the full res with the image tags...

@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post

UpGrad3 said:
@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post
Click to expand...
Click to collapse
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
nathanchance said:
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90

@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?

JayBlack_686 said:
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
this is where i was going wrong i was using a file that had bootloader in the name rather than going into the second zip and finding boot
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Click to expand...
Click to collapse
drmason said:
@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?
Click to expand...
Click to collapse
yes i was
although im now stuck on the bootscreen with the G any suggestions ?
Fixed.
incase it happens to anyone else. i restored the factory image again then started the root procedure. im now rooted and fully working

100003562 Onn 10.1 Android 11 (Bootloader Unlock, Magisk Root)

Hey folks I spent some time working on this yesterday (dumping Rom, Patching etc) so I thought I'd share. I am including the files I used to get this work.
This is for 100003562 Walmart Onn Tablet
I can't comment on other Onn models because I don't have any.
If your tablet goes into meltdown mode, I'm not responsible. I'm sharing the process that worked for me.
*These files are from:
*Android 11, Security Update 5AUG21 --> They probably won't work with any other version so I can't answer questions related to using them for that.
I don't recommend you try these on any other model unless you do it at you own risk.
*Strangely enough, this update doesn't have any of the Walmart apps installed or the bottom button on the taskbar. It asks if you want to install them when you are setting up the tablet*
I chose no.
Steps:
1. Enable USB Debugging, (while in Dev Options go to OEM Unlocking a tick that, (don't know if 100% necessary but I did it in my process)
and fire up a CMD or Powershell Window.
2. ADB:
adb devices (to make sure you are connected)
adb reboot bootloader
~boots to bootloader~
3. FASTBOOT
fastboot devices (to make sure you are connected)
(WARNING: the next command will factory reset the tablet)
fastboot flashing unlock
(follow volume key prompt to unlock and then device will reboot and bootloader is unlocked.)
You will see "orange state" as it boots if it worked properly. I don't have any interest in removing this message so you'll have to go elsewhere if you do.
4. Repeat steps 1-2 and get back into bootloader.
FASTBOOT:
fastboot devices
fastboot flash vbmeta <path to vbmeta.img>
fastboot flash boot <path to migisk patched.img>
fastboot reboot
5. Done
Notes:
I use Magisk Manager to do a direct install patch after I get root. (also don't know if 100% necessary, but it makes me feel better)
I'm including the stock boot.img in case you want to create your own patch with Magisk Manager. I used 24.1 (24100)
I'll answer what I can if you run into issues.
Cheers!

Reserved.

hey i was actually just about to go into the rabbit hole of pulling the boot.img, then i saw this. my tablet is stuck on the 5jan21 patch and wont update. could you tell me how you dumped the rom? also did you have to modify the vbmeta file? thanks

Mayday_Channel said:
hey i was actually just about to go into the rabbit hole of pulling the boot.img, then i saw this. my tablet is stuck on the 5jan21 patch and wont update. could you tell me how you dumped the rom? also did you have to modify the vbmeta file? thanks
Click to expand...
Click to collapse
i used sp flash and wwr. you can prob pull the boot.img pretty easily, but if you tried to take an OTA and it got corrupted, that might not work anyway. the vbmeta an empty one. this boot.img is from the most up to date ota which i got yesterday. i ordered a refurb version of this tablet and started messing with it yesterday. i have a copy of the full ROM dump as well. let me know if you need pieces and I can get them to you. you might be able to flash a few of the partitions and get it running again. can you get into fastboot?

which sp flash version? im on the latest 5.2152, every time i try to dump the full rom, it hangs on 0% readback. same with trying the boot.img. what was the full rom length, just to confirm? i got 0x750000000 from wwr

Mayday_Channel said:
which sp flash version? im on the latest 5.2152, every time i try to dump the full rom, it hangs on 0% readback. same with trying the boot.img. what was the full rom length, just to confirm? i got 0x750000000 from wwr
Click to expand...
Click to collapse
I used 5.1524. i had this issue as well and had to update the com port drivers. i used Iobit driver booster for this and it found the right driver. and yes thats the correct length for the one i dumped. i have the full thing on mega if you just want to flash it with sp flash tool.

that would be very nice. please post. thank you

Mayday_Channel said:
that would be very nice. please post. thank you
Click to expand...
Click to collapse
File folder on MEGA
mega.nz

goldensun1893 said:
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
i got rid of userdata and cache to shrink it some.

thanks man

Mayday_Channel said:
thanks man
Click to expand...
Click to collapse
let me know how it works

could i please get the cache & userdata partitions? id like to keep a complete rom for archive. it seems to have flashed ok, but it broke wifi and its still stuck on january 5 patch. oh well, thats why i have 2 of these

ill drop them on there. be warned the userdata.img is something like 28GB. If you have the NV RAM Warning: ERR 0x10, there are a few tuts on here to fix that. Its common with SP Flash and MTK chips.

I think I figured out why it doesn't work. Spft isn't flashing super.img. even if I edit the scatter file to add super.img. I'll do some more trouble shooting at lunch

alright lets goooo. fixed it. just needed to change a few things in the scatter file and change the vbmeta files to img. next ill start experimenting on patching lk.bin to remove the ORANGE STATE text. thanks for the rom dump

NICE! I took a leap of faith and did this on my Oct 5th 2021 Security update build and it appears to have worked and Im rooted with magisk!!! I added a few additional steps to your commands just in case
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched-24100_w97F6.img
fastboot reboot
I found a USB ADB fastboot driver that was signed and worked on my windows 10 x64 system but I had to go through the "Have Disk" manual driver install and installed even though it wasnt supposedly designed for my hardware. So insane the hoops to do this...
MT65XX-USB-VCOM-drivers\MT65XX USB VCOM drivers\Google_USB_Driver_rev4
Had trouble updating to Magisk to 24.3 however, not sure what pitfall I hit.
Wondering if I should be happy with root or try and flash TWRP and try a different ROM.

Iam in need of some help i am not sure if i have to install something to the tablet or pc but when i do the command "fastboot flashing devices" on my tablet just says on the bottom left =>FASTBOOT mode... and it doesnt change and on my pc it says <waiting for device> idk what am doing wrong can someone help me

beachmiles said:
NICE! I took a leap of faith and did this on my Oct 5th 2021 Security update build and it appears to have worked and Im rooted with magisk!!! I added a few additional steps to your commands just in case
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched-24100_w97F6.img
fastboot reboot
I found a USB ADB fastboot driver that was signed and worked on my windows 10 x64 system but I had to go through the "Have Disk" manual driver install and installed even though it wasnt supposedly designed for my hardware. So insane the hoops to do this...
MT65XX-USB-VCOM-drivers\MT65XX USB VCOM drivers\Google_USB_Driver_rev4
Had trouble updating to Magisk to 24.3 however, not sure what pitfall I hit.
Wondering if I should be happy with root or try and flash TWRP and try a different ROM.
Click to expand...
Click to collapse
Followed the same steps and managed to get it working on my tablet that was on the same secpatch. However I also ran into an issue updating magisk. It acts like it worked fine and then when it reboots it asks to patch again.

Had to patch boot file manually and flash via fastboot. Still get an annoying popup when opening magisk but it's now updated to the latest 25.0.
To update run the following:
Root using ops method
Start your device and make sure that everything is rooted and working
adb reboot bootloader
fastboot flash boot [PATH TO MAGISK PATCHED 25000]
fastboot reboot
Tested on Oct521 SecPatch on a devices already rooted with OPs method. Do this at your own risk. Make backups, etc etc.

hi nice work. sorry for my english. but i have a problem on mi onn tablet 1000035652 android 11. i try to root whit our method on fastboot no problem the tablet is unlock a message appears of the erase all data if unlock bootloader and press up volume then restart tablet so configure again and proced to fourt 4 point to flash vbdata and boot and in fastboot window okay flash then reboot and the tablet power on to the config screen then appear a message of controller apps stop then reboot and reboot infinite loop and i try to lock bootloader gain or reflash boot.img stock but no solution and i search for a alast update.zip or way to reinstal stock firmware can anyone help me ?

Database Users

welcome