Related
The proyect its now opensource, can anyone compile this? like a stand alone app so we can install it in any tablet?
https://github.com/Onskreen/cornerstone
Thx
It is unfortunately not that simple. CornerStone has parts that come as patched system files.
It needs to either be included in a ROM or come as a patch (.zip) for a specific ROM.
cyansmoker said:
It is unfortunately not that simple. CornerStone has parts that come as patched system files.
It needs to either be included in a ROM or come as a patch (.zip) for a specific ROM.
Click to expand...
Click to collapse
I tried patching a few rom-s but with no success...
Anybody got it working?
I asked for help to build a rom ics on our xt615
I present the trick:
we recover a leak motorola ics for our phone (. sbf)
we extracted the boot.img system.img recovery. etc. .....
we have for the moment a Chinese cwm recovery but works in English or a problem with the nandroid
the problem is that when trying to build the rom for our phone and flash that we have a "status 0"
then here we ask a person who could help us build a rom ics
thank you
links:
extracted from sbf
https://docs.google.com/file/d/0B2k1N5APM4JQLWZ3ajVETG54UTQ/edit
testing the construction of the ROM
https://docs.google.com/file/d/0B2k1N5APM4JQaWF0N0Q0TV9pWTA/edit
and the subject of motoluxe xt615 not play pass all first pages on pages 65 to
http://forum.xda-developers.com/showthread.php?t=1660377&page=77
Up please
Thank
Sent from my XT615 using xda app-developers app
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
gee one said:
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
Click to expand...
Click to collapse
Yes but try various solution and i have always error status 0
If you look the topic we have try
Page n° 70\80
Thank
Sent from my XT615 using xda app-developers app
gee one said:
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
Click to expand...
Click to collapse
I don't understand
I took example on several
can you help me to do this update
A big thank
Sent from my XT615 using xda app-developers app
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
gee one said:
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
Click to expand...
Click to collapse
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
dams161 said:
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=31086093
Sent from my XT615 using xda app-developers app
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
gee one said:
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
Click to expand...
Click to collapse
thank you
i try and i say if work
does not work I toujour error status 0
I think that is an error with the update binary. Maybe you can get one from a similar phone? It should be pretty generic, as long as it uses a similar file system/android version. So try to find a binary from an ics device that uses yaffs/MTD.
sent while running with scissors
i try and i say if work
yes works but the boot.img is bad thank you
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
gee one said:
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
Click to expand...
Click to collapse
the concern is that the bootloader is locked
and I think he does not want ics files
you have ideas on how to bypass the UNLOCK or
thank you again
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
gee one said:
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
Click to expand...
Click to collapse
my boot.img
So the zip that I uploaded flashes, but it doesn't boot?
I think your working boot image is GB or Froyo and the new one is ICS. So maybe if I take the kernel from the ICS boot.img and add the ramdisk from your working one, then maybe it might work.
Maybe...
This is the new kernel with the old ramdisk. Again, flash at your own risk.
https://rapidshare.com/files/908298923/xt615ics1.2_mod3.zip
To start with, I've been searching around looking for an answer, but haven't found anything useful.
I have started playing around with my really first ROM. I have a stock Rom for my Xperia Z as base. But I wanted to add some nice mods for this rom.
When I open a flashable mod zip there is two folders, the META INF and system. But how do I add the mod to be installed with my rom?
Thanks a lot!
/Jimmy
MinnesotaVikings1961 said:
To start with, I've been searching around looking for an answer, but haven't found anything useful.
I have started playing around with my really first ROM. I have a stock Rom for my Xperia Z as base. But I wanted to add some nice mods for this rom.
When I open a flashable mod zip there is two folders, the META INF and system. But how do I add the mod to be installed with my rom?
Thanks a lot!
/Jimmy
Click to expand...
Click to collapse
Hi,
To add mods, first download the mod and merge the system folder of the mod with the system folder of the base rom. Then, open the updater-scipt of the mod and copy all lines which are related to setting permissions like set_perm(..); and even symlinks. Paste all these lines at the end of your updater-script of the base rom, but before you unmount all the partitions.
Good luck:good:
MinnesotaVikings1961 said:
To start with, I've been searching around looking for an answer, but haven't found anything useful.
I have started playing around with my really first ROM. I have a stock Rom for my Xperia Z as base. But I wanted to add some nice mods for this rom.
When I open a flashable mod zip there is two folders, the META INF and system. But how do I add the mod to be installed with my rom?
Thanks a lot!
/Jimmy
Click to expand...
Click to collapse
I'm about to start a thread w/a guide on how to take your favorite root tweaks/mods and build them into the settings, if you don't already have it, download and install virtuous-ten studio for your pc to get a head-start :good:
someone needs to make a guide because i can boot p760 roms but screen is reversed and with different kernel's i get instant reboot on lg logo.
thasilenthacker said:
someone needs to make a guide because i can boot p760 roms but screen is reversed and with different kernel's i get instant reboot on lg logo.
Click to expand...
Click to collapse
The easiest way is
1. Replace kernel with working P769 kernel.
2. Replace all propeitrary files with P769 version. (You can have these files list from CM)
3. Add some more libraries (I don't know which files. I got brightness config doesn't working problem but I cannot solve it.)
I think that's all. Then you can add some customize to the rom. I used to port MIUI to P769 and that is what I did. But you may have some problem with some hardware library which is not in propreitary files list. It's an trial and error process but you need to have P769 to test it.
@artit do you think you could list the exact files please?
I was trying to figure out how to get jellybean on p769 but I haven't figured it out lol. I tried building from aosp and got some error I couldn't figure out. I was trying to build aosp, and using Anton X sources.
Sent from my Nexus 4 using Tapatalk
thasilenthacker said:
@artit do you think you could list the exact files please?
Click to expand...
Click to collapse
You better use AntonX repo https://github.com/AntonX/android_vendor_lge_p769
Juanito216 said:
I was trying to figure out how to get jellybean on p769 but I haven't figured it out lol. I tried building from aosp and got some error I couldn't figure out. I was trying to build aosp, and using Anton X sources.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I also tried to build AOSP but cannot boot it up. We already have L9 device tree, it's easier to build CM, AOKP, PAC or AOSPA than AOSP.
artit said:
You better use AntonX repo https://github.com/AntonX/android_vendor_lge_p769
I also tried to build AOSP but cannot boot it up. We already have L9 device tree, it's easier to build CM, AOKP, PAC or AOSPA than AOSP.
Click to expand...
Click to collapse
I attempted before CM 11 sources came out. I haven't tried again since then. I might have another go but this time with CM 11. AOSP might be difficult but not impossible. Then again, I want my tweaks. At the same time though, it would be nice to have a clean, Nexus type of ROM, like a "Google Edition L9"
Sent from my LG-P769 using Tapatalk
ok im using propeitrary files this time im gonna test if it works
@artit by any chance if if's not any trouble for you, I was hoping I could ask how to create an Aroma version of a ROM installer. Any help is greatly appreciated, also thanks for MIUI
leolawliet said:
@artit by any chance if if's not any trouble for you, I was hoping I could ask how to create an Aroma version of a ROM installer. Any help is greatly appreciated, also thanks for MIUI
Click to expand...
Click to collapse
I also start using aroma by examine other dev works. These is what you have to do to use aroma installer.
1. Download it from http://forum.xda-developers.com/devdb/project/?id=330#downloads
2. Downloaded file is an example of aroma. Boot in to recovery and install it, you will see a lot of aroma features. You can create your own test file by copy some config from that file or maybe aroma file in my ROM.
3. Aroma script files are in /META-INF/com/google/android/
- aroma-config -> You use this config to create all dialog and pages in aroma
- updater-script -> Normal updater-script file. You can get aroma options and use it as conditional parameter
- update-binary -> this is aroma program
- update-binary-installer -> this is an original update-binary. If you want to use update-binary from CM or others rom please replace it with this file.
- aroma -> this folder contains resources. I use changelog.txt in this folder.
4. To add aroma to your rom
- In your rom, rename /META-INF/com/google/android/update-binary to update-binary-installer
- copy all aroma files to /META-INF/com/google/android/ (except update-binary-installer and updater-script)
- create you own aroma-config
- customize your updater-script to use options from aroma prop
5. If something go wrong while installing, aroma has an option to save install log to sdcard. You can review what is the problem in that log.
That's all. It's not hard to use aroma.
---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------
Juanito216 said:
I attempted before CM 11 sources came out. I haven't tried again since then. I might have another go but this time with CM 11. AOSP might be difficult but not impossible. Then again, I want my tweaks. At the same time though, it would be nice to have a clean, Nexus type of ROM, like a "Google Edition L9"
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Nice try, I've tried to build AOSP 2 or more times but not success
I can build AOSP but it doesn't boot up. In logcat there're something wrong with display initialzation. I also try to use CM / AOKP build platform to build AOSP. But it has some libs conflict that I cannot solve.
i kept getting failed flashing zip, i was trying to port chameleon os for p760
keeps saying error in updater-binary
thasilenthacker said:
i kept getting failed flashing zip, i was trying to port chameleon os for p760
Click to expand...
Click to collapse
Some command in update-script is wrong or misplaced. It's hard to correct that. For me, I add some ui_print() to see what's the last step script run into and try to see what is the problem.
ok i found my problem at setting permissions
i used cm set_perm and still same thing its says " ste_perm: some changes failed
artit said:
I also start using aroma by examine other dev works. These is what you have to do to use aroma installer.
1. Download it from http://forum.xda-developers.com/devdb/project/?id=330#downloads
2. Downloaded file is an example of aroma. Boot in to recovery and install it, you will see a lot of aroma features. You can create your own test file by copy some config from that file or maybe aroma file in my ROM.
3. Aroma script files are in /META-INF/com/google/android/
- aroma-config -> You use this config to create all dialog and pages in aroma
- updater-script -> Normal updater-script file. You can get aroma options and use it as conditional parameter
- update-binary -> this is aroma program
- update-binary-installer -> this is an original update-binary. If you want to use update-binary from CM or others rom please replace it with this file.
- aroma -> this folder contains resources. I use changelog.txt in this folder.
4. To add aroma to your rom
- In your rom, rename /META-INF/com/google/android/update-binary to update-binary-installer
- copy all aroma files to /META-INF/com/google/android/ (except update-binary-installer and updater-script)
- create you own aroma-config
- customize your updater-script to use options from aroma prop
5. If something go wrong while installing, aroma has an option to save install log to sdcard. You can review what is the problem in that log.
That's all. It's not hard to use aroma.
---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------
Nice try, I've tried to build AOSP 2 or more times but not success
I can build AOSP but it doesn't boot up. In logcat there're something wrong with display initialzation. I also try to use CM / AOKP build platform to build AOSP. But it has some libs conflict that I cannot solve.
Click to expand...
Click to collapse
Thanks, it's more simple than I thought it would be
Thank god I'm familiar with updater scripts
still cant get it to work. @artit you think you could modify this to run on our p769's?
http://forum.xda-developers.com/showthread.php?t=2508699
thasilenthacker said:
still cant get it to work. @artit you think you could modify this to run on our p769's?
http://forum.xda-developers.com/showthread.php?t=2508699
Click to expand...
Click to collapse
It's easier to port it to P768 because all I need to change is a firmware file. But for P769 you need to replace kernel so there maybe some incompatible issues. In AOSPA rom I also had problem when I replaced P760 kernel with P768 (from other rom). But when I build new P768 kernel for that rom it works.
I don't have P769 for testing so it's hard for me to port it to P769. Just wait for CM11 or maybe other ROM (AOKP/AOSPA). Most of its dev have paid a lot afford to new 4.4 version.
i am willing to be a tester if youd work on it, im online everyday
artit said:
The easiest way is
1. Replace kernel with working P769 kernel.
2. Replace all propeitrary files with P769 version. (You can have these files list from CM)
3. Add some more libraries (I don't know which files. I got brightness config doesn't working problem but I cannot solve it.)
I think that's all. Then you can add some customize to the rom. I used to port MIUI to P769 and that is what I did. But you may have some problem with some hardware library which is not in propreitary files list. It's an trial and error process but you need to have P769 to test it.
Click to expand...
Click to collapse
Has the brightness thing been solved yet? I am having this issue with a ROM that was "ported" but is incomplete because it completely lacks brightness control.
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