Database Info

[RECOVERY][MOD] MultiROM v33 + TWRP v3.1.1 for Xiaomi Mi MIX (lithium)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.​Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please: ​
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.​
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium​
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port

We will have to try soon... It's the perfect set up for flashaholics

Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk

I can't make it work

fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...

Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback

fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx

provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output

Superb, I missed it in this great smarphone

acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.

BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.

acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).

I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.

acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?

there is only one TWRP in your folder. can you point me to another. I'll try no worries

acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564

Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]

Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....

BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/

BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?

Tutorial : Decrypt And Flash Any ROM [ Working on Android 10 ][No data loss]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FLASHING INSTRUCTION :
Warning : Always Backup Your Internal Storage For safer side
Points to be Noted :
1 : Dirty Flashing sometime works. But might have hidden bugs.
2 : Remove the pattern and also fingerprints before flashing the rom.
3 : Always you have to flash twrp zip file after flashing rom. Else you will loose twrp.
If you are on some other twrp versions, Kindly download Compatible TWRP recovery IMG file from download Section and Flash it in recovery.
TWRP installer zip by mauronofrio - Supports Android 10
This works Fine. I recommend all to use this recovery.
To Decrypt Your Device : [ For First Time ]
Step 1: Place the Full ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now select Full ROM zip file and swipe to flash it and then flash the twrp zip file again
Step 5: Format DATA and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Step 9: Voila !! Now your device is successfully decrypted and
Now To Flash OOS updates in Your Decrypted Device : - Works For Android 10 Based OOS
Step 1: Place the Full OOS ROM zip file in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp zip file and reboot to recovery.
Step 5: Now in recovery flash magisk 20.4 only
Step 6: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 7: Reboot the phone. Now both TWRP and Magisk will be there and still your device is decrypted too with android 10
To Flash CustoM ROMs in Your Decrypted Device :
Step 1: Place the Full Custom ROM zip file and required base version Rom zip file ( I.e., OOS BETA OR OOS STABLE) in internal Storage.
Step 2: Now Reboot the phone to TWRP Recovery.
Step 3: Wipe Dalvik cache ,Data , System and Cache.
Step 4: Now Flash OOS Zip and twrp and reboot to recovery and Flash oos zip and twrp again and reboot to recovery. Now select Full Custom ROM zip file and swipe to flash.
Step 5: Flash the twrp zip file again and reboot to recovery.
Step 6: Now in recovery flash magisk 20.4
Step 7: Now Flash the No-verity file - Pie Supported here and Android 10 Supported from here[Important]
Step 8: Reboot the phone.
Credits : @topjohnwu, @virtyx and others .
@mauronofrio for his TWRP.

Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr || TWRP installer zip by mauronofrio - Supports Android 10
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​

HatRiGt said:
Download Section :
Recovery:
Official TWRP ||
Blu_Spark TWRP || Unofficial TWRP by joemossjr
For Root :
Magisk
To Decrypt :
No Verity Mod for OP6 ​
Click to expand...
Click to collapse
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?

Unlocked.Devices said:
Please excuse the dumb questions, I am new to these parts (Device Delivery for Tomorrow), but other then Treble and if TWRP isnt decrypting, why else would you want to decrypt your Device? And finally, the No-Verity MOD is the last part of the instructions, so my question is does the device automatically encrypt when all said and done?
Click to expand...
Click to collapse
keeping your device decrypt will make you to switch between any roms easily. You dont need to wipe internal storage thereafter.
Flashing Untouched OOS ROM will make your device to get force encrypt, so to avoid that you need to flash no verity mod .

I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
If your device is encrypted, first take backup of your internal storage and follow the steps in op

mixlex said:
I'm running oos 1.5.11 rooted with magisk 17.1 and twrp 3.2.3-0. can I flash this zip now without starting everything over? Sorry if this has already been asked.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Oops....5.1.11
Click to expand...
Click to collapse
Sadly no. Data format is required to decrypt phone

m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:

refedit said:
m8, I don't get step 4 of decrypting device.
I select Full ROM and at the same time we Format Data?
Thanks for the guide!:good:
Click to expand...
Click to collapse
First flash the rom and then format the data.

HatRiGt said:
First flash the rom and then format the data.
Click to expand...
Click to collapse
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?

snigor said:
After formatting data I'm having issues mounting, I tried fastbooting twrp to get mounted to get files over(any chance this would mess anything up?).
Should the no verity mod always be flashed last and does it require a reflash after say flashing a kernel?
Click to expand...
Click to collapse
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.

Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that

