Database Develop

[Release][2022.6.26] Magisk Manager for Recovery Mode (mm)

Magisk Manager for Recovery Mode v7 202206260
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v19.0 - v25.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
- Source code
- Documentation
- Releases
- Original thread
Note: The GUI "Magisk Manager Recovery Tool" project is a different, stand-alone project.
Which is not affiliated with this CLI "Magisk Manager for Recovery Mode" project.
Edit1: Reported as working on Magisk v23.X! Updated the documentation and released a new version
Edit2: Tested and confirmed working on Magisk v25.X! Updated the module's readme, print lines, inner docs...

I might be doing something wrong but it's not working...
{
"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"
}
Poslano z mojega MI 9 z uporabo Tapatalk

mxxt01 said:
I might be doing something wrong but it's not working... View attachment 4997015
Poslano z mojega MI 9 z uporabo Tapatalk
Click to expand...
Click to collapse
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
Sorry, all clear now [emoji16]
I was just about to try in TWRP...
Thanks!
Poslano z mojega MI 9 z uporabo Tapatalk

Rikj000 said:
Magisk Manager for Recovery v5 202004170
I updated VR25's Magisk Manager for Recovery mode so it now also works with Magisk v20.X!
With this you can be at ease while trying out Android Magisk Modules.
Since if you end up with a bootloop you can just disable the module from recovery
Saved my ass many times!
Flash this in TWRP each time you want to use it, not in Magisk itself.
You can download the new release from my GitHub: https://github.com/Rikj000/mm/releases/tag/2020.4.17
Original thread: https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
Click to expand...
Click to collapse
Thanks this will be handy when experimenting some modules
Sent from my Mi A2 using Tapatalk

Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork

JamesKinds said:
Hi,
Firstly, love your work. You saved my bacon with mm on numerous occasions!
Recently tried to install the latest version via TWRP and received the following error:
Updater process ended with error: 123
Error installing zip file...
Any ideas on how to proceed. I downloaded the latest version as per your instructions.
Thanks for the ongoing support
Click to expand...
Click to collapse
Same here.
Updater process ended with error: 123

Rikj000 said:
Yes, I can see you're trying to flash it in Magisk, that's the problem.
This module needs to be flashed in TWRP!
Also it doesn't stick, each time you reboot into TWRP and you want to use it you need to install it again.
Click to expand...
Click to collapse
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
The old 2019 version sticks for me & I had no issues whatsoever installing it from TWRP on Magisk v20.x setup. I can still do /sdcard/mm from TWRP terminal & do stuff.
Sorry if I'm unable to see what's the purpose of this 'fork'.
Click to expand...
Click to collapse
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.

Rikj000 said:
Are you sure you downloaded and installed my updated version? v5 (2020.04.17)
Because that was the error I was getting with the original v4 (2019.04.04) and the reason I made this new release. Be sure you're downloading from my GitHub fork
Click to expand...
Click to collapse
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?

JamesKinds said:
Hi,
Unless I'm making a mistake, I'm using the ZIP file from here:
https://github.com/Rikj000/mm/releases/tag/2020.4.17
Am I using the wrong file?
Click to expand...
Click to collapse
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP

Rikj000 said:
Nope that should be the right file, please make sure that the zip doesnt have spaces in it's name and don't flash this in Magisk, flash it in TWRP
Click to expand...
Click to collapse
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?

JamesKinds said:
Weird, all criteria mentioned are met. Would the fact that I have an existing installation of mm perhaps trigger the problem?
Click to expand...
Click to collapse
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.

