Yes, both. And i made sure it was the canary buildAnd did you flash Magisk and the encryption disabler? Those are essential to making this ROM boot. Don't use normal Magisk, download canary.
Yes, both. And i made sure it was the canary buildAnd did you flash Magisk and the encryption disabler? Those are essential to making this ROM boot. Don't use normal Magisk, download canary.
Hmmmm that's very strange. It seems you've completed most if not all the instructions on point and still aren't booting the ROM. I wish I could be of more help, I guess my best advice would be to re-do the instructions 1 by 1, maybe you'll see something different you didn't see before. You could also join our Telegram group, maybe someone there knows something I could have missed or went through something similar.
Okay so I got it running after updating to a U3 bootloader. It now runs normal.Hmmmm that's very strange. It seems you've completed most if not all the instructions on point and still aren't booting the ROM. I wish I could be of more help, I guess my best advice would be to re-do the instructions 1 by 1, maybe you'll see something different you didn't see before. You could also join our Telegram group, maybe someone there knows something I could have missed or went through something similar.
There's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.I'm using much less bluetooth now, but since I've installed NcX 2.5.2 my phone doesn't remember the paired devices, I should pair them every time I use it, somebody had or has the same problem?
Thank you, but if I'm not wrong, with UI 2.1 I hadn't this problem. Anyway I will try the module.There's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.
I was only informed of camera issues when someone flashed the ROM when they were on OneUI 2.0. After they upgraded to U3 bootloader (One UI 2.1 or 2.5) this problem was gone. Try it, it may fix it.Would love to have this, I will wait for camera issue to be resolved.
Unless it has already been corrected.
Best wishes
My camera is broken and i was already on oneui 2.5 / U3 i try everything nothing to do im too bad for fixing it :')I was only informed of camera issues when someone flashed the ROM when they were on OneUI 2.0. After they upgraded to U3 bootloader (One UI 2.1 or 2.5) this problem was gone. Try it, it may fix it.
Worked perfectlyThere's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.
Sorry, I wish I knew how to fix it. Since the problem doesn't happen to me, there's no way of knowing how to fix it :/My camera is broken and i was already on oneui 2.5 / U3 i try everything nothing to do im too bad for fixing it :')
Ok, everything worked out. Got it installed. I didn't install 2.5 first.Oh, yeah, how come I don't see TWRP in the package? Am I doing something wrong?
Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Worked perfectlyThere's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.
There's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.I'm using much less bluetooth now, but since I've installed NcX 2.5.2 my phone doesn't remember the paired devices, I should pair them every time I use it, somebody had or has the same problem?
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA