Database Info

android systemui stopped after CM11 nightly

Seems I inadvertently killed my working CM11 opo with 9/30 Nightly
Factory Reset and wiped all data via twrp 2.8.0.1
Installed Nightly, Gapps, Gapps remover, franco r22 and cm11s app pack via USB-OTG
wiped dalvik/cache
reboot to "Unfortunately, the process android systemui has stopped working" > hit ok > infinite repeat
tried to revert to 9/25 and even the M9 snapshot to the same issue
I have a nandroid of when i first got the phone with cm11s on it but no efs backup.
I was using franco r20-updated to r21 just yesterday, Nightly 9/25 just fine with a few issues with certain apps. Figured waiting for a few more days in between nightlies would help with those issues.
Anyone got any suggestions as to what I can do to resolve this? Out of a phone at the moment so in a tough spot.

Factory wipe. Only flash CM11 nightly, flash each zip one by one. One of them is causing your phone to constantly fc.

Seems issue in last CM nightly 0930... Flash 0928 and wait for fix. Affected more (maybe all) devices.

Happened to mine as well. Though I still can't use the cm boot.img past 9/19 either lol

I flashed back 29 nightly and all works fine.

Same issue for me updating to the 09/30 nightly!

@zephiK 9/29 is offline apparently lol
9/28 seems to work (with no other zips done including gapps)

Samsung GS3 - Pulled battery to get control - boot to TWRP and installed 9/28 nightly. All is well. :good:

S5 30/09 can confirm SystemUI crash. On 28/9 atm and fully works.
Autobuilder placed bad commit and built it for all devices.

6.0.1 Update - Battery Percentage messed up

Anyone has this issue with the battery reading a ridiculous percentage?
I just updated to 6.0.1 and this shows up.

Also got this. Did you make any modifications?

The only mods that I have is TWRP, root, and Elemental kernel. But that showed up before the mods.
I don't know if this was due to flashing the update files individually. I didn't want to go the "flash all.bat" way.
Maybe a clean install will solve it.
I also noticed that access to the battery information is no longer present.
I ended up restoring back to 6.0 for now.

I also had got this but I forgot to flash kernel.
Problem solved after 6.0.1 kernel flash.

I just read that on another forum. It is related to the boot.img. I guess we would need a new modified boot.img to be able to root.

I had this too, ElementalX Kernel fixed it for me as it's been updated for 6.0.1 - http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-elementalx-n5-0-44-t2519607
I would imagine other kernels will be available soon.

Phone powers off after flashing CAF based ROMS no boot.

Hi guy,
I have been trying to figure this out for a while now and can't seam to figure it out. Everytime I flash a CAF based ROM after clicking reboot the phone turns off. During this time it is very hard to get the phone to turn back on. Holding the power button does not seam to do anything. I have to hold the power+volup+voldown for around 30 seconds let go and do it again in order to get back into recovery. I am not getting any errors at all when flashing. I really have no clue what it could be. I have tried every CAF based ROM I have come across here and they all do it. The only thing I can come up with is my phone has had the screen, camera, and battery replaced. Could one of these parts or another part be causing a problem that doesn't allow CAF based ROMS to work? I know its a long shot but thats all I can think of at the moment.
Right now I am working on trying to flash CyanogenMod from this thread. I have tried both version 13 and version 14 both have the same problem. This is what I have tried.
Flash HammerheadCAF reboot back into recovery
Flash bootloader&radio_HHZ20h+2.30.zip reboot to recovery
Flash cm-13.0-20161029-UNOFFICIAL-hammerheadcaf.zip
Flash opengapps
Flash SuperSu
Reboot
Black screen of death
What is wrong with this process? I have also tried the same process with cm-14.0-20161029-UNOFFICIAL-hammerheadcaf.zip. I am now going to try this same process with cm-14.1-20161029-UNOFFICIAL-hammerheadcaf.zip. I don't expect any difference though. Anyone have any suggestions?
Thanks,
Rocky
*****Update*****
I have tracked the problem down to CAF TWRP. I have formatted the phone which has removed everything except CAF TWRP and I am still getting the black screen of death situation. When the phone reboots it completely turns off. It will not respond unless I hold down power+volup+voldown for around 30 or 40 seconds. Then the phone will finally enter the bootloader. Are there any other recoveries that will flash CAF based ROMs? I don't know what else to do =(