saleappeal said:
Now ROMs in your decrypted device Flash
After instruction flashed restart always takes place again and again into the recovery
Is there a reason for that
Click to expand...
Click to collapse
could you explain it clearly about what you have done ?

give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775

virtyx said:
give credit where credit is due
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
Click to expand...
Click to collapse
Done bro.

HatRiGt said:
1) Actually never use that twrp that has support for MTP. Always use normal twrp.
If you have got any mounting issue, just flash the fastboot rom and then again boot to twrp and then follow the steps in OP carefully.
2) Yes no verity should be always flashed in the last before you boot into the system .
even if you flash kernel / magisk, then you have to flash no verity.
Click to expand...
Click to collapse
I'm using blu_spark twrp(was recommended both in OP and for flashing pie OB1) and MTP worked fine. Up until formatting, that is.. it does say you might need to restart to use file system(I'm guessing either for mounting or decrypting filesystem after format?). It'll just show the device with no space total or used, and then times out if i try to create a folder or copy something over.. is the trick here to put the needed files on a partition that's not touched when formatting, if that's a thing?
I feel like I'm missing something, but I think my issue was just flashing kernel last.. I'm gonna look into the manual method at some point to get a better idea of what's what! Thanks a lot!:good:

I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.

SelfElevated2 said:
I mean after formatting you end up with no twrp zip to flash and you cant transfer files in twrp…..
Or at least I couldn't at first. I was stuck with no os and an empty internal storage. My newer computer couldn't transfer files.
However after hooking it up to my old computer I was able to transfer files in twrp using blu spark twrp. I put the liquid remix rom, twrp, magisk, gapps and the no verity zip in internal.
flashed rom, flashed twrp, rebooted recovery, flashed gapps, magisk, then flashed no verity and rebooted system.
Pretty sure the only reason I was able to transfer those file is because liquid remix has adb debugging and mtp checked by default in developer settings.
And i'm still decrypted so all is good.
Click to expand...
Click to collapse
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.

In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.

HatRiGt said:
Actually u can also flash twrp file before formating data. Or format data and boot to recovery using Fastboot method.
Click to expand...
Click to collapse
Yeah but stock rom has USB debugging off by default. So someone that flashes stock wouldn't be able to use fast boot or file transfer. They would have to use the UNbrick tool. You may want to to change the order in instructions so less knowledgeable people don't run into problems.
Even if you flash TWRP before formatting, you still lose the no verity you put in internal storage. A fresh install of stock rom won't let you use fast boot commands as USB debugging is off by default
vtec303 said:
In order overcome this file transfer problem after format data I used a USB flash drive and viola, problem solved, hope this helps. cheers.
Click to expand...
Click to collapse
Yeah I just ordered one on eBay yesterday. I figured that would be a huge help as long as TWRP let's you access the other storage.
Sent from my OnePlus6 using XDA Labs

[Treble][Pie]A full guide on how to install 9.0 GSI on Razer Phone on both A/B

I found linuxct's guide (Link: https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684) need to be modified to get 9.0 GSI working (at least in my circumstance). I haven't tried any Oreo Gsi but to my case, I can't properly booted to 9.0 Gsi by following exactly to this guide. That's why I want to write my own processes of getting it works. Hope it's useful to some of you.
0) I strongly recommend you to flash back to stock image from razer, if you have messed up with the partitions. !!THIS WIPES YOUR DATA, PLEASE BACKUP THE INTERNAL STORAGE!!
Code:
(Link: https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip)
After flashing to stock, it should automatically reboot into the system.
/*To your convenience, please put all the required file under the adb tool folder*/
1) Enable USB debugging, reboot to bootloader by command:
Code:
adb reboot bootloader
2) Flash the prebuild boot image in linuxct's guide by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
(Link is mentioned above)
This boot image has TWRP and Magisk built in.
3) Reboot into TWRP by command:
Code:
fastboot reboot
4) In TWRP, tap Wipe and do a factory wipe. DON'T CHANGE THE DEFAULT WIPE SETTINGS.
5) Flash the GSI you have, then reboot to bootloader.
6) Extract and copy the stock boot image from Razer to the adb tool folder, and flash the boot.img by command:
Code:
fastboot flash boot_a boot.img
7) Reboot to the stock recovery, and do factory wipe, then reboot to bootloader.
This will decrypt the /data. (I am not sure why if I do it under TWRP, I can never boot into system, but that's the case.)
8) Flash the prebuilt image from linuxct again by command:
Code:
fastboot flash boot_a boot_linuxct_20180420_cheryl_omr0.img
9) Reboot to the system by command:
Code:
fastboot reboot
And whola, you should be able to boot into system without any decryption message. And you will have a partially functional TWRP.
If you need to flash any other GSI next time, you should first copy the GSI image through MTP in system. Because the TWRP doesn't support adb command and can't be mounted as MTP.
Once you have copied the GSI image, you can reboot into TWRP and flash image as usual.

