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?

[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?

My experience - PIXEL EXPERIENCE PLUS (A11) - GSI-Unofficial

Stable enough to be used as your daily driver.
This rom is not developed nor maintained by me!
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk
Download arm64-ab-11.0-xxxxx
or arm64-ab-vndklite-11.0-xxxxx
Download: Link
Extra tip: try Lawnchair launcher
Install like any other GSI Rom including the Nfc patch.
IMPORTANT! Before booting up the ROM, you will need to perform a factory reset in stock recovery!
Quick and easy way to install GSI & NFC :
1. Extract the ROM .img file from the compressed file.
2. Flash extracted ... .img in fastboot , use command
fastboot flash system (file_name).img
3. In fastboot flash TWRP over eRecovery (!) - guide:
https://forum.xda-developers.com/t/rom-official-anne-9-lineageos-16-0.4151163/post-83603363
4. Run command fastboot reboot , enter TWRP (press and hold Volume Up)
5. In TWRP unmount all except SD Card , Vendor and System (unmount and mount again if needed) and flash NFC patch
6. Go back to the TWRP's main menu, select Reboot > Recovery.
7. Now you can perform factory reset in stock Recovery.
Note: the TWRP will remain instead of eRecovery.
MAGISK ROOT :
(Note: If you don't plan to use TWRP, simply install patched Recovery_ramdisk in fastboot mode. Run command
fastboot flash recovery_ramdisk magisk_patched-23.img ).
Install TWRP-9.1
https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
over eRecovery (it's necessary on EMUI 9.1 - Guide
( Note: for those who want keep the erecovery as a fail-safe:
https://forum.xda-developers.com/t/...-erecovery-with-twrp-installed-on-it.4357127/ )
1. In TWRP flash Mount-fix .zip file
2. Reboot into TWRP
3. Select 'Install Image' and flash
patched recovery_ramdisk
https://mega.nz/file/lp1kHLxJ#htCMaPjSsg_dy0w_jNOft-t_DZRAPwhOvwy_Wr2cjX8
over recovery_ramdisk.
4. Go back , select Reboot > Recovery.
5. Install Magisk manager apk:
https://mega.nz/file/go0m2RiR#M5UTv6FPjWPtDaGPr-u2tpJMCwdf8uwnniZg69LiGfw
(SafetyNet
Contactless payments with Magisk v23.0 )
How to boot into patched Recovery :
- Restart your phone, when appears the yellow warning on the screen, press and hold Volume Up for ~ 2 sec,
release the button and immediately press and hold again for ~ 2 sec. Repeat it 6-7 times, the device will reboot into Stock Recovery (you can perform Wipe cache or Factory reset, also you can use dload method).
ROOT WITH SUPERUSER:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
Not working: VoLTE, LED notification (at least for me)
Screenshots:
{
"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"
}

-Alf- said:
Stable enough to be used as your daily driver.
Credits: @ponces
Requirements: full stock EMUI 9.1, with stock recovery_ramdisk for "arm64-ab" (not vndklite!)
or EMUI 8 for "arm64-aonly"
Download: here
Install like any other GSI Rom including the Nfc patch.
Not working: VoLTE, LED notification (at least for me)
Screenshots:
View attachment 5350493View attachment 5350495View attachment 5350497View attachment 5350499View attachment 5350503View attachment 5350505View attachment 5350507View attachment 5350509View attachment 5350511View attachment 5350513
Click to expand...
Click to collapse
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?

Fjord1 said:
Thanks for sharing !
Is there any difference between Lineage and Pixel Experience?
Click to expand...
Click to collapse
On Pixel Exp. some things work easier and more flexible . And I don't think it's just a placebo

Thanks so much I've been looking for an android11 pixel experience for the p20 lite
Can you use magisk with this?

joenuts2124 said:
Can you use magisk with this?
Click to expand...
Click to collapse
GSI rom is not related to recovery_ramdisk, so it is possible to use the Magisk root on any GSI roms .

I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?

Incomtus said:
I was recently thinking to switch on that rom because there are no more lineageos updates.
Is there an easy way to backup and restore data from lineage to pixel?
Click to expand...
Click to collapse
Try this method
https://forum.xda-developers.com/t/migrate-custom-rom-migration-tool.4252863/
There are several options, I do not remember exactly, but I think that the best results I had with Flasher & Helper

Tried it but magisk is not working....

Incomtus said:
Tried it but magisk is not working....
Click to expand...
Click to collapse
...not at all, or for Migrate only ? And what about SuperUser?

DSU Loader not working, phone don't support?

joenuts2124 said:
DSU Loader not working, phone don't support?
Click to expand...
Click to collapse
DSU loader requires a/b partitions (two different system partitions).

-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
Doesn't emui 9.1 have ab?

joenuts2124 said:
Doesn't emui 9.1 have ab?
Click to expand...
Click to collapse
-Alf- said:
DSU loader requires a/b partitions (two different system partitions).
Click to expand...
Click to collapse
It should be clear, hm?
"AB" in GSIs is not the same thing as physically having AB partitions .
"AB" in GSIs means SAR - system-as-root ( on EMUI 9.1).
P20 Lite supports Project Treble AB, yet is an A-only device ( does not support Seamless Updates).

-Alf- said:
...not at all, or for Migrate only ? And what about SuperUser?
Click to expand...
Click to collapse
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann

Incomtus said:
Not at all, it says like if was not installed, I tried super user app and it tells like not rooted. I have almost same Magiqk issue with Andy Yann lineage but Superuser is working on Andy Yann
Click to expand...
Click to collapse
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.

-Alf- said:
IMO you are doing something wrong .
If you have followed instructions in OP to the letter, it must work. Today I tested SuperUser, also works .
Try total clean flashing - flash service ROM and try again.
Click to expand...
Click to collapse
Very strange i made a clean install,
I went back to stock 9.1.0.132 with DLOAD
I unlocked bootloader and flash the rom with fastboot, i flashed TWRP (9.1) for nfc,
I made a wipe with stock recovery, I booted again on TWRP , i flashed magisk mount fix reboot again on TWRP flashed patched recovery on recovery, and exactly same issue,
I used the same twrp for nfc and magisk. Magisk aint working on last andy Yann build either but works on Emiritein Lineage Os build ( but this one is older)
Did you tried with last build?
For Pixel I tried superuser app on fdroid but doesnt work

Incomtus said:
Did you tried with last build?
Click to expand...
Click to collapse
9.1.0.257
Incomtus said:
For Pixel I tried superuser app on fdroid but doesnt work
Click to expand...
Click to collapse
And why not the superuser linked in OP? Okay, your choice bro...
I'm afraid I can't help you anymore.

I did not see there were an Superuser app in op I was confused with Andy yann forum I made a mix with that two posts
But it is strange that magisk doesn't work if it works for you
Do I have to flag magisk AND superuser ZIP file ?

Incomtus said:
flashed patched recovery on recovery,
Click to expand...
Click to collapse
Then you need boot Recovery to get root permissions (due to patched ramdisk)
Incomtus said:
I did not see there were an Superuser app in op?
Click to expand...
Click to collapse
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"

-Alf- said:
Then you need boot Recovery to get root permissions (due to patched ramdisk)
"Root with Phh SuperUser :
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed) https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE"
Click to expand...
Click to collapse
Yes I know that I have to reboot on recovery that's what I did, as I use to do it with other GSI. But I did not understand I have to root with phh also

How To Guide Root RUI2.0 and RUI3.0 all models with Magisk

WARNING
Do it at your own risk , neither XDA nor me will be responsible for any damage that may occur
Overview
Rooting your device will give you freedom to enjoy plethora of features like removing OEM bloatwares , using system level Firewall , backing up and restoring all data of Apps , underclocking kernel for better battery life etc .
Requirements ​
Bootloader Unlocked Realme GT Neo 2 (Guide - https://forum.xda-developers.com/t/bootloader-unlocking-on-indian-model-rui-2-0-latest-a07.4391679/ )
A PC (windows or linux) with adb- fastboot installed
USB cable
Magisk Stable Apk
TWRP.img thanks to @ SathamHussainM from his thread on the same topic
Downloads ​ADB-FASTBOOT setup for windows https://forum.xda-developers.com/at...484757/?hash=78ebfa42e75a5def462676a93fff24c7
TWRP.img file link https://www.androidfilehost.com/?fid=17825722713688258515
Magisk23 apk Click here
Root Checker App link https://apkpure.com/root-and-safetynet-checker/com.atominvention.rootchecker/download?from=details
STEPS​Copy this file to your PC C:\adb folder and rename it to twrp.img
{
"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"
}
Boot your device into fastboot mode Open Command Line
Go To C:\adb folder , press shift and do a right click , select open Powershell window here
Now type
fastboot devices
, press enter it should show your device now
now type
fastboot boot twrp.img
Process will take 10 second
Your device will reboot and after some time it will show TWRP logo ( it takes time 1 min approx )
wait some time
then In PC file explorer it will show realme gt neo 2 , open it
go to internal storage > Downloads and copy paste the twrp.img file and magisk alpha apk
In twrp backup BOOT , EFS, Modem ,Persist-Image
after backup is done come back to TWRP home and tap on Install button go to the folder where you saved both the files
and select Install image button , now it will show twrp.img file , tap on it then select recovery partition and swipe to confirm flash
After process is complete press Back button and come to TWRP home
Again press install button and select magisk.apk and swipe to confirm flash , this will install Magisk 23 after process is complete press home button go to reboot tab and select system
, Now phone will reboot to system
In phone open file manager and install magisk.apk
Open magisk app it will show magisk installed
just to be sure press the install button and select direct install and press Lets GO
After process is complete press the reboot button and it will boot back to system mode now
Your phone is rooted with magisk 23 and you are eligible to enjoy variety of mods and themes for your device .

Q1) Why are you not flashing recovery directly ?
A) Becuase Its risky (very low chance of flashing failing from fastboot ),So
first we boot this twrp file temporarily and backup all important partitions
When it is clear recovery is working fine , we copy the twrp.img and flash it from twrp to make it permanent .

Q2) Why are you not flashing magisk patched image ?
Ans) Becuase Its risky (the patched boot image you got may not be of your model or software version which will cause bootloop , SO
we trust in magisk to use our device boot.img to create a patched boot.img with magisk support , then we reflash magisk from magisk App to confirm it .

Is there any way to flash stock rom if twrp is installed?

This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.

Spl1tz said:
This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.
Click to expand...
Click to collapse
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device

ultimatesprit said:
Is there any way to flash stock rom if twrp is installed?
Click to expand...
Click to collapse
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2

Email44841 said:
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device
Click to expand...
Click to collapse
Ah gotcha. And now i see bootloader unlock for all variants too. Finally!
Thank you for your hard work

Email44841 said:
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2
Click to expand...
Click to collapse
This is my first realme device.I would prefer to keep a stock rom to flash incase any boot loop. Not decided to flash twrp permanently. i hope i can boot to stock recovery and flash rollback package to be in stock..Will it work?

Is it possible to use Kernal editor app after root to undervolt/overvolt GPU?

I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?

lspgzz said:
I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?
Click to expand...
Click to collapse
sry for disturbe, i got it. Just rename the file into '.zip' and install it

Spl1tz said:
ow i see bootloader unlock for all variants too
Click to expand...
Click to collapse
Incorrect. Not all variants

can we update the magisk to latest version (stable or beta) ?

Yes
reversegear said:
can we update the magisk to latest version (stable or beta) ?
Click to expand...
Click to collapse
You can Safely update to latest Magisk releases

My twrp says "internal storage 0 MB", rui3.0 any idea how to fix this?

I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.

theogr91 said:
I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.
Click to expand...
Click to collapse
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data

RMX3370 said:
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data
Click to expand...
Click to collapse
After i unlocked bootloader i flashed ui 2 twrp to ui3 and bricked i fixed it with ofp flash sideload from twrp i can use my phone just bs on twrp

How to flash rom ,using a recovery while using an Android 12 custom rom?

My phone is encrypted so internal storage is not visible.
Every time I flash a rom it gets FAILED.
How to Flash a different custom rom?

What device are you using? Check this thread:
[ https://forum.xda-developers.com/t/disable-force-encryption.3882786/ ]
Mohit.jangra said:
Try Pitch black recovery, it automatically removes encryption
Click to expand...
Click to collapse

I got the same problem, I hope going to that link solves my problem, I'm using rmx2061.
OldNoobOne said:
What device are you using? Check this thread:
[ https://forum.xda-developers.com/t/disable-force-encryption.3882786/ ]
Click to expand...
Click to collapse

xdajbsolis said:
I got the same problem, I hope going to that link solves my problem, I'm using rmx2061.
Click to expand...
Click to collapse
Oppo Realme 6 Pro. This is an external link maybe helpful to disable force encryption on handroid device ->
[ https:||www.getdroidtips.com|download-dm-verity-forced-encryption-disabler| ]

OldNoobOne said:
Oppo Realme 6 Pro. This is an external link maybe helpful to disable force encryption on handroid device ->
[ https:||www.getdroidtips.com|download-dm-verity-forced-encryption-disabler| ]
Click to expand...
Click to collapse
I'll give it a try thanks a lot! ^_^
I went there and found the thread but unfortunately in dowloads The archive for the disabler is corrupted and cannot be open but fortunately the source github was fine, need some time to analyze this first I'm quite new to this. Thanks for earlier.

xdajbsolis said:
I went there and found the thread but unfortunately in dowloads The archive for the disabler is corrupted and cannot be open but fortunately the source github was fine, need some time to analyze this first I'm quite new to this. Thanks for earlier.
Click to expand...
Click to collapse
check if any of these attachments work, these were downloaded from the same link many months ago so they might or might not work on new models perhaps.

OldNoobOne said:
check if any of these attachments work, these were downloaded from the same link many months ago so they might or might not work on new models perhaps.
Click to expand...
Click to collapse
Thank you i will try this now.
This is my problem. Any ideas how to fix it?
{
"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"
}

> have you tried to >reboot to recovery< ?
> Are you installing ROM or GSI?
> If it is OFox problem then try in OFox FAQ section or thread or t.me
> It is showing no ROM, also if system_root error is showing then Reflash the Stock OS & redo the process to check.
> If it is ROM then OFox is not needed really TWRP also fine, OFox is recommended for Treble GSI usually.
> If it is GSI then try to Erase System Partition then reflash GSI:

OldNoobOne said:
> have you tried to >reboot to recovery< ?
> Are you installing ROM or GSI?
> If it is OFox problem then try in OFox FAQ section or thread or t.me
> It is showing no ROM, also if system_root error is showing then Reflash the Stock OS & redo the process to check.
> If it is ROM then OFox is not needed really TWRP also fine, OFox is recommended for Treble GSI usually.
> If it is GSI then try to Erase System Partition then reflash GSI:
View attachment 5641765
Click to expand...
Click to collapse
I'll give this a try thank you
The thing is I performed a backup but it became like that all the errors occured, Idk what gsi is I just flash a custom rom and it work but now have all these problems because of a tried backup. Now where to get that system. img extracted from stock rom.

xdajbsolis said:
I'll give this a try thank you
The thing is I performed a backup but it became like that all the errors occured, Idk what gsi is I just flash a custom rom and it work but now have all these problems because of a tried backup.
Click to expand...
Click to collapse
Yes , with android 11 Nandroid(TWRP) backups dont restore, its bcoz of the forced encryption thing they say, atleast that happened to me on a 2021 Samsung phone and a 2021 Redmi Note 10 phone. I will try to restore CAOS GSI Nandroid(TWRP) backup today so I'll tell you what happens.
GSI = Generic System Image
[ https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list? ]

OldNoobOne said:
> have you tried to >reboot to recovery< ?
> Are you installing ROM or GSI?
> If it is OFox problem then try in OFox FAQ section or thread or t.me
> It is showing no ROM, also if system_root error is showing then Reflash the Stock OS & redo the process to check.
> If it is ROM then OFox is not needed really TWRP also fine, OFox is recommended for Treble GSI usually.
> If it is GSI then try to Erase System Partition then reflash GSI:
View attachment 5641765
Click to expand...
Click to collapse

OldNoobOne said:
Yes , with android 11 Nandroid(TWRP) backups dont restore, its bcoz of the forced encryption thing they say, atleast that happened to me on a 2021 Samsung phone and a 2021 Redmi Note 10 phone. I will try to restore CAOS GSI Nandroid(TWRP) backup today so I'll tell you what happens.
GSI = Generic System Image
[ https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list? ]
Click to expand...
Click to collapse
I forgot i cannot erase system cause system cannot be found for it cannot be mounted im having a hard time all i need is to format all of them atleast so i can flash a rom and start a new and i observed most of the stock rom for rmx2061 specially the latest is all corrupted and cannot be flashed

Failed doest exist its not mounted and i cant erase the system ow man the struggle is real

If i will flash a stock rom will all errors go away? I was thinking about it thought for quite sometime or maybe flash a new custom rom

Just now I have successfully restored my TWRP Backup file on Shamshung Galhaxy M21 2021 Edition which was android 11 out-of-the-box. So A TWRP(nandroid) Backup is possible on android 11. I restored the CAOS GSI.
If i will flash a stock rom will all errors go away? I was thinking about it thought for quite sometime or maybe flash a new custom rom
Click to expand...
Click to collapse
Are you able to reboot to Fastboot? If you can find a correct Fastboot ROM or Stock ROM or Firmware File for your device then all errors should go away if flashed correctly with correct flashing tool.
Failed doest exist its not mounted and i cant erase the system ow man the struggle is real
Click to expand...
Click to collapse
Yes A/B devices dont show system partition, but it doesn't matter if you can get into fastboot mode and follow the GSI flashing steps I posted before you can flash CAOS/CrDroid GSI as they are as good as ROMs. But before that you need to check in XDA Device Forum if your phone is A/B partition system or A-only Partition. But nevertheless you can try flashing a GSI form the link I had posted before.

OldNoobOne said:
Just now I have successfully restored my TWRP Backup file on Shamshung Galhaxy M21 2021 Edition which was android 11 out-of-the-box. So A TWRP(nandroid) Backup is possible on android 11. I restored the CAOS GSI.
Are you able to reboot to Fastboot? If you can find a correct Fastboot ROM or Stock ROM or Firmware File for your device then all errors should go away if flashed correctly with correct flashing tool.
Yes A/B devices dont show system partition, but it doesn't matter if you can get into fastboot mode and follow the GSI flashing steps I posted before you can flash CAOS/CrDroid GSI as they are as good as ROMs. But before that you need to check in XDA Device Forum if your phone is A/B partition system or A-only Partition. But nevertheless you can try flashing a GSI form the link I had posted before.
Click to expand...
Click to collapse
Btw i cant follow the gsi flashing steps upon enetering code fastboot erase system it says partition doesnt exist.

OldNoobOne said:
> have you tried to >reboot to recovery< ?
> Are you installing ROM or GSI?
> If it is OFox problem then try in OFox FAQ section or thread or t.me
> It is showing no ROM, also if system_root error is showing then Reflash the Stock OS & redo the process to check.
> If it is ROM then OFox is not needed really TWRP also fine, OFox is recommended for Treble GSI usually.
> If it is GSI then try to Erase System Partition then reflash GSI:
View attachment 5641765
Click to expand...
Click to collapse
Since i cant erase system i proceed to flashing system img which is the caos gsi i downloaded but it gave me this error.

> What are the partitions showing up on OFox?
> Do you have any previouss OFox backups?
> Hve you checked if you have installed the latest Realme PC Drivers?
>> I think It seems like your >system partition< has been destroyed.
#NOTE:
> If you have a previous backup done, then try restoring only these partitions: System Image, Vendor Image, Product Image, Odm Image, Boot, Data(excl. storage)
> Uncheck >Enable Digest Verification of backup Files< in OFox settings option
> If restoration shows Successful message then directly reboot to system without wiping anything else
> If you have (t.me) then check in Realme device forums for any soultions or any link to your device Firmware files
You can additionally also check this thread :
[A/B][A-ONLY][SCRIPT][READ-ONLY][EROFS][ANDROID 10+] Universal Disable Force Encryption for RO and RW "NEO STABLE"
Disable Force Encryption NEO Do you all know what DFE is? no? Anyway. Basically, your device has an encrypted data section "/data" by default. Let's look at the advantages of google's solution that we will lose after disabling encryption: -...
forum.xda-developers.com
Click to expand...
Click to collapse

Something related to your issue: