I hope this IS the thread for asking questions..haha...
Firstly I'm a noob at Android developing, but I'm willing to learn..So I just got myself a Samsung Galaxy S Advance, and I'm going to try to root it myself.. But I'm quite buffled with the firmwares that I downloaded at samfirmware for this phone, cos the file inside are quite different from what we always see, listed like this:
cache.img.md5
system.img.md5
hidden.img.md5
kernel.bin.md5
modem.bin.md5
And there is also this file (SS_DL.dll) which I don't know how to use.. for rooting, I'm supposed to find the boot.img and modify some files in it, but I have no idea where to look for it... I suspected it would be in the kernel.bin, or compiled from that file, but that would be out of my knowledge... Is there anyone who can point me to the right direction?
So far i have been trying to decompile the system.img to get their NAND imgs using unyaffs and unyaffs2, but both are not working (segmentation fault and file is not multiple of 2048 + 64 or something)... Is there any other way for me to extract boot.img from the files above?
I have decompiled system.img with dsixda kitchen, to get system files, but I don't know how to get boot.img (kernel). I think it is in the kernel.bin file, but the kitchen can't decompile it. I've been asking around how to get boot.img from this phone but nobody gives me any answer. If we somehow manage to get boot.img and decomple it, we can than make insercure kernel, which could be used for rooting the phone.
Here is the guide for rooting Samsung Galaxy S I9070 Advance.
http://software2tech.com/2012/05/01/root-galaxy-s-advance-i9070/#more-18866
There is one problem though, the most important files, that we need, haven't been uploaded yet. I've already searched this group on facebook, and nwrite them to publish those files (kernels), but there was no answer. So I doubt that they even have those rooted kernels. Maybe you could write them too, and lets hope that they will publish kernels soon!
I think they don't really have the rooted kernel.. Cos Samsung haven't even release the opensource k kernel yet.. But yeah, right now I'm stuck.. I have been trying almost every possible way to create the boot.img, including unyaffs and unyaffs2, but keep getting errors... If we can just ask the guys at rootzwiki to port CWM recovery for us, but maybe they need rooted source too..
This would be great if they could build us CWM recovery. I don't think they need kernel source they just need stock recovery, but to get stock recover.img from our phone we need to know here is located. I have pull partitons layout from the phone, but unfortunatly it doesnt tell anything useful. You can see it in the attachment.
whoa...that is great...maybe that could help...i will try to check with other phones, cos it might be that one of this partitions would contain boot.img as well as recovery.img... how exactly you extract this information, using kitchen, perhaps? haha...
No my phone used to be rooted, until I have upgrade it to new firmware (stupid me I know, but I had test firmware before, and had quite few bugs). And I've pulled this from system partition (in /proc folder). But you can also get it with this:
adb shell
cd proc
cat partitions
I can provide some other files, that might be useful. We just need some help from experienced developers, but so far no help was offered. I've been starting threads all over the place, but nothing .
In the attachment are all the files that might help some developer to get us recovery working!
well, after searching throughout the web, I'm starting to think that without the opensource kernel from samsung, it might be quite impossible for us to root this phone... every other imaginable ways to make these system or boot images seemed to require root access... so far samsung had done a very well job in patching those root exploits...
kilsmap said:
well, after searching throughout the web, I'm starting to think that without the opensource kernel from samsung, it might be quite impossible for us to root this phone... every other imaginable ways to make these system or boot images seemed to require root access... so far samsung had done a very well job in patching those root exploits...
Click to expand...
Click to collapse
Yeah I think you are right, but I wish you wer not . Well no we have to wait for samsung to release source code of the kernel.
Ok source code for kernel is now available!!! You can download it from opensource.samsung.com. I will make a thread later, with mirror links! Now lets compile that sh*** !
hahahahaha...at last...i was checking that site every few hours...this would make it!!
I've just made a thread on XDA:
http://forum.xda-developers.com/showthread.php?p=25782811#post25782811
If you managed to compile it before me please PM . I'm just installing linux, but I won't be able to continue until tommorow, cause I do this on work computer .
Hey there XDAians....
Can someone here point me to a walkthrough or tutorial on porting roms from and to devices of different manufacturers,resolution(mdpi,hdpi etc.) etc.I am familiar with the zip method of porting roms from same manufacturer(sony in my case,xperia U to Sola)but i want to know about porting roms from others like htc,samsung etc and Tools/apps needed to accomplish this.Most of the tutorials i found on XDA are based on the same method of zip porting.
Please help me with this,i really want to learn more about porting.
In the minimum, you must learn how to create a boot.img for your new device based on the boot.img (especially the ramdisk) from the old device.
To do this, you must extract the boot.img of your old device, edit the ramdisk (As there are lots of files named like the device, and those must be renamed to match the new device's name) Probably you must also change the content, to match the needs or to update references to some files, where the name changed.
After this, you can recreate the ramdisk.
Than extract a boot.img of your new device to get the kernel. Take the new Kernel and the new Ramdisk and make a new boot.img
Extracting and recreating a boot.img is described in the later part of this article: How to build a custom kernel
Recreating a ramdisk is described in this article: Create/Modify ramdisk
This might be the first step of a lot of steps...
Kind regards Uwe
Hello,
I tried to do a simple task which raise several problem and it start to drive me crazy, so here I am, asking for help. The subject may have been already mentioned, but can't find an issue with the galaxy s3.
I work with ubuntu 12.04 and Odin on win7. My GS3 has XXELL4 baseband, and 3.0.31-742798 kernel version.
I need to load and run a custom module (let's say a "hello world" one for begin) on the galaxy S3.
I compiled it through a Makefile with the toolchain from the ndk package (
Code:
path_to_ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
and the source code from the samsung web site (GT-I9300_JB_Opensource_Update8.zip).
Obviously, when i tried to insmod my module, I've got some compatibility error like
Code:
Exec format error
.
The fact is that the kernel from website is not the same as the phone one.
So I tried to put the kernel from the website on the phone
I compiled it with the same toolchain and I received a zImage file in result. But what to do with this file ? I extracted a boot.img from the phone with Odin and split it (with perl script stuff) to use the extracted files with my compiled zImage for reconstruct a new boot.img. But since fastboot is not available on GS3 (or I miss something) I can't simply
Code:
$ fastboot flash boot boot.img
, and need to use Odin again. So I replace the boot.img from odin's backup folder on my PC with my boot.img. But the nandroid.md5 file raise an error. Am I doing it wrong or too complicated ? If I can correct the md5 error, is that my module will work ?
I also tried to compil my module directly with the kernel from the phone but didn't manage to extract the kernel files to do it. Stuck with a boot.img. Same with the stock kernel from http://forum.xda-developers.com/showthread.php?t=1646610
I made a lot of research but don't find any concrete solutions to my simple task. Maybe I miss something or looking too deep.
Is there a more simple way to run a custom module on the GS3 ?
sorry for my english
Hello and welcome to xda!
You do not have to use odin to flash your kernel, you can do it via custom recovery too.
Just get an simple cwm package of another kernel for s3 and replace the boot.img in the zip.
I attached a simple empty cwm package, just drag your boot.img to the root of the zip with winrar or something.
hsrars-d said:
Hello and welcome to xda!
You do not have to use odin to flash your kernel, you can do it via custom recovery too.
Just get an simple cwm package of another kernel for s3 and replace the boot.img in the zip.
I attached a simple empty cwm package, just drag your boot.img to the root of the zip with winrar or something.
Click to expand...
Click to collapse
Thanks
I've got also a md5 error when i tried to restore with cwm, since I have no md5 file in my folder. Do I need to generate one ? how ?
EDIT: so a generate a md5 file with md5sum, but still have the Exec format error when i try to insmod my module.
ok, im not good with kernel stuff/modules so i cant help you any further...
try to find someone that has experience with kernel modules
edit: found something with google, not exactly for s3 but the error is pretty common:
http://www.linuxquestions.org/questions/linux-kernel-70/insmod-error-version-magic-4175424366/
http://forum.xda-developers.com/showthread.php?t=444338&page=1
http://stackoverflow.com/questions/...for-android-unknown-relocation-27-when-insmod
Why are you posting in this section?
Glebun said:
Why are you posting in this section?
Click to expand...
Click to collapse
well ... I don't yet have access to other section. But If someone could move the thread in a more appropriate one I'll thanks him.
Yes, you do. Questions go in the Q&A section, obviously
Hello,
I tried to do a simple task which raise several problem and it start to drive me crazy, so here I am, asking for help. The subject may have been already mentioned, but can't find an issue with the galaxy s3.
I work with ubuntu 12.04 and Odin on win7. My GS3 has XXELL4 baseband, and 3.0.31-742798 kernel version.
I need to load and run a custom module (let's say a "hello world" one for begin) on the galaxy S3.
I compiled it through a Makefile with the toolchain from the ndk package (
Code:
path_to_ndk/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-
and the source code from the samsung web site (GT-I9300_JB_Opensource_Update8.zip).
Obviously, when i tried to insmod my module, I've got some compatibility error like
Code:
Exec format error
.
The fact is that the kernel from website is not the same as the phone one.
So I tried to put the kernel from the website on the phone
I compiled it with the same toolchain and I received a zImage file in result. But what to do with this file ? I extracted a boot.img from the phone with Odin and split it (with perl script stuff) to use the extracted files with my compiled zImage for reconstruct a new boot.img. But since fastboot is not available on GS3 (or I miss something) I can't simply
Code:
$ fastboot flash boot boot.img
, and need to use Odin again. So I replace the boot.img from odin's backup folder on my PC with my boot.img. But the nandroid.md5 file raise an error. I deleted the dd5 file and regenerate one with md5sum. Still have the Exec format error when insmod. Am I doing it wrong or too complicated ? If I can correct the md5 error, is that my module will work ?
I also tried to compil my module directly with the kernel from the phone but didn't manage to extract the kernel files to do it. Stuck with a boot.img. Same with the stock kernel from http://forum.xda-developers.com/showthread.php?t=1646610
I made a lot of research but don't find any concrete solutions to my simple task. Maybe I miss something or looking too deep.
Is there a more simple way to run a custom module on the GS3 ? How do I find a loadable and targetable kernel for my module ?
sorry for my english
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Paolo.dev said:
Good evening,
I've written a module for my smartphone and I need to compose a rom to install on my device...
I followed some tutorials, so now I know how to build an android kernel, obtaining a zImage.
Now, a friend told me that I must make a backup with clockworkmod (done!) and download on my pc, than I can recover the boot.img from there and split them in ramdisk and kernel.
Now I can compile my new kernel and merge it (the obtained zImage?) with the ramdisk to have a new rom to flash on my device... is true?
But I don't know how I can split the boot.img (maybe with dsixda kitchen?) and how to create the new rom. I tryied som weeks ago with a .zip rom and the dsixda kitchen and I split and recomposed a rom, but files contained in the .zip files was different from files that I downloaded by my device...
Someone can explain me the correct way to do this process? Thank you!
Click to expand...
Click to collapse
So many u can use
1. http://forum.xda-developers.com/showthread.php?t=1619473
2. http://forum.xda-developers.com/showthread.php?t=2036528
3. http://forum.xda-developers.com/showthread.php?t=1877807
and many more if u search