Maybe don't flash supersu? Cm comes prerooted?

audit13 said:
Maybe don't flash supersu? Cm comes prerooted?
Click to expand...
Click to collapse
Thanks for your reply and time. I also tried flashing without SuperSU and it did the same thing. When I tapped reboot the phone would not turn on. I also tried just flashing the ROM and rebooting. The problem is with TWRP CAF because I have even formatted the phone so there was no ROM just TRWP CAF and when I tapped on reboot to recovery the phone just turned off. The power button wouldn't do anything. It would not even turn the phone on. The only thing I could do was hold the power+voldown+volup for 30 sec let go and press them again and go into bootloader.

Hey guys anyone else have any suggestions? I have tried sending a support ticket to twrp over a week ago. I haven't heard a word from them. I really want to use CAF ROMs

Hi!
I'm facing the same problem. I've been trying everything I can think of, and everything ended with a black screen when trying to boot:
Flashing stock again and then TWRP and CAF.
Flashing a lower version of TWRP (2.8.7.0) and then flashing CAF.
Flashing an AOSP version of CM, then TWRP for CAF and finally CAF.
Fixing permissions.
Changing filesystems to F2FS.
I tried to logcat, but adb logcat keeps waiting for the phone and it doesnt find anything.
Anybody has another idea of what could be happening or how to solve it?
Thanks!

I can flash caf, aswell as noncaf roms on my N5 just fine.
I used the CM14 darkrom CAF. Excellent performance, great battery life
i wiped the device in TWRP caf (Latest) (system,data,cache,dalvik0
Then i flashed the rom and the Darkrom gapps (use only those, as rom comes withouth a launcher. Pixwl launcher embeded into gapps package)
Wipe cahce/dalvik & reboot
It looped like: GOOGLElogo ,bootanimation ,self restart and it works perfectly fine since then
---------- Post added at 18:54 ---------- Previous post was at 18:53 ----------
I should also mention, that i use the european D821 model

I was beginning to wonder if it was just me. I felt like an ass for posting for help because I felt like it was my fault. I still have not gotten any response at all from twrp support. I really want to use car based Roms. I use to be able to when I first got the phone. Now I don't have a clue what the problem is. I am using the 820 USA model.
After doing a Google search for CAF TWRP no boot black screen and other combinations I have found posts around the web from people with the same issue. The only resolution was to revert to stock. I have sent TWRP support another email linking to this topic as well as contacted them on g+ hopefully we can get a resolution.

since i dont own the device.... no logs= we cant help you

Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...

I'm having this problem too, I can flash any non-CAF ROM and it will bootup fine, but any CAF rom will leave me in a black screen. Did you found any solution yet?

I have not been able to find a solution to the problem. TWERP tech support seams to be non existent. I have emailed them numerous times. They don't even take the time to say they will look into it =(

Dark_Eyes_ said:
Funny thing is twrp caf and non-caf are identical, the ONLY difference is that they are looking for a different device name when flashing. So I'd suggest to use the non-caf one, download any caf rom, edit the updater-script and replace every "hammerheadcaf" with "hammerhead" and it will flash just fine. If it really is just a twrp issue that will work. But I don't know why, I feel it's bound to be more than that...
Click to expand...
Click to collapse
What else could it be if we are able to flash absolutely anything else we want to flash except for a CAFE ROM?
I have never tried editting the updater script. Could you please explain how to do the things you described?

Ok I got an update. Today just for ****s and giggles I tried to flash the latest TWRP twrp-3.0.2-0-hammerhead.img on top of itself from inside TWRP using the image flashing process. I got the black screen I been getting that we are discussing here. Therefore, that tells me that the problem is not with TWRP CAF but with flash recovery's in TWRP. For some reason TWRP does not like that. Therefore, I am manually flashing the fallowing files the old fashion way by hand using the android sdk and adb.
1.) TWRP CAF
2.) The latest bootloader directly from the latest google factory image
3.) The latest radio directly from the latest google factory image
4.) Install the latest build of Dark ROM
I will report back with my findings.
Findings are epic fail. No boot, black screen of death.:crying: After holding down volup+voldown+power I am able to get back into recovery just like with flashing all the files through recovery when I first started. However, I can't get the damn thing to boot the ROM. I don't know what to think anymore. I think we just have to come to the conclusion that CAF based ROMs are out of the question for us :crying: :crying: :crying: When my son gets home and can hold the tablet while I operate the Nexus 5 maybe I will try to make a video of the problem. Hopefully this will help lead to a resolution.

Let me guess. All your phones have been repaired or are second-hand devices, aren't they?

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
will a repaired device not work, mine has had the screen replaced. Nothing else just the screen.

experience7 said:
Let me guess. All your phones have been repaired or are second-hand devices, aren't they?
Click to expand...
Click to collapse
Yup, I have replaced the screen, why is that? Is it too much different than the original, shouldn't it work normally?

Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.

experience7 said:
Not sure what's wrong with the hardware. No CAF for you guys, I'm sorry.
Click to expand...
Click to collapse
Wait seriously? because i fixed my screen i am not able to use a caf rom on my device? That seems ridiculous, what would cause that to even be a thing? is there some sort of security flag it checks for?

Yeah I replaced the screen on mine too. Not sure how that plays a role. The only thing I can think of is unless there is a missing driver or something like that because our screens are different.
There's gotta be a way to fix this problem. I wish I knew how to build ROMs, kernels, and recoveries. I don't think anyone will go out of their way to fix a problem that doesn't directly affect them. So for me it is stock, rooted, with ElementalX till this pos croaks.

Not sure what the problem is. Fact is that your screen somehow differs from the 'original' one which causes CAF ROMs to blackscreen.
If you really, really want your phone to run CAF you have to provide a lot more information. You could try to get a running system and fetch some hardware information. Pretty sure there are apps on the Play Store that print hardware brands/model names, etc. Report your results and I'll use the same method to get mine. We should compare. Furthermore we'll need logs. Try to boot CAF. Of course it will blackscreen again but you can reboot to recovery and pull some logs. Maybe last_kmsg and dmesg where the latter one should be even more interesting.
And last but not least I'd like to tag @myfluxi here. Perhaps that's interesting for you...

[DEV] I extracted the updated touchscreen firmware from MIUI Nougat kernel

Haven't managed to test if it fixes the bug because I had to sleep lol.
https://github.com/Demon000/libra/commit/b5067833797cd1eb207cd976bf2419c58ca8c7ed
If anyone can test if it works, I would be very thankful.
How I did it?
Get a hex file editor.
Compile kernel with old touchscreen firmware.
Open the synaptics_biel_sharp_update.fw or synaptic_biel_auo_update.fw that have been generated in firmware/ folder in the hex editor.
Get the MIUI kernel, split it, uncompress it.
In the .fw files, the first four hex groups are magic numbers(a hex group looks like "3F"), and after that there are some common hex groups in sharp and auo firmware.
Use the hex editor to search for the common groups in the MIUI kernel, and also find the magic number before the common groups.
Use the "csplitb" program to split the the kernel binary at the newly found magic number + common groups, and strip the result to 12661 lines.
Repeat this for every common group found.
Then use the objcopy program inside the toolchain to convert the binary files to .ihex, and replace the ihex files in the firmware folder.
Done.
It is complicated, but once you get the first steps it will be easy to understand.
Although I don't know if I did a good job at explaining.

