[ABANDONED] AndroPlusKernel v43
- Thread starter AndroPlus
- Start date
Updated v43 with 372 source
I also updated alucard CPU gov to v5.0 (experimental).
DRM patch and touch in recovery are not working because of /vendor.
I'll look into it.
You mean this patch https://xdaforums.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383/ ?
Yeah I didnt install v42 just v43 in fastboot while being on .376 what will flashing v42 do because it doesnt support Nougat. Also I have recovery now and root just touch screen is hit and miss sometimes it works sometimes it doesnt. Thanks.
AndroPlus Andralex have made a great TWRP(we are testing lineageOS 7.1.1) which works with any kernel. It works because it's loaded by bootloader(vol- and power-button until it vibrates). I did not uploaded because I haven't ask the permission yet. But it's great recovery. please contact Andralex.
I'd be happy to test lineageOS on SGP712 if you need a hand. Using CM13 at present and I already have TWRP loaded into recovery partition.
As I understand this is for people who have backup of TA. But what to do other people who havent it?
This has happened for me too. Get a USB-OTG cable and use a mouse to navigate.
Somehow, my current TWRP flash was more successful, as I don't have the problem now. Same TWRP build, as far as I know.
Hallo All,
I have a little bit Problem with my Xperia Z4T SGP771. The Bootloader is Unlocked. I have the Firmware 32.3.A.0.378 on it. I have do flash the Androplus v42 then TWRP 3.0.2.0 then Androplus v43 and then SuperSU.
I have this read here for to do. It dont run´s. After the flashing Androplus v42 and the TWRP and reboot, i can come in to the TWRP, it was freeze. When i now reboot with a Mouse on the OTG it run´s. When i now flash Androplus v43 and SuperSu, i dont have the TWRP and no Root. What must i do, or what i make wrong ?
Please help me. I have read so many, and notting help´s.
I have a little bit Problem with my Xperia Z4T SGP771. The Bootloader is Unlocked. I have the Firmware 32.3.A.0.378 on it. I have do flash the Androplus v42 then TWRP 3.0.2.0 then Androplus v43 and then SuperSU.
I have this read here for to do. It dont run´s. After the flashing Androplus v42 and the TWRP and reboot, i can come in to the TWRP, it was freeze. When i now reboot with a Mouse on the OTG it run´s. When i now flash Androplus v43 and SuperSu, i dont have the TWRP and no Root. What must i do, or what i make wrong ?
Please help me. I have read so many, and notting help´s.
To enter TWRP again after installing V43, you need to enter fastboot again, push/flash v42 and twrp, and then enter, install v43, supersu (again if it failed ofc)
So its kinda icky needing to go backwards to install something in TWRP. Not that Nougat (Android 7.0) needs much flashing in it as no xposed or anything is released for it. Nor any 7.0 custom rom that ive seen.
Thanks a lot AndroPlus, for supporting this great tablet, with your kernel and TWRP builds. I think the latest kernel version you delivered is fine, at least the version I'm running is (a few versions behind). It made me enjoy the Z4 Tablet way more than when it was stock.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
28***ABANDONED***
I am sorry but I stopped supporting this kernel because I don't have much time recently.
This is first custom kernel for Xperia Z4 Tablet SGP712/SGP771.
Download
Download from official website
How to root
See my blog post:
https://androplus.org/Entry/626/
I won't create kernel for device which I don't own.
If you want me to create, please give me the device.
Donate:
PayPal
XDA:DevDB Information
AndroPlusKernel for Z4 Tablet, Kernel for the Sony Xperia Z4 Tablet
Contributors
AndroPlus, Tommy-Geenexus, DHGE, dl12345, andip71, nilezon
Source Code: https://github.com/AndroPlus-org/android_kernel_sony_msm8994
Kernel Special Features:
Version Information
Status: Testing
Created 2015-08-02
Last Updated 2017-05-0410Sony released kernel source, so I'll start porting today.
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-32-1-a-1-163/
OK, I'll remove changes and release last lollipop update.10@DHGE and @AndroPlus
I've been walking through the binaries of both TWRP as well as touch_fusion, I seriously am dumbfounded by what I couldn't find: the location/binary from which touch_fusion is started... it was beyond my comprehension... seriously mind gobbling
After another attempt to find out what caused touch_fusion to start I searched and searched and finally think to have found the cause and solution :victory:
From what I gather, there are still some config files being read from system, other then the firmware file, the path to these files is hardcoded in the binary, which means that we will need to patch the binary to allow a different path to use them. It also uses 2 libraries from the /system/lib64 folder to function according to the touch_fusion.idc.
I have FINALLY found where touch_fusion is getting started: from the kernel driver :victory:
# This seems to be date-time related and probably used to calibrate timing:
/system/usr/share/zoneinfo
/system/usr/share/zoneinfo/zoneinfo.idx
/system/usr/share/zoneinfo/zoneinfo.dat
# The firmware location is hardcoded in to the touch_fusion binary (this is a good thing, hurray!):
/vendor/firmware/max11945.bin
# The libaries it is using according to the idc file (but the binary has no reference to them):
/system/lib64/touchfilter/tfsw.so
/system/lib64/touchfilter/roadrunner_ukf.so
This is in the kernel config for the MAXIM_STI touch panel driver:
https://github.com/AndroPlus-org/an...om/msm8994-kitakami_karin_common.dtsi#L82-L85
maxim_sti.c
maxim_sti.h
max11801_ts.c (probably linked to the binary firmware file used in the ROM, though I don't know for sure)
Updating the driver to load from /vendor should not even break the stock rom functionality... That should make for an easy test during development
The setting on line 84 seems to be ignored by the touch_fusion binary (luckily)...
Anyway... to make touch_fusion work system-less:
- We will need to incorporate the libraries in the vendor folder;
- Patch the touch_fusion binary to use them and zoneinfo from there too;
- Copy all related idc/config files to the vendor folder together with the config files (which are already stored in the vendor/etc folder in the ramdisk);
- The kernel driver needs a patch, loading touch_fusion from the ramdisk vendor folder instead of from system.
- http://xdaforums.com/showpost.php?p=65212357&postcount=201
The down side of these discoveries is that we will probably need to create a kernel module which overloads the built-in functionality for locked bootloader devices to make this all work trouble free if locked bootloader root is ever found... but let's start with fixing the UB TWRP
A big thanks go to @jelbo, for helping me test using Google Hangouts, that lead to the discovery of the touch_fusion daemon getting started with a touch of the screen and the reason why I started digging in the kernel sources... :highfive:7Features and changelog
I won't answer questions or requests for older version (e.g. "Please update kernel for old firmware!")
Moved to here7
Ok, let's see if I can give you a few pointers for getting TWRP to work. There are two possible configurations you can use
- AOSP kernel
- Sony copyleft kernel
1. AOSP Kernel
This one is fairly easy to get working. You just need to look at my commits on the TWRP branch. Import the device and vendor trees directly from the Sony AOSP source and use their prebuilt AOSP kernel. When building using the CM build environment, the key items are RECOVERY_VARIANT=twrp and BOARD_KERNEL_CMDLINE in the BoardConfig.mk and installation of the TWRP sources in bootable/recovery-twrp.
The disadvantage of this variant is that you're forever doomed to use it in fastboot mode. It's not flashable.
2. Sony 28.0.A.8.251 Kernel
This one is much harder to get working. Look at my commits under the branch TWRP-28.0.A.8.251.
The advantage to this variant is that you can create a flashable TWRP. The way in which this is done is to create a ramdisk that contains a cpio image of the normal boot ramdisk and then you flash the recovery image to the FOTAKernel partition. At boot time, a pseudo init script checks for a keypress. If it finds one, it uses extract_elf_ramdisk to extract the recovery image ramdisk from the FOTAKernel partition, un-cpio's it and then execs the real init. If no keypress occurs, the same thing is done to the cpio image of the normal boot ramdisk.
Obviously, when you look at the steps required to get a flashable recovery, it's clear that the main boot and the recovery need to use the same kernel. Ergo, for a flashable recovery you need to use the Sony copyleft kernel. Here's where some of the problems start to occur. In no specific order,
- Sony kernel sources are incomplete. Several kernel modules, not included in the source downloads, are critical. I pulled the binaries off my device (since they're compiled for the same kernel) and put them into the ramdisk, loading them with an insmod at boot time in the init.qcom.rc script. In particular, one of these completes the initialization of the SoC, without which many /sys/class nodes critical to proper functioning of TWRP don't exist and adb doesn't work. Look at the recovery/root folder on the device_sony_ivy repository to identify these kernel modules
- AOSP and Sony copyleft use a different hardware identifier: AOSP uses kitakami and Sony uses qcom. So you need to rename the various init files to be init.qcom.rc, for example
- Sony copyleft uses dtb version 3.0. Most of the dtbtools are version two. I had endless trouble with this so I added a custom dtbtool to the build. See my vendor_sony_system_dtbtool repository
- Ditto issues with mkbootimage. I created a custom one, vendor_sony_system_mkivybootimg
- The kernel uses a separate dt.img. You need to specify this in the BoardConfig.mk. You then need to make a customkbootimg.mk file that calls dtbtool. You can find this in device_sony_kitakami. Mine is still missing the final steps to create a combined boot image (necessary for dual boot as described above) - I created the dual boot image manually so far. Note carefully that the pagesize on the dt command is NOT the same as the pagesize in the BoardConfig.mk. The latter is 4096 and the dt is 2048. When I tried to use the same pagesize it wouldn't boot. I got the 2048 directly from the Sony instructions on how to build a kernel using copyleft sources in the README_Xperia file.
- You need to add the diffconfig contents to the main kernel config otherwise it won't boot as it's missing key config defines
- You need to modify the kernel commandline otherwise TWRP won't boot. See the commandline in BoardConfig.mk in the device_sony_kitakami repository
- Add the extract_elf_ramdisk if you want to make a flashable recovery. You need to modify the source to support kitakami devices as the default buffer size is too small to contain the extracted ramdisk. I doubled it.
When you build, make sure to do a "make clobber" first. Hope this helps somewhat....
![[NUT]](/data/avatars/s/4904/4904057.jpg?1600603615){kind=avatar}
New posts
-
Question SAMSUNG S22 ULTRA NEED HELP PLZ!!!!!!!!!!!!!!!
- Latest: donkeyman1234
