Yes but you lose custom recoverySo you used the boot.img from the latest stock firmware on the Google website?
![]()
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
After pulling the boot from it, you patch it through magisk and flash it. This will give you root so you can use fkm or exkm app or kernel flasher to flash radioactive or kirisakura kernel and after reboot, you should still have root.
tbh i think its worth it
It happens to me occasionally but I've never thought of it as "an issue"Is anyone having the weird issue with the fingerprint scanner where it stays after unlocking for a little while (the white light under the screen) doesn't happen often but it's fairly regular
yeah, was more worried it was my device then the rom glad that it isnt my phone dyingIt happens to me occasionally but I've never thought of it as "an issue"
The phone still unlocks and it goes away within 2 or 3 seconds
No biggie, no tupac![]()
Yea I have no idea why and it's not the only rom I've experienced it on. But I did panic a bit the first few times it happened.I think we are ok though. Just a slight glitch in the matrix lolyeah, was more worried it was my device then the rom glad that it isnt my phone dying
Sometimes I can't swipe right to open google discover or swipe up to show apps. There is no obvious action that has caused this. I need to restart systemui or reboot the phone to continue.Am i really the only one who sometimes gets issues with some part of screen not working (usually after messing around with the customizations)? Cam issue seems to be known and hopefully worked on?
I've had this happen randomly as well. Usually waiting a few seconds or locking then unlocking my phone fixes it.Sometimes I can't swipe right to open google discover or swipe up to show apps. There is no obvious action that has caused this. I need to restart systemui or reboot the phone to continue.
Your not the only one. Doesn't work for me either. Done the whole shebang, nada. I've read all these posts and instructions numerous times. Root always gets lost on both kernels.I know very well how to perform such an action, thanks for the explanation anyway. Just did it as you suggested but unfortunately nothing. Make sure you have the rom as well set to a and b. Try again soon. Thanks anyway guys.
Same here ive been trying for over an hour followed step by step. when i tried flashing the stock nov boot.img with magisk patched i got stuck at the google logoYour not the only one. Doesn't work for me either. Done the whole shebang, nada. I've read all these posts and instructions numerous times. Root always gets lost on both kernels.
Same hereSame here ive been trying for over an hour followed step by step. when i tried flashing the stock nov boot.img with magisk patched i got stuck at the google logo
Have you been using the "fastboot flash boot rooted_novstock.img" ? Or else when you boot the boot.img, you'll have to manually go into magisk, get it to direct install then flash your kernel.Same here ive been trying for over an hour followed step by step. when i tried flashing the stock nov boot.img with magisk patched i got stuck at the google logo
I spoke to OP only a couple days ago and he didn't mention he wasn't supporting the room anymore.. we'll have to wait and see.Did I read somewhere that to Op no longer has the 6 Pro? If that is true will he no longer be supporting this rom?
Alright ill be trying again later todayHave you been using the "fastboot flash boot rooted_novstock.img" ? Or else when you boot the boot.img, you'll have to manually go into magisk, get it to direct install then flash your kernel.
I've done both methods and can safely say they both work. I'm sat here with kirisakura 4.3.0 and still retaining root.
Since so many people are facing problems, It would be great if someone could post a step by step procedure. And especially since the ROM update might drop soon (hope fully) and users could then flash with the new kennel.Have you been using the "fastboot flash boot rooted_novstock.img" ? Or else when you boot the boot.img, you'll have .....4.3.0 and still retaining root.
That's exactly what I and others have been doing. Still a no-go.If you want to use a custom kernel and keep root You can't magisk patch the boot.img that comes with the ROM and then flash a custom kernel. Root will not be kept.
You have to grab the boot.img from the Stock Nov Google Image and Magisk patch that.
Then fastboot flash boot magisk_patch-xxx.img.
Then once you boot into the phone you can use EKM or kernel flasher to flash a custom kernel and root will be retained
actually can some one provide a link of the older version of this rom? The older versions are more stable. like 7.0
nope go on telegram search raviole ricedroid
Don't let anyone discourage you, you're doing a good job contributing with your time and effort to the community, just ignore trolls and keep doing what makes you happy.Have been off for a bit, will follow up later after work. For the person complaining about building a new build, rice has not made any changes since that build, what exactly should i build a new build for?, also the other roms has multiple builds except evo-x due to me not getting a chance to look at the camera bug. Not sure why some users are getting a battery drain, i am not getting any whatsoever, also someone else that tested prior to me uploading also is not getting any battery drain. Will look at the other responses later.