Where are the programmers?...
The programmers are programming
ShaDisNX255 said:
The programmers are programming
Click to expand...
Click to collapse
why is nobody interested in the A10?
rockeirodohs said:
why is nobody interested in the A10?
Click to expand...
Click to collapse
bcuz its a cheap low budget device?
elliwigy said:
bcuz its a cheap low budget device?
Click to expand...
Click to collapse
yea
but it is still a great cell phone
rockeirodohs said:
yea
but it is still a great cell phone
Click to expand...
Click to collapse
if u say so.. its great for its price i guess
Sent from my SM-G977P using Tapatalk
rockeirodohs said:
yea
but it is still a great cell phone
Click to expand...
Click to collapse
Why don't you try learning? That's pretty much how all developers start, wanting to make their phone better.
rockeirodohs said:
Where are the programmers?...
Click to expand...
Click to collapse
Has the 64bit vendor been made yet?
ShaDisNX255 said:
Why don't you try learning? That's pretty much how all developers start, wanting to make their phone better.
Click to expand...
Click to collapse
How can I do it? I am willing to do, or at least start. If you could help me.
mmacedoc7 said:
How can I do it? I am willing to do, or at least start. If you could help me.
Click to expand...
Click to collapse
There are lots of tutorials on XDA, I suggest you start using google + XDA to learn.
Trust me, it's better to ask
"Hey, I'm following this guide and I'm stuck on this step" instead of
"Hey, can you teach me? Can you give me a guide?"
I tried adding the lib64 folder from the galaxy a20's android 9 vendor to my android 10 galaxy a10 vendor and editing all the .prop files in /vendor to support arm64-v8a, but it didn't boot arm64 gsis (black screen after a10 logo for a while, then reboot). Is this because the library files are made for android 9 or do i have to edit the device tree and kernel too? or is there something else in the vendor I'd have to edit?
Pankiefield said:
I tried adding the lib64 folder from the galaxy a20's android 9 vendor to my android 10 galaxy a10 vendor and editing all the .prop files in /vendor to support arm64-v8a, but it didn't boot arm64 gsis (black screen after a10 logo for a while, then reboot). Is this because the library files are made for android 9 or do i have to edit the device tree and kernel too? or is there something else in the vendor I'd have to edit?
Click to expand...
Click to collapse
I think there was also something you needed to do in ramdisk, but I'm not sure.
The only person I've seen who's been successful in porting arm64 libs to another device is @Astrako I don't know if you want to ask him and maybe he can help you out.
ShaDisNX255 said:
I think there was also something you needed to do in ramdisk, but I'm not sure.
The only person I've seen who's been successful in porting arm64 libs to another device is @Astrako I don't know if you want to ask him and maybe he can help you out.
Click to expand...
Click to collapse
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Pankiefield said:
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Click to expand...
Click to collapse
Have you tried using ClassyKitchen? https://forum.xda-developers.com/chef-central/android/tool-classykitchen-android-roms-t3862584
Pankiefield said:
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Click to expand...
Click to collapse
I think ramdisk may already be in the system (system-as-root device).
Check inside system to see if you have something like init.rc and stuff
ShaDisNX255 said:
I think ramdisk may already be in the system (system-as-root device).
Check inside system to see if you have something like init.rc and stuff
Click to expand...
Click to collapse
but when installing a gsi, system partition would be overwritten, it wouldnt make sense to edit it then.
or do you mean system_root?
Pankiefield said:
but when installing a gsi, system partition would be overwritten, it wouldnt make sense to edit it then.
or do you mean system_root?
Click to expand...
Click to collapse
Yes, I mean system_root
ShaDisNX255 said:
Yes, I mean system_root
Click to expand...
Click to collapse
almost finished my vendor, but cant test it, because the vendor partition is too small.
i searched for a way to resize it but no luck
also, i think theres no zygote stuff that needs to be edited, besides zygote type in default.prop, due to the device being a lot newer than the exy 7870 devices
Related
Hey guys
First of all: I'm not good in develop! But i want to start with CM porting to our Gen8
I just get some infos from chulri how to port CM.
What have to be do:
Build-Scripts for CM on Gen8
Extract some Gen8 Binaries
Build the Kernel with Touchscreen Drivers
Build-Scripts for CM on Gen8
I started a Thread at the CM Forum about this I'll report here..
( http://forum.cyanogenmod.com/topic/24048-cm-port-to-archos-gen8/ )
Extract some Gen8 Binaries
I hope chulri will answere me soon so i can do this
Build the Kernel with Touchscreen Drivers
This have to be done from a guy who has Kernel Knowledge! Anyone?
If anyone's interested i could send a link with an how to, i've found onthe web
Everybody is invited to help to getting this Project started!
Greetz,
Lenn
I'm not a great porter, but I've shadowed a lot of porting with the cm roms, I'll try to do my part if you host the project on something like github(both kernel and rom). I also have a little bit of kernel development experience.
Scaryghoul said:
I'm not a great porter, but I've shadowed a lot of porting with the cm roms, I'll try to do my part if you host the project on something like github(both kernel and rom). I also have a little bit of kernel development experience.
Click to expand...
Click to collapse
Thats good You know more than me
I just could host the normal kernel and rom, because i've do nothing yet
(When chulri answered me i'll catch the original binaries, you can read this here: http://forum.xda-developers.com/showthread.php?t=1029507&page=3 )
You think you could the first step i described?
That would be assome
thank you for start the ball rolling!
Lennb said:
Thats good You know more than me
I just could host the normal kernel and rom, because i've do nothing yet
(When chulri answered me i'll catch the original binaries, you can read this here: http://forum.xda-developers.com/showthread.php?t=1029507&page=3 )
You think you could the first step i described?
That would be assome
thank you for start the ball rolling!
Click to expand...
Click to collapse
Not sure what you mean, you want me to explain how to extract the original binaries?
If you need a tester i'm your man ^^
(and if i can be of help with anything else learn me and i'll try ^^)
link should be this?
http://forum.cyanogenmod.com/topic/19647-archos-gen8/page__view__findpost__p__196966
Scaryghoul said:
Not sure what you mean, you want me to explain how to extract the original binaries?
Click to expand...
Click to collapse
First of all, Thanks for a help appear!!
I think he mean the step of porting CM7 to gen8 is:
1.Build-Scripts for CM on Gen8
2.Extract some Gen8 Binaries
3.Build the Kernel with Touchscreen Drivers
so, step 1 should be "1.Build-Scripts for CM on Gen8"..
Scaryghoul said:
Not sure what you mean, you want me to explain how to extract the original binaries?
Click to expand...
Click to collapse
I dont know, when chulri respone me i'll report it here
@eagleofdeath13
Thanks for support! Maybe you could search someone with Kernel knowledge who could do the first step, i think this is hard
@LeoNg628
Yep,sorry about that, thank you for correcting me
Thank goes to all you guys!
LeoNg628 said:
First of all, Thanks for a help appear!!
I think he mean the step of porting CM7 to gen8 is:
1.Build-Scripts for CM on Gen8
2.Extract some Gen8 Binaries
3.Build the Kernel with Touchscreen Drivers
so, step 1 should be "1.Build-Scripts for CM on Gen8"..
Click to expand...
Click to collapse
Yep,you're right
But i think its the hardest step and i've kernel knowledge,
We have to find someone with Kernel Knowledge who could do this
(Except chulri, i always ask him, but he has to much work right now..)
Oh, well I've never really created a build script before but there are plenty of guides instructing on how to do so.
Extracting the binaries usually consists of adb pulling all of the binaries required for the complication that are proprietary/closed source. I suppose you could just copy/paste them to your sdcard then copy to a computer if adb weren't around but that's just extra work.
As to which binaries we need, I'm not sure yet but we can cross that bridge in a bit.
To make the build script, we should probably analyze other build scripts for other devices and the directories for them.
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Also for whoever attempts to get a functional kernel for cm7 this page may be useful(or possibly me just making sure I read this later)
http://wiki.cyanogenmod.com/index.php?title=Howto:_Build_a_Kernel_Port
Scaryghoul said:
Oh, well I've never really created a build script before but there are plenty of guides instructing on how to do so.
Extracting the binaries usually consists of adb pulling all of the binaries required for the complication that are proprietary/closed source. I suppose you could just copy/paste them to your sdcard then copy to a computer if adb weren't around but that's just extra work.
As to which binaries we need, I'm not sure yet but we can cross that bridge in a bit.
To make the build script, we should probably analyze other build scripts for other devices and the directories for them.
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Also for whoever attempts to get a functional kernel for cm7 this page may be useful(or possibly me just making sure I read this later)
http://wiki.cyanogenmod.com/index.php?title=Howto:_Build_a_Kernel_Port
Click to expand...
Click to collapse
Thank you!
Okey, you really knows a lot more than i am
I'll do the binaries, just say me where they are?^^
Maybe you could try the Build script(s)...
And for the Touchscreen Driver:
We've to look for somebody who do the instructions i've found on the net
Scaryghoul said:
This thread might aid in development, I doubt they have the build scripts for archos but they at least have examples in the program I'm sure and other tools to use.
http://forum.xda-developers.com/showthread.php?t=969266
Click to expand...
Click to collapse
Okey, i know this Thread, its great except the fact it don't support Archos ^^
I'll send a message at these guys about archos devices and parallels about our gen8 devices ad supported devices, so we could create our own script to do it from scratch like they've do
But i now i go to bed^^
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
chulri said:
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
Click to expand...
Click to collapse
I have Desire and Desire HD also Aria and Legend....but all is HTC...the hardware spec is not similar to Archos gen8....
chulri said:
To start with build scripts I would recommend to find a device - which is supported by CM, if there even is one - which has similiar hardware as the Archos Gen8 series and start from there instead to start from scratch.
If there is no such similiar device series you unfortunately would have to start from scratch
Click to expand...
Click to collapse
Okey,thank you
there is no device similar to our archos that is supported
But is it possible to "mix" it?
Like:
Cpu - from a phone that has Arm Cortex A8
[...]
we put together all parts
woukd that be possible?
Yes, CPU might be the most important common part, then WiFi/BT, DSP (for hardware acceleration of videos), Sound, Touchscreen and in the end USB host port.
Lennb said:
Okey, i understand thank you very much, chulri!
I've searched but i dont found anything about writing build scripts on android...
Click to expand...
Click to collapse
I haven't found anything too, but I did some research in the beginning of this year: http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
After installing the repository on the build machine, you have all the build scripts from other devices and can copy and adapt them.
Lennb said:
Okey, then we'll do this step (binaries) in the end, i think the best would be to write the build scripts first? What do you mean?
Click to expand...
Click to collapse
Agreed
Lennb said:
i think we should write now on the developement thread, then the other guys could read it
Click to expand...
Click to collapse
Agreed too
chulri said:
Yes, CPU might be the most important common part, then WiFi/BT, DSP (for hardware acceleration of videos), Sound, Touchscreen and in the end USB host port.
Click to expand...
Click to collapse
Okey, but how do we get these firmwares out of the archos firmware?
http://wiki.cyanogenmod.com/index.p...nMod_for_Sholes#Prepare_the_Build_Environment
After installing the repository on the build machine, you have all the build scripts from other devices and can copy and adappt them.
Click to expand...
Click to collapse
Okey, i just have a windows pc, but i think i put linux on it
Ubuntu is the best for developening, isn't it?
I have to talk to my brother (with-owner of the pc)
I'll put a dual-boot system on my pc
I want Cyanogen!
Lennb said:
Okey, but how do we get these firmwares out of the archos firmware?
Click to expand...
Click to collapse
a) adb pull (this is what the "extract_files.sh" does)
b) root the device and copy files one by one
c) root the device, copy the filesystem image and extract the files by script
Lennb said:
Okey, i just have a windows pc, but i think i put linux on it
Ubuntu is the best for developening, isn't it?
I have to talk to my brother (with-owner of the pc)
I'll put a dual-boot system on my pc
Click to expand...
Click to collapse
So you start developing? If not, no need for linux at all
Lennb said:
I want Cyanogen!
Click to expand...
Click to collapse
4 days ago you wanted UrukDroid, 3 day ago you wantet Honeycomb, now you want CM, will you stay this time?
chulri said:
a) adb pull (this is what the "extract_files.sh" does)
b) root the device and copy files one by one
c) root the device, copy the filesystem image and extract the files by script
Click to expand...
Click to collapse
Sorry, im a noob I just don´t understand.
Adb pull is copy files over adb(command connection over usb); right?
So you start developing? If not, no need for linux at all
Click to expand...
Click to collapse
I try I reset my Pc anyway
4 days ago you wanted UrukDroid, 3 day ago you wantet Honeycomb, now you want CM, will you stay this time?
Click to expand...
Click to collapse
Same answer as in 2
from what i understand 2.2, 2.3 doesnt support usb hosting which is needed for the archos screen
is there a fix for that?
i know android 3.0, 3.1 support usb hosting...
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
GOOD LUCK
Click to expand...
Click to collapse
Hmm, if only another developer told you how to cross compile. Oh wait! Haha, congrats Loglud.
Loglud said:
So I have been working on this for a while trying to get things to cross compile, and i got this to compile it is the Source and the program runs on the nook. Next we will have to write our new init.rc to mount our own os. Someone will have to help me with some research, but I just thought you should know.
Here are the files:
2nd-init.tar
To recomile with the NDK use the following command:
Code:
/home/<user>/Downloads/android-ndk-r7/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-gcc --sysroot=/home/<user>/Downloads/android-ndk-r7/platforms/android-14/arch-arm/ 2nd-init.c
(Thanks to Indirect)
GOOD LUCK
Click to expand...
Click to collapse
Awesome! Great job Log. Big Step in the right direction.
Nice. 10char.
So, did development stop on this? how is it installed?
AdamOutler said:
So, did development stop on this? how is it installed?
Click to expand...
Click to collapse
I want know it too... >.<
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Loglud said:
Jeeze idk, i completely forgot about this thread until you guys posted on it. I never did to much testing. This was mostly done in concurrence with the Kexec-Mod since i had the toolchain up and running. If i remember correctly it did generate the second init file, don't know if it ever loaded it, but i can work on it some more if people want. I was hoping some one would point me in the direction they needed me to go with this.
Click to expand...
Click to collapse
I prefer first a compatible Custom Recovery
I compiled, but I don't know how adapt the hijack...
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
http://and-developers.com/2ndinit
AdamOutler said:
what is 2nd-init? Is it a bootloader? kernel? recovery? where does it come in the boot sequence?
http://nookdevs.com/Dump_NookTablet_Partitions
Click to expand...
Click to collapse
Pratically.. it's the method with many motorola phone (with locked bootloader) can run custom roms like cyanogemod.
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Loglud said:
However the problem is it requires kexec mod.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Sorry, but you're wrong.
From this source use the Hijack method. This mean you can instal a custom rom, but you can't replace the kernel or bootloader.
From the source:
It's also important to remember that 2nd-init does NOT unlock the bootloader, nor does it allow you to run a custom kernel. It simply allows us to utilize the kernel that is there for our own means
Click to expand...
Click to collapse
That method is good enough to run CM9 and it's relative simple to port.
The kexec method is something different, but better: is a system call that enables you to load and boot into another kernel from the currently running kernel.
kexec performs the function of the boot loader from within the kernel.... essentially a hijack to allow us to call another kernel as a function of the stock one, allowing us to bypass the locked bootloader.
Source
Someone has had success with this method
See this twitter feed:
http://twitter.com/androidnemith
@AndroidNemith just have seen your photo with the CWM on the Nook tablet. How did you do that since the Bootloader is locked ?
@PetePetePete1 Hijacking . Same way moto defy and others are doing it. Right now i am kicking it manually looking for a better way now.
@AndroidNemith can you show your current state XDA developers, because they are still searching for a method to get a custom bootloader
@PetePetePete1 It's not quite ready and i got distracted by NookColor bits. If you want to see what i am doing look at the Moto Defy CM
Click to expand...
Click to collapse
I take no credit for finding this, as I haven't been talking with @AndroidNemith
HMG10 said:
See this twitter feed:
http://twitter.com/androidnemith
I take no credit for finding this, as I haven't been talking with @AndroidNemith
Click to expand...
Click to collapse
That would be me then I was also asking AndroidNemith if he could show his current state on XDA but he didn´t reply back yet :S Oh yeah and nice picture
http://yfrog.com/nxrztiij
I am trying to modify a aosp compile build in the Android Ktichen but when I get to the step where i have to convert from updater-script to update-script, it gets stuck at "assert". I have allowed it to run for almost an hour now. how do i resolve this issue?
bump for help..
nexxusdev said:
I am trying to modify a aosp compile build in the Android Ktichen but when I get to the step where i have to convert from updater-script to update-script, it gets stuck at "assert". I have allowed it to run for almost an hour now. how do i resolve this issue?
Click to expand...
Click to collapse
use notepad++ to modify updater script
ICS_XD said:
use notepad++ to modify updater script
Click to expand...
Click to collapse
manually convert? thats gonna take long... anyway, is the update binary still needed after converting?
nexxusdev said:
manually convert? thats gonna take long... anyway, is the update binary still needed after converting?
Click to expand...
Click to collapse
yep
Script. It's spelled "script"!!! j/k
Look up the kitchen on here. It does that as one of the features and does it very well. I believe it was called just "kitchen". I may have the name a little off but hopefully this get you going. Also, it's main purpose is building roms, etc, but it does do the feature you need!
Sent from my Super Galaxy'd SPH-D710
HERE you can see "program" I've made to change splash logos on older lg series..
I wanted to change one in LG G4 but my time and resources are limited and could use little help with this updated device...
I know there has been models released since and this phone hasn't got the big buzz about it anymore but I was hoping to get it done with help of some pioneers of the device..
@codeworkx
@genesixxbf3
@BySezerSimsek
Sorry to summon but could use help in pointing me to location of splash and if known the magic bytes explanation.. :good:
No
IGGYVIP said:
HERE you can see "program" I've made to change splash logos on older lg series..
I wanted to change one in LG G4 but my time and resources are limited and could use little help with this updated device...
I know there has been models released since and this phone hasn't got the big buzz about it anymore but I was hoping to get it done with help of some pioneers of the device..
@codeworkx
@genesixxbf3
@BySezerSimsek
Sorry to summon but could use help in pointing me to location of splash and if known the magic bytes explanation.. :good:
Click to expand...
Click to collapse
Take look on:
https://mega.nz/#!U1txhbQS!k4W4Rln2pTBm1QUfTT24MT96s0USCavlzbSsi2LAOjs
It was extracted from H815 kdz.
br
maxx_hr said:
Take look on:
https://mega.nz/#!U1txhbQS!k4W4Rln2pTBm1QUfTT24MT96s0USCavlzbSsi2LAOjs
It was extracted from H815 kdz.
br
Click to expand...
Click to collapse
The m8 . on the go atm but I see in hex its a bunch of core images file?
Where on device does it reside ? I need to get mine out and compare for sake of "magic" and offsets..
Looks like lg standard format but will have to boot PC to see it really.. We should be able to make a change but depends on location really.. This time I think I will try aroma zip to make changes xD
genesixxbf3 said:
No
Click to expand...
Click to collapse
Well that was cold.. But thx for even showing up..
And don't worry.. I'm used to it.. When I've made first post about root of LG L3II had same responses.. Now its all unlocked with custom ROMs...etc..
IGGYVIP said:
Well that was cold.. But thx for even showing up..
And don't worry.. I'm used to it.. When I've made first post about root of LG L3II had same responses.. Now its all unlocked with custom ROMs...etc..
Click to expand...
Click to collapse
This device is already ****. It has an high chance of bootlooping. Doing that will increase the risk
Envoyé de mon iPhone en utilisant Tapatalk
genesixxbf3 said:
This device is already ****. It has an high chance of bootlooping. Doing that will increase the risk
Envoyé de mon iPhone en utilisant Tapatalk
Click to expand...
Click to collapse
Got one few weeks ago n changing ROMs as much as it goes trying to find one I like not a single issue yet... Found the evil thing gets red hot if screen any more than dim during charge and if CPU at max overclock n heavy operation..
In theory changing images that he posted to smaller less complicated ones would work towards saving the device as less code processed on every boot..
I hate the bootloader unlocked notif..
IGGYVIP said:
The m8 . on the go atm but I see in hex its a bunch of core images file?
Where on device does it reside ? I need to get mine out and compare for sake of "magic" and offsets..
Looks like lg standard format but will have to boot PC to see it really.. We should be able to make a change but depends on location really.. This time I think I will try aroma zip to make changes xD
Click to expand...
Click to collapse
You can get your partition from device by:
HTML:
dd if=/dev/block/mmcblk0p45 of=/storage/9016-4EF8/raw_resources
Replace /9016-4EF8/ part with your micro sd's card name.
And on mmcblk0p46 is raw_resourcesbak.
But I doubt that 'bootloader unocked' notification get any relation with boot logo.
BR
maxx_hr said:
You can get your partition from device by:
HTML:
dd if=/dev/block/mmcblk0p45 of=/storage/9016-4EF8/raw_resources
Replace /9016-4EF8/ part with your micro sd's card name.
And on mmcblk0p46 is raw_resourcesbak.
But I doubt that 'bootloader unocked' notification get any relation with boot logo.
BR
Click to expand...
Click to collapse
Great thanks.
By any chance u knowof/remember what kernel/rom changes splash for custom one ?
Having trouble separating the images contained within..
IGGYVIP said:
Great thanks.
By any chance u knowof/remember what kernel/rom changes splash for custom one ?
Having trouble separating the images contained within..
Click to expand...
Click to collapse
If I understand your question:
Never see any changes on bootsplash, with several stock/customs kernel/roms.
Only 'ulocked bootloader' after regular unlocking, but raw_resources don't contain this words.
But on 000800 start order of images with:
lglogo_image; next is:
powered_android_image
quick_lglogo_image
load_charger_image
recovery
backup_restore
etc
maxx_hr said:
If I understand your question:
Never see any changes on bootsplash, with several stock/customs kernel/roms.
Only 'ulocked bootloader' after regular unlocking, but raw_resources don't contain this words.
But on 000800 start order of images with:
lglogo_image; next is:
powered_android_image
quick_lglogo_image
load_charger_image
recovery
backup_restore
etc
Click to expand...
Click to collapse
Hmm might need to dig into dev tree of this thing to find out where does it call the text about bootloader from..
As for the logo partition it seems some new modified lg version of rle packing
Basically its a multi rle(maybe tiff rle now that I think about it...) partition with padding. pulled from device comes out at 4mb
Yes we can see there is few images there and in this order but where does one start and finish and another start n finish etc is still mystery.. thought maybe bytes after the iamge name are pointing to offsets but don't seem to be able to make sense of it
@IGGYVIP
Hey. Don't know if you're still looking into this, but thanks anyway.
I guess it's more of a luxury than a need, but it would be nice to remove that unlocked warning. I would certainly donate if you succeeded.
I assume this would apply to all LG models.
Perhaps we could start a bounty. Though I don't have G4 but V20 and V10.
Hi i am Building a Android Oreo custom rom for my Samsung galaxy J7 (SM-J700F).I need help about binaries.Please tell me in detail how can i extract binaries?And please explain furthe process to build custom rom successfully.:fingers-crossed:
Go to this thread for the "how to build" part.
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
But he didn't explained ho to extract proprietary binaries
Abdullah786$ultan said:
But he didn't explained ho to extract proprietary binaries
Click to expand...
Click to collapse
Lineage has a script for that on every device repo. You have to be on stock. I don't know if your device is supported though.
Manually you can always copy the blobs on system/vendor/lib and system/lib .
darjwx said:
Lineage has a script for that on every device repo. You have to be on stock. I don't know if your device is supported though.
Manually you can always copy the blobs on system/vendor/lib and system/lib .
Click to expand...
Click to collapse
From where i can find binaries for my phone???
Abdullah786$ultan said:
From where i can find binaries for my phone???
Click to expand...
Click to collapse
1. Maybe someone has uploaded them to the internet. This is not weird, is usual to find system dumps out there.
2. Extracting them from your stock ROM (while having it installed).