Initlogo.rle not change on boot GT-S7275R (Galaxy Ace 3 LTE) - Android Q&A, Help & Troubleshooting

Hi. Sorry for my bad english.
I have Samsung GT-S7275R (Galaxy Ace 3 LTE Europe) and i try to make a flashable md5 rom with other initlogo.
I do this:
Download my firmware (PRO-S7275RXXUAMHH-20130930101515)
unzip to show 7 files: boot.img, cache.img.ext4, hidden.img.ext4, NON-HLOS.bin, recovery.img, system.img.ext.4, tz.mbn.
use kitchen with boot.img to uncompress in one file and one directory (zImage and boot.img-ramdisk).
Change initlogo.rle with my initlogo.rle and build with kitchen. All this ok.
After, i user tar and md5 to make tar.md5 file.
I flash this, and i haven't flash problems but when i boot the initlogo dont change. I try to reset and reflash but nothing change. Anyone can help me? I dont know what i doing bad.
*Initlogo "Samsung Galaxy GT-S7275R" black and white screen before animation, to not mistake
Thanks all and sorry for mi bad english.

I find the problem. Param.lfs has boot logo inside and i have to modify this but i have one trouble.
When i dump param partition with
Code:
dd if=/dev/block/mmcblk0p9 of=/mnt/sdcard/param.lfs
I get this:
Code:
16384+0 records in
16384+0 records out
8388608 bytes transferred in 0.953 secs (8802316 bytes/sec)
All ok, but i try to open it with Hex and code is 00 in all param.lfs. I can't change anything.
I attachen param.lfs if anyone can help me. Thanks!
Download param.lfs
PD: I try ketut jpg extract tool, but not extracted. i don't know what i do

Related

[Q] Unpack system.img GPad G10

Hi all,
I have a question about the GPad G10 firmware files.
I have unpack the rom of the G10, and i have now 3 files, boot.img, recover.img en system.img.
I can unpack the boot.img and the recover.img with split_bootimg, but when i try to unpack the system.img with unyaffs it fails.
I think its because the system.img is an ext3 format?
Can anyone tell me how i can extract this system.img with another way.
You can find the system.img here: tinyurl.com/6kqvoot
Jelmer.
Sorry for my bad english, i am dutch.
In CentOS when i type:
Code:
file system.img
it says:
Code:
system.img: VMS Alpha executable
Can someone tell me how i can extract that sort of files?
Jelmer.
Sorry for bad english, i'm Dutch.

[Q]

hello
i want to create custom boot image.i am using cygwin bash shell and android kitchen.
i extract boot.img with Android Kitchen 0.194 Tools for boot images <unpack/re-pack/etc.>
it show like this
Working folder found
Kernal found at offset 2048 in boot.img
Making folder BOOT-EXTRACTED ....
Extracting kernal ...
Extracting ramdisk ...
Error : NO ramdisk folder found!
Press Enter to counting
How i solve Error:NO ramdisk folder found.
Are you have trouble extracting from the phone or extracting the .img file into something editable? I see at the top of the first page here that there is an update to the Kitchen. Maybe the newer version supports your phone better?

[Q] how do I deploy a modified source code into Note 3?

Greetings
I need some help with packing a compiled image of the Samsung Source into a flashable image. After that I downloaded the stock image of my phone from SamMobile, and unpacked it. I then used an script called umkbootimg to replace the zImage in boot.img with mine and can created another boot.img. Here is what I have now:
stock3$ ls
aboot.mbn recovery.img
boot.img rpm.mbn
cache.img.ext4 sbl1.mbn
initramfs.cpio.gz sdi.mbn
modem.bin SS_DL.dll
N900PVPUCNC5_N900PSPTCNC5_N900PVPUCNC5_HOME.tar.md5 system.img.ext4
N900PVPUCNC5_N900PSPTCNC5_SPR.zip tz.mbn
NON-HLOS.bin zImage
I have tried to use tar –H ustar –C command to pack the files into a tar ball. I then added md5, and zipped the whole thing with zip command. But could not use twrp to flash it. I have also looked into Odin and Heimdall. The greatest success I have had so far has been an image that puts my phone into boot loop, and I had to recover. What is the fastest way I can create an image from this?

