Database Info

[GUIDE] dsixda's Android Kitchen - Now supports SGS2 Skyrocket (Windows/Linux/Mac)

dsixda's Android Kitchen - Now for Samsung Galaxy SII Skyrocket
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S2 Qualcomm MSM8660-based (non-Exynos) custom ROMs. This also applies to the following devices:
AT&T Skyrocket
T-Mobile SGH-T989
Telus Galaxy SII X
Rogers Galaxy SII LTE
Bell Galaxy SII HD LTE SGH-I757M
Galaxy Note SGH-I717
IMPORTANT: If you have the original Galaxy SII GT-I9100 or its variants such as the Galaxy Note SGH-N7000, then click here to follow this other thread instead.
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 version 0.181, you can now create your own Galaxy S2 Skyrocket ROMs with the kitchen.
I'd like to thank twopumpchump (who owns an AT&T Skyrocket) and -Mr. X- (Telus Galaxy S2 X) for helping me out, as well as for testing on their devices and providing feedback. I only have a Bell Galaxy S2 I9100 so their assistance was greatly appreciated!
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
​
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S2 Skyrocket or equivalent with a ClockworkMod custom recovery.
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.
IMPORTANT: To verify your variant of the Galaxy S2 Skyrocket works in the kitchen, open your device's /system/build.prop file and check the ro.product.device value. If the value doesn't exist under the kitchen's tools/samsung_files/sgs2x_variants/ folder then just create a blank file there with same file name as your device's ro.product.device value.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S2 Skyrocket, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
system.img.ext4, tomb.img.ext4 (if it exists) and boot.img (and optionally: cache.img.ext4)
TAR file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4) NOTE: If the TAR file name ends with "MD5", remove the MD5 part from the name.
ZIP file containing system.img.ext4 and boot.img (and optionally: cache.img.ext4)
Custom ROM:
ZIP file created only by the kitchen from the stock firmware (NOTE: The kitchen may NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
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)
If you used a system.img.ext4 but then didn't include the cache.img.ext4, then you have the option to add a cache.img.ext4 later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
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 Samsung Galaxy S2 Skyrocket or equivalent SGS2 LTE devices in this thread!
Most of all, have patience, take your time and enjoy!!

Reserved...

Reserved ...

Nice work guys. Enjoyed cooking rims fir my g2 and mt4g with this. I know what I'm gonna be doing soon
Sent from my SGH-I727 using Tapatalk

now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium

Nice job on the guide I'm gonna sticky this, hopefully alot of people will learn how to cook their own roms for Skyrocket!

A must use for new people who wants to get their feet wet with deving
Sent from my SGH-I727 using xda premium

I will be playing w this during the weekend.
Thanks!

Oh yes, I will be having fun with this! As a non-dev this will be a great way for me to get my feet wet. Thank you!

saweeeeet!!

Thanks again for getting this set up.

I was about to post this last night but dozed off. Great stuff...!

Awesome! Much appreciated! Thought you were done updating this...nice surprise!

Cboss said:
Awesome! Much appreciated! Thought you were done updating this...nice surprise!
Click to expand...
Click to collapse
Yes I was done but felt I needed to put a stop to those persistent tweets/questions from the original SGS2 thread.

thanks so much!

Awesome, great to see this for SkyRocket. Now if we can cook from ICS sources, that had be amazing! I guess we will haev to wait till atleast Galaxy S2 gets ICS officially. Nexus S got it today, jealous!

kornklown69 said:
now we should have roms popping up everywhere
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
yeah, can't wait for those "roms"

Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.

Seannoxious said:
Is there currently a way to develop on top of a vanilla android rom? I personally don't like touchwiz or the carrier branded roms whatsoever. New to the development for this device so i am not exactly sure what's available.
Click to expand...
Click to collapse
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.

dsixda said:
Well, creating a custom ROM with the kitchen is not really development. You would need to compile the AOSP source code or a Cyanogen source to develop a vanilla ROM. The kitchen could be used afterwards to add other things to it like deodexing, root etc.
I have had limited success using the kitchen with a Samsung Galaxy S2 Cyanogen ROM, it depends on how complex the updater-script is. It did work fine on other devices like the Nexus S.
Click to expand...
Click to collapse
Understood i read some things on the cyanogen forums stating that they dont have plans to send out a skyrocket rom. They said that the att gs 2 is so similar to the international and the skyroxket using different chips for the blazay blazay blazay highly unlikely to develop a from for the skyrocket.
If he ports of a cyanogen are flakey and cm has no plans to support the phone BC of little demand or whatever do you know of anybody trying to pursue compiling a source code for the gs2 sr? I have Dev experience and would like to see more options for rooms. Not to discount the work that has already been done atall. I just personally love that vanilla feel. I also like launched pro and works much better in that environment from my experience.

