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.
Related
DiscontinuedI'll make this short and sweet. Thanks to RaiderX303 recent work porting over clockwork recovery we can now flash roms in the update.zip format directly from sd with no need for a pc to flash a new rom. This allows most importantly the ability to to create Nandroid backups and restores.
Using RaiderX303 method I repacked my favorite ROM into a zip package ready for Clockwork Recovery.
Rom is Kouno.Takaaki's HD2ONE 0.3.6. This is based on his original release and everything should work just as it did before on this rom.
Please don't ask questions as to why this doesn't have xyz, or sense this or that, this is a close to stock vanilla android mod, if you want pretty sense skins, or don't like the way it looks, then get a sense rom.
His original thread http://forum.xda-developers.com/showthread.php?t=823471
Intrid.gz is updated to his newest version as of 1.2, details here http://forum.xda-developers.com/showthread.php?t=898067
Kernel is now Prj's .3, which is based off Hastarin's 8.6, modified for nand use. Feel free to update using the method in the Intrid.gz thread if you want a different kernel.
First you need to install clockwork recovery which has been ported by RaiderX303...
http://forum.xda-developers.com/showthread.php?t=898913
Then ...
How to flash;
1: Boot into Clockwork Recovery
2: Select install zip from sdcard
3. Select choose zip from sdcard
4: Select ROM file (HD2ONEupdate.zip) and then confirm
5: Wait for All Done! message
6: A wipe is recommended but not always required, if you experience force closes or things not working, try wiping before posting problems.
Please remember, I am not the original chef for this ROM, I have only repacked it into a format suitable for clockwork recovery so keep questions related to the underlying rom to the original forum. Also if you haven't read anywhere else, when you switch over to clockwork recovery method your userdata will be wiped so backup accordingly.
Download Link:
V. 1.2 http://www.multiupload.com/86KDPU1BXO
Wifi Tether App: http://www.multiupload.com/XVVRIFG83F
V. 1.1 http://www.multiupload.com/UR329DN289
V. 1.0 http://www.multiupload.com/06Q70SASLA
Changelog:
Version 1.2 01/07/2011
-Problems with intrid.gz not recognizing /.data/config.txt should be resolved. Changes to config.txt should now work properly.
-Kernel updated to prj's .3
Version 1.1 01/05/11:
-Updated Intrid.gz to Kouno.Takaaki v1.1 Ramdisk(should make update systemfiles,kernel,etc easier) See original thread for more details http://forum.xda-developers.com/showthread.php?t=898067
-Added Google Talk app and Google News/weather widget to systemapps as not downloadable from market, for all other google apps, ie. gmail,youtube, etc, download the newest version from market.
-Small modification to default MMS settings for Tmobile US users to fix mms send issues. If creating new data img settings will load by default, otherwise goto settings,wirelessnetworks,mobilenetworks,accesspoint names, menu button, reset to default, this will get you updated mms settings for tmobile us.
-If coming from 1.0 you should be able to do a no wipe update in recovery without problems.
Verson 1.0 01/04/11:
- Initial Release
Credits to;
Kouno.Takaaki for his Rom
RaiderX303 for his work on porting Clockwork Recovery
Cotulla + DFT - For MAGLDR and all the great work thats gone into NAND on the HD2
CyanogenMod Team - For the great recovery that allows flashing custom roms
Anyone else who has contributed to android on the HD2
Thanks, wanna try..
What a beautiful day
what initrd and zimage did you use for this rom.zip?
thanks..
rmnet or ppp? thanks!
Hi, I try to change the density with 200 in /system/build.prop. But it is not work when I restart my phone?
Is there a problem? I saw that the rom is based on CM build. But I can change it on CM 6.1.1 build. Could you please help me to take a look?
flashed fine but then just sits at the green htc screen...
did hard reset..same thing...boots to green htc screen.
thnx to titanium backup im back where i started 15 mins later
Does it support data.img on sdcard?
tried this but getting a nand kernel open failed when magldr tries to load the rom any ideas?? Do i have to supply my own kernel??
Ricey
Ok to address some questions and issues.
Build is RMNET, again based on original Nand HD2ONE.
Kernel is proj .2 which is based off of Hastarins Kernels.
Intrid is also from HD2ONE nand build so... it supports data.img to sd (off by default), therefore you must create a folder in the root of your SDcard and do the following:
Name folder. ".data"
Inside ".data" , Name a new txt file "config.txt"
Then you can add any of the following lines:
data2sd=0
- default nand userdata
data2sd=1
- enable data.img support
data_size=512
- size of data.img, only work when data.img support enabled
- default 512
lcd_density=240
- change the size of icons
- default 240
gps_zone=us
- country code, us, fr, jp, etc
- default us
As for people having issues booting or getting stuck at green htc, I would give a few pointers, if first boot then keep in mind the build is creating a new data file and first boot could take 10 minutes, so be patient. Second if getting issues with magldr saying it can't load a particular file/kernel, you probably had a bad flash and I would start by doing a wipe within clockwork recovery and reflash.
bigfoots1 said:
flashed fine but then just sits at the green htc screen...
did hard reset..same thing...boots to green htc screen.
thnx to titanium backup im back where i started 15 mins later
Click to expand...
Click to collapse
Fix permissions after flashing could help
Works just as HD2ONE should - flawlessly Thanks a lot
ok, I thought i had waited 10 minutes...
wasnt sure if it was building or not.
i will try again and wait it out.
like i said titanium backup to the rescueif needed anyway...
Thank you!
drewestate said:
Ok to address some questions and issues.
Build is RMNET, again based on original Nand HD2ONE.
Kernel is proj .2 which is based off of Hastarins Kernels.
Intrid is also from HD2ONE nand build so... it supports data.img to sd (off by default), therefore you must create a txt file in the root of your SDcard and do the following:
Name new txt file ".config" (without quotes)
Then you can add any of the following lines:
data2sd=0
- default nand userdata
data2sd=1
- enable data.img support
data_size=512
- size of data.img, only work when data.img support enabled
- default 512
lcd_density=240
- change the size of icons
- default 240
gps_zone=us
- country code, us, fr, jp, etc
- default us
As for people having issues booting or getting stuck at green htc, I would give a few pointers, if first boot then keep in mind the build is creating a new data file and first boot could take 10 minutes, so be patient. Second if getting issues with magldr saying it can't load a particular file/kernel, you probably had a bad flash and I would start by doing a wipe within clockwork recovery and reflash.
Click to expand...
Click to collapse
15 minutes and counting...still sitting on green htc screen...
please explain...
if there are extra steps needed then why isn't that mentioned prior to this?
schremer said:
Fix permissions after flashing could help
Works just as HD2ONE should - flawlessly Thanks a lot
Click to expand...
Click to collapse
Since this incorporates Clockwork Recovery, can this now be used to swap kernels as well?
25 minutes at the green htc screen. I think its safe to say this has nothing to do with the data file be created. it doesn't work.
followed instructions, it flashes the zip and after reboot it just sits at htc screen...
I think im done messing with this untill i see others who have actually got this to flash and boot properly...
if there is another step then please state it...nebulous comments like "change permissions" are useless
Thanks..
bigfoots1 said:
please explain...
if there are extra steps needed then why isn't that mentioned prior to this?
Click to expand...
Click to collapse
It depends Owning android phone before used to fix permissions after flashing.
Sent from my HTC HD2 using Tapatalk
This build is freakin good
But I have a little problem with me settings.. if I want to go to settings -> sounds the whole settings fc
Tried it with fixin the permissions in the CW mod, but didn't work.. someone else has this issue?
lol..so basically your talking out your ass?
schremer said:
It depends Owning android phone before used to fix permissions after flashing.
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
bigfoots1 said:
lol..so basically your talking out your ass?
Click to expand...
Click to collapse
I'm not sure if understood you right. Anything personal?
This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Galaxy S.
All Samsung Roms are running ontop of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you're not able to flash any kernel or run any filesystem you want. Use it as it is.
Only data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix").
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from earlier CM7?
Do a Nandroid Backup!
Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=galaxysmtd
Compatible Radio Images (>= Nightly 15): http://codeworkx.de/download/cyanogenmod/
Supported devices: GT-I9000, GT-I9000M, GT-I9000T
before flash is recommended to check the md5sum
FREQUENTLY ASKED QUESTIONS:
http://forum.cyanogenmod.com/topic/24169-faq-cm7-on-the-samsung-galaxy-s/
CYANOGENMOD WIKI:
http://wiki.cyanogenmod.com/index.php?title=Samsung_Galaxy_S
HOWTO BUILD FROM SOURCES:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_GalaxySMTD
ADDITIONAL INFORMATIONS:
Maintainers:
- atinm - http://twitter.com/atinm
- codeworkx - http://twitter.com/codeworkx
- coolya - http://twitter.com/dumdidum
- guiperpt - http://twitter.com/guiperpt
- unhelpful - http://twitter.com/unhelpfulone
Irc:
- Host: irc.freenode.net:6667
- Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
- Generic Changelog
- CyanogenMod Source Twitter
- Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
If You Have Any Questions, Please Refer To This
CM7 QUESTIONS & ANSWERS XDA THREAD
http://forum.xda-developers.com/showthread.php?t=1067074
Regards,
~drz
have i ever told you i love you? i'm pretty sure i have but i'd just like to tell you again. i'm sorry for this offtopic post but i'll edit it later to something useful. just wanted to show my affection.
This should be it since the beginning.
Clean thread. That's how I like it
Excited for the Coming Soon patch!
Reboot Recovery
Woah! Can't wait to try this.
The quick troubleshooting post.
This post contains a compilation of problems/issues and answers provided in this thread and earlier threads. Not all answers are tested by me and I will in no way guarantee that this wont mess up your phone.
You know, watch your kittens. They might be eaten by following the advice written down here.
DETAILED INSTALLATION INSTRUCTIONS CAN BE FOUND HERE.
rschenck wrote a very nice (and updated) guide for how you install CM7 on your SGS these days.
Things have changed quite a bit recently, so even if you installed it two weeks ago, you may want to check this one again.
What do people mean with "correct" bootloader? How can I make sure I have the right one?
Do NOT install directly on top of existing Samsung 2.3.3 firmwares or other firmwares based on this (like Darky's 10). Similarly, don't install directly on top of Eclair.
See this very easy guide on the android soul for flashing XXJPU, which is Froyo with the correct bootloaders needed..
I'm not sure I understand these procedures. Can you draw it out for me?
Anticipating this very question, rschenck actually did draw out a flow-chart for you.
See here.
But I'm not using the I9000, I'm using something else...
codeworkx provided a reference list you can check to ensure you are getting the right files.
After flashing the initial CM kernel I can't get CWM Recovery to work. It just displays some weird image
CWM Recovery might have different keymappings from the ones you are used to.
- Volume keys: Naviagte up and down in menus
- Power button: Select item
- Home key: Show/hide menus
If you are only seeing a weird image, chances are you've hidden the menu by pressing the home key. Try pressing it again
I can't find Cyanogenmod nightlies in ROM Manager
Yes. CM7 for the SGS is now mainlined and supports ROM Manager for nightlies, should you have the premium version. If you have the Premium version, follow these very graphic instructions to configure ROM Manager for nightlies.
To install from MIUI (courtesy of runedrune)
- Reboot into recovery using 3-button-combo
- Choose "mounts & storage" and format system, data, cache, datadata
- Do not apply the initial-file.
- Apply the latest update
- Apply the latest gapps (which can be obtained here. You want the one with -gb- in the name )
- Done. Reboot
Odin doesn't recognize my phone anymore and I want this fixed in case I mess something up
You will probably need the Nexus S drivers (which supposedly is really just some updated Galaxy S drivers).
If Odin for some reason don't see your device when connected, make sure the old Galaxy S drivers are uninstalled and removed. Bilboa1 gives some good hints about how to make sure your drivers are actually fully removed. Do check this before proceeding to install the Nexus S drivers.
After you have installed the Nexus S drivers, plug in your phone. Windows should now install some drivers, but you are not done yet. When using download-mode your phone will show up a little differently to Windows, so put your phone in download-mode and plug it in, with neither Kies nor Odin running. You will probably see Windows installing some more drivers.
After doing this, Odin should hopefully be able to recognize (and flash) your phone.
IS THIS "FOR EVERYDAY USE" NOW?
It depends. If you have to ask, it probably isn't.
I've flashed this and decided it is not ready for me. How do I flash back to stock ROMs?
Get the appropriate firmware you are interested in, flash as usual using Odin, but check re-partition and use the 512 pit-file.
For pre-rooted stock-images, you can use EZBase as shown here (also includes download links).
OTHER STUFF / KNOWN ISSUES AND SOLUTIONS
Please take a look here to see if your issue is mentioned and has a known solution before posting.
After flashing CM7 I get strange colours on my screen during boot
You do not have the correct bootloaders. Basically flash 2.2.1 following this article and then redo the CM7 installation. All should be fine.
Guys! Guys! I cannot find Android Market!
Google stuff is not included in CM7 by default. Download and apply latest gapps from CWM. You want the "universal" one with "-gb-" in the name.
But I want the latest gtalk with video and all that fancy stuff
got_milk was nice and uploaded some stuff. Beware though that lots of people are reporting this to force-close a lot, and that's not just on SGS CM7.
Can I run Samsung apps like Memo, Camera etc on this firmware?
No. Sorry. All Samsung apps depend on TouchWiz libraries which can only be found in Samsung firmwares.
How do I get additional themes for CM7 themes chooser?
Check the themes forum here on XDA or search for "CM7 themes" on Android market.
Once installed, the themes will be available in the themes chooser yes. According to the devs should reboot to fully apply the theme, but if you want to avoid reboots Android market might have something for you.
Things used to work, I applied a nightly update and now everything force-closes
Try wiping cache and dalvik cache in CWM. You should do this every time you install a new update.
Does CM7 need a lagfix?
CM7 uses ext4 (for /data) and yaffs2 (for everything else). CM7 does not use Samsung's RFS which was the main cause of poor performance on Samsung firmwares.
So no, your system is already lagfixed, you don't need to apply a lagfix and according to the developers very bad things will happen if you try to apply one anyway.
My current ROM has a lagfix. Do I need to disable that?
Probably not.
If you have a 2.3.3 ROM with 2.3.3 bootloaders, you will want to do a full wipe to stock 2.2.1. See above. In this case you no longer have a lagfix anyway and don't have to worry about it.
If you have a non-2.3.3 ROM with a lagfix, you don't have to disable it. All your partitions will get wiped by the installer anyway and so will your lagfix.
For whatever reason, I want to flash a custom kernel
You can use custom-kernels, but CM7 is a work in progress with new kernel-revisions popping out with every release. Make sure you flash a kernel which is compatible with the nightly you are running. Also: Do NOT flash via Odin, flash via CWM.
rschenck has a very good post on this.
If all you want is a "voodoo kernel" for voodoo sound, just (buy and) install Voodoo Control Plus from the market. It will load the required kernel-modules while you can stay on the stock kernel, making the lives of the developers much easier should you encounter bugs.
Is it possible to flash my own CSC from recovery after installing cm7?
According to the devs, this should not be needed.
Flashing other modems/radios
(Courtesy of GrimVarg: http://forum.xda-developers.com/showpost.php?p=13399590&postcount=8117 )
Odin will not work and it might **** **** up. The reason is that Odin and heimdal does not understand the CM partition layout and will just write the modem where it thinks is should be. Overwriting other stuff in the process.. So you need to use the specific update zipfiles on teamhacksungs sourceforge page
Click to expand...
Click to collapse
Instead of using Odin, download radio-packages from the following link, transfer to your phone and flash via CWM:
http://sourceforge.net/projects/teamhacksung/files/galaxys/
I want to keep my 850 band, and I don't recognize any of the modems on the sourceforge page
Lorssoth says "use KC1" and robbiev80 posted some download links you might be interested in.
Does external SD card work with cm7? Thanks!
It does. Make sure you have the proper bootloaders before installing as mentioned in the first part of this post. EZBase can be used for this.
External SD card will get mounted as /mnt/emmc. This may not be visible to all apps. If you desperately need the contents visible to apps only looking in /mnt/sdcard, create an empty directory there and remount the /mnt/emmc there as well:
Using either the terminal emulator or adb shell:
Code:
su
mkdir -p /mnt/sdcard/external_sd
mount /dev/block/vold/179:9 /mnt/sdcard/external_sd
Note: This is only a temporary fix for when needed. It will cause issues when you try to use USB sharing later. Write the following to get things back to normal:
Code:
umount /mnt/sdcard/external_sd
USB sharing doesn't work
Try installing the Nexus S drivers, instead of the Samsung ones.
After installing this camera doesn't work
Try locking and unlocking your phone. No really.
After installing this I cannot get any data-connections apart from wifi
There is a problem with RIL (radio interface layer)-polling. Lock and unlock and you should be OK.
If this sounds cumbersome, mobilescooby claims that installing Juicedefender somehow fixes this for him and that he no longer needs any lock and unluck boot-rituals.
This issue should now be resolved.
After doing this I still cannot get any data-connection apart from wifi
You might need to configure APN settings. Normally your network-provider will have this information on their homepages and some even offer to send them to you over the network.
After installing this I cannot send and/or receive MMSes
See above: You might need to configure APN settings. Check your provider.
After installing CM7 I cannot connect to my wifi-network
It might be related to what channels you have enabled on your phone. If your wifi network is using channel 12 or higher, you may need to enable those channels on your phone.
Go to Settings/Wifi & Network/Wifi settings/Advanced/Regulatory domain. And try not to be in violation of local laws with regard to channel usage
After installing CM7 I cannot connect to 802.1x EAP Wifi networks
This is seemingly an issue with lots of custom kernels and even some of the Samsung Firmwares. Yours truly can't get it to work at all, not on CM7 nor Samsung's JVB firmware.
Other people have reported that forgetting the network and adding it manually, by entering the SSID (with correct casing) and filling in all the details themselves have solved their problems.
YMMV
After installing CM7 I cannot charge my phone to 100%. WTH
No actual firmwares allows you to charge the battery to 100%, but stops a little bit before it reaches that point. This is to protect the battery from overcharging and should (in the long run) give you much better battery-life.
While stock firmwares from Samsung shows that the phone is 100% charged, this simply isn't true and is just UI-candy to make you all feel comfy. It's really charged to something around 94-98 percent.
So if your phone stops charging around that point, everything is normal, and the only new thing is that your phone is no longer lying to you
My GPS performance is terrible
Welcome to the world of Samsung Galaxy S GPS flux. Things you can try to improve on this includes the following:
- Install faster fix from Android market. Ensure you have the best time-server for your area chosen.
- You can also try AngryGPS, which siberian tiger was nice enough to upload.
- If all else fails, you can also try to flash a radio with a good GPS reputation. For flashing radios, see the appropriate section of this post. For some detailed post about the different radios eeyunopper posted this link and this link. (With ZSJPG I am getting decent result, YMMV)
Auto brigthness is kinda not-worky
You can try the presets outlined by Arkymedes right here.
How do I configure proxy settings?
(Thanks to runedrune)
If you are used to looking for proxy settings under Settings/Wifi & Network/Wifi settings/Advanced, you wont find it there.
Using either Launcher pro/ADW Launcher or another launcher which lets you create shortcuts to activities:
* Long hold on some open space on your launcher
* Select (Custom) Shortcut
* Select Pick your activity/Activities
* Scroll down to settings and click this
* Scroll down the long list and you should find proxy settings
You now have a shortcut to configure proxies as usual.
This "headphones mic on mute + instant music after call bug" is really irritating
If you are using Samsung or Nokia headsets, this is due to a problem on their part. See Arkanius' post right here.
Other things I should be aware of?
- Don't use 2G/3G data-switching. Period. At least not while the data-connection is active.
Not trough widgets, tasker or any other means. Seriously. Should you do this, you might end up having to restore nandroid backups or doing factory resets.
This report has details on more sophisticated ways of cleaning up which may lead to less data-loss, although not everyone can get it to work.
*subscribes*
nice work with the GPIOs, camera and other parts !
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
eeyunopper said:
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
Click to expand...
Click to collapse
I've already notified the mods to close / lock the other one ...
Good job on the clean house, everything is working great on my phone and very speedy
Mortify1 said:
Good job on the clean house, everything is working great on my phone and very speedy
Click to expand...
Click to collapse
The same for me My phone is working so great and very very speedy
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
I'm waiting the upcoming improves on camera in great expectation.
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
no
after format system/data/cache
just apply the last update
runedrune said:
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
Click to expand...
Click to collapse
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Nice things are comming... I hope for battery improvemant and radio FM. Since we got GPS, Compass is not so important but nice additional that save battery/make quicker fix.
Codeworks, do you got any rodemap?
Tantrico I said:
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Click to expand...
Click to collapse
nope. just flash that file. i made the same switch from miui to cm7 two days ago
@codeworkx , if reboot in recovery works = nightlys updates for ROM Manager? !
Enviado desde mi GT-I9000 usando Tapatalk
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 is a collection of tools and apps that I have produced to try to help users of Alliance ROM and various Kernels. Some of these apps may work for other ROMs or Kernels but I must stress that these will not have been tested.
Contents
My Apps - Apps or Flashable Zips that I have produced to address specific needs.
Guides - Guides I have produced to take you through fixes or modifications.
Other Stuff - Useful bits from others.
Bespoke Stuff - Custom stuff that is not Rom or Kernel specific.
Rom Share - Links to Mirrors I have set up for Roms I use with slow download speeds from their original host.
Other useful Links:
Alliance Thread
Alliance OTA Submission Thread
Rom Share - Mirror of ROMs and Kernels I use where the main link is very slow.
Adblock Hub - Some adblockers saved from the Play Store cull.
Apps
My Apps - These are Apps or Flashable Zips that I have created for Alliance Rom or a specific Kernel
SymlinkSD - App that runs on boot and Symliks the External SDCard as /mnt/sdcard - Only needed for Kernels that display this behaviour.
Reset Fuel Gauge - Function to rectify weird battery readings, code taken from Dori's kernel and turned into an app.
Tweaker - Allows you to toggle the following options on your phone if the installed Apps support it:
Camera Silent Menu Item
Disable auto convert SMS to MMS
Change the maximum number of contacts that can be joined to another contact
TogMods - Auto enables any Toggle Modifications you have made on reboot instead of having to make a change to enable them.
AccuWeather Widget - Flashable Zip for either Normal (with Background) or Transparent
LS Fix - Repairs Issue on some LS8 ROMs where the Lockscreen does not come up and a long press of the power button restarts the phone.
Stock Messaging no Convert and Sent Time - Stock Messaging app with the Convert to MMS function disabled and displayed times reflect the sent time not received time.
AOSP Themed Messaging no Convert and Sent Time - AOSP Themed Messaging app with the Convert to MMS function disabled and displayed times reflect the sent time not received time.
SilentCam - Camera app with Silent Option
CPU Idle - Allows user to specify the Scheduler used for CPU Idle for screen on and off as long as the Kernel supports it.
Crash Logger - Captures LastKmsg file automatically after an unexpected reboot. File is saved to SD and copied to Clipboard. Kernel must not have disabled Android Logging.
Boot Wifi - Automatically enables WiFi on Boot for ROMs or Kernels that deactivate WiFi on startup.
Auto Wifi - Automatically enables WiFi on Boot for ROMs or Kernels that deactivate WiFi on startup and renenables WiFi if it is enabled by the user and then immediately deactivated by the Kernel or Rom.
Cache Cleaner - Runs the Cache Clean feature from Dorimanx kernel as a stand alone application. Just run and that's it. It will show the Start Free Ram, End Free Ram and then close itself and remove from memory.
Rom Select - App for Dual Boot users to allow them to change Roms without waiting for STweaks to load first. Tested with Dorimanx, should work with Siyah as well.
The following Apps may no longer be required as they should be fixed.
Dori CamFix - Fixes problems with some CM and AOKP ROMS where the camera force closes when using Dorimanx Kernel.
Fake Notify - Fixes issue for users using AllianceROM where the Notification bar does not show up on boot.
Fake Notify Plus - Fixes issue for users using AllianceROM where the Notification bar does not show up on boot and also sometimes disappears during normal use at Random.
Crackle Stop - Automates TRB's method of fixing the problem of a crackling sound being produced along with notifications. Once installed run and you will need to grant SU access. You will then be presented with a Menu for your Normal 'Idle' mode, this should be the same as the awake idle mode set in STweaks, next you will be asked for an Alt Idle mode, this can be anything, just not the same as your normal mode.
Once set you will need to reboot for the fix to activate.
Once rebooted the app does what it needs to do over a 20 second period (not 20 seconds after the phone has booted as the app will probably be the last thing loaded - so to be safe I'd give it 2 or 3 minutes). You then need to let your phone get into Deep Sleep so leave it for a bit and then after that all should be OK.
Note this is not a one off fix, this process will run on each boot but you do not need to rerun the App unless you want to change the Normal Idle mode.
Guides
My Guides - These are useful Guides I have made to help with various ROM and Kernel Issues.
Swype LSx Fix - Problem where the Custom Dictionary stops working and saving new words when using Swype on LSx ROMS.
IMEI Recovery - Step by step guide on how to backup your IMEI and then how to recover should you need to. This an essential guide, as should you not be able to recover your IMEI your phone will become a very expensive Paper Weight.
Change System DPI Settings - Step by step settings to change the system DPI.
YouTube fix - How to fix the error signing in problem in YouTube.
Other Stuff - Useful bits from others
The Red Blur's Cave - The Red Blur's page of helpful hints and knowledge. Don't bother reporting a problem until you have checked here, this guy is the best resource for all things Galaxy S 2!
Dorimanx Kernel Discussion Thread - Discussion Thread for all things Dori, especially things that should not be posted in the Dev Thread.
HawkerPaul's ROM and Kernel Wipe / Nuke scripts - These scripts should be used before flashing new ROMs or Kernels to clear up all of the left behind bits from your old installation.
Stock Video Fix - Flashable fix for issues with the Stock Video Player Force Closing when opened from the App Drawer, usually only present with Dori and Siyah Kernels. Thanks TRB.
Auto Call Record Mod and Disable increasing Volume Mod - Mods for LSx based ROMs to enable Automatic Call Recording and disable Increasing Ringtone volume.
LSx Dual Boot Mod - Manual Mod to allow Dual Booting of Roms when one of them is LSx
Ficeto's Kernel - Flashable Zip of Alliance 6 and 7 stock kernel.
AC!D Audio Installer - For Alliance Rom
Instructions:
Download and flash through Recovery.
After flash Wipe Dalvik Cache and Fix Permissions
Once booted enter the following into a Terminal Prompt to test install:
su
mount -o rw,remount /system
aaengine
You shouldn't need to run the above command, the install should do it but just to be sure
Reserved 1
Alliance Rom FAQ
How do I install 7.02?
You need to uninstall the Rom Customiser that comes with the Rom then install the new one from play store (https://play.google.com/store/apps/details?id=com.ficeto.alliancemanager) once installed go into Rom Customiser and then OTA and select the updates.
OTA does not mean Samsung or System OTA.
How do I install 7.3? I can't find it in OTA.
7.3 is a full Rom and not an update. As such you need to download the full Rom zip from the OP on the Alliance Thread. Once downloaded flash it through Rom Customiser.
How do I flash the Stock Theme for 7.3?
During installation uncheck the box next to "Alliance Theme".
What can be installed through Rom Customiser?
Anything can be flashed through Rom Customiser as long as it is a Flashable zip, an Odin Tar file or an OTA download.
I have Downloaded a mod or update from OTA which I cannot flash through recovery. What am I doing wrong?
You need to flash these files through Rom Customiser which will then automate recovery. You cannot flash these independently.
What is the default blue colour used in the Rom?
Uncheck the Alpha box Colour Hex code #33b5e5
How can I get the Dandelion Lock Screen Wallpaper back?
Download it from here.
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
Glad to see it finally on xda :thumbup:
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk
Main ROM: AllianceROM v7.01 LSD
KERNEL : PhilZ Touch LSD 4.87 Fixed init version
(DEFAULT PROFILE AND SETTINGS )
MODEM : LS8
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex Pro
Root Manager : SuperSU 1.04
THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ and LS8 + tools to have a bug free rom and kernel + how to back up and RESTORE ROM OM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Current list of kernels on LSJ and pros and cons
http://forum.xda-developers.com/showthread.php?p=36698607
2.Rom Nuke / Wipe scripts
http://forum.xda-developers.com/showthread.php?p=36742265
3. GS2KERNELWIPE script
http://forum.xda-developers.com/showthread.php?p=36742198
4.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
5. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Changing the DPI
Change the Entire System DPI setting.
1. Open Root Explorer
2. Navigate to /System folder
3. Open the build.prop file
4. Scroll down to the 'Additional_build_properties' you are looking for the line
"ro.sf.lcd_density = 240"
The default value for the LCD density is 240, the lower the number the more on
the screen. 200 is a good value to start with.
Save the change.
5. Reboot phone for the change to become effective.
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
trevfee said:
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Click to expand...
Click to collapse
Thanks you so much sir trev for accommodating my request. I will test and if successful I will refer this to my colleagues.
Sent from my GT-N7100 using Tapatalk 2
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
nogo8888 said:
Thanks you so much sir trev for accommodating my request. I will test and if successful I will refer this to my colleagues.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Initial report: just working on note2.
Thank you so much sir.
Without this mod, i cannot access our internal website.
Sir can you post this playstore?
Sent from my GT-N7100 using Tapatalk 2
android ipsec vpn mtu mod
trevfee said:
Bespoke stuff
These are bits that have been requested by others for a specific requirement not Rom or Kernel specific.
MTU 1300 (tun0) - App to set the MTU value to 1300 for a VPN connection using tun0.
Click to expand...
Click to collapse
Since I requested this tweak, I would give a simple explanation on what it does and how to use it.
When your connecting to a ipsec vpn using wifi and having trouble browsing to your internal websites eventhough your connected to it. You can ping your internal network but the trouble is no browsing. The solutions are:
1. Tell your System Administrator to change the ip tcp adjust-mss to a lower value, in my case I used 1000 using 1841 cisco router. This prevents the packet from fragmentation. Packets when fragmented were dropped thus resulting to no browsing. If the Sys Ad refuses to do so because this may cause some issues to Windows users (browsing may slow a little bit), your best solution is to install this tweak.
2. This MTU mod sets the MTU value of your payload to 1300 via tunnel interface of your android device this avoiding packet fragmentation resulting to packet being allowed to pass through the tunnel interface going to ipsec vpn router.
How to use it:
1. Download the vpnc widget from playstore. https://play.google.com/store/apps/details?id=com.gmail.mjm4456.vpncwidget&hl=en
Configure your credentials. Then connect.
2. Once the vpnc widget has been connected open this app. Then you should have browsed your internal network.
Note: This tweak is needed only for wifi connections. If your using carrier data, then this is not needed anymore.
Please give thanks to the creator of this app.
I just gave him the code and he did all the stuff in making this app looks nice and easy to use.
Big credit to OP, trevfee and thanks to my neatrom family (Many40, Mr.Greg, ESD and others who helped me finding the code)
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
nogo8888 said:
Initial report: just working on note2.
Thank you so much sir.
Without this mod, i cannot access our internal website.
Sir can you post this playstore?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Glad it's working for you and thaks for the feedback and explanation for others.
As for Play Store I have yet to purchase a dev account to allow me to upload as I really only make things for people who know how to install from anywhere. Please feel free to trek people to download from this page, I won't be removing the app.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Rom Share
Alliance Rom
Version 6.00 MD5 ad9ef7e3f95b746de4bbc938ebf89a9a
Version 6.10 MD5 eab8fc5f40e47bc1a1a2d06b3d9253e1
Version 7.00 MD5 ae964c3a07aeb460c8d21fe3c0f087e9
Version 7.01 MD5 d761e4625b8406eee3b97fd5eec6ea87
IMEI Recovery
IMPORTANT
FOR THIS PROCESS TO WORK YOU MUST HAVE A GOOD COPY OF YOUR /efs DIRECTORY TAKEN PRIOR TO THE PROBLEM HAPPENING. IF YOU DO NOT HAVE THIS YOU WILL NOT BE ABLE TO RECOVER.
DISCLAIMER - THIS IS AN AMALGAMATION OF IDEAS, PROCESSES AND GUIDES FOUND ONLINE ALONG WITH MY OWN MODIFICATIONS AND PROCESSES THAT I HAD TO MAKE TO GET THE PROCESS TO WORK FOR ME.
ALTHOUGH I HAVE PERFORMED THIS PROCESS IN FULL AND IT HAS WORKED FOR ME I AM NOT RESPONSIBLE FOR ANY DAMAGE OR DATA LOSS THAT ARISES FROM FOLLOWING THIS GUIDE. BY USING THIS GUIDE YOU ARE ACCEPTING ANY AND ALL RESPONSIBILITY FOR ALL ACTIONS AND THEIR RESULTS.
IT GOES WITHOUT SAYING THAT PERFORMING THIS PROCESS WILL INVALIDATE YOUR WARRANTY BUT IF YOU ARE ALREADY ROOTED AND RUNNING CUSTOM SOFTWARE THEN YOU HAVE ALREADY INVALIDATED YOUR WARRANTY ANYWAY.
This is a common problem that usually occurs when a problem is encountered flashing a file from Recovery. Please take the precautions listed below, it will save you a lot of trouble should you ever suffer from this problem.
Backup Process
There are 3 ways that I use to back up the /efs directory.
These are:
1 - Manually copy /efs to your SD Card and make another copy somewhere safe (Computer, Dropbox, etc).
2 - Use HC-kTool to make a backup image of your /efs directory.
3 - Use Galaxy S Unlock AND GSII Repair to make backups of your original /efs directory (These are both the same but by doing both you have two copies of /efs available should you need it).
All Apps available from the Google Play Store or can be downloaded in the AppPack from here
At the end of this process you will have 4 copies of your /efs directory on your SD Card as well as any dulicates you created externally in step 1. This might seem like overkill but trust me taking 5 minutes creating these will save you hours and possibly quite a bit of money in repair costs in the long run should you ever need to recover!
Now you have your backups lets hope that you never need them, but should you then...
Recovery Process
Acknowledgements
Based on original post by XDA Member vaskodogamagmail with more detail and modifications to make process work added by me.
Original Post
Symptoms
You may have one, some or all of the following:
No Signal
Emergency Call Only
No Network
IMEI 004999010640000
IMEI 000000000000000
IMEI
(To check your IMEI number either enter *#06# dial into the dialer or check in Settings, Phone Information)
Prerequisites
Rooted Phone
Try the following processes in order until the problem is resolved.
Method 1:
Open HC-kTool and choose "Restore efs from backup (DANGEROUS!)" then choose "Restore IMG". Once completed you will be prompted to reboot. Perform Reboot and if all has gone well you will have a working phone again.
Method 2:
Open Galaxy S Unlock app and select "Restore saved EFS Folder". This will come up with a response saying "Done". Reboot and see if your phone is working again.
Method 3:
Open GSII_Repair and perform Options 2 and 3. Your phone will reboot. Once it has rebooted see if your phone is working.
Method 4:
Open GSII_Repair and select "Restore saved EFS Folder". This will come up with a response saying "Done". Reboot and see if your phone is working again.
Method 5:
This is the last chance (and the one that after tweaking to what you see below worked for me).
You will Need the following:
Stock GB ROM
Insecure Kernel
ODIN
Quick Root
All of these can be downloaded in the IMEIFix.zip which can be downloaded from here.
Android SDK and ADB instaled on your Computer or a Terminal App on your Phone (Personally I prefer ADB from Computer but you choose whichever you are most comfortable with).
We are going to restore your phone to as close to original stock a possible. No data wil be removed from your SD Card(s) but all installed apps, customisations, ROMs and Kernels will be removed. Please backup everyting you need before runnng this process.
If you are able to make a Nandroid Backup of your Rom you will be able to recover this at the end of the process.
Open ODIN
In Options select "Auto Reboot" and "F. Reset Time".
Select the following files from the "OriginalRom" folder on your computer:
Bootloader -> KERNEL_I9100XEKDB_CL161513_REV02_user_low_ship.tar.md5
PDA -> CODE_I9100XEKDB_CL161513_REV02_user_low_ship.tar.md5
Phone -> MODEM_I9100XXKDH_REV_02_CL995882.tar.md5
Reboot your phone into Download Mode (Hold down Home, Volume Down and Power when turnng on).
When in Download Mode connect to Computer via USB.
You will get a Ready message in one of the top boxes in ODIN. When you have this press the Start button.
After a while your phone will reboot and load up into it's Stock setup.
Configure the settings and then Power down the Phone.
Once Powered down go into Download Mode again (same process as above).
In ODIN press Reset.
Set the same options as before.
This time only set the Bootloader box. Select the file from the "InsecureKernel" folder on your computer - NOTE Insecure means that it is able to be rooted, not that there is a security issue with using it. We will be replacing this later anyway.
Check you have the Ready in the top box in ODIN and press Start.
Once finished your phone will reboot to stock again. IMPORTANT - Disconnect the USB cable before proceeding.
Go to Settings, Applications, Developer Options.
Turn ON "USB Debugging".
Connect USB cable to Computer and Phone.
Open "Samsung Quick Root"
Select "Reboot Device When Finished"
Press "Root Device"
Some text will scroll on the screen and then phone will reboot.
This will have installed SuperUser, Busybox and Rooted your phone.
Install a Root capable Explorer app, I used Es File Explorer, either download from the Play Store or you can install if from the Apps folder of IMEIFix downloaded above.
Open a Command Prompt on your Computer
Enter the following commands:
adb shell
su
busybox umount -l /efs
exit
exit
Using your chosen exporer delete the efs folder from the root of your phone.
Reset the phone, after that open your explorer again and browse to the Root, the efs folder should have recreated and will contain files. These are new and are system generated.
Go to the efs folder using your chosen explorer, and delete "nv_data.bin" and "nv_data.bin.md5".
Go to the working back up of your efs folder on your SD Card, copy the "imei" folder to the efs folder at the root of your phone, then again go to the backed up efs folder on your SD Card and copy the "nv_data.bin" file to your efs folder at the root of your phone using your explorer. Once you have copied this file, please rename the new file to "nv_data.bin.bak".
Make another copy of the "nv_data.bin" file in the backed up efs folder on your SD Card and paste this into the efs folder at the root of your phone again.
On your Computer open a command prompt and enter the following commands:
adb shell
su
chown 1001:radio /efs/nv_data.bin
Reset your phone.
You should now have your Original IMEI, check this by dialing *#06# call into the dialer. If you have the correct IMEI then you are done. You can either reinstall your usual ROM, Apps, Kernel etc manually or restore an existing backup.
If you need to install a Recovery with CWM (to restore backups or install new ROMs and Kernels then please follow these steps:
Install Mobile Odin from ChainFire from the Play Store (or if you are an XDA user you can download from here)
If you have used the XDA version you will also need the eu.chainfire.mobileodin.flashkernel.i9100.v2-1 apk file, this is in the IMEIFix download above in the Apps folder.
Copy the Kernel-V7.tar file from the CWMKernel folder in IMEIFix to your SD Card.
Open Mobile Odin and from there open the Kernel-V7.tar file. This will flash Dorimanx 7.45. If you now boot into recovery you can flash what you need to in the usual way.
By following the process above you will likely find that the Triangle Alert is now on your screen when booting yor phone indicating that your bootloader has been modified. Although this makes no functional difference to your phone you can remove this alert by installing TriangleAway from the Play Store (or if you are an XDA user you can download from here. This will reset the flash counters in your phone and remove the warning.
If you still have the wrong or no IMEI then you will need to seek further help.
There is no obligation but if this guide has just saved your phone and you feel you would like to show your appreciation there is a "Donate" button on the left, please feel free to use it.
YouTube fix
The problem is actually with Xlory's Inverted Play Store so far a fix had not been released by Xlory so we have to use the following workaround based on suggestion from Nos_20 and modifications from Andreas75k.
Fully uninstall YouTube, firstly from the Play Store or Settings, Applications and then from Rom Customiser (Manage System Apps).
In Rom Customiser go to OTA then select and flash Stock Play Store.
Goto Settings, Applications and wipe cache, data and any updates for Google Play Services and Google Play Store.
Reboot to recovery.
Wipe Cache and Dalvik Cache.
Reboot.
Once rebooted reinstall YouTube in Rom Customiser and update through the Play Store or just install directly from the Play Store but obviously it wont be a system app.
That's it, all should now work.
Key here is: don't use any modified versions of Google Play Services, Google Play Store or YouTube, only STOCK.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Hello mate
Thanks for this very helpful and informative thread
:good::good:
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
t-pip said:
Goto Settings, Applications and wipe cache, data and any updates for Google Play Services and Google Play Store.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Click to expand...
Click to collapse
By that ^^ you mean to clear data and cache for google play and google play services and their updates also...
Because I cleared only for the updates and it didnt work... could you please make it clearer for other users
Thanks Alot for the guide and ur 'stuff' very useful
Re: TrevStuff - Apps and Stuff to help with Alliance Rom
Ba7rani123 said:
By that ^^ you mean to clear data and cache for google play and google play services and their updates also...
Because I cleared only for the updates and it didnt work... could you please make it clearer for other users
Thanks Alot for the guide and ur 'stuff' very useful
Click to expand...
Click to collapse
Thanks for that. Yes wipe cache and data after uninstalling updates.
Phone Details and My Apps:
Phone: Samsung Galaxy SII i9100
ROM: AllianceROM i9100 JB v7 beta LSD
Kernel: Jeboo but usually Dorimanx
TrevStuff - My Apps and useful links.
If I answer your question by asking you to search or look somewhere else I'm not being rude. Just encouraging you to use XDA correctly.
Have you backed up your /efs folder? See here.
If I help you, please give me thanks.
Great thread good info. :thumbup:
alliance 7.3
apollo 4.5 regular
I9100
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.