Related
Hey guys. I'm posting this message here because it doesn't seem like there are many experienced devs in the LG Optimus S section over at AndroidCentral (only place with a LG Optimus S forum).
So there are only really two ROMs for the LG Optimus S currently, and myself being a dev, thinks that there should be more. So I took on the task of creating an AOSP ROM for the community. I *think* I have it compiled correctly, and I *think* I have the boot.img packed correctly. The only part I'm stuck at is actually flashing the ROM to my phone... my update-script has an error. While flashing the ROM, I get this message:
Copying files...
E:Can't symlink /system/bin/cat
E:Failure at line 9:
symlink toolbox SYSTEM:bin/cat
Installation aborted.
_________________________________
I've looked at line 9 in the script, and I can't seem to find anything wrong with it, but keep in mind it IS my first time developing a ROM from complete scratch.
If anyone can help me out here, I'd be insanely grateful to you!
Thanks for you time,
mrinehart93
My ROM: http://www.4shared.com/file/3YaJvdFU/LGOptS-AOSP.html
Hi everyone,
I have been trying for quite a while now to compile HID Gadget support for my galaxy S3 and think i may be getting close. My current problem is that when i run insmod g_hid.ko i receive the following
Code:
insmod: init_module 'g_hid.ko' failed (Device or resource busy)
. The weird thing is that next time the screen turns off or if i attempt to insert it again the phone crashes (kernel panic i assume). I get this same error when i try and insmod g_zero.ko (although this one doesn't kill the phone). Can anyone tell me how i would attempt to debug this? Or even better, has anyone got g_hid working on there phone and if so, what modifications/kernel configs did you use?
Also, when compiling the kernel, in "USB gadget support" if i select any option other than Android Gadget in USB Gadget Drivers my kernel fails to build. Has anyone got any USB gadgets to compile and run and if so what procedure/modifications did you have to make. Currently i am compiling my kernel with android gadget selected as the usb gadget driver and then changing it to HID module and running make module_prepair and make module to get my .ko files (which may be why i am getting the above error).
If anyone can provide some insite and advice it would be greatly appreciated.
Thank you
Adrian
After months of trying, it appears i have got it solved. Unfortunately its not the most graceful solution and currently it disables MTP but i dont care. To fix it i searched every file in the kernel for mentions of CONFIG_USB_G_ANDROID and everywhere it was involved in an #if defined statement i added another section like so
Code:
#if defined(CONFIG_USB_ANDROID) || defined(CONFIG_USB_G_ANDROID) || defined(CONFIG_USB_S3C_OTGD)
In this case i added USB_S3C_OTG. As i said, it isn't pretty but it works.
Hope this helps someone in the future coz there is very little info on the net about this
Enjoy
Adrian
Code sample
I asked a question on Stack Overflow about exactly this issue. There is a small group of people who seem quite interested in this issue, and there really is not a lot of information on the net.
I would very much appreciate if you could explain in a little more detail what steps you took to get this to work for you. You could probably answer the Stack Overflow question more decisively than the current answers too: stack-overflow questions/9805731 - is-it-possible-to-program-android-to-act-as-physical-usb-keyboard. (I can't post the link as this forum blocks it.)
darcpyro said:
After months of trying, it appears i have got it solved. Unfortunately its not the most graceful solution and currently it disables MTP but i dont care. To fix it i searched every file in the kernel for mentions of CONFIG_USB_G_ANDROID and everywhere it was involved in an #if defined statement i added another section like so
Code:
#if defined(CONFIG_USB_ANDROID) || defined(CONFIG_USB_G_ANDROID) || defined(CONFIG_USB_S3C_OTGD)
In this case i added USB_S3C_OTG. As i said, it isn't pretty but it works.
Hope this helps someone in the future coz there is very little info on the net about this
Enjoy
Adrian
Click to expand...
Click to collapse
No worries, im happy to help. The funny thing is by reading the answers you got it started me on the right path to finding a solution. Im not sure how this will translate to other devices firmware but in the case of the galaxy S3 it was i went threw every file and added the
Code:
|| defined(CONFIG_USB_S3C_OTGD)
to all if defined statement that made any mention of CONFIG_USB_GADGET so that the code inside would be compiled. This was so that in the .config file for the kernel CONFIG_USB_GADGET would be set to yes and would then allow the hid driver to be compiled. Basically every time i got an error i saying something wasn't compiled or wasn't declared i went to that file, found where it was declared and added that if defined statement. I would upload my working source code but it would take weeks on my internet connection. If there is a specific file you want to see then let me know and i will post its contents.
Good luck
Adrian
darcpyro said:
No worries, im happy to help. The funny thing is by reading the answers you got it started me on the right path to finding a solution. Im not sure how this will translate to other devices firmware but in the case of the galaxy S3 it was i went threw every file and added the
Code:
|| defined(CONFIG_USB_S3C_OTGD)
to all if defined statement that made any mention of CONFIG_USB_GADGET so that the code inside would be compiled. This was so that in the .config file for the kernel CONFIG_USB_GADGET would be set to yes and would then allow the hid driver to be compiled. Basically every time i got an error i saying something wasn't compiled or wasn't declared i went to that file, found where it was declared and added that if defined statement. I would upload my working source code but it would take weeks on my internet connection. If there is a specific file you want to see then let me know and i will post its contents.
Good luck
Adrian
Click to expand...
Click to collapse
Hi Adrian
did you manage to use your android phone as a keyboard with USB_H_HID module ? I'm trying to do the same thing and I would be interested if you have more informations. For now, I had cyanogendmod source for Samsung Galaxy S III and I've compiled the default 10.1 ROM.
Yesterday, I tried to modify kernel options to include USB_H_HID in the kernel but the build fails on some android.c error.
See you
--
Thus0
Hi Thus0
I did manage to get it to work late last year (Just so you know that it can be done).From memory i basically ran grep over every file in the modules directory looking for CONFIG_USB_GADGET and then edited those files to say something like:
#if defined(CONFIG_USB_ANDROID) || defined(CONFIG_USB_G_ANDROID) || defined(CONFIG_USB_S3C_OTGD)
This way it would compile the USB Gadget modules as well. Let em know if you have any more questions and ill try and help.
Adrian
Huh – is it possible to make apk file for root devices?
Shir_man said:
Huh – is it possible to make apk file for root devices?
Click to expand...
Click to collapse
No sorry, as far as i know a custom kernal is compiled
darcpyro said:
No sorry, as far as i know a custom kernal is compiled
Click to expand...
Click to collapse
Is it possible to only use a driver and to load it with insmod in a stock rom? What modification require a custom kernel?
i was looking for a solution and ou,d something for the nexus 7
https://play.google.com/store/apps/details?id=remote.hid.keyboard.client
open xource here with kernel patch
https://www.google.com/url?q=https:...t&sa=D&usg=AFQjCNGztTd4-U4gHvd4DLzdg_qBxLb7gw
maybe someone can use it
syserr presents...
"SE" ROMs for the A2107A-F and A2107A-H
Stock ROMs flashable with SP Flash Tool
-------------------------------------------------------------
SE_A2107A-F_S486_130221_SP.7z (updated Oct 5, 2013)
Complete, all partition blocks you need and then some
Partition block images from freshly opened -F, made with SPFT read mem then chunked with dd
No Root
NVRAM partition for those that have clobbered it and don't have a backup
^ yes, I know I just gave away my MAC address, but I doubt we are neighbors
Android 4.0.3
SE_A2107A-H_A404_121011_ATT_SP.7z (updated Oct 8, 2013)
Note: This is for the 1 SIM version, I don't guarantee it will work on 2 SIM hw.
Complete, all partition blocks you need and then some
Partition block images from a barely used -H, made with SPFT read mem then chunked with dd
I had rooted it before, so I carefully removed Superuser, su, busybox, busbox symlinks, and RootExplorer.
NVRAM partition for those that have clobbered it and don't have a backup, but I've blanked the MEID... so you'd have to restore your own with MKDRT or similar tool.
Android 4.0.4
SE_A2107A-H_VOD_SP.7z (updated May 15, 2014)
Note: This is for the 1 SIM version, I don't guarantee it will work on 2 SIM hw.
Complete, all partition blocks you need and then some
Partition block images from a Vodafone -H, made with SPFT read mem then chunked with dd
Rooted.
NVRAM partition for those that have clobbered it and don't have a backup, but I've blanked the MEID... so you'd have to restore your own with MKDRT or similar tool.
Android 4.0.4
A2107A-F ROMs flashable with CWM Recovery
------------------------------------------------------------
SE_STOCK_A2107A-F_S486_130221-signed.zip (updated Oct 5, 2013)
FAC partition is recreated with a lighter weight mechanism to choose country.
Origins were the above "-F" SPFT dump
No Root, Trying to be stock!
SE_SRS_A2107A-F_S486_130221-signed.zip (updated Oct 7, 2013)
SRS = Stock Rooted Scrubbed
FAC partition is recreated with a lighter weight mechanism to choose country.
Rooted with SuperSU Rooted with chainsdd Superuser
Busybox
All the vendor bloatware removed
Splash animations and annoying load audio removed
A2107A-H ROMs flashable with CWM Recovery
------------------------------------------------------------
SE_STOCK_A2107A-H_ATT_A404-signed.zip (updated Oct 8, 2013)
Note: Only use this on Dual-SIM if you are an experimenter with a full backup of NVRAM partition
Origins were the above "-H" SPFT dump
No Root, Trying to be stock!
Android 4.0.4
From US/AT&T model with 1 SIM slot
This appears much snappier than my -F with 4.0.3 firmware
SE_SRS_A2107A-H_ATT_A404-signed.zip (updated Oct 8, 2013)
Note: Only use this on Dual-SIM if you are an experimenter with a full backup of NVRAM partition
Like SE_STOCK*, but rooted with chainsdd and busybox installed.
Removed boot and shutdown animations
Really there isn't much bloatware to begin with.
Android 4.0.4
SE_FOXTROT_REROOTED-signed.zip (updated Nov 11, 2013) NEW!
I started with FoxtrotKZ's ROM
I found that "su" didn't work and the Busybox install said there was a problem opening a shell with root access.
I re-rooted it. (it works now)
I re-installed busybox. (it works now)
USB Debugging / ADB is enabled right away - adb logcat works first boot.
I removed boot animation/audio and shutdown.
I resisted the urge to remove more, but my objective was just to rework it as a test ROM for myself.
Tree of Tools for the A2107A
------------------------------------------------------------
in my A2107A directory
I'm going to make this second post contain...
---------------------------------
MISC ROM Tweaks
---------------------------------
ClearSky_Overlay_BigData_For_4GB.7z
Overlay files for A2107A-H with 4GB.
Increases standard 1.35GB /data to 2.01GB
Copy these files over your SPFT ROM directory
Tested with ClearSky SPFT ROM, but other 4GB SPFT should work
Custom Scatters
Scatter_And_XBRs_16GB_-_SYSTEM_1.5G_CACHE_.5G_DATA_2.0G.7z
Looking good thanks
Sent from my C6603 using XDA Premium 4 mobile app
F user here, looking forward to flashing this and playing around with it tomorrow. Just wanted to say thanks!
Fine, I bought it for € 99.- in germany last week. In the moment I have the foxtrot rom with phone function on it. Do you plan a 4.04. rooted zip rom for recovery, also ?
Nice rom but dual sim version do not see any sim card.
good :good:
xclaw said:
F user here, looking forward to flashing this and playing around with it tomorrow. Just wanted to say thanks!
Click to expand...
Click to collapse
Your welcome. I found a little oddness with the root, I just switched back from chainfire SuperSU to chainsdd Superuser. I'll get the new SRS uploaded today. (UPDATE: new one is uploaded a few hours ago)
NEO130 said:
Fine, I bought it for € 99.- in germany last week. In the moment I have the foxtrot rom with phone function on it. Do you plan a 4.04. rooted zip rom for recovery, also ?
Click to expand...
Click to collapse
For -H, I will be releasing a rooted one probably tonight. Bare in mind though, this is from a single SIM model. I wouldn't mind purchasing a dual SIM so I had all variants to test on.
I could release an updater that would allow you to reinstall the recovery to CWM5 or CWM6.
nefilim23 said:
Nice rom but dual sim version do not see any sim card.
Click to expand...
Click to collapse
Thanks. Hum, I wonder what is going on. My single SIM -H works "ok" with the dual SIM -H ROMs. I can see MEID etc.. it just shows the second SIM as MEID 000000 or unknown.
It'd be nice to get my hands on a couple of the SPFT dumps of stock roms for -H variants. Or purchase a dual -H tablets even.
That would be great if You could make it work on dual sim. Rom is faster and more responsive than 4.03.
In dual sim all the sim options are inactive and there is no cell networks.
nefilim23 said:
That would be great if You could make it work on dual sim. Rom is faster and more responsive than 4.03.
In dual sim all the sim options are inactive and there is no cell networks.
Click to expand...
Click to collapse
Thanks for the confirmation on it 4.0.4 being snappier, very good to know. Apparently AT&T was able to have Lenovo develop longer than they would have normally and got 4.0.4 stock.
In general to all readers....
So here is what I've found:
The LeWa ROM claims to be 4.0.4 also. It is the only -H ROM I've seen out of about 10 I've archived that claims this, besides my AT&T ROM.
The LeWa ROM may have originated from the Lenovo A750 phone... as that shows as it's build:
ro.product.device=lenovo75_ics
A few reason that the AT&T ROM might serve as a better base for custom work:
1. It's for the hardware, no doubt. Need to figure out tweaks needed for 2 SIMS
2. It apparently uses a newer MTK frameworks: ro.mediatek.version.release=ALPS.ICS.MP.V2 instead of V1
LeWa is much slower than Your rom. I am on foxtrot now that seems little faster than LeWa.
thanks for your sharing
but please , I want to know one thing before flashing this rom to my Lenovo A2107A-H with Duel SIM ,
Is this rom will change my original wireless address and my IMEI for the Duel SIM , I mean is this rom will change the original nvram folder , or it will keep it as it is .
And please for the stock roms without root , I found that the link to A2107A-F is the same as A2107A-H , it means that there is no right link to A2107A-H
I hope that I get an answer from you before I make any crazy modification .
Thanks again and have a nice day
sam_pon said:
thanks for your sharing
but please , I want to know one thing before flashing this rom to my Lenovo A2107A-H with Duel SIM ,
Is this rom will change my original wireless address and my IMEI for the Duel SIM , I mean is this rom will change the original nvram folder , or it will keep it as it is .
And please for the stock roms without root , I found that the link to A2107A-F is the same as A2107A-H , it means that there is no right link to A2107A-H
I hope that I get an answer from you before I make any crazy modification .
Thanks again and have a nice day
Click to expand...
Click to collapse
Oops on the mixup of links. I'll fix, sorry.
It shouldn't change anything in the nvram. NVRAM is somehow magically mounted, it's actually it's own filesystem in a partition block on the flash. So when my -H ROM installs it -- it ONLY writes to the BOOT and SYSTEM/ANDROID partition blocks -- no others. If I were you, I'd still have a backup of your NVRAM directory or partition block (.img).
About root vs no root, I think you noticed I removed the root files from the -H image -- it should be truly stock now. I'm pretty sure I was careful enough that no one would ever notice it was ever rooted.
syserr said:
Oops on the mixup of links. I'll fix, sorry.
It shouldn't change anything in the nvram. NVRAM is somehow magically mounted, it's actually it's own filesystem in a partition block on the flash. So when my -H ROM installs it -- it ONLY writes to the BOOT and SYSTEM/ANDROID partition blocks -- no others. If I were you, I'd still have a backup of your NVRAM directory or partition block (.img).
About root vs no root, I think you noticed I removed the root files from the -H image -- it should be truly stock now. I'm pretty sure I was careful enough that no one would ever notice it was ever rooted.
Click to expand...
Click to collapse
Thanks for answering my question , you know : my problem is that i sent my tablet to changing the whole motherboard for only that NVRAM , So , if you are sure that it will not be touch , i will try the rom , because i realy liked this rom even before i test it ,
and one other thing : you told me that to keep partition block (.img) , what is that partition , and is that mean that there is a way to fix nvram fixed fix or you mean that this fix will be a temperory fix .
please excuse my english because i am egyption , and forgive me for all this questions , but i want to understand every thing before taking my decision .
sam_pon said:
Thanks for answering my question , you know : my problem is that i sent my tablet to changing the whole motherboard for only that NVRAM , So , if you are sure that it will not be touch , i will try the rom , because i realy liked this rom even before i test it ,
and one other thing : you told me that to keep partition block (.img) , what is that partition , and is that mean that there is a way to fix nvram fixed fix or you mean that this fix will be a temperory fix .
please excuse my english because i am egyption , and forgive me for all this questions , but i want to understand every thing before taking my decision .
Click to expand...
Click to collapse
Your English is certainly good enough.
What I meant: Your /data/nvram is really just it's own file system on a partition block on flash. You can copy the files form /data/nvram, but also you can make an image backup of the partition block of flash. Either way should work fine, the partition block image is a bit more "absolute" and it could be restored easily with SP Flash Tool.
Flashing this rom do not change mac, imei etc. WiFi works fine but still no 3g for dual sim
Can You add more languages to this rom? I would like to have polish language and working 3g .
Thanks for Your work. Rom is great and it is good to see this device have chance for better software.
syserr said:
Your English is certainly good enough.
What I meant: Your /data/nvram is really just it's own file system on a partition block on flash. You can copy the files form /data/nvram, but also you can make an image backup of the partition block of flash. Either way should work fine, the partition block image is a bit more "absolute" and it could be restored easily with SP Flash Tool.
Click to expand...
Click to collapse
Really , many many thanks for you , i got your point now about taking a copy of my NVRAM folder for safety Purpose only , but final question : could you please tell me how to make an image backup of this partition to be flashed later by SP flash tool .
i know that my questions too much , but i believe that you are the best one to answer me.
nefilim23 said:
Flashing this rom do not change mac, imei etc. WiFi works fine but still no 3g for dual sim
Can You add more languages to this rom? I would like to have polish language and working 3g .
Thanks for Your work. Rom is great and it is good to see this device have chance for better software.
Click to expand...
Click to collapse
thanks for telling us about your try , and many thanks to make me sure that nothing will change .
Last night I wasn't successful at much.
I tried throwing FM on the AT&T ROM... App and drivers. Didn't work.
Then I tried putting the AT&T ROM on the -F but with boot.img tweaks so it would find the system partition. Didn't work.
I guess I need to scale back a little to have some success.
Sent from my XT912 using xda app-developers app
Hello there are rom custom for my sm-g350 pls ?
Izuna30 said:
Hello there are rom custom for my sm-g350 pls ?
Click to expand...
Click to collapse
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
ngoralph said:
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
Click to expand...
Click to collapse
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
frost245 said:
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
afaik it was moved as i have reported it
Gotta get this working!
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
AlexInHell said:
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
Click to expand...
Click to collapse
As far as I know, the lock shows, that you don't have the write permission on this file
Sent from my SM-G350 using XDA-Developers mobile app
Hello dear people,
I've managed to compile a Kernel for the A515F - using the source code provided by samsung (https://opensource.samsung.com/uploadSearch?searchValue=A515F) - Version A515FXXU3BTF4.
The usage of make (...) yielded an Image (no extension) and a Image.gz file under the path "arch/arm64/boot/" within the sourcecode.
The size of the Image is 30,3mb - the Image.tz size is 10,3 mb - looks good so far doesnt it?
SInce my last kernel-development work is from 5 years ago and a lot of things changed during that time - what are the next steps in order to install this kernel on the device?
I can remember somethings, like using adb / fastboot to flash the related partitions, etc. - im going to get my head around this, but maybe someone could give me some hints ?
Ive also have some other questions:
- Flashing a custom kernel on this device trips the knox status - ive read that this disable secure folders and samsung pay - so no software that im interested in - are there any othere drawbacks of installing cfw ?
- I've read alot of A/B partitions - Ive used an android app which logs some hardware-specific information about the device and as it looks - the A51 uses A/B partitions - what does that mean and how does it differ to smartphones 5 years ago?
- From other kernel-development-work (on x64 / x86 hosts) I know that the modules of a kernel should be a part of the resulting Image / Image.gz file - is this also the case in this scenario? Are drivers / and related modules part of the kernel?
- Is it possible to test this kernel on an android emulator? I dont want to flash something somehow on a device wihtout being sure that it doesnt result in a bricked device.
Thanks in advance!
theWicket said:
Hello dear people,
I've managed to compile a Kernel for the A515F - using the source code provided by samsung (https://opensource.samsung.com/uploadSearch?searchValue=A515F) - Version A515FXXU3BTF4.
The usage of make (...) yielded an Image (no extension) and a Image.gz file under the path "arch/arm64/boot/" within the sourcecode.
The size of the Image is 30,3mb - the Image.tz size is 10,3 mb - looks good so far doesnt it?
SInce my last kernel-development work is from 5 years ago and a lot of things changed during that time - what are the next steps in order to install this kernel on the device?
I can remember somethings, like using adb / fastboot to flash the related partitions, etc. - im going to get my head around this, but maybe someone could give me some hints ?
Ive also have some other questions:
- Flashing a custom kernel on this device trips the knox status - ive read that this disable secure folders and samsung pay - so no software that im interested in - are there any othere drawbacks of installing cfw ?
- I've read alot of A/B partitions - Ive used an android app which logs some hardware-specific information about the device and as it looks - the A51 uses A/B partitions - what does that mean and how does it differ to smartphones 5 years ago?
- From other kernel-development-work (on x64 / x86 hosts) I know that the modules of a kernel should be a part of the resulting Image / Image.gz file - is this also the case in this scenario? Are drivers / and related modules part of the kernel?
- Is it possible to test this kernel on an android emulator? I dont want to flash something somehow on a device wihtout being sure that it doesnt result in a bricked device.
Thanks in advance!
Click to expand...
Click to collapse
First of all, dang that's a lot of questions at once.??
Also you might've already figured out the answers to all of em but still here are all the Answers in case you didn't or for someone else seeing this post.
Q1) For installing the kernel on the device, one option is to flash the boot image using twrp while the other is to compress to boot.img.tar and flash in the AP section of odin.
Q2) The only drawback is tripping knox which makes some samsung apps like samaung pay, samsung pass, secure folder etc to not work on your device EVER. I repeat they won't work on your device ever because tripping knox is an irreversible thing.
Q3) Yes samsung A51 uses A/B partition structures which just means that it has 2 copies of some partitions like system and vendor, for example. For more details google should be able to explain it to you better than me. Aka A-only vs A/B partitions.
Q4&5) I'm sorry but I don't know about that ? but in case you are looking for tests you can ask in A51 telegram group.