DONT WANT A BRICK? Check here

As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.

thanks for the warning for the less experienced users, here's to making a rom kitchen to move roms between devices

I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482

incubus26jc said:
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Click to expand...
Click to collapse
Such greatness!

I appreciate the warning. I came close to flashing another ROM. Kind of we had our own forum not a subforum.

I would also like to add, do not use ES Note Editor (part of ES File Explorer) to edit build.prop. I made one tiny change and rebooted and the phone wouldn't go past the boot logo. The fix was easy enough, but I wish I took the time to edit it properly.

Are the root methods carrier specific? Sorry for the noob question. So I'd be able to root using a Heimdall method for the i9300 - I'm on a Mac.

xjedi said:
Are the root methods carrier specific? Sorry for the noob question. So I'd be able to root using a Heimdall method for the i9300 - I'm on a Mac.
Click to expand...
Click to collapse
Yes, methods are carrier specific, don't use the i9300 methods. As far as I'm aware, Heimdall doesn't work. If you know how to use adb then you can try this method:
http://forum.xda-developers.com/showpost.php?p=29175988&postcount=1
Otherwise you'll have to use bootcamp or some other method to get to windows.

s197 said:
Yes, methods are carrier specific, don't use the i9300 methods. As far as I'm aware, Heimdall doesn't work. If you know how to use adb then you can try this method:
http://forum.xda-developers.com/showpost.php?p=29175988&postcount=1
Otherwise you'll have to use bootcamp or some other method to get to windows.
Click to expand...
Click to collapse
Thanks. Yeah, it looks like Heimdall only works for i9300 not the VZW version. I'll probably just wait til I can borrow a PC laptop or someone comes up with a VZW Mac rooting method that's proven to work.

And while in the subject of being on the right development section...
Archangel, what's the difference between "Verizon S3 and android development" and "Verizon S3 ORIGINAL Android development"?
... I read the first one most of the time but why 2 sections?
The Archangel said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse

aqhilles said:
And while in the subject of being on the right development section...
Archangel, what's the difference between "Verizon S3 and android development" and "Verizon S3 ORIGINAL Android development"?
... I read the first one most of the time but why 2 sections?
Click to expand...
Click to collapse
Read my sticky in original development. XDA is trying to separate users that unzip a rom, toss in a few apps, then release it. Original development is for source built roms, cutting edge features(sense on Samsung S3, custom done ui. Etc) so users who want the best possible roms ASAP, without wasting time. It also helps shed light on those original roms

[Q] Are all these tutorials actually different?

Hi there. I'm getting into programming and hardware modding/hacking and have decided to use my phone as my first breadboard. After perusing XDA (and other sites, and youtube) for several days I am a bit hesitant before moving forward. I understand most of the terminology I've learned, however the tutorials for actually using the concepts seem to be all over the place, or, there appears to be several thousand ways of doing the same thing.
I am asking for confirmation that I have found the correct order of operations and tutorials for what I hope to do.
I would like to install Cyanogen 10.2 on my Verizon Galaxy S3;
Model: SCH-I535(.10)
Version: 4.1.2
***As a new user I am unable to post outside links. I have posted the google search that will bring you to the video in question as the first result.***
First, Root: "wccftech root-install-cwm-recovery-on-galaxy-s3-sch-i535-android-411-412"
Second, Upgrade to 4.2.2?: Do I need to do this? Or will Cyanogen 10.2 jump me right from 4.1.2 to 4.3. If needed, I will find the proper tutorial.
Third, Flash Cyanogen 10.2: "How To Install CyanogenMod 10.2 Android 4.3 Jelly Bean on the Galaxy S3!" (Making sure I use the verizon .zip) Specifically in this tutorial: He's using the Team Win Recovery Project. Many other tutorials do not use this. Should it be used? Is this a preference thing? Is it safer or simpler to use a different program or no program at all?
Fourth: Enjoy.
Thanks in advance!

[Q] Best Close to Stock KitKat ROM for Tab2

