Tuesday, October 21, 2014

MY NEW BANNER!!!!!!!

LOL!!!

Thursday, May 22, 2014

[GUIDE] [HOW TO] Change Package Names of Android Apps

I’ve Seen A Lot of People around Here and Other Forums who wants to know how to change the Package Name of Android Apps (Ex. com.xvipre.settings to com.modded.app) !! But some of them can’t really do it because of proper Programming Skills and Development Knowledge!

So today I will show you how to do it! Without Programming Skills or Extra Development!

Caution: Only use this if the App is Open-Source and ask for Developer Rights before doing this! I and XDA do not support Piracy! So don’t try to ruin Humanity by doing Piracy of Apps!

So This shall be Only Used for Learning and Development Purposes!

Requirements:

· A Brain

· Apktool

· An APK to Work With!

· PC/Android Device

· DroidEdit/Notepad++

· A Little Knowledge in DroidEdit or Notepad++

Now Let’s Start—

At First Decompile your APK using a Suitable and comfortable apktool. Use Apk-Multitool/Virtuous or other Tools.

As you can see there are 2 files and 2 Folders inside Decompiled XVipreSetting.apk Folder.

└── XVipreSettings.apk

├── AndroidManifest.xml

├── apktool.yml

├── res

└── smali

Lets assume that our APK Information is like this—

APK Name: XVipreSettings.apk

APK Package Name: com.xvipre.settings

We’ll Change it to the following—

APK Name: ModdedApp.apk

APK Package Name: com.modded.app

Before you begin, Let me tell you that all the modification done in this Project are Imaginary!

You have to assume that the package is com.xvipre.settings but actually it’s different for each app in the world! So you must know about what you are going to do, and what all these means!

It’s just an example! You have to use your app’s package and your desired app package name! Or Else it won’t Work at all!

Now Open apktool.yml and Search for these lines--

apkFileName: XVipreSettings.apk

And

packageInfo:

cur_package: com.xvipre.settings

orig_package: com.xvipre.settings

Now Edit the Package Name and APK Name as You Desire—

For Example:

apkFileName: ModdedApp.apk

And

packageInfo:

cur_package: com.modded.app

orig_package: com.modded.app

Save the File and Close apktool.yml

Now Open AndroidManifest.xml and Look for these lines—

<manifest android:hasCode="false" android:versionCode="14" android:versionName="2.1" android:installLocation="internalOnly" package="com.xvipre.settings"

Now Edit the Package name here—

For Example:

<manifest android:hasCode="false" android:versionCode="14" android:versionName="2.1" android:installLocation="internalOnly" package="com.modded.app"

Save and Exit.

Now Navigate to /smali/com/xvipre and Do the Following

· Rename settings to app

· Go Back to /smali/com Folder and Rename xvipre to modded

Now It’s Time to Go Hardcore!!

Open Notepad++ And Press Ctrl+F to Open “Find”

Click on Find in Files

Now in Directory, Click on “Browse” or “…”

Now Navigate to your Working Folder and Select /smali/

Now Click on Find What: and Type Your Package Name! But Like This—

Lcom/xvipre/settings

Click on Replace With: and Type Your Desired Package name—

For Example:

Lcom/modded/app

Click on Replace in Files

Now It Shall take up to 1-2 Minutes to Find and Replace all the package names in smalis!

When Done, Just Re-Check All the Files, Folder Names, Recheck AndroidManifest.xml to Find Another Line with Package name And Make Corrections Yourself!

Done for Now! Just Re-Compile and *SIGN* your Newly Created APK!!

Install the APK as User App! See if it Worked! :D

If you Like my Guide… Just Leave a little Thanks! :) :)

Comment if this guide has mistakes or I said anything Wrong, About Errors or Suggestions!

Written by Xtreme Ornob

Official Developer of XVipre ™

Thanks to

Google Inc.

XDA-Developers.

Mushfiqus Salehin (For giving me the Title of “Debeloper Sab” in Bangladeshi Groups)

Everyone Hail to Sadia Afrin Rumu for Teaching me the Usage of Android And Facebook Groups.

She’s an idol to me as she made me realize that I am a “Dim” and also a “Choto Pola”

Monday, March 31, 2014

GUIDE / TUTORIAL ...