Magisk v20.4 ERROR 123 ((( for Recovery

Latest Magisk Canary, working like a charm, thanks

Rikj000 said:
Updated installer script to support the latest magisk. It's unclear to me how you managed to get v4 installed though, me and other users where having issues with it on magisk v20, check the latest comments on the original thread.
All I wanted to do was to be able to use this piece of software again since it saved my skin a lot of times already... If you don't trust my change feel free to review my commits on github, it's all open source
Other benefit to it is that the original didn't have a release / easy and clear instructions, which is the cause of this module being less popular then it should be. I hope my new release clears up that problem aswell.
Click to expand...
Click to collapse
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
I've done a couple of clean flashing in these weeks & I could install the old one via TWRP effortlessly. I'm also on Magisk v20.4 (have tried it using Magisk v20.3 & lower versions as well) & running Android 10.
IDK why you guys are facing issues...
Click to expand...
Click to collapse
Upon further inspection might be due to spaces in the zip file name. But magisk script wasnt up to date anyways. So this version will be supported in Magisk for a longer time then the original due to that.

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
Bro, uninstall all versions this mod, reboot system, boot to twrp flash zip, go in twrp to terminal write mm, write q and click enter, boot to system, reboot to twrp go to terminal and type sdcard/mm important sdcard/mm, now should work

Rikj000 said:
I guess that could be the case if your version sticks (meaning you can see it enabled in magisk manager) then I would try to uninstall it with the Magisk Manager.
And then after a reboot try to flash my version again within TWRP.
Click to expand...
Click to collapse
I found the solution to the installation error eventually. The zip itself MUST be somewhere in internal storage when flashing and cannot be in sd card or otg. And even the old mmfr zip installs for me if I place it in internal storage. So maybe include this in your post. For context, I use Android Q rom with Magisk 20.4.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Z Fold 2 5G (Snapdragon)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy Z Fold 2 5G F9160, F916B, F916U, F916U1 and F916W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download Z Fold 2 5G: f2q.
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash magisk apk in twrp.
8. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
- Haptic feedback is currently not working.
Thanks:
TWRP team
ianmacd for multidisabler and kernel commits
jesec for unlock guide
Sources:
Kernel tree
Device tree

Changelog:
29.11.2021 - Update to TWRP 3.6.0
- Add Symlinked dynamic partitions to fstab
- Update multidisabler
- fstab clean up
- Fix haptic feedback
24.07.2021 - Disable touch on fron screen, Fix USB-OTG.
17.07.2021 - Initial Release.

please help with safety net check

kabirsaad2007 said:
please help with safety net check
Click to expand...
Click to collapse
Magisk module to resets SafetyNet evalType from HARDWARE -> BASIC, fix for SafetyNet on Snapdragon/Exynos devices with hardware attestation. This module will patch original samsung keystore. For install through magisk disable all safetynet fix modules and reboot, then install my module. Or install through TWRP
Enable magisk hide in settings as well.

afaneh92 said:
Magisk module to resets SafetyNet evalType from HARDWARE -> BASIC, fix for SafetyNet on Snapdragon/Exynos devices with hardware attestation. This module will patch original samsung keystore. For install through magisk disable all safetynet fix modules and reboot, then install my module. Or install through TWRP
Enable magisk hide in settings as well.
Click to expand...
Click to collapse
thanks alot brother.really appreciate it

afaneh92 said:
Magisk module to resets SafetyNet evalType from HARDWARE -> BASIC, fix for SafetyNet on Snapdragon/Exynos devices with hardware attestation. This module will patch original samsung keystore. For install through magisk disable all safetynet fix modules and reboot, then install my module. Or install through TWRP
Enable magisk hide in settings as well.
Click to expand...
Click to collapse

afaneh92 said:
Changelog:
17.07.2021 - Initial Release.
Click to expand...
Click to collapse
enable magisk hide

Hello, my phone is f916N korea, oem unlock disapear in developer setting. I try trick change date but not working.
oem lock,kg state : normal
i try flash twrp but failed. Anyone help me?

toraj13 said:
Hello, my phone is f916N korea, oem unlock disapear in developer setting. I try trick change date but not working.
oem lock,kg state : normal
i try flash twrp but failed. Anyone help me?
Click to expand...
Click to collapse
Pay off your device price. Its locked by knox

afaneh92 said:
Pay off your device price. Its locked by knox
Click to expand...
Click to collapse
Thanks for reply, I buy phone used from seller, what can i do?
I'm not living Korea

toraj13 said:
Thanks for reply, I buy phone used from seller, what can i do?
I'm not living Korea
Click to expand...
Click to collapse
I cant help with that.

Hello,
when i try to flash with vbmeta i got Secure Checl fail : vbmeta
any help ? thanks

xxoussxx said:
Hello,
when i try to flash with vbmeta i got Secure Checl fail : vbmeta
any help ? thanks
Click to expand...
Click to collapse
What device?

Samsung Galaxy Z Fold 2
F916W
can someone help me in private ? exchange for $$ or everything here is free ?
thanks

xxoussxx said:
Samsung Galaxy Z Fold 2
F916W
can someone help me in private ? exchange for $$ or everything here is free ?
thanks
Click to expand...
Click to collapse
your bootloader unlocked? if not check my unlock thread link in OP

Hi,
I've sm-f916u1 xaa version (usa version)
I can't record calls
I cant merge calls and make conference call
I would like to flush my device with the version that has these two features
Do you know which csc may contain these features?
would TWRP can help me with a solution? like flushing different region CSC on top of a USA device?
Thank you for your assistance

sonic4003 said:
Hi,
I've sm-f916u1 xaa version (usa version)
I can't record calls
I cant merge calls and make conference call
I would like to flush my device with the version that has these two features
Do you know which csc may contain these features?
would TWRP can help me with a solution? like flushing different region CSC on top of a USA device?
Thank you for your assistance
Click to expand...
Click to collapse
As I answered you on telegram, need to unlock then root your device using magisk and flash my csc decoder and recording module enabler. Or editing the csc manually.

thanks a alot
it works and . it work on my tab s7 SM-T875 too... thank you so much

can someone confirm if Galaxy Watch 3 is still working with the phone after installing twrp?

mcn1970 said:
can someone confirm if Galaxy Watch 3 is still working with the phone after installing twrp?
Click to expand...
Click to collapse
anyone?

Development [ROM][CUSTOM] <<>> Polar Star Pure Edition <<>>

{
"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"
}
Polar Star Pure Edition ​​This ROM is unified for Edge S Pro / Edge 20 Pro.
Custom ROM based on Global Stock firmware
Android 13 RETAIL_T1RA33.55-15-10-1
Android 12 RETAIL_S1RA32.41-20-16-11
Android 11 RETAIL_RRA31.Q3-19-86-6
This custom ROM uses stock kernel without modification.
>>> Preliminary requirements <<<
Only unlocked bootloader
>>> What's done <<<​- Root permissions via Magisk v.26.1 (26100) Stable (Android 12 - Magisk v.25.2 (25200) Stable) ;
- Removed the restriction on writing to the system, which in Android 11 is in Read Only (r/o) mode by default, which eliminates the possibility of modifying it. In this firmware it is possible to mount the system in Read Write (r/w) mode. Encryption is preserved in this case.
- System passes SafetyNet test, device is certified;
- NFC and GPay with unlocked bootloader and Root worked!
- Cleaned and lightened the system;
- Built in additional system color accents (only Android 11);
- Updated Moto and some Google applications; Android Auto is integrated into the system;
- Removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher. In the Android 13 version of the firmware, this feature is implemented systematically.
- YouTube removed, because I use YouTube Vanced;
- Installed apps AdAway ad blocker, Audio Recorder, File Manager, Gallery;
- Ringtones, notifications, alarms sounds have been replaced;
- Mod Logo and Bootanimation;
- The button for calling Google Assistant is reassigned to the: Android 12 - camera shutter and use it to activate the lockscreen; Android 13 - camera launch;
- Beginning with the PStar_PE_A12-41-20-16-5-01 build, I slightly increased the volume of the ear speaker.
How can I turn down the speaker volume?
Use RootExplorer or similar app to delete the mixer_paths.xml file from /vendor/etc. Rename the mixer_paths.bak file to mixer_paths.xml. Restart the device.​
Click to expand...
Click to collapse
- No Warez!
What was done in the latest update (Dec, 05, 2022) :
- Updated ROM base to stock firmware version S1RA32.41-20-16-9;
- New logo & bootanimation;
- Updated Magisk to v25.2;
- Updated applications to the latest versions at the time of ROM build;
- Updated Moto Display;
- Updated Moto Widget;
- Updated Moto Audio Recorder;
- Updated Asus File Manager;
- Completely removed Google Assistant and reassigned its button to the camera shutter;
- Removed Google location history and telemetry apps;
- Removed Turbo and Wellbeing apps;
- Slightly increased the volume of the hearing speaker.
>>> Installation Instructions <<<​1. Extract the system partition images from the archive (see the Download tab) and copy them to any convenient location on your PC.
2. Reboot the device into bootloader mode and:
- If you are installing the ROM for the first time or if you want to install the firmware with all data from the previous firmware removed, then use the _flash_custom.bat executable file;
- If you want to install the ROM as an update to its previous build, then use the _update_custom.bat executable file. Then all your data and applications will be saved and the system will be updated.
3. Phone will reboot into fastbootd mode and flash installation will start automatically. When the installation is completed the phone will automatically boot into the system.
4. When the boot is complete perform the initial settings.
Spoiler: Magisk v.23001(21)
Don't update Magisk and Magisk Manager! Build Magisk (d7e7df3b) (23010) (may be and laters builts) breaks Magisk Hide and SafetyNet.
5. Do not update Magisk Manager, but install this version Magisk Manager 23001(21) in the attached files.
Then you will be asked to configure the working environment. We agree. The phone will automatically reboot after the setup is complete.
6. In the Magisk Manager Settings, disallow "Check Updates". In "Update Channel" select "Custom channel" and in the opened window indicate the link:
Code:
https://raw.githubusercontent.com/topjohnwu/magisk-files/fde0bddfc5683cc8524e323e95f6c8432fbd11da/canary.json
If you are still updating, you can rollback to a working version of Magisk using the following instructions.
-= Rollback Magisk to version 23001 (21) =-
a) Uninstall Magisk with Magisk Manager - click "Uninstall Magisk" button, select "Complete Uninstall".
b) The phone will automatically reboot at the end of the uninstall process.
c) During the rebooting process, press and hold the "volume down" button until the phone enters the fastboot mode. Connect the phone to PC with a USB cable.
d) Extract the boot_magisk.img image from the archive to the folder with the drivers adb:
Android 12 S1RA32.41-20-16_boot_magisk
Android 11 RRA31.Q3-19-86-6_boot_magisk
e) Install boot_magisk.img with the command:
Code:
fastboot flash boot boot_magisk.img
f) Boot into the system and follow steps 5-6 of the basic Instructions for installing the firmware.
>>> Notes <<<
With the update Stock base to RRAS31.Q3-19-86 the problems described below are corrected.​There is a hang-up when entering the connection settings of the NFC and Bluetooth settings. Don't worry about this. You just need to wait a little while.
There is no hang-up when you enable/disable NFC and Bluetooth via the icon from the Notification bar. This happens due to uninstalling any system applications.
>>> Download <<<
Please, don't put the ROM, or links to it, on other sites without the author's permission!
Android 13 PStar_PE_A13-55-15-10-1-02
Android 12 PStar_PE_A12-41-20-16-11-02
Android 11 PStar_Pure_Edition-19-86-6-01​

