Related
!!This is ONLY for Elocity A7!!!
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
for the continued support or you can visit my homepage at Dexter's mods
I Thought this demo deserved to be posted with my Mod for ElocityA7
I get some creds here too , thanks!
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
Download ElocityMod v1.42 patch update
Download ElocityMod v1.41
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your own if it does FC alot, if you do not wipe
PATCHES
installs like regular full updates: rename to Update.zip and run recovery.
- v1.xx Adhoc patch here if you need connecting to mobile teetering app, it will not autostart wifi after sleep.
Previous releases
Download ElocityMod v1.3
Download ElocityMod v1.2
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
[/INDENT]
ISSUES
- Files manager app does FC too much, use the OI filemanager for local filehandling.
CHANGELOG
v1.42
- added latest 17-04 update from ElocityA7 update.
- Fixed sdcard problem, you can now eject/insert as much as wanted.
alternate patch is now removed.
v1.41
- build.prop (ro.kernel.android.checkjni=false) enables Skype to function (and maybe other apps)
- usb stick support added.
- changed sdcard handler to stock, but with exception it only work until you eject sdcard/usb , and a reboot is only way to remount (or restart vold daemon which is from a shell)
- honeycomb bootanimation added.
- Files app added (for copying network files to tablet) is buggy with pictures handling in folders. (might be removed again)
- VPN (script + vpn settings enabled/added)
- HDMI resolution changer added in settings (480p -> 1080p output available)v1.4
- Based on latest 24-02 update from Elocity.
- Cracked the sdcard issue, and its fully working now..
- Added patched hulu Flashplayer 10.2 (uninstall this one first, if you download it from market)
- New calendar appv1.3
- finally latest Market app included (2.2.7 will be upgraded to 2.2.11 when you enter market the first time)
- Added Gsensor fix, so screen rotation works, if playing games that need sensor like SpeedX or racing games..
- Added DSP audio manager with EQU function (does help increasing volume a little too)
- re-arranged process, so installers do not keep trying to install apps.v1.2
- Updated to latest stock of Feb-04 .
- removed wifi Settings again, solution did not work (im told)
- Fixed Calendar app FC.
- Updated Market to the latest release.
THANKS to all who donated up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
Reserved for future use..
This will be very helpful for a lot people. Great of you to put this together for everyone!
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
I look forward to seeing what else can happen with this device, and would be happy to test if needed.
DroidxRage said:
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
Click to expand...
Click to collapse
although its already in non-secure mode, the apps that run "su" dont recognise it, so the root app is required together with its "su" command.
and it actually also have the advantage of you being in control of which apps get root access..
although your "adb shell" is in a root shell, the apps running still has non-su rights to the system, otherwise its would be pretty open as well and without much security.
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Thanks Dexter, tossed a donation your way.
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
rich_e said:
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Click to expand...
Click to collapse
rich_e said:
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
Click to expand...
Click to collapse
I lost root access loading this rom too. It tried to update su but couldn't.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
Couldnt install the su zip file it put on my sd either..
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
rich_e said:
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
Click to expand...
Click to collapse
I cant see what the problem is... dex any ideas?
I may flash the offocial update, reinstall the modified build.prop, and reinstall market.
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
rich_e said:
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
DroidxRage said:
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
Click to expand...
Click to collapse
This didn't work... other than this superuser permissions being messed up everything else works stellar!
If we don't have anything soon, I'll flash back and poke around with the modified build.prop on the official build.
Edit: Reinstalled the official elocity update and got my root back, installed gapps, now updating build.prop. Hopefully this gets me all the market fixes minus that Su thing. Superuser app is available in the market too. Report back soon.
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
rich_e said:
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
Click to expand...
Click to collapse
Yeah pretty much!... did you not have the SU issues with version 1.0? If not I'll just update to that. I can't get Bank of America or Tasker to install even using the build.prop from the ROM, there's something other than the fingerprint in this ROM making the magic happen.
Titanium back up reports root access with V1.0 and I can get the # at the prompt in terminal. Lots of other apps that wouldn't install with the eLocity update install just fine with it too.
im a little confused..
i added the "su" command to the build, it never was there...
i added Superuser.apk as well.. and if you're trying to add those on top , you might corrupt it, and also,
VERY IMPORTANT filesystem has 0 bytes free, so any copying will probably corrupt the su command or other copied files..
Does this rom support ad-hoc wifi tether?
Requirements:
Follow the simple instructions here.
You MUST be rooted
You should be running a custom recovery like ClockWorkMod Recovery (CWM) or Team Win Recovery Project (TWRP). I use CWM, so this guide is based on that.
Your device must be using ARMv7 CPU architecture. If you aren't sure what that is, check this thread.
You must have a file explorer that has root permissions. I use ES File Explorer, so this guide is based on that.
You need at least 60MB of system space for the full offline installation. (30MB for online only version) If you don't know how to check, simply download Titanium Backup from the market. It tells you right on the main screen.
If you are not a noob and know what to do already, please skip this. The permissions are listed at the bottom for easy reference, should you need them.
INSTRUCTIONS:
- Download whichever zip you want. If you need to save /system space, download the the smaller, online-only package, otherwise get the normal one for the full experience. There is also a version of each which removes the "double-take" condition of the app. This is where it loads the results twice. The one that loads the results twice formats search results properly on the first try, but does not auto launch some cards. The non-double-take version may not format some search results properly, but auto launches tasks such as navigation and texting. Choose whichever one you prefer. If you have questions, please don't quote this entire post. Simply edit out the part you have a question about.
Update: Each version listed has the full version and the Offline only version. Pick the one you want and flash it. If you aren't sure which one to use, or if this is too much information or is otherwise overwhelming for you, just flash the M7 version - Offline/Online, since it's the latest. Be sure to scroll down a bit and read about it, though.
Before doing anything, you need to make sure you have at least 60MB of free space on your /system partition for Offline/Online files and 30MB of free /system space for Online Only files.
Flashable ZIPs
[*]M7 - mikeyxda's version 7. This version improves on M6 by tweaking notifications to be more accurate and frequent. This version may use more battery. If you are using a Sense ROM, see the troubleshooting below for a hack to improve Google Now performance and battery efficiency.
Online/Offline via Mediafire - 36.48MB /Hotfile mirror
Online Only via Mediafire - 14.06MB /Hotfile mirror
M7 Update - 3.97MB /Hotfile mirror
M7-Velvet.apk Only
[*]Inverted M7 - This is identical to the M7 files from above, except the colors are inverted, so that it has a black background instead of white, and white text instead of black. If you already have Google Now flashed, you can simply perform the update to this version.
Online/Offline via Mediafire - 36.81MB /Hotfile mirror
Online Only via Mediafire - 14.04MB /Hotfile mirror
Inverted M7 Update - 4.30MB /Hotfile mirror
M7inverted-Velvet.apk Only
[*]M6 - Mikeyxda's version 6. This version has improved on the previous one by fixing the double take problem, typed searches are working, auto launch is fixed, as well as the following fixes from the previous version: Red mic with cards showing with no refresh needed, no FCs, offline dictation, and no stretched words. These zips all use zipalligned apks.
Offline/Online via Mediafire - 36.43MB /Hotfile mirror
Online only via Mediafire - 14.01MB /Hotfile mirror
M6 Update - 3.92MB /Hotfile mirror
M6-Velvet.apk Only
[*]R3 - "Nearly there" version by ReekoTubbs. This version has the Red mic with cards showing with no refresh needed, no double take, no FCs, offline dictation, auto-launch, no blank screen, and no stretched words. These zips all use zipalligned apks.
Offline/Online via Mediafire - 36.48MB /Hotfile mirror
Online only via Mediafire - 14.07MB /Hotfile mirror
R3 Update - 3.97MB /Hotfile mirror
R3-Velvet.apk Only
How to:
- Move the file you picked to the root of your SD card. Don't put it in any folder. This just makes it easier to find.
- Reboot your device into recovery. See your device's specific instructions on how to do this if you are not sure. Google it for a faster answer.
- In CWM, navigate to "Install zip from SD" and select that.
- Next, highlight "Choose zip from SD card" and select it.
- Scroll down to the Google Now zip you loaded onto your SD card, then select it.
- Scroll down and select the option that says "Yes - Install Google Now....zip"
- Once it has flashed, go back to the main CWM menu and select "Reboot system now".
Double Checking:
- Let the ROM boot all the way, then fire up ES File Explorer (or whichever one you feel like using). We need to make sure a few permissions stuck (just in case).
- If you haven't used ES File Explorer before, open it, then hit menu.
Tap settings, then scroll all the way down.
Check the box that says "Up to Root" (pic).
Then check the box that says "Root Explorer"
Allow root access when the dialogue box for Superuser pops up.
After that, check off "Mount file system", then back out of the menu. (pic)
- Navigate to /system/usr/srec/ and find two folders named "config" and "en-US"
- Tap and hold on the "config" folder icon to bring up the options menu, then scroll down to Properties.
- Tap properties, then tap change and see if the check boxes match this picture.
- If it matches, leave it alone and head back to your home screen to enjoy using Google Now! If it doesn't match, change it so it does.
- Do the same thing for the "en-US" folder.
- Go into the settings menu for Google Now and set it up for your Google account and various other settings.
Now What?
So, you flashed Google Now. You're wondering what you can do with it, right? Well, thankfully, Killer-B has a handy little guide to get you up to speed on all the cool stuff Google Now can do as well as how to do it!
Commands & Now Cards For Google Now!!! Now Video, and custom widget
Troubleshooting
1.) The red mic screen won't display.
To fix this, press the normal mic within the Google Now app. While it is listening (after it beeps), press menu > refresh. Now you're at the red mic.
2.) Can't exit the Google Now app with the back button.
Use the Home button.
3.) Google Now Force Closes.
Make sure you have enough space on your /system partition before installing this. You need at least 60MB free for the Offline versions and 30MB free for the Online versions.
4.) Sports cards aren't showing up.
It won't add teams that aren't in season. American football is currently in preseason. Baseball, however, works perfectly fine.
5.) I want Google Now in another language than US English.
From the Google Now home screen with the cards, tap Menu, then Settings. Tap Voice, then Language and select the language you want recognized. The text of Google Now in searches and regular cards should mirror that of your system language.
6.) My phone exploded.
Have a muffin.
If, for some reason, you want to remove Google Now and return to how you were before, flash the following zip. It removes all Google Now files, and returns the original Google Search app and voice files, as well as sets permissions for the Search app.
Google Now to Google Search via Mediafire- 629.35KB /Hotfile mirror
Please don't thank me. Find one of these guys' posts and thank them. They made it happen, not me.
reekotubbs, MikeyXda, Lenny_kano
all credit goes to this thread: http://forum.xda-developers.com/showpost.php?p=29756226&postcount=2856
this app uses many battery? do you know?
not too much for me
I recommended using R3 by Reekotubbs offline version
is the voice search working?
if yes i would like to try
if this is running in the background??
if you don't need the service, just turn off the google now. remember to make a nandroid backup first
updated post.
please give thanks to real developer as I just sharing their guide and works
foid said:
is the voice search working?
if yes i would like to try
Click to expand...
Click to collapse
Yes its working flawlessly
riztdroid said:
if this is running in the background??
Click to expand...
Click to collapse
Yes, but you can disabled it for saving juice
Sent from my GT-I8150 using Tapatalk 2
Any more mirrors? both deleted.
Thanks
Updated link and inverted google now
if you flash adrenolibs v3 google now will more smooth and will having less issue and lags (the one I encounter before)
How to remove it? The link given is not working...
Sent from my GT-I8150 using xda app-developers app
how can i disable it for a moment i don't want to use it? just disable it on the apps settings / freeze it?
@hotheabilly
which version do you prefer?
what version are you using?
what is the update?
google now remover link is updated
test R3 version, it does good.
Google Now work flawless with CM9 by arco or Paranoid by doomsday
thanks for sharing
Yes Yes yessssss its working now
I tried the 1st link Online/Offline via Mediafire - 36.48MB /Hotfile mirror
Thanks Dude
hotheabilly said:
google now remover link is updated
test R3 version, it does good.
Click to expand...
Click to collapse
thanks.. but I mean is the "updateM7.zip" or others.. I downloaded it and there's a /system/app/velvet.apk what for it is? update for the M7?
In flashable zip contains velvet apk (google now itself) and many libs for it.
Sent from my GT-I8150 using Tapatalk 2
I think R3 (update) is not different with M7 (not updated), I always refresh to show more card and stuck on white screen, I flashed M7 2 weeks ago before R3 (from original thread)
and R3 I've got FC everytime I launched the app, so revert back to M7 + updated
thanks for sharing mate
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
Device and OS: SGS3 AT&T (SGH-I747) 4.1.2.
Goal : Cancel the pending OTA update and its notification; prevent future OTA updates and notifications.
Assumptions: You've seen galaxys3root.com how-to-root-u-s-and-canada-galaxy fail-proofnoob-proof (Newbie here so can't yet post the outside link.)
This companion post simply collects the information into one place and optimizes the sequence of steps, instead of reading a whole disjointed thread, which I could not even find again anyway.
Phase 0 - Prep.
- Back up your data.
- Download the necessary files.
Phase 1 - Root the device.
- Connect via USB.
- Use Windows to copy SuperUser.ZIP onto device.
- Boot into download mode (Vulcan death grip with volume down).
- Use Odin to copy RecoveryGalaxyS3USCanada.TAR onto device.
- Disconnect USB.
- Boot into recovery mode (Vulcan death grip with volume up); the new loader launches.
- Install Chainfire's SuperSU (it's inside SuperUser.ZIP).
- Reboot normally.
Phase 2 - Stop OTA updates.
- Using Root Browser:
- Delete the one file in /cache/fota/.
- Rename /etc/security/otacerts.zip to otacerts-zip.bak.
- Add write-permissions on /system and /system/app (really not sure this is necessary).
- Copy FOTAKill.apk to /system/app.
- Rename /system/app/FWUpgrade.apk to FWUpgrade-apk.bak
- Reboot.
- Notification page may still say "New update postponed" (it does not swipe away).
- WAIT until the current postponement expires.
Now the notification is gone!
I feel like there may be one rename that I forgot, but it's listed around here somewhere.
Seemingly spurious information:
- Titanium Backup requiring Lucky Patcher requiring BusyBox; that whole stack failed so not used.
- Remounting /system using a terminal failed.
Wow.
A much easier way if you' ve obtained root would be to uninstall and reinstall titanium backup, click on backup/restore, then go down to where it says AT&T software update (or whatever it's called) click on it, then click uninstall. You will never receive any update notifications again.
Also, if you've already installed the recovery, the update will fail if you let one go through, so you don't need to do anything else to block updates after flashing that .tar file.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
uninstall and reinstall titanium backup, then uninstall AT&T software update (or whatever it's called). You will never receive any update notifications again.
Click to expand...
Click to collapse
I first tried using TiBu to freeze AT&T software update, but it was failing for some reason, so I scrapped that approach.
I want to be able to accept OTA later, just not now, so not ready to completely uninstall anything.
if you've installed the recovery, the update will fail if you let one go through
Click to expand...
Click to collapse
Looks like that's what happened this morning.
Thanks for the clarify, this makes sense now that I have been through the process by overdoing it :fingers-crossed:
This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.
CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?
Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.
Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.
Iloveyou and thanks for that guide I've made my first succeded rom install ever
MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:
Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.
Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.
Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.