• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[EOL][KERNEL] [G93xx][2019-05-25] WirusMOD [Nethunter for Oreo]

Search This thread

Svirusx

Senior Member
Jun 6, 2015
286
218
@Svirusx It may be to early to ask this, but do you have any plans to port either this or just bethunter to stock pie? https://www.google.com/amp/s/forum....t/blackdiamondfesmooth-fastv1-0-t3915483/amp/
For now i focus on tests LineageOS 16.0 Nethunter kernel. Maybe later i try port Nethunter to stock pie but first i must test Stock Pie ROM and see how stable it is and how much memory is used in boot partition for kernel. Stocks use much more capacity of boot partition ;/.
 
  • Like
Reactions: Jack_Rickwood

Jack_Rickwood

Member
Jul 7, 2018
39
4
@Svirusx Ok, thanks a lot. I dont know wether this matters, but when i run 'iw list' it doesnt show monitor mode, does that mean i will not be able to use it? Also 'iwconfig' shows my only network adapter as wlan0.
 

_Danil_

Member
May 15, 2015
43
10
Where are the kernel or system logs saved? I want to try understand why the phone is rebooting. Does anyone else have this problem? The phone at random time reboots.
I don’t want to switch to lineageos. And I hope that the distinguished @Svirusx will find time to update the kernel ;)
 

Svirusx

Senior Member
Jun 6, 2015
286
218
Where are the kernel or system logs saved? I want to try understand why the phone is rebooting. Does anyone else have this problem? The phone at random time reboots.
I don’t want to switch to lineageos. And I hope that the distinguished @Svirusx will find time to update the kernel ;)

Look at dmesg or logcat commands
If you got crash you can too look at /proc/last_kmsg here is saved dmesg before kernel panic
 
  • Like
Reactions: _Danil_

_Danil_

Member
May 15, 2015
43
10
That's what I got after the next reboot.
Perhaps the problem is in the governor. I dont know. Now i try change Governor from Interactive to OnDemand
Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x7f(7)
MON[0] = (7)[0x2e, 0x48]
MON[1] = (0)[0x2f, 0x30]
MON[2] = (1)[0x31, 0x48]
MON[3] = (2)[0x36, 0xaa]
MON[4] = (3)[0x41, 0x58]
MON[5] = (4)[0xff, 0x04]
MON[6] = (5)[0x1b, 0x62]
MON[7] = (6)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0xcf1f7ae9 0x268bc4a4 0xcd14aaa7
CP Mailbox Debug
0x10540180 : 0x1486bc45 0x5501785f
0x10540184 : 0xc5533066 0x249bda00
0x10540188 : 0x6de76f00 0x5988ef78
0x1054018C : 0xf82bd18e 0xc5d9a7ca
0x10540190 : 0x489bc4b4 0x74fc6973
0x105C0038 : 0x 82960b2 0x1f0131e2
CP BL flow
0x10920014 : 0xe351a010 0xf3c44699
0x10800028 : 0xd37a9c2e 0x402eef7e
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0xbaba - Kernel PANIC
а'>r
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Power/Emergency Reset: 0x3ab8ec80
Core1: Power/Emergency Reset: 0x72/PANIC
Core2: Power/Emergency Reset: 0x70d68308
Core3: Power/Emergency Reset: 0x0/PANIC
Core4: Power/Emergency Reset: 0xe3c4b940
Core5: Power/Emergency Reset: 0x7f/PANIC
Core6: Power/Emergency Reset: 0xe3c4b950/PANIC

