[KERNEL] [UNIFIED] Anykernel

Search This thread

mvn_

Member
Oct 28, 2017
18
2
0
You have flashed Systemless SuperSu*? Could cause trouble from what I read on Google.

When I got my hands on this tablet last week, it was running on Android 4.0.2, I think.
Then I tried to install some Roms such as Lineage 13 and Slim. The only one that worked was "Slim-p3100-4.4.4.build.9.4-UNOFFICIAL".

The recovery that I was using said something about "restore root access" (I really can't remember if it was exactly this) when I was going to reboot, I choose "Yes" but it was only 2 days ago that I opened SuperSu for the first time and it was saying "binary occupied", then I did the root following this thread.
 

mvn_

Member
Oct 28, 2017
18
2
0
Hello Andi, sorry to bother you again.

I'm trying to update my TWRP (the one I'm using it's still 3.0.0) but newer ones have the same problem that I was having with roms. I saw that in the LineageOS 13 thread you posted an AnyKernel version for a user with P3110 to flash recoveries. Comparing the files, the only difference that I could see was that the anykernel.sh have the word "KERNEL" changed to "RECOVERY" in "shell variables".

I tried to do the same thing with the AnyKernel file for my P3100 but when trying to flash, it gives me an "ERROR: 1". Is there anything else I could do?

Thanks.
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,224
0
andi34.github.io
Hello Andi, sorry to bother you again.

I'm trying to update my TWRP (the one I'm using it's still 3.0.0) but newer ones have the same problem that I was having with roms. I saw that in the LineageOS 13 thread you posted an AnyKernel version for a user with P3110 to flash recoveries. Comparing the files, the only difference that I could see was that the anykernel.sh have the word "KERNEL" changed to "RECOVERY" in "shell variables".

I tried to do the same thing with the AnyKernel file for my P3100 but when trying to flash, it gives me an "ERROR: 1". Is there anything else I could do?

Thanks.
Use the anykernel.zip for your variant and edit the anykernel.sh

do.modules=1
change to
do.modules=0

block=/dev/block/platform/omap/omap_hsmmc.1/by-name/KERNEL;
change to
block=/dev/block/platform/omap/omap_hsmmc.1/by-name/RECOVERY;


Save the file.
If you are on Windows use Notepad++

Now flash the zip directly after updating the recovery.

Might work, but not tested.
 

mvn_

Member
Oct 28, 2017
18
2
0
Use the anykernel.zip for your variant and edit the anykernel.sh

do.modules=1
change to
do.modules=0

block=/dev/block/platform/omap/omap_hsmmc.1/by-name/KERNEL;
change to
block=/dev/block/platform/omap/omap_hsmmc.1/by-name/RECOVERY;


Save the file.
If you are on Windows use Notepad++

Now flash the zip directly after updating the recovery.

Might work, but not tested.

"ERROR: 1" again... But that's no big deal, I can still flash some roms with this recovery. The only one that gave me errors while flashing was Slim7, so I tought it was because my old TWRP.

By the way, what rom do you personally think runs better on this device? I don't care about having the latest android version.
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,224
0
andi34.github.io
"ERROR: 1" again... But that's no big deal, I can still flash some roms with this recovery. The only one that gave me errors while flashing was Slim7, so I tought it was because my old TWRP.

By the way, what rom do you personally think runs better on this device? I don't care about having the latest android version.
Can you pull /tmp/recovery.log?
This will tell what's up, maybe it doesn't like the lzma compression...

but you could change the zImage of an recovery.img on a Linux machine, it's quite easy.
 

mvn_

Member
Oct 28, 2017
18
2
0
Can you pull /tmp/recovery.log?
This will tell what's up, maybe it doesn't like the lzma compression...

but you could change the zImage of an recovery.img on a Linux machine, it's quite easy.

Code:
Android-Andi @ xda-developers
 
AnyKernel2 by osm0sis @ xda-developers
 
Installing kernel...
/tmp/anykernel/anykernel.sh: line 3: 
: not found
/tmp/anykernel/anykernel.sh: line 7: kernel.string=Android-Andi: not found
/tmp/anykernel/anykernel.sh: line 8: do.devicecheck=1
: not found
/tmp/anykernel/anykernel.sh: line 9: do.modules=0
: not found
/tmp/anykernel/anykernel.sh: line 10: do.cleanup=0
: not found
/tmp/anykernel/anykernel.sh: line 11: do.cleanuponabort=0
: not found
/tmp/anykernel/anykernel.sh: line 12: device.name1=espresso
: not found
/tmp/anykernel/anykernel.sh: line 13: device.name2=espresso3g
: not found
/tmp/anykernel/anykernel.sh: line 14: device.name3=espresso-common
: not found
/tmp/anykernel/anykernel.sh: line 15: device.name4=espressowifi
: not found
/tmp/anykernel/anykernel.sh: line 16: device.name5=p3100
: not found
/tmp/anykernel/anykernel.sh: line 17: device.name6=p3110
: not found
/tmp/anykernel/anykernel.sh: line 18: device.name7=p3113
: not found
/tmp/anykernel/anykernel.sh: line 19: device.name8=p5100
: not found
/tmp/anykernel/anykernel.sh: line 20: device.name9=p5110
: not found
/tmp/anykernel/anykernel.sh: line 21: device.name10=p5113
: not found
/tmp/anykernel/anykernel.sh: line 22: device.name11=espressowifixx
: not found
/tmp/anykernel/anykernel.sh: line 23: device.name12=espresso10wifixx
: not found
/tmp/anykernel/anykernel.sh: line 24: device.name13=espressorf
: not found
/tmp/anykernel/anykernel.sh: line 25: device.name14=espressorfxx
: not found
/tmp/anykernel/anykernel.sh: line 26: device.name15=espresso10rf
: not found
/tmp/anykernel/anykernel.sh: line 27: device.name16=espresso10rfxx
: not found
/tmp/anykernel/anykernel.sh: line 28: syntax error: unexpected "}"
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
Error installing zip file '/sdcard/AnyKernel-2017-11-04-17-13-P3100-ONLYrecovery.zip'
Updating partition details...
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
 

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,224
0
andi34.github.io
Looks like you've not had an Texteditor with Unix EOL or haven't had it enabled.

Edit:
You'll need to do on PC running Linux, lzma compressed ramdisk isn't supported
 
Last edited:

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,224
0
andi34.github.io
Nope, you need to unpack the recovery.img, replace the zImage and repack it.

Mh... Another solution on Windows:
https://goo.gl/vnYpFD

Unzip it twice, once named common, once named p3100.

Place the proper recovery.img inside (p3100 recovery.img inside the p3100 folder, common inside the common folder).

In both folders Drag and drop the recovery.img on the unpackimg.bat to split ramdisk and kernel.


Now you get a ramdisk folder. Replace the one inside the p3100 folder with the ramdisk folder from common (delete everything inside the p3100 ramdiskfolder first)

Now run the repackimg.bat

The new_recovery.img should work as it's using the p3100 kernel.


(Not sure if you understand what I am writing :p)
 
  • Like
Reactions: mvn_

mvn_

Member
Oct 28, 2017
18
2
0
Nope, you need to unpack the recovery.img, replace the zImage and repack it.

Mh... Another solution on Windows:
https://goo.gl/vnYpFD

Unzip it twice, once named common, once named p3100.

Place the proper recovery.img inside (p3100 recovery.img inside the p3100 folder, common inside the common folder).

In both folders Drag and drop the recovery.img on the unpackimg.bat to split ramdisk and kernel.


Now you get a ramdisk folder. Replace the one inside the p3100 folder with the ramdisk folder from common (delete everything inside the p3100 ramdiskfolder first)

Now run the repackimg.bat

The new_recovery.img should work as it's using the p3100 kernel.


(Not sure if you understand what I am writing :p)

I think I undestand, will try later and post the results. :good:

Edit: @Android-Andi The flash goes ok but then the device goes to a bootloop, re-flashing the 3.0.0 makes is work again.

Just to make sure: after repacking I should rename the new file to recovery.img and replace the one inside the common zip file?
 
Last edited:
  • Like
Reactions: Android-Andi

guest4711

Senior Member
New AnyKernel passes SafetyNet on "user" builds, thanks to @Ziyan !
Some tiny updates.
Enjoy!
Booting fine on RR 5.7.4., thanks. Should there be any problems I'll report here.
 

Attachments

  • Screenshot_20171111-185152.png
    Screenshot_20171111-185152.png
    85.1 KB · Views: 205

mvn_

Member
Oct 28, 2017
18
2
0
Edit: @Android-Andi The flash goes ok but then the device goes to a bootloop, re-flashing the 3.0.0 makes is work again.

Just to make sure: after repacking I should rename the new file to recovery.img and replace the one inside the common zip file?

Sorry for bumping, but I think Andi didn't receive a notification about my mention in the edit.
 
Last edited:

Android-Andi

Recognized Contributor
Mar 3, 2013
10,846
29,224
0
andi34.github.io
I've added new device specific AnyKernel because i noticed i used an old defconfig as base on last build.
I've also now added device specific kernel for KitKat Roms.

Please note:
  • Device specific kernel won't get regular updates here!
  • Only flash device specific kernel if you are having issues (your device variant isn't detected right and it will use wrong driver)!

I might post one last device specific TWRP in my TWRP Thread later this week.
 

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
New AnyKernel passes SafetyNet on "user" builds, thanks to @Ziyan !
Some tiny updates.

Enjoy!

Hi Andi, could you please explain which combo is able to have Netflix etc.? Tried it with the Slim_espressowifi-6.0.1-20171117-2255 + AnyKernel-2017-11-11-18-16-espresso -but still the CTS profile doesn't match, the same since a long time... i hope not the stable ones from Slim site + AnyKernel because of the old security updates... :fingers-crossed: DANKE für deine Arbeit, mien Jung ;)
 

Attachments

  • Screenshot_20171124-020040.png
    Screenshot_20171124-020040.png
    44.1 KB · Views: 89
  • Screenshot_20171124-020054.png
    Screenshot_20171124-020054.png
    47.5 KB · Views: 95

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    ANYKERNEL
    espressowifi / espresso3g


    Please respect the following 2 points

    • No feature requests!
    • Overclocked Kernel can be found here
    NOTE:
    This product is provided "as is" without any warranty. Use on your own risk.
    I am not responsible for burned CPU or GPU.

    Any kind of OC is really dangerous on Galaxy Tab2. While OMAP 4460 has a built-in temperature sensor, OMAP 4430 doesn't have one. Nothing stops it from overheating...


    If you don't read and respect the OP, you accept to make a donation of 50$ to a charity of your choice!
    [#WARRANTY]

    It is difficult to update all Roms frequently, and it does not always makes sense to compile, download and flash a whole rom, if only some kernel changes are applied.

    This kernel will include changes before i add them official to our kernel source (most of the time security bugfixes)!
    Android 5.1 and Android 6.0
    This Kernel works on all Android 5.1 and Android 6.0 Roms for espressowifi and espresso3g.

    Android 4.4
    On Android 4.4 we need a different kernel, 4.4 Kernel includes "KitKat" tag on zip name.

    What else to say
    • Kernel compiled using GCC 4.8
    • Anykernel based on Anykernel2 by @osm0sis ( https://github.com/osm0sis/AnyKernel2 ) - it will dump your boot.img and replace the zImage and add proper kernel modules.

    Roms with default libion
    LineageOS (unofficial)
    espresso3g
    • lineage-11-20180131-2053-UNOFFICIAL-espresso3g.zip and newer
    • lineage-13.0_espresso3g-6.0.1-20180130-2211.zip and newer
    • lineage-14.1_espresso3g-7.1.2-20180131-1859.zip and newer
    espressowifi
    • lineage-11-20180131-2033-UNOFFICIAL-espressowifi.zip and newer
    • lineage-13.0_espressowifi-6.0.1-20180130-2146.zip and newer
    • lineage-14.1_espressowifi-7.1.2-20180131-1818.zip and newer

    OmniRom (unofficial)
    espresso3g
    • omni_espresso3g-4.4.4-20180127-2337.zip and newer
    • omni_espresso3g-6.0.1-20180128-0312.zip and newer
    • omni_espresso3g-7.1.2-20180128-1319.zip and newer
    espressowifi
    • omni_espressowifi-4.4.4-20180127-2310.zip and newer
    • omni_espressowifi-6.0.1-20180128-0251.zip and newer
    • omni_espressowifi-7.1.2-20180128-1254.zip and newer

    SlimRoms (unofficial)
    espresso3g
    • Slim-espresso3g-4.4.4.build.9.15-UNOFFICIAL-20180128-0125.zip and newer
    • Slim_espresso3g-6.0.1-20180128-2332.zip and newer
    • Slim_espresso3g-7.1.2-20180131-1617.zip and newer
    espressowifi
    • Slim-espressowifi-4.4.4.build.9.15-UNOFFICIAL-20180128-0028.zip and newer
    • Slim_espressowifi-6.0.1-20180128-2308.zip and newer
    • Slim_espressowifi-7.1.2-20180131-1555.zip and newer

    Unlegacy-Android:
    All official Unlegacy-Android builds starting on 15th feburary use the default libion


    Roms with new DDK
    Slim6 , Slim7, OmniROM4, OmniROM 6, OmniROM 7 and LineageOS 11, LineageOS 13 and LineageOS 14.1 compiled after 01.03.2019

    [#DONATETOME]

    XDA:DevDB Information
    (unified) Anykernel, Kernel for the Samsung Galaxy Tab 2

    Contributors
    Android-Andi, Ziyan
    Source Code: https://github.com/Unlegacy-Android/android_kernel_ti_omap4/commits/3.0/common

    Kernel Special Features: Testing before applying on our source official, CVE fixes

    Version Information
    Status: Testing

    Created 2016-10-21
    Last Updated 2020-05-02
    17
    Update
    • cve-2015-0565
    • cve-2016-8655
    • cve-2015-8966
    • cve-2014-8709
    • cve-2014-9420
    • cve-2016-10044
    • cve-2016-10088
    • cve-2015-8019
    • cve-2016-10208
    • cve-2016-1583
    • cve-2016-6786 & cve-2016-6787
    • cve-2016-9754
    • cve-2016-9794
    • cve-2016-9793
    16
    Fixes CVE-2017-0706 and CVE-2017-1000251
    15
    Since this community can't be silent about OC for Tab2 i've picked OC changes from @ketut.kumajaya to our new common kernel.
    Applied OC Patches have been very well tested in the past on our old kernel.
    • Needed patch files are attached if you like to compile your own kernel.
    • I've kept authorship on all commits, also i've kept Authorship and notes inside Voltage Control code.
    • not applied undervolting on default frequencies

    Limitations:
    • Limit maximum CPU frequency @ 1.35GHz , GPU @ 384 Mhz

    NOTE:
    This product is provided "as is" without any warranty. Use on your own risk.
    I am not responsible for burned CPU or GPU.

    Any kind of OC is really dangerous on Galaxy Tab2. While OMAP 4460 has a built-in temperature sensor, OMAP 4430 doesn't have one. Nothing stops it from overheating...


    • This will be a "one-time-only" kernel.
    • It's compatible with my ROMs compiled since March 2019
      (Should work on my Slim6 + 7, Omni 6 + 7 and LineageOS 13 + 14.1 compiled after 01.03.2019.
      Special KitKat Kernel attached which should work on my SlimKat, Omni 4 and LineageOS 11 compiled after 01.03.2019).
      • don't use it on older ROMs
      • don't use on ROMs i haven't compiled

    You need root and an app like Kernel Adiutor to enable GPU 384 Mhz frequency.
    CPU will work up to 1.35 GHz without root.
    Code:
    $ adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
    1350mhz: 1360 mV
    1200mhz: 1325 mV
    1008mhz: 1388 mV
    800mhz: 1325 mV
    600mhz: 1200 mV
    300mhz: 1025 mV

    I've quickly tested the kernel on Slim6.

    Edit:
    attached another version ("OC-TEST-UV") with undervolting on default frequencies
    Code:
    $ adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
    1350mhz: 1360 mV
    1200mhz: 1325 mV
    1008mhz: 1274 mV
    800mhz: 1213 mV
    600mhz: 1100 mV
    300mhz: 925 mV

    And a 3rd version with undervolting on default frequencies and GPU @ 384 Mhz by default ("OC-TEST-UV-GPUOC")
    15
    One more update.
    • updates to dsscomp & dss/manager,
    • enabled ColorControl for tuna
    • enable BFQ-v7r8 I/O scheduler

    Why there's 2 Kernels?
    • 1st kernel use BFQ-v7r8 I/O scheduler for 3.0 kernel
    • 2nd kernel uses BFQ-v7r8 I/O scheduler for 3.3 kernel - needs a bunch of backports from 3.3 kernel to work (would be good if we don't need them)
    I have never added BFQ scheduler on espresso because it was always buggy (crashes frequently, e.g. if you switch from bfq to anything else after boot)
    Only added for testing. - if it works well, we can discuss to add it by default.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone