Several questions:
1. If I use gapps with AndDiSa's latest ADS_Magpie (ADS_magpie-20110510-signed.zip), does it require the newer version of gapps (GAPPS: 20110508b) linked on ezterry's page?
2. If the answer to 1 is yes, any special advice (definite DO's or DON'Ts)?
Some background:
Have used AndDiSa's ADS_Magpie on rooted G1 for a few weeks and have been very pleased with it.
Checked his page today at http://dl.dropbox.com/u/9870397/android/ADS_magpie/index.html today and saw he has a new version numbered 20110510.
Since it is based in part on ezterry's Gingerbread work (Source Code Repo for ezGingerbread development (Dream and Sapphire)), I've also been following that thread.
With ezterry's GINGERBREAD-DS-Alpha-20110509-1.zip, he includes a statement that reads "Starting this version you must use GAPPS: 20110508b due to the new Platform key in use." That is the reason for my question.
Thanks for your help.
If you do a no wipe install it should work without installing the new gapps due to the backup script included. I didn't have the chance to test it deeply, so I cannot guarantee.
If you do a clean install, the new gapps should work fine.
Sent from my Gingerbread on Dream using XDA App
Edit: Most likely it's more secure to erase system, then flash the rom and then flash the new gapps
Thanks, AndDiSa. I made a full backup (gapps, nand+ext) from recovery and flashed the latest - no problems.
Really enjoy GB with magpie on my G1, getting another 6 months with it will be much more satisfactory.
Thanks for sharing this with the community!
anyone can pelase share the ROM link with me for ADS_Magpie..
evertime i searched i got this LINK
Take the link from my signature ...
AndDiSa said:
Take the link from my signature ...
Click to expand...
Click to collapse
thanks...isn't there any forum for this...where u can post some screen shots and also that will be easily accessible... just a suggestion.
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
NOTE: This guide may also work for other Samsung devices. So if you were told to come here and you have a different device, it was not an error - just make sure you use a base ROM from your own device, not from the I9300! For all other Galaxy S3 variants, this guide might not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
I'd like to thank klander for testing and providing feedback, which is always appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE FOR MAKING YOUR ROM:
NOTE: If you have a non-I9300 device and were told to follow these instructions, then use a base ROM from that device, NOT a ROM meant for the I9300!! The same steps below, however, (and common sense) should be used.
First, you need a rooted Samsung Galaxy S3 I9300 with a custom recovery menu, which allows flashing of custom ROMs.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
Put one or more of your base ROM(s) under the original_update folder. For the Samsung Galaxy S3 I9300, there is support for the following formats (that I know of) which can be placed in that folder:
Stock firmware:
system.img, boot.img, cache.img (and optionally: modem.bin)
TAR/ZIP file containing the above. NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
OR Custom ROM:
must be a ZIP file created by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods such as CyanogenMod, due to potential file structure incompatibility issues)
OR Nandroid backup from custom recovery image:
system.img, cache.img and boot.img
system.ext4.tar, cache.ext4.tar and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
Root your ROM
Add Busybox
Optional: Disable boot sounds
Optional: In the Advanced options menu: De-odex your ROM (your mileage may vary as to whether this works 100%)
Optional: Add or remove the modem.bin from your working folder
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin. Make a Nandroid backup of your current system before you flash anything!
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers and to prevent confusion, please only discuss the Samsung Galaxy SIII GT-I9300 in this thread!
Most of all, have patience, take your time and enjoy!!
just what i need
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Are we still meant to be extracting the img files manually to get them working?
Kangburra said:
I have a de-bloat script if you want a copy to convert to a kitchen script. It's perl calling system values and the kitchen.
Click to expand...
Click to collapse
I'm not doing additional work, but if you'd like you could make a plugin for the kitchen, which would go under the /scripts/plugins folder and can be accessed from the Advanced menu of the kitchen. I can advertise it in the kitchen thread (in the plugins section) as a separate download under your name.
Are we still meant to be extracting the img files manually to get them working?
Click to expand...
Click to collapse
With Cygwin the kitchen will give you instructions on which program to open and how to use it (manually). The programs are found in the kitchen.
With Linux/Mac, it is all automated and very quick.
Just when I thought this kitchen was a goner, you came along and made it work again
I have just put the French zip into the kitchen and it fails to extract the img files.
Available ROMs:
(1) I9300XXDLIH_I9300VFGDLJ1_SFR.zip
Enter selection number (default=1, cancel=0, r=refresh):
Selected I9300XXDLIH_I9300VFGDLJ1_SFR.zip
The new working folder will be named WORKING_101712_171605
Change the name (y/n)? (default: n):
Creating working folder WORKING_101712_171605 ...
Extracting ROM ...
Error: No system folder found!
Press Enter to continue
Click to expand...
Click to collapse
It works after manually extracting so no big deal
Kangburra said:
I have just put the French zip into the kitchen and it fails to extract the img files.
It works after manually extracting so no big deal
Click to expand...
Click to collapse
If the zip contains a tar file then it's not going to work, you need to unzip the tar file.
The best tool for deodex Roms!
THANKS dsixda! :good:
Regards
adesirello (AndyX ROM)
Awesome job mate :good:
tomorrow`s homework !
thanx !
Perfect! Just two days ago i was think at dsixda kitchen! I don`t have enough thanks for this!
Great.
Just what i was looking for.
dsixda said:
dsixda's Android Kitchen - Now for Samsung Galaxy SIII GT-I9300
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII GT-I9300(T) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I9300 ROMs with the kitchen.
IMPORTANT: For all other Galaxy S3 variants, this guide may not be exactly the one you're looking for. There may be support for your S3 device in the kitchen, but I'd need to post different instructions. Check the first post of the kitchen thread for any updates for linked instructions.
Click to expand...
Click to collapse
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
L335K1 said:
just wanted to let u know that when cooking my rom with ur kitchen, awesome by the way, i was getting constant hang at logo on boot. i went back to the beginning as it worked and booted and just added bit by bit until i found the issue. the issue was adding busybox install run parts. it took me a day to figure this out. i went through kernel to framework and nothing fixed this issue where booting just to logo then stuck. finally deleted working folder, went back to a basic rom, slowly added root, then busybox, deodex etc. i dont know if this issue is specific to just me and my particular build but just putting it out there for others wanting to use this excellent kitchen on their i9305.
Click to expand...
Click to collapse
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
dsixda said:
Did you create a /system/etc/init.d folder with your custom scripts after enabling the Busybox Run-parts? That option is quite old but I have not seen anyone try or test it with any of the Galaxies. Maybe when you have time next time, do a logcat while it boots and see what the problem is (assuming you had the init.d folder created already). Thanks
Click to expand...
Click to collapse
yea i created the init.d folder first, (using v29 so it gives u warning anyways), but it still does this. i have to add init.d support manually through my script. but this is awesome, i just gotta remember not to use that feature.. i did both logcat and recovery logs but couldnt make heads or tails of it. it was easier to go back through ur kitchen, add 1 feature at a time until i found the culprit. thanks heaps
Please link to download the kitchen, thank you very much.
misacek said:
Please link to download the kitchen, thank you very much.
Click to expand...
Click to collapse
First post.
This is great!
Thanks dsixda.
YZ.
Please not see me? can give direct link? thank you very much
misacek said:
Please not see me? can give direct link? thank you very much
Click to expand...
Click to collapse
If you refuse to or are unable to read post #1 then you'll have trouble using - and even installing - the kitchen.
Can anyone give a hand to teach me compile and configure AROMA? :n00b: xD
Refer existing ROMs with aroma in it to get a feeling of it and also see the atoms thread for usage instructions
I download last mith rom and reework aroma to fit to the one i try to compile witch his stock gb. I think i done all right but when i tried to flash gave an error (status6) and abort. What i did wrong?
Hey guys, a good while ago I made a guide on how to build your own LineageOS ROMs. I've since updated it several times and made a tutorial video of the entire process to accompany it! I hope some of you will find it useful
Here it is: https://goo.gl/uU0fCy
Also, you can see the youtube tutorial video that accompanies the guide here:
https://youtu.be/m55tUzD7LLo
(There is a banner ad on the tutorial link and it'd help me out a little if you used this one. But you can use the direct link below if that's what you prefer :L )
https://goo.gl/uU0fCy
Enjoy
So I have been following the [ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way Guide. It worked great until:
Download Recommended default setup
Rom:cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
I keep getting the same error of unrecognized/unsupported zip for all 3. I am using Touchpad Toolbox (v42 2015-01-08)
please any help would be amazing.
Q
nikig04 said:
So I have been following the [ROM GUIDE]How to install Android 5.x.x/4.4.x with Jcsullins TPtoolbox Super Easy Way Guide. It worked great until:
Download Recommended default setup
Rom:cm-11-20151116-SNAPSHOT-jcsullins-tenderloin.zip
Recovery:TWRP-jcs-dm-tenderloin-20140612b.zip
Gapps:gapps-444-base-20160602-1-signed.zip
I keep getting the same error of unrecognized/unsupported zip for all 3. I am using Touchpad Toolbox (v42 2015-01-08)
please any help would be amazing.
Click to expand...
Click to collapse
Hmmmm, those ZIP look like they should work with the regular method, but here is my comment.....
I was actually going to install this same KitKat ROM on one of my three tablets, right now I have 2 tablets with Nougat and one tablet with 4.4.4 MLQ, but Nevertells2 gave me a good idea on another forum to install 4.4.4 JC Sullins like yours above, because Nougat is sluggish and has a microphone bug that Nevertells2 would say is a "deal breaker" with Hangouts.
So anyway to make a long story short, try the alternate method below and use your ZIP from above ( not Nougat zips ). I am going to do it this weekend and we can compare notes on how it worked. I am going to use the exact same ZIPS as you.
Click here for Alternate method to install KitKat