Hi,
hopefully someone could point me in the right direction.
So I have a Kate device.
It's been unofficially unlocked ( requested code in February, still haven't received anything ), however up until this point everything was working fine.
The problem is I can't dirty update over LOS nightlies for some reason ( both via updater and manual TWRP flash ) - stuck at boot animation ( 30+ mins ) Clean flash works fine. Problem started somewhere in March builds.
I have updated TWRP and I believe I have the proper FW, since everything works when doing a clean flash.
I'm not using any custom kernels, mods or anything like that, just SU addon + opengapps.
Any ideas?
Thanks
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Denis:) said:
No idea...clean flash works...which is strange...have you tried other roms too?
For official unlock, you waited too long for code LOL. I never received any code and im officialy unlocked. You should write to them so they can manually give you permission.
You should flash via EDL latest china dev and then unlock it...
Click to expand...
Click to collapse
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
feiks said:
Haven't tried others, I enjoy using LOS
As far as unlock goes, unless this is actually the thing that is causing the issue, I'm also just fine with unofficial.
Click to expand...
Click to collapse
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Thanks for suggestion, but unfortunately it also does not help.
The only thing I haven't tried is not installing su addon at all ( when doing clean flash ), but that kind of defeats the point of having custom rom in my opinion.
Also I couldn't find any references to this ( apart from migration issues back when CM became LOS ) on LOS thread, everything seems to be working fine for everyone else, regardless of unlock or su.
Are there any other partitions that should be wiped upon clean install, besides system/data/cache/dalvik?
Simoom Sadik said:
I think it is the su addon.
after u dirty flash, do not install su addon, because your device need to build up dalvik cache.
so after dirty flashing, when the device successfully boot up, reboot to recovery again and flash su arm64 addon.
Click to expand...
Click to collapse
I don't use LOS , but what I've heard is the latest nightly has made changes to updater app so clean flash ROM and try next build & one more option is to use LOS updater from play store , make sure you have latest TWRP & it's setup after installing ROM
Sent from my Redmi Note 3 using Tapatalk
Use only ZCX twrp.
Related
Hi.
So the latest Cyanogenmod (honestly every update out of the CM update that came out on 9th Oct) builds do not work for my device. Whenever I try to boot up the device, the device just gets stuck on the bootup screen, that is the screen where you see the OnePlus logo and there's text in the lower part that says "Powered by Android", except that there is no "powered by Android" text seen.
What should I do in order to get things working?
Sorry to post this in the general thread, I am not yet high enough that I can post in the Android Development Thread.
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Loureiro said:
The latest 2 builds are only compatible with the new Marshmallow Bootloader, AFAIK.
In order to get them working, I would recommend you to flash the full OOS 3.1.3 zip file.
There is the alternative to flash a zip file to get the latest booloader and radio firmware. I haven't tested it, that's why I'm not telling you to do so.
Click to expand...
Click to collapse
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
sundhar88 said:
Yes. Just like that. But OOS 3.X.X has new Bootloader. So new TWRP should be flashed.
New TWRP : http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
And flash it as usual.
Click to expand...
Click to collapse
Alright thanks! If I face any problems I'll post again!
aamodjoshi23 said:
Alright thanks! If I face any problems I'll post again!
Click to expand...
Click to collapse
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
sundhar88 said:
Wait dude! If you're on OOS 2.X.X based ROM and TWRP, then you should flash official OxygenOS Recovery and then flash the Marshmallow ROM. And now you can flash TWRP root or flash CM13 or xposed and whatever...
Refer : http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
Yup. You need to first flash the OOS recovery and then you need to flash the OOS 3.1.3 and then again the TWRP and then you need to flash whichever ROM you want to... Been there, done that. Real pain...
aamodjoshi23 said:
I currently am running the CM 13.0 2016-10-09 build which works like it should. So should I switch to OOS 3.1.3 and then flash the new CM build?
Click to expand...
Click to collapse
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Loureiro said:
That's right.
If you don't want to do a complete wipe, you can try this method: http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
You're a lifesaver dude! Thanks for the link!!
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Adesh15 said:
No need for you to do this.
Just follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917 and then flash latest CM13 nightly.
Click to expand...
Click to collapse
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Cretandus said:
Hi all,
I’m having the exact same problem. I’ve searched several forums, and have seen different solutions, but I’m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don’t want to make any mistakes. I’m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I’m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Install opx_recovery, flash 3.1.3 from recovery. After installed you can fastboot flash Blu sparks latest or Nichets twrp done.
Cretandus said:
Okay, thanks! I'll try this and let you know the outcome. I have to install CM13 before rebooting out of TWRP, right? "Older roms won't boot" meaning my OOS 2.2.2 won't boot. Just checking...
Click to expand...
Click to collapse
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Cretandus said:
Hi all,
I�¢??m having the exact same problem. I�¢??ve searched several forums, and have seen different solutions, but I�¢??m unsure what solution to follow. The steps in this thread seem the most logical to me. But just to be clear, are this the steps I have to follow, in the correct order? I don�¢??t want to make any mistakes. I�¢??m currently on OOS 2.2.2 with TWRP 3.0.2.0.
(make backup, I�¢??m wiping the whole thing)
Copy OPX_recovery and OOS 3.1.3 to phone
Flashboot flash OPX_recovery.img (Lollipop version, not MM)
Reboot (to bootloader?)
Flashboot flash OOS 3.1.3 (from pc or from bootloader?)
Wipe Dalvik/cache
Reboot (to bootloader?)
Flash twrp-3.0.2-0-onyx-20161020-085152.img as found in post from sundhar88
Flash latest CM13
Wipe Dalvik/cache
Reboot in normal mode
Should I download and keep the CM13 recovery version too?
Your reply would be massively appreciated!
Click to expand...
Click to collapse
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
What I did was, first of all, I took the backup using Titanium Backup and took a nandroid backup. Then I already had downloaded the files required, that is the BL zip file, the TWRP recovery, and the latest CM 13.0 build. Then I went to recovery > install and then located the BL and flashed it. Then I tried to flash the TWRP recovery but it didn't. Gave an error saying, "Unsuccessful" or something on those lines.
So I took that TWRP img file and copied it on my laptop. Then I went into the bootloader, which at first I thought was a bad idea since I just flashed the BL zip, then I flashed the new TWRP img file and went to recovery mode. And it had worked. So I flashed the CM 13.0 build too and then booted up the device, and it worked!
I guess that should help
aamodjoshi23 said:
Hi there.
I tried the way these folks suggested, by updating the BL using the zip file and flashing the updated TWRP recovery, and it worked!
Click to expand...
Click to collapse
I'm glad it worked for(don't forget to drop a thanks and a vote would be good too)
Also for next time,please search the forums before creating a thread.:angel:
Adesh15 said:
After flashing the new TWRP for new BL you should reboot to recovery from reboot tab in TWRP.
Then wipe System ,Data and Cache and then flash CM13
Click to expand...
Click to collapse
Adesh15, it worked! Thank you very much!
Cretandus said:
Adesh15, it worked! Thank you very much!
Click to expand...
Click to collapse
Great !
Hello everyone, long time lurker here. I have used xda over the course of many years with many different devices, and I am extremely grateful to all of you!
I recently cam across an issue. So with my OnePlus X I had unlocked it, rooted it, installed TWRP and a custom ROM (6.x.x). I had that setup for a while, it worked well, and I enjoyed it. I decided to try to update to a 7.x rom, but that is when I had issues. Trying to install the rom through twrp didn't work, and I couldn't revert back to the old rom either. I tried to use the master unbrick thread to set it back to stock, and it worked. The problem here is the stock rom is very broken, things like the OPX home launcher simply freeze and crash. Trying to usethe guide on the oneplus website to unlock it all again to reinstall TWRP doesn't work. I can unlock it, but installing recovery is where it screws up.
So it says it installs, but then when I try to reboot recovery it has a DTB: not found...manually rebooting to recovery leaves a black screen with the oneplus square logo.
Any ideas how to fix this? I am so lost, but I love this phone!
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Exodusche said:
Fastboot flash old stock recovery from OOS2 wipe data and cache install 2.2.3 followed by 3.1.4 then make sure your flashing latest TWRP 3.0.3 from there site. Now should be able to flash Nougat.
Click to expand...
Click to collapse
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Archtects said:
Good work sir! Mind you it probably be far easier for him to just
Code:
fastboot flash recovery 3.0.3.28w/e.img
fastboot boot recovery 3.0.3.28w/e.img
And then just plonk a nougat zip onto his device from the TWRP plugged into is computer?
Click to expand...
Click to collapse
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Kéno40 said:
No because he needs to upgrade the bootloader first to have a TWRP 3.0.3 that works OK.
Click to expand...
Click to collapse
True true.
As the title says global beta 7.2.9 is out. Anyone installed it?
What about twrp and root compatibility?
http://en.miui.com/download-299.html here is the link
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
mysa50 said:
Just installed it without issue with twrp 3.0.3. no issue so far, reinstalled twrp and flash super su 2.79 without problem too
Click to expand...
Click to collapse
Can you confirm the process please? Is it just:
1. Download the recovery version of the update to the phone.
2. Boot to recovery (TWRP).
3. Install the update zip file.
4. Re install TWRP.
5. Reinstall the SuperSU zip.
6. Reboot to system.
Do we need additional reboots between the steps? Do we need to unroot before installing the update? Does it matter if the existing global beta ROM is several versions old?
Sorry for asking so many questions. I have not updated the ROM since unlocking the bootloader and installing TWRP/SuperSU several months ago and am worried about bricking my phone.
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
mysa50 said:
That's the steps i did , i first booted the rom just to be sure everything was OK before reinstalling twrp and supersu. I only had a message telling me the update wasn't successful but after installing twrp and wiping cache everything was fine. As long you install the full rom you should be fine with the update (do a clean flash to be sure). What version of Android is actually running on your phone ?
Update twrp to 3.0.3 as the previous version won't work with nougat
Click to expand...
Click to collapse
That's good to know. Just to confirm, the update could be applied "dirty" without a need to reinstall all apps and data afterwards?
I am still on global beta 6.11.3 (which is MM) and twrp 3.0.2.0. Is 7.2.9 based on nougat which would require the update of twrp? I had thought that the nougat beta was on a separate thread open to a closed group only...
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Delete
Bhatyasirr said:
Twrp 3.0.3..?? Not available for Mi5 on twrp site.. Any mirror plz..
Click to expand...
Click to collapse
Look in the mi5 developement thread There is twrp section and in the 3rd post the op uploaded a unofficial release of twrp 3.0.3 but stable enough to be considered as official.
mysa50 said:
I did a clean flash when updated to nougat (was on 6.11.10) but did a dirty flash from 7.1.19 to 7.2.9. Update to twrp 3.0.3 is highly recommended as it's updated with nougat libs and 3.0.2 won't "stick" with nougat miui.
Only the fiirst nougat build was on a closed beta but now it's open beta and can be updated via updater app.
Édit: clean flash is not mandatory i guess, i did it only to be sure to have a clean install without rogue app or incompatibility issue between mm and nougat. I use supersu 2.79 and have no issue
Click to expand...
Click to collapse
Thanks a lot. Shall try over the weekend.
Few screenshots
mysa50 said:
Few screenshots
Click to expand...
Click to collapse
This is on light use, with heavy use (games,messages,phone calls) battery last a day from 6.30 am to midnight and still 10-15% and ~5h30 sot
That's good
how to revert back to miui from LOS ?
it didnt boot up
harrez said:
how to revert back to miui from LOS ?
it didnt boot up
Click to expand...
Click to collapse
Did you try fastboot rom from xiaomi site? Give a look in the Q&A thread you should find how to revert back to miui
chan200606 said:
Thanks a lot. Shall try over the weekend.
Click to expand...
Click to collapse
Finally did it, but not without scare - my Mi5 was stuck at the boot logo with "Bootloader unlock" message screen after flashing the recovery version of 7.2.9 update and reflashing TWRP 3.0.3.0. Luckily managed to get the phone into fastboot mode to flash the fastboot version of 7.2.9 and get the phone back on again. Finally reinstalled TWRP and boot into TWRP before rebooting to system successfully.
The key step I had forgotten was the booting into TWRP after its installation over the 7.2.9 stock recovery, which had led to the bootloop.
So I now have updated to 7.2.9. I do notice that the boot process takes quite a bit longer than 6.11.3 (design of nougat?), but once up, the phone feels as responsive as before.
Hi guys,
I was running twrp 3.0.1-0 with the unofficial linage build, however once I flashed the office build I seem to have gone to what looks like a stock recovery (when you try to flash anything you get a white circle with various colours sliding in and out of phase). Whilst the OS seems fine, I can't seem to flash anything anymore, gapps, supersu etc even via ADB sideload. It will appear to flash successfully, but nothing will have worked. I can boot into fastboot still but that won't let me flash TWRP either.
I read that revoking that the USB privileges would help but when I do that I don't get any pop-up asking for privileges, even after I wiped it and flashed it again, via the stock recovery.
To be honest I could live without TWRP but without gapps (play store) I can't do much.
Any advise or help would be most welcomed.
Thanks!
spotter300 said:
Hi guys,
I was running twrp 3.0.1-0 with the unofficial linage build, however once I flashed the office build I seem to have gone to what looks like a stock recovery (when you try to flash anything you get a white circle with various colours sliding in and out of phase). Whilst the OS seems fine, I can't seem to flash anything anymore, gapps, supersu etc even via ADB sideload. It will appear to flash successfully, but nothing will have worked. I can boot into fastboot still but that won't let me flash TWRP either.
I read that revoking that the USB privileges would help but when I do that I don't get any pop-up asking for privileges, even after I wiped it and flashed it again, via the stock recovery.
To be honest I could live without TWRP but without gapps (play store) I can't do much.
Any advise or help would be most welcomed.
Thanks!
Click to expand...
Click to collapse
Official LOS doesn't have TWRP built-in, and never had, as i remember.
Use opengapps app to install gapps. For root use SuperSU.
If you still need twrp, use kernel (boot.img) from unofficial one.
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Noter2017 said:
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Click to expand...
Click to collapse
I tried the treble versions of magisk too. Even tried the beta. No luck.
Figured it out
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
So it was a problem with the treble implementation of the ROM. I was installing treble ROMs using the stock TWRP/Redwolf recovery. These recoveries install the ROM but don't work or make the /vendor partition. This has led many people to believe that there is something wrong with their phone. Anyway, flashing a custom treble recovery did the job. Although not each one of them is perfect, TWRP_3.2.1-7_mido-treble by @NFound is the best one.
Solved every problem faced by me till now. Custom Magisk for Redmi Note 4 is available and works like a charm.
Magisk-v16.3-mido-treble
It seems no one faced this issue before, anyway this would help the new comers like me.
Thanks.
Couldn't get
I am using RR ROM Oreo since 2 weeks and finding ways to root it
But can't find any way to do it
Addonsu is not working
Treble magisk is not working
I need to change my recovery
But the ROM ended up encrypting my internal storage
So should I clean data to format and remove encryption
Or I can directly install a new recovery ?
Format then wipe everything. With a help of a pc or a laptop download a treble supported recovery or the Firefox recovery(search it).Then try again.