Related
Somebody could please tell me the right way to install the Jhinta Kernel on a Dualboot tablet ?
Well, i know I have to dowload these files and replace it in the OLiFE folder.
but how about the rest of the files ? (the initrd folder and 3.1.10-g8c2655b-dirty.tar.gz)
Thanks and advance my friends
when you using linux the best way is to biuld it by yourself, you can do that on tablet itself.
i'll rite you an script which do it by itself okay?
NoDiskNoFun said:
when you using linux the best way is to biuld it by yourself, you can do that on tablet itself.
i'll rite you an script which do it by itself okay?
Click to expand...
Click to collapse
That would be amazing man, I've never been able to compile jhintas kernel I always get errors (its hard debugging the problem when you have no idea about the commands your using lol)
JoinTheRealms said:
That would be amazing man, I've never been able to compile jhintas kernel I always get errors (its hard debugging the problem when you have no idea about the commands your using lol)
Click to expand...
Click to collapse
kernel.tar.gz
extract it in home directory and run ./kernel-updater.sh from terminal ... needs about an hour so plug in AC
Trying this.
You're awesome man !
FLAWLESS !!! After all the script, all i need to do was flash the kernel files by way of OLiFE.
prog19 said:
Trying this.
You're awesome man !
FLAWLESS !!! After all the script, all i need to do was flash the kernel files by way of OLiFE.
Click to expand...
Click to collapse
normally the script should flash it by itself ...
this one should flash it ... make an mistake in last one
NoDiskNoFun said:
normally the script should flash it by itself ...
this one should flash it ... make an mistake in last one
Click to expand...
Click to collapse
So just to make sure im doing this right, Ive deleted tf101-gnu-kernel from the previous script and ran the new version (Here comes the really noob question) how do i know if jhintas kernel has been installed, would uname -a work?
JoinTheRealms said:
So just to make sure im doing this right, Ive deleted tf101-gnu-kernel from the previous script and ran the new version (Here comes the really noob question) how do i know if jhintas kernel has been installed, would uname -a work?
Click to expand...
Click to collapse
you can see it in systemonitor ...
uname -r should give you 3.1.10-(blah)-dirty ... the you have jhinta's kernel on it ...
Hey man Ive ran the script 3 times and im still on 2.6, I get:
"Cloning into 'abootimg'...
fatal: unable to connect to gitorious.org:
gitorious.org[0: 42.2.0.192]: errno=Connection timed out
gitorious.org[1: 2a02:c0:1014::1]: errno=Network is unreachable
/home/josh/kernel-updater.sh: 11: cd: can't cd to abootimg
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `abootimg': No such file or directory
chmod: cannot access `/usr/bin/abootimg': No such file or directory"
This is the error i get when ive tried manually.
Hi,
I've been trying out NoDiskNoFun's net-install ubuntu as well as this script but i've been getting this message on the terminal:
INFO: task kinteractiveup:61 blocked for more than 120 seconds
Can anyone point me in the right direction on how to fix this?
I have been able to get to the point where only trackpad is not working, but after a few minutes while using it the window manager crashes and the only thing i can do is open a new terminal (via Ctrl+Search+TrackpadToggle). I'm wondering if the problem i mention above is the cause.
jammerkiai said:
Hi,
I've been trying out NoDiskNoFun's net-install ubuntu as well as this script but i've been getting this message on the terminal:
INFO: task kinteractiveup:61 blocked for more than 120 seconds
Can anyone point me in the right direction on how to fix this?
I have been able to get to the point where only trackpad is not working, but after a few minutes while using it the window manager crashes and the only thing i can do is open a new terminal (via Ctrl+Search+TrackpadToggle). I'm wondering if the problem i mention above is the cause.
Click to expand...
Click to collapse
first: wrong thread! post this in Net-Install thread please
this:INFO: task kinteractiveup:61 blocked for more than 120 seconds means nothing and does nothing, just ignore it. i don't know where it comes
i need more details, i don't know hich windows manager you mean. please post used version and your configfuration: Display Manager, Desktop Environment, etc
AND post this in right thread please
---------- Post added at 04:56 PM ---------- Previous post was at 04:54 PM ----------
JoinTheRealms said:
Hey man Ive ran the script 3 times and im still on 2.6, I get:
"Cloning into 'abootimg'...
fatal: unable to connect to gitorious.org:
gitorious.org[0: 42.2.0.192]: errno=Connection timed out
gitorious.org[1: 2a02:c0:1014::1]: errno=Network is unreachable
/home/josh/kernel-updater.sh: 11: cd: can't cd to abootimg
make: *** No targets specified and no makefile found. Stop.
cp: cannot stat `abootimg': No such file or directory
chmod: cannot access `/usr/bin/abootimg': No such file or directory"
This is the error i get when ive tried manually.
Click to expand...
Click to collapse
try to run script while you have internet connection
I did have an internet connection because i downloaded the script before hand lol, Even when i tried compile it manually on my Ubuntu desktop i got the same error, I'm so confused lol
JoinTheRealms said:
I did have an internet connection because i downloaded the script before hand lol, Even when i tried compile it manually on my Ubuntu desktop i got the same error, I'm so confused lol
Click to expand...
Click to collapse
may you can't connect to github cause of your proxy settings like you can't in china ... try ping github.org
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Rinkydink said:
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Click to expand...
Click to collapse
It is in ./TF101-GNU-Kernel/arch/arm/boot/ if the build process was succesfull
Rinkydink said:
I have tried running the script manually. Everything goes smooth until i get to where i am supposed to copy the zImage from /TF101-GNU-kernel...
The zImage is not in that folder.
Click to expand...
Click to collapse
it isn`t build right ...
So i have been following these posts for the past week trying to find out how to get jhintas kernel to work with my tab. Finally i got it through compiling, after fixing a couple bugs, but now i am not sure what to do. I have used OLife and i am running dual boot. I've tried making the flashable image using the dualboot.cfg found in OLIfe and i have tried a couple different initrd found on xda but nothing works. After flashing the proper partition, found by dissecting lilstevie's update script, the system now crashes during boot. It complains about read-only filesystem. This is very frustrating and would greatly appreciate assistance.
nazbert said:
So i have been following these posts for the past week trying to find out how to get jhintas kernel to work with my tab. Finally i got it through compiling, after fixing a couple bugs, but now i am not sure what to do. I have used OLife and i am running dual boot. I've tried making the flashable image using the dualboot.cfg found in OLIfe and i have tried a couple different initrd found on xda but nothing works. After flashing the proper partition, found by dissecting lilstevie's update script, the system now crashes during boot. It complains about read-only filesystem. This is very frustrating and would greatly appreciate assistance.
Click to expand...
Click to collapse
you don't need dualboot.cfg ... you need bootimg.cfg
NoDiskNoFun said:
you don't need dualboot.cfg ... you need bootimg.cfg
Click to expand...
Click to collapse
I am having the very same problem. I managed to compile the kernel and now i have my zImage and I have been trying to use different initramfs. After editing dualboot.cfg i managed to get rid of the read only problem by changing ro to rw. Now it boots but freezes at boot. Sometimes it gets as far as to a black screen with the cursor but then it just freezes again. I am a total noob and i dont know if i need a different initramfs or if i need to configure something else.
I am using second boot partition for Ubuntu.
My dualboot.cfg now looks like this
bootsize = 0x8d6000
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = [email protected] [email protected] vmalloc=128M gpt video=tegrafb console=tty0 usbcore.oldscheme_first=1 [email protected] root=/dev/mmcblk0p8 rw quiet splash
If anyone would be able to help me i would be very glad since I am litteraly going insane over this.
Sooo yeah.... anybody got some help for this one? I have searched google and the forums but can't clearly figure this out, but how do I get a Boot.img for this phone??? I have rebuilt the kernel 3 or 4 different ways and the output never yeilds one, however I apparently NEED one so I can peel away the ramdisk x( any ideas?
EDIT: Okay, so now that I can compile a working stock kernel for the Sidekick, where should I start now? I know we already have a working voodoo lagfix kernel, but I want to make CWM for the stock kernel, that sounds like a good spot. And adding in init.d sounds like another good start. Making my own may help me in understanding it all. I AM taking notes too
Zydrate_blue said:
Sooo yeah.... anybody got some help for this one? I have searched google and the forums but can't clearly figure this out, but how do I get a Boot.img for this phone??? I have rebuilt the kernel 3 or 4 different ways and the output never yeilds one, however I apparently NEED one so I can peel away the ramdisk x( any ideas?
Click to expand...
Click to collapse
If I recall correctly, I used the split_bootimg.pl script, and accompanying instructions, found here:
http://www.android-dls.com/wiki/?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Start by unpacking and repacking a kernel that you already know is functional -- i.e. a copy of a kernel you have already successfully flashed. Once that repack can be flashed successfully, you can move on to making modifications to it, or packing a whole new initramfs and kernel.
I had to remove references to a few of Samsung's proprietary modules to get the kernel to build -- Samsung helpfully supplies the places for those sources to be put (IN TREE -- shame on you Samsung), but not the sources themselves. One such module was rfs, IIRC. I removed the Makefile references so I could finish a compile, then used copies of the compiled modules from an existing initrd. Where you run into compile failures, where the source code appears to be simply missing, this is probably the cause.
I found that I had to manually strip at least the modules that resulted when I built from sources, otherwise the finished image was far too large. Compare the sizes of your compiled kernel and module files to those of a known-working reference image. They should not be too far out of line.
I wish I had saved more notes from my own kernel builds. Regular Linux kernels are so easy, but earlier Android kernels are unnecessarily horrible to build. Still, if you run into any more issues, I'll try to help...
Oh, and please disable the keystroke logger!
nxd said:
If I recall correctly, I used the split_bootimg.pl script, and accompanying instructions, found here:
http://www.android-dls.com/wiki/?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images
Start by unpacking and repacking a kernel that you already know is functional -- i.e. a copy of a kernel you have already successfully flashed. Once that repack can be flashed successfully, you can move on to making modifications to it, or packing a whole new initramfs and kernel.
I had to remove references to a few of Samsung's proprietary modules to get the kernel to build -- Samsung helpfully supplies the places for those sources to be put (IN TREE -- shame on you Samsung), but not the sources themselves. One such module was rfs, IIRC. I removed the Makefile references so I could finish a compile, then used copies of the compiled modules from an existing initrd. Where you run into compile failures, where the source code appears to be simply missing, this is probably the cause.
I found that I had to manually strip at least the modules that resulted when I built from sources, otherwise the finished image was far too large. Compare the sizes of your compiled kernel and module files to those of a known-working reference image. They should not be too far out of line.
I wish I had saved more notes from my own kernel builds. Regular Linux kernels are so easy, but earlier Android kernels are unnecessarily horrible to build. Still, if you run into any more issues, I'll try to help...
Oh, and please disable the keystroke logger!
Click to expand...
Click to collapse
Wow thanks nxd! I don't know if you have seen my other posts, but I'm a newbie at this stuff. Never too late to learn though right?
Now, as for the issues in the build, when I first tried to compile I was getting errors of an undeclared SEGMENT_SIZE in binfmt_aout.c so I searched around and was informed that the aout method is outdated? So I removed it from the config as instructed, seeing as it wasn't needed.
I've gotten to a compile resulting in the zImage and about 8 modules created. Now, the zImage is incomplete at this point if I am correct? If it's flashed, it will simply bootloop. (Because there is more to be done? i.e the ramdisk gz that loads the rom at the bootloader?)
Also, I will check the link about the logger, so I can disable it.
I appreciate all your help I really want to get this stuff down-pat eventually.
Zydrate_blue said:
I've gotten to a compile resulting in the zImage and about 8 modules created. Now, the zImage is incomplete at this point if I am correct? If it's flashed, it will simply bootloop. (Because there is more to be done? i.e the ramdisk gz that loads the rom at the bootloader?)
Click to expand...
Click to collapse
Correct, you need to put the modules onto an initramfs, and then assemble the zImage and initramfs into a boot.img. The URL I posted has instructions to both unpack and repack. I suggest that you obtain repack settings (command line, perhaps memory addressing) from an existing working image.
You can probably use the initramfs from an existing image as the basis for your new boot.img as well, replacing the modules from the old imitramfs with your new modules.
nxd said:
Correct, you need to put the modules onto an initramfs, and then assemble the zImage and initramfs into a boot.img. The URL I posted has instructions to both unpack and repack. I suggest that you obtain repack settings (command line, perhaps memory addressing) from an existing working image.
You can probably use the initramfs from an existing image as the basis for your new boot.img as well, replacing the modules from the old imitramfs with your new modules.
Click to expand...
Click to collapse
I hate to ask this because I'm afraid of being a pain in the a**.... but I hope you won't mind working with me, I'm in for the long run. Anyway, am I supposed to have a initramfs after the compile somewhere within the source? Or is this something I acquire from an an outside source? I promise I have done like 30-40 searches before hand. I have a feeling am missing something obvious -_-
Again, thank you for your generous help
Zydrate_blue said:
I hate to ask this because I'm afraid of being a pain in the a**.... but I hope you won't mind working with me, I'm in for the long run. Anyway, am I supposed to have a initramfs after the compile somewhere within the source? Or is this something I acquire from an an outside source? I promise I have done like 30-40 searches before hand. I have a feeling am missing something obvious -_-
Again, thank you for your generous help
Click to expand...
Click to collapse
The kernel compile will NOT produce an initramfs for you. It will produce the zImage (compressed kernel image) and modules.
The initramfs is an archive containing some files. During boot, when the kernel reaches the end of device initialization, it then creates an empty memory-backed filesystem, and extracts the initramfs contents into that new filesystem.
Ideally the initramfs would be generated by the Android build system, using the binaries produced by the kernel compile. But Samsung provides the bare minimum for GPL compliance, and so we don't get all the pieces we'd need for that. Presumably assembling those pieces is a big part of what windxixi has done, however.
When I worked up my boot.img, I used someone else's existing initramfs, dropped in my compiled modules and a few other minor changes, and then re-assembled it with my compiled zImage. If you're already working with windxixi's build kit and kernel sources, it might save you some time to use his initramfs as a basis for your own.
Really, once you've unpacked basically any SK4G boot.img, and extracted the files from the initramfs, I think you'll see the layout and that aspect the process will be clearer to you.
nxd said:
The kernel compile will NOT produce an initramfs for you. It will produce the zImage (compressed kernel image) and modules.
The initramfs is an archive containing some files. During boot, when the kernel reaches the end of device initialization, it then creates an empty memory-backed filesystem, and extracts the initramfs contents into that new filesystem.
Ideally the initramfs would be generated by the Android build system, using the binaries produced by the kernel compile. But Samsung provides the bare minimum for GPL compliance, and so we don't get all the pieces we'd need for that. Presumably assembling those pieces is a big part of what windxixi has done, however.
When I worked up my boot.img, I used someone else's existing initramfs, dropped in my compiled modules and a few other minor changes, and then re-assembled it with my compiled zImage. If you're already working with windxixi's build kit and kernel sources, it might save you some time to use his initramfs as a basis for your own.
Really, once you've unpacked basically any SK4G boot.img, and extracted the files from the initramfs, I think you'll see the layout and that aspect the process will be clearer to you.
Click to expand...
Click to collapse
I haven't found any boot.img from another kernel, however I have finally figured out how to unpack the zImage D I think I'm a bit closer now, however, now I need to figure out how to un-cpio the initramfs.cpio and/or use the intramfs folder I now have. (in the unpacked zImage)
Then the next step I suppose would be learning how to incorporate the modules that I have. hmm..
Zydrate_blue said:
I haven't found any boot.img from another kernel, however I have finally figured out how to unpack the zImage D I think I'm a bit closer now, however, now I need to figure out how to un-cpio the initramfs.cpio and/or use the intramfs folder I now have. (in the unpacked zImage)
Then the next step I suppose would be learning how to incorporate the modules that I have. hmm..
Click to expand...
Click to collapse
On the page I linked to in my first reply, under "Alternative Method", those instructions worked for me to split, unpack, repack, and assemble. Did they not work for you?
Regarding how to incorporate the modules, you would copy them into the extracted directory in the same locations in the initramfs as the existing module files. Generally something like /lib/modules. Look for files ending in '.ko'. They may be spread out a bit in your compiled kernel sources, but they should all be in one directory in your extracted initramfs directory.
As for an existing boot.img, it's a Froyo kernel, but there's this: http://forum.xda-developers.com/showthread.php?t=1663622.
nxd said:
On the page I linked to in my first reply, under "Alternative Method", those instructions worked for me to split, unpack, repack, and assemble. Did they not work for you?
Click to expand...
Click to collapse
I tried this method of repacking, but so far I have not been able to re-pack my zImage successfully. (I feel pretty close to getting this) Maybe I am putting the modules in the wrong place? Or perhaps I am skipping a step. I believe I need to assign more room for the modules. I am getting the error that initramfs_cpio is too large.
My initramfs has 2 directories in it- and I created a folder within called lib and placed the modules in there... that may be the wrong way, but I don't think it changes the need for more room in the kernel. Something to do with padding values maybe? /:
Also, the script I am using for this is from JunYoung- it is repack-zImage.sh a tool for de-compiling and recompiling a zImage. That's how I got to my initramfs directory in the new zImage I built with the source.
Zydrate_blue said:
I tried this method of repacking, but so far I have not been able to re-pack my zImage successfully. (I feel pretty close to getting this) Maybe I am putting the modules in the wrong place? Or perhaps I am skipping a step. I believe I need to assign more room for the modules. I am getting the error that initramfs_cpio is too large.
My initramfs has 2 directories in it- and I created a folder within called lib and placed the modules in there... that may be the wrong way, but I don't think it changes the need for more room in the kernel. Something to do with padding values maybe? /:
Click to expand...
Click to collapse
I think your extracted initramfs should have more than two directories.
Would you paste a listing of the files and directories here? Do this:
Code:
cd [path_to_extracted_initramfs] && find *
nxd said:
I think your extracted initramfs should have more than two directories.
Would you paste a listing of the files and directories here? Do this:
Code:
cd [path_to_extracted_initramfs] && find *
Click to expand...
Click to collapse
This is what I have after I unpack the zImage:
cpio-t
decompression_code
initramfs
initramfs/root
initramfs/dev
initramfs.cpio
kernel.img
padding3
padding_piggy
part3
piggy
piggy.gz
piggy.gz+piggy_trailer
piggy_trailer
ramfs+part3
sizes
EDIT: I also tested unpacking another zImage that is working, in fact I tried it on the Bali SK4G that we use currently (I hope that was okay with you /: I probably should have asked) but it just keeps displaying code as if it won't finish unpacking. It makes sense because there is a lot more to unpack, I think it is because it is compressed.
Zydrate_blue said:
This is what I have after I unpack the zImage:
cpio-t
decompression_code
initramfs
initramfs/root
initramfs/dev
initramfs.cpio
kernel.img
padding3
padding_piggy
part3
piggy
piggy.gz
piggy.gz+piggy_trailer
piggy_trailer
ramfs+part3
sizes
EDIT: I also tested unpacking another zImage that is working, in fact I tried it on the Bali SK4G that we use currently (I hope that was okay with you /: I probably should have asked) but it just keeps displaying code as if it won't finish unpacking. It makes sense because there is a lot more to unpack, I think it is because it is compressed.
Click to expand...
Click to collapse
You don't need my permission to use my Bali-based Linux kernel image or patches.
Where can I get a copy of this other boot.img you're working with? It seems clear the hacks and workarounds I used with the Bali-era kernel don't translate directly across. I'd like to take a look and see what I can make of it.
nxd said:
You don't need my permission to use my Bali-based Linux kernel image or patches.
Where can I get a copy of this other boot.img you're working with? It seems clear the hacks and workarounds I used with the Bali-era kernel don't translate directly across. I'd like to take a look and see what I can make of it.
Click to expand...
Click to collapse
Well, I never really found a literal "boot.img" from what I read I have to compile a zImage and in the sidekick's style system boots this as a boot.img??? And I have only used the one from kernel source so far, seeing as I could not get the Bali zImage to split.
As for the initramfs.cpio that us within the zImage, I tried to un-cpio it and I get an error about removing '/ from name?
I could send you the zImage I got from source o.e
EDIT: I never found a copy of boot.img, I couldn't even get one from an outer-source.
Sent from my SGH-T959V using xda app-developers app
Zydrate_blue said:
As for the initramfs.cpio that us within the zImage, I tried to un-cpio it and I get an error about removing '/ from name?
Click to expand...
Click to collapse
That's more of an advisory than an error. It's just telling you that it's stripping off the leading /, i.e. extracting to a relative path.
It sounds like you probably succeeded in extracting the initramfs.
nxd said:
That's more of an advisory than an error. It's just telling you that it's stripping off the leading /, i.e. extracting to a relative path.
It sounds like you probably succeeded in extracting the initramfs.
Click to expand...
Click to collapse
Well, then that sounds better! But what about this one:
cpio: dev/console: Cannot mknod: Operation not permitted
1 block
I forgot there was a following error
Zydrate_blue said:
Well, then that sounds better! But what about this one:
cpio: dev/console: Cannot mknod: Operation not permitted
1 block
I forgot there was a following error
Click to expand...
Click to collapse
You'll probably want to extract the files as root. Otherwise device nodes won't be created, like above, and permissions won't be kept on any of the files.
Be careful to be in a safe (i.e. empty) working directory when you do that. It will extract the files into your current working directory.
nxd said:
You'll probably want to extract the files as root. Otherwise device nodes won't be created, like above, and permissions won't be kept on any of the files.
Be careful to be in a safe (i.e. empty) working directory when you do that. It will extract the files into your current working directory.
Click to expand...
Click to collapse
Okay so now after I execute as root, it gives me this message:
cpio: /dev/console not created: newer or same age version exists
So the directories are empty after extracted?
Zydrate_blue said:
Okay so now after I execute as root, it gives me this message:
cpio: /dev/console not created: newer or same age version exists
So the directories are empty after extracted?
Click to expand...
Click to collapse
There's another argument you needed: --no-absolute-filenames
Unfortuantely it looks like cpio will have kept the absolute path and overwritten files on your real machine.
Extract into a directory using --no-absolute-filenames and see what files on your host system were overwritten. Those files should be recovered somehow before proceeding.
Sorry I didn't catch that.
nxd said:
There's another argument you needed: --no-absolute-filenames
Unfortuantely it looks like cpio will have kept the absolute path and overwritten files on your real machine.
Extract into a directory using --no-absolute-filenames and see what files on your host system were overwritten. Those files should be recovered somehow before proceeding.
Sorry I didn't catch that.
Click to expand...
Click to collapse
Oh god -_- wow I messed up then. well....the only file that was within the cpio was a file named console.... so I think I need to fix that?
I'm not mad or anything, it's a risk you take ya know? But I may need help.
EDIT: Okay so I reboot my laptop and it reboot fine, no issues. I don't think it actually overwrote any file (luckily because that cpio file didn't have anything in it...heh) So should I now try the command with the new argument?
Zydrate_blue said:
Oh god -_- wow I messed up then. well....the only file that was within the cpio was a file named console.... so I think I need to fix that?
I'm not mad or anything, it's a risk you take ya know? But I may need help.
EDIT: Okay so I reboot my laptop and it reboot fine, no issues. I don't think it actually overwrote any file (luckily because that cpio file didn't have anything in it...heh) So should I now try the command with the new argument?
Click to expand...
Click to collapse
I'll take a look at the boot image this evening. It would seem very odd to me if the only file on the initramfs was /dev/console.
Hello!
Device: i535PP
Kernel version: 3.4
Build date: July 22(futex(towelroot) patched)
So, I am trying to get the symbol table or whatever the heck it is.
I do not have root access, that is what I need the symbol table for > read about that here
So I can't do this the easy way of just open /proc/kallsyms
I have the zImage from boot.img.
I have kept reading on google ect that the most common type of compression used by Android kernels is gzip.
I have looked for the gzip magic numbers in a hex editor and also using hexdump/grep and dd.
I tried using binwalk zImage | head and it didn't see any gzip headers in the file, it found lzo and "pcrypt" or something like that but. I found the magic numbers for gzip... I did some googling and. I belive the whole "pcrypt" is because I had my device encrypted, and I had the OTA flash able rom on my and did all the extracting and Shia on my phone. I have since then decrypted the device and reextract everything.
I believe I am supposed to be after piggy.gz...
When I get the offset and use dd to skip to the beginning of the gzip header and save, I do gunzip piggy.gz and it says that it's corrupted. When I use a hex editor it's also corrupted...
Anyone who has done this before, mind helping me out?
I'll upload the zImage if needed.
Just don't go get the addresses yourself and post them here, I want to get some of the experience out of this
I will be more than happy to add to the list of thankyous/credits when it's all done and I test then make a release. I would also be able to port the exploit to other devices too.
I think I know why....
Probably messed it up when I tried going it on a pc I moved it back and forth via ftp... I didnt have a usb cable at the time.
If anyone wants to take a shot at this, please do. I will love you forever.
No clue what you're trying to do, but my ArchiKitchen should be able to split kernel into zImage and ramdisk, and also unpack the ramdisk, allow you to make changes, and repack it back. You can also replace zImage only if you wish... However, beware, invalid zImage may lead to brick.
You're interested in barebones project. Then you put boot.img in proper folder, restart kitchen, and unpack boot.img.
And if you're interested in decompressing zImage, then sorry, but you're doing it wrong, zImage is compressed binary, and you can't unpack the binary, even if you manage to decompress it.
@JustArchi
Well, thanks for getting me some info about that. But if I understand correctly, zImage is the kernel yes? From what I have read on boot it decompresses itself and copies it into memory. I am not really trying to modify anything, trying to get to the kernel symbols for a device that currently has not working rooting method I am aware of(i535pp on latest build...). Locked boot loader, signature verification of system.img.ext4 so no adding su binary and done. Futex is a no go, kernel compiled July 22. I am trying to port cve 4322 to the device from poc code by retme7 to get a root shell and go from there. If you know how I can go about doing that or point me to a tut, would be great.
Would this help? http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=I535pp
OpenSourcererSweg said:
@JustArchi
Well, thanks for getting me some info about that. But if I understand correctly, zImage is the kernel yes? From what I have read on boot it decompresses itself and copies it into memory. I am not really trying to modify anything, trying to get to the kernel symbols for a device that currently has not working rooting method I am aware of(i535pp on latest build...). Locked boot loader, signature verification of system.img.ext4 so no adding su binary and done. Futex is a no go, kernel compiled July 22. I am trying to port cve 4322 to the device from poc code by retme7 to get a root shell and go from there. If you know how I can go about doing that or point me to a tut, would be great.
Would this help? http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=I535pp
Click to expand...
Click to collapse
If device has locked bootloader, you won't be able to flash custom kernel you made anyway.
Otherwise, you just compile kernel from sources, get zImage, and combine it with the ramdisk through my kitchen.
JustArchi said:
If device has locked bootloader, you won't be able to flash custom kernel you made anyway.
Otherwise, you just compile kernel from sources, get zImage, and combine it with the ramdisk through my kitchen.
Click to expand...
Click to collapse
I am not trying to make a custom kernel. I am trying to extract information from the kernel required for exploitation. I am not even sure I am going about this correctly. I need to symbol table. I believe I ptmx_fops and perhaps a few other things... I have the src, anything valuable?
OpenSourcererSweg said:
I am not trying to make a custom kernel. I am trying to extract information from the kernel required for exploitation. I am not even sure I am going about this correctly. I need to symbol table. I believe I ptmx_fops and perhaps a few other things...
Click to expand...
Click to collapse
Stop it, you're talking nonsense. You won't achieve the thing you want in that way.
JustArchi said:
Stop it, you're talking nonsense. You won't achieve the thing you want in that way.
Click to expand...
Click to collapse
How do I go about making cve 2014 4322 work on my device?
I have been looking and looking...
You dont understand what not having root does to me....
Hi guys,
plz tell me how to create and edit update-binary file.
Thank you
Umn... Update-binary file or updater script?
utsha.saha.58 said:
Umn... Update-binary file or updater script?
Click to expand...
Click to collapse
tell about binary
miyuru priyawadan said:
Hi guys,
plz tell me how to create and edit update-binary file.
Thank you
Click to expand...
Click to collapse
If you are trying to modify the binary to be able to downgrade to an older firmware on a Samsung device, that is not going to work at all, it requires things that a user does not have access to, so don't waste your time trying. Without extensive knowledge of how the bootloader on your device is designed and intimate knowledge of what your hardware components expect from the software that you design, it would take years of time for you to gain the necessary knowledge and enough understanding to implement that knowledge. By then, your device would be too old to use and you will have moved on to a newer device.
Sent from my SM-S767VL using Tapatalk
Hello everyone,
The reason why I wish it to be edited and repack is because I want to change the boot logo(not boot animation) without rooting.
After few hours searching here and there, I found Samsung's boot logo located at BL_[texts].tar.md5
Open it with 7-Zip and open Param.bin, if you like to see it yourself here is a sample:
https://mega.nz/#!bV1XAQ6a!O53nC4V0HNMt3i7Qj6SCN4bxZGtkDqxPQYxSdnh_vm8
I know there's tool to edit and pack the system file but not sure how to do it with BL_[texts].tar.md5 thought
What is the tool available to replace the logo.jpg? Or is it possible to be edited using linux?
Please share what you know, and please don't discourage if you don't know.
doulc said:
Hello everyone,
The reason why I wish it to be edited and repack is because I want to change the boot logo(not boot animation) without rooting.
After few hours searching here and there, I found Samsung's boot logo located at BL_[texts].tar.md5
Open it with 7-Zip and open Param.bin, if you like to see it yourself here is a sample:
hxxps://mega.nz/#!bV1XAQ6a!O53nC4V0HNMt3i7Qj6SCN4bxZGtkDqxPQYxSdnh_vm8 <-- _vm8 no space
I know there's tool to edit and pack the system file but not sure how to do it with BL_[texts].tar.md5 thought
What is the tool available to replace the logo.jpg? Or is it possible to be edited using linux?
Please share what you know, and please don't discourage if you don't know.
Click to expand...
Click to collapse
Greetings and welcome to assist. I think it may be possible with linux, you can unpack and repack the tar file easy enough and then create a md5 file. I have never done it myself but do know of someone who did this on a verizon device with a locked bootloader
Good Luck
Sawdoctor
sawdoctor said:
Greetings and welcome to assist. I think it may be possible with linux, you can unpack and repack the tar file easy enough and then create a md5 file. I have never done it myself but do know of someone who did this on a verizon device with a locked bootloader
Good Luck
Sawdoctor
Click to expand...
Click to collapse
I'm not using any linux OS so I don't know much
1. How to compress tar files and set specific permission to file while compress using linux?
2. Is there any GUI or need to use everything using console?
3. In windows is there any tool available to compress tar file as well?
doulc said:
I'm not using any linux OS so I don't know much
1. How to compress tar files and set specific permission to file while compress using linux?
2. Is there any GUI or need to use everything using console?
3. In windows is there any tool available to compress tar file as well?
Click to expand...
Click to collapse
If you want to use linux there are plenty of prebuilt vm machines at osbox.com, I like linux mint myself as it has a desktop similar to windows. You can also boot linux mint from a usb drive without actually installing it (live mode)
I also found this tool for windows which may work as well
http://forum.xda-developers.com/showthread.php?t=2446269
And this kitchen runs in windows too
http://forum.xda-developers.com/che...-android-roms-editor-assayyedkitchen-t3410545
Hope that helps
Good Luck
Sawdoctor