[GUIDE] Make a kernel for G531F variant

So, I'm doing this tutorial due to the trial and error I got.
Prerequisites:
Ubuntu or any linux-based os with the right packages installed
Source code from the kernel
Backup of you boot partition
These tools here
Patience
1) The first thing you want to do is to do a backup of your boot partition.
Code:
adb shell
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
2) Download the source code from here, extract it and place it somewhere. I placed it in /home/fabio/Documentos/Kernel/sourcecode
3) Download a toolchain, I downloaded "aarch64-linux-android-4.8" from google and placed in "/home/<your username>/Documentos/Kernel/aarch64-linux-android-4.8"
4) Go to your kernel source code and find the file "Makefile", open it and change CROSS_COMPILE= to say the place where you stored the toolchain "/home/<your username>/Documentos/Kernel/aarch64-linux-android-4.8" + "/bin/aarch64-linux-android-"
5) Now that you are done setting up the stuff, open a console and navigate to your kernel source code root and type
Code:
make
make pxa1908_grandprimevelte_eur_defconfig
make -j#
# is the number of cores + 1
6) While that runs, go to where you stored those mkbootimg tools and unpack that boot.img you backed up
7) Once the kernel building is complete. Go to your kernel folder and navigate to arch/arm64/boot and copy the file "Image.gz"
8) Download bless or an Hex Editor of your liking and open the following files: boot.img (the original boot), Image.gz, boot.img-zImage.
Search on the "boot.img-zImage" for 1F 8B 08 and copy everything before then on your Image.gz place what you copied and save it as a different file otherwise it will fail to save.
9) Go to your mkbootimg folder and where you stored the unpacked files and build one boot.img with the following command
Code:
./mkbootimg --kernel image2.gz --ramdisk boot.img-ramdisk.gz --dt boot.img-dt --signature boot.img-signature -o boot2.img
10) Flash the boot2.img using any software you want!
THIS MIGHT NOT WORK! If it doesn't you can send me a DM! I will be retouching this post again and make it prettier adding pictures and stuff but for now I can't do much!
If you know a better way of doing this please say in the replies! I will be building a kernel for this device soon enough
RESERVED
Can you please upload link of custom kernel
I'm still trying to do a kernel with new features, but don't know what to add yet. Trying to make Init.d support without 3rd party apps!
EDIT1: I give up! My phone is too much trouble and since SAMSUNG doesn't care about it neither do I anymore! Try to build the kernel yourself and tweak it as you like! Make a script to automate this process to be easier! Good luck! Anything you need just say
Can you help this guy for porting kernel source code http://forum.xda-developers.com/grand-prime/general/developers-discussion-sm-g531f-custom-t3444598
fabiossilva21 said:
So, I'm doing this tutorial due to the trial and error I got.
Prerequisites:
Ubuntu or any linux-based os with the right packages installed
Source code from the kernel
Backup of you boot partition
Degas mkbootimg tools
Patience
1) The first thing you want to do is to do a backup of your boot partition.
Code:
adb shell
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
2) Download the source code from here, extract it and place it somewhere. I placed it in /home/fabio/Documentos/Kernel/sourcecode
3) Download a toolchain, I downloaded "aarch64-linux-android-4.8" from google and placed in "/home/fabio/Documentos/Kernel/aarch64-linux-android-4.8"
4) Go to your kernel source code and find the file "Makefile", open it and change CROSS_COMPILE= to say the place where you stored the toolchain "/home/fabio/Documentos/Kernel/aarch64-linux-android-4.8" + "/bin/aarch64-linux-android-"
5) Now that you are done setting up the stuff, open a console and navigate to your kernel source code root and type
Code:
make
make pxa1908_grandprimevelte_eur_defconfig
make -j#
# is the number of cores + 1
6) While that runs, go to where you stored degas-mkbootimg tools and unpack that boot.img you backed up
7) Once the kernel building is complete. Go to your kernel folder and navigate to arch/arm64/boot and copy the file "Image.gz"
8) Download bless (Hex Edit) and open the following files: boot.img (the original boot), Image.gz, boot.img-zImage.
Search on the "boot.img-zImage" for 1F 8B 08 and copy everything before then on your Image.gz place what you copied and save it as a different file otherwise it will fail to save.
9) Go to your degas-mkbootimg folder and where you stored the unpacked files and build one boot.img with the following command
Code:
./degas-mkbootimg --kernel image2.gz --ramdisk boot.img-ramdisk.gz --dt boot.img-dt --signature boot.img-signature -o boot2.img
10) Flash the boot2.img using any software you want!
THIS MIGHT NOT WORK! If it doesn't you can send me a DM! I will be retouching this post again and make it prettier adding pictures and stuff but for now I can't do much!
If you know a better way of doing this please say in the replies! I will be building a kernel for this device soon enough
Click to expand...
Click to collapse
i follow this step and build kernel after flash boot.img phone not booting
my boot.img size is 8.2MB (image.gz size 6.5MB) where stock size is 8MB
is problem with size?
sorry for my bad english
How did you flash the boot.img?
fabiossilva21 said:
How did you flash the boot.img?
Click to expand...
Click to collapse
using odin
What changes did you make to the kernel?
fabiossilva21 said:
What changes did you make to the kernel?
Click to expand...
Click to collapse
Add governors
Other setting same as stock
If i build with stock setting without any changes then kernel boot but if i change something then its stuck on Samsung logo
Sorry, I can't really help you... I no longer work with Grand prime... switched to a J5
fabiossilva21 said:
Sorry, I can't really help you... I no longer work with Grand prime... switched to a J5
Click to expand...
Click to collapse
Ok
Noice