Here are the photos proving this works. I flashed Pixel Dust first through the command and booted. Then I reboot into TWRP and flashed PixelExperience through TWRP and get it booted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can't image I figured out to flash the second system_b so quickly lol.
0) In system_a, reboot to bootloader by command: adb reboot bootloader
1) Flash the GSI you have to system_b: fastboot flash system_b [The GSI you have]
2) Flash the stock boot image to boot_b: fastboot flash boot_b boot.img
3) Set active partition to B: fastboot --set-active=b
This is where I found linuxct's guide tricky because it should be 'b'.
'_b' doesn't work.
4) Reboot to stock recovery: fastboot reboot
5) Do a factory wipe, then go back to bootloader
6) Flash the prebuilt image to boot_b: fastboot flash boot_b boot_linuxct_20180420_cheryl_omr0.img
7) Reboot to the recovery: fastboot reboot
And it will brings you to TWRP on B partition, and you can reboot to system_b now.
And whola, and now you can have both AB system with different GSI. And you can switch to any partition by going to TWRP on either partition and switch as you like!
Here are the photos proving I have Pixel Experience and Pixel Dust working seperately on two partitions.

I also found that the prebuilt boot image from linuxct is breaking the wifi. Till now, you should have the TWRP patched boot image on both AB partition. So fixing that is pretty straightfoward.
1) Copy the stock boot image and TWRP installer zip to your phone in system.
Link: https://dl.twrp.me/cheryl/
I used the 3.2.1 version.
2) Boot into TWRP by command: adb reboot recovery
3) Flash stock boot.img on both A/B partition.
You can do this by first flash it to Slot A, and switch to B in TWRP. NO NEED TO REBOOT, SIMPLY SWITCH SLOT IN TWRP!!
4) Flash the twrp zip file.
This should fix your wifi.
DON'T FLASH MAGISK! I found flashing even the latest magisk v18.0 breaks wifi again.

So could you have stock on slot a and another GSI on slot b?

Magisk still breaking WiFi and 4g? I played around with 9.0 gsi's ages ago and that was the only thing stopping me from using it. Have anyone tried the latest canary builds of magisk also?

askylitangel said:
So could you have stock on slot a and another GSI on slot b?
Click to expand...
Click to collapse
Since A/B systems are using a common /data partition, I think you can at most flash an 8.1 Oreo on another slot because the stock image is 8.1. And this breaks the OTA of stock, so pretty meaningless.

It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting

parky169 said:
It worked for me following the guide unfortunately had to go back to stock (no WiFi) shame was looking good too thanks for the guide though helped at least getting system up and booting
Click to expand...
Click to collapse
Follow the guide on #4, it will certainly fix Wi-Fi.

Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either

Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.

BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Pixel Experience, Pixel Dust, Aosp extended 6.1

BoostRoid said:
Any of these ROMS run at the full 120hz? So far I've tried 3 and the seem to run even lower than 60hz.
Click to expand...
Click to collapse
Reboot after first boot fixes it.

parky169 said:
Followed must of the guide except just on partition a all worked nice
Thanks a lot.had no issues installing magisk either
Click to expand...
Click to collapse
To clarify, you only installed on partition A, and installed magisk without breaking wifi?

Apologies for not clearing one thing up,I installed android 8.1 and it all
Worked I didn't realize at first it was android 9 that was having WiFi breaking,I haven't tried that one yet.sorry if I was misleading anyone
With my post.

All I had to do was flash the GSI image via fastboot and that seemed to work fine with no other flashing needed

What gsi ROM did you flash? And have you flashed magisk on it ?.