HOW to Port ROMs...

For Begineers & Advanced Users

Almost Any Device to Any Device!

ONLY FOR MEDIATEK SoCs

In This Guide You'll Learn..

How to Port ROMs From the Same CPU

And Also..

HOW TO PORT ROM FROM A DIFFERENT SoC!!!!!

Works for-

MT6589 to MT6577

MT6582 to MT6572

MT6577 to MT6575

Only ICS to ICS & JB to JB

May also work with 4.1 to 4.2

No Need of Source Code

No Need of Kernel Source

No Need of **ANDROID KITCHEN

No Need of LINUX... :D

Requirements:

* A Brain
* Patience
* Windows XP/7/8
* 7-Zip
* Notepad++
* Bootimg Unpack/Repack Tools for Windows!
* Stock ROM
* And a Little Respect!!

So now Lets Begin...

PORTING For Same SoCs ( Ex: MT6572 to MT6572)

* Replace these from your Stock ROM to the ROM u want to PORT!! Lets Call it "PORT"

FILE LIST FOR REPLACING:

*system/vendor
*system/usr
*system/lib/modules
*system/lib/hw
*system/lib/libncurses.so
*system/etc/firmware
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
*system/etc/bluetooth

For Fixing Problems...

*system/etc/permissions
*system/etc/security
*system/etc/audio
*system/etc/wifi
*system/lib/drm
*system/lib/egl
*system/lib/soundfx

* Now Replace the Stock Boot.img to Port ROM!

* Now Open The Port ROM folder and go to META-INF/google/android and open updater-script in Notepad++

* Do the same for the Stock ROM

* Now In the Port ROM's Updater Script, find a line that starts with this...

