Actually took all night to figure out how to do this.... this has only been tested on XT1944-2_NORA but it should work for any non64bit builds....
Download MY ZIP FILE and extract.
Install MotorolaDeviceManager_2.5.4.exe
Dowload stock rom FROM HERE and extract and combine MY ZIP FILE and this one.
Open cmd prompt
Code:
cd "C:\ADDRESS of combined folders"
flash stock rom using these commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 vendor vendor.img
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now boot twrp_james.img using:
Code:
fastboot boot twrp_james.img
it will take 30-60secs to load cos of the encryption, when it asks for a password just press cancel
while in TWRP, run the following in your ADB terminal
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
then hit wipe > format data > yes
now push magisk with
Code:
adb push Magisk-v19.4.zip /sdcard
install the zip reboot to bootloader
flash twrp with
Code:
fastboot flash recovery twrp-3.3.1-0-nora.img
FIX BAD KEY LOGO BY CHOOSING WHAT YOU WANT FROM HERE
when ur phone loads just open magisk and update it direct install after updating magisk manager
Related
You can grab your firmware from
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
or
https://github.com/motoxplay/stock
Originally Posted by bodivas
Flash with Wipe:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Without Wipe:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
XT1562_LUX_RETASIA_DS_6.0_MPD24.65-18_cid7_subsidy-DEFAULT_CFC_V2.xml.zip
Is it final version of Marshmallow or the soak test version ? I already have Marshmallow ( via a TWRP backup : http://forum.xda-developers.com/showpost.php?p=64210076&postcount=104 ) but it's the soak test version.
Its the same and final
skdubg said:
Its the same and final
Click to expand...
Click to collapse
Do you mean that this TWRP backup ( http://forum.xda-developers.com/show...&postcount=104 ) is actually the final version ?
These 2:
fastboot erase customize
fastboot erase clogo
Arent really necessary, or?
Gesendet von meinem XT1562 mit Tapatalk
Is this file okay to flash for a rooted UK phone with TWRP?
@kyddox Maybe we can/should add the flash instructions to the README.md on github?
heisert said:
These 2:
fastboot erase customize
fastboot erase clogo
Arent really necessary, or?
Gesendet von meinem XT1562 mit Tapatalk
Click to expand...
Click to collapse
are not necessary, like if you want to erase userdata not erase the information from the sd
Enviado desde mi XT1563 mediante Tapatalk
These commands at first didn't work for my Moto X Play (1562) - until I added:
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
Marshmallow RETEU 6.0.1 Firmware!
You may also check my attached flashfile xml for all of the commands that are needed for this firmware.
Can also be found in the firmware package itself. :good:
Then the commands are (with wipe!)
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Check flash file of your firmware and all the sparsechunk files must be flashed .
I manually unlocked my bootloader and began the process of installing TWRP and then Cyanogenmod. After playing with Cyanogenmod I realized I wasn't missing much, so I tried to go back to Lollipop / Marshmallow only to discover that now every time I boot up my phone it immediately goes to the bootloader, requiring me to manually start my phone. If I try to factory reset it does the same thing. I can reinstall TWRP, but the resulting flash will not allow me to flash custom roms or do much more than click buttons that won't do anything. I cannot get TWRP to export my log to the SD card so I can share the issues. Here is what I have noticed:
1. I have no cache directory according to TWRP.
2. If I try to flash a custom rom, IE Cyanogenmod, it reboots recovery and I don't see an error until I attempt to go back and reflash. Again, I cannot export a log file that will open or allow me to copy it to a different directory.
3. No matter what operation I try to perform, rebooting the device always puts it back to the bootloader. I have to manually start my phone from the menu.
Is there something I should be doing differently? Should I try and flash down to Cyanogenmod 12.1 and then go back to Lollipop? Is the previous upgrade to Marshmallow screwing things up?
Hmm... can you try to flash firmware again? For now skip factory reset in recovery. You can do it later. Flash the latest Marshmallow firmware in bootloader mode:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If you want to flash lollipop you must skip partition and bootloader. It might cause bootloop which you will not be able to fix:
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If your phone goes to the bootloader mode every boot, then you didn't close fb_oem mode, when in the bootloader send the command "fastboot oem fb_mode_clear", you should get an OK. Reboot and you should be good to go.
Your phone reboot to system but every reboot it goes first to bootloader or only bootloader is loaded and you can't boot to system? If first then do what @acejavelin said. If system is not loaded then flash firmware again.
<bootloader/ has-slot:system: not found?
I can flash firmware again, but from there it's still acting up. I also cannot do fastboot oem lock.
Now I'm told the storage is in RAW format?
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Change log?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Thanks a lot, my friend... Now I can root my Moto G7 River again! ?
How do I flash this .zip?
ptn107 said:
RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
also available for xt1962-4
Click to expand...
Click to collapse
Tried to install on a xt1962-4 and it goes bootloop :c
MatheusDeFino said:
Tried to install on a xt1962-4 and it goes bootloop :c
Click to expand...
Click to collapse
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
ptn107 said:
-
My link is for the xt1962-1. Did you get the appropriate xt1962-4 image for your device?
XT1962-4_RIVER_RETBR_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT1962-4_RIVER_RETLA_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-XT1962-4-SUTEL-DS_CFC.xml.zip
The xt1962-4 has options. You need to know which one is correct for you.
Click to expand...
Click to collapse
How install?
Mathiusb said:
How install?
Click to expand...
Click to collapse
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Unroot first?
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
eztechio said:
I'm fairly new to rooting on the Moto G7 since I've only tinkered with my Asus Zenfone. I'm currently rooted on the G7 running PPOS29.114-16-5-2 and patched with Magisk. Do I need to unroot, ie. go back to stock, then upgrade to PPO29.114-134 then root and patch again?
Click to expand...
Click to collapse
You can manually download and flash the new firmware and then patch boot with magisk again. You do not need to go back to stock first.
adb sideload
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Filename differences PPO vs PPOS
Does PPO vs PPOS in the filename mean that PPOS can be sideloaded and the other only via OTA or from internal?
ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Is this method to install for RIVER_RETAIL_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip or it is for Mathiusb's xt1962-4 version?
---------- Post added at 02:21 AM ---------- Previous post was at 02:00 AM ----------
Actually ignore my posts. I just read the flashfile.xml in the zip and it has the same steps. duh!
Fastboot 'waiting for any device'
A new Moto G7 XT-1962 US-Retail running the original ROM, unlocked, rooted, and with TWRP installed. It seems to be working okay but somehow during unlocking and setup, it no longer detects the SIM.
So I thought that flashing the most-recent update might also resolve the SIM problem at the same time. Steps from this forum were followed with a difference that I was using a Mac. The contents of the platform-tools (adb-fastboot) directory were combined with the extracted ROM zip files and the terminal launched from there. Like the Windows technique.
ADB works now and Fastboot had worked before using this same approach for the oem unlocking routine:
Code:
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZY226JMG38 device
Now Fastboot (from platform-tools_r29.0.4-darwin.zip) returns "waiting…" and hangs:
Code:
$ fastboot device
< waiting for any device >
$ fastboot getvar max-sparse-size
< waiting for any device >
$ fastboot oem fb_mode_set
< waiting for any device >
$ sudo fastboot device
Password:
< waiting for any device >
Any suggestions about Fastboot and comments about fixing my undetected SIM appreciated. This flashing routine is a scary undertaking for this dummie.
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
eztechio said:
@dlfuller - Is your device booted in bootloader? When you do fastboot devices -l does your device show up?
Click to expand...
Click to collapse
Thanks @eztechio, but the problem turns out to be the fastboot command itself. Only <waiting for device> in the code sample of my post.
---------- Post added at 11:32 AM ---------- Previous post was at 11:25 AM ----------
I stumbled across the answer to my main question elsewhere and hope this might be helpful to other Mac users.
In MacOS adb and fastboot commands must be preceded with "./" most of the time. Why the exception where some adb commands work without it I don't know.
Code:
$ adb devices
List of devices attached
ZY226JMG38 device
$ ./adb devices
List of devices attached
ZY226JMG38 device
$ ./adb reboot bootloader
$ ./fastboot devices
ZY226JMG38 fastboot
$ ./fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.000s
With fastboot working now, it's on to this dummie adventuring into the ROM update…
Thanks @ptn107. Your fastboot steps worked like a charm. I'm now up to date on ROM Build PPOS29.114-134-2
A fresh, clean slate. Just had to install TWRP and Magisk again. My problem before of not detecting the SIM now resolved.
Just wish I could have retained my user apps and data through the upgrade process. Not executing fastboot erase userdata might have been the approach, but I didn't want to chance it.
eztechio said:
I'm trying to adb sideload the zip from recovery and the minute I execute I get adbd status 1 Installation aborted. Also it seems through RSD lite that the zip is corrupted. Anyone else get this issue?
Click to expand...
Click to collapse
I think u have to unzip and flash files through fastboot commands
@HueyT - Yes I had to extract the files and perform each fastboot command in my command prompt terminal. All is good now. I'm actually now on the latest released firmware by doing the same update steps.
Will it bootloop if I install RETUS on AMZ XT1962-1 phones?
August 1 security update is out
RIVER_RETAIL_9.0_PPOS29.114-134-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
== Installation ==
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash partition bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
If you don't want to clear your existing data, you can skip fastboot erase userdata
I used this method to update a couple days ago as i got sick of the update telling me it failed. No issues so far. Had to re-root with magisk after but... such is life.
I can also confirm this works
Stock boot img
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
fwr6236437 said:
I upgraded to 114 -134-4. I can't download the firmware file so I don't have a stock boot.img file to patch with Magisk. I cannot find a download link for 114-134-4. I don't know how to extract the boot img. If anybody could provide me with the stock boot img. For 114-134-4 I would really appreciate it.
Click to expand...
Click to collapse
from PPOS29.114-134-4
boot.img
Thank you so much! Works great!
Thanks for this write up and break down. It saved my sanity. I havent been with Android since the Nexus 5 and picked up the G7 on a BF sale and decided to try and root it and use custom ROMs. Quick story I jacked it up bad so just wanted to get it back to stock and even then was having issues. This worked. Much appreciated.
Clutch
This saved my life because this was my first time rooting and i got stuck in a bootloop trying to root my moto g7 with magisk. Im so glad i found this.
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Ballyeet said:
Hey, is there anyone using a moto g7 power XT1955-4? If so is it rooted or are you willing/ planning to root it? If yes, then i really need your help. Please let me know if you can help me.
Click to expand...
Click to collapse
Me bro... See:
xe500linux said:
Whats the difference between fastboot -w and just wiping everything in Twrp? That could have been it.. Syber makes the official Twrp as well so dont know if the one in OP is any different
And theres 4 roms btw, Havoc OS has no thread but its on Syber's androidfilehost. Same rgb/display issues as Lineage though
Click to expand...
Click to collapse
bruh you dont even have to use the fastboot -w or wipe command
CREATOR OF POST: MY F***IN BAD my speak problem was some bs from a blank flash i sorted it now the only bugs i got in some sketchy nav bar
there are apparently these roms as well:
CARBON-CR-7.0-OPAL-UNOFFICIAL-ocean-20191025-1317.zip
Viper-ocean-20191029-v6.7-UNOFFICIAL.zip
XenonHD-191024-Unofficial-ocean.zip
---------- Post added at 09:53 AM ---------- Previous post was at 08:54 AM ----------
FULL GUIDE TO DEBRICK/INSTALL STOCK ROM/REMOVE BAD KEY/INSTALL CUSTOM ROM AND TWRP
ensure your google accounts are removed from the phone and bootloader is unlocked...
boot to bootloader
run cmd prompt
use cd C:\*LOCATION* to go to folder with full STOCK ROM but make sure you have this files in the folder too [adb.exe, fastboot.exe, adbwinapi.dll, adbwinusbapi.dll] from ur minimal adb and fastboot setup. you will also need the recovery file TWRP-ocean-3.3.1-Syber-v2.2_11-02.img in this folder and the logo.bin file to remove the bad key FROM HERE. I suggest you rename to logonew.bin and put in the stock rom folder. you will also want ur RRromzip, the copypartitions.zip, the TWRP INSTALLER, GAPPS & MAGISK ZIP...
no matter what stage u are at other than bricked [after the BLANK FLASH then resume with this guide. if ur stuck bootlooping or have messed anything up start from the stock rom install or you will end up bricking your phone....
ok so in your cmd open in stock rom folder type these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot-bootloader
when it reboots to bootloader use these commands from the same folder:
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
now use these commands to remove bad key
fastboot flash logo_a logonew.bin
fastboot flash logo_b logonew.bin
now boot the twrp by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
when twrp boots it should show up in ur windows explorer if you have an sd card just drop the files you need on it or you will have to use command adb push copy-partitions-payton.zip /sdcard/
install the copy-partitions-payton.zip
when complete reboot-bootloader
now boot the twrp again by using
fastboot boot TWRP-ocean-3.3.1-Syber-v2.2_11-02.img
now install the rom zip
then the twrp installer zip
reboot-recovery [it auto switches slot]
install gapps and magisk zips
reboot system
you should have ur custom rom and twrp recovery permanently installed now
Thanks for this guide! Does it work with official TWRP?
One more question: I have the RETEU Version, wich zip should i pick? The PPO or the PPOS Version?
thanks in advance!