HO-COOH said:
I also found that the prebuilt boot image from linuxct is breaking the wifi.
Click to expand...
Click to collapse
Using an MR0 image on MR3 is not recommended, and using Magisk will break RIL (data connectivity) and WiFi.
If you want to run Pie GSIs, forget about using Magisk and run phh-su. Lastly, if you want your front camera and Bluetooth A2DP to work, use latest phh-gsi image v109. Using older versions than v108 is discouraged for breaking the mentioned.
Current status:
1. Cheryl specific overlays are not yet merged into phh source code because I'm a lazy assh*le. If you want your device to have Adaptive brightness, gestures, and fix the strong vibration, place the following apk inside /system/overlay or /vendor/overylay
2. Razer Power Service and NFC are faulty and will spam your logcat, which may, in the end, reduce your battery life. You need to extract [email protected] from both /system/lib and /system/lib64 from Razer's stock ROM and place them respectively into /vendor/lib and lib64. I've conveniently extracted them for you (Folder named 32's file should be extracted onto /vendor/lib and folder named 64's file should be extracted onto /vendor/lib64).
To kill NFC until we find a proper solution, go into your GSI's filesystem path /system/app/NfcNci and delete or change NfcNci.apk's filename into anything else, like NfcNci.bak.
3. Common to MSM8998, and I believe several other Qcomm based smartphones, Bluetooth In-Call audio is not working, and audio gets redirected to Earpiece.
4. Everything. Else. Works.
Please thank @phhusson for his amazing job in this project!
---------- Post added at 09:16 ---------- Previous post was at 09:13 ----------
As an extra, if you would like to erase your data/userdata partition without messing up with recoveries, you could just issue the following fastboot command:
Code:
fastboot format:ext4:0xc72dd3000 userdata
Where 0xc72dd3000 is the userdata partition size with FBE enabled.
If you are running a bootimage without FBE, the partition size might be 0xC72DD7000, so the command would be:
Code:
fastboot format:ext4:0xC72DD7000 userdata
--------------------
As a result, a summary of OP would be:
0. Flash latest cheryl fastboot image just like explained in OP.
1. Download the Android 9.0 GSI of your preference.
2. Reboot into fastboot.
3. Wipe your userdata partition with:
Code:
fastboot format:ext4:0xc72dd3000 userdata
4. Flash the system image you downloaded with:
Code:
fastboot flash system IMAGENAME.img
Where IMAGENAME goes your system image name. In our bootloader, you don't need to specify the partition you want to flash, and fastboot flashing into just "system" will flash the current slot.
5. Follow the steps from 1 and 2 from the Current status section above to get all the perks to work.

