Related
If you got ANY questions? Feel free to ask here..
[HELP THREAD]Any Questions? Anyone Can Ask here [GT-5360/5510/5512/6102]
VERY LENGTHY THREAD?? Difficult to read in app? Yes I know friends!! That's why added hide/spoiler button to each post & link to first post in every posts end
Hi, Everyone, This is a GUIDE to NEW / EXISTING users.. There are guides below for advanced users too.. So i have shared my experience at XDA with you all to make others understand and help each other.
If you want to know something/ want me to include a topic here, please PM me.. I will see if i can help with that and write about it.
Hopefully this will help many of you, Now READ ON.. Click On "SHOW CONTENT" Button to See the content on each posts below!
DIFFICULTY LEVELS: It tells you how much difficult it is for you to do the task described below. See the headings of guides in every post to see difficulty of that task.
* --> Very Easy
** --> Easy
*** --> Moderate
**** --> Difficult
***** --> Very DifficultINDEX OF THIS THREAD:
* Abbreviations/Acronyms used in XDA (Android language) [SEE 2ND POST]
* Simple methods to get LOGCAT, DMESG [SEE 3RD POST]
* CWM MD5SUM mismatch error while restoring? Solution for this: [SEE 4TH POST]
* How to use SDCARD instead of internal storage for apps[LINK2SD] [SEE 5TH POST]
* Detailed steps to install Stock rom/Firmware through ODIN [SEE 6TH POST]
* ROM installations instructions [IN GENERAL] [SEE 7TH POST]
* Kernel installations instructions [IN GENERAL] [SEE 8TH POST]
* How to deodex a stock rom in easy way using DSIXDA Kitchen [SEE 9TH POST]
* USEFUL LINKS TO THREADS/GUIDES SECTION [SEE 11TH POST/1ST POST OF 2ND PAGE]
MISCELLANEOUS: [SEE 10TH POST]
* Thread Title tags confusing? Its explained here!
* Why give "Thanks"? Thanks meter explained!
* Stars, User Titles: Junior, Member, Senior Member........? Read to know more!
* XDA/TAPATALK app image uploading problems??
* Make your Thread/Post Aligned(Neat) by using BBCODE TAGS
* Battery Drain?? Read these tips to avoid it.
* Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK]
PLANNED GUIDES ARE:[12th POST]
How to make a kernel--Writing in progress
How to get 10 without spamming / complaining!!
How to modify apps background,looks etc.
CREDITS :
To all my friends and xda members who gave me info to learn about these things.
To anmolsharma1293, deathnotice01, jaison thomas, kidcarter93, lavadepa, MNgez, nikufellow, tjsgy, wcypierre who gave suggestions and info and tips to improve this guide.
To The-Captain our moderator for helping us to improve ourselves, learn more and being kind to new users too.
Credits are added to respective people in the posts related to them whenever i have taken info / used their work[if not done, i will do it soon]. Informations obtained from other threads have been added in the posts related to it and i have done it with the permission of the thread OP. If i have forgotten someone's name please do let me know, and i will add it ASAP..
And please tell me any suggestions to improve this guide to help newbies/noobs as this guide should help all of us to get better at things we can do with an android. PLEASE REPORT ME ANY MISTAKES IF I HAVE MADE IN WRITING THE GUIDE/ IF THERE IS A WRONG INFORMATION.. I WILL CORRECT IT ASAP..
If i missed anyones credit, please forgive me and let me know.. and i will add it as soon as i can, promise!
Thank you.
Abbreviations/Acronyms used in XDA (Android language)
The reason for this guide is that many new users would have difficulty to understand what are these short forms.. everyone says cwm, rom, cm, etc.. but no one says what it is.. and you may feel a bit shy/embarrassed to ask them what it is. So here is my attempt to cover them..
Please do let me know in PM if some words are missing and you want them to be covered.. i will gladly add them, thank you.
This Post is an inspiration from mrhaley30705's thread & Diablo67 thread.
Use CTRL+F to find a specific term.Difficulty --> *
XDA RELATED ACRONYMS
DEV: Developer
ERD: Elite Recognized Developer
FM/FSM: Forum Moderator/Forum Specific Moderator
RC: Recognized Contributor
RD: Recognized Developer
RT: Recognized Themer
SM: Senior Moderator
GENERAL
AFAIK: As Far As I Know
ATM - At the moment
BTDT - Been there done that
CRACK: The password / product key / license key illegally used for unauthorized usage are known as a crack of the software . Also please read the warning posted at warez meaning below. The same applies to cracks
ETA - Estimated time of arrival.. Note: Asking ETA in dev section is a big NO NO..!!
FTFY: Fixed that for you
FTW - For the win
FWIW: For what it's worth
FYI: For Your Information
IBTL/IB4L - In before the lock / In Before Lock
IDK: I Dont Know (Thats what it means and i am not saying i dont know about IDK!!)
IIRC - If I recall / remember correctly
IRC - Internet Relay Chat
LOL - Laugh out loud
NEWBIE: Someone who is new to this field/ forum and wants to learn how to do it rather than say "NOT WORKING! FIX IT!".
NOOB: Someone who is new and doesn't want to learn "HOW" its done, just want to "USE" the end product. So, please guys dont be a noob, be a newbie!
OP: Short for Original Poster, or the person who originally started the thread.
OT - Off Topic
PM: Short for Private Message. Allows users of XDA to send and receive non-public messages. Accessed from USER CP.
P.S: stands for Post Script. It is used when u wrote a message on a postcard and u forgot to mention an important information.*
ROFL - Roll on floor laughing
RTL: Right To Left support (In Some languages you have to start reading from right and end towards left side.. as against to usual method of reading from left to right)
SMH: Shake my head
STH: Something
TBH: To Be Honest
TIA: Thanks In Advance
THREAD: An individual issue page on the forum. This thing you're reading is a thread.
TLDR: Too long to read
TM: stands for Trademark.
USER CP: Short for User Control Panel. This button near the top of the XDA page allows users to update their avatar, personal information, and signature. PMs and subscribed threads can also be checked in this location.
WARES/WAREZ: Warez refers primarily to copyrighted works distributed without fees or royalties, and may be traded, in general violation of copyright law. To make it simple, it is any app/software which has to be paid to use them, but are used without paying any money.. PLEASE NOTE: THIS IS NOT TOLERATED AT XDA. SO PLEASE DONT POST WARES ANYWHERE ON XDA FORUMS. YOU WILL GET BANS/INFRACTIONS IF YOU DO SO!
ANDROID DEVICE RELATED:
ADB: Android Debug Bridge, a utility to run on a PC to allow connection to and control of an Android device. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
AOSP: Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK: An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Apps2SD:A method of storing applications and cache on the device's microSD card.
Bloatware: Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted
Boot Animation: Boot animation is a term for a graphical representation of the boot process of the operating system. After you switch on / reboot phone you see this.
BOOTLOADER: There are two of these; the primary and secondary bootloaders. These programs tell the Android device how to start up, and are critical to its functionality.
Bootloop: When your system recycles over and over without entering the main OS.
BRICK/(HARD BRICK): An Android device that is completely non-responsive, i.e. nothing lights up, the screen does nothing, no combination of button presses cause any reaction. Can only be restored by JTAG or warranty service.
BUILD.PROP: A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations. It is also used to make tweaks to boost speed/performance, etc.
BUSYBOX: An application that contains many standard Unix tools.
BUTTON COMBO/THREE BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. press and hold volume up+home button+power button for 10 seconds will reboot into the RECOVERY menu at any movement when phone is on or Press and hold volume down+power button+home button to get into ODIN mode/DOWNLOAD mode).
Cache:A component that transparently stores data so that future requests for that data can be served faster.
CM: Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
CPU: It stands for Central Processing Unit and handles all the complex mathematical formulas necessary to do everyday things like surfing the Internet.
CSC - File with Carrier Customizations
Custom bin counter: A line of code in several Samsung Galaxy devices' bootloaders that counts the number of times a user uses ODIN to flash ROMS/KERNELS to the device. Commonly used to detect software modification. This is called custom bin down in ODIN mode and it should be 0 to claim warranty. Can be reset with GALAXY TOOLBOX APP by Doky73
Custom: Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
CWM: Short for ClockWorkMod Recovery Menu. This is a program that allows you to install custom ROMS/KERNELS as well as do many other customizations. Often referred to as the "RECOVERY MENU"/"CWM"
DALVIK CACHE: The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
DALVIK: The Android operating system's memory management tool. This program handles which other programs are running and assigns memory to them
DEODEXED: Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
DMESG: dmesg (for "display message") is a command on some Unix-like operating systems that prints the message buffer of the kernel..
DOWNLOAD MODE: Read Button combo to know about this.
EFS: The directory /efs on the Android device's internal storage. Contains files with the Android device's IMEI, wireless devices MAC addresses, product code, and other information..
EMMC: Short for Embedded MultiMediaCard. A chip architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array package.
EXT4: A journaling file system (e.g. NTFS, FAT32 are file systems) often used by Linux distributions. Can be used with Android.
EXTERNAL SD: A micro SD card that has been inserted in the micro SD slot in the Android device. Can be removed.
FACTORY RESET: This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card. It will just make it as a phone just bought from the store state.
FC/FORCE CLOSE: When a program on the Android device becomes unstable/gets an error, the DALVIK program will force it to terminate to prevent further system instability which appears as a Force Close message usually in phone.
FLASHING: The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
FREEZE: Specific to LINK2SD/TITANIUM BACKUP. Using these 2 apps, the user changes a program into a non-functional, but still installed, state. Useful for identifying problem and FCs.
gapps - Google Applications, like GMail, Calendar, Maps, G+, etc
GB - Gingerbread, AKA Android OS 2.3.X
GOVERNOR: A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA: Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS: Short for Ice Cream Sandwich, the Android OS version 4.0.x.
IMEI: Short for International Mobile Equipment Identity. A unique number to identify GSM, WCDMA, and iDEN phones. Used by GSM networks to identify valid devices.
INTERNAL SD: The internal storage memory of the Android device. Not a physical SD card that can be removed.
JB: Short for Jelly Bean, the Android OS version 4.1.x.
JIG: A piece of hardware that makes a physical connection between pins of the USB slot to force the Android device into DOWNLOAD mode.
JTAG: A process of connecting directly to the main board of the Android device to rewrite corrupted BOOTLOADERS.
KERNEL: The kernel is a program that constitutes the central core of a computer operating system. It has complete control over everything that occurs in the system.
LAST_KMESG: last_kmsg is a dump of the printk statements from the kernel before the operating system itself crashed.
LAUNCHER: A program that launches programs in Android. Examples are Touchwiz (Samsung), HOLO Launcher, Launcher Pro, ADW Launcher, and Go Launcher EX.
LCD Density: Pixel density is a measurement of the resolution of devices in various contexts; typically computer displays, image scanners, and digital camera image sensors.
LOGCAT: A command to view messages in one of the system logs. See Android logger.
LTE: Stands for Long Term Evolution. It is based on the GSM/EDGE and UMTS/HSPA network technologies, increasing the capacity and speed using a different radio interface together with core network improvements.
MAI77 method: Its only known here. So dont say this out of SGY forum. This is a method to flash kernel through CWM using Kernel flasher tool made by MAI77. Its basically you have kernel flasher tool and boot.img file in SDCARD root and you select kernel flasher tool in CWM and it will install boot.img file which is the kernel you selected.
MD5 CHECKSUM: A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
MIUI: A Chinese built-from-source ROM. Short for "Mobile Internet User Interface". Also can refer to the MIUI music player, which has been included in other ROMs.
Mod: The act of modifying a piece of hardware or software or anything else for that matter, to perform a function not originally conceived or intended by the designer.
MODEM: The software that interfaces with the phone's radio hardware to connect to cell phone towers.
NANDROID BACKUP: A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
ODEX: A file that is associated with an APK file, containing a list of the dependencies for the program. See also DEODEXED.
ODIN: A Samsung proprietary program that allows the Android device to be flashed back to stock or with custom software.
OVERCLOCKING/OC: Setting the processor's clock speed to run faster than its default setting, i.e. 1248 MHz (1.2 GHz) vs 832 MHz (Default)
OTA - Over-the-Air (usually used as "OTA update" for firmware updates that can be installed directly via 3G/4G/Wi-Fi without the need of an PC)
PIT FILE: Short for Partition Information Table file. One of the possible file types used while flashing with ODIN or HEIMDALL.
Port: To Take a rom or app from one phone and program it to work on a different one.
Ram: (Random Access Memory) A group of memory chips, typically of the dynamic RAM (DRAM) type, which function as the computer's primary workspace.
RECOVERY: The menu that allows a user to do many low-level operations on the Android Device. This menu can either be the stock Samsung menu, or the CLOCKWORKMOD RECOVERY MENU (CWM). See also CWM.
RFS: A Samsung-proprietary file system (e.g. NTFS, FAT32 are file systems) used on some Android devices. Stands for Robust File System.
RIL - Radio Interface Layer
ROM: The collection of programs, themes, and settings that create the general look-and-feel of your Android device. This is what most users will initially be wanting to change. Or custom ROM firmware file, Can also refer to a Read-only memory.
ROOT: Changing the permission level of the Android system to its most powerful level, the root user, allowing full access to the file system. More like Administrator permission in Windows OS.
SGY /SGYD /SGYP /SGYPD : Samsung Galaxy Y / Samsung Galaxy Y Duos / Samsung Galaxy Y Pro/ Samsung Galaxy Y Pro Duos
Sideloading: It means installing applications without using the official Android Market.
SOFT BRICK: A device that is not functioning correctly, but still shows some signs of operation. See also BRICK.
STOCK: The Android software version that comes installed on new devices, prior to sale to the user. Can also be used to refer to the Android software issued from Samsung or the carrier.
Superuser/SU: On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be: root, administrator or supervisor.
TETHER: Connecting the Android device to a computer via a wired or wireless connection to allow the transfer of data through the Android device's internet connection. Commonly used to provide internet access to a laptop or desktop computer when other methods are not desired or available.
THEME: A collection of images, backgrounds, colors, font types, and other visual items to change the Android device's look and feel. Separate from LAUNCHER, and is usually FLASHed in CWM.
TWRP2 - an alternate recovery mode for your phone
UNDERVOLTING/UV: Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
Updater Script: When Android devices install updates via CWM/recovery mode they have to perform a wide range of functions on files and permissions. The scripting language is called Edify and is defined primarily in the bootable/recovery/{edify,edifyscripting,updater} directories of the Android source-code tree.
WCDMA: Short for Wideband Code Division Multiple Access. An air interface standard in 3G mobile communications networks that allows higher speeds and more users.
ZIPALIGNED: An archive alignment tool that provides important optimization to APK files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Reduces RAM consumption.
Simple methods to get LOGCAT, DMESG
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided. Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
This i learnt from paxChristos from his thread.
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> *
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> **
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> ***
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
Or There is another method called All in one logger tool by wcypierre which can get you logcat and dmesg. I have not tested it myself. But i am sure it will work and you can go to that thread and ask your queries about that tool if you want to use that. The dev will help you gladly. So, please thank him for his nice work.The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
From PC[i.e, ADB] GET DMESG:Difficulty --> ***
Note: You will need adb access for this to work, same as logcat. Read PREPARATIONS above to find adb files required and related setup.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things.
Go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb shell dmesg > dmesg.txt
To get last_kmsg:
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
From Android Device GET DMESG:Difficulty --> **
You can also get the dmesg by using terminal emulator.
Code:
dmesg > /sdcard/dmesg.txt
To get last_kmsg:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
FOR APP DEVS / ADVANCED USERS ONLY! LOGCAT INSTRUCTIONS:
Thanks to jaison thomas for this method! NOTE: I have not tested this. sorry. But it will definitely work. I edited the quoted message to make it simple.
jaison thomas said:
log cat using eclipse, i thought it will be simple for advanced users who are into app development.
I will guide how it works
1) install samsung kies in your pc
2) turn on usb debugging in phone.
3) install android plugin for eclipse .
4) now on eclipse click on "window" --> "show view" --> "other" --> "android" --> "log cat". Then click "ok".
Thats it .logcat window will be shown in lower bottom side of eclipse.it is having a green color icon. Also there may be a chance of logcat window minimised in eclipse.do look for a green icon.
5) now conect ur phone using datacable u can see all the things happening inside the phone in log cat window in eclipse.
NOTE: if you couldnt find android under other option.. Do this:
u didnt install android plugin for eclipse do as follows to install android plugin for eclipse.
1) click on help
2)click on install new software
3) then click on add.
4)then you will get a text box with name and location. in name text box type android or any thing,
in the location copy paste this
https://dl-ssl.google.com/android/eclipse/ and press ok,
5)In the Available Software dialog, select all check boxes and click Next.
6)In the next window, you'll see a list of the tools to be downloaded. Click Next.
7)Read and accept the license agreements, then click Finish.
8)If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
9)When the installation completes, restart Eclipse.
Click to expand...
Click to collapse
CWM MD5SUM mismatch error while restoring? Solution for this:
Difficulty --> **
If you have made a nandroid backup and we never actually test whether it works/not.. So, some day when you need to restore it.. you get an error while restoring that "md5sum mismatch" restore aborted!! Then you are in a really bad situation right?? Wrong.. Do this.. and the problem should be solved..
You need to edit nandroid.md5 file stored in /sdcard/clockworkmod/backup/"backup name"/nandroid.md5
NOTE: backup name is usually date and time of your backup/ you could have renamed it to some name.
You need terminal emulator app. Download from play store (android terminal emulator)
Open terminal emulator app and input these commands..
Code:
cd sdcard/clockworkmod/backup/2012-09-30.03.18.47
NOTE: Change 2012-09-30.03.18.47 to the name of your folder
To See what file extensions need to be included. type
Code:
ls
( lowercase "L") and hit enter.
This will list everything inside your current directory (backup files of that particular backup)
To make sure there is no nandroid.md5 file existing already, enter this command:
Code:
rm nandroid.md5
Now to make a new nandroid.md5 file
Code:
md5sum *tar > nandroid.md5
Now its ready to be used in restore inside CWM..
NOTE: USE this procedure to repair nandroid md5sum mismatch error if you are getting this on a backup which has not been modified. If you have opened the backup files to modify the files inside. Its not advised to do this. So, please take note of this.
Special Thanks to cynnar for this idea. i tweaked it to our device from his post.
CLICK HERE TO GO TO FIRST POST
How to use SDCARD instead of internal storage for apps[LINK2SD]
Difficulty --> **
Welcome to LINK2SD app friends!
Easiest app to install and use to extend your internal memory.
What it does?
It creates a symbolic link file(more like shortcut in windows) for apps in internal memory which will point to the real app which will be saved in your sdcard second partition! It mounts the second partition of your SD card as /data/sdext2 and makes OS mounts it at boot time.
It can also move user apps to SD card (force move), with batch moving (multiple apps moving at once) capability.
That feature uses Android's standard SD-card installation feature and does not require a second partition. It can break some apps if they are not meant to be moved to the SD card (Such as Widgets).Preparations:
* You need to have root permission/access[Rooted phone]
* A second partition on your SD card. You should have two partitions on SD card and both should be primary.
* The second partition is used for application files and can be ext2, ext3, ext4 or FAT32 (I prefer FAT32 and no issues i have seen, see note below to know why?).
Note:
1. The second partition will not be accessible through windows OS as it recognises only first partition on removable devices. In Linux you can access second partition too!
2. ext4 is the latest ext format but several ROMs/Kernels have issues with it while fewer have issues with ext3 and ext2. FAT works on all ROMs.
Steps to make 2nd Partition in SDCARD:
Connect phone to PC using USB Cable. Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
Now drag the notification bar from status bar in phone and select "USB Connected" messasge.
Then select "Connect USB storage" button.
Once it is connected, Make a backup of sdcard first to PC(Copy all files inside sdcard to any fodler in PC). Otherwise you will loose data in sdcard.
Now open "MiniTool Partition Wizard Home Edition" download it from This LINK
This tool is compatible with Windows 2000/XP/Vista & Windows 7. Or Use "Gparted" tool for linux users Or "iPartiton" for Mac users.
Note: this partition manager QUEUES the operations. So nothing is deleted and changed UNTIL you click "APPLY" and then confirm by clicking "OK".
Make sure you are deleting partition on SD card! (not your hard disk for example). Dont be afraid, just read everything and think twice before selecting correct drive. Do you see three gray icons on the bottom? Under each of them the capacity of each drive is listed, and SD CARD has slightly different icon. Check the sdcard capacity given in the window to select the proper one.
select "Create As": PRIMARY on the sdcard partition. Choose whatever size(leave some space which we will use for apps partition) you want for sdcard( to have your music, personal files, etc.).
Select "File System:" FAT32
select the second partition below the one you just created which will have the space left when partitioning the first partition.
Select "File System:" FAT32 (YOU can use Ext2, Ext3, Ext4 also.) But my suggestion is please use FAT32. You wont have problems as all ROMS/KERNELS support fat32 by default!
Click "apply" button on top left corner. Partitions will be created and card will be formatted.
Now put your files back to sdcard and disconnect from PC.
NOTE: You can also use CWM partition option. If you want to use CWM partition method to partition your sdcard then see here. I have never tried this method. So i cannot help you with that.Steps to install and use link2sd[2.2.3 version]:
Let the media scanner finish the scanning process, then open link2sd app and you will see a pop up menu "Select the file system of your SD card's second partition"
Choose your partition type for "second partition" you created while partitioning, say you choose "FAT32/FAT16" then your sdcard second partition should be FAT32/FAT16 which is nothing but FAT or vFAT.
Now Press OK. After 2-10 seconds you will see another pop up menu "Restart your phone" Press "OK" (message goes like this "Mount script created, please restart your phone to mount the second partition of your SD card.")
Now do a reboot of your phone.
Link2SD successfully installed.
To make space inside internal memory-->
* Now open LINK2SD app and you will see three buttons on top bar. click on the first button from left side. you will see:* All --> It will show you all the apk/app files in your phone (130+/- apps)
* System --> It will show you all the system apps in phone (100+/- apps)(stored in system memory)
* User --> It will show you all the User apps(i.e, installed by you) in your phone (30+/- apps)(stored in internal & sdcard & second partition memory)
* Linked --> It will show you all the linked apps in your phone (it wont show any now)(stored in your sdcard second partition memory)
* On SD card --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* On internal --> It will show you all the user apps (10+/- apps)(stored in your sdcard first partition. usual sdcard method)
* Frozen --> It will show you all the apps that have been stopped. This is a method same as Titanium backup app "freeze" method. It makes your app invisible to phone. I.e, it will be installed and ready to use.. but you wont see it anywhere in launcher and if you click on a shortcut of such "frozen" app it will say "app not installed" or such message.* Now select options button in phone, then select "Multi-Select". Now press "select all" option.
* Now press "Actions" button. In new pop up window select "Create link"
* Now in new page which appears, select all 3 options to link application, dalvik-cache, library files. Then press "ok" button and wait till the process ends. It will take time depending upon how many apps you have. around say 5 minutes.
* Now go to linked option from top bar first button from left side. and see al the apps having linked->sdacrd tag on them which means they are now in sdcard second partition..
*Long press on any app to view more options.
NOTE: 1. you cannot move link2sd app from internal memory. It is better to keep it there.
2. System applications should not be linked to SD card. Link2SD does not allow these applications to be linked.
3. Link2SD does not move application's private data directory; it moves apk, dex (dalvik-cache) and lib files.
4. Do not move keyboard apps to system memory. they wont work.
Advantages:
1. When you connect your phone to PC as mass storage, Android unmounts FAT partition but the second partition remains mounted in phone. Therefore linked applications are not affected and can be run without problems even when you have access through pc to sdcard.
2. You can use this app to uninstall system apps, move user apps to system apps or system apps to user apps.
3. You can integrate new updates of system apps which will be stored in internal memory to system apps. But please note: You should free the app first and then move them to/from system always for safety of apps so that they wont give FC. If some apps did gave FC after moving please restart the phone.
4. You can use clear cache, dalvik-cache, 2nd partition options. They wont harm your apps, they will remove only unwanted files.
Troubleshooting / Error occurance chances:
Question : When I click on "Move to SD card", I see a progress bar for 2-3 seconds and then:
pkg:/data/app/com.mobisystems.editor.office_registrered-1.apk Failure
[INSTALL_FAILED_INSUFFICIENT_STORAGE]
Answer : Your problem is a simple one.. your internal memory is low..
What link2sd actually does is.. first it moves the files to internal memory and then it sends to 2nd partition.. so you are having issues because.. say the apk file is 20 MB.. and your internal memory is around 20/less MB free.. So, it will give that error even if the second partition is totally empty..
For a work around to this.. you can make backup from titanium or just backup with any app.. then uninstall some apps.. then move that big app.. then reinstall these..
Hope your doubts are solved.. Enjoy the awesome app!
Apps Original thread link and the credit goes to RD bakpinar. So do thank him for this awesome app. You can also donate the dev by visiting his original thread.
CLICK HERE TO GO TO FIRST POST
Detailed steps to install Stock rom/Firmware through ODIN
Difficulty --> **
NOTE: Please dont install/flash FIRMWARE of OTHER DEVICES for your phones! through odin! Make double check before downloading whether its the right firmware for your phone!
Visit the threads respective to your devices to see the latest available firmware.. Links given below.
Samsung Galaxy Y --> [Stock][ROM][Odin] FIRMWARE THREAD BY DOKY73
Samsung Galaxy Y DUOS--> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
Samsung Galaxy Y PRO --> [Stock][ROM][Odin] FIRMWARE THREAD BY GianniDPC
Samsung Galaxy Y PRO DUOS --> [Stock][ROM][Odin] FIRMWARE THREAD BY MANORANJAN2050
To check the current version your mobile has.. Type this code in Dialer Tab which is where you type phone numbers to call..
Code:
*#*#1234#*#*
and check EX. PHONE: S6102DDLG1. See whether it is the latest by visiting samfirmware.com site and type your mobile no. for ex. 5360 in search box in right side of that site page and see whether any new update has come.
PREPARATION:
Switch on PC to windows OS and Login to your account. Make sure your device driver is already installed and your device got detected.. otherwise install kies software which will install drivers too.. Get kies from This LINK
Now connect your device to PC using USB Cable..
Open ODIN software from extracting the file you downloaded from using any of these applications like IZarc/ 7ZIP/ Winzip/ Winrar..
Note:
If you did above instruction and still device not detected? Then do this..
Unplug the usb cable..
Restart both PC and phone..
Then let the PC log in.. and give 5 mins time to it to load everything..
Then connect usb cable to phone and pc..
Open task manager in PC using CTRL+ALT+DELETE..
end process of adb.exe if its existing and kies too... do this end process only once..
Now open odin..
Instructions to install this through Odin:1. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
2. Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
3.you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
4. Note: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue box restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
5. Now select "PDA" button under "Files [Download]" section.. select "PDA_S****_(your firmware version no.).tar.md5" file
Now select "PHONE" button below "PDA" button in "Files [Download]" section.. select "MODEM_S****_(your firmware version no.).tar.md5" file
Now select "CSC" button below "PHONE" button in "Files [Download]" section.. select "CSC_S****_(your firmware version no.).tar.md5" file
Note: **** --> Your device model number. 5360 --> Samsung Galaxy Y, 6102 --> Samsung Galaxy Y Duos, 5512 --> Samsung Galaxy Y Pro Duos, 5510 --> Samsung Galaxy Y Pro.
6. Now remember!! Only "Auto Reboot" "F. Reset Time" options should be selected..
PDA, PHONE, MODEM also should be selected..
7. Now you are ready to flash through odin.. Just press "Start" button.. and wait around 10 minutes until odin finishes and the "yellow" box should show green... It will usually finish within 52 seconds to be precise..
8. Now your phone will reboot. If it starts showing Samsung logo again after few minutes.. Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)...and select "wipe data/factory" and select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
9. Now enjoy your brand new stock rom.. Hope this helps you!!NOTE: IF YOU CANT GO TO ODIN/DOWNLOAD MODE.. YOU NEED AN USB JIG to force phone to Odin mode automatically.. [REF] BORROW A USB JIG NEAR YOU..
CLICK HERE TO GO TO FIRST POST
ROM installations instructions [IN GENERAL]
Difficulty --> *
OK.. so I assume you have latest firmware.. Because its always good to have latest firmware update to avoid unnecessary problems as usually updates will have bug fixes and stability improvements.. If not, then First follow the guide I have given in this thread to install the firmware update if you are not on latest version..
OK, now that we have latest firmware update installed, lets proceed to ROM installation process!
* If you dont have these files Download and keep these files in sdcard (outside all folders / root of sdcard)..
1. Rom.zip file.. link is provided in first page of the ROM thread..
2. CWM file..
Now go to stock recovery by doing this..
Restart your mobile by holding three buttons...
Volume up+home button+power button..
Now when you see Samsung logo release the buttons..
After few seconds you will see 4 options written in red text..
Which is stock recovery (Android system recovery)...
* Select 2nd option in there.. "apply update from sdcard"
* Select "CWM.zip" file u have..
* In cwm(clockworkmod) which is with yellow text..
* Now go to backup and restore option.. make a backup first.. you need to have atleast 250-400 MB of free space in sdcard to do backup...if you dont care about your data/contacts/messages currently existing in phone then no need to make backup.
* Select "wipe data / reset" and then "wipe cache Partition"..
* select "install zip from sd"
* Select "Choose zip from sdca" first option now..
* Scroll down.. and select rom.zip file..
* Then select yes option.. and wait for few minutes for it to finish.. then come bak to previous screen using power button..
* Now select "reboot system now"
* Good, Now you have successfully installed the rom.. First boot takes time.. So wait till atleast 5-10 mins.. It will vibrate onec and then it will boot to your home screen.. This guide is in general. But usually all roms have installation guide..NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE ROMS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN ROM THREADS THEN ONLY TRY THIS.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
Kernel installations instructions [IN GENERAL]
INSTALLATION PROCEDURE FOR KERNELS THROUGH CWM METHOD:Difficulty --> *
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Copy these files inside SDCard.. Kernel.zip (kernel), CWM.zip (ClockWorkMod Recovery tool)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "Kernel.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.INSTALLATION PROCEDURE FOR KERNELS THROUGH ODIN METHOD:Difficulty --> **
* First Download all the files required [from the kernel thread first page of whichever one you want to install]
* Restart your mobile by holding three buttons... Volume up+home button+power button.. Now when you see Samsung logo release the buttons... After few seconds you will see 4 options written in red text.. Which is stock recovery (Android system recovery)... select first option there.. ("reboot system now").. It will say "Rebooting..." in green colour..
* Now when screen gets black.. immediately press and hold volume down+home button+power button..
you will see a page saying "Warning"
A custom OS can cause critical problems in your phone and installed applications.. and it will say some more in next paragraph..
Dont worry about it.. Now press "Volume up" to continue to odin mode..
* you will see ODIN MODE written on top of screen in red..
Now make sure you are connected to your pc through usb cable and pc is logged in and open odin file..
*NOTE: In Odin you will see a yellow/blue color in one box below "ID:COM" section.. If you are not seeing yellow/blue restart your mobile and do same process from step 2. also restart your pc if its still not showing yellow. If it is showing then good.
* Now select "PDA" button under "Files [Download]" section.. A new window to browse files will get opened.. Locate the file boot.tar/boot.tar.md5 file you want to install.. select "boot.tar.md5"/"boot.tar" file..
* Now remember!! Only "PDA" "Auto Reboot" "F. Reset Time" options should be selected..
* Now you are ready to flash through odin.. Just press "Start" button.. and wait around 1 minute until odin finishes and the "yellow" box should show green... It will usually finish within 15 seconds to be precise..
* Now enjoy your brand new stock kernel.. Hope this helps you!!INSTALLATION PROCEDURE FOR KERNELS THROUGH KERNEL FLASHER TOOL[MAI77 METHOD] IN CWM:Difficulty --> *
* First Download all the files required ["boot.img" from the kernel thread first page of whichever one you want to install] and kernel flasher tool
* Copy these files inside SDCard.. boot.img (kernel), KernelUpdate.zip (Kernel Installer tool), CWM.zip (CLOCKWORKMOD)
Note: Don't keep these files inside any "FOLDERS".. Just copy it to SDCard root (parent) folder (Outside of all folders)..
* Switch off your mobile.
After a small vibration (switch off confirmation) PRESS and HOLD 3 BUTTONS (VOLUME UP+HOME BUTTON+POWER BUTTON)
when samsung galaxy logo appears, release the 3 pressed keys..
* After few seconds.. You will see Android system recovery (red text with 4 options lines)..
Select "apply update from sdcard"
Note: (Volume up+down for "scrolling" through options or selection of files, home button for "select" any option.. in CWM only: power button for "back" option)
Then Select "CWM.zip".
* ClockworkMod Recovery v5.0.2.6 is loaded now.
Select "install zip from sdcard"
Select "choose zip from sdcard"
Scroll and Select "KernelUpdate.zip" and select "Yes"
Wait till the menu appears again.. Now Go back
* Select "Reboot system now" and you have successfully installed Kernel.NOTE: THIS IS A GENERAL METHOD.. SHOULD WORK FOR MOST OF THE KERNELS.. BUT IF THERE WAS ANY PROBLEM LET ME KNOW.. I WILL EXCLUDE IT FROM THIS GUIDE.. IF YOU CANT UNDERSTAND INSTRUCTIONS IN KERNEL THREADS THEN ONLY TRY THIS.. YOU CAN CHOOSE TO USE ANY OF 3 INSTRUCTIONS TO INSTALL.. I HAVE WRITTEN THIS ASSUMING YOU ARE ON STOCK KERNEL/ YOUR KERNEL DOESNT HAVE CWM INBUILT. If it has.. then ignore stock recovery instructions mentioned in above instructions.. and directly start from CWM instructions..
CLICK HERE TO GO TO FIRST POST
How to deodex a stock rom in easy way using DSIXDA Kitchen
SPECIAL Thanks to dsixda Recognized Developer / Retired Senior Moderator who has made an all in one ROM kitchen. So thanks to him there are many custom roms are there in xda.
Difficulty --> **** IF YOU ARE NEW TO PC & ANDROID. This is not for you. If you are good with either one then you can try this.
PREPARATIONS:I Recommend you to use linux if you have it.
Kitchen by Dsixda [KITCHEN] Android Kitchen, v0.214 [Linux / Mac / Windows]
You need to have java installed in system to use the kitchen. All the steps for how to setup in windows/linux/mac has been explained well by dsixda in thread link. So i am not going to explain it here again. I assume your kitchen is set up and you are ready to work.
Make a backup in cwm and transfer the system.rfs.tar or system.ext4.tar file and boot.img file inside /sdcard/clockworkmod/backup/"dateofbackup"/ into PC.
Now go to the "/dsixda-Android-Kitchen/" folder and you should see these in that folder:
3 files & 3 folders it should contain:
- menu(file)
- Readme(file)
- .gitignore(file)
- original_update(folder)
- tools(folder)
- scripts(folder)
For Windows users--> Now open command prompt (If you installed Cygwin, then click on the Cygwin shortcut on your desktop to start it) and make sure you get to the path of that folder.. Ex. if folder is in c:\cygwin\home\"username"\dsixda-Android-Kitchen.. Then type this in command prompt..
Code:
cd dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it... Note: Dont use space in folder names as cygwin wont work properly with space in folder names.
Or For Linux Users--> Now open terminal(Use CTRL+ALT+T). and make sure you get to the path of that folder.. Ex. if folder is in /home/"username"/Desktop/dsixda-Android-Kitchen.. Then you will be at /home/"username"/ . So type this in terminal.
Code:
cd Desktop/dsixda-Android-Kitchen
Note: the capital letters should be in capital only when you type it.
Now find that system.rfs.tar or system.ext4.tar file and boot.img file and paste it inside original_update folder. You will also find a file "put_rom_here_" Please ignore that file. Its just to tell you he has created that file.
Ok.. Now that you are at the right path.. just type ./menu in terminal or command prompt. From now on i am just going to say type this. It means you should type that and press "enter" to execute the command. If a menu didnt appear then type
Code:
pwd
You should see in which directory you are currently in. Try to get to the folder where kitchen folder is. Or follow steps again to get to there.
Now then, you should see this menu:
Code:
============================================================
Android Kitchen 0.214 - by dsixda (xda-developers.com)
============================================================
> MAIN MENU
1 - Set up working folder from ROM
2 - Add root permissions
3 - Add BusyBox
4 - Disable boot screen sounds
5 - Zipalign all *.apk files to optimize RAM usage
6 - Change wipe status of ROM
7 - Change name of ROM
8 - Show working folder information
0 - ADVANCED OPTIONS
00 - LEGACY OPTIONS (old and rarely used)
99 - Build ROM from working folder
u - Kitchen Info/Update/Donate
x - Exit
Enter option:
Enter option: 1
Press "Enter"
[CODE}Available ROMs:
(1) system.rfs.tar
Enter selection number (default=1, cancel=0, r=refresh):1[/CODE]
It will ask you this:
Code:
The new working folder will be named WORKING_111212_132324
Change the name (y/n)? (default: n):y
Give a name if you want to identify it easily next time.. for ex. i gave this "Enter a new name (using this prefix): WORKING_DDLJ1" as it is from DDLJ1 firmware update.. you can choose not to give name.
Now it will ask this:
Code:
Would you like to view this ROM's info (y/n)? (default: y):y
Give y as yes as i gave.
It would appear like this if it is stock roms backup:
Code:
Working folder information
Android OS version : 2.3.6
Device : GT-S6102
Model : GT-S6102
ROM Name : GINGERBREAD.DDLJ1
CSC version : S6102ODDLJ1
Rooted (Superuser app + su) : NO
Rooted (unsecured boot.img) : UNKNOWN
BusyBox installed : NO
BusyBox run-parts support : UNKNOWN
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
Press Enter to continue
Now press "Enter" to continue.
Setting up working directory complete.. You can close it anytime if you want when you are at main screen just type x and press "Enter". You can open it again and continue without making the above steps again..
Enter option:0 in main menu for "Advanced options"
Enter option:11
It will show like this:
Code:
NOTE: Reversing the de-odexing process by getting back the odex
files ('re-odexing') is not supported in the kitchen and would
be impossible to implement.
----------------------------------------------------------------
Found 23 *.odex files in system/framework
Found 110 *.odex files in system/app
Enter a choice:
bb = Back up both folders (do first!)
v = Set Android OS version (Current API level = 10)
IMPORTANT: Ensure you set the correct API level
f = Deodex /system/framework
a = Deodex /system/app
b = Deodex both folders (recommended)
s = Deodex a single file
x = Exit
?
Now type bb and press enter. (For safety, backup apks.. you can skip it if you want) Press "Enter" to continue.
Now type v and
Code:
Change the current API level (y/n)? (default: n):y
Please enter the new level number (currently: 15): 10
Press "Enter to continue.
Now type b to deodex your rom. Press "Enter" when this is asked,
Code:
Enable logging to file (y/n)? (default: y):
It will take some time depending upon your computer configuration. So take a small nap It takes 20 minutes in mine usually.
At the end if its successful.. you should see this:
Code:
Finished system/app
A summary of the deodexing has been logged in deodex_111212_133710.log
0 *.odex files remain in system/app
0 *.odex files remain in system/framework
Press Enter to continue
Now press "Enter" to get back to "Advanced options"
Now to make this as cwm flashable zip.. Then type 99 and press "Enter"
[CODE}Select a build option:
Number (default: 1):1
Would you like to optimize the APK files by zipaligning them (y/n)? (default: y):y
Use updater-script in ROM's ZIP file (y/n)? (default: y):y [/CODE]
Now it will show this:
Code:
An updater-script has been created under META-INF/com/google/android of
your working folder. Please review it and make any necessary changes. An
update-binary has also been added.
DO NOT delete any of the files under META-INF/com/google/android.
Proceed with the change (y/n)?
y = Proceed; updater-script and update-binary will be used in the ZIP
file; update-script will remain in working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.
? (default: y):
Now go to that "META-INF/com/google/android." folder.. And replace the "updater-script" with the file i have given in the attachment to this post. rename the "updater-script.txt" file i have given to "updater-script" and delete "update-script" file. Now after replacing the file type y in menu.
It will ask this:
Code:
It is recommended that you sign your ROM.
Sign it (y/n)? (default: y): y
The new ROM will be named GT-S6102_signed_111212_141640.zip
Change the name (y/n)? (default: n):y
and type new file name whatever you want and press enter
You will find the zip file inside OUTPUT_ZIP/"given name".zip
Now its ready to flash the zip file in CWM.
I will write about other options if any users/readers ask me to write it.. otherwise i may update it when i feel there is a need for that.
CLICK HERE TO GO TO FIRST POST
Miscellaneous section
THREAD TITLES CONFUSING? ITS EXPLAINED HERE!Difficulty --> *
[TAGS] --. Use these below tags on your title, So that people can identify it more easily and what the thread is for! Add it in front of the thread for better recognition of thread purpose.
[SOLVED] - for issues that have been fixed or [Q] that have been answered THIS IS A MUST TAG FOR SOLVED THREADS! IT WILL SAVE LOTS OF TIME FOR EVERYONE! PLEASE DO THIS WITHOUT FAIL ALWAYS!
[Q] or [QUESTION] - All Questions thread should have this.
[REQ] - Requests topics for ROM ports, INFO, THEME, MOD, etc.
[TUTORIAL] or [GUIDE] or [HOWTO] - How to do or Guides for some task or info for users/devs.
[UITIL] or [UTILITY] or [TOOL] -- Any kit or tool made for some specific task.
[APP/ 2.2+] -- Apps thread which contains apps made / ported / modded. 2.2+ such tag is also a must which tells what android os or above versions are supported.
[ROM] / [KERNEL] -- As name suggests its a rom development or kernel development thread.
[DEV] -- Developers related thread
[MOD} -- Modded ROM/KERNEL/APP etc thread
[ROOT] or [CWM] -- Rooting thread or root related to thread. CWM related thread.
[AROMA] -- Tool used in recovery. This means the thread for any ROM ? KERNEL ? OTHER WORKS has aroma to flash it.
[TWEAK] -- Tweaks to boost system performance speed etc thread.
[WIP] -- Work In Progress thread.
Also, please do add tags to your threads. See "TAGS" button above your "Quick reply option".. Now see right end of that line to find "EDIT TAGS" button. Click on it and words there.
Code:
Thread owners and others should add relevant words there
So that the thread gets added to searches which have those words
WHY GIVE THANKS? THANKS METER EXPLAINED!Difficulty --> *
Why to Give Thanks?
Giving thanks is important. It lets people know that their work or answer is appreciated. It is a faster method of feedback than posting a reply like "Thanks for your answer!" You must have made one post to give thanks,
You get 8 thanks per day, and they renew after 24 hours or so. Each thanks is independent of the others, so if you give someone a thanks at 3, and then another at 4, those will renew at 3 and 4 the next day. If you run out of thanks, then save that page in a new tab and give thanks later when you have one available. (Or if you are an app user then you can thank them through the app "Just tap on the post and touch thanks button on pop up bar which appears") If you use them all every day you are doing it correctly.
Thanks Meter:
You will see that everyone here has a Thanks Meter above their avatar.
Here are the counts needed to get to the next bar.
1st bar - 26
2nd bar - 51
3rd bar - 101
4th bar - 201
bug here, never gets to 5 bars, probably 501 if fixed.
6th bar - 1001
7th bar - 2001
8th bar - 5001
9th bar - 8001
10th! - 10000+
Not that thanks are an indication of a user's status or stature on XDA. Thanks don't really count for anything other than as a potentially wildly inaccurate measure of a member's ability to answer your question correctly. Some of the most important people here have a lot fewer thanks than you might guess. But it is a nice gesture to hit thanks button to those who helped you as they are not gaining anything in return!
STARS, USER TITLES: JUNIOR, MEMBER, SENIOR MEMBER........? READ TO KNOW MORE!Difficulty --> *
0 to 29 posts - Junior Member
30 to 99 posts - Member
100 + posts - Senior Member
Here is what our Senior Moderator said,
juzz86 said:
There are Junior Members, Members, Senior Members first. These make up the vast majority of XDAs userbase.
Recognised Contributors are nominated by other users and/or Mods/Developers. They are recognised for their contributions which are not specifically Development, such as detailed guides, one-click utilities and other tools/mods.
Recognised Themers are also nominated by users/Mods/Developers, for their work themeing custom ROMs and providing standalone themes for flashing.
Recognised Developers are nominated and approved by the Developer Committee, for their work in Development whether it be ROMs, Root methods, bootloader unlocks etc.
Elite Recognised Developers are again assessed by the Developer Committee, and are deemed to have gone above-and-beyond in providing knowledge/hacks/tools/apps/ROMs for the XDA community.
Forum Moderators are appointed by the Moderator Committee, after submitting an application (see the 'sticky' at the top of this forum - currently applications are not open). They are the first-line of keeping the forums tidy, friendly and orderly.
Senior Moderators are the next step up the ladder, providing site-wide support for Forum Mods and looking after the nitty-gritty issues, as well as areas of XDA not policed by FSMs, such as the Marketplace.
Administrators are next. There are several Admins - each look after a specific part of XDA such as the Portal, the Members and the User Experience of XDA as a whole.
At the top is Mike Channon, who is overall Forum Administrator.
Other titles you may come across:
Moderator Committee - sits on the Mod Committee
Developer Committee - as above, but for Developer Committee
XDA Newswriter - publishes articles for the Portal (front page)
Retired xxxx - have since officially 'left' their XDA position
Hopefully that clears most of them up for you
Contrary to what a lot of people expect, the thanks-meter does not figure at all in determining a users tag.
Click to expand...
Click to collapse
Wondering what those stars below the thanks meter mean?
It means that they've donated money directly to XDA.
A star = €10 euro donation.
A star with 10 written within it = €100 euros, as it represents 10 individual stars.
XDA/TAPATALK APP IMAGE UPLOADING PROBLEMS?? Difficulty --> *
Use Imgur Mushroom app.. its available at play store..
Its app size is very small.. Its a great app for multiple pictute uploads at once..
Whatsmore u can configure prefix and suffix text in settings to add [img] and [/img]..
After uploadingthe pics, it will save all links with prefix and suffix code in clipboard. ready made for you to paste it in the desired post using the XDA/TAPATALK app..
So all u need to do is paste it in post.. very easy and handy.. How to do it? Instructions below!
open imgur mushroom app. Select button right side to upload button which has this "..." button.
now select "settings" in the newly opened pop up menu.
now scroll down and select "output type" in URL settings section.
select "URL to direct image"
select "prefix text" and add [img]
select "suffix text" and add [/img]
now go back and select "pick" button and choose your pics to upload. Alternatively you can multi select in a file browser and share them to this app to upload too! Hope this helps!
MAKE YOUR THREAD/POST NEAT BY USING BBCODE [Bulletin Board Codes]: Difficulty --> *
You see in many Threads and posts people using something to make it look cool / formatted to make it more readable?
And you wish to make your threads/posts the same way??
Then look at this link provided by XDA.. I know many wont know about this..
BBCODE EXPLAINED WITH EX. BY XDA.. CHECK THIS LINK
I will add other info that are not informed there soon..
BATTERY DRAIN?? READ THESE TIPS TO AVOID IT! Difficulty --> *
Are you using live wallpaper? it takes more battery!
Go to Settings-->Accounts and Sync-->Auto-sync option-->uncheck it to save more battery.
If you keep using 3g/wifi it will use more battery.. Use 3g only when u download something..
If you are using widgets, it does drain battery faster.. If you want your battery to last longer, remove them or keep it to minimum 1 or 2. I dont use any widgets.
You have to pay attention to your apps running in the background. Try "Quick system info pro" or "ES Task manager" or "some other apps which shows detailed info on processes running. Stop those processes.
If you are using too many notifications features types of apps it will drain battery as they run in the background all the time..
Keep the screen brightness to as low as possible and readable still. Brightness does takes battery a lot.
Playing games does drain battery faster.
If you have custom kernel, and keep minimum freq higher then it will drain faster too
When u sleep at night and wake up at morning how much battery u lose? I loose around 1 percent.. If its more than 2-10% may be your deep sleep feature is not working.. Check it with CPU SPY app available at play store.
[DUOS ONLY]Do you keep both sims alive? I switch off 1 in sim manager.. Do it if you don't need it all time..
Inspired by a.cid and mf2112 threads.
Enable Whatsapp *AUTO DOWNLOAD IMAGE OPTION* in new versions [TRICK] (2.9.**** versions and above)Difficulty --> *
If you have lost "Auto-download images" option.. Then you are not able to disable the auto download of images. So, to get back that option in Settings-->Chat Settings. You need to do these steps below:
Note: Make sure you have a working Whatsapp already before attempting this. That is you should have already passed the verification process etc and able to chat with others.
Step 1 : Make sure you have "Ticked" option "Unknown sources" under Settings-->Application Settings.
Step 2 : Download this old version Whatsapp and transfer it to click on the downloaded file. It will ask "Replace application"
Press "OK". Then, Press "Install" button. After install press "done".
Step 3 : Now, switch on "Airplane Mode" to "ON" by lidroid toggle or in Settings-->Wireless & network settings--> Flight mode "ON"
Step 4 : Go to Settings-->Date & Time.. Change date to any date/ November/ 2012. Now, open the Whatsapp.. You should see a old Whatsapp.
Inside Whatsapp, Go to settings-->Chat settings and now turn off "Auto-download mages" option by "unchecking" the tick box.
Step 5 : Now, install the new Whatsapp if you have a backup of the app and turn off "Airplane mode" and now you can also update from play store if you dont have a backup of latest version of Whatsapp.
Now open the new Whatsapp and see the option "Auto-download image" option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CLICK HERE TO GO TO FIRST POST
Useful links to threads/guides section
NOTE: I am not adding any SGY forum threads here.. as we all can look into it easily.. I am adding only other forums thread links of XDA which are very useful to us. So please dont ask me to add SGY forum thread links here. And if you find any useful threads which are not similar to already mentioned thread.. Then PM me the link.. I will add it if its good. Thank you for reading!Thread Titles with links and info about it are below:
****XDA SITE RELATED THREADS****[All XDA Members] Requests to Moderators and Admins --> Rather than sending a PM to an individual Moderator, please see this thread in need of Moderator or Admin assistance. They will all be monitoring this thread, and someone will reply without much delay.
XDA Android App - Problems / Bugs / Feature Requests etc. --> Report any faults you find with XDA app in this thread. You can also ask for new features, but cannot promise they will ever be delivered.
SPAM Users --> Any user Spamming in forums / threads? If you feel yes, then do go to this thread and report the user. Please give direct link to the users profile/posts which were spam so that it will help moderators.
[HOW TO]Make The Most Of The XDA App --> This is for all of you who use the app instead of desktop, but may not know how to do certain things.
I Will Post Your Question In The Dev Thread If.. --> Newbies not able to post in dev thread? Some report you want to get it there? Then check this thread to do exactly that!
Help Your Threads Get More Search Hits with Better Titles and Thread Tags! --> I have noticed that many threads do not have thread tags so I think most users don't know about them. This only works with
the XDA website, not the XDA app. Please read this thread to know more about tags which is a very useful method to get your thread popular!
Time Frame/Tell your story here on xda![Archive] --> Where we could talk about our years here at XDA. Lets see who is the oldest and what we have given to this forums.
Share your sig code please --> Very helpful to make your Signature look neat. Read this thread to make your signature better or if you have cool signature then post there.****GENERAL INFO THREADS****[MOD][2.56] AROMA Installer :: 121004-031 :: Open Source --> The World's First ANDROID Touch And Customizable ROM/KERNEL/MODS Installer
List of devices: ARMv7, ARMv6, ARMv5 --> I found a really nice thread that will maybe, help some developers who need to port Roms or for another Reason.
[v6.13] Online Nandroid Backup / Nandroid Backup without re-booting
[HOW-TO] Set up SDK/ADB on Ubuntu 11.10 | 32 & 64 bits
[TUTORIAL]How to make your own Live Wallpaper
[Tutorial/How-To][GB] Make Your Own Custom Rom & Kernel (Last Updated 30/07/2012)****ROM RELATED/INFO THREADS****
ROM DEVELOPMENT THREADS:
[HOW TO] Beginners Guide to Android ROM Development
[Guide]Complete Android ROM development and essential tutorials ~~ By Nero Young ~~
[KITCHEN] Android Kitchen, v0.213 [Linux / Mac / Windows]
[Ultimate Guide][Part 10 released][12/11/2011]Android App Development - From Scratch
ROM MOD THREADS:
[UTILITY] Android Utility - [apktool|dex2jar|smali|more][Mac & Linux][Feb13, 2012]
[MOD][HOW-TO]To disable signature checks
[GUIDE] How to add TABS to Settings with swipe gesture... \m/
[GUIDE] ICS Style 'Settings.apk' - Make it yourself !! !!
[UTIL][Sept 2 2012] Apktool v1.5.0 - a tool for reverse engineering apk files
[IDE][M10] Virtuous Ten Studio - The next level of editing apps
[KITCHEN][01/22] UOT Kitchen (Ultimate Online Theme Kitchen) version 4.0
[MOD][15 Toggles] How to mod Lidroid framework
[APP][DEV] Update me [ROM MAKER] - 2.0.3 - PUSH NOTIFICATION - (updated 2012-09-13)****KERNEL RELATED/INFO THREADS****
KERNEL DEVELOPMENT THREADS:
[KITCHEN]Android Kernel Kitchen 0.2.3 (Linux / Windows)
[Tutorial] Building Your First Kernel
HOWTO: Compile your own kernel from source (WIP)
[Tutorial] How to compile a kernel module outside the kernel
KERNEL MOD THREADS:
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
[KERNEL MODULE] Extra modules pack v0.1.3 (feat. overclock) [OMAP4 kernel 3.0.8]****RARE/COOL APPS THREADS****[APP] Updated: 31/10/12 - PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer!
[APP][DEV] ZipInstaller 2.4.2 for CWM-based + TWRP + 4EXT Recoveries
[APP][2.1+] Gidder - Git server for Android
[APP/5 NOV/2.2+]Turn screen off while MHL/HDMI mirroring WITH TOUCHPAD! [v1.96B11]
[APP][2.1+] FTP Server Ultimate - FTP, SFTP, FTPS server with multi-user, no-root
[App] WifiKill - disable internet for network hoggers (Android 4.x) [31/10/2012]
[App]Mediafire App for Android
[App][2.2+]LauncherWP8[6nov][v1.1.1]
[APP 2.2+] Android Tuner [BETA TESTING]
[APP]DroidSheep : ARP-Spoofing App for Android****MISCELLANEOUS THREADS****[TWEAKS][SCRIPTS] Collection of 'em all - build.prop; init.d; etc.
☠ [Add-on][Tweaks\\Mods]█ PIMP MY ROM █ v2.1.2 {Any Device // Any Rom}[AROMA][WIP] ☠
[Tool][Windows Only][Root] Android Reverse Tethering 2.30 --> surf on your phone using the ADSL of your PC.This work only for rooted users !
[ICON PACKS] mrFenyx's Icons - 8 packs, 800+ Icons, more to come
[Rooted][Guide]Wifi Reverse Tether - Windows and Ubuntu - Ad Hoc Networks CLICK HERE TO GO TO FIRST POST
Well, even though there are 2 kernel guides in our section.. Both are not complete.. So i thought of writing this.. a complete guide to make a kernel.
So, i'll keep updating this post as and when i get time to make it as good as possible..
Files Required:
You need to have Ubuntu or any other Linux distros.. But i recommend Ubuntu 11.10 32 bit as I'm using this version.
Kernel source from http://opensource.samsung.com . Search for 5360 and download "GT-S5360_GB_Opensource_Update3.zip"
Download Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/
Note: It should be Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2. Extract this file & you need to extract the file you got again to get "arm-2009q3" folder.
Download mkbootimg_src.zip from http://d-h.st/xnT
split_bootimg.pl is a perl script required to extract ramdisk from boot.img file. Or use dsixda or championswimmer's kitchen to extract it.
Get ncurses-5.9 lib if you want to work with menuconfig..Link
stock "boot.img" to extract ramdisk for your kernel.
Now that we have all the files required. Lets move on to next step of creating a Build Environment.
Build Environment Setup:
Make a folder. I'll call it "Kernel" folder here. You can name it whatever you want. Now, move the "arm-2009q3" folder inside this "kernel" folder. Extract mkbootimg_src.zip file and move "mkbootimg_src" folder inside "kernel" folder. Move "split_bootimg.pl" file under "kernel" folder too.
CLICK HERE TO GO TO FIRST POST
nice initiative but dont repeat any tuts which we already hav.. good luck!
hell_lock said:
nice initiative but dont repeat any tuts which we already hav.. good luck!
Click to expand...
Click to collapse
lol.. i know mate.. thats y i didnt write till today even though i wanted to write.. see the index page.. almost all are my own findings.. but whenever if i added from others.. then i will add credits as always..
do tell me / crrect me if i am wrong anywhere lol
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
anmolsharma1293 said:
nice guide...waiting for guide on building custom rom...
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
My sign has it already..
Sent from my GT-S5360 using XDA
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
wcypierre said:
Hi, maybe you would like to incorporate my tool(AIOlog) in the retrieving logcat using computer as it works for Windows out of the box(provided that the driver is installed)
Click to expand...
Click to collapse
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
nitubhaskar said:
OK.. thanks for the heads up.. I will see.. I don't know about your tool yet.. so I have to see how it works.. and I still have to write about PC log too..
Thanks for the heads up..
Sent from the MUST have app!
Click to expand...
Click to collapse
Basically for now its more or less the same as the ones in the market, but if you try the latest dev version, it has multiple device support(able to do logging even if there's more than one device, usually the logging would fail if there's more than one device) and many other features that are to be implemented
:good: :highfive:
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
After having several wifi problems on my NST, I could port the wifi attainments on v.1.2.1 to our v.1.1.2. Also, I did minor changes to avoid needless battery consumption.
Now Opera Mobile works like a charm and the NST detects all open SSID, even those with wpa2 enterprise like "eduroam" and it is not necessary certificates for it.
This has been tested on system 1.1.2 rooted with TouchNooter 2.1.31 and with this multitouch kernel. It will probably work on earlier versions and should be safe to use it, but for best results you should be on 1.1.2.
If you accept an advice, whether you need an optimized performance (130mb ram memory available) and a good contrast screen rom on your NST it is better a 1.1.2 (rooted with touchnooter2.1.31 plus a multitouch kernel to be installed with CWM recovery and the NoRefreshToggle.apk) than a 1.2.1 with fastmode or norefresh. In the second post of this thread, I've left some instructions for having TouchNooter in pristine conditions.
Find enclosed this wifi's cwm update.
Best.
Downgrade your NST to TouchNooter 2.1.31
I've left this instructions for those who need help to downgrade their NST and install TouchNooter 2.1.31. Also, I've included some good tweaks:
If you accept an advice, whether you need an optimized performance (130mb ram memory available) and a good contrast screen rom on your NST it is better a 1.1.2 (rooted with touchnooter2.1.31 plus a multitouch kernel to be installed with CWM recovery and the NoRefreshToggle.apk) than a 1.2.1 with fastmode or norefresh.
1. Make a backup of your NST with noogie following this instructions.
2. Download the Original 1.1.0 update (repacked for use with Clockworkmod based Recovery).
3. Burn 2gb_clockwork-rc2.img file to be written on a SD-Card using Win32DiskImager or dd on linux.
4. Open the SD-Card (where you burn 2gb_clockwork-rc2.img) and copy the nook_1_1_update_cwm.zip on the SD-Card.
5. Power down and insert the SD-Card on the NST.
6. Press the power button for 3 seconds, so that the device boots (you don't have to hold the power button after the 3 seconds)
7. As soon as the display changes to the "CWM logo" screen, push and hold the lower left and the lower right button until the screen changes again. Wait until you see the recovery
Now boot into Clockworkmod recovery (Button layout: Both Buttons on the left: BACK / Upper button on the right: UP / Lower button on the right: DOWN / n button: SELECT / Power button: TOGGLE DISPLAY).
8. Install through CWM recovery the nook_1_1_update_cwm.zip update placed on the SD-Card. When you read installation completed press power button during 10 second and eject the SD-card.
9. Press power button to turn on the nook to let the devices open commonly.
10. Now turn off the NST again and make a factory reset (eject any SD-Card inserted on the NST and as soon as the display changes to the "read forever" screen , push and hold the lower left and the lower right button until the screen changes again. Wait until you see the factory reset instructions and follow it). After, turn on the NST a register again it on B&N and turn off.
11. Now turn on again and install the 1.1.2 update following B&N instructions. After, turn on the NST a register again it on B&N and turn off.
12. Now install TouchNooter 2.1.31 following this instructions.
13. Install this multitouch kernel via CWM again.
14. Now install my wifi implementation via CWM again.
15. Download & install SetCPU utility. Create two profiles on it for Screen On (Set Min AND Max clock freq. to 800 MHz, governor=userspace, no scheduler checked) and another for Screen Off (Set Min AND Max clock freq. To 300 MHz, governor=conservative, no scheduler checked). And check “Apply on boot”
16. Download & install SystemApp Remover to disable some apps that drain the battery (eg:AFfileDownloadService.apk,AccountAndSyncSettings.apk, AirRuntime.apk, ApplicationsProvider.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, ContactsProvider.apk, CrytoServer.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, GlobalSearch.apk, gtalkservice.apk, Home.apk, Library.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk, SysChecksum.apk, Talk.apk, TalkProvider.apk, TelephonyProvider.apk, WaveformDownloader.apk).
17. Apply this tweaks (you can use Root Explorer for it):
-In file /system/lib/egl/egl.cfg. Delete the line "0 0 android". (This disables the hardware rendering and forces software rendering, it is optional, just try it and check what is better for you).
-In file /system/build.prop add the next lines at the end of the present text:
Code:
# Tweaks
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
ro.compcache.default=18
ro.kernel.android.checkjni=0
ro.HOME_APP_ADJ=1
#
# Dalvik options
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=128m
dalvik.vm.deoxopt-flags=m=v,o=y
#
# Battery
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
18. For better performance with NoRefresh, reduce from 400 to 200 the "Auto Activate Time Window". If you cannot find on your apps drawer the shortcut to "NoRefresh Settings", reinstall the app: NoRefresh.apk. Or modify it manually on /data/data/com.eink.norefresh/shared_prefs/com.eink.norefresh_preferences.xml (I set this on 150 but it has to be tested)
Code:
<string name="activate_delay">200</string>
19. Also, I recommend you to use the "Reading Now Button" on the left side of the main status bar as "Orientation Switch". You can do that with Nook Touch Tools.
20. On the other hand, if you can afford buy a good task killer as "Advanced Task Killer Pro by Rechild", I recommend you to auto kill apps when screen is off. (Note:Some task killer drain the battery, that the reason I recommend you Advanced Task Killer Pro). Also, uninstall "Super Manager" and "Amazon Market", both drain the battery.
I've set on the first post a new update with minor changes to avoid needless battery consumption.
Best.
kuskro said:
I've left this instructions for those who need help to downgrade their NST and install TouchNooter 2.1.31. Also, I've included some good tweaks:
If you accept an advice, whether you need an optimized performance (130mb ram memory available) and a good contrast screen rom on your NST it is better a 1.1.2 (rooted with touchnooter2.1.31 plus a multitouch kernel to be installed with CWM recovery and the NoRefreshToggle.apk) than a 1.2.1 with fastmode or norefresh.
1. Make a backup of your NST with noogie following this instructions.
2. Download the Original 1.1.0 update (repacked for use with Clockworkmod based Recovery).
3. Burn 2gb_clockwork-rc2.img file to be written on a SD-Card using Win32DiskImager or dd on linux.
4. Open the SD-Card (where you burn 2gb_clockwork-rc2.img) and copy the nook_1_1_update_cwm.zip on the SD-Card.
5. Power down and insert the SD-Card on the NST.
6. Press the power button for 3 seconds, so that the device boots (you don't have to hold the power button after the 3 seconds)
7. As soon as the display changes to the "CWM logo" screen, push and hold the lower left and the lower right button until the screen changes again. Wait until you see the recovery
Now boot into Clockworkmod recovery (Button layout: Both Buttons on the left: BACK / Upper button on the right: UP / Lower button on the right: DOWN / n button: SELECT / Power button: TOGGLE DISPLAY).
8. Install through CWM recovery the nook_1_1_update_cwm.zip update placed on the SD-Card. When you read installation completed press power button during 10 second and eject the SD-card.
9. Press power button to turn on the nook to let the devices open commonly.
10. Now turn off the NST again and make a factory reset (eject any SD-Card inserted on the NST and as soon as the display changes to the "read forever" screen , push and hold the lower left and the lower right button until the screen changes again. Wait until you see the factory reset instructions and follow it). After, turn on the NST a register again it on B&N and turn off.
11. Now turn on again and install the 1.1.2 update following B&N instructions. After, turn on the NST a register again it on B&N and turn off.
12. Now install TouchNooter 2.1.31 following this instructions.
13. Install this multitouch kernel via CWM again.
14. Now install my wifi implementation via CWM again.
15. Download & install SetCPU utility. Create two profiles on it for Screen On (Set Min AND Max clock freq. to 800 MHz, governor=userspace, no scheduler checked) and another for Screen Off (Set Min AND Max clock freq. To 300 MHz, governor=conservative, no scheduler checked). And check “Apply on boot”
16. Download & install SystemApp Remover to disable some apps that drain the battery (eg:AFfileDownloadService.apk,AccountAndSyncSettings.apk, AirRuntime.apk, ApplicationsProvider.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, ContactsProvider.apk, CrytoServer.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, GlobalSearch.apk, gtalkservice.apk, Home.apk, Library.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk, SysChecksum.apk, Talk.apk, TalkProvider.apk, TelephonyProvider.apk, WaveformDownloader.apk).
17. Apply this tweaks (you can use Root Explorer for it):
-In file /system/lib/egl/egl.cfg. Delete the line "0 0 android". (This disables the hardware rendering and forces software rendering, it is optional, just try it and check what is better for you).
-In file /system/build.prop add the next lines at the end of the present text:
Code:
# Windows management
windowsmgr.max_events_per_sec=500
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.product.multi_touch_enabled=true
#
# Tweaks
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
ro.compcache.default=18
ro.kernel.android.checkjni=0
ro.HOME_APP_ADJ=1
#
# Dalvik options
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=48m
dalvik.vm.deoxopt-flags=m=v,o=y
#
# Battery
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
18. For better performance with NoRefresh reduce from 400 to 200 the "Auto Activate Time Window" (I modified the xml preferences tags for this app to have this setting on 150 but it has to be tested).
19. Also, I recommend you to use the "Reading Now Button" on the left side of the main status bar as "Orientation Switch". You can do that with Nook Touch Tools.
20. On the other hand, if you can afford buy a good task killer as "Advanced Task Killer Pro by Rechild", I recommend you to auto kill apps when screen is off. (Note:Some task killer drain the battery, that the reason I recommend you Advanced Task Killer Pro). Also, uninstall "Super Manager" and "Amazon Market", both drain the battery.
Click to expand...
Click to collapse
I want to try this but is it possible to have a kernel with multi touch AND usb host ?
tebra said:
I want to try this but is it possible to have a kernel with multi touch AND usb host ?
Click to expand...
Click to collapse
I've never tried but I think so. Here you have some: https://code.google.com/p/nst-recovery/downloads/list
kuskro said:
I've never tried but I think so. Here you have some: https://code.google.com/p/nst-recovery/downloads/list
Click to expand...
Click to collapse
One more question, why did you don't upgrade to 1.1.5 firmware?
Kernel with multitouch and usb host are based on 1.1.5 firmware
tebra said:
One more question, why did you don't upgrade to 1.1.5 firmware?
Kernel with multitouch and usb host are based on 1.1.5 firmware
Click to expand...
Click to collapse
This update was for NSTG.
kuskro;41518419
16. Download & install [URL="https://play.google.com/store/apps/details?id=com.danesh.system.app.remover&hl=es" said:
SystemApp Remover[/URL] to disable some apps that drain the battery (eg:AFfileDownloadService.apk,AccountAndSyncSettings.apk, AirRuntime.apk, ApplicationsProvider.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, ContactsProvider.apk, CrytoServer.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, GlobalSearch.apk, gtalkservice.apk, Home.apk, Library.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk, SysChecksum.apk, Talk.apk, TalkProvider.apk, TelephonyProvider.apk, WaveformDownloader.apk).
17. Apply this tweaks (you can use Root Explorer for it):
-In file /system/lib/egl/egl.cfg. Delete the line "0 0 android". (This disables the hardware rendering and forces software rendering, it is optional, just try it and check what is better for you).
-In file /system/build.prop add the next lines at the end of the present text:
Code:
# Tweaks
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
ro.compcache.default=18
ro.kernel.android.checkjni=0
ro.HOME_APP_ADJ=1
#
# Dalvik options
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=128m
dalvik.vm.deoxopt-flags=m=v,o=y
#
# Battery
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
18. For better performance with NoRefresh, reduce from 400 to 200 the "Auto Activate Time Window". If you cannot find on your apps drawer the shortcut to "NoRefresh Settings", reinstall the app: NoRefresh.apk. Or modify it manually on /data/data/com.eink.norefresh/shared_prefs/com.eink.norefresh_preferences.xml (I set this on 150 but it has to be tested)
Code:
<string name="activate_delay">200</string>
19. Also, I recommend you to use the "Reading Now Button" on the left side of the main status bar as "Orientation Switch". You can do that with Nook Touch Tools.
20. On the other hand, if you can afford buy a good task killer as "Advanced Task Killer Pro by Rechild", I recommend you to auto kill apps when screen is off. (Note:Some task killer drain the battery, that the reason I recommend you Advanced Task Killer Pro). Also, uninstall "Super Manager" and "Amazon Market", both drain the battery.[/hide]
Click to expand...
Click to collapse
System App Remover and Root Explorer isn't in my list in the Android Market. I tried using the search function in the Market as well and it doesn't seem to work at all. Any recommendations?
Beefvvl said:
System App Remover and Root Explorer isn't in my list in the Android Market. I tried using the search function in the Market as well and it doesn't seem to work at all. Any recommendations?
Click to expand...
Click to collapse
You need installing searchmarket.app to work together with Google Market.
Best.
kuskro said:
I've left this instructions for those who need help to downgrade their NST and install TouchNooter 2.1.31. Also, I've included some good tweaks:
If you accept an advice, whether you need an optimized performance (130mb ram memory available) and a good contrast screen rom on your NST it is better a 1.1.2 (rooted with touchnooter2.1.31 plus a multitouch kernel to be installed with CWM recovery and the NoRefreshToggle.apk) than a 1.2.1 with fastmode or norefresh.
1. Make a backup of your NST with noogie following this instructions.
2. Download the Original 1.1.0 update (repacked for use with Clockworkmod based Recovery).
3. Burn 2gb_clockwork-rc2.img file to be written on a SD-Card using Win32DiskImager or dd on linux.
4. Open the SD-Card (where you burn 2gb_clockwork-rc2.img) and copy the nook_1_1_update_cwm.zip on the SD-Card.
5. Power down and insert the SD-Card on the NST.
6. Press the power button for 3 seconds, so that the device boots (you don't have to hold the power button after the 3 seconds)
7. As soon as the display changes to the "CWM logo" screen, push and hold the lower left and the lower right button until the screen changes again. Wait until you see the recovery
Now boot into Clockworkmod recovery (Button layout: Both Buttons on the left: BACK / Upper button on the right: UP / Lower button on the right: DOWN / n button: SELECT / Power button: TOGGLE DISPLAY).
8. Install through CWM recovery the nook_1_1_update_cwm.zip update placed on the SD-Card. When you read installation completed press power button during 10 second and eject the SD-card.
9. Press power button to turn on the nook to let the devices open commonly.
10. Now turn off the NST again and make a factory reset (eject any SD-Card inserted on the NST and as soon as the display changes to the "read forever" screen , push and hold the lower left and the lower right button until the screen changes again. Wait until you see the factory reset instructions and follow it). After, turn on the NST a register again it on B&N and turn off.
11. Now turn on again and install the 1.1.2 update following B&N instructions. After, turn on the NST a register again it on B&N and turn off.
12. Now install TouchNooter 2.1.31 following this instructions.
13. Install this multitouch kernel via CWM again.
14. Now install my wifi implementation via CWM again.
15. Download & install SetCPU utility. Create two profiles on it for Screen On (Set Min AND Max clock freq. to 800 MHz, governor=userspace, no scheduler checked) and another for Screen Off (Set Min AND Max clock freq. To 300 MHz, governor=conservative, no scheduler checked). And check “Apply on boot”
16. Download & install SystemApp Remover to disable some apps that drain the battery (eg:AFfileDownloadService.apk,AccountAndSyncSettings.apk, AirRuntime.apk, ApplicationsProvider.apk, BnAuthenticationService.apk, BnCloudRequestSvc.apk, ContactsProvider.apk, CrytoServer.apk, DemoMode.apk, DeviceManager.apk, DeviceRegistrator.apk, GlobalSearch.apk, gtalkservice.apk, Home.apk, Library.apk, Music.apk, NookCommunity.apk, Phone.apk, QuickStartActivity.apk, Shop.apk, Social.apk, SysChecksum.apk, Talk.apk, TalkProvider.apk, TelephonyProvider.apk, WaveformDownloader.apk).
17. Apply this tweaks (you can use Root Explorer for it):
-In file /system/lib/egl/egl.cfg. Delete the line "0 0 android". (This disables the hardware rendering and forces software rendering, it is optional, just try it and check what is better for you).
-In file /system/build.prop add the next lines at the end of the present text:
Code:
# Tweaks
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
ro.compcache.default=18
ro.kernel.android.checkjni=0
ro.HOME_APP_ADJ=1
#
# Dalvik options
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize=128m
dalvik.vm.deoxopt-flags=m=v,o=y
#
# Battery
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
18. For better performance with NoRefresh, reduce from 400 to 200 the "Auto Activate Time Window". If you cannot find on your apps drawer the shortcut to "NoRefresh Settings", reinstall the app: NoRefresh.apk. Or modify it manually on /data/data/com.eink.norefresh/shared_prefs/com.eink.norefresh_preferences.xml (I set this on 150 but it has to be tested)
Code:
<string name="activate_delay">200</string>
19. Also, I recommend you to use the "Reading Now Button" on the left side of the main status bar as "Orientation Switch". You can do that with Nook Touch Tools.
20. On the other hand, if you can afford buy a good task killer as "Advanced Task Killer Pro by Rechild", I recommend you to auto kill apps when screen is off. (Note:Some task killer drain the battery, that the reason I recommend you Advanced Task Killer Pro). Also, uninstall "Super Manager" and "Amazon Market", both drain the battery.
Click to expand...
Click to collapse
After do this I can't connect to wifi.
Now I try to restore to factory configuration and I cant install 1.2.1.
:crying:
keteflips said:
After do this I can't connect to wifi.
Now I try to restore to factory configuration and I cant install 1.2.1.
:crying:
Click to expand...
Click to collapse
Just use your own CWM backup, you took right before installing this mod...
keteflips said:
After do this I can't connect to wifi.
Now I try to restore to factory configuration and I cant install 1.2.1.
:crying:
Click to expand...
Click to collapse
Restore your noogie backup and choose the correct update for your NST:
- Download the nook 1.2.1 UK update from here.
- Or download the nook 1.2.1 USA update from here.
kuskro said:
Restore your noogie backup and choose the correct update for your NST:
- Download the nook 1.2.1 UK update from here.
- Or download the nook 1.2.1 USA update from here.
Click to expand...
Click to collapse
This is what I did and it worked perfectly.
Thank you.
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.
(My thread is also available in the Nextbit Development Forum)
This thread will always be a Work In Progress. Please be patient, as we receive new development it will be posted here. Thank you very much!
Do subscribe to this thread to get notified on any new updates.
The "Complete Guide" series is back, now for the holy Nextbit Robin! (check out my profile for other "complete guide" threads for my past devices)
First things first, this guide is made mainly for our great Nextbit Robin - Ether. Some steps may or may not work for other phones...
Please note that the results of the following methods may vary. I will not be held responsible for destroying your device. PROCEED AT YOUR OWN RISK.
For increased chances of these working, ensure you're on the latest version of Robin.
If you don’t know what rooting, flashing and *explosion* means, this probably isn’t the thread for you.
Credit me if you want to take anything from this thread. DO NOT create duplicates of such threads.
Enjoy!
Complete guide to all things Robin:
NOTE: The chapters are in chronological order, meaning everything after Chapter 2 assumes you already have root and unlock.
---------------------------------------------------------------------------------------------------------------------------------
CHAPTER 0: TERMINOLOGY (in my own words)
- Terms
- Tidbit
(To be honest, if you need to even look at this, this thread isn't for you.)
- Root: Gaining full administrative control of your device. "Jailbreaking" in terms of Android.
- ROM: The customized operating system that your Android runs on.
- Kernel: The thingy that links software and hardware
- Radio: The thingy that sends and receives messages, calls and data.
- Flash: Installing a zipped file in Recovery Mode
- Recovery: The software that allows tweaking and flashing, and other weird stuff that will destroy your phone.
- Fastboot: The thingy that allows recovery mode to happen.
- Brick: The term says it all.
- Bootloader: Quite literal; loads the phone for bootup.
- Nandroid backup: A backup-ed image of your current system
- ADB: Android Debug Bridge; some command line tool that sends information from and to the phone to, and from the computer
- CWM: ClockWorkMod; a recovery system
- XDA: The holy website that is full of weird stuff that makes your phone wayyyy better.
Now let's paint a picture:
Imagine you are your Android phone.
Before "rooting", you are trapped in jail.
Upon "rooting and unlocking", you are released from jail.
You go to a shopping mall named "XDA".
You find a credit card lying on the floor from the company "Recovery". On the back, it says there is no passcode required, and there is a infinite amount of money inside.
You enter a store and get a sweatshirt with the word "ROM" on it.
You didn't buy the shirt, the shirt just happens to be free, but still requires you to swipe your credit card anyways.
You keep the receipt as a "backup", just in case the shirt spoils.
Just then, you get greedy and get all the badges in the store.
Stupidly, you pin all the badges on your shirt, turning it as heavy as a "brick".
Then, the shirt rips, unable to put (it rhymes with boot) it back together again.
Luckily you still have the receipt to return the shirt, and return back to your good old disgusting shirt.
Click to expand...
Click to collapse
---------------------------------------------------------
CHAPTER 1: PREREQUISITES
- Nextbit drivers are installed on your computer: http://bit.ly/Robin_USB_Driver
- A proper and working Wi-Fi network
- Enable Developer Options
- Enable USB Debugging
- Ensure Robin is charged to at least 50%
- Original and genuine Nextbit in-box USB cable
- Backup all files!
---------------------------------------------------------
CHAPTER 2: ESSENTIALS
- Backup
- Root
- Unlock
- TWRP
- Flashing
- Restoring backups
BACKUP:
Titanium Backup Method:
Use “Titanium Backup” batch backup
1. Menu -> Batch
2. Run -> Backup user apps + system data
OR:
Manual Non-Root Method:
- Messages: “SMS Backup & Restore”
- Contacts: should be synced with the cloud, if not: Export to SIM card
- Calendar: should be synced with the cloud
- Notes: use “Google Keep”, it will be synced with the cloud
- User Dictionary: “User Dictionary Backup”
- Call Logs: “Call Logs Backup & Restore”
- Launcher (assuming you use Nova Launcher): Settings -> Backup & import settings -> Restore or manage backups
- Apps: “Helium” or any other app
- Nandroid Backup
store all backups in internal storage and transfer to your computer
ROOT + UNLOCK + TWRP RECOVERY:
http://forum.xda-developers.com/nextbit-robin/development/tool-robin-toolkit-v1-0-root-twrp-t3375908
(kudos to @daavm)
1. Download the tool
2. Just follow the instructions
**NOTE: Relocking again will result in data wipe**
FLASHING:
Clean Flash:
1. Backup your data!
2. Reboot into TWRP Recovery
3. Go into settings and enable “Use Aroma File Manager”
4. Wipe Dalvik, Cache, System & Data
5. Flash your chosen ROM, basebands, firmware updates and other crap
6. Flash any GApps package. (the one I use: http://forum.xda-developers.com/android/general/gapps-lp-gapps-pa-gapps-aroma-installer-t3010798; kudos to @raulx222 & @slim Team)
7. Flash anything else (e.g. frameworks, boot animations, splash screens, themes etc.)
8. Reboot
9. DONE!
OR:
Dirty Flash: (flashing without wiping anything, used for updating to newer ROMs or reflashing)
1. Reboot into TWRP Recovery
2. ONLY wipe Dalvik Cache
3. Flash your chosen ROM, basebands, firmware updates and other crap
4. Flash any NEWER GApps package. If you manually installed/updated through Play Store, skip this step.
5. Flash anything else (e.g. frameworks, boot animations, splash screens, themes etc.)
6. Reboot
7. DONE!
It is perfectly fine if the first bootup takes a while, that is perfectly normal. Upon boot, Android will optimize itself so just let it do it’s work. Do put the phone under a fan as it does tend to get hot when optimizing since it is at max brightness or some dumb reason.
If it takes ages (like over 10mins) to boot up, it means you might have bricked your phone! Do source the XDA indices for any unbricking tutorial, or keep a lookout for an update on this page for instructions. (I don’t have any/don’t need to find any as I have never bricked any Android, so ya.)
Click to expand...
Click to collapse
DO NOT dirty flash if your newer ROM:
- Doesn't allow/support it
- Has a major update
- Has a Android version or firmware jump (e.g. from Lollipop to M)
- Is a totally different ROM from the previous one (e.g. from Stock to Cyanogenmod)
If after dirty flashing you experience any ROM issues (e.g. battery drain, lag etc.), I would advice you to do a clean flash instead.
Click to expand...
Click to collapse
RESTORING BACKUP:
Titanium Backup Method:
1. Use “Titanium Backup” batch restore
2. Menu -> Batch
3. Run -> Restore missing apps with data (*NOTE*: DO NOT RESTORE SYSTEM DATA)
4. Once done, go to Backup/Restore on the main app interface
5. Restore manually: Calendar Storage, Internet Bookmarks, Messaging SMS/MMS Prefs, Phone SMS/MMS/APN, User Dictionary, Wi-Fi Access Points**
6. Launcher Settings: (assuming you use Nova Launcher) Settings -> Backup & import settings -> Restore or manage backups
**What can I manually restore?**
Red: DO NOT RESTORE, YOU’LL END UP BRICKING/BOOTLOOPING YOUR PHONE!!!
White: 99% safe, go ahead
Green: 70% safe, beware of potential brick
Grey Stirkethrough: DO NOT RESTORE
Click to expand...
Click to collapse
OR:
Manual Restoration Method:
- Messages: “SMS Backup & Restore”
- Contacts: should be synced with the cloud, if not: Export to SIM card
- Calendar: should be synced with the cloud
- Notes: use “Google Keep”, it will be synced with the cloud
- User Dictionary: “User Dictionary Backup”
- Call Logs: “Call Logs Backup & Restore”
- Launcher (assuming you use Nova Launcher): Settings -> Backup & import settings -> Restore or manage backups
- Apps: “Helium” or any other app
store all backups in internal storage and transfer to your computer
---------------------------------------------------------
CHAPTER 3: ADDITIONS
- Boot Animation
- TWRP Recovery Theme
- ExoPlayer for YouTube
- Ad-free
- Control
- Task Management
BOOT ANIMATION:
6.x Marshmallow:
https://www.copy.com/s/t%3A83YzqkU0VlAHdSsY%3Bp%3A%252Fbootanimation-flashable.zip%3Boid%3A400
(kudos to @Upstreammiami)
(flashable)
1. Download “Root Explorer” app
2. Go to root/system/media
3. Mount R/W
4. Change “bootanimation.zip” to “bootanimation.old”
5. Download “bootanimation-flashable..zip” and flash in recovery
6. DONE!
5.x Lollipop:
(if not flashable)
1. Download “Root Explorer” app
2. Go to root/system/media
3. Mount R/W
4. Change “bootanimation.zip” and “shutdownanimation.zip” to “bootanimation.old” and “shutdownanimation.old” respectively
5. Copy your boot animation and shutdown animation of choice and rename to “bootanimation.zip” and “shutdownanimation.zip” respectively
6. Change permissions to rw-r-r-T (Read Owner, Read Group, Read Others, Write Owner, Sticky)
7. Mount R/O
8. Reboot
9. DONE!
TWRP Recovery Theme
http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
(kudos to @z31s1g)
1. Choose 1440x2560 Themes Folder
2. Download your chosen zip file to your device
3. Change "28xX_vx_1440_xxxx.zip" to "ui.zip"
4. Open your favourite file manager app
5. Go to the TWRP folder
6. Create a folder named "theme" **no capital letters!**
7. Copy "ui.zip" into this folder
8. Reboot to recovery
9. DONE!
Faster YouTube: ExoPlayer
http://r3pwn.github.io/yt-exoplayer.html
1. Download “Root Explorer” app
2. Go to data/data/com.google.android.youtube/shared_prefs
3. Add the following lines below "<map>":
Code:
<string name="exo_player_activation_type">ADAPTIVE</string>
<boolean name="enable_exo_cache" value="true"/>
<boolean name="show_exo_player_debug_messages" value="true"/>
4. Once done, close and mount R/O
5. Force Close YouTube app in Application Settings
6. Reboot
7. Done!
Ad-Free
- Download "AdAway" app from F-Droid
https://f-droid.org/repository/browse/?fdid=org.adaway
Control
- Download "SELinux Mode Changer" from F-Droid
https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
Task Management
- Download "Greenify" or "Servicely"
http://www.apkmirror.com/apk/oasis-feng/greenify/
http://www.apkmirror.com/apk/francisco-franco/servicely/
Honestly, I don't encourage battery managers such as "Battery Doctor" or "Clean Master (Speed Booster)" as realistically, it takes up more battery or RAM in trying to keep the app open to "properly manage the battery". Yes there are benefits such a having a zippier G3, but there are better methods out there.
Click to expand...
Click to collapse
---------------------------------------------------------
CHAPTER 4: FONTS
- Fonts
- Emoji
Changing ROM Font
http://forum.xda-developers.com/android/themes/fonts-flashable-zips-t2964304
(kudos to @gianton)
Simply flash the zip in recovery and done!
Changing Emoji
New iOS 9.1 Diverse Jaundice Emoji:
http://forum.xda-developers.com/android/software-hacking/mod-apple-8-3-diverse-color-emoji-t3136169
(kudos to @caiosilva96)
1. Download “Root Explorer” app
2. Go to root/system/fonts
3. Mount R/W
4. Change “NotoColorEmoji.ttf” to “NotoColorEmoji.old”
5. Copy your emoji of choice and rename to “NotoColorEmoji.ttf”
6. Change permissions to rw-r-r (Read Owner, Read Group, Read Others, Write Owner)
7. Mount R/O
8. Reboot
9. Now, on your phone (with new emojis installed), go to http://emojipedia.org/skin-tone-modifiers/
10. Copy the "(skin colour)" that comes before "Emoji Modifier Fitzpatrick Type-1-2"
11. Go to your settings app, then keyboard settings, then personal dictionary
12. Create a new word "(skin colour)", shortcut of "skin2"
13. Repeat for skins 3-6
14. Reboot if you want to
15. DONE!
- To change the skin colour, type the emoji, followed by the shortcut word (e.g. "skin2")
OR:
Traditional iOS Emoji:
http://forum.xda-developers.com/lg-g3/themes-apps/howto-change-lg-smiley-to-google-smiley-t2809012
(kudos to @Soulfly999)
1. Download “Root Explorer” app
2. Go to root/system/fonts
3. Mount R/W
4. Change “NotoColorEmoji.ttf” to “NotoColorEmoji.old”
5. Copy your emoji of choice and rename to “NotoColorEmoji.ttf”
6. Change permissions to rw-r-r (Read Owner, Read Group, Read Others, Write Owner)
7. Mount R/O
8. Reboot
9. DONE!
---------------------------------------------------------
CHAPTER 5: BATTERY
- The cliche...
- Extreme
the cliche stuff...
Turn on power saving, turn off bluetooth, Wi-Fi, data, NFC etc., turn off automatic brightness and blah blah blah...
The Extreme Battery Life
http://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
(kudos to @vaisakh7)
please note this chapter is incomplete.
---------------------------------------------------------
CHAPTER 6: GOODBYE
- Going back to stock
GO BACK TO STOCK:
Robin Factory Images:
https://community.nextbit.com/t5/Tools/Nextbit-Robin-Factory-Images/m-p/10649#M26
(kudos to @Nextbit_Khang)
1. Download "OOWW_1_xxx.zip" accordingly and unzip
2. Connect Robin to your computer
3. Boot into Fastboot (Power + Volume Down)
4. Windows: Open command window in the downloaded folder (Shift + Right click)
Mac: Open Terminal and navigate to the folder location
5. Windows: Type
Code:
flash-all.bat
, then Enter
Mac: Type
Code:
./flash-all.sh
, then Enter
6. Let the terminal do the magic and you're good to go!
---------------------------------------------------------
CHAPTER 7: MISCELLANEOUS
- Developer Settings
- System UI Tuner
- Smart Storage Activity App
- Fix Smart Storage FC
- Access FQC Menu
- Nova Launcher Secret Labs
ENABLING DEVELOPER SETTINGS:
1. Settings app
2. About phone
3. Software info
4. Tap build number repeatedly until it prompts you
ENABLING SYSTEM UI TUNER: (i.e. enable battery percentage indicator & customise quick setting tiles)
1. Pull down the notification shade
2. Tap and hold onto the 'gear' icon until prompted
3. You're done! Just open the settings app and tweak away!
ENABLING SMART STORAGE ACTIVITY APP: (on third party launchers)
1. Open Smart Storage Options
2. Continuously tap "Version" until prompted
3. Now enable "Show Smart storage in Launcher" and you're good to go!
FIX SMART STORAGE FCs:
(you need to try this multiple times until you can complete all steps)
1. Pull down the notification shade
2. Open Smart Storage's "More Settings"
3. QUICKLY scroll to the bottom
4. QUICKLY Tap "Sign out"
5. Now close the app and clear it's cache
6. Relog and it should be fine
ACCESS FQC MENU:
(kudos to @Nextbit_Khang)
NOTE: Only work for 119F build!
1. Open Dialer app
2. Type:
*#*#3721#*#*
Click to expand...
Click to collapse
ENABLING NOVA LAUNCHER LABS SETTINGS:
1. Nova Settings
2. Hold down ‘volume down’ key until it prompts you
---------------------------------------------------------
CHAPTER 8: ADDITIONAL INFO
- Device Architecture
Architecture: arm64 + arm
Screen DPI: 480
Drawable Class: xxhdpi (extra extra high density)
Google Play services - Build Suffix: (-448)
How does this affect me?
Well, when you install apps, downloading the correct arch version means the app is better optimised for our phone (and you'll potentially save some internal storage space too!)
As for Google Play services, you MUST install the correct build version. (Example: v9.0.90 (448-xxxxxxxx) )
For more info, click here: http://www.apkmirror.com/faq/#What_are_these_weird_terms_I8217m_seeing_on_some_APKs_8211_dpi_nodpi_arm_arm64_x86
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------
Thanks for reading. If this helped, do give me a thumbs up or donate ad-free to me.
"Let's get this pinned on the General Thread shall we? Pretty please with cherry on top..." :victory:
Changelog
26th May:
- Removal of Development Index
---------------------
OLDER:
10th May:
- Added "Going back to stock" method
- Added more users to credits
- Changed several links to XDA threads
8th May:
- Changed rooting method to "Robin Toolkit"
- Subtle changes after proofreading
- Shorten forum naming
7th May:
- THIS THREAD WAS BORN!!!
[LEGACY] Dev Index
NOTE: This will no longer be maintained.
Reserved.
Reserved.
Thanks! @Lousyguyy
Sent from my Robin using Tapatalk
@Lousyguyy : Thanks for this - it was about time there was a dev index for the Robin.
Just a couple of points to note in your OP:
Also note that these steps WILL VOID YOUR WARRANTY. PROCEED AT YOUR OWN RISK.
Click to expand...
Click to collapse
Except it doesn't! Nextbit have explicitly stated that rooting your phone or loading a custom ROM etc will NOT void the warranty.
For increased chances of these working, update your KDZ to Lollipop first using OTA or Flash Tool.
Click to expand...
Click to collapse
I think you've accidentally copied this from an LG thread?
[deXter] said:
@XDeathy : Thanks for this - it was about time there was a dev index for the Robin.
Just a couple of points to note in your OP:
Except it doesn't! Nextbit have explicitly stated that rooting your phone or loading a custom ROM etc will NOT void the warranty.
I think you've accidentally copied this from an LG thread?
Click to expand...
Click to collapse
Oh haha thanks for taking time to read through the thread mate! I'll get it changed tomorrow when I'm free. (And yes I did copy the templates from my V10 thread oops)