Hey Guys,
I'm quite a Noobie when it comes to ROMS and I haven't ventured into Custom ROMS in any way before. But, because in the infinite wisdom of Samsung (my one B!TCH) is they don't maintain support for older devices like Apple do, I need to consider updating my Tab 2 to get some decent performance.
There appears to be about 4 - 5 ROMS that are being regularly maintained and I'd like to know which one is as close to stock Samsung ROM and easy to install with no requirement to Root the device. I have installed ROMS via Odin quite a few times, so I am confident in that area.
Ones I know about:
SlimKat
CyanogenMod 11
Mokee
SOKP
Cheers and thanks
Willo

Please some help!

People aren't answering because what you're asking for isn't possible. None of them are like the Samsung ROM and they ALL require a custom recovery and root. You can't install them over Odin. If you do root then try them yourself and see which one works best for you. That's part of the fun of Android!
Not to mention you posted a question in the General forum not the Q&A forum...
http://forum.xda-developers.com/showthread.php?t=2699848
Sent from my Nexus 4 using XDA Premium HD app

Android Update for Galaxy Tab 2 10.1 - Suggestions and How-to

Hello everyone,
I'm new to this platform and to be honest a bit overwhelmed. Apologize if this thread is in the wrong section.
I should also mention that I'm not too familiar with technical points.
I own an old Galaxy Tab 2 10.1 (P5110) which claims its Android version 4.2.2 is still the most recent one for this device.
So I'm looking for a way to update to a newer versuon, at least Android 6.
My first question is which Android version you suggest?
Second one, how exactly do I do this (is there a step by step tutorial)?
Third one what are the risks? I read something about data loss and completely broken devices?
Thank you in advance.

Hi,
Please Check This Out :
[ https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim7-t3661612/post73520377 ]
Hope I Helped You !

André-1902 said:
Hello everyone,
I'm new to this platform and to be honest a bit overwhelmed. Apologize if this thread is in the wrong section.
I should also mention that I'm not too familiar with technical points.
I own an old Galaxy Tab 2 10.1 (P5110) ...
Click to expand...
Click to collapse
Mate, I'm on the same boat. Same tablet, also overwhelmed The only response to your post points to some custom ROM page but the instructions are not detailed. I thought I had to throw my tablet but it seems like it still has some life to breath if I can get it a newer ROM (many apps are not supported anymore with Android 4.2).
I think the first thing to do is root the device but where to start? I'd prefer using linux with adb, etc.
There is a lot of stuff here. Is there anyone that has taken the time to write a detailed step by step guide somewhere?
BTW, my intention is not only to revive the device but to ditch all Google crap apps. In an ideal world, I would have installed a ROM from /e/ Foundation, but they do not support the device so I guess my next best bet is some custom ROM that uses LineageOS?

Hi,
First you need to root your device and install TWRP recovery:
More info here:
https://forum.xda-developers.com/ga...final-root-single-step-twrp-recovery-t3404779
It's an old thread but you'll get the idea.
See this one as well:
https://www.getdroidtips.com/twrp-recovery-samsung-galaxy-tab-2/
You'll need to find the correct version for your model otherwise you'll and up with a nice paperweight.
After this, you'll be able to back up your current ROM and install new ones. Unfortunately, I have a different model of Tab 2 that has no available custom ROM's so I can't say which ROM is better than other. I would read more in the link provided for slim roms.
To get rid of the installed bloatware and even Google apps I used SD Maid. See my thread below with what's left on my tablet (Disclaimer: it's a barebone setup and not all things work so I don't advise going that deep unless you're willing to take the risk of having a bricked tablet. You were warned!):
https://forum.xda-developers.com/ga...recting-samsung-tab-2-10-1-att-i497-t4079993/.
Cheers!

More things for you to read:
https://forum.xda-developers.com/showthread.php?t=2203309

André-1902 said:
Hello everyone,
I'm new to this platform and to be honest a bit overwhelmed. Apologize if this thread is in the wrong section.
I should also mention that I'm not too familiar with technical points.
I own an old Galaxy Tab 2 10.1 (P5110) which claims its Android version 4.2.2 is still the most recent one for this device.
So I'm looking for a way to update to a newer versuon, at least Android 6.
Click to expand...
Click to collapse
You can take a look at my thread here, but you use at your own risk! It worked for me.
Complete Guide to Root and Update Samsung Galaxy Tab 10.1
Hi all. Complete noob here - just wanted to document my journey for resurrecting my daughter's Samsung Galaxy Tab 10.1 tablet to make it usable again. It had stock rom on it (android 4.0.4) ICS and would not update. Consequently, none of the...
forum.xda-developers.com