Database Users

[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z

{
"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"
}
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
It should work when you flash it, but using it is still a try at your own risk procedure.
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
So, you must be sure to keep /system in ReadOnly mode in TWRP and don't try to alter it unless you're using a custom Kernel/boot to disable verity.
Of course, custom ROMs come with custom boot, so no worries about verity security with Lineage or AOKP for example.
Click to expand...
Click to collapse
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on moto.shreps.fr.
Changelog:
twrp-3.0.3-n2-athene_shreps.img
- Kernel and boot update - should be compatible with more variant
- Some TWRP fixes
twrp-3.0.3-n1-athene_shreps.img
- Qseecom and crypto stuff updated to N
> I'm able to decrypt my /data partition (F2FS) - Tested on XT1650-03_NPL25.86-17-3
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- Removed cursor pointer
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z, Tool/Utility for the Moto Z
Contributors
Shreps
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2017-01-30
Last Updated 2017-03-07

[ROOT] How to root with latest N firmware NPL25.86-17-3
Simple procedure:
Unlock your BL
Flash this TWRP Recovery
Download the superuser zip (thanks to phh)
Flash it through TWRP
Reboot
Install phh's SuperUser app from play store
Enjoy

Shreps said:
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
Click to expand...
Click to collapse
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again

erfanoabdi said:
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
Click to expand...
Click to collapse
Use superuser systemless root, has mentionned in post #2. It's safer.

Shreps said:
Use superuser systemless root, has mentionned in post #2. It's safer.
Click to expand...
Click to collapse
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser

erfanoabdi said:
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
Click to expand...
Click to collapse
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser

[email protected] said:
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
Click to expand...
Click to collapse
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser

erfanoabdi said:
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
Click to expand...
Click to collapse
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2

Shreps said:
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Click to expand...
Click to collapse
Currently I'm using phh without any issue but FlashFire doesn't work with this, it requires SuperSU

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP

erfanoabdi said:
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
Click to expand...
Click to collapse
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA

kethsawant said:
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
Click to expand...
Click to collapse
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
I tried that in Stock rom but ended up in bootloop..

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)

kethsawant said:
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
Click to expand...
Click to collapse
OK use my TWRP and flash this super su
This is not modded version just old version of stock superSU
Please test it and tell how is it.

Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.

paulnorinn said:
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
Click to expand...
Click to collapse
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.

Shreps said:
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Click to expand...
Click to collapse
Ok, thats fix it. I can now touch the screen. Guess I have to do it on every boot?
Thanks for the tip.

OK I formatted my partitions in twrp and it was formatted as ext4. I read somewhere that the moto Z uses f2fs by default. Is this true and I just reduced performance of my phone because of a bug in twrp? I couldn't find an option to format as f2fs.

Perform the update without losing the root

Hi,
I would like to do the last update for the Mi A1, but without losing the root. I'm rooted with CF-Auto-Root and SuperSu is installed without TWRP. How can I do? Possible with FlashFire?
Thanks.

AFAIK it isn't possible. There is a feature in MagiskManager that lets you root the OTA update in the second slot but its not working for our device yet. The same goes for FlashFire.

Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.

So, I too rooted my phone using the CF-Auto-Root. I tried to unroot through SuperSU, but it didn't work. I also tried to flash the boot.img, and that didn't work either. I'm new to all of this, and I don't really know what I'm doing.
How can I actually unroot this sucker?