Cozmy, you are magic. Lot of thanx, Man.

Many thanks. :good:

How does one flash this?

danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
You cannot, devs that make custom roms can use it to build rom with fixed display firmware.

danbrown162 said:
How does one flash this?
Click to expand...
Click to collapse
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.

Harrynowl said:
I can post a kernel build with it later, not tested as currently I'm working on lineage os using all the vendor binaries and blobs from the nougat release.
Click to expand...
Click to collapse
I couldn't get it to update the firmware because I was not using Xiaomi touchscreen drivers in my kernel, but the firmware itself should be working fine.
I don't want to bloat my CAF touchscreen driver so it will take me longer until I find where it fails.
Please keep us updated.

https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.

Cozzmy13 said:
https://drive.google.com/open?id=0B9WMSJf5LSatdG5WM24zNnJPaEk
Kernel image which fixes the touchscreen problem.
PS. This kernel may use more battery, just because I didn't spend time optimizing the kernel, but rather optimizing the source-code quality, lol.
You can try flashing your original kernel to see if the fix remains.
Tested on Resurrection Remix Nougat.
EDIT: I haven't tested it on any AUO panels, as my phone has a Sharp one.
EDIT2: Flashed back the Resurrection Remix kernel and touchscreen is still fixed. Success!
Guide: backup your kernel, flash the kernel I provided, restore your old kernel.
Proof as attachment.
Click to expand...
Click to collapse
I hope this gets implemented on next releases of our roms

solis_f said:
I hope this gets implemented on next releases of our roms
Click to expand...
Click to collapse
Just give the ROM maintainers a link to this, they will surely add it to the ROM.

Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.

Phlogistol said:
Holy **** You're a hero Cozzmy13, thank you!
I just tried the image on my AUO Mi4c, and I couldn't boot TS CM13 with the kernel. The fix didn't stick after restoring the original boot partition, but I have a feeling we're very close here
I'll try flashing RR later and see what I get, I have a Nandroid backup somewhere.
Click to expand...
Click to collapse
It's my fault, I compiled the image with RR ramdisk. It definitely works on RR Nougat, that's for sure. I have since switched to Lineage OS and the fix sticked.

I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.

bankov said:
I have problem . Ive installed the fix on AICP 12.1 the phone doesent boot. Returned the old kernel from backup. My phone boots but now i have problem with my hardware buttons, sometimes take 3-4 to respond to the touch. I also deleted and flashed system partititon but problem stil presist.
Click to expand...
Click to collapse
Is the touchscreen problem fixed? If it's not then this is not my fault. If it is fixed then it's XIAOMI's fault. I will test on my device and report back. Use on-screen buttons until I do some research.

The problem was not in your update. It was from the last AICP update 23.01.2017 i installed 19.01.2017 and buttons are fine now. The touchscreen seems to be fixed iven with full wipe, going back to miui and restoring 19.01.2017 AICP.

Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?

Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Can you explain the problem a bit more?
Did it get fixed after restoring?

Phlogistol said:
Well, I just installed RR on my AUO mi4c, and it doesn't work. The touchscreen is broken and registers touches consistently but strangely. It even does it in recovery. I'm trying to restore my backup now.
EDIT: backup restored. Still don't know why the firmware didn't work
bankov, which flavor of mi4c do you have? Sharp or AUO?
Click to expand...
Click to collapse
Mine is AUO. My touchscreen was like yours but it was from AICP update.
Basicly im not 100% shure it is fixed but i remember it couldnt register touch on the left bezel if somhere else is toched on the screen. And now is fine.

For anyone applying this from now on, the process is not reversible, because of the way the driver checks if firmware can be updated, it only wants to do upgrades, not downgrades.
Also, for anyone having problems that go away after a clean flash, they are probably not because of my fix.
If they don't go away, there is probably an updated firmware version somewhere that fixes it. I'll extract them again from the newest Nougat version.