Tried multiple android 9 GSI roms and some boots but no wifi and data (some don't even boot).
Wifi fix (works on Arrow OS) on post #4 doesn't work. After flashing twrp 3.2.1.0, the phone does not boot on any android 9 GSI roms. Anyway thanks for your work trying to make GSI work on Razer phone.

Hello, I followed your instructions in post 4 to the letter, I've got 4g but no wifi. Any ideas what I'm doing wrong?

[Treble]Flash some (GSI) on the Razer Phone with wifi fix

How to Flash Any Generic System Image with WIFI 100% working on Razer Phone
You have to follow exactly step by step or it will not work. But don't worry, all these step very easy & work if you don't miss any step.
Here some photos proof proving this all features and WIFI works:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As we know, actually there are some guides how to install any GSI on razer phone such as linuxct's guide (Link: https://forum.xda-developers.com/razer-phone/how-to/treble-install-generic-image-gsi-razer-t3770684) and HO-COOH's guide (link: https://forum.xda-developers.com/razer-phone/how-to/treble-how-to-install-9-0-gsi-razer-t3883586), some of them can't not boot in GSI or wifi not work after root with magisk.
Follow this way, I'm sure after flash GSI, all feature work, special wifi 100% working.
Special thanks and credit to @linuxct, with lots of help from other members.
Working Features: GSI Image for Razer Phone
Almost all the important features are working perfectly fine with the GSI Image for Razer Phone.
- GPS
- Rear Camera (only one of the lenses, needs further testing/pulling the Razer camera app apk)
- Front camera
- Microphones
- Sensors, each and every of them
- Speakers, sound playback, videoplayback (needs further testing)
- Fingerprint scanner
- WiFi, Bluetooth, NFC
- 120Hz screen features
- Color adjustments from the Oreo DP1 by Razer
- 4G LTE
- In-Call audio
ROMs GSI can be booted & root:
arrowOS - 9.x (crash for the first time)
Lineage OS 15.1 (most stable, recommend)
Resurrection Remix
HO-COOH and linuxct suggested Wifi still not work on these below GSI yet after root, so I'm not sure it
AOSP Android 9.0 Pie (if you choose this, it need flash a ndroid 9.0 Pie Gapps Package or you can download OpenGapps 9.0.)
AOSPExtended ROM (if you choose this, it need flash a ndroid 9.0 Pie Gapps Package or you can download OpenGapps 9.0.)
Pre-Requisite
flash_all.bat back to stock image from razer factory images [url]https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip[/URL]
SHA-256 Checksum: cf63490e488a49832da861693d070e01f78c62ebe7d0f0aa5568ed83739173bc
When restore original factory images complete. Connect the usb cable, boot into system, enable USB debugging and tick "Always allow from this computer" after pop up "Allow USB debugging?"
1.) Obtain boot.img from the latest Razer factory image. (If you are not already on the latest, best to just flash it using Razers guide to restore using factory image.) https://developer.razerzone.com/razer-phone-dev-tools/factory-images//
2.) Obtain TWRP.img and TWRP.zip from https://dl.twrp.me/cheryl
3.) Obtain Magisk from: https://github.com/topjohnwu/Magisk/
5.) Push 4 files to /sdcard by ensuring all 4 files are inside of your platform-tools folder, and following command: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v18.1.zip /sdcard"
Instructions to flash GSI
1.) Type: "adb reboot bootloader "
2.) Type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
3.) Once in TWRP, DO NOT SLIDE to allow modifications, but tap on Read Only. Go into Reboot, then make sure you're on partition A.
Now back, go Install, tap on 'Install Image' choose the boot.img you, and flash it as boot image.
Back into Reboot, move to partition B and repeat the step above.
Set the partition A as active, tap Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it.
4.) Go into Reboot, press on Bootloader.
5.) Razer phone, you should choose Image for ARM64 A/B device. Copy file GSI image, paste to folder Platform tools adb and flash the GSI system image onto your system_a partition, example you want flash Lineage 15.1 (system-arm64-aonly-gapps-su.img),
type: "fastboot flash system_a system-arm64-aonly-gapps-su.img "
6.) When flash finished. Type: "fastboot erase userdata && fastboot reboot ". If you skip this step, it will stuck boot into system with decrytion message or force enter password. Wait about 5 ~ 10 minutes, it will boot into system.
Root GSI with wifi 100% work.
After boot into system, you must enable "Android debugging".
You have to reload again 3 files to /sdcard with the following command: "adb push boot.img /sdcard", then "adb push twrp-installer-3.2.1-0-cheryl.zip /sdcard", then "adb push Magisk-v18.1.zip /sdcard"
1.) Type: "adb reboot bootloader " and "adb reboot recovery" or type: "fastboot flash boot twrp-3.2.1-0-cheryl.img && fastboot reboot"
2.) Once in TWRP, DO NOT SLIDE to allow modifications, but tap on Read Only. Go into Reboot, then make sure you're on partition A.
Go back, go in Install, tap on 'Install Image' choose the boot.img , and flash it as boot image.
Back into Reboot, move to partition B and repeat the step above.
Set the partition A as active, tap Install, choose the twrp-installer-3.2.1-0-cheryl.zip and flash it. When finishes, do the same with the Magisk zip file.
3.) Reboot and check wifi, I guaranteed WIFI 100% work, if you stuck in TWRP, just type: "fastboot flash boot_a boot.img && fastboot reboot"
4.) Download newest Magisk direct in the phone, and install it. Don't install through adb.
Bonus how fix ctsProfile: false
1.) Open Magiskmanger, tap on Download, type: " MagiskHide Props Config", tap install".
and also download Busybox by type: "Busybox for Android NDK", tap install wait unstill finish. Now reboot.
2.) Open play store, searching: "Terminal Emulator", install it.
Run it, and
type: "su" enter, "props" enter, "1" enter, "f" enter (choose what kind of your devices from list, example me razer phone) I type "13" enter, "y" enter, "y" enter.
Done, now reboot and recheck SafetyNet status, all passed.
Watch this video more clear:
Now your phone fully Root and all main feature work. Thanks again for a lot help from many other forum's members. Every times, SafeNet status fail or broke,zero just repeat above steps then reboot.

I don't know whether it's my guide's flaw or something, there are indeed some GSIs just won't boot following my guide. (But some others boot just fine)
I will be very appreciate it if you can help testing the Pixel Experience Pie GSI here: https://github.com/EnesSastim/Downloads/releases
And sorry, I followed your guide exactly from stock, and latest Magisk v18.1 still breaks wifi on Android Pie. You can test it out yourself. (Because I see your post are the screenshots of Android Oreo with Magisk) linuxct replied to the issue in my guide by the way.

I tested Lineage 15.1 (system-arm64-aonly-gapps-su.img), ArrowOS 9.x, it worked like charm both of them with WiFi fix and not stuck logo boot or force enter passwords

bexiu said:
I tested Lineage 15.1 (system-arm64-aonly-gapps-su.img), ArrowOS 9.x, it worked like charm both of them with WiFi fix and not stuck logo boot or force enter passwords
Click to expand...
Click to collapse
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.

HO-COOH said:
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.
Click to expand...
Click to collapse
don't forget this command after flash arrowOS, you have to type exactly "fastboot erase userdata", don't try
Code:
fastboot format:ext4 userdata
fastboot format:ext4:0xc72dd3000 userdata
fastboot format:ext4:0xC72DD7000 userdata
, becuase it's not work in this case.
Rom Lineage 15.1, I tried this (system-arm64-aonly-gapps-su.img) from https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690

bexiu said:
don't forget this command after flash arrowOS, you have to type exactly "fastboot erase userdata", don't try
Code:
fastboot format:ext4 userdata
fastboot format:ext4:0xc72dd3000 userdata
fastboot format:ext4:0xC72DD7000 userdata
, becuase it's not work in this case.
Rom Lineage 15.1, I tried this (system-arm64-aonly-gapps-su.img) from https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
Click to expand...
Click to collapse
No luck. I followed the exact same steps on Arrow OS. Still breaks Wi-Fi. Can you post a screenshot with Magisk working on any Android Pie roms? I believe it's really like what linuxct said.
Oh, Arrow OS has serious bugs too. System UI is always crashing. And the NFC icon on the status bar seems fake.

HO-COOH said:
So is it rom specific issue? I can get Pixel Experience booted but rooting it with Magisk breaks wifi. I am testing out ArrowOS now.
Click to expand...
Click to collapse
HO-COOH said:
No luck. I followed the exact same steps on Arrow OS. Still breaks Wi-Fi. Can you post a screenshot with Magisk working on any Android Pie roms? I believe it's really like what linuxct said.
Oh, Arrow OS has serious bugs too. System UI is always crashing. And the NFC icon on the status bar seems fake.
Click to expand...
Click to collapse
I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS.

bexiu said:
I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS.
Click to expand...
Click to collapse
Yes I am talking about ArrowOs. I can't get Wi-Fi with Magisk on it. It's Android Pie and I think you can't install Magisk with any Android Pie roms.

HO-COOH said:
Yes I am talking about ArrowOs. I can't get Wi-Fi with Magisk on it. It's Android Pie and I think you can't install Magisk with any Android Pie roms.
Click to expand...
Click to collapse
Yes, I'm not try AOSP Android 9.0 Pie, as you said, I think wifi will not work on them.
I think you should clean first by WIPE advanced, tick: Dalvik/ ART Cache; System; Data; Internal Storage before rom back factory images. After finish flash factory images. you follow from this step: Instructions to flash GSI and Now root GSI with wifi 100% work..

bexiu said:
Yes, I'm not try AOSP Android 9.0 Pie, as you said, I think wifi will not work on them.
I think you should clean first by WIPE advanced, tick: Dalvik/ ART Cache; System; Data; Internal Storage before rom back factory images. After finish flash factory images. you follow from this step: Instructions to flash GSI and Now root GSI with wifi 100% work..
Click to expand...
Click to collapse
Then you should really change the title, because you still can't use Magisk to root Android Pie, but only Oreo. I would be very excited if Magisk could root Android Pie on Razer Phone, but still no.

sorry about that. I'm not try on Pixel Experience, just tried on Lineage 15.1 and arrowOS both work.
Ok, I changed title. I'm just happy, enjoy and share something when I can still custom flash some GSI 9 pie base on factory images razer phone. thank you anyway.

