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

Custom ROMs and Recovery for Realme C12

Are you disappointed to see that there are no threads in Development section of XDA?
No worries, since Realme C11, C12 and C15 MTK share similar specs, things that are made for other two devices will work in our device too.
So our Custom ROMs and TWRP etc., are at Realme C11 forum https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Flashing Custom Recovery
First backup stock recovery
If you rooted the device, then see this, else follow below.
- Connect your device to PC
- Shift + Right click in platform-tools folder and select open command window here
- Run below commands to backup stock recovery
Code:
adb reboot recovery
adb root
adb pull /dev/block/by-name/recovery
adb reboot bootloader
You will get a file named recovery in your platform-tools folder. Rename it to stock-recovery.img and place it in safe place.
Click to expand...
Click to collapse
- Download latest TWRP from here in your PC
- Download vbmeta.img from here in your PC
- Place those two .img where platform-tools is extracted.
- Rename recovery file to custom-recovery.img
- Run below commands in command prompt that you opened above
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
fastboot flash recovery custom-recovery.img
fastboot reboot recovery
Custom Recovery is not permanent when you are using Stock ROM. It will be replaced with stock recovery after you boot to Stock ROM.(See 2nd post to overcome this)
There is no Hardware button Combo like Power + Vol Up to boot to recovery mode. Only way is to use adb/fastboot or root
Spoiler
You cannot see files in Internal Storage because of decryption(FBE) is broken in OUR device's TWRP. So use External SDCard for flashing if you are using TWRP
It will be blank for 1½ minute when you boot to TWRP 3.5.0. Don't touch the screen when it is blank. Press Power Button once to wake up screen in TWRP.
Flashing Custom ROMs
- Download custom ROM from here
- Place it in your External SDCard
- Backup the things in your InternalStorage, because we are going to wipe it.
- Boot to TWRP with below command
Code:
adb reboot recovery
- Choose Wipe and select Format Data and type yes
- Go back and choose Install and choose External-Storage in Select Storage at bottom
- Select the custom ROM zip that you downloaded above
- Flash it and Reboot
- Enjoy!
Spoiler
If you get recovery bootloops, then flash stock recovery. See below post to flash stock recovery
List of ROMs for C12​Below ROMs are only for UI1. So don't flash when you are in UI2
Havoc-OS
ArrowOS
LineageOS
exTHm UI
PixelPlusUI
WaveOS
CipherOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks

How to stop stock ROM from flashing stock recovery and keep custom recovery?
To do this, you need to root your C12 with Magisk.
Flash below attached RealmeRecoveryKeep.zip in Magisk app and flash custom recovery. Enjoy it accross reboots in stock rom.
Any recovery like TWRP, PBRP, SHRP, OrangeFox etc., will work with this.
Flashing Stock Recovery
Flashing it is same as TWRP.
Below I have attached Stock recovery from A.83, but it may work with any other version of UI1.
Don't flash this in UI2
First extract the zip and flash like TWRP.
SHA1 of img is:- a6ceb27226d09d6fbe9069f5e9f5448efaa10268
Guide for Flashing Stock ROM is at https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/post-84630979
Thanks

I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.

JustAnormalGuy said:
I can't backup stock recovery. Getting this error:
adb: error: failed to copy '/dev/block/by-name/recovery' to '.\recovery': remote open failed: Permission denied
My bootloader is unlocked and I got magisk working.
Click to expand...
Click to collapse
Since you are rooted, run below commands in Termux to backup stock-recovery to internal storage.
Code:
su
dd if=/dev/block/by-name/recovery of=/sdcard/stock-recovery.img
Copy this stock-recovery.img to a safe place in your PC or External SDCard.
And also you can flash TWRP using
Code:
su
dd if=/sdcard/TWRP.img of=/dev/block/by-name/recovery

thanks a lot, i thought I got stuck with stockrom and have developer support for it

Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)

Shawmik said:
Hi!
I need to flash back my stock recovery. I have a question.
Should I flash the vbmeta.img too at first? (Just like I did while flashing twrp?)
Click to expand...
Click to collapse
It is not needed, but flashing it will not do any harm.
Thanks

hello pa i need your help i can't flash castem room and stock room there is an error in my twrp

Zeyn0101 said:
hello pa i need your help i can't flash castem room and stock room there is an error in my twrp
Click to expand...
Click to collapse
Send the error picture

I can't post a photo here, may I ask your Instagram to send a photo of my twrp error

Zeyn0101 said:
I can't post a photo here, may I ask your Instagram to send a photo of my twrp error
Click to expand...
Click to collapse
Upload at https://oshi.at/ and send here

https://oshi.at/vZrBLB

Zeyn0101 said:
https://oshi.at/vZrBLB
Click to expand...
Click to collapse
Spoiler
{
"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"
}
Follow this https://forum.xda-developers.com/t/unbrick-your-realme-c12.4260759/post-84859061

where do i get the super.img file

HemanthJabalpuri said:
List of ROMs for C12​Below ROMs are only for UI1. So don't flash when you are in UI2
exTHm UI
ArrowOS
PixelPlusUI
WaveOS
CipherOS
LineageOS
PixelExperience Plus
FluidOS
PixelExperience
Thanks
Click to expand...
Click to collapse
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?

GreatTech said:
I would like to ask if the roms above now work on Realme C12 ui2 and if it's safe to flash a custom rom? Especially Arrow OS? Why can't they be flashed on ui2? Any idea on how to downgrade to ui1 so that I can flash it with Arrow OS?
Click to expand...
Click to collapse
There is only Lineage OS for UI2 which is at https://github.com/techyminati/releases/releases/tag/1.0.2-RMX2185
Other ROMs based on UI2 will come soon.
Also if you want to downgrade to UI1 follow below steps
- Flash TWRP from https://androidfilehost.com/?fid=7161016148664786711 (Don't use other TWRP)
- Boot to TWRP
- Enable 'Skip Treble Compatibility error' in settings
- Flash ozip
- Format Data and wipe cache
- Reboot

HemanthJabalpuri said:
{Mod edit: Content of quoted post removed on request of OP.}
Click to expand...
Click to collapse
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!

GreatTech said:
Hi! Thank you for the reply HemanthJabalpuri ! I would like to ask if you know the download link for ozip? I'm familiar with the other steps on TWRP except for ozip? Would I need to download ozip on Realme C12 or is it a setting? Do you know a reliable, stable and trusted download link for ozip? I apologize for the dumb question. Thank you for the explanation btw, I appreciate it!
Click to expand...
Click to collapse
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks

HemanthJabalpuri said:
Normally, you can download latest stock rom(which is usually in .ozip format) can be found at realme website by searching 'Software update - realme' in Google to go your region specific site.
But many custom ROMs have bugs with different versions of stock rom. So suggested stock version version to be less buggy with custom roms is A.87.
All the latest and older .ozips can be downloaded at https://realmeupdater.com/downloads/archive/RMX2185/
So for A.87, here is the link for it https://download.c.realme.com/osupdate/RMX2185_11_OTA_0870_all_1TbYEnns8MEW.ozip
Thanks
Click to expand...
Click to collapse
Oh wow, nice. Thank you so much for this! I appreciate the help!

followed the steps you listed carefully, can't believe that it worked, thank you for the detailed instructions man, I successfully downgraded to realme ui1.

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: