Develop Bugs

[GUIDE] How to manually upgrade firmware

First of all, this guide expects you to have some basic knowledge how to use fastboot, have working ADB/fastboot connection on your computer and understand the fact that this may brick your phone if you mess up.
I am NOT responsible for anything! This will wipe everything on your phone, so get backups if needed.
This guide is written for X720 and supplied files are ONLY for X720. Same procedure will work on X727, but you will have to get right files yourself.
All files are from stock 23S, just extracted, converted and repacked for your convenience.
Read the whole guide before doing anything. If you're unsure about anything, don't do it.
Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yhiU5FbCmYuf47VH4Qar5RhV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <-- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin​5. Reboot, and let it boot up (takes some time)
6. Flash TWRP, wipe everything and install ROM (you have done this before, won't write a guide)
Credit for this guide goes to @darkobas

get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.

Presterin said:
I'm only guessing, since many have flashed this successfully, but maybe a bad download or incompatible fastboot.
Click to expand...
Click to collapse
thx
i will try again.

Does anyone know which ones are safe to flash over the existing rom? I do not wish to wipe or break current rom.

I flashed everything except system and boot on top of Omni rom. Everything works great.

Does anyone know where I can get all of the files for my x727, I considered using the files from these OTA zips but I think some of the files are missing like the modem firmware and system.img.

On x720 some of the files were divided into scatter files, had to do some research to get them sorted.

Which fastboot is compatible with system.img? Because of me too :"target reported max download size of 536870912 bytes
Invalid sparse file format at header magi". minimal fast boot 1.42
Edit: ok..as long as the post I wrote started installation

Should/Can we install the latest fastboot? Mine is on shop altered 17s from over a year a go, which to be fair runs great; i just fancy a change.
Thanks

write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do

Any solution?
Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
Stuck here as well

Hasancaktar said:
write "fastboot format data" command say "Formatting is not supported for file system with type ' '." what do i have to do
Click to expand...
Click to collapse
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished

Great guide Thanks.
It saved me from a system wipe and a nightly not recognized by TWRP...:crying:

tsongming said:
First, you provided no information. For example what phone do you have, what OS etc.
I am guessing EUI: It would be alot easier to simply flash the firmware for your device instead of flashing the exact same pieces of it one at a time. By extracting the bits from the full OS.
This is a old outdated guide that has way too many steps, and it was made a long time ago. Since the name of the guide is upgrading firmware, I assume thats what you are trying to do.
Since you are hoping to flash firmware, I will go ahead and assume that you already have your bootloader unlocked, have flashed Twrp and are rooted? You can accomplish updating your firmware with one step. > Go to Lineage 15.1 page and go to downloads section. Here you will see firmware listed, download the firmware to your device. One flash in Twrp will install all of the radio and sensor files needed.
Hint: always boot to recovery first, checking the Twrp installation boxes if present> this is a best practice to avoid bricking your phone.
If you have any issue after following the steps I mentioned ( Its possible because of the fastboot commends) You may need to clean wipe reset and start fresh
Before you begin disable any passwords and fingerprints within the system settings.
Boot to recovery > click wipe > advanced wipe > check cache ( not Dalvik, just cache) > swipe> press home key to return to main menu.
Click install >Navigate to your download folder and select firmware > swipe to install > clear cache again> reboot to recovery
If there are any check boxes to check for TWRP installation, check them >
Once back in recovery reboot to system > Finished
Click to expand...
Click to collapse
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.

jackpollard said:
I hate to be that person, but where the heck is the firmware dl's on the LIneage site? I did search and search. Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720

amdol said:
https://forum.xda-developers.com/le-pro3/development/rom-lineageos-15-0-leeco-le-pro3-t3683720
Click to expand...
Click to collapse
Thank you! My flaw was looking on https://lineageos.org/ and not on here.

ajegile said:
get error
C:\Program Files (x86)\Minimal ADB and Fastboot\x720_upgrade_23s>fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
get the same. iam not shure if i have the x722 or x720. they look same

[GUIDE] How to root your Asus Zenfone 6 without TWRP | Info about A/B

Hey guys and girls,
This is a bit of copy and paste for from my guide for the HTC U12+. I thought it might be helpful to people here too.
If you find mentions of the HTC U12+ please notify me and I will correct them.
I couldn´t find any guide on how to root the Asus Zenfone 6 without twrp yet, so I thought maybe it´s good to have one. It´s also useful for people who don´t like to boot/flash the recovery but want root access.
I also decided now to do a little write up about the A/B slot partition system.
General Information about the A/B slot partition system and seamless updates
Google firstly introduced seamless updates on the Pixel Phones and with it the A/B partition system.
So this means, contrary to non A/B devices, there are two copys of most partitions except userdata.
We have two system (system_a and system_b), two boot (boot_a and boot_b) and two vendor (vendor_a and vendor_b) partitions, amongst others (can be found further down in the partition list but let´s concentrate on these).
When booted in the OS, one slot is actively used and the other is "inactive".
The main advantage that emerges now is, that in case an OTA arrives the "inactive" partitions get updated, while the OS is running. That means while the actual OTA is happening you can use your phone just like you always do.
The following reboot will boot into the former "inactive" slot and use the seamless updated partitions. This happens seamless and just with a reboot. So OTAs are much faster!
If you are interested further here are some links:
https://www.xda-developers.com/list-android-devices-seamless-updates/
https://source.android.com/devices/tech/ota/ab/
https://source.android.com/devices/tech/ota/ab/ab_faqs
Here’s another writeup from the XDA portal!
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But here are a few tips and tricks:
How to reboot to bootloader to be able to use fastboot:
From booted OS with buttons: Press and hold power down until the screen goes black, then press and hold power and vol up to enter bootloader
non responding and the phone isn´t booting: press and hold power plus volume up to enter bootloader
From the OS or recovery via ADB (requires USB Debugging enabled in dev options):
Code:
adb reboot bootloader
How to get the active slot:
Code:
fastboot getvar current-slot
How to set the active slot:
A word of advice. If you don´t know what you´re doing you should probably not change slots. Because my U12+ only has a working A Slot. The B slot is without the first OTA or flashing a RUU unbootable.
Set active slot to a:
Code:
fastboot --set-active=a
Set active slot to b:
Code:
fastboot --set-active=b
How to extract the boot.img from a firmware.zip
1. Download the firmware zip from here : https://www.asus.com/Phone/ZenFone-6-ZS630KL/HelpDesk_Download/
2. Follow the steps described here: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-extract-payload-bin-ota-t3830962
3. Obtain your boot.img
How to root your phone without TWRP
Prerequisites:
- unlocked bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries (can always be found here
- working adb and fastboot environment
- magisk-patched boot.img
How to:
1. Download the latest magisk manager from here and install it on your phone: https://github.com/topjohnwu/MagiskManager/releases
2. Get a boot.img that fits your current firmware. Look at the point above, how to extract it from an Asus firmware zip.
Important: if you decide to use a pre-patched boot.img (available below), download it and place it in your fastboot folder, then skip to step 11!
3. Copy the extracted boot.img to your phone
4. Open the magisk manager app and tap two times on install
5. Now choose patch boot.img file and select the previously extracted boot.img you copied to your phone in the upcoming file chooser
6. Wait for the boot.img to be patched
7. Now connect your phone to your pc and make sure usb debugging is enabled in developer options
8. Open up a terminal in your fastboot folder and make sure adb is working by typing
Code:
adb devices
into terminal which should return your serial number
9. Pull the patches boot.img to your fastboot folder via:
Code:
adb pull /sdcard/Download/magisk_patched.img
10. Reboot to bootloader:
Code:
adb reboot bootloader
11. Flash the magisk patched boot.img:
Code:
fastboot flash boot magisk_patched.img
12. Congratulations you´re now rooted.
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609

Is it possible to do this and still get OTA updates from ASUS?

sidamos77 said:
Is it possible to do this and still get OTA updates from ASUS?
Click to expand...
Click to collapse
You need to unlock the bootloader for this which will prevent you from getting ota updates automatically from asus. But you can install updates manually.

Ok, great, thank you.

Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.

Any way to unofficially unlock the Bootloader?

vasra said:
Remember, this will void your warranty (as per Asus' own definition). Sad, but true.
I would root it in an instant, but am hesitant due to warranty being void.
Click to expand...
Click to collapse
In Europe unlocking the bootloader and rooting doesn't legally void warranty. It was ruled this way a few years ago.

Freak07 said:
[...]
Pre-Magisk-Patched boot.imgs
Important: Make sure to download the correct version, that matches your firmware.
Downloads: https://www.androidfilehost.com/?w=files&flid=295609
Click to expand...
Click to collapse
The folder WW_PHONE-16.1210.1904.75-0 which is the firmware my device has, is empty. Do you still have the prepatched boot.img of that version ? ASUS doesn't have that version for download anymore.
Thanks in advance.
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?

GRöder said:
how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-26#post-2433773
https://swedroid.se/forum/threads/snabba-fragor-snabba-svar-zenfone-6.165775/page-37#post-2442236
Use Translator.

I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
the getvar command returns the following output:
Do you have any advice for me ?
Edit:
After being curious and trying which worked, I tried to flash it at the active slot b explicitly: which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.

Freak07 said:
Did you download the latest adb and fastboot binaries from the link I provided in the OP?
Or did you use already existing ones or from a toolkit/easy installer etc. from somewhere on xda?
To me it sounds you were using outdated binaries.
Fastboot flash boot boot.img detects the active slot automatically if you’re on the latest binaries. Did it like this on the zenfone like on all other A/B devices I’ve owned so far and it works just fine.
Click to expand...
Click to collapse
That might have been the the point. In fact, I did download them, but I used (definately outdated, because on my pc since literally years) a minimal adb and fastboot installation.
I didn't think about it, as this is my first A/B device.
I won't try it now with the latest ones, because it worked and I don't want to destroy something (since we still dont have a working TWRP for backup & recovery) but I guess you're right, and the problem were the outdated binaries.
Thank you.

GRöder said:
If not: how can I update manually since I do not get any OTA Updates with a locked Bootloader ?
Click to expand...
Click to collapse
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.

isthisadagger said:
Download the new Firmware from Asus and copy it to the root of sdcard. Unplug the usb cable or reboot or search for update in settings. It will find the update file and display a notification.
Click to expand...
Click to collapse
In fact, I tried that before I tried the stock-recovery-method (found it at the ASUS FAQ-pages), but it didn't work, even after a reboot, no notification showed up.

GRöder said:
I managed to update my device using the stock recovery. (There is a option like "apply update from sdcard") Now it is on the -133 Firmware, so I should've been able to use the existing, pre-patched boot of that firmware. When I tried to flash it, I got the following error:
Code:
fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'bootb' (47064 KB)...
OKAY [ 1.094s]
writing 'bootb'...
FAILED (remote: (bootb_b) No such partition)
finished. total time: 1.106s
the getvar command returns the following output:
Code:
fastboot getvar current-slot
current-slot: b
finished. total time: 0.009s
Do you have any advice for me ?
Edit:
After being curious and trying
Code:
fastboot flash boot_a magisk_patched.img
which worked, I tried to flash it at the active slot b explicitly:
Code:
fastboot flash boot_b magisk_patched.img
which worked, too. I'm having root, now.
The point is, to specify the partition precisely (e.g. with _a or _b).
Thank you for the guide, maybe you could add my findings to make it easier for others to root their devices, @Freak07 .
Click to expand...
Click to collapse
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks

Ya how do we unlock the bootloader without asus knowing it

MirkoMirko9 said:
sorry guy,
how you unlocked the bootloader ? for me official tool asus doens't work. error due to internet connection is the message.
please can you explain every step ? thanks
Click to expand...
Click to collapse
nikhil18 said:
Ya how do we unlock the bootloader without asus knowing it
Click to expand...
Click to collapse
I used the official app, while the device was connected to the internet. So yes, ASUS knows that I unlocked the device.
The device was still at the -75 firmware, when I did it.
 @MirkoMirko9 If you can live with asus knowing that you unlocked the device, try it again with active internet connection.
As far as I know, there is no other method yet.

unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?

QuazIqbal said:
unable to unlock bootloader with the official unlock device tool, it is showing network error although my network is alright. Any workaround?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=79817571&postcount=31

magisk_patched boot.img for .156 firmware is uploaded to the patched boot.imgs folder

Help getting start

Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------

@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.

Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help

ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.

Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need

ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?

Twrp 3.3.1-0 & root [updated] kane/troika

Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!​
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.

Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !

tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.

daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.

Worked to my, Thnx

Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards

gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.

tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk

gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk

Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?

"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english

First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update

Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !

sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp

It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.

It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse

Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?

Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?

simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.

Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.