thank you so much!
this works great! however, i have an issue with my date and time when i reboot. whatsapp complains my date and time is incorrect (and microg crashes on boot, but i'm not sure it's related). sometimes it stays wrong and the date is set to 2018 (i then have to correct it manually because the internet doesn't work if the date is drastically wrong), but sometimes it corrects itself. it's not a major issue, but it's still annoying. and no, i do not have gapps installed and will not install gapps. thanks!

:good:
Great review, you made my day after trying other how-tos. Everything works like a charm, thx again

[TWRP + MAGISK] Root your Motorola One Action

TWRP + MAGISK for our Motorola One Action​
First of all, let me thank to @ilia3367 for his big effort bringing the joy of mod to our phones (One Vision and Action) and my fellow countryman @sfoot13 for his unvaluable help.
Original guide
Disclaimer
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Backup all your personal information, it'll be wiped.
* This process was performed on the XT2013-1 using PSBS29.-21-20-4 compilation.
Click to expand...
Click to collapse
Instructions
1- Unlock your Motorola One Action using Motorola's Official Guide.
2- Download this file to your PC.
2.1- Get the latest compilation of your firmware, according to your region, here.
2.2- Unzip the file downloaded on step 2 on c:\adb (you should already have installed ADB, Fastboot and Drivers at this point) and unzip the firmware in a place of your convenience.
3- Copy the files KANE_flash_stock.bat and vbmeta.img (remember, both files are from the file you've downloaded on the step 2) of c:\adb to the firmware folder you unzipped on step 2.2.
3.1- Some firmwares have one more system.img_sparsechunk than others, in case the firmware you've download has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
4- Copy this files (located at c:\adb) to your External SD (mandatory):
Disable_Dm-Verity_ForceEncrypt.zip
MagiskManager-v7.3.4.apk
Magisk-v19.4.zip
TWRP-3.3.1_Installer_One_Vision.zip
This is where the fun begins.
5- Reboot your phone to bootloader mode.
6- Once detected, execute the KANE_flash_stock.bat you've edited and copied to the firmware folder and wait until the phone reboots to bootloader again (around 2-3 minutes)
7- Open CMD on your computer and type
Code:
cd c:\adb
, then
Code:
fastboot -w
and when it's done
Code:
fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
8- TWRP will boot on your phone, surely in Russian, check the box and swipe to allow modifications on /system. I suggest you to set TWRP on your language (if not Russian of course ), the language setting is on the right column on the third button, and then, the globe icon (the last one), choose your language and set it up using the gray button.
*If you can't get to TWRP the first time, after the Android One Screen, keep pressing volume down and power buttons, when the phone shuts down, release the button power and get into fastboot again and try the command described above (fastboot boot TWRP...). Try until you can get into TWRP recovery, the first time took me around 4-5 times.
8.1- According to your language, go to Install > Select Storage > Micro SD card and flash TWRP-3.3.1_Installer_One_Vision.zip, once it's done, go to the home screen.
8.2- Now tap on Wipe > Format Data > Type Yes and go back to the home screen again.
8.3- Reboot to Recovery.
9- Install > Magisk-v19.4.zip and Disable_Dm-Verity_ForceEncrypt.zip, go to the home screen and tap on Reboot > Bootloader
9.1- On CMD type
Code:
fastboot flash vbmeta_a vbmeta_patch.img
and when it's done, press the power button to start.
10- The phone will show Android One Logo > Unlocked Bootloader warning screen > Android One Logo > It will reboot and will repeat the same process
10.1- After that scary but necessary reboot, it will reach the setup screen and... It will reboot and will repeat the process shown on step 10.
11- Once it reaches the setup screen again it will not reboot again (randoms reboot has been reported, nothing serious, let it reboot and keep it using).
12- Complete setup.
13- Uninstall Magisk Manager and install the APK you've copied to your External SD on step 4.
Now you're rooted.
Thanks for taking the time to read the whole guide and excuse my not-so-well (poor is threshed) english.
The original guide didn't work for me on the part when it says to boot TWRP using fastboot > Wipe Data > boot TWRP via fastboot again, it kept hanging on the Android One screen.
Greetings,
Charly.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I keep getting stuck on boot screen
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant

Root Moto One Action - Working on Android Pie (9) and Q (10) 23.01.2020
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
There's another way to do it.
Download the files and install magisk on your phone.
1. Open magisk and patch your boot.ing
2. Save your patched boot to adb-fastboot folder.
3. Reboot to bootloader.
4. Flash vbmeta.img: fastboot flash vbmeta_a vbmeta.img
5. Flash your patched boot: fastboot flash boot_a PATCHEDBOOT.IMG
6. Flash vbmeta_patched: fastboot flash vbmeta_a vbmeta_patch.img
7. fastboot erase userdata and reboot.
8. Configure your phone and install magisk manager apk.
9. Here, you'll need and app... Franco kernel app, because that app allow you to flash zips without twrp (I don't know a similar app).
10. Open Franco kernel app and install twrp installer zip and reboot.
11. Reboot into FASTBOOT and type fastboot -w after that, select "Reboot Recovery".
12. Now, configure Twrp, change language and format Data (type YES), if you don't format data, you'll end in bootloop.
13. Flash magisk again because the phone was unrooted when twrp installer was flashed and flash Disable_Dm-Verity_ForceEncrypt.zip.
14. Reboot and if everything was successfully, you should be rooted with twrp working.
15. Be grateful
---------- Post added at 02:33 AM ---------- Previous post was at 02:27 AM ----------
@Tuandroidaldia
Thank you so much for the guide

If you want to UPGRADE or DOWNGRADE MAGISK, do this:
Download the Magisk version that you need and reboot into recovery.
1. Flash the downloaded Magisk version.
2. Now flash Disable_Dm-Verity_ForceEncrypt.zip
3. Reboot.
4. Check if everything is ok.
5. Hit or say "thanks".

anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
I rooted my device and then made this guide, so yes, I "followed" it If you're not able to boot into TWRP then you're missing some steps, like "fastboot -w"

Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.

binary**# said:
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
Click to expand...
Click to collapse
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.

Tuandroidaldia said:
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Click to expand...
Click to collapse
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.

binary**# said:
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
Click to expand...
Click to collapse
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.

Tuandroidaldia said:
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Click to expand...
Click to collapse
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions

So here are my results
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.

binary**# said:
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
Click to expand...
Click to collapse
I understood you. One of the steps for achieving root is to flash the Stock Firmware (with the patched vbmeta.img), so, If you want to go back to stock, you have to flash the entire firmware using the same commands as described above (with the stock vbmeta.img)

binary**# said:
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
Click to expand...
Click to collapse
Thanks for the note, I'll change the guide ASAP. If you don't get to TWRP at the first try, you have to reboot into bootloader again (keep pressing the power button and volumen down button until it powers off, release the power button and it should reboot to bootloader), enter fastboot boot TWRP-3.3.1_Motorola_One_Vision.img and see if you can boot into TWRP, if not, try again until you can boot to TWRP (it took me around 3 or 4 times to get TWRP booted on my One Action the first time)

Hi Guys!
Got my Action One today (US User here!) and was pulling out my damn hair!!!
For those who can NOT boot into TWRP double check STEP 3!!! My issue was, even though I copied the extra zip file into the firmware folder, it did NOT overwrite the vbmeta.img so it was still loading the non patched version! Once I saw that the version it was flashing was from 9-16-2019 (For my firmware - RETAIL) and not the one from the zip from 9-26-2019! Once did that, on the second try TWRP booted and volia!
SO OP Please add to check the vbmeta.img is the correct version being flashed if they can not boot to TWRP and thanks for the instructions!

Ok so stupid me (This happened to me on my G5s+. I come from Quark so there was only one possible firmware for the phone since it was a verizon branded firmware) flashed the wrong firmware (RETAIL vs RETUS) but this guys doesn't see to work on the XT2013-4 though. The RETAIL firmware will let me have data but no voice on Verizon.
Any suggestions anyone?

My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.

thalesjans said:
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
Click to expand...
Click to collapse
During the original setup, where did it fail? Did it not boot TWRP?

Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!

thalesjans said:
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
Click to expand...
Click to collapse
So you first downloaded and flashed your firmware from the listed and did the sets to add in the extra line of code for it? Did that even complete? Then the fastboot -w? Also you copied over the vbmeta.img in the zip to the firmware folder? Twrp will not boot if that patched file is not there. Also you only boot from twrp not flash it. You don't flash it until later
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Also what model of the XT2013 are you uaing? There is XT2013-1 thru XR2013-4.

Root success! Xt2013-2
So I finally rooted my Moto One Action (XT2013-2). I read on many forums that the method of flashing the patched boot.img file gave some kind of validation error for their boot files. But anyhow I went ahead with the very method and was able to successfully root my device. Here are the steps to be followed.
STEPS:
View attachment 4870223
NOTE: USERS HAVING XT 2013-2 (INDIAN VARIANT) MAY DIRECTLY TAKE MY PATCHED BOOT.IMG FILE. IT IS BASED ON THE FIRMWARE VERSION PSBS29.39-23-6
1. Extract the boot.img file from the stock firmware.
2. Patch it via Magisk Manager. The magisk_patched.img file will now be created under the Downloads folder. Move it to the platform-tools folder on your desktop.
3. Reboot to fastboot mode and flash the vbmeta file via fastboot flash vbmeta_a vbmeta.img
4. Now use the fastboot flash boot_a magisk_patched.img to flash the patched boot file.
5. Next, flash the vbmeta patched file using fastboot flash vbmeta_a vbmeta_patch.img
6. Then erase user data using fastboot erase userdata
7. Finally fastboot reboot
8 Now set up the device and install the Magisk Manager app.
9. Head over to the Magisk Manager app. It will ask for some additional configurations. Allow it. It will take a minute or two for the Magisk configuration to complete. Once done, your device will automatically reboot once. it's normal.
10. That's it. Your Moto One Action will now be successfully rooted (as already mentioned, the process was carried on the version XT 2013-2.)