If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Now the ROM is the same for both modifications.

ROM update S_Pro_Pure_Edition. Added ROM 20_Pro_Pure_Edition.

Updated the ROM for both devices.
What's done:
- replaced the CommandCenter_2 widget with a slightly larger one;
- updated Moto and some Google applications;
- remapped the Google Assistant button to the camera shutter button;
- removed the pill (bar) at the bottom of the desktop under the dock + made a small distance from the bottom edge of the display to the dock icons and under the keyboard. Especially good on NovaLauncher.

Thanks for the ROM.
I was wondering if widevine was L3 or L1 on this.

Updated the ROM to the base RRA31.Q3-19-50.
Since 11.10.21 the firmware is unified for both versions of the phone.

Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.

rendmazues said:
Hello, @ilia3367 do you happen to have any links where I can download your custom rom aside from mega.nz. Would really appreciate if you do, thanks.
Click to expand...
Click to collapse
Nvm my request, I just have additional question. Does this rom supports OTA? When I searched online, they said that OTA will be downloaded thru playstore so I think it is possible to be supported if that is the case.

do you happen to have any links where I can download your custom rom aside from mega.nz.
Click to expand...
Click to collapse
No. I don't have any free space on my other file stores.

rendmazues said:
Does this rom supports OTA?
Click to expand...
Click to collapse
No. This ROM only supports its own updates, which will be released as Stock firmware updates become available.

Hello
Can you add "Task lock" function in recent apps screen?
I want to keep apps I often use in task list, even if I push "all clear".

Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.

ilia3367 said:
Attention users of Custom ROM or users of Root Magisk on Stock firmware!
Starting with version Magisk (d7e7df3b) (23010) the structure of this utility has changed - now Zygisk is used, but Magisk Hide was removed from the utility, SafetyNet test fails.
Read more in the Magisk thread.
For whom these features are important, but accidentally updated Magisk, I offer instructions in the first post of this thread.
Click to expand...
Click to collapse
Thanks for the tut on how to downgrade, I accidentally updated mine. I'll do the downgrading later.

ilia3367 said:
If you have requests, I can make the same ROM for Moto Edge 20 Pro.
Click to expand...
Click to collapse
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.

hello I just did the steps to be root, I succeeded. install root explore and link2sd to be able to remove apps they give me per, isos, but when I want to uninstall I can't.
root explore does not let me change to r / w and uninstallation fails and link2sd removes but reboot and this is the app.

tarshar01 said:
Yeah Sir, We need a custom rom for edge 20 pro and also how to root this mobile.
Click to expand...
Click to collapse
Now the ROM is the same for both modifications.

Naza1879 said:
root explore does not let me change to r / w and uninstallation fails
Click to expand...
Click to collapse
Are you getting Root on the Stock firmware or on this Custom ROM?
Did Root Explorer ask Magisk for permission the first time it started up?

