Related
PLEASE NOTE: If you are using a Canadian handset, I recommend switching over to my JL2 based ROM. It's the same speed (if not quicker), and I will be providing much more updates for it. The ROM can be found here: http://forum.xda-developers.com/showthread.php?t=906977
News
12/23/10 - v0.2 released! Includes an error-checking script to prevent possible errors from occuring, new Steam recovery, wipe and non-wipe versions and more! Check the changelog for more info.
12/22/10 - v0.1, initial beta release
Hey everyone,
This is a rom which aims to provide the absolute best user experience by being extremely quick without sacrificing any necessary features. The majority of Samsung bloatware is removed, however a good portion of the pre-installed apps are left untouched. This ROM is based on XXJPY (Froyo 2.2.1).
If you have any questions prior, while, or after installing this ROM, please read the first few posts, as I'll try to address every possible (major) problem which can occur. If, after reading the posts, you are still encountering a problem, please reply to this thread being as detailed as possible. This allows me to fix problems quickly and easily.
Now, this is my first ROM, so there are bound to be a handful of bugs. However, I've been using this ROM for a few days and have yet to encounter any major problems.
Note: Please don't complain about Quadrant, Linpack, or any other pointless benchmark scores. If you've used the ROM and it's sluggish, by all means tell me, but don't base your opinion of the speed merely on a benchmark.
Okay, so what now?
1. Download and Install Instructions
2. Changelog, To-Do
3. FAQ and Problems
4. Screenshots, Media, User Comments
Features
Based on XXJPY (Froyo 2.2.1)
Patched Speedmod kernel, version K12 hz=256(allows you to mount on computer without problems)
Steam multi-touch recovery: update.zip on SD card
Added an error-checking script which prevents errors when installing [thanks Darkyy!]
All-black Gingerbread theme (saves battery)
Fully deodexed
Fully zipaligned
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox
All protected apps in market - modified build.prop
Big APN list, which allows instant internet + MMS access
Integrated ClockworkMod Recovery
Stock AOSP Lockscreen
Bell UGJK3 Modem
Backlight Notifications
Added Applications:
Nexus S Live Wallpapers
Swype v 2.15 (Newest)
Launcher Pro
Optional: Gingerbread Keyboard (install from SD Card)
Removed Applications:
AllShare
Diary
Aldiko Reader
Press Reader
Layar
Thinkdroid
Write and Go
Credits (in no particular order)
-Hardcore for the kernel
-santiemanuel for the Nexus S Live Wallpapers
-vukandric for the theme
-Darkyy for help on the update script, and for generally being awesome
Download and Install Instructions
Downloads
Latest and Greatest
-v0.2: seeARMS XXJPY (12/23/10)
Wipe: http://www.multiupload.com/L9SUOBKO88
No Wipe: http://www.multiupload.com/9F5E89AYTP
-v0.1: seeARMS XXJPY (12/22/10)
http://multiupload.com/G6XTJF07MO
Modems
To flash these modems, use Odin and select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
JL2: http://www.multiupload.com/TC1ME8VB20
JK4: http://www.multiupload.com/3HOKWMBHO2
Installation Instructions
Before installing, disable any lagfixes (which can typically be done by booting into recovery mode and selecting "Disable Lagfix").
Also, if you wish, backup everything! Perform a NANDROID backup in recovery, backup your music, files, etc. In case something goes wrong (it will eventually), you'll have peace of mind.
Please note: this rom will wipe all your data. It will not, however, format your internal or external SD cards. This means you'll lose apps and settings, but not music, movies, etc.
Lastly, I recommend performing a factory reset before installing any new rom.
If you're running a previous version of my ROM, feel free to install the non-wiping version. However, if you're switching roms, I recommend running the standard version, which will erase all data.
1. Download and copy this file to your internal memory card.
2. Boot into recovery, and select "Install zip from sdcard".
3. Select "Choose zip from sdcard", and scroll to the ROM.
4. Select OK, and wait for the file to flash.
5. Reboot. This reboot will take a while (upwards of 2-5 minutes), so be patient and don't shut off your phone!
Congratulations, you've successfully flashed!
After it boots, I'd recommend doing a few things in order to allow your phone to be as quick as possible:
1. Boot back into recovery, select "Advanced SpeedMod ULK Features". Choose "LAGFIX options", then "Faster: EXT4 ALL". This applies a lagfix, and converts the partitions into the faster EXT4 filesystem.
2. In recovery, go back to the Advanced SpeedMod ULK Features menu. Choose "TWEAK options", and enable every tweak. For more information about these tweaks, see HERE.
Also, window animations are disabled by default. You can enable them by going into settings -> Display, and selecting Animations.
3. If you'd like the Gingerbread Keyboard, open up the My Files application and navigate to the directory "Gingerbread_Keyboard". Open up the .APK file and install as usual.
Changelog And To-Do
Changelog
v0.2
-Google Voice Search updated
-Added option to install gingerbread keyboard
-Updated kernel version to K12
-Added error checking script - with help from Darkyys rom (This prevents possible errors when installing)
-added nowipe and wipe versions
-Modified build.prop to allow all protected market apps
-Added Steam recovery - check FAQ for info on how to access it
v0.1 - Initial beta release
To-Do
-Gingerbread Keyboard
-Extended Power menu
-Support for different themes
-Stock application pack (available for flashing through CWM)
-Better modem (JL2? JK4?)
-Faster browser
-Modded SMS Application
-Modded Camera Application
If there's anything else you'd like to see in this ROM, just ask.
FAQ And Problems
FAQ
I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
No worries. Follow these steps:
1. Download Odin from here.
2. Download the Speedmod kernel for whichever Android version you're running. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
7. Now you're required to download the patch for the Speedmod kernel, which will allow you to copy the ROM over to your internal SD card. If you don't install this patch, the internal SD card will be detected as a CD drive, and will be read-only. The patch is able to be downloaded from HERE. Simply copy this patch to your SD card, boot into CWM, and flash it using "install zip from sdcard". After doing this, follow the normal steps to install this rom!
I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
Simply perform a factory reset. Clear the cache + Dalvik cache in recovery as well, if you'd like.
What's this steam recovery and how do I access it?
Click to expand...
Click to collapse
Steam recovery is a new, semi-functional multi-touch recovery created by sztupy. This recovery has all the features the standard CWM one has and more. Check his thread for more info.
Please note: Because (currently) the only Steam-compatible kernel is based on a much older base version (ie: not XXJPY), a small amount of features are incompatible, such as lagfix options, kernel options, etc. However, the majority of features (such as mounting, wiping, etc) are working just fine. I'm working on getting everything working; as soon as it is, it will fully replace CWM on this ROM.
To enable it, just boot into CWM and go to "Apply sdcard: update.zip". After doing this, it will boot into the new Steam recovery. You must do this every time you want to access it.
My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Screenshots, Media, User Comments
Screenshots
Click for a larger image.
User Comments
°Dexter° said:
Impressive rom seeArms, really really fast...faster than others, indeed.
...
Very good work,no major issues by now,i'm eagerly waiting for next release
Click to expand...
Click to collapse
Existence. said:
it's runnin great, thanks seeARMS. can't wait for the JL2 version. i really dont wnt to brick my phone and i think the JL2 version fixes the SD dying problem so i cant wait!
Click to expand...
Click to collapse
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
gonna try this ROM out!
Quadrant score? I will try it, looks good.
gonna try this release soon, good job
fenerbuuh said:
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
Click to expand...
Click to collapse
I'm using this modem because I need the Canadian band, because, well, I'm located in Canada. And, according to this guide, this modem is very good on battery life and reception.
In later versions of this ROM I'll most likely include a different modem (or a flashable modem). Something like that.
Any modem you'd prefer to see included?
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Hey man, to bad i flashed Docs jpy rom just yesterday evening, and dont want to change rom on a daily base. But ill test it for sure just because id not have to change kernel afterwards...
so thanx for your work and keep it coming man...
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
seeARMS said:
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
Click to expand...
Click to collapse
I'm looking forward to this,man!Thank's
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
No way man, but you could get hardcores kernel as an odin package, it comes with cwm recovery, flash that first and then use cwm to install this rom.
Mparmpa-Nikos said:
I'm looking forward to this,man!Thank's
Click to expand...
Click to collapse
Done. See the FAQ.
Welcome new devinteresting rom,gonna try it...
Thank you
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Sounds good
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Darkyy said:
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Click to expand...
Click to collapse
Will do Darky, thanks.
canad1an said:
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Click to expand...
Click to collapse
Market comes updated to version 2.2.7 already. I haven't had any problems with it at all.
Hi all, this thread has been written for the first time modifier who is adventurous enough to want to get the best from their phone, but who is unsure how to proceed.
It has been designed to be easy to understand and be as user friendly as possible.
Before I go any further, it's only fair to state that I am NOT the original author/developer for any of the processes, methods or software contained herein, I will try to give credit where it is due.
Please be aware that these instructions are Galaxy Wonder SPECIFIC, I DO NOT KNOW if they will work on any of the other variants of this phone.
It should be noted that any modifications performed on your phone carry an element of risk. The responsibility for this risk lies with YOU as it is YOU who are CHOOSING to follow these instructions. Neither I nor anybody else mentioned in this post will accept ANY responsibility if you damage your phone by following the instructions detailed below.
Also note that by following these instructions, you WILL be voiding your warranty.....
All the processes detailed below are possible WITHOUT the use of a PC. there is an alternative method for all the processes that uses a PC and a software package called ODIN. People will argue in favour of one method or the other.....My preference is to do everything "in phone" without ODIN.
Before you start any of the listed processes check to see that you have AT LEAST 50% remaining battery power. I'd personally recommend that you fully charge your phone before you start.
Finally, if it is your intention to install a custom ROM, it is necessary to follow EVERY procedure listed IN THE ORDER listed. Failure to do so WILL lead to damaging your phone.....you have been warned.....
Step 1) Rooting
When you Root your phone, you are giving yourself "administrator" rights to your device. you CANNOT move on to the other steps unless you've Rooted your phone.
Please see the thread below (created by @THE E ) that details a step by step guide (with resources) for rooting your phone.
Here is an alternate link for the update zip.......
https://www.androidfilehost.com/?fid=24052804347838294
I have, since compiling these instructions, begun to read that the method below, WILL work for Android version 2.3.5, but MAY NOT work with Android version 2.3.6. To find out which Android version you are using, tap...
Settings>> about phone/device>>Android version.
If you find you have 2.3.6 try the method anyway...it won't damage your phone, it just won't work (if these reports are accurate). I am trying to get clarification from the developer on this, so please bear with me......
If it doesn't work, please leave a comment at the end of this thread and/or the below linked thread......
(Edit...this has been confirmed working on at least two 2.3.6 devices....thanks for the feedback @azim and @WonderTester )
http://forum.xda-developers.com/showthread.php?t=1317394
The first method detailed in the link is the easiest. You will find the "update zip" file in "downloads". It needs to be moved (copied and pasted) from downloads so that it is NOT inside ANY folder but is still in your internal phone memory (root directory).
More confident users may want to make a backup of their 'stock' recovery before installing CWM. this backup will be useful if you've rooted your phone and installed CWM, but haven't installed a custom ROM..... and then discover a need to send the phone in for repair. This post by @elchi1234 will tell you how to do it......
http://forum.xda-developers.com/showthread.php?p=46433083
Step 2) installing ClockworkMod
ClockworkMod (CWM) is an advanced piece of software that replaces the pre installed recovery partition on your phone. It allows you to (amongst other things) make NANDROID backups (I will cover this later), factory wipe your phone and install CUSTOM ROMs. the method quoted below was provided to me by @IvanKurnia . You need to install TERMINAL EMULATOR and BUSYBOX (available in the Play Store) in order for this method to work.....
THESE STEPS NEED ROOT & BUSYBOX, BUT DON'T NEED A PC & ODIN..
FOR BEST RESULTS, UPDATE YOUR SUPERUSER.APK, SU BINARY, AND BUSYBOX
Open one of these links (courtesy of @arco68 )..
CWM 6.0.1.2
https://www.androidfilehost.com/?fid=24052804347838291
CWM 6.0.4.4
https://www.androidfilehost.com/?fid=24052804347838292
CWM 6.0.4.5
https://www.androidfilehost.com/?fid=24052804347838293
-download and extract (unzip) the file from your chosen link.
-put the recovery.img file in /mnt/sdcard (internal phone storage. NOT external SD card)
-download "Terminal Emulator" (by Jack) from the Play Store
-open Terminal Emulator then type "su" and click enter
-allow root access..
-then type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13"
(the su and dd if=/.....text needs to be entered without the " " quote marks)
then click enter
(the 0 in mmcblk0p13 is the number NOT the letter).
-then some text will appear at the bottom of the Terminal Emulator panel.
-exit terminal emulator.. check the recovery by turning off the device then turn on with volume up button, home button, and power button pressed together.. until "Galaxy W" screen shows up, release the power button only.. then you will enter CWM
-navigate with up (up) and down (down) vol buttons and home keys (select) and power (back) and click "reboot system now" to reboot
The above method has a proven track record for successful implementation.
There is an alternative method of installing a recovery (created by @pepoluan) which bypasses the need to type code into terminal emulator. See this thread for details.......
http://forum.xda-developers.com/showthread.php?t=2113946
There is an alternative custom recovery for the Wonder called TWRP.....it has one major advantage over CWM in that it is a 'touch' recovery....you touch the screen rather than relying on pressing buttons to use it. Please see this thread........
http://forum.xda-developers.com/showthread.php?t=2046035
for download and flashing instructions.
Step 3) preparing your phone for CUSTOM ROMs.
When you flash (install) a CUSTOM ROM on your phone, it is necessary to wipe everything (including original Android OS, Apps, SMS messages, call records, contacts etc) from your phone before hand. If you need these on your phone after ROM installation, you have to make copies of them first.
To copy the OS, you will need to create a NANDROID BACKUP....You might ask why this is necessary...simple...If you (for some reason) want/need to go back to the factory installed software, the NANDROID BACKUP is the easiest way to do so.
In order to create it, you need to reboot into recovery (switch the phone off, then switch back on while pressing the power, home and volume up keys, then releasing ONLY the power button when the SAMSUNG logo appears) Use the volume down button to scroll to "backup and restore" and use the home button to select, then on the next screen, select backup.
You will need 800mb or more of free memory to create this backup....any less and it won't complete.
When done, reboot your phone and use your file browser to search for a file called ClockworkMod. If you find it on your external SD card you don't need to do a thing, If you find it in internal storage, you need to "zip" it (minimal compression) and move it to your external SD card, otherwise it'll be deleted during the wipe process prior to installing your custom rom.
It is advisable to create a Nandroid backup not only before flashing your very first ROM, but also before you upgrade from an older version of your chosen ROM to a newer version (eg CM10 a2 to CM10 a4.1) that way you ALWAYS have a functioning copy of a working setup that you can go back to if something goes wrong.......
To backup your Apps, you'll need to download APPBAK from the play store.
To backup your SMSs, you'll need to download SMS BACKUP AND RESTORE from the play store.
To backup your call logs, you'll need to download CALL LOGS BACKUP AND RESTORE from the play store.
Open each app in turn and use it to create backup files for everything you want to restore. As before, if these files are stored on internal storage, move them to your external SD card to prevent deletion.
CAUTION.....DO NOT attempt to back up app user data (high scores, game progress etc) this data MUST NOT be re installed when you re install your apps.
To create a backup of your contacts, you need to go to your contacts on your phone, press the menu button, select import/export then select export to SD card to create a backup file...again, check for file location and move if necessary.
Make a note of WHERE the backup files are located before you move them. It will probably be a good idea to return them to their original location once you have installed your new ROM. That way when you use the apps to restore your data, the apps will be able to find their respective backup files.
You are now ready to install your CUSTOM ROM.
Step 4) CUSTOM ROM installation
Below is a list of CUSTOM ROMs that will install through CWM.
In this section, you'll see several references to GAPPS. This is an acronym for Google APPS which is a package that contains Google related software such as Play Store etc. Without it, you won't be able to access any of the Google services.
CM9-based ROM (Icecream Sandwich 4.0.4)
Spoiler
Aokp-Milestone6-iattilagy (by @iattilagy)
http://forum.xda-developers.com/showthread.php?t=1844186
BioHazard v.5 (by @hypnos17)
http://forum.xda-developers.com/showthread.php?t=1927428
CyanogenMod 9 (by @arco68) (ORIGINAL CM9)
http://forum.xda-developers.com/showthread.php?t=1576874
EHNDROIX ¤ 12.9.13 (by @AlessandroXCV)
http://forum.xda-developers.com/showthread.php?t=1850859
InDroiD REMICS V5.1 (by @kkrraazzyy)
http://forum.xda-developers.com/showthread.php?t=1842544
MIUI v.4 2.8.10 RC2 (by @Alex93917)
http://forum.xda-developers.com/showthread.php?t=1749067
PARANOIDANDROID Ecstacy[RC 2] (by @Doomsday94)
http://forum.xda-developers.com/showthread.php?t=1753065
PARANOID ANDROID HYBRID BUILD 2 (by @filosofi_killms)
http://forum.xda-developers.com/showthread.php?t=1929027
RemICS v1.5 - SIII look (by @sparta20)
http://forum.xda-developers.com/showthread.php?t=1753233
Revamed v.1 STABLE (by @droidgeo17)
http://forum.xda-developers.com/showthread.php?t=1892863
Xperia ICE Stable v3.1 (by @filosofi_killms)
http://forum.xda-developers.com/showthread.php?t=1863386
CM-10 based ROM (jellybean 4.1.2)
Spoiler
CyanogenMod 10 (by @arco68)
http://forum.xda-developers.com/showthread.php?t=1990795
MIUI Unofficial Port by @blacksmith yogi
http://forum.xda-developers.com/showthread.php?t=2228665
Express999 by @ipromeh
http://forum.xda-developers.com/showthread.php?t=2281277
broodROM Jellybean by @outerh3aven
http://forum.xda-developers.com/showthread.php?t=2289326
VeloxROM by @miki2o
http://forum.xda-developers.com/showthread.php?t=2171430
CM-10.1 based ROM (jellybean 4.2.2)
Spoiler
CyanogenMod 10.1 by @arco68
http://forum.xda-developers.com/showthread.php?t=2214042
ParanoidAndroid by @krislibaeer
http://forum.xda-developers.com/showthread.php?t=2295544
LiquidSmooth by @educk
http://forum.xda-developers.com/showthread.php?t=2295554
Monster [CM10.1+SlimBean] by @ipromeh
http://forum.xda-developers.com/showthread.php?t=2214959
Touchwi5 ROM by @ipromeh
http://forum.xda-developers.com/showthread.php?t=2259071
pacman v22.2.0 the aio rom by @evanlocked
http://forum.xda-developers.com/showthread.php?t=2218224
mirrors for Arco's ROMs
These ROM/GApps packages will be downloaded as zips which need to be extracted so that you have a ROM zip and a GApps zip.
DO NOT extract these zips as this is the format that is needed to flash the packages in CWM. You will need to download 7zipper 2.0 from the playstore in order to extract the files.
Spoiler
CM9 final
https://www.androidfilehost.com/?fid=24052804347838957
CM10 final kernel 2.6
https://www.androidfilehost.com/?fid=24052804347838960
CM10 final kernel 3.0
https://www.androidfilehost.com/?fid=24052804347838961
CM10.1 alpha 6
https://www.androidfilehost.com/?fid=24052804347838959
Some members have requested the ability to use their removable micro SD cards as an alternative to the phones built in storage. on CM-9 this facility is built in. on CM-10 and CM-10.1, it is not. Normally, to achieve this, the ROM would have to be modified after installation. Some members (myself included) are uncomfortable when it comes to modifying code. With that in mind a forum member called @temenalie has taken the latest builds of Arco68's CM-10 and CM-10.1 and modified the code so that the storage mount swap takes place DURING the installation, so that the end user doesn't have to do it 'post install'
Arco68's CM-10 Final (JB 4.1.2)
http://www.mediafire.com/?2qbmgw8bdwbf3am
Arco68's CM-10.1 Alpha 7 (JB 4.2.2)
http://www.mediafire.com/?3l7lh438f3xofql
Edit (20/10/15) the above two links are non functional, I am trying to re-source these ROM's and hope to be able to make them available again in the near future.
These ROMs should ONLY be used if there is an external SD card present in the phone that you want to use as phone storage.
ROMs courtesy of @arco68 , modifications courtesy of @temenalie.
Each of the above links opens the home page for that specific ROM. Most will have installation instructions on the first page. ALL instructions MUST be followed EXACTLY to avoid damaging your phone. some will have a separate "GAPPS" file which needs to be installed as well as the ROM.
Unless otherwise stated in the instructions for the individual ROMs, the method detailed below can be used to install all the ROMs from the links above. You MUST read all the instructions for your chosen ROM in case there are any differences in the installation methods.
-1) download the ROM and GAPPS (if Needed) to your phone/SD card
-2) switch off then reboot your phone into recovery
-3) create your NANDROID BACKUP (if you haven't already done so)
-4) scroll to and select "wipe cache partition"
-5) scroll to and select "advanced" then scroll to and select "wipe dalvik cache"
-6) this is the point of NO RETURN. press the back button then scroll to and select "wipe data/factory reset"
-7) scroll to and select "install zip from sdcard" then "choose zip from sdcard" or "choose zip from external sdcard" depending on where you downloaded the ROM and GAPPS files. you MUST install the ROM FIRST followed by GAPPS (if necessary/not included in the ROM)
-8) press the back button until you see "advanced", select it then select "fix Permissions" (if necessary) then scroll to and select "wipe battery stats"
-9) press the back button and select "reboot system now"
A more in depth "pristine" wipe method can be read about in the article below created by @pepoluan ....
http://forum.xda-developers.com/showthread.php?t=2044861
It can be used to replace the steps from step 4 above. Although it isn't necessary to complete this "pristine" wipe unless you were having problems with your "stock" ROM, or, after flashing your new custom ROM, you discover you have problems with that ROM and the only option is to do a complete wipe and re install.
Wait for your phone to boot up. You'll have to set up your phone again like you did when you purchased it and you'll have to sign into your Google account again in order to use the Play Store. Once the setup is complete, download APPBAK, SMS and CALL LOG BACKUP AND RESTORE, and restore your saved backups....
CAUTION......DO NOT restore user data generated by your apps. This will cause instability in your apps and make them force close.....
To restore your contacts, you need to open the newly installed (included in ROM) People app, press the menu button, select import/ export and then import from storage.
.you have now completed the process of modifying your phone.....congratulations and enjoy.....
On step 8 of the installation process, I mentioned 'wiping battery stats'. This is NOT something that is crucial to ROM installation, but it IS something that needs to be done after EVERY new installation. The reason being that your phone will calibrate your battery to your current ROM. When you install a new ROM, it'll have different battery usage patterns. If you don't get rid of the old battery data, you could experience some 'irregularities' in what the phone sees as the percentage of battery use compared to the actual battery use. Once this data has been wiped, you'll need to complete 3 or 4 full charge - full discharge cycles in order to calibrate the battery to the new ROM.....
One final point, none of the above would have been possible without the hard work of developers like @arco68 and the countless others who have given their time so that we can get the best from our phones.........
(All information correct and up to date at time of post creation)
if you liked this post, or it has helped you in any way, please hit thanks
thankyou for reading.....happy flashing
404 Page Not Found
The page you requested was not found.
ji.sonu said:
404 Page Not Found
The page you requested was not found.
Click to expand...
Click to collapse
I think it would help, if you would specify on which of the many links provided that error occured .
I've just attempted to open each link, and they all seem to work......
CM9...I don't HAVE to.....I just.....can..
@Keith
good work hahaha you understand all of those things just for a while.. I will thank you later, I've given 8 thanks..
Stickied
I made this a sticky for now. Seems quite useful.
If any of you see things to improve or to correct, please tell the OP so.
jotha - forum moderator
Looking forward to your feedback...
CM9...I don't HAVE to.....I just.....can..
Why do we have so many variants of CM9?Can someone explain each differences?
azhiekurosaki said:
Why do we have so many variants of CM9?Can someone explain each differences?
Click to expand...
Click to collapse
Every custom variant of CM9 based roms are tailored for a specific thing, theme, or style.
paranoidandroid for example, attempts to bring tablet interface to handhelds.
MIUI, as far as I know, attempts to create a smooth user interface, which should give the user 60 fps on the screen.
There might also some apps/tweaks difference. Try reading all the related thread to find out about each one. No pain, no gain
Sent from my GT-I8150 using xda app-developers app
reidzeibel said:
Every custom variant of CM9 based roms are tailored for a specific thing, theme, or style.
paranoidandroid for example, attempts to bring tablet interface to handhelds.
MIUI, as far as I know, attempts to create a smooth user interface, which should give the user 60 fps on the screen.
There might also some apps/tweaks difference. Try reading all the related thread to find out about each one. No pain, no gain
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
That's one thing I didn't cover on purpose....the differences between the ROMs as that is down to (informed) personal choice. The purpose of the original post is to familiarize new users with the basic process of modifying their phones. Once they have that experience of flashing custom ROMs, they can then start experimenting to see which ROM best suits their needs....
Having said that the original version of CM9 is always the best place to start......
CM9...I don't HAVE to.....I just.....can..
great
great info ... first time viewing ... loved alot
choclateguy85 said:
great info ... first time viewing ... loved alot
Click to expand...
Click to collapse
No problems mate...that's what it's there for.....just remember to hit thanks lol
CM9...I don't HAVE to.....I just.....can..
keithross39 said:
Step 4) CUSTOM ROM installation
Below is a list of CUSTOM ROMs that will install through CWM. (list courtesy of MyDeSTiNaTe)
In this section, you'll see several references to GAPPS. This is an acronym for Google APPS which is a package that contains Google related software such as Play Store etc. Without it, you won't be able to access any of the Google services.
CM9-based ROM:
Original CM9 http://forum.xda-developers.com/show....php?t=1576874
BioHazard http://forum.xda-developers.com/show....php?t=1843207
InDroiD REMICS http://forum.xda-developers.com/show....php?t=1842544
MIUI http://forum.xda-developers.com/show....php?t=1749067
PARANOIDANDROID Ecstacy http://forum.xda-developers.com/show....php?t=1753065
Aokp-Milestone6-iattilagy http://forum.xda-developers.com/show....php?t=1844186
Digital.AOKP-Milestone6.I8150.BZS http://forum.xda-developers.com/show....php?t=1840869
EHNDROIX http://forum.xda-developers.com/show....php?t=1850859
RemICS http://forum.xda-developers.com/show....php?t=1753233
XPERIA ARC http://forum.xda-developers.com/show....php?t=1863386
Click to expand...
Click to collapse
Nice thread mate, very very usefull thread
for the best part, you just need fix the links above, and everything will be fine
that's why @ji.sonu said 404 page not found
temenalie said:
Nice thread mate, very very usefull thread
for the best part, you just need fix the links above, and everything will be fine
that's why @ji.sonu said 404 page not found
Click to expand...
Click to collapse
Thanks for your comment....but can you tell me WHICH links are broken....I've tested them all again... and for me, they all work.....
CM9...I don't HAVE to.....I just.....can..
keithross39 said:
Thanks for your comment....but can you tell me WHICH links are broken....I've tested them all again... and for me, they all work.....
CM9...I don't HAVE to.....I just.....can..
Click to expand...
Click to collapse
all the links CM9-based
OK....thanks fella.....I'll get onto my PC tonight and copy and paste links to individual threads rather than copy and paste a list of links....maybe that'll solve the problem.....(I hope)......
CM9...I don't HAVE to.....I just.....can..
check your inside direct link, should with the lines showthread.php?t= not show....php?t=
---------- Post added at 09:38 PM ---------- Previous post was at 09:35 PM ----------
keithross39 said:
OK....thanks fella.....I'll get onto my PC tonight and copy and paste links to individual threads rather than copy and paste a list of links....maybe that'll solve the problem.....(I hope)......
CM9...I don't HAVE to.....I just.....can..
Click to expand...
Click to collapse
your welcome, mate. I'm so glad that we can help each other
all the links CM9-based is working now, bro. good job
Good to know mate......thanks...
CM9...I don't HAVE to.....I just.....can..
keithross39 said:
Good to know mate......thanks...
CM9...I don't HAVE to.....I just.....can..
Click to expand...
Click to collapse
You're welcome
Sent from my GT-I8150 using xda premium
This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.
CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?
Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.
Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.
Iloveyou and thanks for that guide I've made my first succeded rom install ever
MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:
Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.
Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.
Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We will not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our instructions word by word
are unfriendly
WIKI
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Endeavoru_Info
INSTRUCTIONS
First time installing CyanogenMod 12.0 to your HTC One X (GSM), or coming from another ROM:
Read the official wiki
Read known issues and FAQs
DO A BACKUP
Unlock your device via http://www.htcdev.com if you haven't done so already
Read post #3 and flash a recovery supporting the new storage layout
DO A DATA WIPE / FACTORY RESET
Copy GApps and the CM 12.0 zip to your SD card
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Flash the boot.img included in the CM 12.0 zip via Fastboot
Reboot (be patient, "optimizing apps" takes a while)
Don't restore system data using Titanium Backup!
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 12.0:
If you're coming from a pre-/data/media build read post #3
Copy the CM 12.0 zip to your SD card
Boot into Recovery
DO A BACKUP
Flash the CM 12.0 zip from SD card
Optionally flash the most recent GApps for Lollipop if you encounter problems
Flash the boot.img included in the CM 12.0 zip via Fastboot if necessary. If in doubt, flash it.
Reboot (be patient, "optimizing apps" takes a while)
Upgrading from CyanogenMod 11.0: (untested and unsupported, see FAQ below)
Read the known issues and FAQs
DO A BACKUP
Read post #3 and flash a recovery supporting the new storage layout
Copy GApps and CM 12.0 ZIP to your SDCard
Boot into Recovery
Flash the CM 12.0 zip from SD card
Flash GApps for Lollipop from SD card
Flash the boot.img included in the CM 12.0 zip via Fastboot
Reboot (be patient, "optimizing apps" takes a while)
DOWNLOADS
Recovery: See post #3
CM12.0 unofficial testing builds:
Old layout:
2014-12-17
2015-01-02
2015-01-11 (broken UMS)
2015-02-03 (fixed boot.img)
2015-02-28
New Layout (read post #3):
2015-02-14
2015-02-28
CM12.0 official stable builds: Not available
CM12.0 official nightly builds: Not available
Google Apps: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
CHANGELOG
http://github.com/CyanogenMod & http://www.cmxlog.com/12/#
2015-02-28
Synced with CM
Fixed an issue with some SIM cards
Fixed USB OTG
Fixed broken Wi-Fi after a soft reboot
Device encryption should work (make a backup first!)
Fixed Rezound Proximity Calibrator
2015-02-14
Uses new storage layout. Read post #3. New boot.img and a complete wipe is required!
Synced with CM
Maybe working Google Play Movies
2015-02-03
Fixed boot.img is not required but recommended.
Synced with CM
UMS situation unchanged from 2015-01-11
Included a fix to allow moving Apps to SD
Allow toggling NVIDIA smartdimmer under Settings -> Display -> Advanced settings -> Adaptive backlight (with fixed boot.img)
Allow toggling sweep2wake under Settings -> Display -> Advanced settings -> Double-tap to wake (with fixed boot.img)
Allow changing the vibrator intensity under Settings -> Sound & notification -> Other sounds -> Vibrator intensity (with fixed boot.img)
2015-01-11
Synced with CM
Default to MTP for new installations (set it to MTP manually in the storage settings when coming from an older build)
Revert some custom UMS related fixes which restores the stupid pre 2015-01-02 auto-mount behavior. DON'T UPDATE IF YOU WANT TO USE UMS
Enable multi-user UI (and guest mode)
Fix setting maximum CPU frequency
Fix signal strength
2015-01-02
Synced with CM
Fixed SD card / UMS mounting issues
Fixed tethering
Button backlight is now adjustable
Long press action for "Recents button" now available (back is still missing)
USB connection mode can now be set to MTP
2014-12-17
First testing build
KNOWN ISSUES
Roughly in order of seriousness.
Outgoing calls & mobile data might be problematic
There is currently an issue with some SIM cards (MultiSim?) that don't work properly. You are able to receive calls and SMS messages but you cannot make calls or send SMS and mobile data does not work. The cause has been identified: http://review.cyanogenmod.org/#/c/88932/
No mobile data after disabling Wi-Fi
IP routes are not updated properly (check if "ip route")
Disable and enable mobile data to work around this
Recent App switcher is broken in landscape and may cause reboots.
Workaround: Select "Disable HW overlays" in the Developer options.
Using NFC with the Smart Lock feature causes a deadlock.
No device encryption possible.
No P2P/Wi-fi Direct.
Battery stats list Wi-Fi as always turned on even though it was disabled.
Audio may be problematic with MHL.
Sense 5 camera features not available (no burst, no zero-shutter-lag, picture quality seems to be worse).
Docking stations are not properly supported
Dock speakers do not work
Select "Disable HW overlays" in the Developer options to avoid crashes
Dock drains the battery
Proximity sensor issues (screen stays black after call, hardware issue, it may not affect you).
Workaround: install Rezound Prox Sensor Calibrator and play with the PS1_CANC slider).
SD card might not be available or might be always shown as shared.
Workaround: unplug the phone from your PC.
Moving Apps to SD is broken
Tethering seems the broken
No MTP
Mobile signal display is incorrect.
Unable to change the maximum CPU frequency through the settings.
FAQ
Can I dirty flash coming from CM 11.0?
It should work.
Do I need to update the recovery?
Please read post #3.
Where are the Sweep2Wake, Button Backlight Notifications and Fast Charge Settings?
Not accessible anymore from the settings. The functionality is still in the kernel. See second post for details.
When do the nightlies start? When do upload the next version? When do you fix XYZ?
I don't know.
Device not recognized in Windows (Recovery, UMS, MTP)
Please follow the steps outlined under "Option 1" or "Option 2": http://mdmower.cmphys.com/htc-drivers-adb-recovery/
Xposed?
No.
XDA:DevDB Information
CyanogenMod 12.0, ROM for the HTC One X
Contributors
Thömy
Source Code: https://github.com/CyanogenMod/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Testing
Created 2014-12-17
Last Updated 2015-02-28
Here are instructions to enable or disable some features that were previously in the advanced settings menu. Currently untested with Lollipop!
Button Backlight Notifications (enabled by default)
Button backlight notifications are enabled/disabled by settings write permissions on a special file. To disable them remove the write permission for the sysfs file with
Code:
chmod 444 /sys/class/leds/button-backlight/slow_blink
Only execute it while the lights are not currently blinking.
The newest kernel also contains the ability to limit to the notification brightness. Do
Code:
echo 1 > /sys/class/leds/button-backlight/slow_blink_brightness_limit
to limit the brightness to your normal button backlight brightness (which you can adjust in the settings).
Fast Charge (disabled by default)
Fast charging is disabled by default and can be enabled with
Code:
echo 1 > /sys/devices/platform/htc_battery/fast_charge
Sweep2Wake (disabled by default)
Code:
# Enable s2w
echo 1 > /sys/android_touch/sweep2wake
# Adjust the needed swipe length. 325 for one button (default), 500 for two buttons and 850 for three buttons
echo 500 > /sys/android_touch/s2w_min_distance
# Disable direction independent behaviour
echo 0 > /sys/android_touch/s2w_allow_stroke
Nvidia SmartDimmer (disabled by default)
Now called "Adaptive backlight". Setting was moved to the "Display & LED" menu.
All settings where you manually have to execute a command are not persisted between reboots. You can use a third party app that supports toggling the settings or you can put the commands into /data/local/userinit.sh to apply them at boot.
The New Storage Layout
To combat the space problems on Lollipop due to ART builds will be switched to the /data/media storage layout that is commonly used with newer Android devices.
The new partition layout will change our internal SD card be the /data partition. The internal SD card will also be located in this partition under /data/media. This means the 25GB can now be distributed freely between Apps, Data, Music, Picutres, Dalvik cache, ... that were previously on separate partitions. Moving apps to SD is unnecessary now.
The transition to the new layout requires a complete wipe including the SD card contents.
Advantages
Free disk space problems are largely gone because the sdcard and /data share the same place
Properly supporting UMS and supporting moving Apps to SD is getting harder and harder. This change will make both unnecessary
Disadvantages
2GB (size of the old /data partition) are “lost”
Breaks compatibility with all existing ROMs, recoveries and boot.imgs
Hopping between Sense and CM based ROMs will be nearly impossible
No more UMS, only MTP
Downloads
Recoveries using the old storage layout.
TWRP 2.8.1.0 (by teemo)
CWM
Recoveries using the new storage layout
TWRP 2.8.4.3 (by @teemo, @Thunder07)
Migration
Basic steps for switching to the new storage layout.
Flash a recovery using the new layout
Reboot to new recovery
Format /data (Wipe -> Format Data in TWRP)
Flash ROM (don't forget the boot.img)
SD Card Data Migration
This guide uses TWRP 2.8.4.x to convert your phone without losing data.
Boot into the TWRP recovery supporting the old layout
Make a backup (only /data needed)
Copy everything (including hidden folders) from the SD card to your pc
You can use UMS or MTP
This will include the backup
Reboot to fastboot and flash the new TWRP recovery using the new layout
Flash the boot.img from the ROM you are using
Reboot to new recovery
Format /data (Wipe -> Format Data)
Go back to Mount and enable MTP if it is disabled
Reboot the recovery
Restore your SD card backup to the Internal SD card
Use the “Internal Storage” device
Execute “adb shell chown -R media_rw:media_rw /data/media/0/” to fix the permissions
Restore your /data backup from the SD card
If you don’t see any backups then you might have to move /data/media/0/TWRP to /data/media/TWRP manually
Flash the new ROM
adb push and flash it or use adb sideload, it’s your choice
More Information
You'll find more information in the New Storage Layout for HOX Endeavoru thread by @teemo and in the New Storage Layout document by myself
wow....it's christmas gift from Thomy...
Thanks a lot for your great work..will test it soon.. I'm the first to see this post..
I hope i'm the first to test this Unofficial Build..
Update 1 (On 18/12/14 - 2:54 (GMT +1)):
-- Flashed the rom successfully -- No black screens, no random reboots -- Wait for atleast 5-10 minutes on the first boot, it does take a long time on the first boot, but it boots successfully, don't just rush and reboot repeatedly
----------------------------------------------------
First time I'm testing Lollipop build:
1.) yeah, the interface is really amazing, pretty smooth UI compared to Kitkat
2.) every little animation is blend to perfection
3.) You'll love the Lollipop from the initial look at Unlock screen..
What's working so far (tested till now):
Wifi, Bluetooth, GPS -- Working fine..
Apps -- almost every app worked perfectly,
Broken:
App2SD is not working-- yeah, known as many reported about it earlier.. when updating the app, it says out of storage, so the best way is to uninstall and then reinstall the app...temp solution..
As of now, it's a perfectly stable build...will update later in detail..
Haven't checked so far: Normal Phone call...I hope it's perfect too.. also i didn't check the mobile data...
Ohh can't wait :fingers-crossed:
Any screenshots?
kicikk said:
Any screenshots?
Click to expand...
Click to collapse
Added.
Wake up and see THOMY'post,it is very very wonderful day.thanks lot Thomy.
Sent from my One X using XDA Free mobile app
Thanks, will report back after a day or so of use.
Thömy said:
Added.
Click to expand...
Click to collapse
hey thomy thanks a lot for this man! You are literally rebreathing life into this phone LOL. I upgraded to an S4 in anticipation of lollipop but then it broke so im happy that there is progress for this phone!
im very tempted to install this experimental build but its been a while since ive done any flashing... i dont wanna ef anything up. Maybe ill wait for a more stable copy.... but knowing me i probably will end up flashing it.
Finally LP has arrived on HOX thanks @Thömy you are the Xman of HOX.
Downloading......
So I got the ROM installed smoothly, I was trying to install the GAPPS you provided and I got the following error log:
Installing files....
cleaning up and setting metadata...
set_metadata_recursive:some changes failed
E:Error in /sdcard/gapps-lp-20141109-signed.zip
(status 7)
Installation Aborted
Click to expand...
Click to collapse
btw while installing the ROM i got this message at the end but it said install WAS complete:
Warning: No file_contextscript succeeded: result was [0.200000]
Click to expand...
Click to collapse
do you guys know what this is for?
I am going to try redownloading the GAPPS again and try flashing it again.
EDIT: Tried it again, didnt work.
Also, the ROM is running very smoothly from what i have used so far. The cell data doesn't work? I think you should mention that in the OP but otherwise nice job looking forward to the stable releases!!
----
from some research online, its due to the recovery I have on it? I'm at CWM version
Excited / Cautious
@Thömy Thanks
I'll wait & see how things go before downloading it, I have a question about project volta? the battery optimization thing Google did for Lollipop, does it work for the HOX? my battery has seen better days
I've installed the Rom and Gapps without any issues...
PaKii94 said:
So I got the ROM installed smoothly, I was trying to install the GAPPS you provided and I got the following error log:
btw while installing the ROM i got this message at the end but it said install WAS complete:
do you guys know what this is for?
I am going to try redownloading the GAPPS again and try flashing it again.
EDIT: Tried it again, didnt work.
Also, the ROM is running very smoothly from what i have used so far. The cell data doesn't work? I think you should mention that in the OP but otherwise nice job looking forward to the stable releases!!
----
from some research online, its due to the recovery I have on it? I'm at CWM version
Click to expand...
Click to collapse
Yeah, i guess, you have to update your recovery to the latest recovery.... I have installed it without any issues in philz latest recovery..
I haven't tried using mobile data...but most of the other features and apps work without any hiccups...i must say this is way too good for unofficial build.. great work by Thomy..
Thanks for the great ROM again everything is working fine and is nice and smooth :good:
raminjpr said:
Yeah, i guess, you have to update your recovery to the latest recovery.... I have installed it without any issues in philz latest recovery..
I haven't tried using mobile data...but most of the other features and apps work without any hiccups...i must say this is way too good for unofficial build.. great work by Thomy..
Click to expand...
Click to collapse
well i updated my CWM Recovery and now reflashing the roms. wish me luck!
EDIT: completed yay time to setup and test out. Thanks again OP!
Everything seems to be working perfectly except Mobile Data.
Its amazingly beautiful and smooth Great preview we are overwhelmed.
Thanks @Thömy
Anybody tried flash it with TWRP 2.8.1. 0?does it work?
Sent from my Galaxy Nexus using XDA Free mobile app
So data is working on that build?
Nevermind, saw it's not working atm..
Tapped from another Dimension
DumbleCore said:
So data is working on that build?
Tapped from another Dimension
Click to expand...
Click to collapse
You mean Mobile data network?
Sent from my One X using XDA Free mobile app
This is a CyanogenMod 12.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y). Support for G800M is untested so far.
DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE
Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
Hence please do not ask for support or ROMs for the G800H.
Working features
Receiving and making calls
Hardware sensors (Light, Orientation, Compass, Proximity, Acceleration)
Audio
Bluetooth (audio in HFP seems to be distorted with at least some headset devices)
Wifi
HW accelerated GUI
USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
Camera (pictures+video: Back+Front)
MTP storage
IR
GPS
NFC
Non-working features:
Fingerprint scanner (no app for tests found)
Pulse sensor + Step counter (no app for tests found)
Hall sensor
SELinux
Known issues:
See the Bug Report section of this thread
Disclaimer:
You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
Click to expand...
Click to collapse
Before you start:
Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.
Download:
Odin3-v3.07 (it is contained in CF-Auto-Root)
TWRP 2.8.7.0 recovery image [08/07/2015] (AndroidFileHost Mirror)
CM 12.1 ROM for G800F/M/Y (AndroidFileHost Mirror)
Google Apps (contains Google Play, ...) for Android 5.1.1 from Jajb (Recommended) or the one that suits you best from Consolidated GApps.
Install recovery:
Reboot your device into Odin mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
Confirm the following warning message with the Volume-Up button.
Connect your device to your PC via USB
Make sure the device driver's are installed on your PC
Start Odin
In Odin select PDA and select the recovery image (recovery.tar.md5)
Check that only "Auto Reboot" and "F. Reset Time" is set
Click on "Start": the kernel image should be flashed now and the device should reboot afterwards. By flashing the recovery, your warranty will be void.
After the recovery flashing process was successful, power of your device. If not restart into Download mode and flash again or flash the stock rom.
Before you flash:
You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 12.1.
Flash CyanogenMod:
Reboot into recovery mode (Press Volume-Up + Home + Power button)
If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
If you haven't copied the installation files yet, you can now copy the GApps and CyanogenMod zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
Install the CM 12.1 ROM zip-package
Install the GApps zip-package
Reboot the system and enjoy a Lollipop
How to root:
No SuperSu is needed as CyanogenMod already comes with integrated root support. Root access is disabled by default.
You normally do not need root access. If you want to activate root access for apps, do the following:
Open the Settings menu, select "About Phone"
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.
In case you want to go back to the stock ROM:
lf you do not have the latest ROM for the G800F you can download it from SamMobile
Reboot your phone into Odin mode
Open Odin on your PC and connect your smartphone with your PC via USB
If you have a zip-file unzip it so that you have a .tar.md5 file
In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
Normally the stock rom fails to boot as the data from CM12 is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
Reboot
Changelog
Code:
15/08/2015:
* Synchronize with newest CM 12.1 sources (contains stagefright patches)
08/07/2015:
* Update to latest CM-12.1 sources (LMY48G)
* Camera app supports saving pictures to external SD-cards
* Partition sizes of system and data slightly reduced to avoid "unable to mount /system" failure during installation on some variants of the G800 (e.g. G800Y)
19/05/2015:
* Update to CyanogenMod 12.1 (Android 5.1.1)
* Merged Kernel-sources from G800FXXU1ANL1
* Re-enabled NFC
* TWRP update
11/04/2015:
* Update to CyanogenMod 12.1 (Android 5.1)
* Update to TWRP 2.8.6.0
* Fixed blinking capacitive touchkey lights
* Fixed unresponsive touchscreen on wake-up
* Added support for Automatic Brightness control
* Added advanced touchscreen settings (Glove and Hovering mode)
* Use open-source Light-HAL, Power-HAL and IR-HAL implementations
* Updated Power-Profiling
23/03/2015:
* Fixed non-working mic on incoming call issue
* Fixed non-working menu-button
* Synchronized with latest CyanogenMod sources
This section is for developers:
A README file with build instructions can be found here:
Code:
https://github.com/cm-3470/patcher_kminilte
Sources:
Code:
https://github.com/cm-3470/android_device_samsung_kminilte
https://github.com/cm-3470/android_vendor_samsung_kminilte
https://github.com/cm-3470/android_kernel_samsung_kminilte
https://github.com/cm-3470/android_device_samsung_smdk3470-common
Developers welcome
At the moment the G800F/M/Y specific port of this ROM is only done by one person (hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.
Thanks to Unjustified Dev from Team Regular. As the S5 mini (G800F/M/Y) and the Galaxy Light are quite similar we worked on this together.
XDA:DevDB Information
[G800F/M/Y][ROM][5.1.1][LMY48G] CyanogenMod 12.1 for G800F/M/Y [Alpha 15/08/2015], ROM for the Samsung Galaxy S5 Mini
Contributors
hennymcc, Unjustified Dev
Source Code: https://github.com/cm-3470
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery [version from 15/08/2015]
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-15
Last Updated 2015-09-22
FAQ:
Question:
I'm trying to flash this rom but it says to me: "This package is for kmniltexx, kminiltedv, kminilteub; this device is kminilte. E:Error executing updater binary zip ...."
Answer:
The device names were changed with the newest CM12 build to be able to distinguish between G800F (kmniltexx), G800Y (kminiltedv) and G800M (kminilteub) as all of them are kminilte devices. The new builds of TWRP and CM12 detect the correct device at runtime.
Older TWRP releases (for example that of RVR in another XDA thread) still detect the device as kminilte (instead of kmniltexx,...) and hence are not able to install the new CM 12 releases so please do not install RVR's TWRP if you want to install CM 12. Always use the TWRP image linked in the first post of this thread.
Reserved
As none of the pre-alpha testers reported any issues with NFC, I assume that the broken NFC of LS97 and me was caused by electrostatic discharge while removing and re-inserting the battery (at least I did this hundreds of times). In addition we already broke our NFC some weeks ago after having used 5.0.2 for some while, so this ROM should be at least as safe as 5.0.2 and there is no direct link between the custom ROM and the broken NFC.
Just as a precaution: to avoid damage of the NFC-chip (which is connected to the antenna in the battery) by electrostatic discharge, use the power button to reboot the smartphone instead of removing the battery.
What a nice first post for this new ROM
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
CTXz said:
Are the links above the same like the ones you posted into the comments in your 5.0.2 thread? Just so i know if something has changed in thos links obove.
Click to expand...
Click to collapse
Exactly the same.
hennymcc said:
Exactly the same.
Click to expand...
Click to collapse
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
CTXz said:
Ok thanks. Also have you figured out whats up with the screen turning on after locking delay since turning off nfc didn't result changes. Also it doesn't happen always. Only sometimes
Click to expand...
Click to collapse
I haven't looked any deeper into this so far.
So how is the Final version going to look like if this is Alpha... Damn [emoji41]
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
CTXz said:
Hey. What i did is just rather turn them off completely.
Settings > Buttons > Backlight > Uncheck Illuminate buttons
Else there is no fix, due cm12.1 universality it doesn't work with the buttons like the stock ROM did.
Click to expand...
Click to collapse
Well tried that but The setting just changes back to the default.
Nielsieboy said:
Well tried that but The setting just changes back to the default.
Click to expand...
Click to collapse
Ok thats wierd. Have you wiped all partitions you needed to like said above ( dalvik cache, cache, system, data )
If it gets verry anoying you might give a reflash a try. Also i know this sounds funny but did you atleast try rebooting the device?
---------- Post added at 08:55 PM ---------- Previous post was at 08:50 PM ----------
Also did you give this a shot https://play.google.com/store/apps/details?id=com.deskangel.kblight
There are many more apps on gplay for button backlight. Just search it
i've flashed it yesterday over the old buidl (without full wipe). so i got FC's on several google apps.
after flashing several different gapps for lolipop 5.1 the errors with the FCs are still stere.
then i've made a full clean install with full wipe and installed the pa gapps from the 04-10-2015 and now everything works fine & smooth.
tommorrow ill gonna test the bluetooth cause on the old build there were sond errors....
but for now it looks very good
I've discovered something. If you enable LiveDisplay the device will lag a bit.
And when you think I did a full wipe and reflashed the ROM, just to find out that my problem was related to this little feature...
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Nielsieboy said:
I have a small problem, everytime i touch the screen my capacitive buttons light up. I already tried disabling this in the settings but it doesn't let me do that.
Anyone have soms advice ?
Click to expand...
Click to collapse
it doesnt let you do that? why not? for me it worked...(i hate those lights too)
DerMoeJoe said:
@henny: can you confirm that this mod will work on your build ?
It sounds very good
Click to expand...
Click to collapse
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
LS97 said:
I personally don't see a lot of advantages in it and would not recommend it, especially for this phone, regardless of whether or not it's compatible.
Click to expand...
Click to collapse
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
CTXz said:
Why not. I use it for daily use and i have to say i have less bugs than my stock rom had.
With that it boosted my phone like hell and there is no more lagg when oppening apps, going to the homescreen, scrolling through apps and no more touchwiz. Plus you got the newest android up to date. That fixed some app issues with my phone ( i no longer got the app not compatible error after lolipop. Oh yeah and no more bubble sounds when pressing on something Thaankk you! There are many other things that i preffer over the stock rom. So i see so much potential in this ROM and would preffer it as much as i can if you got a s5 mini g800f.
Click to expand...
Click to collapse
The only way to find out if it works is to try it. So if you want this feature you can flash that mod and report if it works .
I personally do not need it as I want the phone to turn off when I "power it off".
Note that the mod could cause stability issues. So before reporting bugs here you should reinstall CM 12.1 first with a full wipe and check if the problem is still present.
Edit:
this was supposed to be an answer to DerMoeJoe's question about the QuickBoot mod