Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
me too
Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.
sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it
Related
i have pushed the board files to my github to compile a fully working kernel for the GSM Hero. i dont own the device, but Behnaam has been working with me testing and such. anyhow everything works. the link to my source can be found below:
GoDmOdE-KeRnEl-SoUrCe
anyhow enjoy i do this for the community and ask for nothing but in return. Devs have at it!!!
Behnaam already beat you to the punch, link.
gu1dry said:
Behnaam already beat you to the punch, link.
Click to expand...
Click to collapse
i seen but i can update this one plus i guess i forgot to add two files . btw they are there now and it will compile for sure. (i just did it) enjoy
will it say no more huge battery drain ?
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
EDIT: Had a lapse and forgot to compile a new wlan module... will reupload after school today
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
zjr8 said:
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
Click to expand...
Click to collapse
Here ya go mate
http://www.megaupload.com/?d=724NZ7Q1
Are the video drivers included?
MerXury13 said:
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Click to expand...
Click to collapse
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
It's too early for me^^ sorry
dipje said:
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
Again... getting boring
Can someone please compile this one with overclock patch?I have no idea how to compile from source else I would do it
l0st.prophet said:
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
Click to expand...
Click to collapse
Hence it got video drivers
Can anyone point me in the direction of a good write up on how to build a boot.img from this git repo please?im using ubuntu 10.4
so can we use this kernel on the vanilla roms?
anon2122 said:
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Click to expand...
Click to collapse
Do you have the latest commit? I believe initially there were some missing files. I know when I grabbed the source the first time i had wlan drive compile issues
I applied this to both cronos rom and to superhero rom and both got really sluggish after installing it (I used the boot.img posted among the first posts).
Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!
I'll take this...
and this...
One more...
Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium
Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium
Awesome!! tyvm!!
Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.
all u need now is a video tutorial
My man!!! Thank you for this!!
Sent from this phone
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.
You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.
Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App
Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium
Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App
Great Guide!
Very informative and well put, Thank You.
thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!
Hi everyone. I am attempting to buld my first ROM and am following a guide to build beanstalk. I am at a point that confuses me. The comand is "breakfast (Device name)". Is this just looking for "n7100" or is there a speacial name I have to put there? Thanks!!
PS: Before anyone say this is not the place for this, Id like to say sorry first. IF i can get this to work and I get permision from scott this will turn into a new Beanstalk build thread.
It depends on the Beanstalk build environment setup. Your best bet is to PM someone that has already built for a device and ask them.
Just something to try, you could try the breakfast command without typing anything after it and see if your device name shows up then.
When I started building from source, I have never used the breakfast command, only lunch and make.
Thanks for the reply. I am running into another problem thats a step before that. I am trying to get the curl command to work. It creates a file called repo but when I try to do the next command repo init "blahblah" I get an error code saying syntay error Doctype HTML. The only thing I can think of is that the repo file should be a python script but is getting saved as html. I dont know how to fix this. Can someone post there repo file. This is the code to I am using to create the repo file.
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Bert.C said:
It depends on the Beanstalk build environment setup. Your best bet is to PM someone that has already built for a device and ask them.
Just something to try, you could try the breakfast command without typing anything after it and see if your device name shows up then.
When I started building from source, I have never used the breakfast command, only lunch and make.
Click to expand...
Click to collapse
Goneeuro said:
Thanks for the reply. I am running into another problem thats a step before that. I am trying to get the curl command to work. It creates a file called repo but when I try to do the next command repo init "blahblah" I get an error code saying syntay error Doctype HTML. The only thing I can think of is that the repo file should be a python script but is getting saved as html. I dont know how to fix this. Can someone post there repo file. This is the code to I am using to create the repo file.
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Click to expand...
Click to collapse
Have you got that big list of dependencies installed? If you dont know what I mean, search for aosp amd setting up build environment and theres a list of packages that need imstalling, python beimg one of them.
Actually looking at that link I dont think thats where my repo come from. If you can wait until tomorrow when Im back at my pc Ill sort out a step by step guide if you want? As in noob starting from scratch guide that I followed to get set up.
Sent from my GT-N7100 using Tapatalk
Bert.C said:
Have you got that big list of dependencies installed? If you dont know what I mean, search for aosp amd setting up build environment and theres a list of packages that need imstalling, python beimg one of them.
Actually looking at that link I dont think thats where my repo come from. If you can wait until tomorrow when Im back at my pc Ill sort out a step by step guide if you want? As in noob starting from scratch guide that I followed to get set up.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yeah. I had a wrong link in the curl command. It was an old link. I googled it and replaced it, now everything seems to be working. Lets see though. Any help you can give though I would apreciate it.
Goneeuro said:
Yeah. I had a wrong link in the curl command. It was an old link. I googled it and replaced it, now everything seems to be working. Lets see though. Any help you can give though I would apreciate it.
Click to expand...
Click to collapse
What steps have you already taken mate? Start from the very beginning if you can and we shall get you up and running in no time at all (unless you already are?)
Hi. I got it syncing now. Thanks. The next command I'm not to sure of is the breakfast command.
Sent from my GT-N7100 using xda app-developers app
Goneeuro said:
Hi. I got it syncing now. Thanks. The next command I'm not to sure of is the breakfast command.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Did you add your N7100 repo's to the local manifest?
Bert.C said:
Did you add your N7100 repo's to the local manifest?
Click to expand...
Click to collapse
Can I message you on hangouts?
Bert.C said:
Did you add your N7100 repo's to the local manifest?
Click to expand...
Click to collapse
Sent PM. :good:
Ok. Next question. Where or how do I get the device specific files for the note 2 so I can try to build the newest beanstalk. I thought they would automatically come from CM but the device isnt supported. Not sure if I mentioned this or not before but I have never done this before so it is a learning experience for me.
Ok guys I've made some tweaks to the Mms.apk,
1) Auto SMS to MMS conversion disabled.
2) Ulimited lines for text typing area.
3) Fixed issues with delivery reports.
4) Minor tweaks.
Next build:
1) MMS fix (First I need confirmation of it's not working from at least two people)
2) Dark them.
3) You say.
Link:
http://www.mediafire.com/download/4h47r4k45ekzeu4/Mms.apk
Instructions:-
Download the Mms.apk file and copy it to your fastboot folder. Open command prompt and enter the following commands:-
Code:
adb remount
adb push Mms.apk /system/app/
adb shell
chmod 644 /system/app/Mms.apk
exit
adb reboot
Make sure to press enter after each command. Also, make a backup of your original Mms.apk in case you experience any problems.
Press thanks to keep me motivated and provide further updates.
Hi,
File deleted?
Invalid or Deleted File.
The key you provided for file access was invalid. This is usually caused because the file is no longer stored on MediaFire. This occurs when the file is removed by the originating user or MediaFire.
Still have questions, or think we've made a mistake? Please contact support for further assistance.
Click to expand...
Click to collapse
unster said:
Hi,
File deleted?
Click to expand...
Click to collapse
Was going to DL this to add to the rom, can you send me a copy of your latest @MScorporation95 ?
unster said:
Hi,
File deleted?
Click to expand...
Click to collapse
mcgi5sr2 said:
Was going to DL this to add to the rom, can you send me a copy of your latest @MScorporation95 ?
Click to expand...
Click to collapse
Sorry for the problem guys. Link fixed.
I need some cool ideas for my next build. Suggestions are appreciated.
MScorporation95 said:
Sorry for the problem guys. Link fixed.
I need some cool ideas for my next build. Suggestions are appreciated.
Click to expand...
Click to collapse
How about helping to build EV3.2 and then CM10.1?
mcgi5sr2 said:
How about helping to build EV3.2 and then CM10.1?
Click to expand...
Click to collapse
Yeah sure.. When we're starting?
MScorporation95 said:
Yeah sure.. When we're starting?
Click to expand...
Click to collapse
I'm uploading the the latest CM10 with your mms.apk in it now. I will clean my github and then sync in the device/vendor/msm7x30 trees that I have so far for them. The latest build I have done have two main issues, firstly the kernel isn't building properly, it comes out around 4kbs too small, and won't boot very far. Using a downloaded version of hellboy the rom boots past the htc screen onto a black, with the latest version we should be able to pull a logcat to see more closely what we need to fix.
Once I have it all uploaded I'll start a new thread and add any and all stuff I know so far, so that anyone can pitch in if they feel like it. I think we should make it a rookie friendly as possible so that anyone here can contribute.
mcgi5sr2 said:
I'm uploading the the latest CM10 with your mms.apk in it now. I will clean my github and then sync in the device/vendor/msm7x30 trees that I have so far for them. The latest build I have done have two main issues, firstly the kernel isn't building properly, it comes out around 4kbs too small, and won't boot very far. Using a downloaded version of hellboy the rom boots past the htc screen onto a black, with the latest version we should be able to pull a logcat to see more closely what we need to fix.
Once I have it all uploaded I'll start a new thread and add any and all stuff I know so far, so that anyone can pitch in if they feel like it. I think we should make it a rookie friendly as possible so that anyone here can contribute.
Click to expand...
Click to collapse
Alright, I'm ready when you are. PM me.
SplashInjectorsplash injector is a tool created by me based on the work done by @makers_mark . it is a basic command line interface but it gets the job done. it supports all oneplus devices so far except the oneplus x :crying: i can add support once someone gets me the logo.bin file from that device. The tool is pretty simple its based on the work here https://forum.xda-developers.com/oneplus-3/themes/mod-splash-screen-image-injector-t3441999 this is where i got this all from. i know it can be kinda hacky and only supports unix systems i think you can get it working by using git bash on windows. In its current state it can decode and encode all oneplus logo.bins (Including the OnePlus 5!) it can also pack flashable zips for you automatically. all you need to do is run the decode option edit the file you want in the output folder. Then you can run the encode command and it will pack it all back up. Then package it with the package command. Once again major credit to @makers_mark he did all the leg work. i just made it a little more friendly. lmk if there is any issues you find
Telegram: @ethanbanker if you need anything contact me here.
Now lets get to it
follow the instructions here located here
https://github.com/ethanbanker2428/SplashInjector
Updates:
1.52: Ok guys im not a windows expert...i barely use it so the tool does support windows now but it cant package files. it does give you all the tools and files you need to package one tho. you can use a tool such as this https://forum.xda-developers.com/android/software-hacking/tool-6-feb-android-flashable-zip-t3551772 this update also includes a completely revamped system. lmk about any bugs you find. for windows you need to install and use GIT bash. i also added a update function to easily update the tool. its simple but it works. heres my git again for you guys https://github.com/ethanbanker2428/SplashInjector
WARNING I AM NOT RESPONSIBLE FOR ANYTHING YOU DO. DO THIS AT YOUR OWN RISK
Excellent...... working great for OP5
Thanks
biohaz55 said:
Excellent...... working great for OP5
Thanks
Click to expand...
Click to collapse
Hi, I can't get it working on Windows. If I send you a PNG will you make me a zip?
Thanks! Here is the Windows binary and src for logoinjectorv1.52.
makers_mark said:
Thanks! Here is the Windows binary and src for logoinjectorv1.52.
Click to expand...
Click to collapse
thanks im gonna rebuild with the newest version and probably work on a windows version tonight :good:
Can you make a captain America one?
can u please make flashable zip i cannot get the method to flash . can u guide me please @bobglaus
freakzapster said:
can u please make flashable zip i cannot get the method to flash . can u guide me please @bobglaus
Click to expand...
Click to collapse
did u use option 3? package? that should make one after you edit the files
bobglaus said:
did u use option 3? package? that should make one after you edit the files
Click to expand...
Click to collapse
actually i dont know to edit files i am new to this thats why i am not understanding
freakzapster said:
actually i dont know to edit files i am new to this thats why i am not understanding
Click to expand...
Click to collapse
click the help option. i feel it explains it pretty well. to edit the png in the output folder use gimp or photoshop
Ok just an update windows support is finished and in the tool now. I'll push probably tomorrow it works and packs and unpacks fine just getting issues with packaging the zips. It corrupts them. Im gonna switch to 7zip and see if that works then I'll push
bobglaus said:
Ok just an update windows support is finished and in the tool now. I'll push probably tomorrow it works and packs and unpacks fine just getting issues with packaging the zips. It corrupts them. Im gonna switch to 7zip and see if that works then I'll push
Click to expand...
Click to collapse
Other option is to move the files to the output folder and ask the user to manually zip them, it's available on windows right click menu.
---------
I have a question, what's the BGR option for? I thought it was for op5 display but it only change the color of the pngs, so I switched it for RGB and now my logo looks good.
I share my mod, original was taken from CUSTOM BOOT LOGO PACK FOR OnePlus3.
badtzo said:
Other option is to move the files to the output folder and ask the user to manually zip them, it's available on windows right click menu.
---------
I have a question, what's the BGR option for? I thought it was for op5 display but it only change the color of the pngs, so I switched it for RGB and now my logo looks good.
I share my mod, original was taken from CUSTOM BOOT LOGO PACK FOR OnePlus3.
Click to expand...
Click to collapse
bgr does **** up the colors a bit or fixes it. its one of those things where you use it if you need it and you will know if you need it.
also update to anyone else that update will have to wait. im a perfectionist and im revamping the whole thing to alot cleaner code. windows should work tho and the oneplus x will be supported hopefully too
Update: Ok guys im not a windows expert...i barely use it so the tool does support windows now but it cant package files. it does give you all the tools and files you need to package one tho. you can use a tool such as this https://forum.xda-developers.com/android/software-hacking/tool-6-feb-android-flashable-zip-t3551772 this update also includes a completely revamped system. lmk about any bugs you find. for windows you need to install and use GIT bash. i also added a update function to easily update the tool. its simple but it works. heres my git again for you guys https://github.com/ethanbanker2428/SplashInjector
bobglaus said:
Update: Ok guys im not a windows expert...i barely use it so the tool does support windows now but it cant package files. it does give you all the tools and files you need to package one tho. you can use a tool such as this https://forum.xda-developers.com/android/software-hacking/tool-6-feb-android-flashable-zip-t3551772 this update also includes a completely revamped system. lmk about any bugs you find. for windows you need to install and use GIT bash. i also added a update function to easily update the tool. its simple but it works. heres my git again for you guys https://github.com/ethanbanker2428/SplashInjector
Click to expand...
Click to collapse
Hi, I created the zip but it won't flash in twrp. Is there a compression method to use? Using 7zip.
Bigs1985 said:
Hi, I created the zip but it won't flash in twrp. Is there a compression method to use? Using 7zip.
Click to expand...
Click to collapse
use the tool i linked in the post you qouted
bobglaus said:
use the tool i linked in the post you qouted
Click to expand...
Click to collapse
I thought it didn't package the zips correctly? Is that fixed?
Bigs1985 said:
I thought it didn't package the zips correctly? Is that fixed?
Click to expand...
Click to collapse
No this one https://forum.xda-developers.com/android/software-hacking/tool-6-feb-android-flashable-zip-t3551772
how can i pull LOGO.bin from my oneplus 5?
when i run:
adb shell dd if=/dev/block/sde17 of=/sdcard/partition/LOGO.bin
Click to expand...
Click to collapse
i get this error message:
dd: /dev/block/sde17: Permission denied
Click to expand...
Click to collapse
Please help
Thanks
spicemaster said:
how can i pull LOGO.bin from my oneplus 5?
when i run:
i get this error message:
Please help
Thanks
Click to expand...
Click to collapse
Of course you need root,The right command is
adb shell su -c dd if xxxx