hello, everyone! I want to know this ROM's back main camera whether support longer than 1/4s exposure by Gcam?
Now I'm using Chinese Rom. It has a serious touch screen issue, and doesn't support longer than 1/4s exposure by Gcam.

Sir, Can you make a video on how to install this on moto edge 20 pro, On YouTube and share link

Updated the ROM to the base RRA31.Q3-19-50-1 - - - PStar_Pure_Edition-19-50-1-02

[ROM][12.1][tissot][OFFICIAL] crDroid v8.4 [10.04.2022]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
Download twrpboot.img & twrp.zip in your pc (link above) and extract zip file
Hotboot twrp from your pc with command fastboot boot boot-recovery.img
Wipe system, wipe data, wipe dalvik cache
Copy downloaded rom from pc to your phone and start the installation
After installing flash twrp.zip and reboot to recovery again
Install gapps & magisk (optional) and then reboot your phone
Profit! (Enjoy your rom)
Update installation:
You can choose to update via seamless ota or use recovery mode method
For recovery update method:
Reboot to recovery from phone
Flash Rom.zip & Twrp.zip and reboot to recovery
Flash Gapps
Flash Magisk (optional) & reboot your phone
Profit! (Enjoy your rom)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: CLICK HERE
Download:
ROM CLICK HERE
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/12.0/changelog_tissot.txt
Known issues:
You tell me!
Visit official website @ crDroid.net
crDroid Tissot Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

You should try this awesome rom

That's a very nice rom, I switched from crdroid7. No crushes or freezes, only bug i found is that after a reboot lockscreen needs a few seconds to start responding. Gestures navigation is very smooth and really pleasant to use, in crdroid7 it was a bit worse. Lacks many customisation features known from previous version. Magisk works without a problem. I did not install gapps.
Good job, thanks for that

