HELLO EVERYONE
I AM CURRENTLY DEVELOPING A ROM AND I WANT TO KNOW HOW TO ADD V6 SUPERCHARGER SCRIPT TO
MY ROM
--abhishekr700
just run v6 supercharger in your rom - set it all up then pull your system to your pc either with adb or use the tar command in android terminal emulator on phone and copy to pc
then use the tar file generated in android kitchen to set up working folder
one more thin
i started building rom from stock rom and stock kernel
i added int.d support via android kitchen
so will init.d work
one more thin
i started building rom from stock rom and stock kernel
i added int.d support via android kitchen
so will init.d work
yes if the user uses a kernel that supports init.d
marcussmith2626 said:
just run v6 supercharger in your rom - set it all up then pull your system to your pc either with adb or use the tar command in android terminal emulator on phone and copy to pc
then use the tar file generated in android kitchen to set up working folder
Click to expand...
Click to collapse
But I have already built much of the rom.
Isn't there a way to add it by other method
Like I run v6 supercharger on my phone then copy 99supercharger from init.d folder to my rom init.d folder
Also my stock rom has stock kernel
And I added init d support to my rom via kitchen
Will.init.d script work
abhishekr700 said:
But I have already built much of the rom.
Isn't there a way to add it by other method
Like I run v6 supercharger on my phone then copy 99supercharger from init.d folder to my rom init.d folder
Also my stock rom has stock kernel
And I added init d support to my rom via kitchen
Will.init.d script work
Click to expand...
Click to collapse
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it
marcussmith2626 said:
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it
Click to expand...
Click to collapse
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing
marcussmith2626 said:
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it
Click to expand...
Click to collapse
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing
abhishekr700 said:
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing
Click to expand...
Click to collapse
why dont you build the rom then flash it and see?
marcussmith2626 said:
why dont you build the rom then flash it and see?
Click to expand...
Click to collapse
what if the phone bootloops or doesn't boot
will i be able to open recovery mode
abhishekr700 said:
what if the phone bootloops or doesn't boot
will i be able to open recovery mode
Click to expand...
Click to collapse
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode
marcussmith2626 said:
why dont you build the rom then flash it and see?
Click to expand...
Click to collapse
what if the phone bootloops or doesn't boot
will i be able to open recovery mode
marcussmith2626 said:
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode
Click to expand...
Click to collapse
i have stock kernel in my rom
i think the recovery mode will open ??
marcussmith2626 said:
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode
Click to expand...
Click to collapse
i have stock kernel in my rom
i think the recovery mode will open ??
abhishekr700 said:
i have stock kernel in my rom
i think the recovery mode will open ??
Click to expand...
Click to collapse
re-read my quote again
are you replacing the kernel? if no then no chance of loosing recovery mode!
Related
Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta
nutmegy said:
Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta
Click to expand...
Click to collapse
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Moon2 said:
You need adb:
-Get this installer: http://developer.android.com/sdk/index.html
-Go to Available Packages, Expand Third Party - Google - select USB Driver
-Update adb driver, if not already installed from: C:\Program Files\Android\android-sdk-windows\google-usb_driver
-Copy "adb.exe" and "AdbWinApi.dll" from "C:\Program Files\Android\android-sdk-windows\platform-tools" to "C:\Windows\System32".
-Run the batch file.
Click to expand...
Click to collapse
thank you very much!
I will give this a go!
Moon2 said:
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Click to expand...
Click to collapse
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?
agarp said:
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?
Click to expand...
Click to collapse
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.
works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!
Moon2 said:
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.
Click to expand...
Click to collapse
thnxx for the clarification, now i get it
nutmegy said:
works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!
Click to expand...
Click to collapse
Is all that done on the phone? It seems you installed the kernel on the phone somehow. I'm clueless about adb, I tried to use it before but was dumbfounded by it all.
Do I need Eclipse? Downloading the SDK stuff...installing JDA SE and it talks about Eclipse.
Moon2 the links dead it says file has been removed anybody re upload it????
I'm sorry to have to open another thread just for this, but I was waiting for zephyr1988 to update his files for aurora 4.1a. As he didn't do it yet, here it is
I had posted these in the other thread, but the files are now outdated and there was some confusion regarding the kernel inside the zip. These files, fix this, because I updated the kernel and services.jar for Aurora 4.1a.
Please, to understand what this does, read this thread:
http://forum.xda-developers.com/showthread.php?t=1710233
Notes:
- This is only for those with Aurora 4.1 + 4.1a update. For other versions, there will be auto-reboots, especially with the gallery, so, if don't have the latest aurora version, don't install this.
To install, flash both zips in recovery. Boot takes a little longer, but believe it, it's worth it
MIRROR
Thanks, fjsferreira! You're incredibly helpful all the time.
I get this error when i try to download.
404 - Not Found
greddyrx7 said:
I get this error when i try to download.
404 - Not Found
Click to expand...
Click to collapse
Yes, I get that too, looks like a problem with xda. Here is an alternate download. Extract the two zip files first
http://www.mediafire.com/?ifhpwtzmtevv1fl
Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?
Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800
sr21 said:
Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?
Click to expand...
Click to collapse
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...
demolition23 said:
Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800
Click to expand...
Click to collapse
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.
fjsferreira said:
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.
Click to expand...
Click to collapse
I tried with 5.5.0.4 and then with 5.8.4.5.
i will redownload and try again..
EDIT
Same again...Will try manually. Thanks anyway!
Priority charger in attached files didn't work but files from Mediafire did.
fjsferreira said:
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...
Click to expand...
Click to collapse
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.
sr21 said:
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.
Click to expand...
Click to collapse
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.
fjsferreira said:
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.
Click to expand...
Click to collapse
Hello fjsferreira,
Thanks for updating the zip, I was away for a week with no access to a PC.
I have updated the original thread with 4.1a OOM priority charger and a init.d zip that does not mess with the boot.img now that dzo has included it in his ROM, so it should be compatible with newer versions.
I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app
bassdrum01 said:
I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
These are scripts that run at boot time to change memory management so that you always have a good amount of memory available. The package also contains some scripts to fine tune screen sensitivity, sdcard and CPU performance, those require editing the script files to uncomment some lines. Read the instructions on the other thread to fine out how to use this.
Sent from my U8800
OK . We all i believe find it chaotic to organize in forums now. So this is a thread just for ideas and problem with cwm or twrp on our device.
All that i have found now is that recovery.img is somehow backed with boot.img. So i have to ask if there is any developer that can look inside this.
Help appreciated. We (developers) have already compiled TWRP and CWM ( me via ubuntu and clockworkmod recovery builder) and none of them is booting.
You might want to look at xperia p boot.img??? Same processor u8500 same screen size. I'm a noob. Just said what I felt. Coming from xperia device where our recoveries are always packed inside boot.img
In ramdisk . /sbin/recovery is where our recovery binary is present.
#pitchblack5691#
thanks for help ! i will definetely looo for it
Might be useful
http://forum.xda-developers.com/showthread.php?t=2020895
http://forum.xda-developers.com/showthread.php?t=1903017
#pitchblack5691#
also coming from xperia forum and for My xperia U and have also novathor u8500 and i have asked dev to explain mothod used in XU for port this method to GIII mini but no reply from him now in XU the recovery are in tar and flashable to phone without odin or another flash only by ADB + run me script in commande window inside recovery tar we have unziped recovery ( icone ....) and some files relative to phone ( fstab ..... )
How is it going? Did everyone stop developing or are you guys just moving in silence trying to figure things out?
Sent thru time and space from my s3mini.
silently moving
Shapeshift said:
silently moving
Click to expand...
Click to collapse
Good to know! Give us a shout if we can help somehow.
currently working on cwm 6. dont know why i cant boot
Perhaps need to no only make recovery but also kernel ?
If this 2 filz run together
Sent from my GT-I8190 using xda app-developers app
From what I understand, You just need to write a piece of code in the ramdisk init files to execute the recovery during boot. No need to modify the kernel.
#pitchblack5691#
If any one is interested i got a dumped ram disk also a got it rebuild-ed,
and yes the recovery scripts are there plus the pngs etc.
I also believe that the device has 2 recovery's, they are the same one just acts as a backup.
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
spawk said:
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
Click to expand...
Click to collapse
They had the internet in 1969?
Take your time. We have root and what roms we have are stable.
Sent from Spaceball One.
Hahaha!
Sent thru time and space from my s3mini.
xd the error is not from me haha i have corect date and time
is new technologie hahahaha retoure backwards in android
and if you see here you can read need new builded kernel to make CWM just read thread 2# and 3# http://forum.xda-developers.com/showthread.php?t=1771347
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
spawk said:
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
Click to expand...
Click to collapse
I sent info about device to that developer. That app is now supporting our golden for full backup incl boot & recovery.img with .zip from here. Only problem is we dont have a working custom recovery to flash that .zip with :/
as Faria wrote above should change the recovery that is in the kernel and the same meter and the same rom in it and in the kernel for which you go just tell me that the two are complementary if a move (size , addition, retirees), the other answers are more about the two is that one feature that the other is that we will say to his control as .
now change I believe that both will adjust in any case theoretically
First I want to say thank you to czechop for his patch and all his work and for telling me wich files to mod to have radio working.
I want to say thank you to fjfalcon and Mioze7Ae too for kernel sources and all their work for our phone.
Currently phone boot on 2ndboot kernel from OpenRecovery with a script.
It boot slow and with some bugs but it boot and ask for pin code and radio is working (I was abble to make a call)
So 2ndboot kernel sources are here : https://github.com/Zachary57/android_kernel/tree/kernel-mod
Kernel image is attached
To use (at your own risk) :
1-Download zip attached
2-Extract 2ndboot.zip to /system (2ndboot.zip is on attached zip so you need to unzip 2 zip) and 2ndboot_system.sh to /sdcard/OpenRecovery/scripts
You should now have /system/2ndboot folder on your phone and 2ndboot.sh in /sdcard/OpenRecovery/scripts
3-Reboot phone holding volume up to boot into OpenRecovery
4-Select run script / 2ndboot_system.sh
It will run script /sdcard/OpenRecovery/scripts/2ndboot.sh that call file in /system/2ndboot
Specifications :
-Kernel OC to 1GHz stock voltage
-SWAP
-Smartass V2 governor
Problems :
-It sometimes fail to boot.
-Sometimes 2ndboot stop to work (you have infinite reboot) so you need to erase files and download them again to make it working
Last post update : 23/02/2013
Now possible load custom core? without pc and after rebooting core works? and what in kern.zip? this is new core or old?
vadims746 said:
Now possible load custom core? without pc and after rebooting core works? and what in kern.zip? this is new core or old?
Click to expand...
Click to collapse
Yes it is possible to load custom kernel without pc. kern.zip contain custom kernel only.
Do you continue working and updating 2nbdoot for best working and what is functional of kern.zip?
vadims746 said:
Do you continue working and updating 2nbdoot for best working and what is functional of kern.zip?
Click to expand...
Click to collapse
For now I am learning kernel developpement but I will try to update this.
In kern.zip all work like with stock kernel. I just applied czechop patch on Mioze7Ae kernel sources and czechop tell me what line was wrong.
I don't know if swap work. I think it is on kernel but I can't make it working for now.
[UPDATE]
Swap not implemented on kernel. I will try to implement it.
How long need wait script installing 2ndboot in OR?
vadims746 said:
How long need wait installing 2ndboot in OR?
Click to expand...
Click to collapse
It doesn't install it just script and files that you copy to sdcard. Then you run script that load 2ndboot kernel. You have to do that on each reboot while we don't put a script that make that automatically at startup.
When you hit 2ndboot.sh in OpenRecovery/run script it take approximately 2minutes to start boot.
where put kern.zip,and where put core with swap support? for example boot3.img.I run script 2ndboot.sh and its install and reboot,but how use 2nbdoot?
vadims746 said:
where put kern.zip,and where put core with swap support? for example boot3.img.I run script 2ndboot.sh and its install and reboot,but how use 2nbdoot?
Click to expand...
Click to collapse
When you run 2ndboot script it run custom kernel that is provided in zip. kern.zip is already on other zip. It is kernel image.
You can't boot boot3.img you can only boot zImage (it is what is kern).
Kern is a zImage it contain custom kernel modded to keep radio working after 2ndboot.
how install kern.zip? and where put him?
Great job done man.
I will look at cm10 for xt720.
i had been working this and very happy you succed in 2ndboot working.
I will switch back to xt720 and try this.
Thanks for your work!!!
Sent from my SGH-T759 using xda premium
vadims746 said:
how install kern.zip?
Click to expand...
Click to collapse
Don't install it. Just extract files from 2ndboot.zip :
Extract 2ndboot to /sdcard and 2ndboot.sh to /sdcard/OpenRecovery/scripts
2ndboot.zip contain all files needed. kern.zip is for developpers that have 2ndboot module.
We can install .zip files,and we need .zip core
vadims746 said:
ok thanks,and how i can now install boot.img?
Click to expand...
Click to collapse
The only way to use boot.img is to use fastboot on each reboot : http://forum.xda-developers.com/showthread.php?t=990735
It suggests that we need .zip core?
vadims746 said:
It suggests that we need .zip core?
Click to expand...
Click to collapse
Yes or to implement missing function in kernel.
Hi
How long does reboot take and do put kernal main storage card ?
Sent from my SGH-T759 using xda premium
mchlbenner said:
Hi
How long does reboot take and do put kernal main storage card ?
Sent from my SGH-T759 using xda premium
Click to expand...
Click to collapse
Kerel reboot take about 2 minutes. It is long but it work everytime (with usb wire disconnected) I tried.
Can you explain more "do put kernal main storage card ?" I didn't understand that part of your sentence.
I use Mioze7Ae 2ndboot files from here : forum.xda-developers.com/attachment.php?attachmentid=1388600&d=1349812889
with zImage I compiled (zImage is kern) and source are available here : https://github.com/Zachary57/android_kernel/tree/kernel-mod
In fact custom kernel is kern (it's a zImage file) and is located in /sdcard/2ndboot.
2ndboot.sh script load it using 2ndboot.
Yes the kernel i downloaded were do i put it.
Also on italy sbf just let you know.
How long does take to load from 2ndreboot script.
Sent from my SGH-T759 using xda premium
mchlbenner said:
Yes the kernel i downloaded were do i put it.
Also on italy sbf just let you know.
Sent from my SGH-T759 using xda premium
Click to expand...
Click to collapse
Just download 2ndboot.zip and extract 2ndboot folder to /sdcard and 2ndboot.sh to /sdcard/OpenRecovery/scripts
Kern.zip is include in 2ndboot.zip it's file kern on /2ndboot
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
mdh-labs said:
I have been playing around with kernels (for nexus 5), to add some features to the stock kernel. But I have problem with Samsung. I am trying to build a flashable custom kernel for Samsung S7 edge (G935F). .Steps I followed to create the boot.img are:
Get the stock source code (Samsung openSource)
Modify the kernel (just add/remove some TCP features)
Build the kernel (as per the kernel READ.ME, with aarch64-linux-android-4.9 toolchain)
-->created Image, with no loadable modules (*.ko)
Unpack the boot.img from the stock kernel (abootimg -x )
Create new boot.img replacing the original zImage with the custom kernel Image (abootimg --create . . . )
Make tar.md5 file of the custom boot.img for Odin3
Pushed the custom kernel using Odin3, but it fails to boot ("kernel not enforcing seadnroid"). I have tried using TWRP (install from zip), but it just does bootloop. Can anyone see what I am doing wrong? Am I missing something? I have read most of the "Build kernel from source" dev-threads but have not found a solution for this, nor am I allowed to post my questions there as I am just a junior member.
I would highly appreciate any help, as I have already invested some days with no avail
Click to expand...
Click to collapse
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
dave7802 said:
I dont want to tell you something you have already read, if you have been through the Dev forums, But on the off chance:
Have you removed the Fingerprint reader?
The Kernel will fail to boot with it enabled, Unless you know the workaround (EchoTeam)
Click to expand...
Click to collapse
Hmm ... Fingerprint reader? No, I have not removed anything. I was thinking that since I am not adding anything that was not already in the stock kernel source, I do not need to do any modifications. How can I remove this reader?
Here are the temporary solutions.
Way A:
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Way B: (If you want to completely disable (or bypass) TEE)
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Replace /system/lib64/hw/gatekeeper.exynos8890.so,/system/lib64/hw/keystore.exynos8890.so with these i uploaded.
Both of them will make your FP Sensor not working.
(Lock Screen will work)
But,at least,you get a stable custom kernel.
Click to expand...
Click to collapse
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
dave7802 said:
http://forum.xda-developers.com/s7-...m-g935f-fd-t3361460/post66762787#post66762787
Thank @Jesse Chan He also fixed the fingerprint too.
Click to expand...
Click to collapse
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
mdh-labs said:
Thanks a lot, I will try that. I have already seen his custom kernel (would love to ask something on his thread but . . . )
Click to expand...
Click to collapse
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Jesse Chan said:
I saw someone mention me.
Well, you must disable all TIMA-related configs as well as KNOX_KAP to get kernel boot.
And then, if you want to get a stable kernel with FP, you must apply my FP fix.(could be found in my Kernel's flashable zip)
Click to expand...
Click to collapse
I appreciate that you have had the time to look at my question. I've tried the tricks you suggested but my kernel still cannot boot. Modified the .config file (with menuconfig):
disabled
# CONFIG_KNOX_KAP is not set
# CONFIG_TIMA is not set
# CONFIG_TIMA_LKMAUTH is not set
not in config anymore
-CONFIG_TIMA_LOG=y
-CONFIG_TIMA_RKP=y
Then built a custom boot.img as mentioned in my question and added the META and mcRegistry folders from your flashable zip file to create a zip file out of the three.
I have also tried by removing the libbauth* files from system/lib/ and system/lib64 directories?
One more thing, does it matter whether I get just an Image file or zImage from kernel build (I get only Image and .gz of it)?