format(".......

and only replace the mmcblk0p.. with the stock one!

* Do the same for this line...

mount("...

Example:

This is the PORT one!!!

format("ext4", "EMMC", "/dev/block/mmcblk0p5", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");

This is the Stock one!!

format("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");

Now just Replace the "mmcblk0p3" from STOCK to PORT!!

It should look like this:

format("ext4", "EMMC", "/dev/block/mmcblk0p3", "0", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/system");

DO NOT REPLACE THE WHOLE LINE!

* Now go back to the Folder of Port ROM and You'll see 2 folders & 1 file named

-META-INF
-system
-boot.img

* Now Select these three and Click Right Mouse Button and Click on 7-Zip ->> Add to Archive

* Now a dialouge box should appear!

* Configure the Format like This:

Archive format: ZIP

Compression Level : Normal

Compression Method: Deflate

Dictoioany Size: 32k

Word Size 32

* Now Start Zipping and Push the ZIP to your Memory Card

* Go to Recovery >> Install ZIP & Wipe Data

Finished!!

Now was that so hard?? Its a Really Easy thing to d0!!

Now Come to the Hard Part!!

Porting From Different SoCs ( Ex: MT6582 to MT7572 )

Read this carefully & apply the way i say!

* Take the ROM u want to port & name it PORT!
* Take your Stock ROM & Name it Stock
* Now Replace These files from Stock to PORT--

*system/vendor
*system/usr
*system/lib/modules
*system/lib/hw
*system/lib/libncurses.so
*system/etc/firmware
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
*system/etc/bluetooth

* Now Open build.prop in notepad++ & Search for this line

ro.mediatek.platform=MT65xx

Now Replace this (MT65xx) with your CPU!!

For Example

ro.mediatek.platform=MT6575

* Now Go To META-INF/google/android and open updater-script in notepad++

* Add this line between the lines of "set_perm"

set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt65xx.so");

[Replace the mt65xx with your cpu]

Example:

set_perm(0, 0, 0644, "/system/vendor/lib/hw/gralloc.mt6572.so");

* Now Go back to the Rom folder and Take the boot.img and decompile it with any bootimg-unpack tool!

* Now delete the zimage and rename boot.img-ramdisk to PORT-Ramdisk

* Now Do the Same for Stock boot.img and open the folder named PORT-ramdisk and copy all the files from PORT-ramdisk to boot.img-ramdisk of your Stock boot.img

* Now Go to boot.img-ramdisk and open init.rc

* Now find these lines and replace with your cpu
#Create Chip Property
on early_property:ro.hardware=mt6582
setprop ro.mtk.hardware mt6589

on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6589

example :

#Create Chip Property
on early_property:ro.hardware=mt6582
setprop ro.mtk.hardware mt6572

on early_property:ro.hardware=mt6589
setprop ro.mtk.hardware mt6572

* Now Compile your New boot.img and Pack your New ROM and Flash!!

Cheers!!!!

Porting Lewa OS5 ROM:

* Replace These files from Stock to LeWa OS5 ROM

*system/vendor
*system/usr
*system/lib/modules
*system/lib/hw
*system/etc/firmware
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
*system/etc/bluetooth

* Replace Stock boot.img to Lewa OS5 ROM

* Unpack boot.img

* Open init.rc

* Find these lines

on early_property:ro.build.type=user
write /proc/bootprof "INIT: user build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

on early_property:ro.build.type=userdebug
write /proc/bootprof "INIT: userdebug build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

on early_property:ro.build.type=eng
write /proc/bootprof "INIT: eng build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar

* Now Add this line in the end of 1t and 3rd line

:/system/framework/lewa-framework.jar

Example:

on early_property:ro.build.type=user
write /proc/bootprof "INIT: user build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/lewa-framework.jar

on early_property:ro.build.type=userdebug
write /proc/bootprof "INIT: userdebug build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

on early_property:ro.build.type=eng
write /proc/bootprof "INIT: eng build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar:/system/framework/lewa-framework.jar

* Now Compile the new boot.img and Repack your New Lewa OS5 ROM

Porting MiUI ROM

Replace These files from Stock to MiUI ROM

*system/vendor
*system/usr
*system/lib/modules
*system/lib/hw
*system/etc/firmware
*system/etc/vold.fstab
*system/etc/vold.fstab.nand
*system/etc/bluetooth

* Replace Stock boot.img to Lewa OS5 ROM

* Unpack boot.img
* Open init.rc
* Find these lines

on early_property:ro.build.type=user
write /proc/bootprof "INIT: user build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

on early_property:ro.build.type=userdebug
write /proc/bootprof "INIT: userdebug build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar

on early_property:ro.build.type=eng
write /proc/bootprof "INIT: eng build setting"
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/telephony-common.jar:/system/framework/mms-common.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/mediatek-common.jar:/system/framework/mediatek-framework.jar:/system/framework/secondary-framework.jar:/system/framework/CustomProperties.jar:/system/framework/mediatek-telephony-common.jar:/system/framework/mediatek-op.jar:/system/framework/emma.jar

* Do the Same as Lewa and add this line in the end of 1st and 3rd line.

:/system/framework/miui-framework.jar

* Compile the New Boot.img and Repack your new ROM and FLash!!

Cheers!!

Enjoy your New ROM and Give Credits to me for if I Helped you! ;)

For Advanced Users:

PORTING FIX:

Framework:

* decompile framework.jar

* Go to

\smali\com\mediatek

* Replace All Files from STOCK to this Folder

* Now go to

\smali\com\android\server

* Replace All Files from STOCK to this Folder

* Compile framework.jar and Push to Device!

* This Should FIX Bootloop, Mms.apk, Phone.apk, Settings.apk, Contacts.apk Force Close

* Fixing Other Problems:

Files related to Specific hardware:

* Replace if Not Working!!

* Camrea:

\system\lib\libcamalgo.so
\system\lib\libmhaldrv.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so

* GPS:

/system/xbin/libmnlp

* Bluetooth & Wifi:

/system/lib/libbluetooth_mtk.so
/system/lib/libbluetoothem_mtk.so

* Radio:

\system\lib\libaudio.a2dp.default.so
\system\lib\libaudio.primary.default.so
\system\lib\libaudiocompensationfilter.so
\system\lib\libaudiocustparam.so
\system\lib\libaudioeffect_jni.so
\system\lib\libaudioflinger.so
\system\lib\libaudiosetting.so
\system\lib\libfmar1000.so
\system\lib\libfmcust.so
\system\lib\libfmjni.so
\system\lib\libfmmt6616.so
\system\lib\libfmmt6620.so
\system\lib\libfmmt6626.so
\system\lib\libfmmt6628.so

* For Fixing Wifi & FM-Radio do this!

(NOT NEEDED IN MT6572)

fmradio.driver.chip=1

(Change it to 3 if yours is MT6628)

mediatek.wlan.chip=MT6620

(Replace mediatek.wlan.chip=MT6620 to your WLAM Chip Type Ex: mediatek.wlan.chip=MT6628 for MT6628)

mediatek.wlan.module.postfix=_mt6620

(Replace mediatek.wlan.module.postfix=_mt6620 to your WLAM Chip Type Ex: mediatek.wlan.module.postfix=_mt6628 for MT6628)

* Now open updater-script and Find this line or ADD a New one(If Not Found)!!

symlink("wlan_mt6620.ko", "/system/lib/modules/wlan.ko")

(Replace wlan_mt6620.ko to your WLAM Chip Type Ex: wlan_mt6628.ko for MT6628)

It Took Me 2Days & 5 Hours to Collect Data & Write this Thing!
I didn't Eat or Drink Water Properly,I Didn't Sleep Properly,
I Created This just for you all!
So That No ONE Ever Says Modontek Again! Its Against Humanity!
Please Value my Work & Do Not Blame me if it Doesnt Work!
I Work Day & Night to Learn More & More!
I Respect All the Developers & Modders of Android
But Some Jerks Just Dont know How to Behave like a Human!
Some Developers Behave like they are the BEST! LOL!
But It's NOT TRUE!
We Can't Be the Best! We Are All the Same!
We all are the Students of XDA-University!
We all use Others Work!
Why Not Work together? Why Not Develop our Knowledge More & More!??
I Don't think I Own any Respect from anyone!
But I Think I Own Respect for my Works & Contributions to Andoid Open Source Project!
I Believe in Humanity! Please Do NOT Copy This and Take Credits!
If This Was Helpful to you in Any Way...
Just Mention my Name in your ROM and Give me Some Credits!

Written by Xtreme Ornob

Official Developer of XVipre™

Coming Soon: Creating Your Own ROMs, Integrating ROM Info & Developer Info into ROM

Sorry for my BAD ENGLISH!! :P :P

Like my Page: XVipre ROM

Officially Released on Facebook Group

WALTON Primo F2 Solutions & Devs

Tuesday, March 11, 2014

SIMPLE Theory About Android ROMs

This one is for some ROM freaks

>>Android ROMs (System Core)

Now-a-days....

We find a lot of Custom ROMs, Stock Based ROMs for our Android Smartphones!

But Most of us Do Not Admire others Works &
We Try to steal others works without knowing
who the developer is of that ROM !!
But its not about that!
I Just Wanna tell u guys something...

What is ROM???

Answer: ROM = Read Only Memory!
This Acctual ROM was discovered for advanced
computing systems & some solutions on
memory devices! It could only READ data out
of the desired object!
Now...

What is RAM??

RAM = Random Access Memory!
Used as the Primary Memory, CPU controlled
Devices to store data & later move them
somewhere to keep the files / data!

Now we know What is what!

So Now Let me Explain to you About Our
Android Devices

There is ROM and also RAM Availabe in all
types of androids!
The ROM used in these ARM devices are
mainly The Core Bundle of Softwares that run
the Android System! And these ROMs were
Supposed to be Read-Only!
But there's Root!! So we Root our Androids
to gain access to the System Files & do
dancing with them!
Like Setting up Custom Recoveries!
Do some Modifications...
And After that! We Finally Install A CUSTOM
ROM!!!!
Now a Custom ROM is a modified, Themed,
Patched Up System!
So Now the Rule is Broken! ROM isnt a ROM
afterall!
It Wasnt enough for us!
NOW we Format our ROM & Install New ROMs
Everyday!
We get it out of one device & play with it &
put it in another device! Cool huh?
Sounds Easy?
Try it baby! So now that we know that we
use these ROMs like Music, Videos, Total Data
& Such thing,
It has turned into a RAM !!!!
It Stores Data, Removes It, Stores Data from
another Device, Moves Data from here to there!
And does much more than that! Just like RAM!
Right??
Why do we call it ROM?? We Should start
Calling it RAM instead!
The day is not far when Google will confirm it
being RAM & Unlock the Devices without
Requiring ROOT so that we can install
THOUSANDS OF ROMs Everyday! And Blow
Up Our Devices!

R. I. P Google's Android System!

--Xtreme Ornob'$ TheØrY

Saturday, March 8, 2014

The Tru-Q-Mod V1.0 (XVipre™)

The Tru-Q-Mod V1.0 (XVipre™)
======================

by Xtreme Ornob

A Total Package for Shifting Any ROM into

Full-Gear!
for 4.1.x, 4.2.x, 4.3.x (kernel 3.4.0+)

* More Clear Sound
* More Bass
* More Audio Volume (Boosted)
* Reverb, Virtual Effects
* Updated Graphics Drivers
* Added Custom GPU libs
* More Clear Overall Graphics
* Improved Picture Quality
* Improved Video Playback Quality
* Improved Display Contrast
* Improved Display Colors
* Call Audio Fix
* Recording Volume Increased
* Sound Recording Quality Improved
* Fixed Overall Display Quality
* Added X-Clean (XVipre™) Script
* More Free RAM
* RAM, CACHE Optimized!
* Cleans Upto 300mb of Cached Apps RAM Usage!
* 0-Lag Fixes
* Added Advanced Governor Tweaks
* Added IO Tweaks
* Added Full ext4 Overdrive (file system speed boost)
* CPU More Powerful
* CPU More Power Consuming
* GPU More Power Consuming
* More GPU Response
* GPU Usage Over Full UI
* CPU Sleep State SuperSleeper ( XVipre™)
* Modded MusicFX
* Modded AudioEffectService.apk
* Added Dobly Surround!
* Added SysCtl Controls
* Added Init.d Script Support for Any ROM
* Added CrossBreeder, Adreline Scripts
* Added Lite Minfree Controls
* Added Tru-Q-XVipre-Mod Advanced Scripts
* Added Sony HW libs
* Camera Quality Increased!
* Zoom Fixed
* More Powerful Flash
* More Speedy File Access & Thumb Preview
* Specially Built for Mediatek SoCs
* Boot-up Time Speedup
* Boosted File System Read/Write
* Boosted Overall CPU, GPU, OOM, STORAGE
* Fixed Several Lags on mediatek devices
* Fixed UI Lags
* Almost All HD Games Supported Without Lags!
* Super Fluid Lagfree Experience in UI, Launcher, Apps, Games, Video Playback, Audio
* More Responsive Touch!
* More Multitasking
* Zipaligns Every APK on installation
* Zipalign Every APK After Every 5days.
* Optimize SQLite Database Every 5days.
* More Battery Backup
* Battery Consuming libs
* Added XVipre™ Official Bootanimation, Shutanimation, Boot Sound, Shut Sound
* No Auto Close Apps
* Super RAM Management
* Added sqlite3, haveged, tune2fs

Screenshots:

Link: MediaFire

Instructions:

* Reboot Into Recovery

* Install ZIP

*Reboot

* Install Terminal Emulator from Google Play Store

* Type "su" and Press Enter

* Click "Grant" to Get Root Access

* Type "xclean" and Press

You will see that it is cleaning your overall memory!

Enjoy Your Freedom!

_=_=_=_=_=_=_=_=_=_=_=_=

All Used Scripts, Apps, Mods

- AwesomeBeats (Modded)
- Bravia Engine 3
- xReality Rngine (Modded)
- xLoud Audio Enhancement (Modded)
- Some of ClearAudio+ features
- CrossBreeder
- Blended Graphics Drivers & Audio
- V6 SuperCharger
- X-Beats
- X-Clean
- GovernorX
- XVipre™ Scripts, Modded Apps
- XVipre™ Platlogo

|_|__|_|__|_|__|_|__|_|__|_|__|_|__|_|__|_|__|
===============================

All features Combined by Xtreme Ornob

Specially made for XVipre™ (W35, F2, G1)

Officially Released on facebook group

Walton Primo F2 Devs & Solutions

XVipre™ , Tru-Q-Mod, X-Beats , X-Clean, GovernorX
---------------------------------------------------------

Officially Developed by Xtreme Ornob

Thanks to

Wasik Jahan Eshan

Groups:

Symphony Xplorer W35

Walton Primo F2 Devs & Solutions