One sidenote, I don't know if it is only the case for me but after I clean flashed this rom, and flashed official twrp 3.5.2 installer afterwords, it just won't boot. What's worse, it will stuck twrp on splash screen and booting other twrp via fastboot does not help - always same issue. I tried with 3.6.0 but same problem. Maybe it's only for me?

Exmantion said:
One sidenote, I don't know if it is only the case for me but after I clean flashed this rom, and flashed official twrp 3.5.2 installer afterwords, it just won't boot. What's worse, it will stuck twrp on splash screen and booting other twrp via fastboot does not help - always same issue. I tried with 3.6.0 but same problem. Maybe it's only for me?
Click to expand...
Click to collapse
Will be fixed...

How can I flash the gapps? I am a crDroid new user

New Update is Up!
2nd February 2022
Changelog : HERE
Download : HERE
Telegram Group : HERE
OTA Pushed for Existing Users!

Thanks for the update.
OTA didn't work for me, bootloop.
Maybe something with my setup
So here is what I did.
I had to flash manually:
Got to recovery (power+vol up)
In recovery (crDroid) I flash TWRP installer
rebooted to TWRP
Flashed the zip downloaded by OTA updater (from /data).
Rebooted to recovery (crDroid recovery)
Flashed Gapps and Magisk.

It's an amazing rom, however I noticed the icons are slightly stretched vertically, since it seems to be a wider margin in the side edges of the screen. Is there any way to fix that?

Sr. Lumia said:
How can I flash the gapps? I am a crDroid new user
Click to expand...
Click to collapse
You install the ROM, reboot to recovery and then install the Gapps zip-file.

This is just an Android 12 Beta-build. When will there be an official stable build?

