[ROOT] [Extreme Syndicate] [Snapdragon][N950U/U1][V8 Bootloaders]

Dec 12, 2016
6
0
1
[ROOT] [Extreme Syndicate] [Snapdragon][N950U/U1][V7 Bootloaders]


Rooted Nougat Rom

This is last nougat rom made for note 8 it is prerooted with flashfire and safestrap preinstalled. It has CSC stuff for all carriers added. Its debloated slightly with knox removed. Some stuff may not work but im not sure as I cannot test but this stuff may include fingerprint and or face recognition. If stuff doesnt work it probably related to using pie modems and non-hlos on a nougat rom which you have no choice.


Downloads
system_n8_brb4.7z
BL_N950U_NOUGAT_V8.tar.7z
Includes Fingerprint and Face Unlock fix for above nougat rom. Just flash in BL slot in odin after everything else
Magisk_System-v21_2.zip This is system magisk not the normal systemless magisk so magisk hide and modules will not work!
SuperSU_System.zip
Safestrap-4.10-B03-GREATQLTE-PIE.zip Will boot straight to safestrap only for pie roms
Safestrap-4.10-B03-GREATQLTE-NOUGAT.zip Will Give you the safestrap splash screen on boot
SM_955_Mods_Safestrap_NOUGAT.zip Will fix volte icon

Directions
If you didnt upgrade to V8 bootloaders using odin. I recommend flashing full stock firmware with V8 bootloaders even if you are already on V8 bootloader via OTA update. I feel that maybe something in the OTA from V7 bootloaders to V8 may have corrupted a bootloader file and some people have experienced bricks with trying to update to V8 bootloaders from V7 using the below method so I recommend flashing full stock V8 firmware in Odin before trying this method and just understand there has been a risk of bricking device. Full stock can be found on Sammobile or updato or any other service you can find it. You will have to reroot of course. If you Updated to V8 bootloaders using odin method already then no need to do so again

Safestrap Method
1. Extract system.img from the system_n8_brb4.7z and copy to phone also copy either SuperSu_System.zip or Magisk_System-v20.4.zip reboot to safestarp and flash system image
2. Flash either SuperSu_System.zip or Magisk_System-v20.4.zip
3. Reboot to download and flash BL_N950_NOUGAT_V8.tar.md5 in odin
4. If you get constant rebooting to safestrap flash Nougat safestrap zip while in safestrap



New V8 Pie Rom With Safestrap For The N8 SM-N950U/U1 Can Be Found In The New Threads Below

DTI1 Pie Rom With Safestrap
i think edl method is easiest way for me i had rooted N950U bootloader 5 with android nougat
 

GanDopEST

Member
Jul 3, 2018
8
1
13
Can you share the process you did or the link to flash Wanam Xposed?
the xposed i meant to ask was Rovo 's xposed for 7.1.1 not wanams lollipop. I apologize for misleading anyone . https://dl-xda.xposed.info/framework/sdk25/arm64/
the process I used was op's COMBINATION_FA70_N950USQU8ATF1.tar.md5 via custom odin. N950us atm was v8 w/o using odin. upgraded to v8 from OTA. so I chose to adhere to jk's red lettered warning and flashed a stock v8 from Sammy. the only issue i had was audiocoredebug didn't have "test helper" I don't recall which menu I found it in but overall process is for above novice cord-cutters. since Dec 11 I've been "SuperSu" 》 enjoying "payload" not to the fullest due to my hard to break habits. I heart xposed and chelpus whenever SuperSu + busybox is properly installed. does anyone know if xposed is compatible with combo firmware?
 

zfk110

Senior Member
Jan 11, 2014
943
194
73
Atlanta
Samsung good lock gives you status bar modification and I think will let you disable it


Sent from my iPhone using Tapatalk
Only problem I got with the Nugget custom ROM after applying a theme from the Samsung themes store it does apply but when I restart the theme will go away then I have to go in and reapply the same theme, and then it will stay in as soon as I restart it will go away I don't know if someone else has that kind of bug, issue and I don't know if there's any fix for it thank you
 

GanDopEST

Member
Jul 3, 2018
8
1
13
SuperSu app won't open and I'll have to force stop the app. its happening more frequently. I assume it's the kernel manager set to low on the "low memory killer." just a guess