Related
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S 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 version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[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 S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
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 (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img 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 factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
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 S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame
Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game
Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app
Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game
Hello Wildfire S users !
Here is the guide of the Marvellous Team, the ultimate guide that describes everything you need o play with your phone. There are many tutorials on the web about how to unlock, how to install a recovery or a rom, but none of them explains all these operations. So here, you'll learn first a few things about how Android works, you'll learn a few words of vocabulary, how to unlock, how to choose the best recovery and how to flash it, how to choose the rom you'll prefer and how to ask questions and report errors.
I just say, sorry if this tutorial lacks vocabulary and is not grammatically correct : I'm not English, I'm French, and I'm not really good in English
SUMMARY
Post #1 : Explanations, disclaimer, summary
Post #2 : Unlocking process
Post #3 : Choosing and installing your recovery
Post #4 : Choosing and installing your ROM
Post #5 : Good rules when using the forum, how to help the developer
DISCLAIMER
I am not responsible for anything that can happen to you or your phone. Everything that I say in this tutorial worked for me, and if you do everything as I say, there is no reason for you to brick your phone.
If something happens to your phone, do not even try to blame me, cause I will redirect you to this disclaimer and laugh at you
SOME EXPLANATIONS ABOUT ANDROID
Okay, let' start unlocking your phone. But do you know exactly what unlocking your phone means ?
Here are some explanations about how Android works.
First, when you power on your device, it will start the bootloader. This is like the BIOS for a PC : it checks the processor, the RAM (memory),, and it launches the system. You don't see anything at the screen when it boots, because it is quite fast. You can boot into bootloader without going to the system next by pressing Power + Volume Down (you'll maybe have to remove and replug the battery before doing that).
What's the point of booting into bootloader ? You can go then into fastboot and recovery. Fastboot is a tool that will allow you to flash some things on the unlocked phone, like another recovery, or another kernel.
The recovery is the tool you'll use the most when playing with your phone : it is like a micro-system that can modify the real Android system. For example, it is the tool you'll use when flashing roms : you can't modify the system when you're already into the system ; if you delete all Windows system files to replace them with other files, your system will crash and your PC will not boot
I spoke about the kernel. The kernel is launched by the bootloader ; it will load all the modules that are necessary for Android to work, for example the touchscreen driver, the RAM allocator, and alll. You can see when the kernel is working at boot because you have HTC written in green over a white background.
You'll need to know that for the next steps of the tutorial.
CREDITS
The Marvellous Team : djolivier, thehacka1, Kevinjoa, Mazer.one
simonsimons'34
All the Wildfire S devs, and especially benjamingwynn, dudeman, OliverG96...
And many more I forgot !
This tutorial has taken quite a long time to write, so please press thanks if you think I deserve it
SUPPORT
As you may have heard, the Marvellous Team is about to end. thehacka1 and djolivier already have new devices. Mazer.one, Kevinjoa and I will probably get new devices soon (maybe in few months for me, I still hesitate between Galaxy Note 2 and Galaxy Mega).
I will however still maintain this thread, reading the answers, modifying what needs to be modified, etc. If you see I do not reply, don't worry, I'm certainly overwhelmed by work (I entered the French equivalent of college this year and I must work a lot) I will surely read your question and answer it, even if it isn't immediately. Moreover, other people of the forums will certainly answer you too
So, let's unlock your phone !
Unlocking your phone allows you to bypass the protection on the recovery and system partitions that HTC put. With an unlocked phone, you can use fastboot to flash a recovery (because the original recovery doesn't allow the user to flash anything).
Be careful ! Unlocking doesn't give you access to everything ! You can't modify the bootloader, the radio (part of the system that manages communications with network) and all the important thins of the phone. To modify these, you need to get S-OFF, and that's another problem
WHAT IS YOUR MODEL ?
There are several models of Wildfire S. The most common are marvel and marvelc. To know if you are marvel, just go intoo About phone section, you should find your model name. If it is A510e, it is marvel. If it is A510c, it is marvelc. This part of the guide is made for marvel, do not try to do these steps with a marvelc ! But the part with the choice of your rom and how to report bugs is okay for both models.
If you have a marvel, you maybe have a 2012 model. You can know that with your serial number, that should be also in the about phone section. You should have something that begins with two letters and then you should have a digit. If this is 2, you have a 2012 model and may have some problems with the unlocking process. Go directly to the part HTC Official Unlock.
INSTALL HTC DRIVERS
To unock your phone, you'll need your computer to recognize it. The best way is to install HTC Sync which automatically provides HTC drivers.
You can find HTC Sync here.
You can also download only the drivers, for example the Win7/8 64 bits version with this tutorial.
UNLOCKING WITH SIMON'S HTC UTILITY v4
So, if you have a marvel, AND NOT A 2012 MODEL, I propose you to unlock it using simon's HTC Utility (it should work too with marvelc, but I didn't test). This tool can be found here. This is pretty easy to use, even if you'll need the .NET framework to launch the program. If you do not have a marvelc, use only the unlocking feature !!!
HTC OFFICIAL UNLOCK
If you have a 2012 model, or if HTC Utility doesn't work for you, you can always try HTC Unlock method. It will work 100% but you will lose your warranty AND all your data. So, before doing anything, download SMS Backup & Restore and Super Backup and make a backup of everything.
Then go to this page, select your device and start the procedure.
Here is a guide written by @Uksus17 and translated by @niks255 :
0. Check your bootloader version in fastboot:
- If you have HBOOT 0.90.0000 - start with step 1.1.
- If you have HBOOT 1.09.0000, 1.08.0000 (or 1.03.0000) -
download and flash PG76IMG.zip via fastboot.
- If you have HBOOT 1.09.0099 - start with step 3.
1.1. Download this zip and put it to your SD card. (http://d-h.st/QwN)
1.2. Reboot your phone into bootloader (VolDown+Power) and when the checking is done press VolUp to install. After installation you must remove this file from your SD card before you continue.
2.1. Do steps 1.1 and 1.2 again with this second zip (it has the same name as the previous, but it's a different one) PG76IMG.zip. After all these steps you must have HBOOT 1.08(9).0099, which can be unlocked. (http://d-h.st/kGN)
3. Download and unpack Android.zip to your C:\ drive.
4. Make sure "USB Debugging" is checked. If it is, connect your phone to PC via USB and run Unlock.bat from Android folder on your C:\ drive.
5.1. Your phone will reboot into fastboot.
5.2. Now you will have htcdev.com opened in your browser. Now you need to register there. (Do not close command line!)
5.3. Confirm your email.
5.4. After you done step 5.3, go back to htcdev.com and log in.
6. Then go back to command line and press Enter. You must select the token the way it is selected on the picture below and copy to clipboard. DO NOT CLOSE COMMAND LINE!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. Go back to your browser, scroll to step 10 and paste your token in form, then click submit.
8. After a while you should recieve Unlock_code.bin on your email. Save it to C:\Android.
9. Go back to command line and press Enter.
10. Now choose yes using volume buttons and power button. CAREFUL ! this operation wipes all data on internal memory, for the second time pleaase make sure you made a backup !!! (it doesn't wipe the sd card).
Good. Now, your bootloader should print *UNLOCKED*
Now let's do he real part of the job, what this tutorial has been made for.
CHOOSE YOUR RECOVERY
The choice of the recovery is very important. For the Wildfire S A510e, there are a lot of available recoveries :
ClockWorkMod 5, 6 and 6 Touch Version
TWRP 2.2.2.0 and 2.3.3.0
OWL-mod 0.1.2 (based on ClockWorkMod).
These recoveries usually are also available for non-marvel models, you can find a link to the other versions in the thread. But DO NOT TRY TO FLASH ON YOUR DEVICE A RECOVERY THAT ISN'T MADE FOR IT ! Meaning, if you want to try ClowkWorkMod 6 Touch Version, but you have a marvelc, do not flash the marvel version. Look for the marvelc version of the Internet. You could brick your device doing this
So, every recovery has a lot of advantages and also a lot of drawbacks. I will list them here.
CWM 5
It can be found here.Take the Wildfire S CDMA version for marvelc.
It is a good recovery, usually the one that everybody use. It is not a touch recovery, so you'll need to use it with volume keys and power button.
It doesn't have amazing features, but is official and working.
CWM 6
This is the newest version of ClockWorkMod recovery. It is better than CWM 5 : support of incremental backups, lighter and faster backups, new interface, etc.
You can find it here.
This one is pretty well working too, although it is not a touch recovery and even if it is not official.
CWM 6 Touch version
Like CWM 6, but using the touchscreen : better for the power button which is not made for a huge use.
The problem is that this one isn't very stable : some features do not work, the screen is strangely sized. Use it only if you want to try, but not if you just want stability.
You can find it here.
TWRP 2.2.2.0
It is another touch recovery, open source and absolutely different. It is less used and is perfectly stable. It has many more features than CWM, especially a file manager (very, very handy when you want to mod some system things without your PC).
I love it, but there is just one problem with the backups and restores : they take (for me at least) 5 more time than CWM ones. If you do not often backup/restore, that is OK, else you'll quickly get bored of waiting 30 minutes before flashing your rom.
TWRP 2.2.2.0 can be downloaded here.
TWRP 2.3.3.0
This was the latest version of TWRP available for the Wildfire S. You can download it on this website.
It is better than TWRP 2.2.2.0 but has a major problem : it cannot flash some old files. That's quite annoying when you want to try a rom and you see you can't because the rom zip file is too old :/
TWRP 2.7.0.0
This is the latest version of TWRP, built by @Olivier for our phone. It is definitely pretty cool, has loads of features and nearly no bugs. You can find it here : http://forum.xda-developers.com/showthread.php?t=2692158.
Like TWRP 2.3.3.0, it cannot flash some old files :/
OWL-mod 0.1.2
This recovery has been made especially for the Wildfire S. For now, it is pretty like CWM 6, with a few mods. But the next version looks very interesting
Here is the thread.
PhilZ recovery 6.0.2.8
Here is PhilZ recovery, a recovery which looks very much like CWM 6.0.2.8 but has some nice features. Here is the non-touch version : http://forum.xda-developers.com/showthread.php?t=2605331.
Then, I let you choose, try some of them and see by yourself
FLASH YOUR RECOVERY
That's easy if your bootloader is unlocked.
Download Android SDK here. Extract everything, and open cmd (Start menu - Execute - cmd). Then, in cmd, navigate to the repository you extracted everything (cd path\to\directory). Then, in this directory, go to sdk\plaform-tools.
In this folder, place the recovery file you downloaded.
Now, reboot your device in bootloader mode. Then go into fastboot. If the device is recognized you should see USB Plug on the screen.
You can now type
Code:
fastboot.exe flash recovery your_recovery_file_name.img
and voila ! You should see a loading bar on the screen, and you can reboot into recovery
THE BEST FLASHING TOOL
@Uksus17 made a pretty nice tool to help you install a recovery : just make sure USB debugging is enabled in your phone's settings, then connect it to the computer (of course, with the drivers installed - see before) and just run the .bat
You can find the script here : https://www.dropbox.com/sh/nuf2pq3ay9eu7xk/7gtYOs07EN
WINDOWS 8.1
On Windows 8.1 the fastboot drivers do not work. Thus you have to use another way to install the recovery : PG76IMG. The recovery will be downloaded as a zip file that you will put at the root of your sd card. Then just reboot into bootloader (vol down + Power) and it will flash it automagically @niks255 made PG76IMG for TWRP 2.2, 2.7 and CWM 6.0.4.8. You can find it here : 2.2, 2.7, 6.0.4.8
Now, you have your recovery... Let's speak about ROMs !
WHERE TO FIND YOUR ROMS
All the ROMs for the Wildfire S are here. You'll see, there are loads of ROMs for our phone
HOW TO CHOOSE THEM
Ah, which ROM is the best... An endless debate in XDA forums !
By the way, many "noobs" post threads to know which ROM is the best, and it annoys a lot the Senior users. Here I will list the existing kinds of ROMs and what they are made for, so that you won't have to spam the forum anymore
Stock rom
There are a lot of modded stock roms. The most advanced is by @Kevinjoa, and it can be found here. Moreover, it is a Marvellous rom !!!
Advantages : Very, very fast and an excellent battery life. Easily moddable and themable.
Drawbacks : Old Android version (2.3.5 ).
Sense 3.5 rom
These roms are based on the same Android version as stock rom, but with the latest Sense version (for Android 2.3). The fastest rom for the Wildfire S is EQDKP 5.2. There is also Marvellous Sense 3.5, and many other roms.
Advantages : Very fast, and good battery life. A very beautiful UI.
Drawbacks : one or two bugs. Old Android version (2.3.5).
CyanogenMod 7.2
CyanogenMod (cm) is the ultimate rom for all phones. It is based on pure Android (AOSP) and has a few more good features.
Advantages : very fast and an excellent battery life. Some mods that makes you forget that you have an old Android version : notification swipe-to-clear, flac support. Very themable : a lot of versions exist in the forum, modded to look like Sense 4, and all.
Drawbacks : a few bugs. Old Android version (2.3.7)
CyanogenMod 9.1
This is the Android 4.0.4 version of CyanogenMod. It is an excellent rom.
Advantages : Android 4 ICS. Very themable and moddable.
Drawbacks : it slows down the phone and has some bugs.
CyanogenMod 10
This is the Android 4.1.2 version of CyanogenMod, and is also a very good rom. Many versions exist in the forum, with a lot of mods and some derivated os.
Advantages : Android 4.1 Jelly Bean. Very themable and moddable, with many derivated versions.
Drawbacks : few space in /system, so you can't install full Google apps (see later in the tutorial). It feels slow sometimes. It has some bugs.
CyanogenMod 10.1
The 4.2.2 version of CyanogenMod.
Advantages : supported by OWL team. Android 4.2.2 Jelly Bean. Very themable too.
Drawbacks : very few space in /system. Also it is definitely slow. And it has bugs.
CyanogenMod 10.2
The 4.3.1 version of CyanogenMod.
Advantages : supported by Team Simplicit. Android 4.3.1 Jelly Bean. Very themable too.
Drawbacks : Well, there are very few features compared to CyanogenMod 10.1 And very few space in /system. Also it is definitely slow. And it has bugs, mostly sensors and camera.
CyanogenMod 11
The 4.4.2 version of CyanogenMod.
Advantages : supported by Team Simplicit. Android 4.4.2 KitKat. Very themable and has few bugs. It is faster than than previous versions thanks to Android optimization.
Drawbacks : There is few space in /system, and camera doesn't work.
Paranoid Android
Paranoid Android is a rom based also on pure Android but without cyanogenmod modificactions. We have two versions : Android 4.1 and 4.2. Both have bugs. The interesting features are in the per-app personnalisation feature : you can choose the size of each app, apply some statusbar colors per-ap, etc. Paranoid Android 3+ (Android 4.2) also has Pie feature and Halo.
Advantages : per-app functionnalities. Halo and Pie.
Drawbacks : bugs. Less features than CyanogenMod. few space in /system
MIUI
If you're a nostalgic of Sense, MIUI is for you. We have MIUI based on Android 2.3, 4.0 and 4.1. It is Android modded to be more beautiful.
Advantages : very beautiful UI.
Drawbacks : slow, and only in English.
AOKP
AOKP is based on pure Android and offers some new features like CyanogenMod. We have AOKP 4.0, 4.1 and 4.2.
Advantages : good personnalisation features.
Drawbacks : bugs and few space in /system.
AOSP
AOSP is the very pure Android with no bonus features.
Advantages : The one we have, by @thehacka1, is very fast.
Drawbacks : few space in /system, no CyanogenMod features.
PAC-man
PAC-man is the ultimate rom for people who want loads of features, or basically for those who do not know which to choose between CyanogenMod, AOKP and AOSPA (Paranoid Android). It offers features from all these three roms.
Advantages : so many features ! Android 4.2
Drawbacks : No camera. For me, extremely fast battery drain.
OmniROM
A modded AOSP 4.4.2 KitKat.
Advantages : supported by Team Simplicit. Android 4.4.2 KitKat. Has a lot of nice features. It is faster than than previous versions thanks to Android optimization.
Drawbacks : There is few space in /system, and camera doesn't work.
The best way to choose your rom is to test all of them. But you certainly don't have time for that.
If you want performance, choose Sense 2.1/3.5 or cm7.
If you want a good UI, choose Sense 2.1/3.5 or MIUI.
If yu want the latest Android, choose cm10.1 or AOKP 4.2
If you want a lot of features, choose PAC-man
And remember : you never need to flash any kernel except if the rom developer tells you so ! The rom already contains the good one
GOOGLE APPS
When you've downloaded a rom, you'll also need to download google apps if they are not installed. They are installed in Sense and MIUI roms, but not always in other roms (the hread usuallly says it).
You can find the gapps package for your Android version at goo.im/gapps - only for Android < 4.1. For Android 4.1 use these lite gapps, and Android 4.2 use these ones. Sometimes, a link to gapps is provided in the rom thread. Use this link instead of mine.
HOW TO FLASH
Just put the rom zip and the gapps zip in your sdcard, boot into recovery, make a backup, wipe data, cache, dalvik cache, system and sd-ext (if you can) and select install zip from sdcard then go to your rom zip and flash. After that flash your gapps zip without any wipe.
Yoou can then reboot. Be careful, it can take some time.
INCREASE INTERNAL MEMORY
As you may have seen, the stock rom has very few space for apps. You can increase it with Int2Ext
First you must partition your sd card. You can use a tool like gparted. Reduce the size of the existing fat32 partition and create a new partition in ext4 format. Note : make sure you've done a backup of your sd card data ! This will erase all data on your sd card.
Then you can go to this page and choose the script that is made for you. Flash it right after gapps without any wipe.
In my mind, Int2ExtV2+ is the best. But it needs 150 MB of storage for 500 Mb of ext4 partition. Int2Ext or Int2Ext4 do not need that, but will slow down the phone a lot, even if you have a good sd card.
ABOUT BRICKING YOUR PHONE
A lot of people, when they start playing with their phone, are afraid to brick it, meaning that it doesn't work anymore and can go straight to trash. That is normal, I was thinking that too But the risks are very low. If you are not S-OFF, it is difficult to brick your phone. I flashed more than 150 roms, installed kernels that didn't work, change 10 times of recovery and I never experienced a brick.
There are two kinds of bricks : softbrick and hardbrick. If your phone is softbricked, you can still go into recovery, wipe everything and install a new rom. If your phone is hardbricked, hmmm... there are very few chances of recovery, because it doesn't boot anymore
Let's talk about support now !
WHERE TO POST A QUESTION
It is easy : when you have a problem with a rom, post it right in the rom thread. Do not create a thread in General section with your problem. If you can't post in the rom thread, or if your problem is very specific, or just if nobody answered you in the rom thread, then post in Q&A section. NEVER IN GENERAL ! general sections is for threads that are not about a mod, a rom, a kernel, a recovery, an accessory or a question. For example, this guide
When you have a problem, people will often ask you to give them a logcat. But what is it ?
HOW TO LOGCAT
The logcat is the command that gives you all the informations about the system in real time, errors, warnings, or just debug info. When you have a problem and if you create a post or a thread about it, try to provide a logcat. This is easy !
In cmd, navigate to the repertory where fastboot.exe was. Plug your device to your computer. Usually Android debug is activated by default, you can verify in your phone's parameters. It depends on the Android version, but for Android >= 4.0 it is in Develper tools and for Android < 4.0 it is in the app menu, in the development section.
Now type
Code:
adb logcat
: you should see a lot of text. Don't worry if you understand nothing ! Just give everything to the people who ask you for the logcat. Then follow their instructions
Advice by @csoulr666 :
For a better and cleaner logcat you can do
Code:
adb logcat -v long
And if you want to put it in a text file
Code:
adb logcat -v long >logcat.txt
Then just upload the file It is easier to read and doesn't spam the thread (very difficult to scroll when you're on your phone ). Moreover with that you do not get into troubles with the character limit.
Just a precision about Android >= 4.2. You can't logcat on first boot, because of a new thief-protection feature. You'll need to boot, to plug the phone to the computer, make sure you have the latest adb installed (adb version - it must be 0.1.31 or more) and when you try to connect to the device, a popup will appear and prompt for adb access. Reply yes, and check the remember box, and now here you are, yu can logcat with this rom !
If you still want to logcat on first boot, you can use this guide (thanks to @thehacka1 !).
RESPECT THE DEVELOPER
A rom developer is a human being He has the right to sleep and to work and to have fun ! Do not ask for updates of the rom everytime, and don't bame him if he disappears from the thread for a few days... The more you ask for updates, the less he wants to make them
Do not forget to press thanks button when you think the dev deserves it ! Do not just post "thanks"
As you may have heard, the Marvellous Team is about to end. thehacka1, djolivier and Kevinjoa already have new devices.
Click to expand...
Click to collapse
I haven't got new device yet
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 04:30 PM ---------- Previous post was at 04:30 PM ----------
Good guide btw :good:
Sent from my Nexus 7 using XDA Premium 4 mobile app
I literally thanked every one of your posts :laugh:...........This thread will actually sort out many noobish threads(provided they read this first)
I hope this is stickied or atleast kept on the first page so that your time consuming work doesn't go in vain
I would actually like to contribute a bit.......for a better and cleaner logcat anyone can use the following command
adb logcat -v long
Click to expand...
Click to collapse
And if you want to put it in a text file
adb logcat -v long >logcat.txt
Click to expand...
Click to collapse
csoulr666 said:
I literally thanked every one of your posts :laugh:...........This thread will actually sort out many noobish threads(provided they read this first)
I hope this is stickied or atleast kept on the first page so that your time consuming work doesn't go in vain
I would actually like to contribute a bit.......for a better and cleaner logcat anyone can use the following command
And if you want to put it in a text file
Click to expand...
Click to collapse
Thanks for your feedback
I add your logcat advice !
izi501 said:
Thanks for your feedback
I add your logcat advice !
Click to expand...
Click to collapse
For logcat you also need your device's drivers. And don't forget 4.2.2 can't be logcated.
thehacka1 said:
For logcat you also need your device's drivers. And don't forget 4.2.2 can't be logcated.
Click to expand...
Click to collapse
Device drivers have already been installed if you unlocked your bootloader And 4.2.2 can be logcated, it just cannot be at first boot... But you're right, they may need to logcat on first boot. Could you please give me the link of your tutorial to get ADB working on first boot on 4.2.2 please ?
izi501 said:
Device drivers have already been installed if you unlocked your bootloader And 4.2.2 can be logcated, it just cannot be at first boot... But you're right, they may need to logcat on first boot. Could you please give me the link of your tutorial to get ADB working on first boot on 4.2.2 please ?
Click to expand...
Click to collapse
An alternative to device drivers is HTC Sync but that is a big hassle. Here is the link: http://forum.xda-developers.com/showthread.php?t=2296632
thehacka1 said:
An alternative to device drivers is HTC Sync but that is a big hassle. Here is the link: http://forum.xda-developers.com/showthread.php?t=2296632
Click to expand...
Click to collapse
I provided link to drivers and HTC Sync Thanks for the tutorial ! I add it immediately.
Anybody knows where I can find SIMON'S HTC UTILITY? I cant find working link anywhere!
denis022 said:
Anybody knows where I can find SIMON'S HTC UTILITY? I cant find working link anywhere!
Click to expand...
Click to collapse
Windows - Linux - Post with links
Must admit this is a great tutorial good job
I have unlocked my bootloader but after flashing and going into recovery there is no response by the recovery....cwm and twrp both not responding
I have a 2012 model a310e hboot 1.09 and I have s-off... It was s-off when I got it.
Sent from my HTC Sensation using XDA Premium 4 mobile app
yasir4abbas said:
I have unlocked my bootloader but after flashing and going into recovery there is no response by the recovery....cwm and twrp both not responding
I have a 2012 model a310e hboot 1.09 and I have s-off... It was s-off when I got it.
Sent from my HTC Sensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm... if you have a A310e you're in the wrong forum mate You have a wildfire, not a wildfire s !
But if you have 2012 model, it is possible that you need to try another recovery... you tried all of those I proposed in the guide?
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
izi501 said:
Hmmm... if you have a A310e you're in the wrong forum mate You have a wildfire, not a wildfire s !
But if you have 2012 model, it is possible that you need to try another recovery... you tried all of those I proposed in the guide?
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
Click to expand...
Click to collapse
Sorry it is an A510e...and I gave tried two recoveries twrp 2.2 and cwm nodded for 2012edition non are responding to touch...
Sent from my HTC Sensation using XDA Premium 4 mobile app
yasir4abbas said:
Sorry it is an A510e...and I gave tried two recoveries twrp 2.2 and cwm nodded for 2012edition non are responding to touch...
Sent from my HTC Sensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You could try cwm 6, or owl mod... I must say, as I do not own a 2012 model, I don't know which recovery works for them
Envoyé depuis mon HTC FeuSauvage S avec Tapatalk 4 now Free
Marvellous CM10 - RELOADED
Thanks man fr yr ROM: Marvellous CM10 - RELOADED(I hit he button).
(Maybe not the right place, but thanks :good::good::good::good::good::good::good:
I use yr rom fr three days, very good battery and very stable. no problems.
Installed like in OP3 from thehacka1 and Installed INT2EXT+ and format /sd-ext.
Made it personal: deleted viper4android / seeder / wallpaper / filemanager and installed: ES file explorer / acalender / ROM Toolbox.
Camera/camcorder could be better.
Woooooow
[Q&A] [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Q&A for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV][OTA] CyanogenMod 11.0 Galaxy 551/Callisto (GT-I5510) Port [androidarmv6]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ansh2000 said:
result is same as before.
Click to expand...
Click to collapse
TWRP 2.6.0.0 and ClockworkMod v6.0.5.3 upload pls.
can't install it
Hi ! I need help with this installation procedure, cause i put the code on the terminal emulator, and then, my cwm is deleted.. I want to try this cm rom ! Please help !
Problem with recovery
I didn't have problems before with installing any rom or recovery, I think I've passed through all of possible combinations, but this time, it's terribly buggy :/
I started from stock rom 2.3.6 XEO (as always) then installed CWM Custom Recovery "CWM-5.0.2.8_GAZZY.tar" (need some cwm to update, right?) but stock rom didn't find "flash_image" just like few other roms (arkas for ex.)
Finally Burnmode's KitKatSpecialEdition didn't alert about anything missing and it just jumped to the next line. (success I think, right?) The problem is that when I reboot into recovery it flashes a blank, black screen and reboots leaving my phone recovery-less ! What do I do wrong? Since then I tried many roms and most of them don't work anymore (no luck with cm10.2 for example, KitKat special edition works, so it's the only thing I can now run without bugs, but it's BurnMode's rom, it always works well)
I downloaded recovery.img "2014-12-04 22:43:18" which is the newest (at least now!) is there a problem with the recovery, my phone or maybe I am doing something wrong? My options are now very limited since many things crash my phone (can't flash a stock rom anymore, might be hard to do it again)
Hi
Thanks for your great work. I updated my cooper (s5830) to the latest release but my device won't boot. So I return back to the previous version.
For totoro??
Hi Sir, Im on Galaxy Y s5360 , no possibility for our totoro device?
Help!
help me when i'm trying to download cwm on github is error that i'm missing the Overall/Read permission. How can i fix it? Help
recovery
I couldnt download u recovery, u wot m8 with it i havrnt got perms, upload it normal or get REKT
Can we expect working cm12 on our devices? Or this is the end of the unofficial support?
The page is closed now. Is anybody known how long will be unable to download ROMs on this page? Are there any other links in which we can get RC14 for Callisto? Thanks for help!
Updates? LinkS?
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
anasahmad17 said:
Hi, are there any updates for Callisto?
Whats the last stable build for daily use?
LInks?
Click to expand...
Click to collapse
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
steve8x8 said:
No more development since Feb '15 (http://forum.xda-developers.com/showpost.php?p=58590015&postcount=261), last version seems to be
Code:
[...] 112913587 Feb 11 18:56 cm-11.0.0-GT-I5510-callisto.zip
and the server hosting the images has gone (http://download.androidarmv6.org/_builds/callisto/).
You may try to find a copy of the zip, check the md5sum (mine is 37c0f0fadb2f0d7444a175e42b78a84a )
Please share your findings.
BTW, 11.0-20150211 (that's how it identifies itself) is quite responsive once you've changed the CPU governor and IO scheduler settings ("Performance" menu in Settings, I'm using SmartassV2 and Deadline. Only tick "Set on boot" after a while of testing, I have seen some particular settings freeze the phone!)
Click to expand...
Click to collapse
I tried finding the rom and the only one i could find on the inter-webs is here but the website is paid one so i cant download and i cant check the checksum
http://chomikuj.pl/kaktus47/Telefon....0.0-GT-I5510-callisto,4616249982.zip(archive)
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Prerequisites:
You must have flashed CWM6 using Odin before.
Also you need a second partition on your sdcard, formatted as ext4.
Preparation:
Put the files you need on the sdcard (normal vfat partition), shut down the phone.
Charge the phone's battery.
Now the really tricky stuff (if you mastered Odin, that's just a piece of cake though):
Start the phone into recovery.
Flash the ROM image, and wipe data.
Boot into Android, install and setup s2e to use the sd-ext partition.
Reboot into recovery.
Flash the gapps package, and possibly one of the keyboard zips (see http://forum.xda-developers.com/showpost.php?p=56625731&postcount=162 for those). You may have to switch off package checks in between.
Reboot into Android, and change your governor and io scheduler settings.
Done.
Edit: I've got requests to share the filespace - which should be accessible by link. I'm re-adding the URL now. Apologies to everyone who tried in vain
@steve8x8 Hi, I know it's been a long time but i hope you see this, but could you please be more specific with the steps? what files to use, what keys to press? Sorry it's been a while since i used this phone or any android phone, what odin version should i use?
Have you searched the 'net (and the archive.org) for the original 551 blog? It has/had a quite good explanation of almost everything related to this particular phone. Odin version doesn't matter much, I had used 4.34 (that was current when the instructions were written) and 4.43 IIRC, no difference. Make sure to get good instructions for the CWM flash, as this is the stage where most bricks happen.
To make things easier, I'm uploading the stuff related to the Odin step from my HD ("Odin" subfolder on GDrive), more than two years old. Use them on your own risk, and check the URLs provided.
Note that I didn't go directly for CM11, but installed CM10.2 first. I would have to read the instructions to tell whether this was actually necessary...
On the way, I upgraded the recovery (from the jenkins server that doesn't exist any longer, http://jenkins.androidarmv6.org/view/Developers/job/cm-recovery/24/ of Oct 2014) to 6.0.5.3. (IIRC I did this using the terminal emulator, not Odin, but that should be possible too. I'll upload the recovery.img)
You perhaps max have to create your own Odin-flashable recovery similar to the following (again, I assume no liability at all!):
- take a .tar.md5 as starting point, and unpack it (it's just a tar with a checksum appended)
- replace the recovery.img
- create a new tar file x.tar (name it as you like)
- (cat x.tar; md5sum x.tar) >x.tar.md5
- Odin flash that
I admit it becomes more and more difficult to keep the necessary tools, files, and instructions available and in shape for devices as old as this one (I'm still confused by the "KERNEL3" series.)
---------- Post added at 09:22 AM ---------- Previous post was at 09:00 AM ----------
Quick addendum: there's a new, stagefright-fixed cm11 available for callisto, see http://forum.xda-developers.com/showthread.php?t=2453085&page=27 - which is currently being debugged but looks promising (see page 29 of that thread)
---------- Post added at 10:09 AM ---------- Previous post was at 09:22 AM ----------
It seems that there's a lot of stuff still around if you search for the "galaxy-551" tag.
Bebek's GD might also be interesting (with Odin, CWM5, and more, but stopping at Gingerbread): https://docs.google.com/folderview?...SURkMEE&tid=0B-QaRW7SLPQPTHpaQXR5b1ZVMHc#list
1
bro help
thx for sharing
steve8x8 said:
OK; here you go. That's what I found on my disk. No checksums, so you got to trust me, or unpack and inspect everything. (Perhaps someone else can confirm?)
https://drive.google.com/folderview...hrbmxzZFUwdTd0N1RSdTN4OHI1VzhsVlk&usp=sharing
Click to expand...
Click to collapse
Please don't remove those files from gdrive!:good:
Danke sehr
I didn't plan to, and indeed they are still there. Is there anyone using a Callisto running CM11?
Last night I had a dream: There was a recent ROM upgrade for the Callisto (not sure whether Nougat or Oreo), and I had started to dig out all the old instructions and notes to make it happen.
Only in the morning, after having a big mug of coffee, I realized it was only a dream :'(
armv6 ghosts haunting...
About CM12
Please Post all your Feedback, Fixes or Discovery of new Bugs and Discussion about Mike's CM12 here.
Its compiled by me and released here for some public testing. It was and is Mike's CM !! its his Hardwork !
Thanks to Mikeionniia for his Hardwork and ROM , Langes for helping in the Guide and @Men_in_black007 for helping me in compiling.
Downloads and Build's History
1. 4 Jan 2015 (Initial Build) http://d-h.st/vMXg
*Calls not Going Through but Calls are being Received
*Internet/Data Plan Not Working
*Camera is Working
*Video camera is not 100% stable, sometimes it restart phone. 480p recording work mostly without problems
2. 22 Jan 2015 (Wifi Started Working) http://d-h.st/4Ii
*Wifi Working
*Bluetooth Working
*SMS Working
*Randomly Reboots alot
3. 5 Feb 2015 (Calls/Data work randomly) http://d-h.st/34om
4. 12 Feb 2015 (Calls/Data much Stable. Less Random Reboots Much Stable) Kernel not working so Not uploading this.
5. 17 Feb 2015 (Many Changes inside the Settings. Overclock Built in the Settings and many minor changes. Smoother/Stable) [B]http://d-h.st/AcDk[/B]
6. 7 March (Stable than any other build. Smoother/Faster. Loving it. Some changes in Settings) [B]http://d-h.st/2KHx[/B]
FOR ALL LATEST AND NEW BUILDS PLEASE GO TO THE OFFICIAL THREADS HERE !! Plz hold your Q&A and Discussion in their respective Discussion Threads only !! Don't spam the Dev Threads !!
CM12 For all LegacyXperia Devices http://forum.xda-developers.com/xperia-arc/development/dev-2011-unofficial-cyanogenmod-12-0-t3053950
AOSP Lollipop For all LegacyXperia Devices http://forum.xda-developers.com/xpe...v-2011-android-source-project-builds-t3053170
Gapps
DOwnload Pico,Nano or Micro Gapps Only.. no Bigger than this. !!
from here http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
Install Instructions
You should have an Ext4 Partition on your sd card to install properly. I have a 4gb Ext4 Partition on my 32gb card.
Be Warned the process of creating an Ext4 Partition can/maybe wipe your SD card.. So Back Up appropriately
1. Flash .79 FTF in Flash tool
2. Flash Boot.img from Fastboot.
3. Staying in fastboot, erase system and userdata
fastboot erase system
fastboot erase userdata
4. Boot Device, Enter Recovery and (Factory Reset) and then (Wipe Cache)
5. Go to Apply Update, Scroll to the Location of you Zip file of the ROM and Install the ROM !
6. Boot ROM.
Detailed Installation Instructions here for Newbies
http://forum.xda-developers.com/showpost.php?p=58830270&postcount=110
How to Root The ROM or Activate Root on the ROM ?
Go to Settings / About Phone / Build Number and (Press this Continuously for 7+ times until it shows u
that Development Options is Activated.
Go Back to Settings, Click on Development Options and Enable Root Access For Apps/ADB or Both.
Review Video
Installation Video
Thank you for this. From the quick testing I did the D-Pad and buttons work fine but the D-Pad has incorrect directions like it's been rotated anti clockwise up is right, left is up, down is left, right is down. Although you probably know that already directions for installing are slightly incorrect. There is no CWM with this boot.img its CyanogenRecovery so we can't mount /system to wipe it, but it still seems to install and boot fine. System is erased with Fastboot in a previous step anyway
Camera is upside down, but again obvious one you probably know about Well done to everyone involved in getting this device on the cutting edge! Performance is really really good, its like lollipop was made for this
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Phone (Calls u mean) - Not Working
Wifi - Not Working
GPS - I didn't Test
Prox. Sensor - I didn't Test
Light Sensor - I didn't Test
Auto Rotate - Was working I think so, I don't remember
Sound - Working
BT - Working
Camera - Working
DocMAX said:
What about Phone, Wifi, BT, Camera, Sound, GPS, Auto-Rotate when slider is out, prox. Sensor, light sensor - is all that working? What yes what not?
Click to expand...
Click to collapse
Owriço Winchester said:
hello guys
What rom base should I use? the same as 4.4.4
stou curious to test 5.0 thanks
Click to expand...
Click to collapse
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
saqibkhan said:
what do you mean by ROM base you should use.. ??
did you mean KErnel ?? explain your question plz.
Click to expand...
Click to collapse
need to flash stock MT25i (Neo L) ftf
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
all I can say is.. I have a 32gb memory card.. a Ext4 4 gb Partition.. and when I installed the ROM .. it showed me everything as One large 1gb Partition.. not 1gb.. something 900mb ..
So make a partition and then Install the ROm !! it should work like it did work for me.. I Wiped everything from ADB .. and Installed from the Recovery by Cyanogen only.
javix1997 said:
Installation guide?
I need to flash the same boot.img of KitKat and mt25.ftf or something new?
You not said nothing about how to install this special ROM 5.0.2
Please put an installation guide in the post
Thanks and great work
Click to expand...
Click to collapse
DocMAX said:
OK guys, i'm leaving. CM12, CM11 and all Android 4.x stuff is simply crap. Functions are missing, the UI is nochy. Overall not feeling good. And probably nobody will ever release a superb CM1x ROM. So i'm back at Ginger Bread - the original. Bye.
Click to expand...
Click to collapse
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
hello !! I wonder if you could help me to port for xperia neo v
What would it take?
There is cm12 for neo v. Just look for it on Yours phone forum
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Bakisha said:
I had compiled cm12, but i don't have time right now to reformat my 32gb card to make 2nd partition.
Btw, in what format is that 2nd partition? Ext2 or ext4?
As i see from source code, system is 900MB, so i guess data partition is on 2nd partition on sdcard?
Just asking, so to flash cm12 i need:
Flash any .62+ firmware (to unlock custom partitioning)
Flash kernel from zip
Erase system and userdata from fastboot
Flash rom from recovery
?
Ps: as for cm7, i can't help much, because i don't have harddisk space in virtualbox (cm12 source took all avaiable space)
If you can compile cm7 kernel, try with values from my thread (the 220/700 ones)
I can recalculate values again if you need more space. As i recall, official cm7 for zeus is around 130 MB and gaaps is around 7MB, so maybe 149.5/770 partitions size is ok?
Sent from my R800i using XDA Free mobile app
Click to expand...
Click to collapse
Hi that's nice that you compiled again.. cuz Mike might have made some changes and some bugs might be done with..
yes system was 900mb+ etc.. and I had a 4gb partition on my card for Link2SD .. its Ext4 !! as far as i remember.
Step 1...i flashed the .79 FTF for Xperia Play..
Step 2...then i Wiped System and userdata by fastboot as listen in Mikes CM11 OP !
Step 3...Then i flashed Kernel.. (or you can switch these steps 2 or 3)
Step 4... Install ROM by Using Cyanogen Recovery. i can we need to go to Install Update.zip option ..
Edit : i think 210/700mb is more than enough.. values are already calculated by you so thanks for that.. its always nice to have some space in system else it keeps showing (System Low on Memory Error)
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
saqibkhan said:
i can compile as well. but im confused.. i have already the cm12 source downloaded and compiled.. will the cm7 take the same space on top of that.. or how will i differentiate the folder for both.
is their a step by step guide i can follow.. and at which step do i need to change the Kernel Values ! and where.. i have no clue of that ! can you rite a quick step guide for me.. lead me into the right direction and i can ask you my doubts along the way.
Click to expand...
Click to collapse
To be honest, i don't know. My guess is that you need to delete cm12 source, then from ~android/system folder do the repo init for cm7
There is a guide for building CM here but use
Code:
repo init -u https://github.com/CyanogenMod/android.git -b gingerbread
instead of ics
Editing partition should be easy, as you only need to edit file semc_zeus_defconfig (it should be in ~android/system/kernel/arch/arm/configs/ folder or just search where is that file when you download source)
Then build as a guide say.
I am not 100% sure about building CM from source, so i'm only guessing, maybe someone else with better knowledge about compiling could say
As for CM12, i'll compile it again in few days, and hopefully i'll have time to test it for weekend
saqibkhan said:
true that.. when ever I return to ginger bread from all the other ROMS I feel so relieved !! its soo fast and easy and special.. if you can help me.. help in building a cm 200/700mb Kernel.. cuz cm7.3 runs like hell fast.
but yeah.. we need newer ROMS as well and I was loving everybit of Lollipop .. but once the Bugs are done.. i will be back on that..
Click to expand...
Click to collapse
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
DocMAX said:
cm 7.3? i only see cm 7.2 on official site. is EVERYTHING working? (including touchpads?)
Click to expand...
Click to collapse
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Does the second partition have to be 4GB in order to install CM12 or what size?
P.S. Tested Dead Space on CM7.3, Touchpads not working. I have found Doom Kernel + ICS, without heavy apps, to deliver the best overall performance for the Xplay. Overclocking to 1.8GHz makes even Reicast playable.
saqibkhan said:
yes cm7.3 .. DEv of cm7.2 ended a long time back.. then the FXP team compiled cm gingerbread again late in 2013 December I think .. and started calling it cm7.3 . kinda like the EOL version.. its amazing .. only change I want is a 210/700mb Kernel.. that would make it even more useful
IDK about the Touchpads though.
you should look here at my post in this thread !!
http://forum.xda-developers.com/showpost.php?p=57610312&postcount=3038
Click to expand...
Click to collapse
i dont see light sensor working?