Develop Bugs

[ROM][GB27 GB08 GA10 FL16][ODEX/DEODEX]Kobridge's Stock ROM+Tweaks+Addons - Samsung Epic 4G Touch

Like always, do it at your own risk. I'm not responsible for any damages on your device.
*Kobridge's GB27 Odexed/Deodexed ROM OP
*Kobridge's GB08 Deodexed ROM OP
*Kobridge's GA10 Odexed/Deodexed ROM OP
Kobridge's Stock FL16 Odexed/Deodexed ROM
What is this? (Thanks to everyone who help me to get rid of the really annoying ads. Now I don't see those annoying Ads after login)
This ROM is completely FL16 JB stock ROM with rooted, busybox added. There are three versions of this ROM based on odexed (pure stock) or deodexed.
1. CWM Flashable FL16 Pure Stock ROM (Odexed) - can be used with Data Wipe or No Data Wipe - Mirror
MD5 Check Sum - bcafc6e7fdb1a8a495850c5d131c15d7
2. CWM Flashable FL16 Pure Stock ROM (Deodexed apk) - only apk files deodexed - I don't think you need this.
3.CWM Flashable FL16 Pure Stock ROM (Fully Deodexed) - Deodexed /system/app + /framework - can be used with Data Wipe or No Data Wipe - Kobridge's_Stock_ROM_vFL16DS.2.zip 2/2/13 Updated!
MD5 Checksum: 7f8e5abf2109ddfd1430a5dfc7532006
How to Flash?
Before flashing this ROM, be sure that you have a nandroid backup available or make a new nandroid backup. Flash this ROM at your own risk, I'm not responsible for any damages on your phone!
The steps are same as other ROMs. You'll need a CWM recovery kernel to flash this ROM and after flashing this ROM, you will lose the CWM recovery kernel because this ROM replace the CWM recovery kernel with stock FL16 kernel.
You will also need to flash the FL16 modem zip file (separate link provided) while flashing this ROM. Or you can flash it separately.
No Data Wipe - if you want to keep your current manually installed non-stock apps, do not wipe the data partition. You would be able to use your old configuration in most cases. I used this option to upgrade my previous rom to FL16. No issues found.
Data Wipe/Factory reset - it's also ok doing factory reset or wiping data partition using CWM recovery tool before flashing this ROM if you want to do a clean install. There's no reboot nor force closing issue found.
Kernel & Modem
FL16 modem - zip - Mirror1
MD5 checksum: 16d0bf291fbb72f88d8ef010881fcb79
FL16 stock Kernel - zip Mirror1
MD5 checksum: 5346cefd4d1605a7665fed72c5cb2f5e
Do you want to remove the bloatware apps after flashing the stock rom?
Check out post# 2 below
Kobridge's Tweak Modes and Addons
To download, check out Post# 3 below
Kobridge's Silent Camera Mod vFL16.2 & vFL16.3a & vFL16.3b
Removed sounds - autofocus_error, autofocus_ok, camera_click, camera_click_bestshot, camera_click_short, shutter_500 (from Camera APK)
Auto_focus, Auto_focus_error, Cam_Start, Cam_Stop, camera_click, Camera_click_short, camera_empty, camera_focus, Charger_Connection, PowerOff, PowerOn, & all Shutter (from system ui audio)
Recently added - vFL16.3a & vFL16.3b - several new features added
Kobridge's System App Backup & Recovery Tool - Advanced users only
Note: Incorrect use of this tool would cause a bootloop. When this tool recovers system apps, it first deletes all system apps. So, after the recovery, all system setting values are set to default.
System App Backup from CWM recovery: This tool makes backup of your system apps from /system/app and /preload/symlink/system/app folders.
You can use this tool whenever you makes the nandroid backup, flashed new kernel or you have the system app changes. If something goes wrong with system app, you can use this backup to recover the system apps. This would be a very convenient tool for most of users because to recover the system app, we may spend lots of time - recover the system using ROM, nandroid backup and make the changes again, etc.
System App recovery tool: After you make the backup of your system apps using my system app backup tool, you can simply use this recovery tool from CWM recovery. It will restore the all system apps based on the backup data. This tool recovers the system apps from /sdcard/backup/system and /sdcard/backup/preload folders.
Benefits using Kobridge's System App Backup/Recovery tool -
you don't need to flash the bloatware remover or manually remove the system apps after flashing the rom. You can simply use this tool to go back to previous status.
If system does not boot with system app issue, just simply odin the recovery kernel and flash the backed up system apps using recovery tool. Flash the original kernel and reboot. Your phone will boot without doing everything again!
After the recovery, all system settings moves back to factory default - clean up effect
After the recovery, all system data stored in /data/data folder cleaned up and any garbages removed!
without wiping data partition, you can get the same effects for the system apps.
a lot more...
Cons using Kobridge's System App Backup/Recovery tool -
You lose the previous saved system settings. Every system app's settings goes back to factory default.
Kobridge's CSC Tweak - experience the extended menu and options
Note: If you changed the values by yourself or removed any CSC stock files, then CSC tweak may not work.
Tweak includes:
Menu - enabled search menu(search menu button), common pinchzoom enabled
Camera - silent mode option
Message - Message size, max slide count increased, max picture resolution increased, enabled reply all, group message, scheduled email sending (specify date, time), save voice message
Enabled all delivery, read confirmation menu from SMS, MMS, send email over sms, subject length from 40 to 120
Launcher,
contact - account icons in contact list, show all logs, call details, contact import/export option, menu to add reject list
call
web browser - default homepage changed to google, removed lots of favorites from default broswer
email
a lot more
Tdunham's Mods - check post#3
How to flash Kobridge's Tweak into Stock ROM
4 different Kobridge Tweak modes are available at post #3 below. Do not use this tweak other than Jelly Bean and stock rom.
Starting from this ROM, there's no tweak added on the Kobridge's Stock ROM. You need to separately download and flash it.
What's new on FL16 ROM -
Please report and check post #4 for up-to-dated information.
ROM version history:
FL16DS.2 : Current version [1/31/03] Fixed Telenav issue.
FL16DS.1 : Couple of minor changes from FL16DS.0 (changed to format /preload partition during flashing. few symlinks from /system/app folder removed. Link1
FL16DS.0 : Initial version. - Kobridge's_Stock_ROM_vFL16DS.0.zip download link1 link2
FL16OS.0 : Initial version. - No changes made from initial version - Kobridge's_Stock_ROM_vFL16OS.0.zip
Credits
SexTape for his leaked ROMs
sfhub for recovery kernel (EL26)
tdunham, Shadow_God for being a great developer and friend
rwilco12 for his great rom/kernel/modem repository and his XDA dedication
Special Thanks to:
leaderbuilder, Vadyr56, MN-Joe, Yaantra,JonSCSL,Doctor_XXX,draven760,RevAtB,cdss

Kobridge's Stock Bloatware Remover for Jelly Bean (FL16/FL04 ROM)
How to flash - just like flashing the rom, flash zip file from CWM recovery (I recommend to use EL26. You can find the EL26 CWM zip tar files in here)
You can flash this zip file just after flashing the rom or you can flash this zip file separately depending on your need. Be sure that after you flash this zip file, you may need to flash the original Kernel also at the same CWM session without rebooting your phone.
Where you can find the removed apps
You can find the removed apps from /mnt/extSdCard/Removed_Apps (system apps) and /mnt/extSdCard/Removed_Apps/preload (preload apps). To bring it back to your phone, move the apk files to /system/app or /preload/symlink/system/app folder and reboot.
Download Kobridge's Bloatware Apps Remover Tool vJB2.2
Download it from here - Kobridge's_Stock_Bloatware_Remover_vJB2.2.zip Mirror
No backup version - Download here - Kobridge's_Stock_Bloatware_Remover_NoBackup_vJB2.2.zip Mirror
How to recover old APK [or odex] files if I already removed some apps using previous version of bloatware remover:
To do this, you need to flash the ROM again that will recover all stock apps. At the same CWM recovery session, flash this bloatware remover and reboot.
Old version:
Kobridge's Bloatware Apps Remover Tool vJB2.1 - Do not use anymore Mirror
Code:
Books.apk
GoogleFeedback.apk
ID.apk
Magazines.apk
MediaHub_SdgtlSpr.apk
MobiTV.apk
mSpotRadioSprint_VPL.apk
Music2.apk
nascar09_prod.apk
NOVA2HD.apk
PlusOne.apk
PolarisOffice4.apk
SprintMobileWallet.apk
SprintMusicPlus.apk
SprintZone_DSS.apk [v2.1]
Videos.apk
YahoonewsDaemon.apk
YahoonewsWidget.apk
YahoostockDaemon.apk [v2.3]
YahoostockWidget.apk
Some useful info on JB ROM:
Some widgets are not working on JB depending on the launcher.
Samsung Task manager is not showing from app list. To launcher the app, you can use the widget or long pressed 'home' button to run the Samsung task manager.
Old sqlite3 binary does not work on JB. I had to change the sqlite3 binary in this rom to make the wifi sleep timer working.
It appears that external_SD under /SDCARD is no longer pointing to external SD card. Now it's under /mnt/extSdCard, /storage/extSdCard - I need to look at some scripts running during the boot.
System partition is too small to hold all apps. It seems like that's the reason why Samsung added /preload partition and moved some of non-core apps there. I tried to keep all apps into /system partition and phone didn't boot.
snapshot key - vol down + power do not work any more. To get the snapshot, press the home key + power button together
New way to recover the phone using Nandroid & stock ROM: (you can use this methond with Kobridge's system app backup/recovery tool)
Because Jelly Bean is using another partition which is not covered by our traditional CWM recovery. Whenever you restore your phone using nandroid backup oly, you may not get the full restore of your phone. It's because the /preload changes are not included. So, there is no way to backup this folder by cwm recovery.
So, what I'm suggesting method is
1. Be sure that you have a nandroid backup after JB rom flashed. Be sure that you have the flashable JB rom.
2. now to start the nandaroid recovery, reboot into cwm.
3. (full wipe data & cache) or do the factory reset
4. flash JB rom
5. (do not reboot after flashing the ROM) recover nandroid backup on the same recovery session
6. Flash Kobridge's Bloatware remover tool if you did that before
7. flash the JB kernel again (if your CWM kernel during nandroid backup was ICS or lower, then phone won't boot without this step)
8. reboot
Some other Kobridge's Tweaked ROM info:
When many apk files are updated or if you flashed new Kobridge's stock ROM, remove /data/local/zipalignedapk file and reboot. It will try to re-zipalign all apks from /preload /system/app /data/app.
Removed apks are placed in /storage/extSdCard/Removed_Apps/ (from system/app) and /storage/extSdCard/Removed_Apps/preload (from preload/symlink/system/app). /storage/extSdCard folder is a symbolic link of /mnt/extSdCard.
To move the removed apps back to original folder, you have to copy(move) the apk files from Removed_Apps folders to /system/app folder and change the permision to 644 and reboot. You cannot move the apk files back to /preload folder because the symbolic link is not there. To move it to preload folder, you have to manually create the symlink for the move files.
If you do not want to use Kobridge Tweak, remove the init.d folder and /system/bin/dvfs.sh file. For build.prop, copy it from original stock rom and place it to /system folder.
To check the tweak result, find /data/log/kobridge_tweakxx.log files (total 4 files created)
Again, I do not use 'data wipe'. From ICS to JB, everything moved ok and working fine for me.
On the same CWM recovery session, you can flash the ROM, Modem, and bloatware remover script also. But be sure that you need to wait enough time until system reboot and settle. After flashing the ROM, you may need to wait about upto 5 minutes. If you removed alignedapk file and doing the re-zipalign, then it would also take 3-5 minutes.

Kobridge Tweak Pack vJB4.2
From this version, I do not include my Kobridge tweaks into stock rom. So, if you want to add Kobridge Tweaks into this ROM, you need to flash the separate zip file (I want to give you the option that you could use any tweaks from anyone).
**only recommend to use on pure stock JB Kernel**
a. Kobridge Tweak v4.2SF - Mirror
b. Kobridge Tweak v4.2F - Mirror
c. Kobridge Tweak v4.2M - Mirror
d. Kobridge Tweak v4.2A - Mirror
e. Go back to stock default and remove the tweaks installed by Kobridge Tweak pack - download
Kobridge's Silent Camera Mod
Four different flashable zip files available for Camera apk. If you use the CSC tweak, then you will only have one option to turn on or off the shutter sound.
1. Kobridge_Silent_Camera_vFL16.2.zip - download
Features:
No Sounds -Camera shutter, focus, click, Cam start, stop, record
No Charger connection sound
No PowerOn sound
No Shutdown sound
2. Kobridge_Silent_Camera_vFL16.3a.zip - this version is the combination of vFL16.2 and vFL16.3b. - download
Features:
No CSC required
Enabled shutter sound on off option
Most Camera & Camcoder sounds removed in Camera apk itself and system ui folder
power key to take the photo (if power key is press shortly, then it goes to screen off mode. So, press it a little longer. When the picture is taken, device option menu also showed up. Need to click 'back' key to remove the device option menu)
Removed low battery alerts from Camera and Camcoder. Enabled taking pictures and recording in low battery
Able to take pictures or recording during the call
Able to use flash in low battery
All features of vFL16.2
3. Kobridge_Silent_Camera_vFL16.3b.zip - changes were only made in camera apk. - download
Features:
No CSC required
Enabled shutter sound on off option
Most Camera & Camcoder sounds removed in Camera apk itself and system ui folder
power key to take the photo (if power key is press shortly, then it goes to screen off mode. So, press it a little longer. When the picture is taken, device option menu also showed up. Need to click 'back' key to remove the device option menu)
Removed low battery alerts from Camera and Camcoder. Enabled taking pictures and recording in low battery
Able to take pictures or recording during the call
Able to use flash in low battery
4.Want to go back to stock Camera? No problem - click here
If you flash this zip file, it will remove any changes made from above Camera Mods and you will hear every sounds provided by Stock rom.
Old versions:
Note: VFL16.1 is not stable
Kobridge_Silent_Camera_vFL16.1.zip download here - Mirror
Kobridge's System App Backup & Recovery Tool - Advanced users only
Note: to backup and recover, it takes about 5minutes (little more or less). So, please be patient.
System App Backup from CWM recovery - Kobridge's_sysapp_backup_v1.0.zip - download here - Mirror
System App recovery tool - Kobridge's_sysapp_recover_v1.0.zip - download here - Mirror
Kobridge's CSC Tweak - experience the extended menus and options
Note: If you see that some app or function does not work after flashing CSC tweak, try it to flash again just after flashing the ROM.
Kobridge_CSC_Tweak_v1.1.zip - download here - Mirror
To go back to Stock CSC, download Stock CSC flashable zip file - Kobridge_Stock_CSC_FL16.zip - download
Old version:
Kobridge_CSC_Tweak_v1.0.zip - download here - Mirror
Kobridge's SystemUI mod - enabled all 20 stock QuickSetting (togglebar)
Note: MultiWindow and AllShareCast are not displayed because of the phone's configuration.
** SystemUI.apk still stays in /preload partition.
** Few screenshots available at post#306 - here
1. Kobridge_Stock_FullQuickPanelSetting_vFL16.0 - Enabled all Stock Quick Panel (Toggle bar) items - download
2. Kobridge_SystemUI_Mod_vFL16.0 - FullQuickPanelSetting + battery, wifi, Signal bar mod - download
3. Go back to stock SystemUI (into Preload partition) - download
Tdunham's Mods collections for FL16 (deodexed ROM only)
Extended toggles and addons - Click here
All-in-one mod - check here
This mod includes Music Skip Mod, Back to Kill Mod, Ripple Lockscreen, Aosp Toggle, Extended Restart Menu
Call Recorder Mod - check here
Centered Clock Mod - check here
Format all X2 - works for both odexed and deodexed because it's formatting all!
FL16 - 1x/3G Mod - here
Hosts Ad Blocking - here - works on both odexed & deodexed
Settings Addon - here
Power Menu Mod - here
Battery Life in JB ROM - 12/22/12 - this information is subject to change.
So far, what I've found on JB rom is, there are lots of wakup locks comparing with ICS and GB. I think one of the reason why is, I never saw any wifi connection issue on JB rom whenever the screen turned on from deep sleep(?). From the ICS rom, we've seen lots of wifi wakeup failures but I've not seen this from JB.
So for overall, the battery life in JB is worst comparing with ICS or GB. For me, it's less than half of my ICS battery life. I'm still trying to figure out to make the battery life better on JB.
Update 12/23/12
I removed lots of wakeups but
Still not happy with battery life personally. Below three screenshots with 4.2A mode. A little fast battery consumption comparing with in ICS. (I'll test this again after my new battery arrives 1800mA)
Update 01/11/12 - with new battery
Finally got new 1800mA battery and measured battery life during one full charge cycle.
The battery life is much better than before comparing with my old battery.
Battery life shows in screenshots below starting from 4th and it's based on -
FL16 Stock deodexed, fl16 stock kernel/modem, no tweaks but some app level tweaks to reduce the battery consumption. Some of the apps are showed in screenshots and percentages being used.
Update 01/14/12
Finished the second life cycle of new battery. For overall, battery life is great even without the tweaks. I like this ROM!
The screenshots are available at http://forum.xda-developers.com/showthread.php?t=2059714&page=42
What's next? Battery life after applying the Kobridge Tweak Modes.

What's new on FL16?
Toggle bar moves - 'sync' option added into toggle bar (screenshot #2)
Telenav still does not work on FL16 odex version - once after open the app, it goes directly google market and update the app. But it's FC'd. - fixed on current version
vtt-sprint.apk removed from symlink
Connection Optimizer name changed from ConnectionManager.apk to ConnectionManager-wimax.apk
USB Mass Storage connection option is gone from Settings. Nowhere to find it.
Trick - download 'USB mode switch for SGS1 on CM (usb switch). This one always worked for me on any rom whenever I had an issue on mounting USB storage as mass storage. (screenshot #3&4)
Settings > Application manager - 'ON SD CARD' tab added
Internet browser force closing on different DPI (200)
Exchange service - whenever wifi sleep policy is set the 'never' (turn off wifi during the sleep)', it uses most of CPU and makes the phone unable to sleep! When the policy is set to 'always wifi turned on' then, phone sleeps better! Something wrong with connection optimizer. If you do not use exchange email, then freeze this service along with email app

First!
Thank you Kobridge
I hope those tweaks turn out well :fingerscrossed:

looks like your knocking this out. 2nd.
EDIT: looks very nice.

Yipes! Excellent. Watching closely.
Sent from my SPH-D710 using Tapatalk 2

Downloading now, how are wimax speeds looking kobridge? I've only been getting 1.2Mb max on cm9/10 compared to 10+ on stock el26
Edit: Pulled 5.4 up last night, not bad! BTW for anyone wondering about 4g tethering, try the latest beta of the app Wifi Tether for Root Users from their project site (the market version wouldn't connect and every other app dropped to 3g)

It worked.
El26 for wipe and modem and rom and bloat away

What is this I see......Kobridge is at it again :thumbup:
Sent from my SPH-D710 using Tapatalk 2

Strange it shows phone is sleeping while screen is on
Touchwiz home has stopped twice
And everything in my folder disappeared
And is turbo scroll back?

I have a question. How are you managing to deodex the services.odex file??? Everytime I try to deodex this Stock ROM this is the only part that errors out and will not deodex. All the rest of the framework and apk's deodex just fine. The error I get is as follows:
NOW AT FILE 40 OF 44 IN system/framework: services.odex
Disassembling services.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d ../framework -x services.odex
Error while disassembling method Lcom/android/server/enterprise/email/EmailPolicy$EmailBroadcastReceiver;->onReceive(Landroid/content/Context;Landroid/content/IntentV. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: class Landroid/app/enterprise/IEmailPolicy$Stub; cannot be resolved.
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.unresolvedValidationException(ClassPath.java:536)
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.getSuperclass(ClassPath.java:540)
at org.jf.dexlib.Code.Analysis.DeodexUtil.parseAndResolveMethod(DeodexUtil.java:212)
at org.jf.dexlib.Code.Analysis.DeodexUtil.lookupVirtualMethod(DeodexUtil.java:103)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3640)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1106)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
opcode: invoke-virtual-quick
CodeAddress: 8
Method: Lcom/android/server/enterprise/email/EmailPolicy$EmailBroadcastReceiver;->onReceive(Landroid/content/Context;Landroid/content/IntentV
ERROR: Aborting services.odex
I'm clueless. How do i fix this error??? Please note that I am using dsixda's kitchen tools in linux to complete task.

Launcher keeps force closing also. kinda just freezes at times >_>

Couldn't you dial ##diag# to switch the usb mode?
Sent from my SPH-D710 using Tapatalk 2

Is it possible to make a tar of the decodexed rooted file?

Works perfectly! Thanks kobridge!
Sent from my SPH-D710 using Tapatalk 2

Is there a way to remove the tweaks in case we decide to back to stock settings?
Sent from my SPH-D710 using Tapatalk 2

StoverA said:
I have a question. How are you managing to deodex the services.odex file??? Everytime I try to deodex this Stock ROM this is the only part that errors out and will not deodex. All the rest of the framework and apk's deodex just fine. The error I get is as follows:
NOW AT FILE 40 OF 44 IN system/framework: services.odex
Disassembling services.odex ...
java -Xmx512m -jar baksmali.jar -a 15 -d ../framework -x services.odex
Error while disassembling method Lcom/android/server/enterprise/email/EmailPolicy$EmailBroadcastReceiver;->onReceive(Landroid/content/Context;Landroid/content/IntentV. Continuing.
org.jf.dexlib.Code.Analysis.ValidationException: class Landroid/app/enterprise/IEmailPolicy$Stub; cannot be resolved.
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.unresolvedValidationException(ClassPath.java:536)
at org.jf.dexlib.Code.Analysis.ClassPath$UnresolvedClassDef.getSuperclass(ClassPath.java:540)
at org.jf.dexlib.Code.Analysis.DeodexUtil.parseAndResolveMethod(DeodexUtil.java:212)
at org.jf.dexlib.Code.Analysis.DeodexUtil.lookupVirtualMethod(DeodexUtil.java:103)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInvokeVirtualQuick(MethodAnalyzer.java:3640)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyzeInstruction(MethodAnalyzer.java:1106)
at org.jf.dexlib.Code.Analysis.MethodAnalyzer.analyze(MethodAnalyzer.java:213)
at org.jf.baksmali.Adaptors.MethodDefinition.addAnalyzedInstructionMethodItems(MethodDefinition.java:389)
at org.jf.baksmali.Adaptors.MethodDefinition.getMethodItems(MethodDefinition.java:311)
at org.jf.baksmali.Adaptors.MethodDefinition.writeTo(MethodDefinition.java:132)
at org.jf.baksmali.Adaptors.ClassDefinition.writeMethods(ClassDefinition.java:338)
at org.jf.baksmali.Adaptors.ClassDefinition.writeVirtualMethods(ClassDefinition.java:310)
at org.jf.baksmali.Adaptors.ClassDefinition.writeTo(ClassDefinition.java:117)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:186)
at org.jf.baksmali.main.main(main.java:308)
opcode: invoke-virtual-quick
CodeAddress: 8
Method: Lcom/android/server/enterprise/email/EmailPolicy$EmailBroadcastReceiver;->onReceive(Landroid/content/Context;Landroid/content/IntentV
ERROR: Aborting services.odex
I'm clueless. How do i fix this error??? Please note that I am using dsixda's kitchen tools in linux to complete task.
Click to expand...
Click to collapse
+1 I can't deodex it to save my life!
Sent from my SPH-D710 using xda premium

Usb connect works fine without tweaks
Sent from my SPH-D710 using Tapatalk 2

fredrick1213 said:
Is there a way to remove the tweaks in case we decide to back to stock settings?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The tweak is not included in this ROM. To apply the tweak, you need to manually flash the tweak zip file.
Stryke_the_Orc said:
+1 I can't deodex it to save my life!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I'm a novice about deodexing. But what I can tell you is you need to add bootclass path on it.

Related

PLEASE NOTE: If you are using a Canadian handset, I recommend switching over to my JL2 based ROM. It's the same speed (if not quicker), and I will be providing much more updates for it. The ROM can be found here: http://forum.xda-developers.com/showthread.php?t=906977
News
12/23/10 - v0.2 released! Includes an error-checking script to prevent possible errors from occuring, new Steam recovery, wipe and non-wipe versions and more! Check the changelog for more info.
12/22/10 - v0.1, initial beta release
Hey everyone,
This is a rom which aims to provide the absolute best user experience by being extremely quick without sacrificing any necessary features. The majority of Samsung bloatware is removed, however a good portion of the pre-installed apps are left untouched. This ROM is based on XXJPY (Froyo 2.2.1).
If you have any questions prior, while, or after installing this ROM, please read the first few posts, as I'll try to address every possible (major) problem which can occur. If, after reading the posts, you are still encountering a problem, please reply to this thread being as detailed as possible. This allows me to fix problems quickly and easily.
Now, this is my first ROM, so there are bound to be a handful of bugs. However, I've been using this ROM for a few days and have yet to encounter any major problems.
Note: Please don't complain about Quadrant, Linpack, or any other pointless benchmark scores. If you've used the ROM and it's sluggish, by all means tell me, but don't base your opinion of the speed merely on a benchmark.
Okay, so what now?
1. Download and Install Instructions
2. Changelog, To-Do
3. FAQ and Problems
4. Screenshots, Media, User Comments
Features
Based on XXJPY (Froyo 2.2.1)
Patched Speedmod kernel, version K12 hz=256(allows you to mount on computer without problems)
Steam multi-touch recovery: update.zip on SD card
Added an error-checking script which prevents errors when installing [thanks Darkyy!]
All-black Gingerbread theme (saves battery)
Fully deodexed
Fully zipaligned
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox
All protected apps in market - modified build.prop
Big APN list, which allows instant internet + MMS access
Integrated ClockworkMod Recovery
Stock AOSP Lockscreen
Bell UGJK3 Modem
Backlight Notifications
Added Applications:
Nexus S Live Wallpapers
Swype v 2.15 (Newest)
Launcher Pro
Optional: Gingerbread Keyboard (install from SD Card)
Removed Applications:
AllShare
Diary
Aldiko Reader
Press Reader
Layar
Thinkdroid
Write and Go
Credits (in no particular order)
-Hardcore for the kernel
-santiemanuel for the Nexus S Live Wallpapers
-vukandric for the theme
-Darkyy for help on the update script, and for generally being awesome

Download and Install Instructions
Downloads
Latest and Greatest
-v0.2: seeARMS XXJPY (12/23/10)
Wipe: http://www.multiupload.com/L9SUOBKO88
No Wipe: http://www.multiupload.com/9F5E89AYTP
-v0.1: seeARMS XXJPY (12/22/10)
http://multiupload.com/G6XTJF07MO
Modems
To flash these modems, use Odin and select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
JL2: http://www.multiupload.com/TC1ME8VB20
JK4: http://www.multiupload.com/3HOKWMBHO2
Installation Instructions
Before installing, disable any lagfixes (which can typically be done by booting into recovery mode and selecting "Disable Lagfix").
Also, if you wish, backup everything! Perform a NANDROID backup in recovery, backup your music, files, etc. In case something goes wrong (it will eventually), you'll have peace of mind.
Please note: this rom will wipe all your data. It will not, however, format your internal or external SD cards. This means you'll lose apps and settings, but not music, movies, etc.
Lastly, I recommend performing a factory reset before installing any new rom.
If you're running a previous version of my ROM, feel free to install the non-wiping version. However, if you're switching roms, I recommend running the standard version, which will erase all data.
1. Download and copy this file to your internal memory card.
2. Boot into recovery, and select "Install zip from sdcard".
3. Select "Choose zip from sdcard", and scroll to the ROM.
4. Select OK, and wait for the file to flash.
5. Reboot. This reboot will take a while (upwards of 2-5 minutes), so be patient and don't shut off your phone!
Congratulations, you've successfully flashed!
After it boots, I'd recommend doing a few things in order to allow your phone to be as quick as possible:
1. Boot back into recovery, select "Advanced SpeedMod ULK Features". Choose "LAGFIX options", then "Faster: EXT4 ALL". This applies a lagfix, and converts the partitions into the faster EXT4 filesystem.
2. In recovery, go back to the Advanced SpeedMod ULK Features menu. Choose "TWEAK options", and enable every tweak. For more information about these tweaks, see HERE.
Also, window animations are disabled by default. You can enable them by going into settings -> Display, and selecting Animations.
3. If you'd like the Gingerbread Keyboard, open up the My Files application and navigate to the directory "Gingerbread_Keyboard". Open up the .APK file and install as usual.

Changelog And To-Do
Changelog
v0.2
-Google Voice Search updated
-Added option to install gingerbread keyboard
-Updated kernel version to K12
-Added error checking script - with help from Darkyys rom (This prevents possible errors when installing)
-added nowipe and wipe versions
-Modified build.prop to allow all protected market apps
-Added Steam recovery - check FAQ for info on how to access it
v0.1 - Initial beta release
To-Do
-Gingerbread Keyboard
-Extended Power menu
-Support for different themes
-Stock application pack (available for flashing through CWM)
-Better modem (JL2? JK4?)
-Faster browser
-Modded SMS Application
-Modded Camera Application
If there's anything else you'd like to see in this ROM, just ask.

FAQ And Problems
FAQ
I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
No worries. Follow these steps:
1. Download Odin from here.
2. Download the Speedmod kernel for whichever Android version you're running. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
7. Now you're required to download the patch for the Speedmod kernel, which will allow you to copy the ROM over to your internal SD card. If you don't install this patch, the internal SD card will be detected as a CD drive, and will be read-only. The patch is able to be downloaded from HERE. Simply copy this patch to your SD card, boot into CWM, and flash it using "install zip from sdcard". After doing this, follow the normal steps to install this rom!
I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
Simply perform a factory reset. Clear the cache + Dalvik cache in recovery as well, if you'd like.
What's this steam recovery and how do I access it?
Click to expand...
Click to collapse
Steam recovery is a new, semi-functional multi-touch recovery created by sztupy. This recovery has all the features the standard CWM one has and more. Check his thread for more info.
Please note: Because (currently) the only Steam-compatible kernel is based on a much older base version (ie: not XXJPY), a small amount of features are incompatible, such as lagfix options, kernel options, etc. However, the majority of features (such as mounting, wiping, etc) are working just fine. I'm working on getting everything working; as soon as it is, it will fully replace CWM on this ROM.
To enable it, just boot into CWM and go to "Apply sdcard: update.zip". After doing this, it will boot into the new Steam recovery. You must do this every time you want to access it.
My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.

Screenshots, Media, User Comments
Screenshots
Click for a larger image.
User Comments
°Dexter° said:
Impressive rom seeArms, really really fast...faster than others, indeed.
...
Very good work,no major issues by now,i'm eagerly waiting for next release
Click to expand...
Click to collapse
Existence. said:
it's runnin great, thanks seeARMS. can't wait for the JL2 version. i really dont wnt to brick my phone and i think the JL2 version fixes the SD dying problem so i cant wait!
Click to expand...
Click to collapse

hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?

gonna try this ROM out!

Quadrant score? I will try it, looks good.

gonna try this release soon, good job

fenerbuuh said:
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
Click to expand...
Click to collapse
I'm using this modem because I need the Canadian band, because, well, I'm located in Canada. And, according to this guide, this modem is very good on battery life and reception.
In later versions of this ROM I'll most likely include a different modem (or a flashable modem). Something like that.
Any modem you'd prefer to see included?

Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...

Hey man, to bad i flashed Docs jpy rom just yesterday evening, and dont want to change rom on a daily base. But ill test it for sure just because id not have to change kernel afterwards...
so thanx for your work and keep it coming man...

Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.

seeARMS said:
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
Click to expand...
Click to collapse
I'm looking forward to this,man!Thank's

Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
No way man, but you could get hardcores kernel as an odin package, it comes with cwm recovery, flash that first and then use cwm to install this rom.

Mparmpa-Nikos said:
I'm looking forward to this,man!Thank's
Click to expand...
Click to collapse
Done. See the FAQ.

Welcome new devinteresting rom,gonna try it...
Thank you

Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.

Sounds good
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!

Darkyy said:
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Click to expand...
Click to collapse
Will do Darky, thanks.
canad1an said:
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Click to expand...
Click to collapse
Market comes updated to version 2.2.7 already. I haven't had any problems with it at all.

i decided to compile things for newbies like me so we stop makin a foll of ourselves asking around etc...
i will be compiling links tocustoms roms and things that i think and others think maybe of great significant to our devices
first is the FAQ guide,,
this contains rooting and other cool stuff
(i may include links outside xda if needed)
http://forum.xda-developers.com/showthread.php?t=1512749
http://forum.xda-developers.com/showthread.php?t=1325453
rooting tip:
since basically rooting will or might void warranty right,so ill share what i did to a friends phone...
basically just created a nandroid back up of his current rom using skins recovery..
then installed a new custom rom(rooted rom)
voila...2 bird 1 stone,,,custom rom and root at the same time...
and in case you want the old one back just restore to back up..
not sure if this method counts the bin....
here is for the list of updating to official and unofficial stock roms
http://androidadvices.com/update-samsung-galaxy-s5360-xxkk6-gingerbread-235-firmware/
http://forum.xda-developers.com/showthread.php?t=1325453
http://forum.xda-developers.com/showthread.php?t=1465800
CUSTOM ROMS
Creeds
http://forum.xda-developers.com/showthread.php?t=1453286
Repencis
http://forum.xda-developers.com/showthread.php?t=1516037
MySS
http://forum.xda-developers.com/showthread.php?t=1518439
Hybrid
http://forum.xda-developers.com/showthread.php?t=1465405
Blazing Hatred
http://forum.xda-developers.com/showthread.php?t=1508053
Sense Aurora
http://forum.xda-developers.com/showthread.php?t=1506927
Terma Rom
http://forum.xda-developers.com/showthread.php?t=1520167
Infected
http://forum.xda-developers.com/showthread.php?t=1446677
Emerald
http://forum.xda-developers.com/showthread.php?t=1492418
Aurora V2
http://forum.xda-developers.com/showthread.php?t=1538616
Chobits
http://forum.xda-developers.com/showthread.php?t=1573306
Bazzrom
http://forum.xda-developers.com/showthread.php?t=1557740
CM7
http://forum.xda-developers.com/showthread.php?t=1583959
Tweaks
ram and battery life tweaks by [email protected]
http://forum.xda-developers.com/showthread.php?t=1491714
Beats
http://forum.xda-developers.com/showthread.php?t=1526643
Guide to A2sd
http://forum.xda-developers.com/showthread.php?t=1524940
Build prop
http://forum.xda-developers.com/showthread.php?t=1533688
(note build prop edits here are from other device pick the thing that you feel will be applicable)
http://forum.xda-developers.com/showthread.php?t=771232
http://forum.xda-developers.com/showthread.php?t=1533688
Sd Card Partitioning
http://forum.xda-developers.com/wiki/SD_card_partitioning
make your back keys vibrate
http://forum.xda-developers.com/showthread.php?t=1463510
Recoveries
Skins
http://forum.xda-developers.com/showthread.php?t=1446796
Madteam
http://forum.xda-developers.com/showthread.php?t=1467492
Fix Earphone Issues if you have any
http://forum.xda-developers.com/showthread.php?t=1469034
sgy manual
http://forum.xda-developers.com/showpost.php?p=22372536&postcount=1
ROM SURVEY and Discussion
http://forum.xda-developers.com/showthread.php?t=1511345
From MAI77
some few custom ROMs change MAC addr of wifi, thereby keeping them from reregistering immediately in WLAN if "access point" limits via MAC#
From Ronnieryan
ronnieryan said:
here's the drivers
http://depositfiles.com/files/3raqcskp2?subid=141468
anyways if you want smart keyboard, just PM
Click to expand...
Click to collapse
ALSO Adding the Elusive CREEDS ROM LINK NOT THE NANDROID one,,the original one please refer to creeds for the installation procedures
maybe uploaded files that u downloaded are broken..i will upload now the creeds ROM i downloaded b4
http://www.mediafire.com/?wc2xxkg83wa8bvu,5fgy69r5yw7hpnu,swtzbbod5nsnq7q,yzzjcy3hdgzkow0
the files are aranged from 1-4, proper install
for AOSP and 2.1
http://www.mediafire.com/?eecmc4fu8abgy12,g8y4cee45utp190
thanks to ronnieryan
KERNELS!!!!Finally!
Press Thanks For Maroc-OS & Rate 5 Stars
Files Needed :
Odin3 1.84 : http://www.mediafire.com/?y7v62dq119suj8r
Odin 1.85 : http://www.mediafire.com/?zgqfh954k9flr47
Versions:
Test Kernel :http://www.mediafire.com/?0j6guwgg60opj7y
Alpha v0.1 :http://www.mediafire.com/?1rsf19z8qgl1qu6
Alpha v0.4 : DELETED
Alpha v0.5.1 DELETED
Alpha v0.5.2 http://www.mediafire.com/?4p6sfran2si6f3j
Alpha v.0.5.7 http://www.mediafire.com/?fzndkvldkhais0g
V0.6 RC 80 http://www.mediafire.com/?xdkh1n2owok72cx
V0.7 RC 10 http://www.mediafire.com/?1vx122767j43z4f
INSTRUCTIONS :
Short Flashing Guide
- download the .tar file
- install Kies, or Samsung driver pack
- download Odin3 1.84 or 1.85 (download links above)
- stop Kies
- stop all active ADB sessions
- start odin
- power off Your SGY
- boot into download mode
- Press Vol Down, Home, and Power at the same time
- When (about 5 sec) Warning screen appears, release Volume Down and Power, then (a bit later) Home
- press Vol Up (You'll get Odin mode screen)
- in the PDA field, browse for the kernel tar
- leave all other fields and checkboxes default!
- connect your phone, You must see yellow 0:[COMxx] in the first ID:COM and "Added" in the message box
- Start flashing by the START button.
- flashing will start immediately, see the progress in the message box, and progress bar on the phone
- Wait 1-3 minutes, until green PASS! in the upper left
- SGY will reboot, leave it as is for 2-5 minutes until startup finishes
OR
Flash Kernel Without Increasing Custom Bin Count
Special Thanks to FAQBLY For This Wonderful zip
faqbly has compiled a script that can flash boot.img from CWM Recovery and it will not increase Custom Bin Count.
Benefits
You can Install Custom Kernel without increasing your Custom Bin Count.
Below is the ZIP file from faqbly
http://www.mediafire.com/?26928er6dqmucrm
Instructions:
In the .zip file provided by faqbly, you have to replace the boot.img with the boot.img from the tar file of a kernel
Example would be to download kernel from Maroc-OS
You Will Have A .tar file that contains the boot.img
Extract boot.img from tar, and place it to the zip by faqbly
And flash via CWM Recovery
Apps Needed
A2SD : http://www.mediafire.com/?86t3oztvoyb0dul
Droidwall : http://www.mediafire.com/?mcxb6y8qg26mfg3
No-Frills CPU:http://www.mediafire.com/?ow3r7zl96chd9kp
If Ever Problem Occurs, Just Flash Back To These Kernels
Stock http://www.mediafire.com/?dzfcrhb8fj3s40x
Terma Kernel http://www.mediafire.com/?81d1acx1c19m9k5
Test Kernel http://www.mediafire.com/?0j6guwgg60opj7y
Originally Posted by mai77 View Post
this reports aims to stay concise & readable and maintains hyperlinks to posts in this large thread, that contain specific info, especially the source code to solve a problem or add a feature. If you come across another code snippet from the Android world, that could improve SGY OS: post it in this thread ! kernel testers can switch between kernels without changing the rest of the system, here is a drop-in-replacement stock kernel to exchange for our custom kernel, flash as PDA with ODIN.
Kernel wish list / feature list
unreported __ EXT2/EXT3 & EXT4 support. (just kernel support, still need scripts to convert blocks)
unreported __ System/Cache & /Data mounted as EXT4 R/W. (needs fixes)
unreported __ Added /Data mount, IO Scheduler and CPU Governor Feature (Conservative, Ondemand, Powersave & Userspace governors are enabled)
Neg report __ NETFILTER Compatibility with DROIDWALL /// report on 0.6 -80, 0.7
unreported __ INIT.D Support
unreported __ Root Support (su). (currently DELETED)
Neg report __ "adb root" support , default.prop file /// report on 0.6 -80, 0.7
unreported __ Overclock / Undervolt support : at 1GHz, but needs some fixes
unreported __ Best ZYGOTE Service for Detailed CATALOG
unreported __ recovery in Read/Write mode
unreported __ some improvements & fixes, bmlunlock
here is the thread
http://forum.xda-developers.com/showthread.php?t=1550065
HOW TO FLASH KERNEL GUIDE THE EASIEST WAY
Requierements:
boot img file (2 the kernel your flashing and termagrancis kernel)
mai77 flasher thingy
and cwm of mads or skins...
procedure:
download the kernel respectively,both kernels are on tar file do you need to extract them using any extarctor (for me i used androzip form market)or tyu can use es file manager...
extract them on sdcard one file at a time and rename them
example kernel 1
after extrract rename boot.img to boot.imgx
do the same thing on the other kernel,but rename differently...
now,,,decide which kernel to flash..
example
i renamed
boot.imgx(marcos kernel)
boot.imgz(terma kernel)
i will flash
terma kernel
rename or remove the other letter
the kernel you wnat to flash should have the boot.img name,.
now go to recovery..
install via zip
choose sd card update
choose SGYbiCWM.zip
and apply reboot,,,
youre done,.,,!
check under settings kernel...
this was the method ive opersonally used
http://forum.xda-developers.com/showthread.php?p=23803175#post23803175
LOST PHONE>>
http://forum.xda-developers.com/showthread.php?t=1572006
BATTERY CALIBRATION!
AUTION: DO THIS PROCEDURE ONLY ONCE OR TWICE, FULLY DRAINED BATTERY CAN CAUSE CRYSTALLIZATION WHICH SHORTENS BATTERY LIFE.
HAVE CWM INSTALLED INCASE YOUR STOCK RECOVERY HAS NO ADVANCED OPTION.
1. Fully drain your battery, play some games, music, etc.. NO PORN!!
2. Let your battery cool for atleast 2 minutes
3. Restart phone to remove residual charge( it will boot only halfway)
4. After the phone shuts down remove battery and let it cool for atleast 2 minutes.
5. Re insert battery and charge your phone in OFF mode.
6. After the phone reaches 100% charge boot into recovery (Power+Home+Volume_up button)
7. Go to advance (I think some android has this in recovery, if not go to CWM and you will find it there).
8. Wipe battery stats.
9. Press Power/Back and Reboot your phone
10. Wait till the phone reaches 100% charge and disconnect charger
11. Have a happy life.
Before my phone has a battery life of less than a day (about 20 hours) with battery saver, task killer and minimal settings. After calibration my phone without task killer and battery saver installed lasts short of 3 days with moderate settings. I use only a Ram cleaner and V6 fast engine flush now. "Cleaner" apps are good, "Killer" are not..
THIS IS A BATTERY CALIBRATION PROCEDURE NOT A BATTERY LIFE EXTENDER(THERE IS NO SUCH THING), JUST SAYING SO THERE IS NO CONFUSION.
taken from
http://www.symbianize.com/showpost.php?p=10845667&postcount=14
Arrow Creed's 2.0 (ICS inspired) installation guide
As per request here is the original thread for files and photos
http://forum.xda-developers.com/showpost.php?p=22219562&postcount=97
This is a Creed's 2.0 installation guide. Only for Samsung Galaxy Y (GT-S5360)
Make sure you are on 2.3.6 Gingerbread
Before we start, make a cwm back up of your current rom
How to back up:
1. Place "skin1980cwm zip" to the sd card (needed files are attached below)
2. Go to recovery mode (press volume up + power button + home button all at the same time)
3. Use the volume up and down key as your scroll key and choose "appy update from sdcard"
4. Choose "skin1980cwm.zip" (use the home button to select)
5. You will be in a new interface (yellow fonts)
6. Go to "restore and back up"
7. Select "back up"
8. Wait until back up completes then reboot
note: If something goes wrong, just "restore" your back up using cwm
Creed's 2.0 (with 14 toggles and swipe to remove notifications)
Features:
*Soft Root- SU
*Pre Deodexed
*ZipAligned
*Maps With WorldWide Navigation
*Bloatware Removed
*BusyBox Support
Message App:
*No Auto Sms To Mms Conversion
*No Receipient Limit
*Built In 5 Theme
Touchwiz App(Samsung Home) :
*Transparency Level Increased
*Alphabetical Auto Arrange
*Landscape Orientation Introduced
*Auto Brightness Option in Display
*Boot Animation Enabled
*Custom Boot Animation Added
*Custom Power On Sound
*Reduces Startup Time ~Less Than 13 seconds
14 Status Bar Toggles
*All 5 From Samsung(Wifi,B/T,Soung,GPS,Orientation)
*Data
*Lockscreen-Off
*FlashLight
*Shut Down Options (Reboot,Recovery & Download mode)
*Airplane Mode
*Brightness
*Auto Synchronise
*Screen Timeout
Default wallpaper
Things (files) you will be needing:
(1) update.zip (if you are not yet rooted to by-pass system commands)
(2) Skin1980cwm.zip
(3) creed's 2.0 zip
download from here
Creed's Rom 2.0
(4) boot animation fix zip
(5) 14 toggles zip
How to root: (required)
1. Place the "update.zip" in your sd card
2. Go to recovery mode (press volume up + power button + home button all at the same time)
3. Select "apply update from sdcard"
4. Find the "update.zip" and select it (using the home button)
5. wait to finish then restart phone
Creed's installation instructions:
1. Place all the (4) needed files in your sd card
2. Go to recovery mode (press volume up + power button + home button all at the same time)
3. Use the volume up and down key as your scroll key and "wipe data and "wipe cache"
4. After wiping, choose "apply update from sd card"
5. Choose "skin1980cwm.zip"
6. You will be in a new interface (yellow fonts) then select "install zip from sd"
7. Find "Creed's 2.0 zip" and select
8. Wait for installation to compete (3-5mins)
9. Restart phone
note:
After installing Creed's rom 2.0 install the "boot animation fix zip" first
then the "14 toggles zip" using the same method as above (except for #3)
"Swipe to remove" notifications instructions:
note: extract the "swipe to remove" rar file (contains two files)
1. Download "root explorer"
2. Open "root explorer" and go to your sdcard
3. Set the permission from r/o to r/w
4. Copy the "framework.jar"
5. Paste it to the system/framework folder
6. Set permissions to rw-r-r
repeat the procedure with the "systemUI.apk" (place it on system/app folder)
note: you will encounter a lot of force close (normal) but just go on
7. Press the power button and restart the phone
"DroidX" boot animation (alternative)
1. Open "root explorer" and go to your sdcard
3. Set the permission from r/o to r/w
4. Copy the "bootanimation.zip"
5. Paste it to the system/media folder
6. Set permissions to rw-r-r
7. Restart the phone
Fonts (alternative)
Roboto
Sweet Confusion
Ubuntu R
Comicbook Commando
Chocococky
More fonts here
1. Place on sdcard
2. Click and install
3. Go to "Display"
4. Go to "screen display"
5. Go to "font style"
6. Choose the font that you like
TweakZV6 Performance Scripts
note: make a cwm back up (for emergency)
1. Place "TweakV6.zip" on sd card
2. Go to recovery mode (press volume up + power button + home button all at the same time)
3. Use the volume up and down key as your scroll key and choose "appy update from sdcard"
4. Choose "skin1980cwm.zip"
5. You will be in a new interface (yellow fonts)
6. Find "TweakV6.zip" and select
8. Wait for installation to compete
9. Restart phone
Credits to:
pratyush.creed (creed's rom 2.0)
budyisdead (swipe to remove notification)
evanlocked (DroidX boot animation)
krishna_nirvana (update zip)
Skin1980 (skin1980cwm zip)
[email protected] (tweakzV6 zip)
SethDeCode'z (fonts)
feel free to add..
i will add if i find or deem anything useful..

<post deleted>

thanks I'll merge it asap

Add that there isn't a CM/MIUI port for SGY yet while you're at it Anant.
Although my hopes that newbies will go there before making a new thread is almost nil. *-*

silvane
well i am guessing that aswell....but will still try for our references an index And help page is what i am aiming will complete in 2 days....
Sent from my GT-S5360 using Tapatalk

Thread moved to general and stuck!

great thread!
very useful!

nice thread good work

galaxy y
plz tell me how to increase or make use of sdcard as internal memory for my samsung galaxy y and i currently rooted my phone and i have gingerbresd 2.3.6. Which customrom is suitable with better features

u can use custom rom like,creeds v2.0,repencis v2.0 or hybrid 2.0,these rom r good and less bugs.. use link2sd or a2sd.. in link 2 sd u need to partition ur sdcard to make it work..

some few custom ROMs change MAC addr of wifi, thereby keeping them from reregistering immediately in WLAN if "access point" limits via MAC#
pls put in guideline

nice writeup

mai77 said:
some few custom ROMs change MAC addr of wifi, thereby keeping them from reregistering immediately in WLAN if "access point" limits via MAC#
pls put in guideline
Click to expand...
Click to collapse
Added on first page
Sent from my GT-S5360 using Tapatalk

Hey mai would be glad if you added my thread in tweaks
link
**Thanks for adding i thanked ya **

[email protected] said:
Hey mai would be glad if you added my thread in tweaks
link
Click to expand...
Click to collapse
Will add after a day or two mate
Sent from my GT-S5360 using Tapatalk

Nice Thread

i had rooted my phone through CWM , does my custom bin counter increased??

aman.droid said:
i had rooted my phone through CWM , does my custom bin counter increased??
Click to expand...
Click to collapse
no...bin counter if you flash updates using odin

thumbs up for this!!
very useful guide for newbies!!

Thanks for the useful info.

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

Note: This ROM is a Modified Stock ROM 4.2.1 with a few apps added and other features. Check below.
Based on Build : XOLO_Q1000_S101_130607
Friends, this CWM flashable ROM provides stock experience only with certain useful features and tweaks, no major UI changes have been done. It maybe useful for those who’ll are having problems rooting.
Stock kernel has been used.
Download link:
XOLO Q1000_mj
Features:
- Rooted( SuperSU is used)
- Deodexed.
- Busybox added.
- Init.d support(Some tweaks added )
- Few Build.prop tweaks.
- Custom bootanimation enabled ( You can add your ‘bootanimation.zip’ to ‘data/local’ folder)
- Bash shell support.
- Ubuntu fonts used.
- Percentage Battery icon.
- Beats Audio added.
- Your external Micro-sd card will be detected as ‘Phone Storage’( This solves the problem for certain games.)
Apps Added:
- Walkman Music Player and Volume+ equalizer app(Full Credits: @mahfoozceecy)Thank You very much!
- Holo Launcher.
- ReScan SD
- QuickPic
- Mobo Player
- LG Camera and others.
Flash it at your own risk
IMPORTANT PLEASE NOTE:
In order to avoid bootlooping issues, before flashing out the zip file, perform these steps:
(1) Remove the boot.img and meta-inf folder from that zip file..
(2) Then download this new meta-inf folder link-------------->https://drive.google.com/file/d/0B7kpQGwEs84ed0tKV1hZaC1wNmc/edit?usp=sharing
(3) Extract the meta-inf.zip. Put this new meta-inf folder inside the XOLO Q1000_mj ROM zip file .
(4) Follow instructions written below for clearing out your phone.
Now simply flash the ROM!
Extremely Sorry for inconvenience!
INSTRUCTIONS:
(1) Backup anything you want and go to CWM Recovery. This ROM will wipe your data.
(2) Wipe out everything:
- Factory reset
- Mounts and Storage/Format system.
- Again go to Advanced/Wipe Dalvik cache,battery stats.
This will make your phone into clean state.
(3) Install Zip from sdcard/choose zip file and reboot.
Credits:-
Thank these people if you want :
@mahfoozceecy
Android kitchen
UOT Kitchen

How You get 20Gb free ? in phone storage ?

External sd card is detected as phone storage and vice versa

Then Its Super Coool ..
Can You Mode Miui v5 Rom for this Future ?

Miui ROM v5 has already been uploaded for xolo q1000 and it works as well.

m_jani said:
Miui ROM v5 has already been uploaded for xolo q1000 and it works as well.
Click to expand...
Click to collapse
No bro i m saying can you add this future Your external Micro-sd card will be detected as ‘Phone Storage’( This solves the problem for certain games.)
In miui v 5.

Change the mount lines.
Change the values in(highlighted in yellow):
dev_mount sdcard--------------Change the sdcard0 to sdcard1 & '1' to '0'
dev_mount left_sdcard---------Change the sdcard1 to sdcard2 & '2' to '1'
Image link

m_jani said:
Change the values in(highlighted in yellow):
dev_mount sdcard--------------Change the sdcard0 to sdcard1 & '1' to '0'
dev_mount left_sdcard---------Change the sdcard1 to sdcard2 & '2' to '1'
Image link
Click to expand...
Click to collapse
I have to edit from pc then replace via root explorer and restart ?

Go to system/etc folder using some file manager with root explorer enabled.....and change the values as i have explained in the previous post

m_jani said:
Go to system/etc folder using some file manager with root explorer enabled.....and change the values as i have explained in the previous post
Click to expand...
Click to collapse
Thanks For fast and good reply
Thanks Hited
I have DOne Successfully But i m not able to install Apps in Phone storage (memory card)

greenlight093 said:
Thanks For fast and good reply
Thanks Hited
I have DOne Successfully But i m not able to install Apps in Phone storage (memory card)
Click to expand...
Click to collapse
Go to Settings/Storage....................select your 'default write disk' option and try.

m_jani said:
Go to Settings/Storage....................select your 'default write disk' option and try.
Click to expand...
Click to collapse
This option not available in miui v 5

It might be somewhere in settings idk exactly....m nt using miui rite now......ask miui porter maybe he can help

m_jani said:
Note: This ROM is a Modified Stock ROM 4.2.1 with a few apps added and other features. Check below.
Based on Build : XOLO_Q1000_S101_130607
Friends, this CWM flashable ROM provides stock experience only with certain useful features and tweaks, no major UI changes have been done. It maybe useful for those who’ll are having problems rooting.
Stock kernel has been used.
Download link:
XOLO Q1000_mj
(Note: Click on 'File' on top-left of the webpage and click 'Download')
Features:
- Rooted( SuperSU is used)
- Deodexed.
- Busybox added.
- Init.d support(Some tweaks added )
- Few Build.prop tweaks.
- Custom bootanimation enabled ( You can add your ‘bootanimation.zip’ to ‘data/local’ folder)
- Bash shell support.
- Ubuntu fonts used.
- Percentage Battery icon.
- Beats Audio added.
- Your external Micro-sd card will be detected as ‘Phone Storage’( This solves the problem for certain games.)
Apps Added:
- Walkman Music Player and Volume+ equalizer app(Full Credits: @mahfoozceecy)Thank You very much!
- Holo Launcher.
- ReScan SD
- QuickPic
- Mobo Player
- LG Camera and others.
Flash it at your own risk
For those who are having problems related to boot issue, please make sure you have proper CWM Recovery installed. For that you can use SP Flash Tool:
SP Flash Tool folder, boot.img ,scatter file, recovery.img.
Steps:
- Make sure you have all drivers installed i.e. MTK6589 Drivers x86-DroidDict(link) and VCOM drivers(link) installed. Click on 'File' on top-left of the webpage and click 'Download'.
- Click on Flash_tool
- Click on Scatter-loading and select the file 'MT6589_Android_scatter_emmc'
- You will see 'BOOTIMG' & 'RECOVERY' has been selected. Make sure its the one present in the same folder where the 'scatter' file has been placed.
- Switch OFF your phone completely,remove the battery and re-insert it.
- Connect your XOLO Q1000 to the computer.
- Click on 'Download' button and you will see your phone being detected and the flash process will start.
- You will be confirmed when its done with the Green circle.
- Now, keep Volume up+Power button on your phone pressed nad in a few seconds you will get your CWM Recovery screen. Then flash this ROM.
INSTRUCTIONS:
(1) Backup anything you want and go to CWM Recovery. This ROM will wipe your data.
(2) Wipe out everything:
- Factory reset
- Mounts and Storage/Format system.
- Again go to Advanced/Wipe Dalvik cache,battery stats.
This will make your phone into clean state.
(3) Install Zip from sdcard/choose zip file and reboot.
Credits:-
Thank these people if you want :
@mahfoozceecy
Android kitchen
UOT Kitchen
Click to expand...
Click to collapse
Not Working...After flashing this ROM , bootlooping starts!! Can you post the original stock ROM without any tweaks that can be flashed through the CWM directly not by sp flash tool?

See you will have to flash boot.img and recovery.img from this thread.....using spflash tools scatter file method......only these three files you will hve to flash..... then install the rom zip.....m sure it will work 100%....do reply if any probs

arkaredevil said:
Not Working...After flashing this ROM , bootlooping starts!! Can you post the original stock ROM without any tweaks that can be flashed through the CWM directly not by sp flash tool?
Click to expand...
Click to collapse
Ok, just confirm if you need the stock rom cwm flashable zip?

m_jani said:
Ok, just confirm if you need the stock rom cwm flashable zip?
Click to expand...
Click to collapse
No thnks..problem solved:victory:..u can try MIUI ROM..it's awesome!!

arkaredevil said:
No thnks..problem solved:victory:..u can try MIUI ROM..it's awesome!!
Click to expand...
Click to collapse
Great you must be happy.......I have tried the MIUI ROM by @Javajohn and it worked great. However, am not a fan of MIUI so reverted back to stock based rom!

m_jani said:
Note: This ROM is a Modified Stock ROM 4.2.1 with a few apps added and other features. Check below.
Based on Build : XOLO_Q1000_S101_130607
Friends, this CWM flashable ROM provides stock experience only with certain useful features and tweaks, no major UI changes have been done. It maybe useful for those who’ll are having problems rooting.
Stock kernel has been used.
Download link:
XOLO Q1000_mj
(Note: Click on 'File' on top-left of the webpage and click 'Download')
Features:
- Rooted( SuperSU is used)
- Deodexed.
- Busybox added.
- Init.d support(Some tweaks added )
- Few Build.prop tweaks.
- Custom bootanimation enabled ( You can add your ‘bootanimation.zip’ to ‘data/local’ folder)
- Bash shell support.
- Ubuntu fonts used.
- Percentage Battery icon.
- Beats Audio added.
- Your external Micro-sd card will be detected as ‘Phone Storage’( This solves the problem for certain games.)
Apps Added:
- Walkman Music Player and Volume+ equalizer app(Full Credits: @mahfoozceecy)Thank You very much!
- Holo Launcher.
- ReScan SD
- QuickPic
- Mobo Player
- LG Camera and others.
Flash it at your own risk
For those who are having problems related to boot issue, please make sure you have proper CWM Recovery installed. For that you can use SP Flash Tool:
SP Flash Tool folder, boot.img ,scatter file, recovery.img.
Steps:
- Make sure you have all drivers installed i.e. MTK6589 Drivers x86-DroidDict(link) and VCOM drivers(link) installed. Click on 'File' on top-left of the webpage and click 'Download'.
- Click on Flash_tool
- Click on Scatter-loading and select the file 'MT6589_Android_scatter_emmc'
- You will see 'BOOTIMG' & 'RECOVERY' has been selected. Make sure its the one present in the same folder where the 'scatter' file has been placed.
- Switch OFF your phone completely,remove the battery and re-insert it.
- Connect your XOLO Q1000 to the computer.
- Click on 'Download' button and you will see your phone being detected and the flash process will start.
- You will be confirmed when its done with the Green circle.
- Now, keep Volume up+Power button on your phone pressed nad in a few seconds you will get your CWM Recovery screen. Then flash this ROM.
INSTRUCTIONS:
(1) Backup anything you want and go to CWM Recovery. This ROM will wipe your data.
(2) Wipe out everything:
- Factory reset
- Mounts and Storage/Format system.
- Again go to Advanced/Wipe Dalvik cache,battery stats.
This will make your phone into clean state.
(3) Install Zip from sdcard/choose zip file and reboot.
Credits:-
Thank these people if you want :
@mahfoozceecy
Android kitchen
UOT Kitchen
Click to expand...
Click to collapse
Hey. I already [email protected] the recovery andall.. I ttriedto flash this rROM. But started bootlooping.. WWhat do I do? Please reply fast..

Hey can anyone upload this ROMs stock gallery.apk? Thanks a ton!

|
|
| sediROM - or why I created a new ROM based on good old (ancient) ICS
|
|
| Read the background and the whole story and all the discussions about sediROM here:
| http://forum.xda-developers.com/showthread.php?t=2789119
|
|____________________________________________________________________________________________
Some first words:
A lot has changed since I forked LiteROM v0.9 in May 2014 and therefore started sediROM. sediROM has grown up in the meanwhile to a standalone ROM with some mods coming from LiteROM but in comparison to the current state of sediROM they are not many anymore.
LiteROM was a very good starting point for me to dive into ROM development and doing my first steps here so many thanks going to thegreatergood, of course.
As a result of that learning process I will change the base of sediROM in one of the next major releases (see Roadmap) to remove the rest of LiteROM stuff which I do not need/use anymore.
Summary:
Debloated, Partially De-odexed, Zip-aligned, SuperSU, Busybox, Init.d Support, Tons of Memory and Build.prop Tweaks, Sysctl Tweaks, 14 toggles Mod, Power Menu, Tethering fix and more...
Aroma Install
Customizable Apps, Tweaks, Mods
BLN Support
Selectable Kernel, Modem, Bootanimation
No Samsung backdoor inside!
Full Feature List:
Explanation: Default values in "Easy Installation" mode are marked in the following lists in RED
Installer:
sediROM flashing will be done by AROMA installer which gives you 2 selectable modes when starting:
Easy Installation:
This will do all the hard stuff for you and installs besides the ROM itself well tested preselected apps & enhancements.
You need to choose this mode when you install sediROM the first time or want to install an upgraded version of sediROM.
Default values in "Easy Installation" mode are marked in the following lists in RED
.
Modify Installation:
This mode needs an existing sediROM installation first. So you can choose the Easy Installation mode first and after that has finished simply choose this mode to modify things like the Kernel, Modem whatever. This mode can be choosen whenever you want - e.g. you can test a Kernel X and after a while you want to test another one - no problem - simply restart the Installer and choose the Modify Installation mode!
Available Kernels:
sediKERNEL v1.0 (Kernel 3.1.10) (see changelog for details)
CM11 based (Kernel 3.1.10)
JB 4.2 LiteKernel release-20130222 (see changelog for details)
JB 4.2 LiteKernel release-20130221 (see changelog for details)
LiteKernel v1.2.2 GPU not OverClocked and with UnderVoltage
LiteKernel v1.2.2 GPU OverClocked and with UnderVoltage
LiteKernel v1.2.2 Original LiteRom v0.9 Kernel.Tweaked - LiteKernel v1.2.2 overclocked with UnderVoltage
LiteKernel_l2hsicpatched-bubor-r20150506 with L2_HSIC patch based on code of 2014-04
Stock ICS Kernel UCLJ3 (Kernel 3.1.10)
Enhanced UCLJ3 stock Kernel
enhancements:
- init.d support (this enables sediROM bluetooth fix for this kernel)
- added custom boot animation support
Stock ICS Kernel UCLH2 (Kernel 3.1.10)
Available Modems:
UCLJ3
UCKL1
UCLH2
UCKI3
RUXKJ5
Some meaningful Apps & Tools:
ATOM launcher
Several other launchers available in "modify" mode (Apex, Nova, ADW, Stock)
Ghostery, Quickpic, ES File Explorer, AndroidTerm, Vodoo Sound Control
Camera apps: Open Camera, HD Camera Ultra, Stock, ICS, JB)
Kii Keyboard, Samsung Keyboard (default enabled), Go Keyboard, Stock Keyboard
"Under the hood" - Integrated Features:
The possibility to execute shutdown scripts (and for boot-up but every Kernel in sediROM supports that out-of-the-box)
The possibility to choose a non-rooted mode! If you're running Apps which detects root (and hiding is not possible) or if you want to be most secure than this mode is for you. Enterprise users may want this to be complain with their security policy e.g.
(Major) Bugfixes (related to ICS and/or LiteRom):
That was driving me nuts and costs WEEKS to fix -> BT fix (better a fully working workaround) for loosing paired devices after a reboot!!!
Lags/waits when pressing the power button to switch the display on
Within Aroma installer: Many many fixes and enhancements when modifiying or/and installing the ROM to get the most out of it
There are many other fixes which can be found in the full changelog
Device encryption was not working in LiteROM. That was fixed in sediROM since v1.1.
Known issues:
Check the open bug reports for a complete list: Click
HOW-TO flash & Download:
Disclaimer:
sediROM is not fully finished nor bugfree (yet).
[*]But is has less bugs and more features then it's fork "LiteROM" and fixes bugs within stock ICS as well.
[*]I use it continuesly since 1th of May 2014 and sporadically developing / enhancing sediROM since then.
Installing sediROM may result in several explosions in your garden (or in that of your neighbour) .. you have been warned!
DO NEVER USE OPTIONS WHICH ARE MARKED AS "TESTING" IN THE INSTALLER!
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE (nor the things that happens to your house and/or car!)
Requirements:
Do a nandroid backup and ensure you have an EFS backup, too !! EFS: (http://forum.xda-developers.com/showthread.php?t=2019540)
COPY THAT BACKUP TO AN EXTERNAL DEVICE TOO !!!! --> SAVED MY DAY TODAY BECAUSE OF MD5 MISMATCHES THAT CAN HAPPEN.. (I cannot recommend that "fixes" cursing around to simply workaround MD5 sum checking! If the md5sum mismatch you should NOT restore IMO. That may simply not work or can result in bad behaviour etc minutes later or some days later)
Check your backup! (e.g. md5sum -c nandroid.md5) in BOTH places (on the Glide AND on your external ressource)
Install TWRP(!) or migrate to it! DO NOT USE CWM - flashing may fail with CWM (and is besides that not recommended).
DL- Link CWM: CWM v6 (click) (several users reported CWM will not work! use TWRP!)
DL- Link TWRP: twrp v2.7.1 (click)
You should have a windows box running Odin + TWRP near - just for the case.
Flashing Guide:
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE (nor the things that happens to your house and/or car!)
Copy BOTH the sediROM zip AND the sediROM md5 file to your Glide!!
Boot into Recovery mode (Poweroff the device then Power on while holding Volume Down)
Ensure that you use TWRP and that the MD5 sum file is in the same directory as the sediROM zip! Only then TWRP will automatically check the MD5 !
Flash the latest sediROM zip file
Choose "Easy Installation" mode
Answer the few questions and wait until the flashing finishes
When finished - reboot and wait until it has fully started up
The Android setup wizard should come up (if not -> flash again
Go through the wizard and reboot once again afterwards
Enjoy
Please read the FAQ (click)!
Please file a bug if you encounter problems: File a bug (click here)
Download:See above in the Download Menu (click here to open it)http://forum.xda-developers.com/devdb/project/?id=4942#downloadshttp://forum.xda-developers.com/devdb/project/?id=4942#downloads
Mirror:
Use this ONLY when the above xda DL does not work!! Mirror Downloads may be outdated or not available all the time! Mirror-Link <-- DOWN. Write me a PM if the xda download does not work and I will upload it for you
Take also a look on:
Changelog
FAQ
Roadmap
Trouble
File a bug
Request a feature
Best regards
xdajog
Special THANKS (please give them a Thanks-Click ! That costs you nothing but 2 seconds (for each)!!)
thegreatergood for LiteROM v0.9 and LiteKernel builds --> Give a "Thanks" here
bartito for Shutdown-Script option (and therefore the possibility to fix the BT issues!!) --> Give a "Thanks" here
PS: Happy for every single click on my "thanks" button (you are free to do that on the changelog, roadmap and faq post again... )
And as an absolutely premiere I want to say thank you to maddbomber83 for the donation.
You're the first one (until now the only one ) who say thx this way. Highly appreciated and motivating.
Sources:
sediROM --> https://github.com/xdajog/android_i927_sediROM
sediKERNEL --> https://github.com/xdajog/kernel_samsung_i927
.
XDA:DevDB Information
sediROM, ROM for the Samsung Captivate Glide
Contributors
xdajog, bubor (for all his work! highly appreciated!), maddbomber83, organic2 (for heavy testing!)
Source Code: https://github.com/xdajog/android_i927_sediROM
ROM OS Version: 4.0.x Ice Cream Sandwich
ROM Kernel: Linux 3.1.x
ROM Firmware Required: sediTWRP or TWRP >= v2.7
Based On: STOCK, LiteROM
Version Information
Status: Stable
Current Stable Version: v2.1 (2.1.2)
Stable Release Date: 2016-01-04
Current Beta Version: ---
Created 2014-07-11
Last Updated 2016-07-26

FAQ
Frequently Asked Questions (FAQ)
Why another ROM and why build on ICS?
Please read the full story here: http://forum.xda-developers.com/showthread.php?t=2789119
[*]Do you need to network unlock the Glide?
Follow the excellent guide here: >Click here<
And also take a look on my additions to it here: >Click here<
[*]When version [FILL-IN-WHATEVER-YOU-LIKE] will be released?
Please keep in mind that this project is not a full time job so questions about a release date is something I will / can not reply to.
This is not because I don't like you but it is because I cannot promise anything. RL is my priority and this can not be controlled (fully) as you may know
[*]Is device encryption supported?
Yes, device encryption is supported since sediROM v1.1
You may want to check out a working TWRP version to be able to still do nandroid backups here sediTWRP with decrpytion support (click)
Hint: Device Encryption is fully supported when choosing the easy installation mode while installing.
That means if you choose the modify mode afterwards be careful what to choose within the TWEAK section (kernel optimization/swap internal to external sdcard/...). Those are not all tested yet so do a backup before choosing them. ALSO for /sdcard! because that gets encypted to.
If you choose the easy installation method and change only apps/kernel/modem etc you will be safe though.
[*]Can I upgrade from a previous version of sediROM?
basic* --> will be explained some lines later (pls look for: "What does "tested (basic)" means?" in this FAQ)
v2.0 ----> v2.1
Yes: tested (basic + full)
basic --> pls look for: "What does "tested (basic)" means?" in this FAQ
full -----> tested on my production device, too
v1.7 ----> v2.0
Yes: tested (basic + full)
basic --> pls look for: "What does "tested (basic)" means?" in this FAQ
full -----> tested on my production device, too
v1.6 ----> v1.7
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.5 ----> v1.6
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.1 ----> v1.6 (this is the last upgrade test for v1.1. I will not test upgrading to higher releases from v1.1!)
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
v1.1 ----> v1.5
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ)
The same pre-requirements necessary as in v1.0 ---> v1.1 !
v1.0 ----> v1.1 (this is the last upgrade test for v1.0. I will not test upgrading to higher releases from v1.0!)
Yes: tested (basic --> pls look for: "What does "tested (basic)" means?" in this FAQ).
Manual pre-requirements necessary! To upgrade from v1.0 to v1.1 you need to wipe /system partition manually before you start the upgrade because there is a bug in v1.1 and v1.5 preventing from doing the partial wipe which normally will do that for you.
These are the steps:
Within TWRP choose the wipe menu and then "advanced". Afterwards select only "system" !
Go on and afterwards start the sediROM installer again and choose "partial wipe". Because you have wiped /system manually the installation should run fine afterwards.
This way you will NOT wipe any configs or apps or something as long as you leave /sdcard and /data untouched in step 1.
That workaround should work even when you already tried the partial wipe in "Easy Installation" mode.
If you use L2SD here a special note: from @maddbomber83:
maddbomber83 said:
Just as a note; upgrading an install that has a lot of symlinks (such as L2SD) does not appear to be working properly. If your install includes any of these then as the Developer has stated, MAKE SURE TO DO A NANDROID BACKUP!
On mine at least, the phone had a lot of FC errors focused around the PHONE APK. If you did do a data wipe and can get back into your phone but are missing your linked apps then:
Q. I upgraded/changed my ROM and I can not see my linked apps, their files are on the 2nd partition but the system can not see the apps. How can I make them available, do I need to reinstall and relink them again?
No, if you didn't wipe data when updating ROM the only thing you need to do is to run "Recreate mount scripts" from "menu -> more" within Link2SD and do a normal (not quick) reboot.
If you wiped data, after executing "Recreate mount scripts" and rebooting, run "Relink all application files" from "menu -> more" and then reboot. All of your linked apps should be available again after reboot.
If you also wiped dalvik-cache, in addition to the above step run "Link dalvik-cache files".
Click to expand...
Click to collapse
What does "tested (basic)" means?
When I test upgrades I do that very basic. As the system is still the same (ICS 4.0.4) and normally no android related things changed I strongly believe that doing upgrades shouldn't harm anything. Even all the apps should work as long as you don't played around with system apps (In Titanium Backup and other tools you can make an app a system app which means it will also be copied to the /system area which will be overwritten due to the upgrade. If you have converted a user app to a system app it will be lost then). Normally you wouldn't do such a conversion but as it is possible I need to add that hint here..
When I state an upgrade path as "tested (basic)" it means that it SHOULD work but as always no guarantee
My Test setup is always as follows:
a custom wallpaper (Home + Lock Screen)
added some icons to the launcher
set a lock screen password
system settings for screen timeout and screen off
WiFi settings for my WLAN
Installed Titanium Backup app
acquiring root permission (ES File Explorer and after "adb shell")
Upgrade guide:
do a nandroid backup! <-- sigh this is VERY important do not skip that step!!
copy that backup to your pc just to be sure!
choose to install sediROM
choose easy installation
then (the upgrade magic): choose "partial wipe" !
complete the rest of the installation and you're done.
[*]Screen wakeup delay?
I have a screen wakeup delay when using sediROM! AND I use sediROM < v2.0 (e.g. v1.7).
The problem here is the default used kernel in sediROM before v2.0.
All smaller versions uses "Litekernel" as the default kernel which is the root cause for this problem.
Before v1.7 there is no really option for fixing this other than installing another kernel manually.
In v1.7 you are able to switch to the CM11 kernel in the modify mode within the sediROM installer but the shipped version has issues with MTP (connecting storage to PC).
So that is also not a workaround for everyone unfortunately but if you do not use MTP (USB mass storage works btw) this may an option for you.
Well so what is the solution?
Install sediROM v2.0 and use the latest sediKERNEL (default in easy installation mode) or the CM11 kernel (including the MTP fix) provided by bubor or the modified STOCK UCLJ3 kernel by xdajog (me).
All of them have no screen wakeup delay issues and working fine.
All are available in v2.0 and you can switch between them in the modify mode as always (sediKERNEL is default since v2.0)
[*]What is that "Bluetooth HSP fix"?
Bluetooth HSP (HeadSet Profiles) is buggy in ICS 4.0.4. All paired devices gets lost after a reboot. In sediROM there is a fix for this implemented. To be honest that fix was the reason why I started sediROM..!
It is implemented in two steps:
a shutdown script which backups the bluetooth pairings and settings
an init.d script on boot which restores those pairings
The problem that pairings go to hell after a reboot is kind of special. The first thought was to simply backup the correct folders and restore them again when boot up. That alone won't work - the pairings will not shown up when enabling BT afterwards because they are deleted right when BT gets enabled. I tried to find out why but without success. Then I found a way by simply protecting the BT config file. That said when BT starts up it can not delete it anymore and stops trying that and that means the restored pairings will be read and shown.. A little bit crazy I know but it works very great (in my case).
Further Readings (they may related to this issue):
Kenneth Thorman's discoveries
Google Issue 34161
Some suggestions at stackoverflow (5885438)[/MENTION]
Another one from StackOverflow: 5102549
There are different caveats depending on which sediROM version you are using with the current implementation:
sediROM >= v1.7
Since v1.7 the BT fix is very stable and the caveats we have are absolutely minor:
Bluetooth will from now on always beeing OFF after a restart. That is wanted and nothing really bad and is a protection that things goes right.
After sediROM is up'n'running you can switch on BT and/or off again - only when rebooting BT will be always off again.
The system needs to be fully started in order to get BT working. As this is only a couple of seconds (about 10-20 sec) and starts while in boot process this has no impact for the user.
sediROM < v1.7
If you change the name in BT settings that will not be restored atm so it is sticked at "SGH-I927"
Under some circumstances the BT fix hasn't worked. check out the details at the bottom to find out the reason.
sediROM = v1.5 OR sediROM < v1.5
If you want to delete a pairing it was restored in sediROM <v1.5 when you reboot - to completely delete a pairing you need to:
in sediROM = v1.5:
You don't need to do anything. If you delete a pairing or add a pairing both will be saved and no need to do anything else then reboot.
In case you have problems you can delete /sdcard/.sediROM/btfix/00_btbackup.tar and/or check the logs in /sdcard/.sediROM/btfix/ . But that is normally not needed anymore.
in sediROM < v1.5:
delete "/data/local/tmp/00_btbackup.tar" and then reboot
Detailed background information
and the reason why before v1.7 it may haven't worked for everyone:
"rm" will delete the directory and I'm not able to find out which file will be deleted first and therefore I can't prevent the deletion of the pairings as I do before!
Background:
/system/bin/bluetoothd will remove the whole directory /data/misc/bluetoothd (well that is known and at the end the reason why the pairings gets lost in ICS)
I "fixed" that by making the config file immutable so Android is not able to delete the directory anymore which results in the fact that the pairings will stay!
Unfortunately it is not such easy as thought. On my second device I saw that my pairings still get lost..
Well ... As mentioned bluetoothd wants to remove and it uses "rm -r" for this. Exactly it will call "rm -r /data/misc/bluetoothd/".
.. and "rm" uses the C function "readdir()" when it parses the directory and readdir() will give you the result randomly (it depends on several not predectivable things).
There is no chance to know the exact order and even when it would be the case then mine would be different from yours!
... but that's not all. Some docs said that subdirs will be deleted first when using "rm -r" but in fact that is NOT true! If it would be true then the solution would be very easy.
The question stays why it happens on my productive phone and the previous fix still working fine on my DEV device. I believe that it is because I restored a previous made BT backup after I installed sediROM v1.6.
The command "tar" uses the same behaviour as readdir() so it is also randomly when it comes to restoring a backup. That would explain it maybe but I'm not totally sure.
You can test that readdir() behaviour very easily. If you execute a "find . -type f -print" you will see what readdir() see.. The result is obviously unsorted.
Execute it again and the result stays the same but that changes when files are deleted or other things happens to the filesystem!
In my case the problem occured after enabling encryption because that changes also things related to readdir() obviously.
Further readings:
- http://linux.die.net/man/3/readdir
- http://utcc.utoronto.ca/~cks/space/b...x/ReaddirOrder
- http://stackoverflow.com/questions/8...antee-an-order
The way of finding a solution:
- I tried to find out the root cause again (means bluez Java code).
- I tried to port the latest v4 of the bluez stack which contains a lot of fixes.
- I tried to re-compile bluetoothd in order to remove the whole folder deletion.
- I tried to save/restore the settings.db sqlite3 database (alone and together with the BT files)
- I tried some other stupid things.
The solution:
At the end I found a working solution (again). Instead of protecting a single file only which readdir() accesses randomly I switched over to protect the whole directory.
This way the order within the directory doesn't matter anymore
That alone wasn't enough. I needed to completely restructure the way of handling that fix.
That means:
- the bluetooth main.conf was changed to set InitiallyPowered=false !
- I stop all bluetooth related processes when booting
- I restore the previous BT settings and pairings
- I make the BT dir(!) immutable
- Then I give rfkill0/state the info (add a "1") that bluetooth is able to start
- Then I start all BT processes in correct order
- Then I remove the immutable bit from the BT dir
(Minimal) Caveats:
- Bluetooth will from now on always beeing OFF after a restart. That is wanted and nothing really bad and is a protection that things goes right.
After sediROM is up'n'running you can switch on BT and/or off again - only when rebooting BT will be always off again.
- The system needs to be fully started in order to get BT working. As this is only a couple of seconds (about 10-20 sec) and starts while in boot process this has no impact for the user.
[*]What is that "adb" thing??
adb stands for: Android Debug Bridge and can help a lot when it comes to work with your device. It is not for developers only but they use it a lot of course.
But a normal user can use this to exchange files without the need of mounting, backing up the device, reboot the device and use it as a very comfortable way of having a terminal emulator.
Normally adb itself is not available as a standalone application - it comes with the Android SDK which is very big and heavy if you want to use adb and/or fastboot (another great tool) only.
But we live in a great world with many people wanting to make things easy so here you go when you want/need only adb and fastboot:
download & install adb at lifehacker
(Direct link for Windows users: Got to easy ADB install thread)
[*]What is a "nandroid" backup?
nandroid means essentially: "a full image of all your partitions" so it is a full snapshot of your ROM including all your apps and contents.
The name NANDroid is a portmanteau of "NAND" (as in Flash memory - NAND flash) and "Android." (Source)
[*]How to create a "nandroid" backup?
(See above for the meaning of "nandroid backup")
You have several options on how to do that.
The normal and absolutely recommended way is to do that "offline" (from within recovery mode) but you can also do it "online" (while Android is running).
.
Offline nandroid backup by using TWRP recovery: Guide
If you have no custom recovery installed read on.
.
Online nandroid backup:
by using an app:
There is 1 (known to me) "online" nandroid backup tool available which will backup from within your running Android: PlayStore.
I tested it and still using it since a while and I really like it but I would not fully resist on it.
I had no problems backing up but sometimes an app is lost when restoring. This may have been fixed but well it is like imaging a running Windows or Linux system:
Do not do it online if you can - it may/will work but there could be problems/inconsistencies later!!
If you never made a nandroid before doing it online will not harm anything and should be your first start. So install the Online Nandroid backup tool and begin.
Check out this guide for some hints: Guide
(If you like the Android app do not hesitate to buy the unlock key to support the developer!)
by using commandline tools:
First of all you need "adb" installed (check out the FAQ #8 above).
Then you need someone who is telling you the device partition table and you need a big sized SD card to hold the images.
The reason is that you will use a special command named "dd" which images the whole partition (not the content only!).
dd is a VERY dangerous tool because if you use it wrong your device may get bricked so it is essential that you are using the
correct command and check that twice!
Check out the next FAQ on how to do this for the i927.
[*]How to create a "nandroid" backup for the i927/cappy - WITHOUT having a custom recovery?
The whole process will take a big amount of time but it is worth to follow each step including the md5sum checks at the end.
Please read the previous FAQ first because there you will find more information about background and other options you may have.
Ensure you have a SD card inserted which is big enough and having enough free space available (4GB at least! I recommend at least 8 GB but this depends on the size of your current data partition. A completely stock ROM with nothing installed and unused will need 3 GB space).
.
Install "adb" on your pc (check out the FAQ #8 above).
root your device (check out FAQ #12)
connect with adb to your (running) i927:
adb shell
(you should see a prompt)
su
(you need to grant permission if you haven't yet)
Then backup your current ROM and data:
dd if=/dev/block/mmcblk0p2 of=/storage/external_SD/system.2015-07-20.img
dd if=/dev/block/mmcblk0p9 of=/storage/external_SD/boot.2015-07-20.img
dd if=/dev/block/mmcblk0p6 of=/storage/external_SD/userdata.2015-07-20.img
dd if=/dev/block/mmcblk0p8 of=/storage/external_SD/recovery.2015-07-20.img
# If you never backed up your EFS you really should do that once:
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
Click to expand...
Click to collapse
Just to be sure you can do an online backup now, too ( Guide ) Online Nandroid backup App
.
copy the backup(s) to your device (connect USB cable - open your external storage and drag&drop) <--- DO NOT SKIP THIS STEP!!!! It is absolutely essential!
Check your copy on your device:
md5sum /storage/external_SD/system.2015-07-20.img
md5sum /storage/external_SD/boot.2015-07-20.img
md5sum /storage/external_SD/userdata.2015-07-20.img
md5sum /storage/external_SD/recovery.2015-07-20.img
md5sum /storage/external_SD/modemst1.img
md5sum /storage/external_SD/modemst2.img
Click to expand...
Click to collapse
Download a md5sum checker like this one Windows MD5 and load each file you copied to it (on Linux the "md5sum" command can be used of course).
compare the md5sums from the above output and ensure that they are all matching.
[*]How to root the i927/cappy?
There are several guides on this here are 2:
- First or
- Second
[*]"efs" backup and/or restore?
There are several guides on this but here is mine.
Backup efs:
1) open a terminal
2) type in su --> now you may need to give root permissions
3) type in tar zcvf /sdcard/efs-backup.tar.gz /efs
4) type in dd if=/dev/block/mmcblk0p1 of=/sdcard/efs-dd.img
5) connect your device to a PC and copy both the efs-backup.tar.gz and efs-dd.img to your PC
6) now you have a full backup of your efs and therefore your phone unlock state
Step 2 is essential you need root for this in order to work.
Normally you can see a change from a dollar $ sign to a hash # one after root has been achieved like this:
xxxxxx:/ $ > su (answering the request for root permissions with yes)
xxxxxx:/ # >
Restore previously saved efs:
1) open a terminal
2) type in su --> now you may need to give root permissions
3) connect your device to a PC and copy your dd-image backup "efs-dd.img" to /sdcard of your device
optional: do the same for the tar archive "efs-backup.tar.gz". This is just needed for the case the dd image is corrupt.
4) type in the terminal dd if=/sdcard/efs-dd.img of=/dev/block/mmcblk0p1
optional: if that step fails ensure you have mounted /efs (ls -la /efs should show you several files) and execute (press Enter after each line):
su
cd /
tar xvzf /sdcard/efs-backup.tar.gz
5) reboot your device
6) now your efs is fully restored and therefore your phone unlock state, too
Step 2 is essential you need root for this in order to work.
Normally you can see a change from a dollar $ sign to a hash # one after root has been achieved like this:
xxxxxx:/ $ > su (answering the request for root permissions with yes)
xxxxxx:/ # >
.

Changelog
Changelog of sediROM
v2.1.0 - v2.1.2 (Release date: 2016-01-04)
--------------------------------------------------
Bugfix Release
Github detailed changelog (compared with the previous version):
https://github.com/xdajog/android_i927_sediROM/compare/v2.0...v2.1
Github tag for this version:
https://github.com/xdajog/android_i927_sediROM/tree/v2.1
Enhancements
introducing sediROM testsuite: /system/xbin/sediROM_testsuite.sh
execute it like this to test if your sediROM version is fully working:
adb push sediROM_testsuite.sh /sdcard/ && adb shell "su -c sh /sdcard/sediROM_testsuite.sh"
Fixes
issue #25 (https://github.com/xdajog/android_i927_sediROM/issues/25)
YES ALL THE FOLLOWING IS > 1 < SINGLE RELEASE
v2.0.68 -v2.0.1 (Release date: 2015-12-29)
--------------------------------------------------
Major Release
Github detailed changelog (compared with the previous version):
https://github.com/xdajog/android_i927_sediROM/compare/v1.7...v2.0
Github tag for this version:
https://github.com/xdajog/android_i927_sediROM/tree/v2.0
Enhancements
first sediROM app (sediROM_boot.apk) inside.. the app itself is extremely simple: a text and a button thats all. When
sediROM boots the first time a new added init script will detect if this is the first boot and if this is the case it will open
the sediROM_boot app. Read & follow carefully the hints there!
you to reboot. May be annoying but due to douzends of changes in v2.0 it is really necessary to point to a clean reboot.
All scripts related to run sediROM on github now !!!! Starting from v1.7.
Introduced the first version of sediKERNEL (v1.0) a customized kernel optimized for STOCK ICS so as for sediROM.
sediKERNEL is based on CM11 kernel made by bubor (so l2_hsic patched, no wakeup delays, OC etc) enhanced by:
- adding MTP support for STOCK ICS!
- less battery drain
default kernel = sediKERNEL v1.0
Upgraded AROMA from v2.56 to v2.70-RC2 (means compiling 2.70rc2 from the sources!)
Go DIRECTLY from the installer to the MODIFY mode!
That means when you choosen the easy installation mode and everything went fine you will get the
offer to open the modify mode instead of rebooting
No adb debugging from initial ram disk (security fix)
No adb debugging as default (security fix)
Integrated LiteKernel_l2hsicpatched-bubor-r20150506 with L2_HSIC patch included (hopefully fix battery drain)
The kernel is based on code of 2014-04 afaik also maded by bubor
Integrated enhanced UCLJ3 stock Kernel (option in modify mode)
enhancements:
- init.d support (this enables sediROM bluetooth fix for this kernel)
- added custom boot animation support
Migrated and integrated JB 4.2 LiteKernel release-20130221 to sediROM (option in modify mode) which comes with the following changelog:
(all changes between v1.2.2 to 20130221)
- Interactive set as default governor ... Wheatley lags on AOSP
- Added FM Radio Driver
- Fixed Mic for AOSP
- Fixed/Added 1.4ghz frequency
- Fixed/Added Smartassv2
- Removed USB Whitlists
- Recoded BLN myself so that there is no need for an app... has in kernel blinking ...
- Tons of Cleanup
- XZ Kernel Compression
- Removed Wake Lag
- Fixed and increased Charging Current
- Tweaked Ondemand for better performance
- New Storage Setup
Migrated and integrated JB 4.2 LiteKernel release-20130222 (option in modify mode) which comes with the following changelog.
HINT: MTP does not work with this kernel. I will not fix that! If you need MTP use release-20130221 or sediKERNEL!
(all changes between r20130221 to r20130222)
- Entropy Tweaks inspired by lambgx02s Seeder (for silky smoothness)
- Memory Managment Tweaks
- Added Dynamic vsync
- Zipaligning and Fix permissions at boot (zeppelinrox script)
- Tons of Kernel Tweaks for Battery life and Performance...
- IO tweaks...
- Auto EFS Backup...
- New Experimental WIFI Management battery saving feature: If at screen off, WIFI is inactive and or using very little traffic, it gets turned off
and then on again once you wake device, if battery level is below 50% it will no longer turn wifi on again, if you disable WIFI it will be left alone...
- Decreased Vibration Intensity (when you boot up device you will feel a slight vibration)...
- New Experimental CPU Management feature: Frequency get changed according to battery level....
- No more laggy lock screen drawing ...
- Instant wake to lock screen
- Removed Increase Charging Current mod till more testing can be done
- Improvements for better battery life
- Stability
- Option to Disable WIFI and CPU Control
- Clear Memory after boot
- Massive Improvements to: Performance, Battery Life
- Fixed Battery leak with CPU + WIFI manager
- Memory Management Improvements
- SD card Speed Tweaks
- Reduced Wake Lag
- Reduced Stuttering when playing music on screen off
- CPU-Manager is now enabled by default ... it boosts wake speed manages sleep speed and reduces max speed as your battery diminishes ... the profiles are fully modifiable and all with no battery drain ...
- MTP is now the default pc connection ... if you want mass storage change /data/LiteKernel/MTP to "0"
- Memory management improved .... should also help for battery life
- frequency with Interactive governor will now stay a little lower ... should help with screen on battery life ....
crond (provided by busybox) activated to automatize things like in Linux
init script 00sediROM will prepare the settings, paths etc for crond to start
and init script 99sediROM will start the crond
Open Camera will be the only camera app installed by default. HD Ultra camera stays an option in modify mode.
added this changelog to AROMA installer screen
added modify option after easy install in README of the installer zip
updated sqlite3 binary to v3.8.7.4 (THANKS to user tech128 details: http://forum.xda-developers.com/showpost.php?p=52174054)
Removed all my own copyright hints and licensed all sediROM scripts under CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0) license! Freedom for everyone ;o)
New script header including new version concept of all sediROM scripts
Updated SuperSU app and binaries to v2.46
Installation of SuperSU is now completely based on the original installer to avoid any problems while installing
Added a new minimalistic terminal app AndroidTerm (https://play.google.com/store/apps/details?id=jackpal.androidterm) which replaces connectbot as default installed terminal app.
Connectbot will not being installed by default anymore but you can still install it in modify mode.
Connectbot has many advantages but 1) updating within a ROM is harder then with AndroidTerm and 2) I want to keep it minimal so no ssh, telnet. only a local console.
BACKUP Connectbot before upgrading when you still want to use it.
If you want to continue using CB you can upgrade and at the end of the installer select "Start sediROM modify mode"
and install Connectbot directly after installation (Screen "Main Features" - Section "Tools"). Nevertheless you still need to restore your settings as they are lost.
Added Ghostery (v1.2.1) - a very tiny (around 2 MB installer files), fast, stable and anonymous browser (https://www.ghostery.com/en/how-it-works). Will be installed by default!
Removed Google Chrome to save disk space (the installer files are 64 MB!)
Chrome is VERY slow on our phone in comparison to other browsers (try to open several tabs & browsing) and last but not least updating it within sediROM is harder then with other browsers.
BACKUP Google Chrome before upgrading when you do not want to loose settings.
Started to use a common function file for the init scripts in sediROM (/system/etc/sediROM/init.func)
Several new boot logs are written to /cache/*.debug which makes debugging easier (commit b053e738 and commit e3fe9332).
After sediROM is booted fully up everything will be moved to: /preload/.sediROM/boot/.
Added commandline aliases/shortcuts for remounting any mountpoint as read-write (remountrw) or read-only (remountro) - handled by commit 41fcc3c6.
Added automatic /efs backup !!!
- The backup is a full image dump made by dd
- backup will be saved to /sdcard/efs_[current-date].dd
("[current-date]" will be replaced by the current date+ unix timestamp)
- if somehow no timestamp could be generated the sediROM version number will be used instead
- if the backup fails we will CONTINUE! That means the installer will not abort to ensure that you will not end with an unused device
That also means that you should not rely on that efs backup it is a help for those not familar with the CLI only.
Added a "getdate.sh" script in aroma installer to filter tzdata errors
Added a sediROM bootanimation (NSA) and made it default
Removed facebook installer files from sediROM zip (was unused since the beginning) which frees some space of the ZIP
Fixes
on first boot bluetooth will be enabled once. This is needed to ensure that /data/misc/bluetoothd/MAC-ADRESS will be created.
That directory is device specific and will be created by Android when not existent. As the bluetooth fix from this version on
depending on a indicator file within this directory it is necessary to enforce its creation by enabling bluetooth once.
This is done within the init script 00sediROM_1stbootDT.
(!) whenever a soft reboot or system force close has happened bluetooth has stopped working. The only workaround was to
reboot the device. A fix was added which checks every minute if the bluetooth indicator file is there and if not the init
script for fixing bluetooth will be restarted. This way in worst case scenario of a soft reboot crash after 1 minute latest
Bluetooth becomes usable again (so no reboot anymore needed).
Changes:
- /etc/cron.d/root
Added:
- /system/xbin/sedi_btFCdetect.sh
fixing some problems with encrypted storage detection
due to a timing issue some early logfiles of sediROM were not got written to /sdcard. The fix was to use /preload instead:
When sediROM boots the init script 00sediROM_first will try to mount /preload.
If mounting /preload was successful it will be used for all logs and existing data will be moved to /preload.
It would be nive to have a symbolic link here but this is not possible across different filesystem types. So there will be
an indicator created in /sdcard/.sediROM with the hint to goto the /preload for logs instead.
All scripts within sediROM were modified to check for the existence of this indicator file and dependending on that they use
/preload or /sdcard for their logging data.
(!) when a soft reboot occured the bluetoothd directory gets trashed, too. If you then rebooted the empty bluetooth settings gets
backed up and therefore you boot with emtpy BT settings. This was fixed by using an indicator file (btfix.indicator) which
will be added after booting the first time. When a system shutdown is initiated sediROM will check for this file and as a
soft reboot would also delete that indicator file it will detect this and backup when this indicator file is still there.
In other words: when a soft reboot has occured you can safely reboot now and your settings will be there on the next reboot and
not lost.
cosmetics within updater-script output and AROMA
(!) Extreme battery drain caused by Google Play Framework Service.
This fix is a big one and splitted into 3 parts:
1) When system booting up /system/xbin/sedi_fix-gplay-drain will be triggered by /system/etc/init.d/00sediROM_first
2) /system/etc/init.d/00sediROM_first will also enable the cron daemon crond (coming with busybox) so we can automatize things
"enable" crond means several things need to be setup first:
a) creating a /etc/passwd
b) creating /etc/cron.d/
c) starting crond as a process
3) With the now introduced crond we can run the script /system/xbin/sedi_fix-gplay-drain every 8 minutes.
This is to ensure that even when Google updates (this will be done SILENTLY! by Google) it's app(s) it will be fixed again on the next cron run.
/system/etc/cron.d/root contain's the magic line for that.
For details checkout the original thread here:
http://muzso.hu/2014/09/18/how-to-f...yanogenmod-11-with-google-play-services-and-o
http://forum.xda-developers.com/showpost.php?p=53881089
http://www.imoseyon.com/2011/02/cron-on-android-is-awesome.html
init.d scripts cleanup. 00sediROM_tweaks in the installer package under /system was never used because always replaced by the BTfix one.
I moved the both scripts 00sediROM_first and 00sediROM_last to /system/etc/init.d/ instead of havin them within BTfix.
All this is firstly cosmetic only but becomes more and more important to have things clear for coding.
Removed the option to install Cranium & IcePop Bluetooth (was for testing purposes only)
compat linkage when coming back from JB now respecting it's existence. That means it will check first and do the links when needed only.
RNGD's init script was blocking for 30s the next boot scripts (changed to 3s intervalls)
changed order for the BT fix init script (from 99 to 92)
the 00 sediROM init script was not respecting encryption state which itself is not a problem but as the switch to /preload is happening in this
version this has result in problems. The fix was to check for encryption state and /data/misc before proceeding
fixing enhancing databases coming with init script 16sqlite:
- sqlite3 binary was not working (since literom days....!) and therefore replaced!
- when /data and/or /sdcard is encrypted no enhancements had taken place (now respecting encryption state and wait until decrypted)
installer: When FULL-wiping all init scripts were not executed because of missing /preload/.sediROM and /sdcard/.sediROM. Those directories are
created by the installer now or when they exist the following files gets deleted instead:
- /preload/.sediROM/.initialized
- /preload/.sediROM/dir-moved-2-preload.txt
- /sdcard/.sediROM/.initialized
- /sdcard/.sediROM/dir-moved-2-preload.txt
installer: When PARTLY-wiping all init scripts were not executed because of missing /preload/.sediROM and /sdcard/.sediROM. Those directories are
created by the installer now or when they exist the following files gets deleted instead:
- /preload/.sediROM/.initialized
- /preload/.sediROM/dir-moved-2-preload.txt
- /sdcard/.sediROM/.initialized
- /sdcard/.sediROM/dir-moved-2-preload.txt
BETA-related (fix affects BETA release only): litekernels in modify mode could not be installed (therefore may soft bricked the phone!)
RFKILL switch desc added inside 92sediROM_btfix, slightly modified the log output too
(!) Not everything was cleaned/removed when UN-ROOT was selected. The uninstallation/unrooting will remove all related parts now including dalvik cache etc.
daemon mode in install-recovery.sh makes no sense in sediROM as it is not SDK 18+ and no selinux forced therefore removed
When switching the kernel the modules within /system/lib/modules/ were not deleted (e.g. dhd.ko) which could had caused trouble in rare situations.
The installer now deletes all modules when switching to another kernel
BETA-related (fix affects BETA release only): new sediKERNEL version (v1.0 build 50). Change: wifi as kernel module instead builtin.
On encrypted devices the installer was not able to mount /data and /sdcard. Now it will:
- check for the existence of dm-0 and dm-1 which are the unlocked /data and /sdcard partitions
- when they can be found they will be mounted and used accordingly and correctly
- when they can NOT be found an abort is raised to avoid data loss - 3 hints are given to solve the situation
- you N--E--E--D sediTWRP - Clockworkmod cannot unlock encrypted devices and "normal" TWRP versions are not able to unlock STOCK ROM encryption!!
--> sediTWRP can be downloaded here: http://forum.xda-developers.com/showthread.php?t=3007035
installer: When upgrading / partial wiping the system partition will be deleted at the END now. This is to avoid data loss e.g. when you have an encrypted
device and not unlocked the partitions in sediTWRP (or when using CWM or other "normal" TWRP versions)
installer: When normal installing / full / recommended wiping the system partition will be deleted after successful mount of /data and /sdcard first.
This is to avoid data loss e.g. when you have an encrypted device and not unlocked the partitions in sediTWRP (or when using CWM or other "normal" TWRP versions)
installer cosmetics:
- Easy installation description changed
- "Recommended Wipe" renamed to "Clean install / Recommended Wipe"
- "Partial Wipe" renamed to "Upgrade mode / Partial wipe"
fixes an issue where Android goes into a boot loop in rare circumstances (issue #11). In rare cases several XMLs will be zeroed out by Android when not shutdown cleanly.
Those XML files still be there but they are empty! When Android boots up it tries to open those XMLs and as they are empty the whole boot process will hang!!!
I fixed this by:
- adding a new function which searches for all opened /data/system/.*xml files after a given period of time
- after this time period a file size check will be made: if the open xml is 0 it will be renamed
- when a renaming happened the parent process will be killed to ensure the boot process will not stop
moved the first boot detector to the near end of the boot process instead! That may fixes other issues as well regarding displaying the first boot app
better integration of the wait for system readiness while booting up (commit d0970abf6ec6c65af9999e2428b96fe293a55f17).
bluetooth file exchange was not working since a change in audio.conf
content in installer welcome screen
modify mode: when no kernel was selected the radio/modem force selection dialog appears
modify mode: removed several hard coded preselections
modify mode: modifying failed under some circumstances which resulted in aborting and may have left you with an unusable device
For older releases see attached file (View attachment CHANGES.log) !
Click to expand...
Click to collapse
Dev facts
sediROM v2.1 (Bugfix Release)
Development duration: about 8 hours
Finished on: 2016-01-04
Builds taken: 3
Changes: 2
sediROM v2.0 (Major Release)
Development duration: about 304 hours
Finished on: 2015-12-29
Builds taken: 69
Changes: 64
sediROM v1.7 (Important Bugfix Release)
Development duration: about 68 hours
Finished on: 2015-02-02
Builds taken: 7
Changes: 6
sediROM v1.6 (Important Bugfix Release)
Development duration: about 24 hours
Finished on: 2015-01-08
Builds taken: 22
Changes: 11
sediROM v1.5 (Big Maintenance Release)
Development duration: about 67 hours
Finished on: 2014-12-24
Builds taken: 24
Changes: 21
sediROM v1.1 (Bugfix Release)
Development duration: about 28 hours
Finished on: 2014-10-21
Builds taken: 15
Changes: 8
sediROM v1.0 (First Stable Release)
Development duration: about 640 hours!
Finished on: 2014-09-02
Builds taken: 58
Changes: more than 82
Click to expand...
Click to collapse

Trouble?
Trouble after flashing?
For EVERY request you have to upload the install log:
after every installation an automatic logfile will be saved to /sdcard/install_sediROM_vX.x.x.log where vX.x.x is the sediROM version number. Upload that log to pastebin and give me the URL.
Flashing failed? or Download mode always coming up?
Download rooted stock ICS http://forum.xda-developers.com/showpost.php?p=30421243&postcount=1
Go in download mode
Open Odin in Windows
Select Auto-Reboot and nothing else and add in the PDA section the above ROM (unzip first - you need the tar.md5 inside)
When it finishes your Glide should reboot (and Odin should say PASS). You do not need to wait if it is fully booting up and you can reboot once again in the download mode
Open Odin in Windows again
Flash TWRP (pretty nice gui, better handling, charging while active) or CWM (ugly gui, more robust, will NOT charge while active) over the PDA slot again (see flashing guide above for DL links)
(I use TWRP and several reflashings etc and it is working fine for me - but keep in mind that Nandroid backups are NOT compatible between those both recovery tools so choose the one you had before. I can highly recommend that you switch to TWRP when you currently using CWM because the handling and features are great (besides flashing probs of course)
For those who need more details and screenshots etc: http://unbrick.itcse.com/unbrick-soft-bricked-samsung-captivate-glide-sgh-i927/
"no recovery kernel" displayed when trying the recovery menu?
That is easy to solve when you know the correct partition name.. That is for the glide "LNX".
On Linux: Start heimdall or heimdall-frontend and simply flash a kernel back. For this you need a pit file which need to be catched first:
Download PIT:
Code:
$> heimdall download-pit --output mycurrent.pit
Flash the kernel with that catched PIT info: (Click to see an image of the heimdall frontend)
Flashing itself failed? Corrupted image message or /cache mount failures?
Flash with TWRP instead of CWM! See the OP for the DL Link (section Howto & Download)
loosing signal / bad signal ?
In my case I had sometimes problems with my baseband (loosing signal / bad signal) which was silly.
I found out that this was not ROM related because happens with several ROMs and total random.. Because of that randomness it was first hard to say if it is ROM/Modem based or not.
So if you come in such a situation and a modem change does not help I can recommend to open you Glide's back and check the SIM..
Sometimes (not often) it can be easy: In my case a little tape fixed my problems with that because the SIM is hanging very lax in it's case..
Maybe that little trick helps others, too

Roadmap
ROADMAP FOR sediROM
I never promise that a requested feature will be in a specific version or even added!
But you can add your ideas and wishes here if you like:
Open a Feature request (click here)
If you find a bug then it is your absolute responsibility to file a bug.
You can do it here: >CLICK HERE<
Version X.x
The Roadmap has been completely moved to github:
Github Milestones
upcoming features/enhancements need to fulfill at least one of those:
Fixing a (real) bug or serious problem
Performance optimization
Battery optimization
System optimization or stability
Even if your request met one ore more of those requirements I will decide on my own if it will be added or not.
If you don't like that you're free to create your own ROM
On the roadmap the base of sediROM was planned as UCLJ3 but to be honest according to the thread poll () I will look into the base question before starting v3 again.
The poll result is clear: It has to be stable - I don't care about the base
So I'm free to decide I will look into the issues CM9 has and compare them with UCLJ3 and then I will decide which will be the base at the end.
If someone is willing to help - let me know your results, analysis!
sediROM BETA download area / file exchange
http://tinyurl.com/pv7utvl
(password protected - PM me to get access)

Great!!! :laugh: Downloading tonight! :fingers-crossed::fingers-crossed::fingers-crossed:

It's great to have so many choices for people to choose from
I've added this to the guide of course ;D People would love using this ROM because you can be close stock and have the stability of a custom ROM!
Also I would like to remind people if you cant post bugs in the dev section,post what ROM your using and bug in my thread so we can figure it from there

Waiting for the link:thumbup:
Sent from my HTC6435LVW using XDA Premium 4 mobile app

I believe sediROM's installer is the main show stopper atm.
but as now it is good enough to state as alpha because it is working fine in my tests (tested preseleted config only) and therefore if someone wants to help me - even when it is still a risc - write me a PM.
... and I cannot say it often enough:
DO A NANDROID BACKUP
COPY THAT BACKUP TO AN EXTERNAL DEVICE TOO !!!! --> SAVED MY DAY TODAY BECAUSE OF MD5 MISMATCHES THAT CAN HAPPEN..
ENSURE THAT YOUR BACKUP IS FULLY OK (e.g. md5sum -c nandroid.md5) in BOTH places (on the Glide on on your external ressource)
You should have a windows box running Odin + CWM6) near - just for the case. TWRP is not such bulletproof then CWM in my case..
regards
xdajog

This is great! Thank you all for the continuing support for our Glide!
Sometimes ancient is better when it was made with at least some support from the manufacturer. I'm still running GB based OsiMood as I haven't found a better alternative (because of Samsung's non-existant support for our great devs).

Yeah today I shot a used Cappy. That will be much easier for development when not needing to use my productive device. Will be here in 2 weeks..
Sent from my SGH-I927 using XDA Free mobile app

THat Rom can install in Roger?
Sorry My English Not good

joedeng said:
THat Rom can install in Roger?
Click to expand...
Click to collapse
yes it will work on Rogers variant, too. But I cannot recommend to use sediROM when you do not have good enough english skills to understand what you need to do in case of trouble.. You need to know how you can rescue your system in case of error or problems.
I wrote a very basic troubleshooting guide in the original post of this thread.
If you still want to try write me a PM and I provide you the download link to the current testing version (v1.0.18) of sediROM.
regards
xdajog

xdajog said:
yes it will work on Rogers variant, too. But I cannot recommend to use sediROM when you do not have good enough english skills to understand what you need to do in case of trouble.. You need to know how you can rescue your system in case of error or problems.
I wrote a very basic troubleshooting guide in the original post of this thread.
If you still want to try write me a PM and I provide you the download link to the current testing version (v1.0.18) of sediROM.
regards
xdajog
Click to expand...
Click to collapse
I do not generally write good English but I can understand. That the rom of your development from LiteRom v0.9 rom right? On the status bar has percent battery and 14 toggle it? If the trial is still okay, right? just as there were some errors when spending alone is not
p/s Finally i will try it, you get me your link, i will test it ^^

joedeng said:
I do not generally write good English but I can understand.
Click to expand...
Click to collapse
ok just wanted to be sure that you know what you're doing
That the rom of your development from LiteRom v0.9 rom right?
Click to expand...
Click to collapse
Yes it is based on LiteROM v0.9 as stated in the OP. (Well atm I'm currently re-thinking this and testing a complete new build on stock ICS instead of LiteROM).
On the status bar has percent battery and 14 toggle it?
Click to expand...
Click to collapse
yes to both
p/s Finally i will try it, you get me your link, i will test it ^^
Click to expand...
Click to collapse
You have a PM

Hey i have already install your rom. It awsome, but you can add some more app. Example click Volume Up or Down wake phone. Get some launcher LG, Samsung, Sony...More theme. recent app, status bar add slide brightness......

Today i have test, it can not share file via bluetooth...Stock ROm can do it. But Your Rom can not share file via Bluetooth....

joedeng said:
Today i have test, it can not share file via bluetooth...Stock ROm can do it. But Your Rom can not share file via Bluetooth....
Click to expand...
Click to collapse
From your device to another one or
from another one to your one or
in both direction?

Call for enhancements for sediROM v2
My idea for the upcoming version v2 is:
Keep as close as possible to Stock, fix known issues, remove bloatware and enhance it by features coming from apps - and not by re-compiling sensitive things like framework etc. The only reason for touching system components would be if that would fix something but not to add features into it. An example is the Quick settings bar which is not workin as expected in LiteROM. There are apps out there (e.g. a well configured Widgetsoid bar or one of the others) who can do the same but they do not touch system files. the sames goes to Bluetooth which seems to not working (as joedeng reported) like expected but it do work in Stock.
One another very important thing to mention:
I do not want to be a full-feature-blown-containing-everything-what-is-available-ROM!
upcoming v2 features/enhancements need to fulfill at least one of those:
Fixing a (real) bug or serious problem
Performance optimization
Battery optimization
System optimization or stability
So I hope you got the idea
So as I'm currently developing both directions it would be possible to hear your thoughts about that way.
This is your chance to be part of sediROM v2
So: If you have features you want to have or if know about issues within ICS STOCK Rom let me know!

Send me your link v2 in my box...Whay u don't post link down in top? I think your rom it good...