Seems like GPS location doesn't work. It's not connecting to SATs :-(
Maybe at next release.

zagzag99 said:
Seems like GPS location doesn't work. It's not connecting to SATs :-(
Maybe at next release.
Click to expand...
Click to collapse
Hey...jst 1 2 share my experience about the gps. I was trying to improve the gps by trying to edit the gps.conf file (read some advice on this forum), so i was editing a few line of code here and there hoping to improve the gps, it doesn't seems to work well, so i start wondering if this gps.conf file even relevant ? So i try NOT TO use it by renaming the file to .old and test it with an app from play store (GPS Reset Com - GPS Repair), installed the app, did a GPS fix from the app, went outside of my house to test ...and surprise surprise..it lock on to about 8 to 10 GPS, and now i am using Google Maps for navigation without any problem. Normally it got a fix within 20/25 sec, i hope this can help you in some ways ...

Jason Looi said:
Hey...jst 1 2 share my experience about the gps. I was trying to improve the gps by trying to edit the gps.conf file (read some advice on this forum), so i was editing a few line of code here and there hoping to improve the gps, it doesn't seems to work well, so i start wondering if this gps.conf file even relevant ? So i try NOT TO use it by renaming the file to .old and test it with an app from play store (GPS Reset Com - GPS Repair), installed the app, did a GPS fix from the app, went outside of my house to test ...and surprise surprise..it lock on to about 8 to 10 GPS, and now i am using Google Maps for navigation without any problem. Normally it got a fix within 20/25 sec, i hope this can help you in some ways ...
Click to expand...
Click to collapse
Thanks for the reply.
So you used a root explorer to just rename the gps.conf file at what path ?
And can you link the playstore app that you used to repair the config ?
Did it use root ? And produced a new file next to the renamed one ?

zagzag99 said:
Thanks for the reply.
So you used a root explorer to just rename the gps.conf file at what path ?
Click to expand...
Click to collapse
I use solid explorer, Root/vendor/etc or just do a search in root directory.
zagzag99 said:
And can you link the playstore app that you used to repair the config ?
Click to expand...
Click to collapse
GPS Reset COM - GPS Repair - Apps on Google Play
GPS tools & navigation system. Get a faster GPS fix, repair GPS problems.
play.google.com
zagzag99 said:
Did it use root ? And produced a new file next to the renamed one ?
Click to expand...
Click to collapse
Yes, my device is rooted and No, i didn't create another file, just rename the gps.conf to gps.conf.old

New Update is Up!
crDroidAndroid-12.1-20220410-tissot-v8.4.zip
Download
Changelogs
Recommended Gapps for 12L
Donate me here

Thanks. Nice to see MI A1 is still alive. Still a nice phone. Will try this rom.

upload speed indicator always show 0

General [NE2213] OxygenOS 13 C.20

[NE2213] OxygenOS 13 C.20
{
"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"
}

Full OTA Link:
[NE2213] OxygenOS 13 C.20

Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk

S /\ E E D said:
Full OTA Link:
[NE2213] OxygenOS 13 C.20
Click to expand...
Click to collapse
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks

ugendersingh said:
Hi mate if I update to this stable version using oxygen updater app from beta 2, will I loose my data? Thanks
Click to expand...
Click to collapse
I don't think, BTW have a backup from your data before install

S /\ E E D said:
I don't think, BTW have a backup from your data before install
Click to expand...
Click to collapse
Hi Mate I have tried backup using oneplus clone phone app but it doesn't backup photos and videos. Any other way of backing up data?

S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Did someone try alread this method here from android 12 updates?
Magisk OTA Update reboot directly
Hey Guys, I don't found any similar thread about this topic, so I will create a new. I have magisk installed and used OxygenOS 12.1 A.10. Today I got the first update to A.12. I did it the same way as I did on Android 11. Recover Image ->...
forum.xda-developers.com

NE2215 here; no C.20 yet for us.

2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?

beterman said:
2- Uninstall magisk (Complete uninstall) => Auto reboot <---- do i have to do this? or is that optional?
Click to expand...
Click to collapse
If you ask from me, I answer it with yes, you should do it
However someone else maybe say you skip that
You can also ask from @Prant about this

Prant said:
NE2215 here; no C.20 yet for us.
Click to expand...
Click to collapse
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL

foamerman said:
Wait 2 or 3 more days for the NE2215 we're the bastard child of the 10 pro LOL
Click to expand...
Click to collapse
Hahaha, "Global" version.

I'm having trouble extracting the boot.img from payload.bin with payload_dumper in Python. See the error below. Anyone any tips or care to upload the boot.img?
Traceback (most recent call last):
File "payload_dumper.py", line 92, in <module>
dump_part(part)
File "payload_dumper.py", line 55, in dump_part
data = data_for_op(op)
File "payload_dumper.py", line 41, in data_for_op
data = dec.decompress(data)
_lzma.LZMAError: Input format not supported by decoder
NEVER MIND:
used Fastboot enhance instead and that worked well

Hi i have a question somebody can check Viper4android working on oxygen os 13? And how to install

S /\ E E D said:
Update instruction for Root users:
1- Uninstall all magisk modules => Manual reboot
2- Uninstall magisk (Complete uninstall) => Auto reboot
3- You can only install Full OTA with Local update option (I don't recommend incremental update)
4- [Optional] After update if you need root access extract stock boot.img from Full OTA and patch it with magisk
Click to expand...
Click to collapse
Local update option disabled in update menu?

Hello, anyone can help me please ?
after the update, I patch the boot.img with magisk i have magisk_patched.img file and I flash it with the commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
after that the phone reboots in bootloader loop mode forced to reflash the original boot.img
what mistake am I making?
EDIT : sorry i find a tutorial to root :
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
it's ok with this ...

Hi guys !
Is NFC payment with google wallet working on this build ?
And battery life semme better/worst/similar to android 12 ?
I'm still with android 12 and wonder if it is worth to go for A13 now
Thanks !

Yes / better

Prant said:
Hahaha, "Global" version.
Click to expand...
Click to collapse
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.

biglo said:
I notice you keep calling 2215 the global version when its not. That may have been what most people thought in the beginning but its simply not the case. Even if you browse the one plus community pages where they release the information about these updates they are also labeling 2213 as the global version. 2215 is for North America.
View attachment 5725283
Click to expand...
Click to collapse
Exactly