What do you mean by it "didn't work"? What steps have you tried? You're not supposed to flash the CFAR boot.img, instead you should use `fastboot boot boot.img` to boot into it (don't do anything after it's run, it'll automatically boot), use FlashFire to flash the zip version of SuperSU (found here http://supersu.com/download), and then reboot normally on the phone.

justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
After the full unroot, all the apps that had access for root (eg. Viper4Android, BusyBox, SELinux, etc) will working again after the update?!
http://techintouch.it

The apps will work once the system is rerooted, but you'll need to authorize the apps in SuperSU again.

Can I use the SuperSu OTA survival mode? Maybe it works?

Ok, so here's what I did.
I followed kraatus90's guide to using CF-Auto-Root. I ran the .bat executable, and I rooted my phone. Everything works. I downloaded SuperSU from the Play Store to manage the apps.
I then tried to lock the bootloader, and got the "The system was destroyed" error. So, I had to unlock it again for the phone to function.
I went into the SuperSU app and tried to do the full permanent unroot, but all I got was "Uninstallation Failed"
So, then I went to find a stock boot.img, and got one.
Now, I don't know how to reverse what I did.
I tried booting into the stock boot.img from fastboot mode, and it looked like it worked because my rooted apps spotted working, but I wasn't able to download the latest security patch.
Those are the steps I did, and I don't know how to proceed further.
EDIT 1: So, after toying around with it some more, and trying to recover the stock.img in both FlashFire, and SuperSU, and trying to flash an external stock.img through fastboot, I think I know what the problem is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think that the A/B partitions are what are getting me in trouble. Do I need to change the active partition through fastboot? do I need to flash something to one of the partitions through FlashFire? What can I do?
EDIT 2: So turns out, you need to use fastboot flash boot_b boot.img, and then it'll work.

Can I flash the OTA file with FlashFire without losing root? I don't have TWRP installed and I'm rooted with SuperSu.

justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data

kkn14 said:
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
Click to expand...
Click to collapse
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp

DeV91 said:
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
Click to expand...
Click to collapse
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?

kkn14 said:
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
Click to expand...
Click to collapse
i didnt read the whole thread, but i didnt find a january oreo boot image there.
only flash a patched boot.img that is from the current build you are on.
anyway, you could try to simply boot the patched boot.img with fastboot:
fastboot boot patched_boot.img
while this may boot the system without problems, things like not being able to activate wlan could happen. because this boot image was for a different build.
however, as long as it boots the patched image, you could then simply go to magisk manager and press install direct (recommended method) - this way it will patch your stock boot image, modfying your partition directly. remember: you only "booted" the patched boot image before with the "fastboot boot" method, this will only "load" the boot.img in to memory, and will not modify your actual partition.
another way would be to just boot into twrp revovery and flash the newest magisk on your own. i'd recommend this method as you will not risk in flashing a wrong boot.img from a different build version
fastboot boot recovery.img
as long as you just boot stuff, this will only be loaded into RAM, which is a volatile memory and will be lost on a reboot - hence not modifing partitons and maintaining the possibility of taking OTAs.

[OFFICIAL] OxygenOS 9.0.6 FINAL Stable (Android 9.0) for OnePlus 3/3T

{
"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"
}
Hi everyone!
We are starting to push the incremental roll-out of OxygenOS 9.0.6 for both the devices.
[Changelog]
System:
Updated Android security patch to 2019.10
General bug fixes and improvements
Updated GMS apps
For those who were on previous versions for OnePlus 3 and 3T, we appreciate your active feedback and attempts to reach out to us. With your help, we have been able to better optimize and improve several key areas. Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.com/feedback/
This OTA will have a staged rollout, the OTA will be received by a limited number of users initially and will have a broader rollout in a few days after making sure there are no critical bugs, so using VPN to download this build might not work as the rollout Is not based on regions and is randomly pushed out to a limited number of devices.
This will be the last update for these two devices and we can't thank you enough for your invaluable feedback throughout these three years. With your support, we improved Oxygen OS across three major Android versions and dozens of updates. This is not the end for the OnePlus 3 and 3T, though. Starting next week, we will start highlighting some of the great work done by the developer community, for those of you considering to have a go at Custom ROMs.
Your feedback is appreciated. Hope you enjoy and let us know how you feel about the update in the comments below.
Never Settle :fingers-crossed:

Downloads
OOS 9.0.6 for OnePlus 3T
MD5 : e4e46aa9eebffdd485071383dcda4218
OOS 9.0.6 for OnePlus 3
MD5 : 7c2a1e83ac1a83a3ceb287983496549b
OOS 9.0.5
OOS 9.0.5 for OnePlus 3T
MD5 : ba020a5047f6a166853ec77486f2fd62
OOS 9.0.5 for OnePlus 3
MD5 : f7e17059507758b90dd9709d24e243bb
Official TWRP 3.3.1-0
ROOT: Magisk

Installation Methods
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Important Note: If your device’s Bootloader is Unlocked, then installing this firmware will factory reset your phone as this is a firmware upgrade. All your personal data and app data will be wiped clean! So backup before flashing!
Download the necessary files from the post above and follow as below.
********************* For OOS Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3/3T is now running on the latest OxygenOS firmware & OS based on 9.0 Pie :fingers-crossed:
PS: The first boot may take some time so keep calm and wait for it to boot.
************************ For OOS users with TWRP and unlocked Bootloader************************
NOTE: This dirty flashing method is from the users who tried it and were successful. Please backup to be on safer side.
1. In TWRP, wipe cache & dalvik
2. Flash OOS Full Rom Zip
3. Flash Magisk for Root access (Optional)
4. Reboot to TWRP (to retain recovery as TWRP)
5. Reboot to system
************************ For Custom ROM Users with TWRP Recovery************************
Download the required files from Post 2
Once you have downloaded all the required files on your device, please follow as below:
Backup your phone storage contents to an external mass storage as everything will be wiped.
1. Reboot to TWRP recovery
2. Wipe Dalvik , System, Data & Cache
3. Format Data partition - system will be encrypted (this is a must else system will not boot the new Android version)
- Now your phone has been completely wiped. Copy the zip files to your phone by connecting to your PC/laptop while still in TWRP
3. Install Menu > Select OOS Full Rom Zip > Swipe to Flash
4. Flash Magisk for Root access (Optional)
5. Wipe Dalvik & Cache
6. Reboot System and enjoy latest OxygenOS based on 9.0 Pie :fingers-crossed:
PS: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.

Want to get rid of DM-Verity/Force Encryption? Check this THREAD

what is adaptive display mode ??

Hey i recently both a one plus 3t and rooted it how do i know which roms support sah charging and which do not?
i want to flash the latest nitrogen oreo 8.1 does that support dash charging?

ak_bagade said:
Hey i recently both a one plus 3t and rooted it how do i know which roms support sah charging and which do not?
i want to flash the latest nitrogen oreo 8.1 does that support dash charging?
Click to expand...
Click to collapse
fyi, almost all roms support dash charging. you are good to flash any rom
Sent from my OnePlus 3T using XDA Labs

VKD L!NK!N said:
what is adaptive display mode ??
Click to expand...
Click to collapse
looks like OnePlus copy pasted the update details from OnePlus 5 and forgot to remove the adaptive screen calibration which is not available for us. LOL
Sent from my OnePlus 3T using XDA Labs

@Siddk007 Flashing magisk right after 5.0.1 will make twrp stay as before? I always lose it after flashing oos

Siddk007 said:
Downloads
OOS 5.0.1 full zip : Gdrive
Blu_Spark TWRP
ROOT: Magisk OR SuperSU
Warning : Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Click to expand...
Click to collapse
Are you sure Magisk 15.1 is fine to be flashed with Rom 5.0.1 ?
Have you tried this yourself?
There are many posts mentioning bootloops because of this magisk version
Unleashed by my rooted OP3T in 8.0

Nice someone opened a new topic.
OP3T is still a beast

My OP3T is on OOS 4.5.1. It is rooted with Magisk 14.0. I have twrp version 3.1.1-x blu spark v38 . I want to update to the latest OOS 5.0.1. Can anyone give me advice on the steps to take and which versions I need of everything? I don't want any bootloops...

conephall said:
My OP3T is on OOS 4.5.1. It is rooted with Magisk 14.0. I have twrp version 3.1.1-x blu spark v38 . I want to update to the latest OOS 5.0.1. Can anyone give me advice on the steps to take and which versions I need of everything? I don't want any bootloops...
Click to expand...
Click to collapse
You need to get blu_spark TWRP 3.2.1.x (v8.61)
And to avoid problems, I suggest you go for Magisk v14.6. I myself am on Magisk v14.6 and didn't face any boot loop. And, to be on safer side, do take backup of all your data
Sent from my #FlagshipKiller 3T using Tapatalk

Hi,
thanks for this hint! Using Magisk 14.6 did the trick for me, combined with the blu_spark TWRP 3.2.1.x (v8.61) and wiping Dalvik/Cache.
After the first start, I ran the update to Magisk 15.1 directly in Magisk Manager and it also worked.
Every try befoe that led to a non starting system that got stuck in the OnePlus screen.
BR,
Matthias

matmike said:
Hi,
thanks for this hint! Using Magisk 14.6 did the trick for me, combined with the blu_spark TWRP 3.2.1.x (v8.61) and wiping Dalvik/Cache.
After the first start, I ran the update to Magisk 15.1 directly in Magisk Manager and it also worked.
Every try befoe that led to a non starting system that got stuck in the OnePlus screen.
BR,
Matthias
Click to expand...
Click to collapse
Can confirm same behavior with phone getting stuck on boot logo when updating with 15.1 but succeeding with 14.6.

tal123 said:
@Siddk007 Flashing magisk right after 5.0.1 will make twrp stay as before? I always lose it after flashing oos
Click to expand...
Click to collapse
after flashing oos in twrp, reboot to recovery not system, flash magisk. then reboot to system. twrp will stay
Sent from my OnePlus 3T using XDA Labs

RASTAVIPER said:
Are you sure Magisk 15.1 is fine to be flashed with Rom 5.0.1 ?
Have you tried this yourself?
There are many posts mentioning bootloops because of this magisk version
Unleashed by my rooted OP3T in 8.0
Click to expand...
Click to collapse
well, i have not tried myself but some have reported that magisk 15.1 works. let me confirm again. else i will update OP with 14.6
have u tried to unmount system prior to flashing magisk 15.1?
edit: 15.1 works if after rebooting oos and then flashed
Sent from my OnePlus 3T using XDA Labs

Siddk007 said:
Installation Methods
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Download the necessary files from the post above and follow as below
PS: Dirty flash is fine if you are running a previous OOS version or any rom based on OOS, else if you come from a custom rom Clean Flash is recommended.
********************* For Stock Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3T is now running on the latest OxygenOS 5.0.1 firmware & OS based on 8.0 Oreo :fingers-crossed:
PS: The first boot may take some time so keep calm and wait for it to boot.
* After flash is successful go back to recovery and a wipe of cache is recommended.
* If in any case flash is unsuccessful the system would prompt you to download the full 1.4GB zip.
* Download that and follow the same process as above.
************************ For Rooted Users with TWRP Recovery ************************
Download the required files from Post 2
Once you have downloaded all the required files on you device, please follow as below
1. Update TWRP to the ones provided above by flashing the downloaded image
2. Reboot Recovery and Take a Nandroid of your existing ROM
(Note: Nandroid from 3.0.4-1 cant be restored on older version or and visa-versa)
3. Wipe > Advance Wipe > Select Dalvik & Cache > Swipe to Wipe
4. Install Menu > Select OOS 5.0.1 Full Rom Zip > Swipe to Flash
5. Flash the provided SuperSU/Magisk to maintain root (Optional)
6. Wipe Dalvik & Cache
7. Reboot System and Enjoy OxygenOS 5.0.1 Firmware & Latest OOS based on 8.0 Oreo :fingers-crossed:
The first boot may take some time as the system would boot twice due to flash of supersu so keep calm :fingers-crossed:
PS: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Click to expand...
Click to collapse
Can magisk be flashed after rebooting the rom? I tried flashing rom and magisk at the same time and it was stuck at the 'powered by Android' screen for about 7 minutes.

goodoldie1996 said:
Can magisk be flashed after rebooting the rom? I tried flashing rom and magisk at the same time and it was stuck at the 'powered by Android' screen for about 7 minutes.
Click to expand...
Click to collapse
yes, flash magisk after rebooting the rom
Sent from my OnePlus 3T using XDA Labs

Siddk007 said:
well, i have not tried myself but some have reported that magisk 15.1 works. let me confirm again. else i will update OP with 14.6
have u tried to unmount system prior to flashing magisk 15.1?
edit: 15.1 works if after rebooting oos and then flashed
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
What do you mean?
If you flash the Rom and then you reboot without flashing Magisk,then you will lose the custom recovery.
In this case not only you wont be able to flash Magisk, you will have the stock recovery and you will have to start the whole process from scratch
Unleashed by my rooted OP3T in 8.0

Realme X2 Pro Root | RUI 1.0 | C.38 | Custom Recovery | Magisk Canary | SafetyNet Pass | FP

~*~ Disclaimer: I'm not responsible if you destroy your device or break your warranty. Use at your own risk! ~*~
Update your Realme X2 Pro with C.38 with System Update or download the file specific for your device CN/IN/Global and simply opening the ozip file in your File Manager. Latest RUI Updates since c27 and Magisk Canary fixes FP which used to break when rooted. Magisk 20.4 gives issues with RUI and custom roms
Official TWRP for Realme X2 Pro which is also maintained by Mauronofrio is not the same as unofficial TWRP 3.4.0 by Mauronofrio which is given below. Use only as mentioned in this post. Official TWRP has issues when flashing ozip.
​If TWRP 3.4.0 by Mauronofrio or OrangeFox Recovery for realme X2 Pro is already installed. Repeat these steps for every RUI Update. Thanks @minoccio​
Install c38 update ozip with TWRP and dont reboot to avoid bootloop/softbrick
No need to wipe any partition (Dirty Flash)
[Not recommended] Reboot only if its needed to automatically replace the custom recovery with stock by not installing modified vbmeta or not rooting the device by installing magisk.
Install vbmeta.imgwith TWRP by selecting vbmeta partition.
[This step is essential to have TWRP persistent by not getting replaced with stock recovery and also to avoid bootloop]
Install Magisk Canary - Rename apk tp zip and flash (Optional only if root is required)
Reboot to System (May take 5-7 minutes to complete booting)
Follow the below procedure to root RUI or to replace stock recovery
Make sure the bootloader is unlocked. click here for Unlock Procedure
Boot to fastboot(power off device and hold vol- and power)
Install latest TWRP or OrangeFox in fastboot with a Windows PC. Use Minimal ADB Fastboot v1.4.3
TWRP - Download: TWRP 3.4.0-0 Thanks @mauronofrio
Code:
fastboot flash recovery twrp-3.4.0-0-RMX1931-mauronofrio.img
OrangeFox - Download: OrangeFox-R10.1 Thanks @Jerry08
Code:
fastboot flash recovery OrangeFox-R10.1_1-Unofficial-RMX1931.img
OrangeFox Recovery for realme X2 Pro - Download: OrangeFox-R11.0_1-Stable-RMX1931 Thanks @Jerry08
Code:
flash OrangeFox-R11.0_1-Stable-RMX1931.zip in custom recovery
Reboot to Custom Recovery
Install VBMETA with Custom Recovery - To avoid bootloop or softbrick your device and to make custom recovery persistent.
Download: VBMETA
Flash Magisk Canary - Download to your device.
Download: Magisk Canary module[12.1 MB]
Rename the .apk file extension to .zip, for example: Magisk-v22.0.apk → Magisk-v22.0.zip. If you have trouble renaming the file extension (like on Windows), use a file manager on Android or the one included in TWRP to rename the file. Thanks @topjohnwu
[*]
{
"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"
}
Get Magisk Canary Uninstaller to your device as a precaution to uninstall magisk canary by flashing this uninstaller zip file in custom recovery in case of any issues or bootloops related to Magisk.
Download: Magisk Canary Uninstaller [2.54 MB]
Reboot to System (May take 5-7 minutes to complete booting)
New Magisk Canary app will be installed automatically in few seconds
Update Magisk Canary app
Download: Magisk Canary app [9.45 MB]
Uninstall any previous old versions of magisk
Open Magisk Canary app
Click Gear button on the Right Top Corner
Under section Manager click Hide Magisk Manager
Enter any new name of your preference
Modified Magisk manager will be installed
Under Magisk section, enable MagiskHide Toggle
Go Back to Magisk home and click shield icon present at the bottom
Go to MagiskHide - Enable toggle for all banking apps/Google Pay/apps which fail when rooted
Go To SafetyNet - It would Pass basicIntegrity and ctsProfile in basic evaluation mode with Success message.
Note: SafetyNet in canary build passes in stock roms above (C.28) and custom roms still have to use Magisk V20.3
Troubleshoot:
Recover from Black Screen of Death (BSoD) or stuck with realme logo on boot
Can follow the following instruction(s) in any order
Hold Vol+ and Power button till it restarts (more than 10 seconds)
Work in Flashboot to Flash or Wipe anything as per your requirement.
Try flashing Custom Recovery
Flash Magisk Uninstaller if issue related to Magisk
Download: Magisk Canary Uninstaller [2.54 MB]
Check if there are two magisk app installed then Uninstall only the newly magisk app installed which was the result of flashing the magisk module.

Cool! Thanks.

Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.

Rj_Param said:
Install VBMETA with Custom Recovery only if the Factory Recovery was replaced with Custom Recovery -
i am little confused you already said to flash custom recovery, so stock recovery is going to replace anyways.
Click to expand...
Click to collapse
Install vbmeta only when you replace stock recovery with custom recovery. If custom recovery is previously installed with vbmeta, they don't need to install vbmeta again.

I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?

adsubzero said:
I want to update to c28, but I'm already rooted on c27 and with Fox recovery. I need to install the newest TWRP to be able to flash the ozip, so do I only need to flash the TWRP image (over the fox image) or are there any extra steps?
Click to expand...
Click to collapse
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.

hack-os said:
You could install update just by opening the c.28 update ozip in your file manager.
You could also install twrp and update to C28 but anyway your custom recovery will get replaced with stock recovery. Again you will be required to install custom recovery if necessary.
Click to expand...
Click to collapse
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?

I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure

adsubzero said:
I remember reading that you can't install the ozip via file manager method if you have a custom recovery, are you sure it can be done safely?
Click to expand...
Click to collapse
Yes when you have custom recovery then you cant install ozip directly from file manager but when you click the ozip in file manager, it takes you to custom recovery if not de-bloated and its completely safe

minoccio said:
I updated from c27 rooted to c28 rooted without reinstall twrp. My procedure:
install UNOFFICIAL 3.4.0 TWRP by Mauronofrio (official 3.4.0 doesn't work for this) -> install c28 ozip (within twrp) -> install vbmeta.img - > install magisk 20.4 (if you want to retain root). Only reboot at the end of procedure
Click to expand...
Click to collapse
Yes you are right, the custom recovery stays only if modified vbmeta is installed if not gets in bootloop.
I suggested this procedure because it is safe for everyone who initially have stock recovery or custom recovery

Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0

nkbhr said:
Guys, please help.
I have to update to twrp 3.4.0 from twrp 3.3.1
Do I need to flash vbmeta patcher after flashing twrp 3.4.0
Click to expand...
Click to collapse
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.

hack-os said:
Mostly you dont need to install vbmeta again since vbmeta and recovery partitions are technically different. if it bootloops then install vbmeta.
Click to expand...
Click to collapse
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.

Magisk hide keep failing
Please help

nkbhr said:
Thank you my friend. I was able to successfully flash twrp 3.4.0. Can you also tell me what partitions to backup in twrp for a proper nandroid backup.
Click to expand...
Click to collapse
Data and system partitions enough imo

Series of the nightfall said:
Magisk hide keep failing
Please help
Click to expand...
Click to collapse
Did you enable magiskhide in settings? Check op for attached images

hack-os said:
Did you enable magiskhide in settings? Check op for attached images
Click to expand...
Click to collapse
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.

hack-os said:
Data and system partitions enough imo
Click to expand...
Click to collapse
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.

nkbhr said:
The system partition is not available for backup. Boot and data are available. Please see the photo. Thanks.
Click to expand...
Click to collapse
System image should be what you need

Series of the nightfall said:
Yup I done all as your instructions
Magisk hide manager keep failing on the rename process.
Click to expand...
Click to collapse
Uninstall magisk and try everything again. If you never missed any steps and magisk hide option to rename should definitely work on devices above Android 9.

[EOL][11] crDroid 7.8

{
"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/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
LineageOS recovery IMAGE (Download from here)
copy-partitions script (Download from here)
gapps (Download from here)
Magisk 23 for root (after first boot) - (Download from here)
First time installation:
Install stock Android 11 ROM via FASTBOOT if you're on Android 10 (NOTE: this step is irreversible!, you won't be able to use Android 10 ROMs anymore)
Reboot to fastboot
Flash LineageOS recovery IMAGE - fastboot flash boot LineageOSRecovery.img
Reboot to recovery
Sideload copy-partitions script via Apply update (this script makes sure both slots on your phone uses same firmware by copying it from active to inactive slot)
Factory reset (wipes internal storage!)
Sideload ROM zip via Apply update
Reboot recovery
Sideload Gapps (optional) via Apply update
Sideload Magisk (optional) via Apply update
Reboot to system
Update installation:
Reboot to recovery
Sideload ROM zip via Apply update
Reboot recovery
Sideload Gapps (optional) via Apply update
Sideload Magisk (optional) via Apply update
Sources:
ROM: https://github.com/crdroidandroid
Device tree: device tree url
Kernel: kernel url
Vendor: vendor url
Download:
ROM
Known issues:
Screen flickers during FOD scan
No custom recovery supported
Credits:
@Harukey - device sources, kernel
@MasterAwesome , @Vishalcj17
@FindYourSelf007 - testing
Visit official website @ crDroid.net
crDroid Mi A3 Telegram
crDroid Community Telegram
Donate to help our team pay server costs

Changelog
15.7.2021
crDroid 7.8
Gapps/Magisk recovery installation fixed
FINAL BUILD
21.6.2021
WARNING: DO NOT UPDATE FROM 12. MAY BUILD OR OLDER, CLEAN FLASH AND FACTORY RESET REQUIRED (doesn't apply for 26. may build)
crDroid 7.7
26.5.2021
WARNING: CLEAN FLASH AND FACTORY RESET REQUIRED
THIS ROM USES OSS VENDOR FROM NOW ON
Switched to OSS vendor
Built-in recovery works, makes installation and update easier
Install and update zip unified
DT2W fixed
Off-screen FOD disabled (didn't work properly anyway)
12.5.2021
crDroid 7.6
Vendor v12.0.6.0 EEA
MAC randomization
12.4.2021
crDroid 7.5
Vendor v12.0.5.0 EEA
SDcard fixed
Auto-brightness fixed
9.3.2021
we're official
crDroid 7.4
vendor updated to v12.0.6.0
off-screen FOD partially works
14.2.2021
Initial build

Tnx for your Rom <3
Good Job!

Tnx man!

Nice Rom, Bluetooth was not getting sound initially installing Ainur Narsil MK1 fixed it.

Did someone flash it from stock Android 11? I need to unlock, install TWRP and so on, directly on 11. I have one on the stock and is really bugged, thinking to change to cr to see if it improves.

guilhermoser said:
Did someone flash it from stock Android 11? I need to unlock, install TWRP and so on, directly on 11. I have one on the stock and is really bugged, thinking to change to cr to see if it improves.
Click to expand...
Click to collapse
Just flashed from stock yesterday. It's running fine, still have some bugs, extra features not working but that's not a big problem, can use as daily rom. And it's an initial build, can be improved in the future

Hi,
1. Which gapps are you using? NikGapps basic and BiTGapps are both failing signature verification on Lineage recovery. Even accepting this, the installation fails. Magisk 21.4 fails signature, but installs and works.
2. While we have these conditions (Unofficial build, no recovery decrypting the internal storage) can you consider building a Gapps version?
3. Can we flash SHRP zip when booted to Lineage recovery (via apply update)?
Thanks.

Technical said:
Hi,
1. Which gapps are you using? NikGapps basic and BiTGapps are both failing signature verification on Lineage recovery. Even accepting this, the installation fails. Magisk 21.4 fails signature, but installs and works.
2. While we have these conditions (Unofficial build, no recovery decrypting the internal storage) can you consider building a Gapps version?
3. Can we flash SHRP zip when booted to Lineage recovery (via apply update)?
Thanks.
Click to expand...
Click to collapse
1. Try openGapps
2. Most likely he won't build a Gapps version. He's aiming to go official and crDroid is against gapps build in principle. I may be wrong tho.
3. NO. Flashing any other recovery through LOS one WILL BRICK your device! Don't try it!

Technical said:
Hi,
1. Which gapps are you using? NikGapps basic and BiTGapps are both failing signature verification on Lineage recovery. Even accepting this, the installation fails. Magisk 21.4 fails signature, but installs and works.
2. While we have these conditions (Unofficial build, no recovery decrypting the internal storage) can you consider building a Gapps version?
3. Can we flash SHRP zip when booted to Lineage recovery (via apply update)?
Thanks.
Click to expand...
Click to collapse
1. I don't use gapps so can't help with that.
2. crDroid doesn't support built-in gapps so no, maybe another ROMs have them.
3. Didn't try that. I think it's safer to flash recovery img to inactive slot via fastboot and flash recovery zip from there, should install recovery to both slots.

Sairagav said:
Try openGapps
Click to expand...
Click to collapse
For Android 11? Where? Thanks.

Technical said:
For Android 11? Where? Thanks.
Click to expand...
Click to collapse
[Android 13] [GApps] NikGApps [ARM64]
Hi Everyone, Here I'd like to Introduce you with my custom Gapps package that I use on day to day basis when I flash a new Rom. As I've observed many people struggling with finding the correct version of gapps to flash, I decided to build a...
forum.xda-developers.com

Technical said:
For Android 11? Where? Thanks.
Click to expand...
Click to collapse
oops it doesn't exit yet my bad

Since the rom uses its on first time setup it doesnt ask me for my google credentials to restore my google backup.
Can I force that somehow ? I can only see my Backups in Google drive but can't restore from em.

drozo8o8 said:
Since the rom uses its on first time setup it doesnt ask me for my google credentials to restore my google backup.
Can I force that somehow ? I can only see my Backups in Google drive but can't restore from em.
Click to expand...
Click to collapse
After flashing & following the instructions, Flash the 'NickGapps Stock zip' from the recovery. That should solve your problem & you will get the default 'Google Setup', that will allow you to restore you filles & settings.

Golbinex said:
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/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
LineageOS recovery (Download from here)
gapps (Download from here)
Magisk 21.4 or newer for root (after first boot) - (Download from here)
First time installation:
Install stock Android 11 ROM if you're on Android 10 (NOTE: this step is irreversible!, you won't be able to use Android 10 ROMs anymore)
Reboot to fastboot
Switch to slot A - fastboot set_active a
Flash FASTBOOT ROM zip - fastboot update crDroidAndroid-11.0-20210214-laurel_sprout-v7.3-FASTBOOT.zip
Reboot to fastboot
Switch to slot B - fastboot set_active b
Flash TWRP image - fastboot flash boot twrp_11.img
Reboot to recovery
Flash LineageOS recovery zip
Switch to slot A - fastboot set_active a
Reboot to recovery
Factory reset (wipes internal storage!)
Flash Gapps (optional) via Apply update
Flash Magisk (optional) via Apply update
Reboot to system
Update installation:
Reboot to recovery
Flash OTA ROM zip via Apply update
Flash LineageOS recovery zip via Apply update - don't forget this step, otherwise you'll lose access to recovery!
Reboot recovery
Flash Gapps (optional) via Apply update
Flash Magisk (optional) via Apply update
Sources:
ROM: https://github.com/crdroidandroid
Device tree: device tree url
Kernel: kernel url
Vendor: vendor url
Download:
FASTBOOT ROM zip https://www.androidfilehost.com/?w=files&flid=323070
OTA ROM zip https://www.androidfilehost.com/?w=files&flid=323071
Known issues:
Screen flickers during FOD scan
FM radio is not working
No custom recovery can decrypt internal storage as of now
Credits:
@MasterAwesome , @Vishalcj17 - device sources, kernel
@FindYourSelf007 - testing
Visit official website @ crDroid.net
crDroid Mi A3 Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
Hello sir, hope you are well in the pandemic.
I'm using your rom for some time & loving it.
But, i like to indicate some cons & problems that i have faced.
First of all, in the "Installation Process"
in step 9, there should be a line added. As mentioned no twrp recovery can emulate the internal memory.
Solution: User should flash the 'LineageOS recover.zip' using the adb sideload. (entering twrp recovery, then advance, then adb sideload. Connect phone using usb, flash the zip file from the PC using SDK platform tool, command - "adb sideload <file name>". I think most of the noobs maybe having trouble, like me .)
Second, After using the OS for about sometime i have noticed some bugs (problem).
1. some error (Force close) in some apps.
2. The auto screen off doesn't turn off the display until i manually turn it off by pressing power off button. (i've tried both turning on/off always screen & ambient display, but doesn't have any effect.)
3. Video streaming gets laggy (my network is fine & the lagging happens always.)
4. The Cast tile doesn't work.
5. The bugs mentioned above by the other users above.
Sir, i love your work very well. Its a cleanest & a well furbest OS for Mi A3. I believe if you give some effort to this OS it could be the best of all. I will keep you posted for more bugs.
Peace

Used for two weeks, no trouble.
Waiting for updates.

New build is up.
we're official
crDroid 7.4
vendor updated to v12.0.6.0
off-screen FOD partially works

After update no access to external storage, recovery too.

abtogenxda said:
After update no access to external storage, recovery too.
Click to expand...
Click to collapse
Did you flash LineageOS recovery zip right after flashing ROM as it is said in update instructions? If not, switch A/B slot from fastboot, reboot to recovery and flash LineageOS recovery.