Invalid Boot.img when trying to extract kernal and ramdisk.

A very warm Hi! to the XDA community
My phone, the Sony Xperia E4, does not have a recovery - so I am slowly learning how to develop one. It has an MT6582 chip.
In the process I have obtained the stock boot.img (via boot.sin) from the phone's stock .ftf firmaware file.
I wish to use MTK droid tools to create the recovery, however it first gave me the error that the boot.img file is not split. After some research I came to learn that such boot.img files need to be split into the kernal (Zimage i believe) and ramdisk.
After some further research I came across this seemingly helpful guide and tool on how to split the boot.img file on Windows (unfortunately I do not have Linux at my disposal atm).
Now to my issue: (referring to the aforementioned guide & tool) When running the command
Code:
bootimg.exe --unpack-bootimg boot.img
I get this error:
Code:
AssertionError: invald bootimg
Which leads me to believe the boot.img file I have extracted may be corrupt or extracted from the wrong .sin file.
If you are still with me, how can i confirm that the boot.img file from the stock rom is indeed "working" and contains ramdisk and kernal?
Some extra information:
This is the guide I used to initially extract the boot.img file from my phones stock firmware. They highlight that boot.img is extracted from the kernal.sin file. My firmware has no such file. Later in the comments it mentions that newer Sony phones have the boot.img file in the appropriately named "boot.sin" file. This is the file i used to extract my boot.img. Thus from here I cannot see why the boot.img file cannot be split.
The full command line and response is:
Code:
C:\Users\\Downloads\Cofface>bootimg.exe --unpack-bootimg boot.img
arguments: [bootimg file]
bootimg file: boot.img
output: kernel[.gz] ramdisk[.gz] second[.gz]
Traceback (most recent call last):
File "<string>", line 2213, in <module>
File "<string>", line 1424, in unpack_bootimg
File "<string>", line 151, in parse_bootimg
AssertionError: invald bootimg
Thanks very much in advance!

Categories

Resources