{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Call for all kernel devs with a Sony Z5 Compact who would like to help out building an official NetHunter kernel for that device.
I've started on a NetHunter kernel with support for HID keyboard and mouse, injection, nexmon, & rtl8812au but the HID patch seems to cause a bootloop (might be something else though). I don't have that device and the person requesting it doesn't have a computer.
I've used the NetHunter kernel-builder:
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
with this local.config:
https://gitlab.com/kalilinux/nethun....config.examples/local.config.example.suzuran
and with these kernel sources:
https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1
following this guide:
https://www.kali.org/docs/nethunter/nethunter-kernel-1-patching/
We need someone that can rollback our commits and find the one that caused the bootloop (maybe the switch from perf to interactive?) and help fixing the offending commit.
Any help will be greatly appreciated.
Thanks heaps,
Re4son
Just received feedback from the person claiming that it was the HID patch which caused the bootloop; he didn't actually test it and just assumed that the issues were caused by that patch.
I'm pretty sure that it wasn't that patch. This bit of info might open the door to kernel hackers that don't want to play with USB drivers
Great project for Sony
Welcome all kernel hackers.. Its free guys, try please..
upp guys..
and 1 upp...
not so hardd..
@yesimxev
@kimocoder
helpppp
If I remember correctly I applied the nexmon patch with nethunter and that's when I experienced problems; more likely that, if the problem isn't fixed yet. BTW, is this Nethunter running a 4.14 kernel in a chroot shell or is this an actual patch to the existing boot.img for 14.1? I can modify the commit, but am unsure how to build an install.(Android SDK)?
&(*) said:
If I remember correctly I applied the nexmon patch with nethunter and that's when I experienced problems; more likely that, if the problem isn't fixed yet. BTW, is this Nethunter running a 4.14 kernel in a chroot shell or is this an actual patch to the existing boot.img for 14.1? I can modify the commit, but am unsure how to build an install.(Android SDK)?
Click to expand...
Click to collapse
kernel version generally doesnt matter. you need to git clone your kernel source and patch then recompile, and you will get Image.gz-dtb or zImage .
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
Re4son,
Looking at the kernel builder source ( https://github.com/Re4son/android_kernel_sony_msm8994 ) indicates this is dedicated to certain build versions, am I mistaken ? I tried installing this through the .zip installer for 7.1.2 and notice in prompt that patching the boot fails, but the rest installs. I managed to patch the boot image (https://gitlab.com/kalilinux/nethun...ethunter-devices/-/tree/master/nougat/suzuran) , but am unsure if ramdisk needs other libraries as well or if the kernel does (nexmon-fw & system)? Mainly trying to accomplish manually patching of the kernel and installing the rest with the installer if possible. Please advise as to the proper method to get everything in it's right path for Nethunter to be running correctly.
Re4son said:
Call for all kernel devs with a Sony Z5 Compact who would like to help out building an official NetHunter kernel for that device.
I've started on a NetHunter kernel with support for HID keyboard and mouse, injection, nexmon, & rtl8812au but the HID patch seems to cause a bootloop (might be something else though). I don't have that device and the person requesting it doesn't have a computer.
I've used the NetHunter kernel-builder:
https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
with this local.config:
https://gitlab.com/kalilinux/nethun....config.examples/local.config.example.suzuran
and with these kernel sources:
https://github.com/Re4son/android_kernel_sony_msm8994/tree/nethunter-14.1
following this guide:
https://www.kali.org/docs/nethunter/nethunter-kernel-1-patching/
We need someone that can rollback our commits and find the one that caused the bootloop (maybe the switch from perf to interactive?) and help fixing the offending commit.
Any help will be greatly appreciated.
Thanks heaps,
Re4son
Click to expand...
Click to collapse
is this type support nethunter ? i see in wikipedia, suzuran is 3 type = E5803, E5823, SO-02H.
i see in the market, sony xpesia z5 compact is many type like this picture :
Related
KDE Plasma Active two is a beautiful display manager for embedded devices. Its currently based on MeeGo. Porting is a very difficult task. I would therefore like to be contacted by aspiring developers who would like to help me in this project.
For those of you who don't know what Plasma Active is. It is the Mobile/Tablet version of the popular Desktop Environment/Display Manager KDE. Screenshots below.
Pull Down App Menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Time And Date Settings
Activity Screen (activity switcher on the left)
YouTube Demonstration
Is that even possible for our devices O.O you have the courage of a jedi...
wow. its look really good. hope that there will be another dev to help u with that
I guess the easiest way is to just run it in chroot and connect via vnc. I.E., just install it in ubuntu chroot.
It may be tempting to run it natively, but there are obstacles.
1. I9100 has unified kernel for boot/recovery, so you cannot, say, replace recovery with custom kernel and boot android/meego based on which keys you hold
2. I9100 stock kernel has a lot of hacks and non-standard/broken drivers (touchscreen, framebuffer) that will need patching/fixing to work with native GNU/Linux build
3. There are no Mali400 opengl/egl libraries for exynos and GNU/Linux. I have not tried ones from st-ericsson u8500, but I guess they should work.
I have been porting i9100 support to vanilla kernel with the aim of running meego or, at least, SHR. I got linux 3.2.0 booting with half hardware working, but there are things to do. Some drivers need rewriting because my aim is to clean them up and submit to vanilla kernel.
-modem driver needs rewriting (userland power interface, better modemctl replacement)
-sensors drivers need rewriting (replace userland interfaces with input/iio like done for mainlined drivers)
-sound driver needs major rewriting (it is too complicated and does not even compile on 3.2. not to say it's crap and will never get accepted mainline in its current state)
-suspend and cpufreq are broken.
-mali400 needs porting from linaro tree
Other hardware (touchscreen, wifi, bluetooth, microsd, internal mmc, camera LED, camera, battery) are working though
sp3dev said:
I guess the easiest way is to just run it in chroot and connect via vnc. I.E., just install it in ubuntu chroot.
It may be tempting to run it natively, but there are obstacles.
1. I9100 has unified kernel for boot/recovery, so you cannot, say, replace recovery with custom kernel and boot android/meego based on which keys you hold
2. I9100 stock kernel has a lot of hacks and non-standard/broken drivers (touchscreen, framebuffer) that will need patching/fixing to work with native GNU/Linux build
3. There are no Mali400 opengl/egl libraries for exynos and GNU/Linux. I have not tried ones from st-ericsson u8500, but I guess they should work.
I have been porting i9100 support to vanilla kernel with the aim of running meego or, at least, SHR. I got linux 3.2.0 booting with half hardware working, but there are things to do. Some drivers need rewriting because my aim is to clean them up and submit to vanilla kernel.
-modem driver needs rewriting (userland power interface, better modemctl replacement)
-sensors drivers need rewriting (replace userland interfaces with input/iio like done for mainlined drivers)
-sound driver needs major rewriting (it is too complicated and does not even compile on 3.2. not to say it's crap and will never get accepted mainline in its current state)
-suspend and cpufreq are broken.
-mali400 needs porting from linaro tree
Other hardware (touchscreen, wifi, bluetooth, microsd, internal mmc, camera LED, camera, battery) are working though
Click to expand...
Click to collapse
My workflow would be :-
extract boot.bin from device
split into kernel, initrd, commandline
recombine to boot.bin
reflash to device
if it still boots andriod move on to
get kernel source and compile
combine new kernel zImage with commandline and initrd
flash to device
if it still boots android move on
edit kernel commandline to set root=/dev/mmcblkXp2 init=/sbin/init to pick up plasma active on partition 2 of a sdcard I have prepared or copied form Archos G9 images on web.
kernel should have a framebuffer device so I can see things but won't be accelerated unless I have Mali drivers for X11 backend, don't think we have seen any working baseband stuff so I don't expect to make calls.
Hi Folks,
I create new thread just for easy that we focus on kernel building here and continue with rom on existeing thread
This kernel is almost all standard very minor changed. config based on "prebuilt" Q8650_perf_defconfig. ramdisk is from 408 firmware. I installed 408 rom by olleh (odexed ... duhhhh). No optimation have been made since I have no idea what should be optimized. Give me idea ... LOL
- download zip file from this thread > no heavy since only 3.3 MB flashable via CWM. Get CMW from TheManii (my Guru in android compilation). See the kernel version is x1123
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what you get :
- customs kernel
- fully rooted system i.e you can do on fastbot $adb remount to have write access to device.
- suggest flash TheManii Streakdroid4-250 and immediately flash this kernel.
The main reason SD4 250 is hard to install is due to using a stock kernel, it's also the reason I havnt released SD5 250 at all (as there's plenty of alternatives)
If you're willing: just make a kernel with as little changes as possible, but with signature checking disabled for /system apks.
I dont think it's as simple as setting ro.secure=0 as I've made a modified ramdisk and it still fails on modified apks (pretty much every one in SDx 250 as I've added langs back to them)
I dont think I have the time to also learn how to recompile entire kernels, esp since SDx 25x is primarily intended for my own use. But I'd def like to release it with a modified kernal that would allow users to install it easier.
Hi TheManii.
This is my first time recompile linux kernel for android. It is really pain (comparing to recompile for PC). I will check and surf how to do your request. Just currious .. it is the kernel controlling /system/app/*.apk (?) ... need to check and learn kernel code then.
btw installing SD4-250 with default kernel I face FC many times when do setting on sound, receiving incoming calls, connect device to pc via usb port etc. But after flashing my kernel all FC gone ... I personally not sure it is because of kernel. But my venue now run smoothly powered by your SD4-250.
Btw I search on google and no lucks. How to get and add baseband (radio) file on ROM. I succeed to build a plaint rom can live on venue but always lack of GSM function. I dont think it caused by ril.d (ril_htc_d for htc) which is binary (?) or any ril_dell_d ... available
would you release SD5-250 ROM and let us work to do something to make dell venue have more options of customs rom.
Folks,
I can build a version of kernel-v4.06 myself. Run smoothly, no problem found so far. x1123's guide, if strictly followed, can bring such result to you.
It will be the best if you make it little under volt
sent via xda app
chacona said:
Folks,
I can build a version of kernel-v4.06 myself. Run smoothly, no problem found so far. x1123's guide, if strictly followed, can bring such result to you.
Click to expand...
Click to collapse
Navigation and maps crash when using your otherwise smooth running kernel. Can you please look into it.
Sent from my Dell Venue using Tapatalk 2
I've got a Samsung Galaxy Alpha (EU) and started to create a recovery. It doesn't fully work yet but we will get there ...
You can get the sources here: http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/
My phone arrived and I got the recovery working. Looks like some features aren't working yet. I need to dive deeper and get the kernel compiled.
hensk said:
Do you have experience to unlock Art in Developer setting coz is kernal related
will be nice to have it
Click to expand...
Click to collapse
you can try by replacing libdvm.so to libart.so in /data/property/persist.sys.dalvik.vm.lib
the adb command for should be: adb shell 'echo libart.so >/data/property/persist.sys.dalvik.vm.lib'
i would like to remind you that ART and exposed are not compatible. i also read that samsung's touch wiz will crash or cause bootloop with ART. you can do a backup and try ART. in case you have bootloop just restore, install another launcher, unistall touch wiz and you should be fine
in case you will try, please report back and let us know how it went.
I was able to fix the kernel to build it with the CM toolchain. Next step is using a built kernel. After that it is time to start with CM.
neofral said:
you can try by replacing libdvm.so to libart.so in /data/property/persist.sys.dalvik.vm.lib
the adb command for should be: adb shell 'echo libart.so >/data/property/persist.sys.dalvik.vm.lib'
i would like to remind you that ART and exposed are not compatible. i also read that samsung's touch wiz will crash or cause bootloop with ART. you can do a backup and try ART. in case you have bootloop just restore, install another launcher, unistall touch wiz and you should be fine
in case you will try, please report back and let us know how it went.
Click to expand...
Click to collapse
Thanks neofral,for scripts info but about
not compatibility ART with Wanam I know this issue i have SGS 4 also
modpunk said:
I was able to fix the kernel to build it with the CM toolchain. Next step is using a built kernel. After that it is time to start with CM.
Click to expand...
Click to collapse
you dude building kernal also,will it work with TW roms or only for CM
The plan is to get it first working with the TWRP recovery. The rooting stuff should be disabled. And I need adb working on the recovery. Currently you can't get a 'adb shell' on the recovery.
I ran into several issues building the kernel. A lot of fixes are needed, especially for a out of source build. The CM toolchain is old which is also an issue. But the biggest problem is that the dts files are missing to build the Device Tree ...
modpunk said:
I ran into several issues building the kernel. A lot of fixes are needed, especially for a out of source build. The CM toolchain is old which is also an issue. But the biggest problem is that the dts files are missing to build the Device Tree ...
Click to expand...
Click to collapse
i think it's a serious issue since CM officially don't support Exynos platform anymore. they say it's about Samsung Knox but i'm sure there are other things in the play.
if your aim is to build a kernel for our devices i think it's much better to have an awesome kernel for stock rom first and leave some time to see how things develop in CM community with regards to Exynos
neofral said:
i think it's a serious issue since CM officially don't support Exynos platform anymore. they say it's about Samsung Knox but i'm sure there are other things in the play.
if your aim is to build a kernel for our devices i think it's much better to have an awesome kernel for stock rom first and leave some time to see how things develop in CM community with regards to Exynos
Click to expand...
Click to collapse
This was just of issues with Exynos 4, see https://plus.google.com/+CyanogenMod/posts/2a8SiSZpxPn
I've sent a mail to the Samsung using their form on the opensource website. Lets see if they will release new Kernel sources.
I finally got the kernel built in the CM tree and it works using the stock dtb file. Now I need to fix adb/mtp.
hensk said:
hi m8
You already have progress in building your recovery & kernal
send it to me if you like tester
Click to expand...
Click to collapse
In the meantime mtp is correctly starting up after fixing the init system. Parsing /proc/cpuinfo failed cause the buffer was to small for a octa core. adb still doesn't start. I will try tomorrow or on the weekend...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah, finally a adb shell as root on the recovery! Time to start with CM ...
Mod Edit
Thread cleaned.
Unless you are a developer and contributing to this project , please refrain from posting here.
Thank you
malybru
Forum Moderator
Alright, I just made a custom kernel based on current Android Oreo build 41.3.A.2.234 which enabled root properties and you can flash it by using fastboot method and then, you can install Magisk and also drmfix on TWRP after flashing the custom kernel. Just got an idea to create this custom kernel by editing the rootkernel script and this custom kernel might fix some issues especially the chrome browser turned into "Android Go" mode due to tiny swap partition.
Before installing, make sure that you have current Android Oreo build 41.3.A.2.234 installed on Xperia XZs G8231 or G8232 model and the bootloader must be unlocked first (you will need to perform backup on TA partition first before doing so - I'm really didn't noticed about that part before unlocking my device so don't follow my mistakes by not performing TA partition backup before unlock the bootloader!)
One more thing to remember - DO IT AT YOUR OWN RISK!!!
Download it here:
G8231: [Google Drive link]
G8232: [Google Drive link]
Note: If you did not have current firmware build installed, you can install it by using Xperia Flashtool program. Make sure that you are flashing the right kernel for your device model. You will be not entertained if you ask on how to unlock bootloader and even flashing the custom kernel. You should know the risk of flashing the wrong kernel and you should know how to handle it.
UPDATE: Adding the G8232 custom kernel as requested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great work sir :good:
great work for this and is able to dual sim version ??
Dark Pwince said:
great work for this and is able to dual sim version ??
Click to expand...
Click to collapse
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.
amirzaim said:
Not tested yet on dual-sim version because I don't have that device. You may want to try it out but at your own risk.
Click to expand...
Click to collapse
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?
QPR_FC said:
Can anybody confirm whether this works on dual sim?
Does both SIM get recognised in the phone using this boot.img kernel?
Click to expand...
Click to collapse
Ok...just flash the G8232 custom kernel which I posted here recently.
amirzaim said:
Ok...just flash the G8232 custom kernel which I posted here recently.
Click to expand...
Click to collapse
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file
QPR_FC said:
Thanks, because I tried to create my own using Rootkernal v5.23 and the tool kept bombing out....
[email protected]:~/Documents/SONY/rootkernel$ ./rootkernel.sh kernel.elf boot.img
================================================================================
-------------------ROOTKERNEL V5.23 FOR XPERIA DEVICES--------------------------
================================================================================
-e Rootkernel V5.23
kernel.elf: kernel.elf: cannot execute binary file
Click to expand...
Click to collapse
Probably a few of x-executable files which didn't set its permission for executable: bootimg, busybox, init and even rootkernel.sh itself
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Universal SafetyNet Fix for Samsung Devices
Magisk Modded Module for OneUI 2.5 & 3.1
Original dev : @kdrag0n
This is a universal fix for SafetyNet on devices with hardware attestation and unlocked bootloaders. It defeats both hardware attestation and the new SafetyNet CTS profile updates released on January 12, 2021. The only requirement is that you can pass basic attestation, which requires a valid combination of device and model names, build fingerprints, and security patch levels.
Passing basic attestation is mostly out-of-scope for this module; this module is meant to defy hardware attestation, as well as reported "basic" attestation that actually uses hardware under-the-hood. Nonetheless, it features a few basic attempts at helping pass basic attestation on some devices, especially older devices and devices running stock ROMs. No device-specific features (such as the new Pixel-exclusive Google Assistant design or screen-off voice match) will be lost with this fix.
This Magisk Module is modded to work on every Samsung Device.
No more biometrics errors and random reboots.
Works on every OneUI 2.5 & OneUI 3.1 ROM.
For GSI ROM use the original one here.
Instructions:
Install MagiskHide Props, set props to A50 if needes.
Install modded SafetyNet Fix module and reboot.
Enable MagiskHide in Magisk Settings.
Voala, you passed safetynet.
Changelog V2
- Fixed Biometrics issues on OneUI 3.1 (Android 11)- Fixed random reboots or bootloops- All Samsung Devices supported
Hello XD
It works?
Ugly.n.depressed said:
It works?
Click to expand...
Click to collapse
Try it, it really works! ; )
installed, i restart in recovery but when the samsung logo shows up freeze and restart in normal mode, now i dont have magisk and i dont what do now
I'm on latest FreshROM, Magisk 20.4 and this module. Installed as it was said on the first post. Works like a charm.
Which ROM are you using? Maybe your problem is somehow related with ROM.
TheHEARER said:
I'm on latest FreshROM, Magisk 20.4 and this module. Installed as it was said on the first post. Works like a charm.
Which ROM are you using? Maybe your problem is somehow related with ROM.
Click to expand...
Click to collapse
I've tested it on Cobra & FreshROMs and it works on both. I think the guy above is doing something wrong tho.
What I did:
- installed Magisk Hide from Magisk,
- installed module which I downloaded from this thread via Magisk by Install from storage option.
TheHEARER said:
What I did:
- installed Magisk Hide from Magisk,
- installed module which I downloaded from this thread via Magisk by Install from storage option.
View attachment 5209789
Click to expand...
Click to collapse
Maybe he doesn't know how to set props.
Anyways, hello brother! Greets from Czechia
rvdekoff said:
Maybe he doesn't know how to set props.
Anyways, hello brother! Greets from Czechia
Click to expand...
Click to collapse
It is not a problem when you know how to do some sort of things. For any others who have any problems, follow instructions in my and first post. I guarantee, everything should work as it should be.
Greetings from Poland rvdekoff! ; )
Thank ypu sir it worked for me
This one should work for OneUI 3.1 too, if someone have time to test it, lemme know.
rvdekoff said:
This one should work for OneUI 3.1 too, if someone have time to test it, lemme know.
Click to expand...
Click to collapse
Ok i will test
rvdekoff said:
This one should work for OneUI 3.1 too, if someone have time to test it, lemme know.
Click to expand...
Click to collapse
a505f its work?
I'm sorry, but how do i set props?
How i can unninstall it after bootloop?
Error on Samsung S4 mini VE - Unsupported CPU arch armeabi-v7a
If you do upload video, I could not upload it, please help me.
Don't have an upload video?