Cozzmy13 said:
Can you explain the problem a bit more?
Did it get fixed after restoring?
Click to expand...
Click to collapse
Sure, I was a bit pressed for time yesterday
The touchscreen was inconsistent, for lack of a better word. Touches on a specific point on the screen didn't register on that location, but on some other one. It wasn't random because I could reliably reproduce this. There were also some points on the screen I couldn't reach at all. The capacitive buttons also didn't work. I'd have taken logs, but I couldn't get into developer options
I don't know exactly how this works, but the touchscreen got reversed to its original state when I managed to restore a backup of my earlier TS CM13.1 system from TWRP (I restored all available partitions). It took a few tries because of the weirdness though When I say original state, I mean it still suffers from the multitouch bug, so nothing got fixed.
Hope this is useful, but I'm stumped. Could we have different digitizers?

Back on Stock Nougat and very happy

After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.

While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems

Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
None of STOCK ROM or OTA updates can be flashed/updated by TWRP, you need to be on stock recovery as well everything stock (unmodified system, boot and all).

I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.

Harshseth said:
While ota updates.......i brought to twrp only.... instead of installing latest security update.......... manually tried to install update...bt i can't..... gets an error... didn't u faced such problems
Click to expand...
Click to collapse
In order to use the OTA path you have to be on stock recovery, boot and kernel, not on TWRP. Otherwise you get the error that you experienced.

xAnkris said:
I faced this problem too, but I fixed mostly of the battery drain tweaking the kernel with the ElementalX app to ~0,80/h. I had to set the little cores working like big cores do, because all little cores and one big were in use always; and applied LightingBlade profile.
Click to expand...
Click to collapse
I went that path but it didn't seem to help much. Besides, I am happy with this stock setup. It is much better than when I was on Marshmallow stock and went over to custom ROMs. I can do anything I want to do and install any app I desire to use. Good performance, great battery life, and customizable as much as I want. No need to be on custom.

pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat

ADITYA_KUMAR said:
Are you able to root the stock nougat build npjs25 14-8.?
If yes how you rooted your phone. Plzz guide me. I also want to root my stock nougat
Click to expand...
Click to collapse
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.

pastorbob62 said:
Before you can root stock Nougat you must first unlock you bootloader, install TWRP then flash Elemental X kernel 1.04 from TWRP.
Click to expand...
Click to collapse
What is elemental x kernel. I have a unlocked bootloader.

ADITYA_KUMAR said:
What is elemental x kernel. I have a unlocked bootloader.
Click to expand...
Click to collapse
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.

pastorbob62 said:
Instead of asking questions that have been answered numerous times (ad nauseam) you should try reading through the forums. I realize you are a raw noob, but if you wanted to learn Calculus, would you ask a bunch of questions without doing any reading and studying? It's no different when you are modifying your smart phone.
Here is a link to a thread that will guide you to rooting stock Nougat. It works for all versions of stock Nougat.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
But don't do anything until you have read through the procedures and fully understand. Above all, make a backup of your system from TWRP before you do anything else.
Click to expand...
Click to collapse
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked

pastorbob62 said:
After several weeks of battling terrible battery drain, lag and sluggish performance I am back on Stock Nougat, build number NPJS25.93-14-8. With moderate use, my battery is now averaging less than 2% per hour ( < 1% while sleeping), where on the custom ROM of choice it was running over 5% per hour, even while sleeping. I tried every trick and tweak I could find and Better Battery Stats didn't show anything that could account for the high drain. I even tried a different ROM to no avail. So I threw in the towel, returned to stock, and did the latest OTA updates. I am now running rooted with ElementalX kernel 1.04 and I couldn't be more pleases with the overall performance and battery life.
I am sure it was something I missed but I got tired of spending hours trying to get back to the original performance and battery life the custom ROM had several weeks ago. Sometimes you just gotta do what you gotta do.
Click to expand...
Click to collapse
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.

siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root. Else, without the mentioned modifications, you'll trip the anti-rooting protection built into the stock kernel, and you'll have bootloops unless you reflash your stock ROM as you experienced.
Easiest way, as per the guide is to:
Flash/boot TWRP.
Backup.
Flash ElementalX or vegito (any custom kernel will do, as these kernels do not have the anti-rooting protection).
Reboot to test.
Boot back to TWRP
Flash SuperSU v2.79 or newer, or magisk 13 or newer
Reboot.
You should be rooted, on stock, and if you've flashed magisk, Safetynet should be working It's working well on NPJS25.93-14-8 and it's stable. Granted, a few apps now seem to detect root/magisk (and fail to download/update from the Play Store, with an error 0), but nothing that a sideload from a legitimate source wouldn't solve...

champsp said:
Very true.
Also try LightningBlade tunables(v 1.2.3 ; the newer version does not work that well for me..).
Stock rom provides the best balance between Performance and Battery life.
Click to expand...
Click to collapse
True that! :good:

siddhesh9146 said:
once I tried to root on stock nogut, so I installed TWRP and flashed SuperSu and my phone got bricked
Click to expand...
Click to collapse
If you had followed the link I supplied you would have had your answer as to why you had problems and also how to fix it.

echo92 said:
If you're rooting on stock Nougat, you must have a custom kernel flashed (or used the temporary dm-verity disabler on the stock kernel) before you root.
Click to expand...
Click to collapse
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.

moonlightdrive said:
Hi, sorry for ask, do you know where can i find the temporary dm-verity disabler?
I tried with a script named "no-verity-opt-encrypt-5.1" (this works for the G5 Plus 'Potter') but i haven't had any success. Even i unpacked the stock boot.img and i tried to manually patch it, but i failed here too.
Honestly i would like to test the stock kernel, because i never used it, i am always attached to flashing EX to get root access. Thank you in advance.
Click to expand...
Click to collapse
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...

echo92 said:
I don't know if this will still work on later builds than the November/December 2016 builds, but here's the kernel with dm-verity disabled: https://forum.xda-developers.com/mo...t-how-to-root-n-firmware-npj25-93-11-t3532556 Seems to cause bootloops though on the later builds however
Strictly speaking, I misspoke - it's not really a dm-verity disabler, more a stock kernel with dm-verity disabled. I think EX kernel is still the more stable and more reliable option. It would be nice to be able to root the stock kernel though...
Click to expand...
Click to collapse
Oh, i see, thanks for your response. I'll look into it to see how he did to by-pass the dm verity, and try to modify the last boot.img that we have.

I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
You may wish to back up your data with TWRP or ensure you have your photos and videos somewhere safe prior to flashing this.
Reboot to TWRP and backup your device.
Flash the above script.zip in TWRP and wait for it to complete. (it should be fixing the permissions in /data/media)
Reboot and you should be able to download/update apps again from Google Play afterwards. You may have to uninstall the app and re-install the app if it keeps failing.
I've got this working on a XT1642 running June 2017 stock ROM, rooted with magisk 13.3 and apps including Snapchat and Google Chrome update without issue now.

echo92 said:
I mentioned earlier in this thread about getting Error 0 whilst updating apps in Google Play. As it turns out, thanks to this tip here https://forum.xda-developers.com/showpost.php?p=73552496&postcount=57 it appears to be an error with permissions on the /data/media partition.
I managed to fix it with osm0sis' script:
Download from here https://forum.xda-developers.com/showthread.php?t=2239421 the sdcard Fix Permissions script http://forum.xda-developers.com/attachment.php?attachmentid=3761904&d=1464187934
Click to expand...
Click to collapse
Useful info, this happened to me a couple of days ago. I thought it was something related to the integrated Chrome WebView in conflict with the system WebView, because it only happened when i tried to update Chrome, or any of his variants (dev, beta, canary, etc). Thanks.