Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
I98 said:
Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
Click to expand...
Click to collapse
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Meticulus said:
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Click to expand...
Click to collapse
Ok great, I might then start this project on the weekend
Thanks
I98 said:
Ok great, I might then start this project on the weekend
Thanks
Click to expand...
Click to collapse
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thank you very much
but when I'm using this command on cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Thanks again
I98 said:
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Click to expand...
Click to collapse
Looks like WinRAR has support for cpio?... never tried it but...
Meticulus said:
Looks like WinRAR has support for cpio?... never tried it but...
Click to expand...
Click to collapse
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
btw, is it just possible to place the init.rc file in the folder as that is the only file that has to be modified?
I98 said:
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
Click to expand...
Click to collapse
1. Linux on a virtual machine.
2. push the ramdisk to your player using adb. Then, use cpio in adb shell on device or terminal emulator.. :good:
Related
Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Sent from my GT-I9001 using XDA
Hey did you ever get your answer? I am also looking to do the same thanks.
EternalFame said:
Hey does anybody have a TUT in how to decompile an existing kernel so i can make some changes and then recompile it?
Click to expand...
Click to collapse
This is not the way it's done.
You'll have to get your kernels configuration. This is done either by see if there's a /proc/config.gz using the running kernel, or using the extract-ikconfig script shipped with the kernel source to extract the configuration from the kernel file.
Code:
$ extract-ikconfig kernel.img-kernel
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
[...]
This configuration you supply to the kernel source. If the vendor got some specific patches (they do), you'll have to get the kernel source from them, patches included. They must supply you the source, or be in violation of the GNU General Public License.
Building the Android boot image using mkbootimg, you'll also have to get the base address from this config.
Code:
$ extract-ikconfig kernel.img-kernel | grep PHYS_OFFSET
CONFIG_PHYS_OFFSET=[B]0x00200000[/B]
Now you have everything you'll need to build a correctly configured kernel and making the Android boot image. Detailed build instructions are included in the kernel source as well.
Wow thank you
Sent from my SGH-T989 using xda premium
Can we extract kernel with dsixda kitchen?
Edward Cullen
Kernel can be extracted, rename to *.zip
purrungo said:
Kernel can be extracted, rename to *.zip
Click to expand...
Click to collapse
it kernel.lz or etc format when use extractor it say corrupted archive
why manufacturers have to provide kernel to users when they don't want users to modify their products?. Many manufacturers just sell devices, and strangely there are many dev.er who CaN overclock or patch, modify the kernel with boot.img, HOW did they do thAt??? Kernel source code sometimes is their devevloper source code, not from manufacture stock source code.
i want to de and recompile kernel file for WSA
(windows subsystem for android)
any help?
foxhackerr said:
Any help?
Click to expand...
Click to collapse
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Renate said:
Depending on what/how much you want to modify it can be easier to patch an existing kernel than to build from scratch. Me? I'm lazy. I never build anything.
Get boot image
Extract kernel
Decompress kernel
Extract kallsyms
Disassemble kernel
Come up with a patch and patch it
Put it back together
(Steps 4 & 5 may be combined depending on your tools. I do them separately.)
Click to expand...
Click to collapse
How to do this??
kxrma said:
How to do this??
Click to expand...
Click to collapse
Use dd if rooted or EDL or extract from update
I use my imgutil.exe
I use my imgutil.exe
I use my kallsyms.exe or cat /proc/kallsyms on a running system
I use the stock objdump processed afterward with my own findref.exe (not really released yet). You could use Ghidra.
Use any hex editor. I also use my own kpatch.exe (not really released yet).
I use my imgutil.exe
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Jurellz said:
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Click to expand...
Click to collapse
hope someone contacted him
ztotherad said:
hope someone contacted him
Click to expand...
Click to collapse
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
Did you tell QuBe2 that?
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Jurellz said:
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Click to expand...
Click to collapse
I have used that exact code to boot sense myself!
notta said:
I have used that exact code to boot sense myself!
Click to expand...
Click to collapse
On the Fascinate??
istealhome said:
On the Fascinate??
Click to expand...
Click to collapse
Yes it was but now the fassy has a 1gb sys partition!
notta said:
Yes it was but now the fassy has a 1gb sys partition!
Click to expand...
Click to collapse
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
istealhome said:
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
Click to expand...
Click to collapse
Yes I am speaking of Jt's new partition layout for the 1gb!
notta said:
Yes I am speaking of Jt's new partition layout for the 1gb!
Click to expand...
Click to collapse
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
istealhome said:
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
Click to expand...
Click to collapse
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
notta said:
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
Click to expand...
Click to collapse
Ahhhh I see! Hey! You should talk to xboxfanj; he's been trying to get Sense 2.1 to boot on the fassy for a while now but hasn't been successful, tell him about the new partition layout and it should help him get 4.0 working for our phones! I'd be glad to test out for a dev duo like that
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
this wouldnt work on the showcase right?
Jurellz said:
this wouldnt work on the showcase right?
Click to expand...
Click to collapse
It would still boot most likely on the showcase if it does on the fascinate. I think kernels should be interchangable.
i flashed it and it rebooted and looped in recovery
Jurellz said:
i flashed it and it rebooted and looped in recovery
Click to expand...
Click to collapse
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
xboxfanj said:
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
nevermind i flashed it and this is what i get .
http://pastebin.com/YMQVULvZ
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
Well you could do that if you have the repo as well...
You could also save yourself some time by running "make bootimage"!
Hi guys!
This is a Kernel Kitchen based on Dsixda's android kitchen. I only add functions to compress/decompress in lzma
FULLY TESTED AND WORKING!
Features:
Code:
- COMPATIBLE WITH LINUX AND CYGWIN
- Wiew boot.img details
- Compress/decompress in Gzip and [B]Lzma[/B]
- Make Nand Boot folder
- Change command line in boot.img
- Extract ramdisk from boot.img or recovery.img in any folder
- Restart kitchen for refresh options
Downloads:
https://github.com/Lopicl/linux_kernelkitchen/releases
Sources:
https://github.com/Lopicl/linux_kernelkitchen
How to use:
1. Download latest version
2. Extract zip where you want
3. On ubuntu should ask for run in terminal when you double click menu. If not, type on terminal: cd to kitchen directory and "./menu"
4. At first boot will be created WORKING_BOOTIMG directory, insert in it your boot.img and type "k" on the kitchen.
5. Now the kitchen is set up!
Thanks:
- BIG THANKS TO DSIXDA
- Me for adapting some scripts to use only kernel part and add lzma.
Lopicl.00 said:
Hi guys!
This is a Kernel Kitchen based on Dsixda's android kitchen. I only add functions to compress/decompress in lzma
FULLY TESTED AND WORKING!
Features:
Code:
- COMPATIBLE ONLY WITH LINUX (not tested with Cygwin yet)
- Wiew boot.img details
- Compress/decompress in Gzip and [B]Lzma[/B]
- Make Nand Boot folder
- Change command line in boot.img
- Extract ramdisk from boot.img or recovery.img in any folder
- Restart kitchen for refresh options
Downloads:
https://github.com/Lopicl/linux_kernelkitchen/releases
Sources:
https://github.com/Lopicl/linux_kernelkitchen
How to use:
1. Download latest version
2. Extract zip where you want
3. On ubuntu should ask for run in terminal when you double click menu. If not, type on terminal: cd to kitchen directory and "./menu"
4. At first boot will be created WORKING_BOOTIMG directory, insert in it your boot.img and type "k" on the kitchen.
5. Now your kitchen is set up!
Thanks:
- BIG THANKS TO DSIXDA
- Me for adapting some scripts to use only kernel part and add lzma.
Click to expand...
Click to collapse
Awesome man! thanks!
good work!
Working in Cygwin!
Click to expand...
Click to collapse
Victorxs said:
Awesome man! thanks!
good work!
Click to expand...
Click to collapse
Thanks for report!
But please hit thanks button.
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
Lopicl.00 said:
Thanks for report!
But please hit thanks button.
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
Click to expand...
Click to collapse
thanx man .. working great with gs3 mini.... i was wondering if u could help me with one thing..
i just want to add some govornors and schedulers to my stock boot.img
but after extracting all i got is zimage and ramdisk folder.... i have looked into ramdisk folder and have found nothing in where i can add govornors and schedulers... couldnt find a way to extract the zimage though..
can u please tell me how to add govornors and schedulers?? and in where i should start the editing???
or can i even add schedulers and govornors to a extracted boot.img???
pulak861 said:
thanx man .. working great with gs3 mini.... i was wondering if u could help me with one thing..
i just want to add some govornors and schedulers to my stock boot.img
but after extracting all i got is zimage and ramdisk folder.... i have looked into ramdisk folder and have found nothing in where i can add govornors and schedulers... couldnt find a way to extract the zimage though..
can u please tell me how to add govornors and schedulers?? and in where i should start the editing???
or can i even add schedulers and govornors to a extracted boot.img???
Click to expand...
Click to collapse
Hahaha, for do that you need the kernel source and compile a new zImage. You can download your phone source at opensource.samsung.com
Posted from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip... : P
No one is interested?
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Lopicl.00 said:
No one is interested?
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Click to expand...
Click to collapse
What benefits do you see using this,if you dont mind me asking.
Sent from my SCH-I545 using xda app-developers app
theboo7 said:
What benefits do you see using this,if you dont mind me asking.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
You can compress/decompress the ramdisk in lzma, it gives more speed and better compression ratio than gzip.
Also you have not to download all the dsixda kitchen for use it only for kernels. You just download this. Oh and this kitchen will be also updated if there is any bug or new functions requests, dsixda wont as he left android development...
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Lopicl.00 said:
You can compress/decompress the ramdisk in lzma, it gives more speed and better compression ratio than gzip.
Also you have not to download all the dsixda kitchen for use it only for kernels. You just download this. Oh and this kitchen will be also updated if there is any bug or new functions requests, dsixda wont as he left android development...
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Click to expand...
Click to collapse
Ah I see. Well thank you, I'll definently give this a try, I'll probably need to sort out problems because my device is jfltevzw and we have to loki
Edit
Hmm unless I don't Loki until after.
Still new at this. Lol
Sent from my SCH-I545 using xda app-developers app
Up. This kichen is useful, folks!
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Lopicl.00 said:
Up. This kichen is useful, folks!
Sent from my chocolate bar that also makes coffee using Tapatalk 4 integrated microchip
Click to expand...
Click to collapse
Does this program require Java? It gives me a error saying the program java is not found.If yes,JRE is enough or do I need JDK.
Thanks in advance.
-Anderson- said:
Does this program require Java? It gives me a error saying the program java is not found.If yes,JRE is enough or do I need JDK.
Thanks in advance.
Click to expand...
Click to collapse
Yeah, you need openjdk 6.
Inviato dal mio Nexus 7 utilizzando Tapatalk
Finally.
Found the answer at last! Searching really pays off
Thank you very much for this :good:
I was finally able to changed the cwm (5.0.2.6) built in on Hell's Fusion #50 Kernel to version 5.0.2.8, with the boot.img ACTUALLY working .
My first tries (without using kitchens, but manual typing of commands), ended up as non-working boot.img.
This project involves the GT-I8730, not the SGH-I437 or the SGH-I437P.
Disclaimer
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
General Info
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community.
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced.
Click to expand...
Click to collapse
Developers/Contributors
• @kotzir (TWRP, cm-11.0, cm-12.x, cm-13.0)
• @aureljared (General Help)
• @szezso (cm-10.1, cm-11.0)
• @KINGbabasula (cm-10.1, 10.2) (General help)
• @jjchico (CWM/CM) (General help)
• @arco68 (Kernel Porting)
GitHub repos
- @kotzir's GitHub
- @aureljared's GitHub
- @KINGbabasula's GitHub.
- @jjchico's GitHub
- @szezso's GitHub
The CyanogenMod team would like to thank everyone involved with this project!
The Express does not follow standard kernel and ramdisk addresses.
To decompile the boot image:
Code:
unmkbootimg boot.img > info.txt
mkdir ramdisk
mv initramfs.cpio.gz ramdisk/initramfs.cpio.gz
cd ramdisk
gunzip -c initramfs.cpio.gz | cpio -i
To recompile, make sure you're still in the ramdisk folder, and do these to make the ramdisk:
Code:
find . | cpio -o -H newc | gzip > initramfs.cpio.gz
mv initramfs.cpio.gz ../initramfs.cpio.gz
cd ../
Now look at the info.txt you created earlier. At the bottom of 'To recompile this image...', there will be a mkbootimg command. Copy and paste that to your terminal, but before you hit Enter, add this just before '--base 0x80200000':
Code:
--ramdisk_offset 0x02000000
You may want to take a backup of the original boot image.
Reserved 2
Reserved 3
Sent from my GT-I8730 using Tapatalk
So is this rom stable and everything? cause I'm pretty noob at all of this and dont want to mess things up
EDIT: Link is dead :/
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Noisecake said:
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Click to expand...
Click to collapse
I've tried a couple on my phone but they won't upload, we'll have to wait for goo. im to fix there site.
Sent from my GT-I8730 using XDA Premium 4 mobile app
You are to fix the site?
You have an idea of when it will be fixed?
Or maybe somebody else can provide a temp upload? The site shows that the file has been downloaded over 200 times so someone must have it right? Xd
Sent from my GT-I8730 using xda premium
Yes i seen that to, it's either the download quantity is wrong or it maybe down in certain country's, I'm in Australia and i can't get it to download.
Sent from my GT-I8730 using XDA Premium 4 mobile app
Noisecake said:
You are to fix the site?
You have an idea of when it will be fixed?
Or maybe somebody else can provide a temp upload? The site shows that the file has been downloaded over 200 times so someone must have it right? Xd
Sent from my GT-I8730 using xda premium
Click to expand...
Click to collapse
Noisecake said:
So is this rom stable and everything? cause I'm pretty noob at all of this and dont want to mess things up
EDIT: Link is dead :/
Click to expand...
Click to collapse
Noisecake said:
*Bump
Is it possible for someone to upload it to another site? I must try this out lol :d
Click to expand...
Click to collapse
barclac said:
I've tried a couple on my phone but they won't upload, we'll have to wait for goo. im to fix there site.
Sent from my GT-I8730 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please read top of original post.
Got Goo to download. When I install CM 10.2 it sits on splash screen for about 20 seconds and then goes dark, double buzz and splash screen again. Not managed to change the boot image as yet. Not sure I can find time for that until Thursday.
Got my PC to boot to a 64 bit Ubuntu 13.10. Thanks to your tutorial @aureljared am having a go at building. What are you using to pack and unpack in Linux when you replace the boot image? Windows usually messes up.
Bazzan
bazzan said:
Got Goo to download. When I install CM 10.2 it sits on splash screen for about 20 seconds and then goes dark, double buzz and splash screen again. Not managed to change the boot image as yet. Not sure I can find time for that until Thursday.
Got my PC to boot to a 64 bit Ubuntu 13.10. Thanks to your tutorial @aureljared am having a go at building. What are you using to pack and unpack in Linux when you replace the boot image? Windows usually messes up.
Bazzan
Click to expand...
Click to collapse
I modified mkbootimg and unmkbootimg.
Download the tools by doing these in a terminal (I'm going to refer to my folder as tools):
Code:
[email protected]:~$ mkdir tools
[email protected]:~$ cd tools
[email protected]:~/tools$ git clone https://github.com/aureljared/mkboot_and_mkrecovery.git
[email protected]:~/tools$ cd mkboot_and_mkrecovery
[email protected]:~/tools/mkboot_and_mkrecovery$ ./copy.sh
The script copies the tools into your /usr/bin folder, but will ask for root permissions nonetheless.
Take note that you will be typing mkboot into the terminal, not mkbootimg.
Any progress, guys? =>
You know even though i wouldn't have a clue what I'm doing, i gave it another go, and even stuffed things up more than i did before, so I'm leaving it up to you guys, but at 64 I'm not afraid to give it a go.
Sent from my GT-I8730 using xda app-developers app
So guys is CM 10.2 working on the Galaxy Express ?
Hiro Nakamura said:
So guys is CM 10.2 working on the Galaxy Express ?
Click to expand...
Click to collapse
No. Problem with kernel.
Sent from my GT-I8730 using Tapatalk
aureljared said:
No. Problem with kernel.
Sent from my GT-I8730 using Tapatalk
Click to expand...
Click to collapse
Explain the problem, maybe we can make other developers understand and help, that we know from other phones and kernels.
Been doing a bit of experimenting. Flashed @KINGbabasula's rom and as reported stuck on the samsung splash screen, buzzes twice and reboots. Tried flashing a s4 mini kernel over it . Long shot but no joy.logic was as cwm came from the s4 mini and they are close cousins so might work.
Built my own cm10.2 using the tutorial provided by @aureljared using the KINGbabasula Git repository. First. Installed using the older cwm. Same result as KINGbabasula's rom. When i updated the cwm and had another go it gave me the same errors we saw on page 26 with assert failed. At least helps me spot errors in my build. Don't get the error with KINGbababasula's build.
Bazzan
Svennen said:
Explain the problem, maybe we can make other developers understand and help, that we know from other phones and kernels.
Click to expand...
Click to collapse
Okay.
CyanogenMod automatically packages boot.img with its own kernel, right? Well, that kernel doesn't boot on this phone (I don't know why).
So far we have tried numerous builds, even got to the point of using the stock kernel, all to no avail. The events below simply occur when we try booting CM:
1) phone stays at phone logo, goes black, vibrates twice, and reboots only to repeat the process; OR
2) phone stays at phone logo, then screen slowly maxes out brightness making screen extremely hot (has to press and hold power to reboot)
Also, since our CWM is from the S4 Mini (which has extremely close specs to ours) repackaged with stock kernel and correct addresses, @bazzan here tried repackaging the boot.img with a kernel from a cm-10.2 build for serranoltexx (this is what you did, right?), also to no avail.
So right now we are stuck on rooted stock 4.1.2 with CWM 6.0.3.7.
Take note: mkbootimg does not use the same addresses as the stock boot.img.
* load addresses:
kernel: 0x80208000
ramdisk: 0x82200000
tags: 0x80200100
* cmdline = console=null androidboot.hardware=qcom user_debug=31
Click to expand...
Click to collapse
Any developer aid would be greatly appreciated.
Sent from my GT-I8730 using Tapatalk
bazzan said:
Been doing a bit of experimenting. Flashed @KINGbabasula's rom and as reported stuck on the samsung splash screen, buzzes twice and reboots. Tried flashing a s4 mini kernel over it . Long shot but no joy.logic was as cwm came from the s4 mini and they are close cousins so might work.
Built my own cm10.2 using the tutorial provided by @aureljared using the KINGbabasula Git repository. First. Installed using the older cwm. Same result as KINGbabasula's rom. When i updated the cwm and had another go it gave me the same errors we saw on page 26 with assert failed. At least helps me spot errors in my build. Don't get the error with KINGbababasula's build.
Bazzan
Click to expand...
Click to collapse
Hi, i get this error too...
Can you update your rom backup?
thanks:cyclops:
SuperR's Kitchen has moved to a dedicated subforum found at the link below.
SuperR Kitchen
forum.xda-developers.com
Regarding MTK devices, I have never owned one so I am totally unfamiliar with special requirements they may need. I will add support for everything I can as issues come up
SuperR. said:
If you want to build a flashable boot.img, you should build boot flashable. If you want to build a full rom, you should build a full rom. If you want to build a flashable zip with deodexed files you should choose build custom and choose the option you want.
Click to expand...
Click to collapse
I took the first option (build full rom zip) after deodexing.
Is it good enough or do I still need to select specific custom zip to build?
ferbulous said:
I took the first option (build full rom zip) after deodexing.
Is it good enough or do I still need to select specific custom zip to build?
Click to expand...
Click to collapse
It depends on what you want to end up with. If you only want the full rom zip then full rom is good. If you want more zips with different contents, make more
SuperR. said:
Sounds like your build.prop either reports the rom as less than Lollipop or the build.prop line is different than all others I have ever seen. Please post it so I can take a look.
Did you install the package I linked above?
Click to expand...
Click to collapse
Edit: The prop says it is 5.1.1
https://mega.nz/#!GURQQADK!ujhHvu1XJ7F9BNz8cgBSclKMGilcP6fYLetub82zLzU
nghia0423 said:
Edit: The prop says it is 5.1.1
https://mega.nz/#!GURQQADK!ujhHvu1XJ7F9BNz8cgBSclKMGilcP6fYLetub82zLzU
Click to expand...
Click to collapse
This is the line we are looking for:
ro.build.version.sdk=22
and it says it is Lollipop for sure. I am not sure why it is telling you that. Are you sure you are working on the correct project?
not-i said:
So with my Moto X files I have successfully unpacked, deodexed, done some minor mods and its repacked system_new.img and its the same size as original system/img so looks promising.
I'm guessing now I "created rom zip" and thats when system.new.dat is created?
Click to expand...
Click to collapse
How did you unpack the moto x system image with this kitchen?
I just tested the moto x vzw 5.1 system image with no luck.
Many moto firmwares use an encrypted sparse format (MOTO.W›.MOT_PIV256).
I am able to use imgextractor (windows) to dump the image and list of symlinks, as well as get image info, but I haven't found any linux utilities that can handle this format.
At one point I got to plug-in my device - so far, so clear, but what if I make a rom for a device I don't have
Androidwizzard said:
At one point I got to plug-in my device - so far, so clear, but what if I make a rom for a device I don't have
Click to expand...
Click to collapse
You only need to plug in your device if you are ripping the img's from it. Normally you can get the by-name info from a boot.img. If the device does not use by-name you will need to create an mmc file and still don't need to plug in the device.
fyi
nghia0423 said:
Well this program is made for linux
Click to expand...
Click to collapse
ok well then, for the record....
the program does not like functioning with a linux emulator
v0.9.0.2
Changes:
When entering Boot/Recovery Tools, recovery no longer takes precedence. You will be presented with a choice of which to work on if boot.img and recovery.img both exist in the project directory.
Looks very nice. I guess I'm going to have to dust off my Linux install and give it a go.
SuperR. said:
Are you on the newest kitchen? I ask because it now checks to make sure you have all the other dependencies met. If you are running the newest kitchen and you are on 32-bit Ubuntu, I have no idea what is going on. Are there any errors in the terminal if you scroll up after building the zip?
Click to expand...
Click to collapse
I changed to 64 bit ubuntu and I'm able to install lib32.
Now I can generate he zip file without any issues. Looks like I'm definitely ditching the 32bit system now.
Been considering that, myself. BUT.. I deodexed ur ROM with a 32 bit Linux Mint system.. 64 bit processor tho, you?
Sent from my N9510 using Tapatalk
SuperR. said:
Try it and let us know. If you have trouble, post links to all the img files so I can have a look.
Click to expand...
Click to collapse
I am trying to create a custom rom for “Huawei Mediapad T1 8.0”. I just need a flashable rom from the stock system.img and boot.img.
I am using “dell Inspiron 15r n5010” model computer with 4gb ram and 500 gb harddisk, dual booting windows 7 with linux mint rafaela.
Version of super kitchen is 0.9.0.4. version of android 4.3 (emui 1.6)
I extracted system, boot, recovery from device using the super kitchen by options 1 and 4.
After the extraction i checked out the options and at some point kitchen wanted me to choose from set_meta or set_perm, i chose set_meta but it said that my kernel doesnt support the set_meta type and chose set_perm by default.
Using the kitchen, I debloated the firmware.
Then built the fullrom zip.
I tried to flash using TWRP recovery, but it doesnot allow me and said , “This rom is for 'msm8610' devices, This is a 'mediapadt1'”. I thought to delete that line from updater script. But didnot delete because, that may need some changes in other files too.
I think that buildprop product name is differing from recovery product name.
I have attached files i was using,, I am new to linux and also android rom building..
Help me..
Update to latest version and try again..? I'm running same dualboot system you are (diff PC) He's made many changes since earlier this week to encompass more devices
Sent from my N9510 using Tapatalk
Huawei is little complicated to build roms, can you upload the firmware?
Gesendet von meinem D6503 mit Tapatalk
stamilselvan said:
I am trying to create a custom rom for “Huawei Mediapad T1 8.0”. I just need a flashable rom from the stock system.img and boot.img.
I am using “dell Inspiron 15r n5010” model computer with 4gb ram and 500 gb harddisk, dual booting windows 7 with linux mint rafaela.
Version of super kitchen is 0.9.0.4. version of android 4.3 (emui 1.6)
I extracted system, boot, recovery from device using the super kitchen by options 1 and 4.
After the extraction i checked out the options and at some point kitchen wanted me to choose from set_meta or set_perm, i chose set_meta but it said that my kernel doesnt support the set_meta type and chose set_perm by default.
Using the kitchen, I debloated the firmware.
Then built the fullrom zip.
I tried to flash using TWRP recovery, but it doesnot allow me and said , “This rom is for 'msm8610' devices, This is a 'mediapadt1'”. I thought to delete that line from updater script. But didnot delete because, that may need some changes in other files too.
I think that buildprop product name is differing from recovery product name.
I have attached files i was using,, I am new to linux and also android rom building..
Help me..
Click to expand...
Click to collapse
Take a look at this post
http://forum.xda-developers.com/showpost.php?p=63088636&postcount=234
I try build for s3 i9300 with system.img boot.img and zip file
always I have
executing updater binary in zip
any help please
Sent from my GT-I9300 using XDA Free mobile app
Parse dat is out of date, whats your recovery version?
Gesendet von meinem D6503 mit Tapatalk