Core7: Power/Emergency Reset: 0x7f
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 00 00 IM:0d 11 8b CDET:2d 0c CTRL:40 3b 00 b2 HVCT:00 00 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x00

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 sec_tima_l[email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=700ec7ba10b7cb2985230ca6181dd15b connie=SM-G930F_OPEN_EUR_051196c879a6d87df7648cebccaeacc1 fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,

I attached the full log to the post.
 

Attachments

  • last_kmsg.zip
    174.5 KB · Views: 12
Last edited:
  • Like
Reactions: Svirusx

Svirusx

Senior Member
Jun 6, 2015
286
218
That's what I got after the next reboot.
Perhaps the problem is in the governor. I dont know. Now i try change Governor from Interactive to OnDemand

I attached the full log to the post.

That could be problem but Interactive is default Governor. I think i must disable some nethunter drivers and enable they 1 by 1 to find which driver make this problem. Only testing it take a lot of time because of wait for reboot.

Do you use Stock ROM?
 

_Danil_

Member
May 15, 2015
43
10
I think the problem is not with Governor. I changed through MTweaks with the change at startup. The phone still reboots.
And restarts are not always accompanied by a kernel panic.
There are such types:
reboot reason: 0xfafa - Safe Kernel PANIC
reboot reason: 0x0 - Power/Emergency Reset
reboot reason: 0xbaba - Kernel PANIC
Logs I hid.
Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x51(2)
MON[0] = (2)[0x2e, 0x48]
MON[1] = (3)[0x2f, 0x30]
MON[2] = (4)[0x31, 0x48]
MON[3] = (5)[0x36, 0xaa]
MON[4] = (6)[0x41, 0x58]
MON[5] = (7)[0xff, 0x04]
MON[6] = (0)[0x1b, 0x62]
MON[7] = (1)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0x 6 0x 6 0x 6
CP Mailbox Debug
0x10540180 : 0x1486bc47 0x7401785f
0x10540184 : 0x444b30e6 0x249ada40
0x10540188 : 0xede76d00 0x5988ef78
0x1054018C : 0xf83bd18e 0xcff8a7ea
0x10540190 : 0x589bc434 0x5efc7971
0x105C0038 : 0x382960b2 0x ea131e2
CP BL flow
0x10920014 : 0xf371e010 0xf3cc4699
0x10800028 : 0xd372942a 0x403eee5e
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0xbaba - Kernel PANIC
Fatal exception in interrupt
PC is at timerqueue_add+0x60/0xc0
LR is at enqueue_hrtimer+0xb4/0xf8
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Alive/PANIC
Core1: Alive/PANIC
Core2: Alive/PANIC

Core3: Dead
Core4: Alive
Core5: Alive/PANIC
Core6: Alive
Core7: Alive/PANIC
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 43 05 IM:0d 11 8b CDET:2d 0c CTRL:3f 3b 00 b2 HVCT:00 03 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x3f

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 [email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=762871741431394ee3a58f770aa76982 connie=SM-G930F_OPEN_EUR_48fea6b19bb2196a57958406f3fc2d86 fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,


Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x4f(1)
MON[0] = (1)[0x2e, 0x48]
MON[1] = (2)[0x2f, 0x30]
MON[2] = (3)[0x31, 0x48]
MON[3] = (4)[0x36, 0xaa]
MON[4] = (5)[0x41, 0x58]
MON[5] = (6)[0xff, 0x04]
MON[6] = (7)[0x1b, 0x62]
MON[7] = (0)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0x 6 0x 6 0x 6
CP Mailbox Debug
0x10540180 : 0x9486b445 0x7501585f
0x10540184 : 0x555b30e6 0x249ada01
0x10540188 : 0x6de76d40 0x5988ef78
0x1054018C : 0xf82bd1ce 0xccd9a7ea
0x10540190 : 0x58dbc434 0xd6ec6971
0x105C0038 : 0x582860b2 0x1f8131e3
CP BL flow
0x10920014 : 0xf25be010 0xf3e54699
0x10800028 : 0xd36a902f 0x402cee7f
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0xdfc5e630 - Power/Emergency Reset
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Power/Emergency Reset: 0x134d80
Core1: Power/Emergency Reset: 0xffffffc0
Core2: Power/Emergency Reset: 0x600003c5
Core3: Power/Emergency Reset: 0x0
Core4: Power/Emergency Reset: 0x30
Core5: Power/Emergency Reset: 0x0
Core6: Power/Emergency Reset: 0xc0ac0a98
Core7: Power/Emergency Reset: 0x71
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 00 00 IM:0d 11 8b CDET:2d 0c CTRL:40 3b 00 b2 HVCT:00 00 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x00

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 [email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=a492abac94dbc5b469e1b69e1b6a1938 connie=SM-G930F_OPEN_EUR_976a8e830e82356101dc38dffae754ee fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,




Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x40(0)
MON[0] = (0)[0x2e, 0x48]
MON[1] = (1)[0x2f, 0x30]
MON[2] = (2)[0x31, 0x48]
MON[3] = (3)[0x36, 0xaa]
MON[4] = (4)[0x41, 0x58]
MON[5] = (5)[0xff, 0x04]
MON[6] = (6)[0x1b, 0x62]
MON[7] = (7)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0x 6 0x 6 0x 6
CP Mailbox Debug
0x10540180 : 0x9486b445 0x7501585f
0x10540184 : 0x555b30e6 0x249ada01
0x10540188 : 0x6de76d40 0x5988ef78
0x1054018C : 0xf82bd1ce 0xccd9a7ea
0x10540190 : 0x58dbc434 0xd6ec6971
0x105C0038 : 0x582860b2 0x1f8131e3
CP BL flow
0x10920014 : 0xf25be010 0xf3e54699
0x10800028 : 0xd36a902f 0x402cee7f
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0xfafa - Safe Kernel PANIC
safe panic handler at cpu 0
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Power/Emergency Reset: 0x0
Core1: Power/Emergency Reset: 0x0
Core2: Power/Emergency Reset: 0x0
Core3: Power/Emergency Reset: 0x0
Core4: Power/Emergency Reset: 0x0
Core5: Power/Emergency Reset: 0x0
Core6: Power/Emergency Reset: 0x0
Core7: Power/Emergency Reset: 0x0
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 00 00 IM:0d 11 8b CDET:2d 0c CTRL:40 3b 00 b2 HVCT:00 00 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x00

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 [email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=8f5f0c598bd07cac5c832e34cedb9ba3 connie=SM-G930F_OPEN_EUR_f5fa4c42f455214ca9ab9de8619482a5 fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,



Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x58(3)
MON[0] = (3)[0x2e, 0x48]
MON[1] = (4)[0x2f, 0x30]
MON[2] = (5)[0x31, 0x48]
MON[3] = (6)[0x36, 0xaa]
MON[4] = (7)[0x41, 0x58]
MON[5] = (0)[0xff, 0x04]
MON[6] = (1)[0x1b, 0x62]
MON[7] = (2)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0x 6 0x 6 0x 6
CP Mailbox Debug
0x10540180 : 0x9486b445 0x7501585f
0x10540184 : 0x555b30e6 0x249ada01
0x10540188 : 0x6de76d40 0x5988ef78
0x1054018C : 0xf82bd1ce 0xccd9a7ea
0x10540190 : 0x58dbc434 0xd6ec6971
0x105C0038 : 0x582860b2 0x1f8131e3
CP BL flow
0x10920014 : 0xf25be010 0xf3e54699
0x10800028 : 0xd36a902f 0x402cee7f
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0x0 - Power/Emergency Reset
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Power/Emergency Reset: 0x0
Core1: Power/Emergency Reset: 0x0
Core2: Power/Emergency Reset: 0x0
Core3: Power/Emergency Reset: 0x0
Core4: Power/Emergency Reset: 0x0
Core5: Power/Emergency Reset: 0x0
Core6: Power/Emergency Reset: 0x0
Core7: Power/Emergency Reset: 0x0
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 00 00 IM:0d 11 8b CDET:2d 0c CTRL:40 3b 00 b2 HVCT:00 00 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x00

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 [email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=9d069ced077bf0e1c72b64ca6448abd6 connie=SM-G930F_OPEN_EUR_11167fc9ecd84ce1baa8772f5e5e5f3c fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,


Samsung S-Boot 4.0 for SM-G930F (Mar 7 2019 - 21:43:29 22457191)
EXYNOS8890 EVT 2.0 (Base on ARM CortexA53)
4068MB / 0MB / Rev 9 / G930FXXS4ESC3 / (PKG_ID 0x40000000) / LOT_ID N62C7 / SHIP /WDT_RST (0x1000000)
MON: 0x41(0)
MON[0] = (0)[0x2e, 0x48]
MON[1] = (1)[0x2f, 0x30]
MON[2] = (2)[0x31, 0x48]
MON[3] = (3)[0x36, 0xaa]
MON[4] = (4)[0x41, 0x58]
MON[5] = (5)[0xff, 0x04]
MON[6] = (6)[0x1b, 0x62]
MON[7] = (7)[0x0c, 0x00]
nAsv_BIG:5 ,nAsv_LITT:7 ,nAsv_G3D:9 ,nAsv_MIF:7 ,nAsv_INT:7 ,nAsv_CP:9 ,nAsv_CAM_DISP:a
nIds_BIG:0 ,nIds_LITT:0 ,nIds_INT:0 ,nIds_MIF:0 ,nIds_G3D:0 ,nIds_DISP:0 ,nIds_CP:0 ,
Resume bl2 flow
BL2_VAL : 0x 1f 0x 1f 0x 1f
clk_init bl2 flow
BL2_CLK_VAL : 0x 1c 0x 1c 0x 1c
dmc_init bl2 flow
BL2_LPDDR4_VAL : 0x 6 0x 6 0x 6
CP Mailbox Debug
0x10540180 : 0x9486b445 0x7501585f
0x10540184 : 0x555b30e6 0x249ada01
0x10540188 : 0x6de76d40 0x5988ef78
0x1054018C : 0xf82bd1ce 0xccd9a7ea
0x10540190 : 0x58dbc434 0xd6ec6971
0x105C0038 : 0x582860b2 0x1f8131e3
CP BL flow
0x10920014 : 0xf25be010 0xf3e54699
0x10800028 : 0xd36a902f 0x402cee7f
Resume el3 flow
EL3_VAL : 0x 8a0 0x 8a0 0x 8a0
s5p_check_dump_gpr: RST_STAT(0x1000000)
reboot reason: 0xfafa - Safe Kernel PANIC
safe panic handler at cpu 0
Core stat at previous(IRAM)
Core4: Hotplug
Core5: Hotplug
Core6: Hotplug
Core7: Hotplug
Core0: Reset
Core1: Hotplug
Core2: Hotplug
Core3: Hotplug
Core stat at previous(KERNEL)
Core0: Power/Emergency Reset: 0x0
Core1: Power/Emergency Reset: 0x0
Core2: Power/Emergency Reset: 0x0
Core3: Power/Emergency Reset: 0x0
Core4: Power/Emergency Reset: 0x0
Core5: Power/Emergency Reset: 0x0
Core6: Power/Emergency Reset: 0x0
Core7: Power/Emergency Reset: 0x0
SICD state at previous(IRAM)
Power mode: No power mode
muic_register_max77854_apis
muic_is_max77854 chip_id:0x54 muic_id:0xb5 -> matched.
[MUIC] print_init_regs
INT:00 00 00 ST:1f 00 00 IM:0d 11 8b CDET:2d 0c CTRL:40 3b 00 b2 HVCT:00 00 LDO0:47

MUIC rev = MAX77854(181)
init_multi_microusb_ic Active MUIC 0xb5
ifconn_init: MUIC Mode
[MUIC] print_init_regs
load Secure Payload done.

Chip ID : 05774c5d5144 / 0x00000000
EL3 Monitor information:
Onyx-OPR6-8511R1-1-g186f7 186f7bf d0d3607 8508926 6fa036e 5629f57 sw0323.kang aarch64-linux-gnu-gcc (crosstool-NG linaro-1.13.1-4.8-2013.09 - Linaro GCC 201

UFS link established
UFS device initialized
bConfigDescrLock: 1
sw_unlock success
sw_unlock success
sw_unlock success
ifconn_com_to_open:
[MUIC] CONTROL1: 0x00

[Debug Info.]
S-BOOT : VERSION_-+H0
SecureOS : 20 (MB)
- read_bl1
blk_bread_bootsector: LUN 1, from 0x0, size 0x10, buffer 0x90c08000
Verify_Binary_Signature 0x90c20120 [email protected], [email protected]
pit_check_signature (PIT) valid.
PARAM ENV VERSION: v1.0..
ATAG_CMDLINE: 131 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c androidboot.dram_rev=00000000 androidboot.dram_info=FF,02,00,4G androidboot.ap_serial=0x05774C5D5144 sec_debug.sjl=1 ess_setup=0x91200000 [email protected] [email protected] [email protected] charging_mode=0x30 s3cfb.bootloaderfb=0xe2a00000 lcdtype=16452 lcdres_offset=7340604,0 consoleblank=0 vmalloc=384m sec_debug.reset_reason=3 sec_reset.reset_reason=3 ehci_hcd.park=3 oops=panic pmic_info=35 cordon=0f50057c729238e236aea418e075037b connie=SM-G930F_OPEN_EUR_ac38cc2e4bf884ba04eb6defdbdff3de fg_reset=0 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=G930FXXS4ESC3 androidboot.selinux=enforcing androidboot.security_mode=1526595585 androidboot.ucs_mode=0 [email protected] androidboot.hw_rev=9 androidboot.hardware=samsungexynos8890 androidboot.warranty_bit=1 androidboot.wb.hs=030c sec_debug.bin=A androidboot.hmac_mismatch=0 androidboot.sec_atd.tty=/dev/ttySAC4 androidboot.serialno=ad07170205a60b7a2b snd_soc_core.pmdown_time=1000 androidboot.fmp_config=0 firmware_class.path=/vendor/firmware region1=EUR region2=OPEN'
param logs: R,N,N,R,N,R,R,N,R,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,R,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,



What about the voltage? Is it changed in the kernel? It are different from stock, do not know?
 
Last edited:

Svirusx

Senior Member
Jun 6, 2015
286
218
I think the problem is not with Governor. I changed through MTweaks with the change at startup. The phone still reboots.
And restarts are not always accompanied by a kernel panic.

What about the voltage? Is it changed in the kernel? It are different from stock, do not know
I'm testing now new kernel with only drivers needed to work all things from features. I think today i add some drivers and test further. One day without reboot.

I stay now on Stock ROM + Magisk, busybox, MicroG.
 
  • Like
Reactions: _Danil_

_Danil_

Member
May 15, 2015
43
10
I'm testing now new kernel with only drivers needed to work all things from features. I think today i add some drivers and test further. One day without reboot.

I stay now on Stock ROM + Magisk, busybox, MicroG.

As I understand it, no need to extract all Binaries from Nethunter_Binaries.7z
Only necessary.
For Atheros AR9271, as I understand it htc_9271.
Maybe the problem is that I threw everything? In the extreme case, the problem is in the ROM itself, but the clean TGP works fine.
I'm going to change the ROM this weekend, I'll try on it.
 
Last edited:

Svirusx

Senior Member
Jun 6, 2015
286
218
As I understand it, no need to extract all Binaries from Nethunter_Binaries.7z
Only necessary.
For Atheros AR9271, as I understand it htc_9271.
Maybe the problem is that I threw everything? In the extreme case, the problem is in the ROM itself, but the clean TGP works fine.
I'm going to change the RON this weekend, I'll try on it.

Reboot problem is in kernel. I must find which driver do that and exclude it in next release ;]
I too copy all binaries they aren't soo heavy.
 
  • Like
Reactions: k4mu5 and _Danil_

k4mu5

Member
Nov 29, 2017
16
3
Reboot problem is in kernel. I must find which driver do that and exclude it in next release ;]
I too copy all binaries they aren't soo heavy.

What should be the problem in terms of copying the nethunter binaries files to the path system / etc / firmware and system / xbin, the rom is read-only, the reset deletes them, some parameter to change? Thank you and the contribution of the kernel is appreciated..:good:
 

Svirusx

Senior Member
Jun 6, 2015
286
218
What should be the problem in terms of copying the nethunter binaries files to the path system / etc / firmware and system / xbin, the rom is read-only, the reset deletes them, some parameter to change? Thank you and the contribution of the kernel is appreciated..:good:
Copy binaries to system/bin instead of xbin.
In system/etc/firmware files aren't removed after reboot. You need to use file explorer like root explorer which can remount system partition as r/w.
 

greymood

Member
Apr 22, 2019
6
1
Installing complications.

SM-G930F

In the installation, after flashing Nethunter.WirusMOD.____.zip I get the normal Aroma installation.
I select to install Busybox and etc but after I've installed everything I get uevent error. (which I ignored)
So, I clear cache and reboot to System and install NetHunter apk. In there I get error that BusyBox hasn't been installed nor any root is available.
Step 6 requires me to install Magisk NetHunter module, could you specify what repository do I get it from?
 

Svirusx

Senior Member
Jun 6, 2015
286
218
There is a picture of Kali Nethunter Logo which covers the midle screen. How can I fix it.
What do you mean, in TWRP -> aroma?

SM-G930F

In the installation, after flashing Nethunter.WirusMOD.____.zip I get the normal Aroma installation.
I select to install Busybox and etc but after I've installed everything I get uevent error. (which I ignored)
So, I clear cache and reboot to System and install NetHunter apk. In there I get error that BusyBox hasn't been installed nor any root is available.
Step 6 requires me to install Magisk NetHunter module, could you specify what repository do I get it from?

Before start download magisk 19.0.zip from official thread and Busybox_for_android_NDK-1.30.1.zip(In magisk manager you have option download only)
Try install:
1. Nethunter.WirusMOD.XXX.zip without root and busybox.
2. Install remove encryption.zip
3. reboot to system (if data is formated than end first configuration)
4. reboot to TWRP install busybox and magisk.
5. Install Nethunter magisk module from magisk manager
I use my kernel with those steps.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9

    End of Life WirusMOD Nethunter Kernel for Oreo ROMs
    Samsung Galaxy S7 / Edge
    Code:
    I am not responsible for bricked devices.
    If you going to flash it, you accepted it.
    Of course your warranty is void.

    This thread is for herolte. If you have S7 Edge go here

    FEATURES:

    • BadUSB
    • HID gadget keyboard/mouse (with possibility to temporarily disable)
    • DriveDroid
    • USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
    • Ethernet
    • F2FS
    • Bluetooth HCI USB support
    • RTL-SDR DVB support
    • Most features of TGPKernel

    Supported ROMs:
    • S7 Stock O ROMs - G930F / G930FD / G930W8 / G935F / G935FD / G935W8
    • S7 Hybrid O ROMs (G930F/G935F) - The Galaxy Project (TGP), Ambasadii S7, SilverRom, etc
    • S9 Port ROMs
    • N8 Oreo Port ROMs

    Download:
    Latest version Herolte here.

    Installation:
    1. Flash latest TWRP twrp-3.3.0-1+ ( to see data partition with enabled disk quota)
    1. TWRP Backup your ROM
    3. Flash Nethunter WirusMOD
    4. Magisk and busybox is needed you can choose in aroma or install it later.
    5. Install Magisk Nethunter module from Magisk Manager -> Downloads (Or another version of Nethunter)
    If you get crashes in Magisk Nethunter app than install from here.
    6. Install kalifs-armhf-*.tar.xz by Nethunter manager
    7. Extract Nethunter_Binaries.7z and binaries to folders:
    Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
    hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
    Now you have Nethunter on your herolte/hero2lte.


    EXTRA:
    1.In Utilities.7z are wifi testing tools binaries like aircrack-ng compiled from source of nexmon (Not needed for Nethunter only for test tools direct from android without Nethunter)
    If you want use binaries you need to copy it to /system/bin or /system/xbin and give permissions to it rwxr-xr-x

    2. DriveDroid without bugs made by disabling HID Patch:
    • To disable HID Patch: use this command in terminal: "echo Y > /sys/module/g_android/parameters/hid_disable"
      Changing mode isn't instant after changing module status. Use DriveDroid (mount iso -> dismount) to active hid_disable.
    • To enable HID Patch: "echo N > /sys/module/g_android/parameters/hid_disable" and use DriveDroid like with disabling HID Patch.
      HIDPatchSwitch this is simple script which can switch between HID enabled and disabled and show changed status.


    Old Installation steps:

    1. TWRP Backup your ROM
    2. Flash Nethunter.WirusMOD.G93xx.vx.x.XXXXXXXX.zip
    2.1.Look at EXTRA.
    3. Busybox is needed you can choose in aroma or install another version.
    6. Install Magisk Nethunter module from Magisk Manager -> Downloads (Or another version of Nethunter)
    If you get crashes in Magisk Nethunter app than install this version.
    7. Install kalifs-armhf-*.tar.xz by Nethunter manager
    8. Extract Nethunter_Binaries.7z and binaries to folders:
    Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
    hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
    9. Download Modules for your version of smartphone and copy it anywhere in your phone.
    By using modules you can add features to kernel for which i hadn't memory in kernel and aren't most important like rarely used wifi card modules or file systems modules. Load only those which you need.
    You can use modules by those commands insmod, rmmod, lsmod or use Module Loader this app is outdated but works fine.
    Now you have Nethunter on your herolte/hero2lte.

    EXTRA:
    If you want to have unencrypted data partition:
    1. Format data partition(you lose your data).
    2 Flash Kernel with option NO ROOT
    2. After flashing kernel flash "remove encryption.zip".
    3. Reboot to system (First start configuration wizard).
    4. Reboot to twrp and flash Magisk.


    Screens:

    52511993-f2687700-2c02-11e9-9f61-de3eb8d965cc.jpg
    52511994-f399a400-2c02-11e9-9665-2476cba4b9cc.jpg
    52511078-ccd96e80-2bfe-11e9-9f1d-5027d932c784.jpg



    Credits:
    djb77 for his TGPkernel source
    Nethunter creators for the best portable penetration testing tool.





    XDA:DevDB Information
    [KERNEL][G93xx][2019-05-25] WirusMOD [Nethunter for Oreo], Kernel for the Samsung Galaxy S7

    Contributors
    Svirusx
    Source Code: https://github.com/Svirusx/Nethunter-s7-kernel-WirusMOD-Oreo

    Kernel Special Features: Powered by TGPKernel

    Version Information
    Status:
    Testing

    Created 2019-02-09
    Last Updated 2019-06-22
    2
    CHANGELOG

    2019.09.27- v1.4
    Upstream to tgpkernel source Version 6.15.2[EOL]

    2019.06.22- v1.3
    Update source to TGPKernel Version 6.15.0

    2019.05.25 - v1.2
    Updated TGPkernel source to v6.14.0 (release from 2019-05-23)
    Rebased source, removed loadable modules
    Ramdisk compressed with xz to get more free space for drivers.
    Little fixes in defconfig

    2019-04-20 - v1.1
    Added monitor mode patches to some wifi usb drivers.
    Added possibility to disable HIDPatch (this fixes DriveDroid)
    Added HIDPatchSwitch: Simple sh script to switch status of HIDPatch (Info in comments in script)
    Updated TGP source to Version 6.12.8

    2019-02-09 - v1.0
    Initial release.
    2
    What's different between 2 of your kali net hunter or wiresmod nethunter

    This WirusMOD Nethunter is based on TGPKernel so it have features of TGPKernel too. Normal Nethunter is based on Stock Kernel.

    I'm not sure if this is related but could this help me with the 5 GHz Wi-Fi disconnects on my phone every 10 minutes from the AP?
    No other device has this issue for me, only this phone and I tried changing channels already, they all drop exactly at 10 minutes and I've given the phone permanent local IP, no lease time.
    On the other hand 2.4 GHz is rock solid.

    No, this kernel can't help you for disconnects.
    2
    Can you update kernel to the latest version of tgpkernel 6.15.2? The current version of WirusMOD is compiled based 6.15.0
    https://github.com/TheGalaxyProject/tgpkernel-s7-o

    I switched to MoRoKernel when i saw TGPKernel is EOL, but i see that after EOL it is still getting some updates weird...
    You can find Nethunter MoRoKernel based here.
    2
    As I understand it, no need to extract all Binaries from Nethunter_Binaries.7z
    Only necessary.
    For Atheros AR9271, as I understand it htc_9271.
    Maybe the problem is that I threw everything? In the extreme case, the problem is in the ROM itself, but the clean TGP works fine.
    I'm going to change the RON this weekend, I'll try on it.

    Reboot problem is in kernel. I must find which driver do that and exclude it in next release ;]
    I too copy all binaries they aren't soo heavy.