Access all apps from market - XPERIA X10 General

I'm not responsible if your phone crashes, bricks, vanishes or display Apple logos, or if you buy apps you can't use because "wrong version".
Also, experimental tweak, don't expect miracles - It is useful for developpers and curious guys ^^
Okay guys, here is a very easy tweak to allow you to display/install (NOT use, most won't work) all apps from Market (your version and all upper), just add the stuff I give below and you're ready to go
What you need : rooted phone, Android (1.6, 2.x.y, 3.x... Stock or not)
File to edit : /system/build.prop
How to edit : Root explorer
How long : 5 minutes (edit, reboot, try)
** Make a backup of your build.prop !!!!!! (Root Explorer will do it automatically) **
1. Root Explorer > Go to /System/ > Long press build.prop and click Open in Text Editor
2. Find the line :
Code:
ro.build.version.sdk=7
Simply edit the value (API Level) according to what you want to display.
Code:
API Level = 7 >> Android 2.1 (Default)
API Level = 8 >> Android 2.2
API Level = 9 >> Android 2.3
API Level = 10 >> Android 2.3.3
API Level = 11 >> Android 3.0
Save and check backup is created, then reboot and try searching apps you usually can't access (ie. for Android 2.1 : Flash Player)
What it will do :
* Display & install apps for your current Android version AND upper versions (ie. if you set API Level to 9, you will see apps for Android 2.1 + 2.2 + 2.3). Dunno if you can display previous versions, but you can try levels 3,4...
* Allow you to get .apk directly from Market (install, then copy apk with Root Explorer)
What it will not do :
* Make the downloaded/installed apps of other versions to work. The apk will come with no icon, service name and will probably crash when you'll try to run it - You can try to patch it with APK Manager. So do not buy apps, you will probably won't be able to use them ! (Check also the version, Market will NOT warn you about the app's API Level)
Hope this will help people to port .apk files from other versions to our old 2.1...

what about device fingerprint?

DooMLoRD said:
what about device fingerprint?
Click to expand...
Click to collapse
I haven't tried, but there are also several strings you can edit in the build.prop... Those *should* allow to change fingerprint.

Related

Noob's Guide to a Droid X

Welcome to the Droid X guide! I hope to expand up on this as much as possible, so be sure to check back for updates!
The Benefits of rooting
So why root your android phone? Well, there are several benefits... First, you can backup up your phones current state whenever you would like (makes is easy to jump back and forth if you mess things up!). In addition, you can also install different themes (different color interfaces for the basic framework and applications). You can also install custom ROMs (this is an Android OS that has been built from either Motorola's source, or the Google SDK and released through their generosity for the rest of us to enjoy!
Rooting: Many people are unsure of rooting their phones but have heard of other people doing it. Here is my stance on rooting your phone:
If you are technically savvy, or can follow instructions well and have confidence in your ability to do so, I would definitely recommend it! If you are unsure of your abilities to do so, and simply use your Droid X because it is a great phone right out of the box, then I would recommend reading through this guide and some other threads on the Droid X forums so you can familiarize yourself with the potential possibilities and process' involved with rooting and customizing your phone. I do not say any of this to deter anyone from wanting to root their phone, it just can be a dangerous situation for those who are not familiar with how it could potentially damage their phone.
I have seen many ask about the dangers of rooting. First off, yes it will void your warranty, but you CAN unroot your phone. I will include this information later =)
#1 rule of modding your phone: ALWAYS TAKE A BACKUP BEFORE MAKING ANY MODIFICATIONS!
with that said... let's continue =)
Rooting: Just because you have a rooted phone, does not explicitly open up new features on your phone.... What it does do, is open up the possibility for features on your phone =) Keep reading...
Themes: In order to theme your phone, you first have to deodex it. If you attempt to theme the phone without deodexing it, you can run into issues... Themes allow you to change the look of the phone framework and applications (e.g. different colors or images). Make sure to follow rule #1, and then follow any specific instructions that the creator of the theme may have included with their post.
Droid X Bootstrap: This is the saving grace for the Droid X created by Koush. Installing this application once rooted allows you to create backups, restore backups and install custom themes, ROM's, and other modifications that have been made into flashable zip format. I will explain how to use this later as well.
Custom ROMs: Custom ROM's are a developers build of the android operating system either using the Motorola ROM as their base, or building directly from Google's SDK. Many of the ROM's for the Droid X are "blur-free" which means that they look like a generic android OS install the way Google intended it. The default "ROM" that comes on your phone has what is known as "blur" by Motorola. It is just graphical enhancements to the way the phone operates that mostly tie into social networking applications and widgets. Many Android enthusiasts believe that Motorola Blur or HTC Sense ruins the Android feel. Whether or not to use a blurred or blur-free ROM is really up to you and how you like your phone to look and feel.
I will cover more about ROM's later in my posts and try to give an overall description of each. As usual, before trying to flash any ROM, be sure to backup your phone.
Overclocking your phone: Overclocking for those who do not already know what this means, is basically the ability to tell your phone's processor to run at a higher speed. This basically just improves performance on your phone, but can be harder on the phone as well. By telling the phone run at a faster processor speed, you can decrease the battery life of your phone. The droid X overclocks in a different manner than with most Android phones, due to the inability to run custom kernels on the Droid X.
For those who are not familiar with the potential of overclocking your phone, I highly recommend not doing it. While rooting can be dangerous, if you mess up overclock settings on your phone, you can do more harm than good.
So I have seen a bunch of people asking questions that seem to pop up repeatedly on the forums... I plan on adding to this as i put this guide together for a few people who really needed more step by step instructions to get going. Feel free to suggest stuff for me to add, and I will throw it in.
Thanks, and enjoy the following:
Ok, here are the steps for setting up the sdk, getting rooted, and all that good stuff... have a feeling I will be making this into a new thread...perhaps....
SDK:
First off... you will want to go to the following site to download the sdk:
http://developer.android.com/sdk/index.html
Grab the following download: android-sdk_r08-windows.zip
I saved it to C:\sdk (i created a folder called SDK right at the root of C: drive). When it finishes, unzip this using 7zip (or any other unzip program you like) to the sdk folder. When it is finished unzipping, you should have a folder called "android-sdk_r10-windows". If you open up that folder, you will find a folder called "android-sdk-windows". Open this folder up and double click on the "SDK Manager.exe". This will open up a window, and bring up additional windows, one of which will ask you to "choose packages to install". You can download any or all of them. I recommend downloading the following: (NOTE: this may have changed as I don't recall the API versions for sdk r10)
• Android SDK Platform-tools, revision 1 (the top-most download)
• SDK Platform Android 2.3, API 9, revision 1
• SDK Platform Android 2.2, API 8, revision 2
• USB drivers (I don't think this shows up in the latest version of the sdk's first download window. I believe it is found if you go to the available packages section the "Android SDK and AVD Manager and expand the 3rd party section....but if you happen to see it in there...grab it)
This should be sufficient for now. All packages are accepted by default. If you do not wish to download all of them, simply highlight each one (one at a time) and then click the reject button towards the bottom middle of the window. When you have selected the packages you wish to download, click the install button.
After this has installed, you now have the Android SDK installed on your machine. You can close all windows related to the SDK, as we don't actually need to do anything with it, it simply has tools within it that we will need later. (This is where the adb command originates from. There is an adb.exe tool in the "platform-tools" folder of the sdk install, but we will get to this later).
Now you will want to go to your desktop (or anywhere you have a shortcut or icon for My Computer), right click on My Computer, and select properties. Under the "advanced" tab of the window that opens, you should see a button at the bottom that says "environment variables". Click on this, and then find the "Path" variable under System Variables NOT user variables. Click Edit and go to the end of the "Variable Value" field. You will want to make sure there is a semicolon ";" at the end of this before typing any additional info. You will want to add the full path of your android SDK install. For example, if you followed my example for download/saving/extracting/installing above, you would type the following information into the end of the "Variable Value" section:
C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools
If you installed to another location, be sure to type the correct path to the "tools" folder within your installation of the Android SDK. Then click the OK button, and close any windows that were opened from adding to the "path variable".
Droid X Drivers
This section is a little more difficult to explain, as there are so many variables depending on what operating system you are running (windows XP, Windows Vista, Windows 7, etc). and whether or not you are running a 32-bit or 64-bit instance of your chosen Operating system.
Here is one link for Droid X drivers:
http://www.verizon-phones.org/verizon-motorola-droid-x-usb-drivers-pc-charging-drivers-download.html
I simply googled Droid X drivers, I'm sure this isn't the best link, but just for example I'm throwing it out there. If you google Droid X USB drivers you should be able to find the drivers you need, as well as help and instructions on how to get everything working.
Once you get the usb drivers installed, you will want to connect your Droid X to your computer. If it is recognized, you will get a notification in your drop down bar on your phone. On your phone, press on the USB connection in the drop down menu, and select "charge only". Next, open up a command prompt on your computer. Type the following in and hit enter:
adb devices
You should see something simiilar to the following come up if everything is configured correctly:
C:\>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015A882315005010 device
If you see something similar to what I have above... then ADB is working correctly, and we can continue! Now we will move on to getting your device rooted! You will want to grab the z4root.apk that I have attached earlier in this thread and download it onto your computer. We will now test out if adb is indeed working! Save the z4root.1.3.0.apk and put it in the "tools" folder of the sdk we downloaded earlier. Now open up a new command prompt (or use the one we opened earlier if you haven't already closed it!) Change directories to the "tools" folder of the sdk:
If you installed the SDK where I used in my example.... type the following:
cd C:\sdk\android-sdk_r10-windows\android-sdk-windows\platform-tools (press enter)
type the following: adb install z4root.1.3.0.apk (press enter)
You should now see the following:
C:\android-sdk-windows\tools>adb install z4root.1.3.0.apk
1833 KB/s (978414 bytes in 0.521s)
pkg: /data/local/tmp/z4root.1.3.0.apk
Success
z4root and ROOTING
If you get all of this, you have now installed a package using adb and we know the interface works. If you don't want to have to mess with this method of installing, you could also download "Astro File Manager" from the android market. You would then need to save z4root.apk to your sdcard of your Droid X. Then open the Astro program and browse to your SDcard and file the z4root.1.3.0.apk. Press on the .apk file and it should come up with a box that says something similar to "open with app installer" or "app manager"... don't recall exactly what it says, but should be something similar to package management or install of some sort. After pressing on that, you should see an install button. Press on that to install z4root.
Now that z4root is installed, you will want to go to your application list on your phone and press on the z4root to open the application. Press on the permanent root button and wait! This process may take a while, and your phone will reboot, but when it does, you are now rooted.
Make sure when trying to root your phone that you go into Settings-->Applications-->Development make sure "usb bebugging" is enabled.
Removing BOOTSTRAP COMPLETELY (You only need to follow these steps if you WANT to remove Droid X bootstrap by Koush, this is not installed on your phone by default).
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Note: all text in quotes is just what you should type...do not include the quotation marks when entering commands.
Disclaimer: I take no responsibility if you mess up your phone. Typing these commands incorrectly CAN mess up your phone. By following these directions, you do so at your own risk.
Installing Droid X Bootstrap
You can grab this .apk file from this thread as well, as I have it posted in one of my previous posts. You will then install this .apk file the same way that you installed z4root. Obviously if you are using the adb command prompt method, you will want to replace z4root.apk with the full name of the droid X bootstrap apk; if you are using a file manager or installer, just follow the same instructions as before as well.
With the bootstrap installed, you are now able to take backups and restore them as well in the event your phone has problems.
Will be adding SBF instructions and links soon =)
If this guide has helped you, please say thanks!
THEMES AND HOW TO USE:
NOTE: In order to install a theme, you must deodex your phone. If you attempt to try and install a theme without deodexing your phone, you can run into problems down the road.
How to Deodex Your phone the EASY way:
Below is a link that Septhin (from Sephtin.com, all credits go to him for this) posted. This is a SYSTEM ONLY flashable .zip that will give you root, as well as deodex your phone ONLY if you are on the 2.3.340 OTA for verizon. Copy this to your sdcard, and flash in bootstrap recovery! Note: If coming from anything other than an existing 2.3.340 system, then you should wipe data/factory reset for safety's sake!
http://www.mediafire.com/?gvvgnum0uma2huk
If you are on the 2.3.15 OTA looking for Deodexed system:
http://www.mediafire.com/?drixq6ry6ja83oq
How to Manually Deodex your Droid X:
Note: all credit for this portion of the writeup goes to Webst3r on droidxforums and those he has mentioned at the bottom of this section. I did not write up the deodex portion of this guide. I am simply including it as a one stop guide to help as many people as possible.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR PHONE!
You must be rooted!
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
1. Unzip xUltimate v2.2, and launch "Main.exe"
2. If everything goes well xUlt should recognize the phone and make a connection. You now should see a list of options.
3. Run option 1. After option 1 is done, run option 2.
4. Now these well take a while. Run option 3.
5. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
6. Now run option 4, and wait.
7. Exit xUltimate, and put the phone in USB mass storage.
8. Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
9. Open a command prompt, and do the following: (note: at the end of each of the following lines, press the enter/return key on your keyboard)
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Your phone should now be deodexed!
You may notice an increase in speed, and you now have the ability to edit certain files with greater effects. (i.e. services.jar)
Credits: (note these credits are from the original post made by Webst3r, not me, but I would also like to thank them for their work and contributions!)
Rainabba and Mike919: For initially working with me to get a white clock, and later deodex.
toxman: For testing, and being a huge risk taker.
teenfaces: For letting me use his services.jar
And especially Xeudoxus: For letting me a guinea pig, for xUltimate, and answering my questions. And also for the making the xUltimate tool. It defiantly makes thing easier.
SBF: What is it, and what does it do?!?
An sbf file contains the data files necessary to return an Motorola phone back to its "out of the box state". This means it is as if you just pulled the phone out of the box and turned it on. A successful sbf will return you to stock status without any custom ROM, or theme. Usually when one uses and sbf file, you will also want to wipe data/factory reset before hand, and after using and sbf for best results.
SO WHAT DO I NEED?
• RSDlite 4.8 http://www.multiupload.com/HL0ZAL9GK8
• Motorola Drivers: http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
• Correct SBF files for your phone:
o If you are on 2.3.15 OTA (bootloader 30.03): http://www.multiupload.com/HS3Q4U95CG
o 2.3.32 Full SBF: Then go to this site for all the mirror lists. I will post a few direct links below: http://www.mydroidworld.com/forums/droid-x-discussion/5633-droid-x-2-3-32-full-sbf.html
• http://www.multiupload.com/QX7Q3B53UQNOTE: http://depositfiles.com/en/files/60kvlswk2
o If you have already flashed 2.3.32, and/or have 30.04 bootloader: 2.3.34 SYSTEM ONLY SBF:
• DIRECT LINK TO SBF: http://www.megaupload.com/?d=OXK9Q1ZG
• some have preferred to flash individual files through Bootstrap recovery from MyDroidWorld. If you would like to use this method and are more comfortable flashing files than SBF, use this site:
o http://mydroidworld.com/forums/droi...ystem-baseband-2-3-340-kernel-bootloader.html
• 2.3.340 FULL SBF: http://www.mydroidworld.com/forums/droid-x-discussion/6367-new-full-sbf-droid-x-2-3-340-a.html
• Thanks to Maderschramm, there is any easier way to get back to stock on 2.3.340 OTA WITH ROOT
MADERSTCOK "SBF" (note I did not do this write-up, all credit goes to Bouchigo on android forums. Original credit goes to Maderschramm over at DroidXforums and XDA)
NOTICE: Coming from ANY non-blur based ROM and doing Maderstcok is guaranteed to bootloop due to mismatch in framework without a data/cache wipe.
http://www.droidxforums.com/forum/droid-x-hacks/15666-maderstcok-ota-2-3-340-update-zip.html
maderstcok - OTA 2.3.340 update.zip
None are responsible for your phone but you.
After a bit of work I've created an update.zip for you guys that want a fresh install of 2.3.340 without sbfing.
This is the FULL, OTA 2.3.340 - contains radio, kernel, and all other updates, even those EXCLUDED by the 2.3.340 system only sbf.
What that means is that if you have 2.3.15, 2.3.151, or 2.3.320 you're one update.zip away from the OTA 2.3.340
This is useful in many ways:
• You want stock .340 but didn't create a nandroid backup
• Can't OTA (modded phone)
• Get ready for an OTA
• Remove Root
• Add bloat back
• Re-Odex
• Your phone is acting weird on the update
• Something broke
• Fresh ROM install
• You don't want to flash 5 update.zips or sbf to update your phone
• etc.
This will format your system data (helps prevents bootloops - not 100%) and system (in case a rom put some apps in the /system/app) partitions and also changes the boot image to the stock moto M (to fix the Tranquility boot logo - something even an SBF won't fix).
As always, make a backup and I'm not responsible for what happens to your phone.
Download the file here and place it on your sdcard: http://www.droidxforums.com/forum/
• Mirror 1 http://ubuntuone.com/p/XAk/
• Mirror 2 http://www.megaupload.com/?d=4AO672L1
Instructions:
1. Using the Droid X Bootstrapper make a backup. (more information here)
2. Browse (using volume buttons) to "install zip from sdcard" and select it with the camera button.
3. Select "choose zip from sdcard".
4. Select "maderstcok340.zip"
5. Confirm the install.
6. Be patient, wait for the install to finish.
7. Reboot the Droid X. DO NOTHING ELSE IN CLOCKWORKMOD!!!!!!!
8. Activate the phone with VZW (more instructions below).
If you attempt to create a backup or flash a rom post maderstcok installation you're going to have a paperweight. This seems to be because maderstcok removes root and the clockworkmod recovery area, so it doesn't like you playing around in there. Re-root and reinstall the bootstrapper, then create a backup or flash a new rom, DON'T DO IT BEFORE REBOOTING THE DX AFTER ISNTALL.
Formatting Data and Cache is optional; however, if you want a really clean install do so. If you factory reset you'll be forced to activate the phone automatically while if you don't you'll have to follow the quick and dirty activation instructions below - the choice is ultimately yours.
Quick and dirty instructions for activation:
1. Dial *228
2. Press 1
3. Enter last 4 of primary acct holder's SSN
4. Wait - more in depth instructions in a link further down.
This can take some time, especially on the two system installs and the radio install. Don't battery pull unless you want a brick.
The file won't flash properly if you have a botched download - this seems to be caused by the size of the file. Please check your file size before flashing:
Size: 284.7 MB (298481300 bytes)
MD5: ce7122280eafad4a39ba7fefeb764bf5
My free filehosters sometimes .zip the .zip - it looks like maderstcok340.zip.zip
Just unzip once and check the md5 to make sure it checks out - if not, redownload. Don't try to flash the .zip.zip without unzipping it once!
You'll have to activate your phone again after the install. See this for additional help.
If you encounter any problems during the flashing process follow standard ROM installation troubleshooting (i.e. battery pull, factory reset, etc.)
A lot of this stuff is from Team Black Hat - I did pull some of my own phone files too - but if you're looking to donate, please hit them up. Without them we'd be up a creek. Tell 'em I sent ya
One final note - z4root seems to work flawlessly after flashing this file. Just thought I'd throw that in there...
Enjoy!
How to use RSDlite and an SBF file:
NOTES ABOUT USING SBF and RSDlite: Make sure your battery is fully charged. If your phone dies while applying an SBF file, you could be stuck...Be sure to create a backup before using SBF, this could be a nandroid backup, and I would also recommend backing up your SMS messages and applications and any application data (use Titanium backup).
I have found this to have the best results.... before applying an SBF, boot into bootstrap recovery and do a wipe data/factory reset.
1. Turn off your phone. Hold down the "Volume down" + camera button while holding the power button. Your screen should flash and say
Bootloader
30.03 (or 30.04 if you are on the latest update)
Battery OK
OK to program
Connect USB
Data Cable
2. Open up RSDlite and click the " ... " button to browse to the appropriate SBF that you need to use.
a. If on bootloader version 30.03 then you will want to use the VRZ_MB810_2.3.15_1FF_01.sbf file
b. If on bootloader 30.04, then you will more than likely want to flash the 2.3.34 system only sbf (SHADO_X6_2.3.34_SYSTEM-ONLY.sbf)
3. Once it recognizes the file, connect your droid X to the computer via the usb cable. You should see your phone listed in the bottom section of RSDlite.
4. Click the start button, and watch the magic at work =)
5. When your phone reboots, I generally try to do another wipe data/factory reset.
a. When turning phone on, hold down home button + power button. When the droid with the ! comes up, press the search button. You can use the volume up/down buttons to navigate, and the camera button to select.
If your phone dies during sbf, A) make sure to charge your battery before sbf next time B) here are some instructions
IF YOUR PHONE DIES DURING SBF
How to Fix
One thing that you may notice is that when you have this error, your phone will not charge the battery and you'll only be able to see the screen turn on if its plugged into the wall. Somewhere on the screen it will say "Your Battery is Low" and "Cannot Reprogram" or something like that. The easiest way to get through this is to find a friend with a charged battery or go to your local Verizon store and see if they have a demo phone they can use to charge your battery. If you're like me though you will not be lucky in any sense like this so you will have to find the MacGyver inside of you and get a little creative. What you need for this is an old USB cord. One end must be a standard USB cable head and the other can pretty much be anything. Once you have that, follow these steps:
NOTE: I TAKE NO RESPONSIBILITY FOR DAMAGE DONE TO ANY PHONE, BATTERY, ETC. FOLLOW THESE STEPS WITH CAUTION TO AVOID RISK OF DAMAGE.
1. Take your cable and cut off one of the ends, leaving a standard USB plug at the opposite end to plug into your computer.
2. Now you need to strip about and inch of the wire off until you get to the core where you should see 4 colored wires (red, black, white, and green). The colors don't really matter and they may vary, just as long as you can see a red wire and a black wire.
3. Strip off about a quarter inch of the rubber sleeving on the red and black cables, exposing the actual metal wire.
4. Twist the metal strands of each of the wires a couple of times so that all of the wires from the black cable are together and all of the wires from the red cable are together. This is just to make sure that you don't create a short circuit.
5. Here's where it gets a little tricky. You are going to use this cable to make the phone think the battery is fully charged, when in fact you will just be powering the phone using the power from the USB port. Pull out the battery on your phone and find the 4 exposed metal slots (the battery terminals).
6. Each of the far terminals should be labeled with a plus (+) or a minus (-). What you need to do is put exposed leads on the red wire up to the positive terminal and the leads of the black wire up to the negative terminal.
7. While still holding the leads on their respective terminals, slide the battery back into place in the phone. MAKE SURE THE WIRES ARE NOT TOUCHING WHEN YOU PUT THE BATTERY INTO THE PHONE! BAD THINGS COULD HAPPEN ONCE YOU PLUG THE CORD INTO THE COMPUTER!
Note: As tested by parm289, you can skip step 7 and just use the cable to charge the battery if you'd like. He recommends allowing it to charge for 6-7 minutes before placing it back into the phone. Thanks parm!
8. Once the battery is in place and the wires are on the correct terminals but not touching each other, plug the USB cord into the computer. If all has gone as it should, the screen on your phone should come on (may have to press the power button) and the phone should be telling you that the battery charge is okay and that it is okay to program. YAY! Your phone is almost back to normal!
9. Go back up to the previous section in this post that tells you how to reflash the .sbf and follow all of the instructions there. Once that has finished flashing the .sbf to your phone, your phone should be back to working order! You will most likely have to redo the entire setup on your phone but at least your phone is no longer a fancy paperweight
ROM overviews:
Note due to the constant change in version numbers, I have may not have updated this list. I will try to keep it updated as I can.
BLUR ROMs: Apex 1.3, ZapX Bazinga, Rubix Blurry 1.8, Simply Stunning X, DarkSlide 4.2, Fusion 2.0, Tranquility 3.7.0 (has option to add blur)
Blur-less ROMs: Tranquility3.7.0, Rubix Focused 1.9.7, Liberty 1.5, Cobalt 1.0 , Ultimate Droid, FlyX, Darkslide 4.2, GummyJar 2.5, Incredibly Re-Engineered 1.0, Obsidian 2.0.2, Fission 2.5.7
LIBERTY 1.5
http://forum.xda-developers.com/showthread.php?t=939592
ROM Features:
Base....Originally based on GummyJAR, I would call Liberty's bas a evolution of GummyJAR at this point
95% of all the apps were built from source.... rather than decompiled and hacked apps via APKmanager!! And it shows in pure speed!!!!
Blurless
Wycontacts
Cytown Phone
AOSP Pattern lock
AOSP tab Lockscreen with the option for Rotary as well
Custom terminal emulator with added color options
Reboot option in power down menu
Launcher2 with increased snap velocity
Custom Liberty wallpapers app
Custom Liberty live wallpapers (nexus Mod like, modded from CM source)
Music control's in lockscreen (will control any music source including Pandora)
MusicMod by Eliot Stocker (built from CM source and compiled by Team Liberty)
Inverted Gtalk and Gvoice
Gingerbread keyboard - built by hotaru modified by Team Liberty for better button size
AppWidgetPicker - credit boombuler
Latest Market included
build.prop tweaks - thanks to LexusBrian400
Ads blocked via hosts file - thanks to delta_foxtrot2
10% battery increments support
Clockwork recovery (bootstrap) installs on initial install
Working init.d with config file (start-up scripts)
Liberty scripts:
(Run them in terminal emulator. Type script_name -help for more info)
** ads, allinone, apploc, backup, bootani, cache, camsound, compcache, chglog, donate, exe, fixperms, freemem, install_zip, load, pulldown_text, install_zip, load, market_history pulldown_text, rb, restore,rmapk, setcpu, setprops, slim, sound, switch, symlink, sysro, sysrw, usb, zipalign_apks **
All apps optimized and zip aligned
More to come...
Toolbox Features:
• App Management:
* Apps2SD
* Remove/Backup system/data apps
* Install Add-Ons on the fly (blur, non-blur, extras, etc.)
* Backup/restore feature
• Liberty Mods
* Switch between transition animations
* Change boot logos
* Set Build Properties * File editor included by Fr4gg0r *
* Install Fonts
* Install Themes from the toolbox
* Pulldown-bar text editor
* Icon Chooser (change application and battery icons)
• Liberty Tweaks
* Ad Blocker (Block/Unblock)
* Cache Manager (clear/move to SD)
* Free Memory
* Manage Boot Animation
* Mount system rw, fix permissions, zipalign apps, etc.
• Reboot Options
* Reboot, reboot bootstrap, reboot recovery, powerdown
• Settings
* App Theme (change theme of toolbox)
* Notify for ROM updates/patches
* Lockscreen Settings
* Recovery safe mode
* Overclocking
* Sysctl Support
* Camera Shutter Sound
* Tools (Spare Parts, Dev Tools, Testing Menu)
* Restore apps feature
* Set install location on boot
* Zipalign apps on reboot
* Clear cache on reboot
* Fix permissions on reboot
Rubix 1.9.7
http://forum.xda-developers.com/showthread.php?t=927644
Rubix Focused 1.9.7 overview: If you are looking for a ROM with great stability and battery life, then look no further than Rubix Focused 1.9.7. Drod2169 has thrown some amazing scripts in this ROM that allow for app backup, ad-block, and many others. His direct support for the ROM and great speed and responsiveness from his dev work makes it a solid choice. In addition, he has fully customized sysctl.conf to help improve battery life, Java VM management, speed and performance.
* SMART One-Click Overclock App (QuickClock for rubiX) (Credit to Paul Anderson’s amazing work!)
* This is a very brilliant OC app. It configures specifically for your device, and OC’s to the BEST value, and voltage settings for your phone.
**If your max speed turns out to be <1100, it will only overclock to 1100. This is for the sake of Overclocking, and the safety of your device to not push it higher.
* Base is GummyJar (Credit Kejar)
* Full firstboot functionality.
* Rotary Lockscreen Option
* AOSP Settings Menu (No Compass Calibrate/Battery Manager. For Battery Info, check out About Phone/Battery Use)
* GB Keyboard with working size (cause size does matter )
* Theme by Mycahya
* Working 3G HotSpot
* Phone as Modem/USB Tether Option (Instructions stored in rubiX Folder on your SDCard)
* AOSP Lock screen instead of themed Moto tabs!
* Lockscreen pattern no longer on a timer.
* Market Apps installed to Data Partition
* This Includes:
* Maps
* Gmail
* Voice Search
* YouTube
* ADW Launcher
* Street View
* Spare Parts
* Adobe Flash Player
* DL Crutch Lite (For Browser Downloads)
* Tweaks adjusted
* File Manager (Credit to Cyanogen)
Gingerbread Parts: (Credit to Pete)
* Launcher 2
* Gallery 3D
* Alarm Clock
* Desk Clock
SCRIPTS: Credit to Fabulous, JRummy, Sephtin and myself.
adblock: block or view ads
apps: run the script for directions. If you choose restore, you must reboot after for it to take effect
backup: backs up all of your user apps. backup -bk is the correct way to run the script
calc: remove/restore the calculator
carhome: remove/restore the car home launcher
dxeye: remove/restore the DX LWP Please note that this is removed by default, and placed in /data/rubix run the script to restore.
email: remove/restore the email app
fixperm: fixes permissions (credit Koush)
gallery: switches between the 2D (credit to Cyanogen) and 3D AOSP Gallery
genie: remove/restore the news/weather app
office: remove/restore QuickOffice: Please note that this is removed by default, and placed in /data/rubix run the script to restore.
sys: write the system read/only (-ro) or read/write (-rw)
zipalign_apks: zipaligns all the apps in system. Unnecessary since this is ran on every boot!
Fission 2.5.7
http://forum.xda-developers.com/showthread.php?t=839246
About Fission: The first generic Android platform for current and future Droid devices. We are a bunch of mad hackers, modders and developers that were not happy with the current model of Droids being "Blurred" so we began a mission to rid our devices from the blurriness of VZW Android systems. It started with a crazy idea of messing with the Droid2 SDK that has turned into a full fledge AOSP generic type of ROM. We have incorporated many features that were only seen in AOSP ROMs before this. Some of the features include Reboot in Power Menu, custom built Framework, vanilla Android GUI, totally blur free app folder and many more AOSP like features to come in the short term future.
Features:
True Vanilla ROM with generic Android feel, not themed to look like one. No blur apps...
Reboot in Power Menu.
Custom Framework - 10% battery increments with display percent number & without.
Overclock ready out of box.
Lots of free memory.
ROM has root and has been deodexed, and zip aligned.
Busybox installed and symlinks have been applied.
Clean base for you to customize how you like.
And many more...
WILL COVER MORE THIS WEEK! Will also clean up this list to cover most important features to reduce lengthy posts.
Short Little MetaMorph Guide for Changing Icons
Had someone in a post ask about changing some battery icons... So this is a little blip about using it...
I recommend checking out DroidPirate.com if you are looking for images. If anyone else has a place they use for icons, please let me know, and I will add it to this post! Thanks
How-To
MetaMorph ONLY installs the current theme files to the app that exist in the /system/app/ if there is no file you must find the .apk on your phone and place it into the /system/app/ directory.
1) pick the icons you want and download the .zip
2) The file should be a “.ZIP” extension, make sure you do not unzip the file.
3) Connect your device via USB and mount
4) On the root of your SD-Card you need to create a folder called “AndroidThemes” IT MUST LOOK EXACTLY LIKE THAT OR IT WILL NOT WORK
5) Copy the .ZIP file you downloaded and place it in the “AndroidThemes” folder.
6) Assuming you already have the MetaMorph application installed on your phone. Open the MetaMorph app.
7) Click on “Unzip/Extract New Theme”
8) You should the .zip file you have added to the AndroidThemes folder like in the image shown below.
9) Click on the file inside of MetaMorph a MetaMorph install screen should come up telling you about the theme you are installing like shown below (just click Close)
10) Now you should see a button located on the bottom click on “Apply All” this will begin the process of the application skinning.
11) You should see a message box that pops up that says “All Themes Applied” like shown below
12) Reboot your phone and make sure whatever app you where skinning is now skinned.
Recovering Contacts If You Lose Backup Assistant When Using a Custom ROM:
For those of you who relied on Backup Assistant in the default Moto ROM for your contacts, you are in luck =)
Go to backupassistant.com and log in. From here, you can see all of the contacts as of your last sync, and then you can back them up as an Outlook CSV. Next, login to your gmail account, click on "Contacts" and then click "Import". Import the .csv file that you generated from backupassistant.com and....VOILA, all of your contacts are now synced to your gmail account, and you can kiss backup assistant goodbye!
SysCtl.conf Tweaks
Credit for this section goes to macpro88 at DroidXforums and Marius from whom macpro mentions below
Liberty 1.0 and Syssctl Config
Listen up everyone! Since the release of Liberty 1.0, JRummy16 also released a new app in the market called Sysctl Config, which gave users an interface to manually edit and tweak the sysctl.conf file. Alongside this, Liberty made it easier to configure the sysctl.conf file using the integrated menu option under Liberty Settings without the use of the app.
Please take special note! That any ROM can utilize these sysctl.conf tweaks, not just Liberty, and rooted stock as well.
(You must be rooted and have busybox installed for this to work on stock)
So what is the purpose of this thread? And what is Sysctl.conf all about?
First of all, we are going to explore what sysctl.conf is.
Second of all, we are going to explore what sysctl.conf does, and what it can do for your phone.
Lastly, we are going to explore how sysctl.conf works and what kind of benefit is has on the Android OS.
Now, before we get started, we need to clear something up! The tweaks and modifications we will discuss in this thread, WILL NOT IN ANYWAY INFLUENCE BENCHMARK SCORES SUCH AS QUADRANT! Benchmark apps are meant to measure hardware performance only and are in no way affected by these tweaks and modifications, but make no mistake! You will notice at least a slight increase in Android's performance and a possible increase in battery life as well.
Another thing that everyone needs to know is that the Android OS is a Linux based operating system, so there will be a lot of references to Linux, just so you are not confused.
So lets get started shall we?!?!
Ok, so first of all, let’s explore what sysctl.conf is.
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
Min Free KBytes (vm.min_free_kbytes) - This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
Dirty Ratio (vm.dirty_ratio) and Dirty Background Ratio (vm.dirty_background_ratio) control how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure) -Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
Oom Allocating Task (vm.oom_kill_allocating_task) (enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.) -This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
This information has been pulled from the following sites:
imoseyon: Sysctl tweaking for faster, longer lasting Android
imoseyon: sysctl (and minfree) tweaks revisited
http://www.linuxinsight.com/proc_sys_vm_hierarchy.html
How to edit the values manually, follow these steps:
1) First enable sysctl from Liberty settings, if you are on Liberty
2) Run Root Explorer
3) Modify /data/liberty/init.d.conf to make sure that sysctl is enabled ("sysctl = 1")
4) Go to /system/etc/, and mount it r/w
5) Modify sysctl.conf by long pressing the sysctl.conf file and selecting "Open in Text Editor." When finished, save the file and exit
6) Run Terminal Emulator
7) Type "sysctl -p" (output should confirm whether you've done step 4&5 correctly)
(Soon to come, how to enable if your ROM does not support sysctl, which will require much more tweaking.)
If you want to check to see if your changes take hold after reboots, run this in Terminal Emulator:
sysctl -a| grep vm
or
sysctl -p
This command will give you all the sysctl values, scroll down to find the ones you edited and verify that they are the same values you changed them too.
Now, if you want the easy way out, our good friend Marius has been great, and created a flash-able .zip that does all of the work for you!
The .zip can be found here, at Marius' blog titled "imoseyon."
When you flash the .zip file, in Bootstrap Recovery, the following will take effect, and please note, any settings you may have altered, will be overwritten!
Applying the .zip will do the following:
1. Install BusyBox 1.18.0 (in an alternate location)
2. Enables cron, which is a Linux time-base job scheduler
3. Tweaks certain kernel elements (vm, minfree, etc.)
4. Tweaks build.prop (on some ROMs)
5. Flushes system caches once a day (1AM PT)
This .zip should be all you need to get your phone running in tip-top shape. The zip is fairly ROM agnostic, meaning that almost any rooted ROM is going to work (rubiX, Liberty, ApeX, Darkslide, etc. and maybe even stock ROM, as long as you are rooted). It should also work for both Droid X and Droid 2.
Please make sure you create a backup before flashing anything!
After you flash the .zip, you can run the following command in Terminal to make sure it was applied successfully:
pgrep -f crond
If you get a value on the following line, the .zip has been applied successfully, don't worry about what number you, everyone may end up with a different number.
If you are really feeling adventurous and are down for a good read, and really want to get to know the Android OS even better, please follow Marius' blog, as it is a great read!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
There really is NO right answer when you research sysctl. The best thing to do would be to search VM Linux tweaks. Most of the time, you'll see sysctl values that people optimizing their Linux systems use. Take a look at those, and then look into the actual name of what you're tweaking, to find out what it does.
VFS Cache Pressure, go ahead and disable that. I think the stock value is 100, so enter that. At the value of "12" which is the default in Liberty (from one of my old sysctl's) causes a slowdown after a while, even though makes everything much more responsive at the get go. The slowdown is why I removed it from rubiX roms. OOM Kill Allocating Task kills off the app that caused you to run out of memory, which runs better than the stock android configuration.
The default values in Liberty sysctl tweaks are what I suggested to JRummy after extensive research and testing with Drod on RubiX. The settings Marius used up above are actually the stock settings, so you would have those values by disabling sysctl all-together, which is definitely an option. By raising the dirty ratio and dirty background ratio to 95 and 60 respectively, you are allowing for fewer memory flushes which results in much improved battery life. I found, as Drod mentioned, that with vfs_cache_pressure too low, you will see some slowdowns in performance at around 50 hours without a reboot. Through additional testing, I determined that a setting of 50 here, half that of stock will provide a good blend of benefits without risk. You would need to be running for something like 150 hours without a reboot in order to ever see a slowdown with this setting. It may be even more than that.
From what I have gathered it seems the general consensus in this thread is that there are two main approaches to this:
vm.min_free_kbytes = a
vm.dirty_ratio = b
vm.dirty_background_ratio = c
vm.vfs_cache_pressure = d
One is the self-maintained, improved overall performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
50 => d => 25*
*at 25 you’re probably going to have to reboot after about two days
Recommend values in bold
The other is the automated purge cache controlled, extreme performance approach:
3072 => a => 2048
95 => b => 70
60 => c => 40
10** => d => 1***
**Need to run a script to purge cache every 22-30
*** Need to run a script to purge cache every 10-16
Personal recommendation for most people (no manual flushing required):
dirty_ratio = 90
dirty_background_ratio = 55
vfs_cache_pressure = 20
If you are willing to play around with manual or timed flushing I think you can squeeze a little more performance and battery life with:
dirty_ratio = 90
dirty_background_ratio = 70
vfs_cache_pressure = 1
A lot of this stuff is subjective and very dependent on your usage pattern. I've gone about 3 days with the latter without having to flush and probably could have gone a lot longer except i was running some other experiments that caused my phone to reboot.
-------------------------------------------------------------------------------------------------------------------------------------
thanks I really needed this thread
Glad to hear it helped. I will be adding to it this weekend hopefully if I can escape from work...
Sent from my DROIDX using XDA App
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
zwade01 said:
Your example of a semicolon turned into a winky face instead of a ( ; ). Might wanna put a couple spaces in there for the noobs
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Haha, oops. Thanks for catching that. Think I fixed it... But dont think it shows up with the same formatting on my phone, so I cant tell.
Sent from my DROIDX using XDA App
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yes, you do.
Sent from my DROIDX using Tapatalk
angryjello said:
<-- n00b
So I rooted my phone and tried to install a rom with rom manager and nothing happened. I tried manually and no roms appeared in the boot menu. Soooooooo my question is, do I need the bootstrapper app in order to install roms?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
SysAdmin-X said:
I think if you press on "flash clockwork" that you dont necessarily need bootstrap recovery, as it is built in.
I personally only use bootstrap recovery as you can still do backups/restores, and install themes and Roms. Just one less step in my opinion. I just manually download the ROMs or themes and move them to my sdcard.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
angryjello said:
alright so i downloaded a rom from romManager but it won't load it from the app. I located the file on my sd card:
clockworkmod/www sephtin.com/rubix/rubiX.js
Now can i just zip the rubiX folder and do a manual boot to it?
Click to expand...
Click to collapse
Um... I'm not super familiar with ROM manager, as I don't personally use it to download ROMs, but from what I know, that looks like a javascript file, and not a .zip for a ROM or theme installation. This looks more like a script that sephtin may have written... I'm not sure if maybe ROM manager calls a javascript file to install the ROM or not, but to my knowledge, if you download the ROM from within ROM manager, it should be able to install it.
Here is my suggestion (I'm assuming you are trying to install Rubix 1.9.7...
Download the ROM from here:
http://bit.ly/hw6rE8
Then connect your phone to your computer via the usb cable. Put the phone in USB mass storage mode and copy the file you downloaded to your SDcard.
Before installing the ROM, use one of the free apps from the market to backup your SMS messages if you don't want to lose them. Also download Titanium backup to backup your applications and data if you don't want to lose that as well. As for your contacts, if you don't have those backed up to your google (gmail) account, then those will be wiped out as well with the Rubix installation.
Then if you haven't already... download Droid X bootstrap recovery and install it. Open the app, and press the top button to hijack the boot process. Then press the "reboot recovery" button to reboot into bootstrap recovery. When the phone reboots in bootstrap, use the volume up/down buttons to move the green highlighted selection, and the camera button the phone to make your selections. Go to the option that says "Wipe data/factory reset, and do this use the camera button to select this (this will wipe out all the downloaded apps and user data on your phone). Next, use the back arrow button on your phone to get back to the main menu if necessary. Browse to install .zip from sdcard, then locate the Rubix file that you copied to your sdcard and use the camera button to select it. This will then install the Rubix ROM. when it finishes, it should bring you back to the main menu, but if not, use the back arrow button on the phone to get back to the main menu. Choose the "reboot system now" button and it will reboot normally.
From the first reboot after installing, it may take SEVERAL minutes before the phone actually boots up, this is normal; give it some time and let it do its thing. If it does not boot up after 15 minutes, something is wrong, and you should post back here for more help (or browse on the forums and google, they are both your friend).
Good luck!
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
angryjello said:
@SysAdmin-X thanks alot bro i was trying so hard to find that file on the web. Must have not been looking hard enough!
Click to expand...
Click to collapse
No problem at all, im glad I could help. Post back if you have more questions
Sent from my DROIDX using XDA App
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
kdkinc said:
Great guide for noobs and for-getters like me.
Is their any reason why you don't also include Maderstcok's SBF method ??
Personally I use it every few weeks especially when jumping Rom's so much.
Thanks for all you do.
Ps when I see someone "new" this is one guide that I refer them too.
Click to expand...
Click to collapse
Thanks, I havent included Maderstcok's yet just cuz I havent gotten to type it up =( plan is to get that and hopefully a lot more info.thrown up there this week!
Appreciate you referring people here! My plan is to make this a one stop guide for all the basics at a minimum.
Sent from my DROIDX using XDA App
angryjello said:
So I backed everything up, hit the top and bottom buttons on the bootstrapper app.
took me to the bootstrap recovery. I wiped all the data, then i selected install from zip. Selected the rubiXFocused1.9.7.zip, and the this happened:
Can't Open rubiXFocused1.9.7.zip
(bad)
installation aborted...
Not Good, any idea why?
Click to expand...
Click to collapse
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
SysAdmin-X said:
Sounds like it might have been a bad download. Try downloading from that link again, if th at doesnt work, here is another link:
http://bit.ly/ga0ejk
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Alright bro it worked for sure now! I got it up and running, thanks so much for this op and all the extra help!

Build.prop Worktool for Windows (v1.7 - July 26 2011)

Script is standalone : you can download latest version without upgrading from previous version
v1.6 > Big update on 3G+ tweak addon, more powerful and much faster
Build.prop Worktool - A powerful but safe build.prop manager/editor
Hi !
Okay guys, since I know how powerful the build.prop can be, I love to play with it.
But I was bored to edit using Root Explorer, or using ADB command-line...
So... Let me present you my outrageously complicated (internally) script to manage your build.prop right from your computer, with ease, fun and safety !
GENERAL :
For any Windows NT kernel (Developped under Windows 7 x64... so should work everywhere )
Portable and ready to use - No installation required, all files included (ADB with drivers also)
Lightweight (<3Mb unzipped, because of ADB very big lol)
Tested on XPERA x10i but should work on ANY Android powered device (if your ROM uses a build.prop located into /system/)
KEY FEATURES :
Easy open/edit your build.prop in your default text editor
Backup creation/management
Save backup on your computer and/or on your device
Safe (Automatic backup generator - Manages up to 2 backup files, exhaustive log file)
Automatic permissions management
Add-on capability : possible to add automated installation scripts to tweak your build.prop
List of present add-ons : 3G+ enhancement tweak
Very clean : deletes all temporary files, auto start/stop ADB server and kills the process when useless
Convenient : direct access to this thread, easy to use
v1.6+ : (beta) Build.prop XPlorer, to check with ease your build.prop
I based the main script on my 3G+ enhancement script, available on the official thread.
** As usual... Use at your own risk **
Test, comment, criticize, if you find anything, just drop a comment or PM
FAQ
FAQ​- Supported devices
It is first developped for Sony Ericsson XPERIA x10, but it should work on any Android device with these requirements :
* Rooted
* File system is mounted Read/Write.
* Build.prop is located into /system/ and named "build.prop"
Sony Ericsson XPERIA x10 : fully working
Samsung Galaxy S2 : half working (file system is read-only...)
- How it's working ?
The script works generally in this way :
It downloads from your device your build.prop and creates two temporary backups.
Then, it opens one of the temporary backup into notepad, to let you edit all you want.
Once file closed/saved, the file is reconfigured automatically, then sent back to your device.
The script allows you next to keep, on wish, the remaining backup and to reboot your device.
- Is this safe ?
The script makes a backup of your build.prop every time you try to access it. There's also human-friendly log file to help you identify problems with ease.
There is also NO automatic upload to your device : the script will always ask you before if you want to upload the new build.prop to your device. Even if you upload it, backup is stored and can even be stored safely on your device for future use.
- Is this all automatic ?
Yes. The script makes backups by itself, reboot your device for you (if you wish), and of course change permissions. But don't worry : it will ask your approval for any important process
- The 3G tweak makes my connection unstable !
The Manager is based on my 3G+ enhancement script, using "Full Mode". In the original script, there is also a "Lite Mode" for some networks (like AT&T) I included in v1.3.
To make your network stable, the script will disable the two lines below :
ro.ril.enable.dtm=1 (will be turned to 0)
ro.ril.enable.a53=1 (will be turned to 0)
To get full details about the 3G+ tweak, check the thread :
http://forum.xda-developers.com/showthread.php?t=951765
Why is there "so many" different batch files ?
It's easier for me to improve/maintain the batch by splitting it into different functions. There's a main script, and subroutines called when needed.
Of course, all the subroutines, including addons, are programmed to be run only from main script. You can run any subroutine separately, but it will mostly crash and create useless files not being deleted. Always run the main script, and do no try to run separately subroutine - not dangerous, but 100% useless/buggy.
- It's not working.
* Make sure your device is :
** ROOTED,
** Full external access to system (su command) [if not, will drop errors like "Operations not permitted" or "file system is mounted read only")
** USB Debugging is enabled,
** Connected using USB and all USB drivers are installed/working.
* You might need administrative privileges in Windows to fully run the program.
* If you're running your device from recovery, you may need to mount /system/ folder before running the script (Partition tools > Mount /system).
- It's still not working.
* Drop a message in the official thread.
* If you get errors about file system Read only, try to run your device in Recovery mode, and fix permissions.
- Will the script create lots of files/make a big drive footprint ?
I hate programs creating lots of temp files. So, the script was developped to create files AND to clean/remove them all once everything is done. Even if it crashes without removing files, you just need to restart the script - it will clean all previous temporary files.
If ADB is run, it WILL be fully closed once everything is done. Server will be killed, then ADB process (named adb.exe) will be killed. Your system will be as clean as it was before running the script.
The script is of course fully portable : there's no installation needed. You can put the script where you want, but you just need to keep all script files/folders in the same folder.
In a future release, I'll add something to purge the log file.
- Which OS is supported ?
It's developped in Windows 7 x64. You should be able to fully run it on any 2000+ Windows NT OS.
As it is NT script, it will work only on Windows computer. It will also not work properly on pure DOS (it's using NT commands and Windows-related commands not included in older Windows NT systems, like NT4).
Report if you tested it on other Microsoft OS (NT 4, Windows 95, 98 or 2000, Dos 6.22...)
- I wanna contribute.
Just right click the .cmd/bat files, edit them with Notepad or anything you want
You can also send me a message (thread or PM) if you notice some piece of code I can improve with other commands (I don't know DOS commands enough )
v1.0 (11/5/2011) = initial release
v1.1 (13/5/2011) = removed BFC tags, updated error 2 (ADB get-state, to help you identify problem), removed 3G tweak returns error 3 if not present (addon = not necessary), added template.bat to create add-ons, improved launcher.bat (add-on primitive detection), added add-on installation detector (displays backup/reboot options only when add-on was installed), corrected folder "\" bug
v1.2 (13 may formely 14/5/2011) = added automated deleter/file checker for 3G+ tweak. Still early stage but looks to work. Automated batch thanks to http://www.dostips.com
v1.3 (16/5/2011) = added 3G+ enhancement lite mode (for networks like AT&T) and removed 1 step on auto deletion, fixed bug of false error when trying to download from device a build.prop.bak not existing, added management options to Backup (send local backup to device, delete backup on device), solved backup internal error
v1.4 (29/5/2011) = fixed window console size, enhanced menus, faster script closing, log file generator, several bugs fixed, enhanced help (readme in Notepad, direct open XDA thread in Firefox), added adb.exe process killer
v1.5 (6/6/2011) = added console title, fixed some menu bugs, updated Readme, weblinks now open in the default user browser, build.prop will now open in default notepad editor, improved interface, fixed unexpected exit bug, added contact me using default email (still experimental)
v1.6 (15/6/2011) = improved ADB process killing, deeply improved 3G tweak script with sed and no more TXT file, readme opens in your default editor, improved interface, updated template, unified common subroutines into BAKengine.bat, user-friendly explorer of build.prop (not great for now), deleted Substengine (deprecated), "0" in menues now refers to Go Back/Exit, improved missing engines detection, added general temp/log file purger/deleter ** To celebrate The Legend of Zelda series 25th Anniversary, my script is now tagged "Powered by Hyrule DOS"
DETAILLED 3G Addon update :
- detects presence of previous installation and files
- Sed command : fastest detection and subtitute of lines
- Optimized for fastest operation and fully clean build.prop file
- Several stuff...
External SED support thanks to GNU Utilities for win32 @ http://unxutils.sourceforge.net/
v1.7 (26/7/2011) = fixed no deletion of TEMP folder/files, fixed ADB command not found, new entries for XPlorer
Known bugs :
* (Main) Will not detect if build.prop.bak and build.prop.old are the same (not very important, I'll improve this later)
* Report anything you find
Developper/Advanced user addendum
(Write in progress)
Backup management
The script creates up to two backups, localed in main directory :
- build.prop.bak
- build.prop.old
Build.prop.old is generated if the script detects there's an existing build.prop.bak, to avoid accidental loss of it.
Build.prop.old is the final backup, and WILL BE DELETED if detected. The script manages backups like this :
1. If an existing build.prop.bak is present...
>> Script will detect for build.prop.old presence - if it exists, it will be deleted,
>> the build.prop.bak will be renamed to build.prop.old.
2. If there is no build.prop.bak detected...
>> Script will generate a build.prop.bak.
ADB Error detection
Error 2 (device not connected) works using a trick - it's not really related to device state.
In fact, the script will attempt to connect your device to download your build.prop. Once it is done - or not - the script checks if a local build.prop file was created. If it's not present, it means ADB encountered an error - about 90% because device is not connected - and will display error 2.
Keep in mind then there is small chance that your error does NOT come of device not connected : administrative privileges missing (don't allow the script to create the file), drivers buggy, ...)
Hi,
I cant use your WorkTool V1.6
It says ADB cmd not found.
v1.7 out, sorry for delay, I prepared it few days ago then I forgot to upload ^^
Really good work
Perceval from Hyrule said:
FAQ​- Supported devices
It is first developped for Sony Ericsson XPERIA x10, but it should work on any Android device with these requirements :
* Rooted
* File system is mounted Read/Write.
* Build.prop is located into /system/ and named "build.prop"
Sony Ericsson XPERIA x10 : fully working
Samsung Galaxy S2 : half working (file system is read-only...)
- How it's working ?
The script works generally in this way :
It downloads from your device your build.prop and creates two temporary backups.
Then, it opens one of the temporary backup into notepad, to let you edit all you want.
Once file closed/saved, the file is reconfigured automatically, then sent back to your device.
The script allows you next to keep, on wish, the remaining backup and to reboot your device.
- Is this safe ?
The script makes a backup of your build.prop every time you try to access it. There's also human-friendly log file to help you identify problems with ease.
There is also NO automatic upload to your device : the script will always ask you before if you want to upload the new build.prop to your device. Even if you upload it, backup is stored and can even be stored safely on your device for future use.
- Is this all automatic ?
Yes. The script makes backups by itself, reboot your device for you (if you wish), and of course change permissions. But don't worry : it will ask your approval for any important process
- The 3G tweak makes my connection unstable !
The Manager is based on my 3G+ enhancement script, using "Full Mode". In the original script, there is also a "Lite Mode" for some networks (like AT&T) I included in v1.3.
To make your network stable, the script will disable the two lines below :
ro.ril.enable.dtm=1 (will be turned to 0)
ro.ril.enable.a53=1 (will be turned to 0)
To get full details about the 3G+ tweak, check the thread :
http://forum.xda-developers.com/showthread.php?t=951765
Why is there "so many" different batch files ?
It's easier for me to improve/maintain the batch by splitting it into different functions. There's a main script, and subroutines called when needed.
Of course, all the subroutines, including addons, are programmed to be run only from main script. You can run any subroutine separately, but it will mostly crash and create useless files not being deleted. Always run the main script, and do no try to run separately subroutine - not dangerous, but 100% useless/buggy.
- It's not working.
* Make sure your device is :
** ROOTED,
** Full external access to system (su command) [if not, will drop errors like "Operations not permitted" or "file system is mounted read only")
** USB Debugging is enabled,
** Connected using USB and all USB drivers are installed/working.
* You might need administrative privileges in Windows to fully run the program.
* If you're running your device from recovery, you may need to mount /system/ folder before running the script (Partition tools > Mount /system).
- It's still not working.
* Drop a message in the official thread.
* If you get errors about file system Read only, try to run your device in Recovery mode, and fix permissions.
- Will the script create lots of files/make a big drive footprint ?
I hate programs creating lots of temp files. So, the script was developped to create files AND to clean/remove them all once everything is done. Even if it crashes without removing files, you just need to restart the script - it will clean all previous temporary files.
If ADB is run, it WILL be fully closed once everything is done. Server will be killed, then ADB process (named adb.exe) will be killed. Your system will be as clean as it was before running the script.
The script is of course fully portable : there's no installation needed. You can put the script where you want, but you just need to keep all script files/folders in the same folder.
In a future release, I'll add something to purge the log file.
- Which OS is supported ?
It's developped in Windows 7 x64. You should be able to fully run it on any 2000+ Windows NT OS.
As it is NT script, it will work only on Windows computer. It will also not work properly on pure DOS (it's using NT commands and Windows-related commands not included in older Windows NT systems, like NT4).
Report if you tested it on other Microsoft OS (NT 4, Windows 95, 98 or 2000, Dos 6.22...)
- I wanna contribute.
Just right click the .cmd/bat files, edit them with Notepad or anything you want
You can also send me a message (thread or PM) if you notice some piece of code I can improve with other commands (I don't know DOS commands enough )
v1.0 (11/5/2011) = initial release
v1.1 (13/5/2011) = removed BFC tags, updated error 2 (ADB get-state, to help you identify problem), removed 3G tweak returns error 3 if not present (addon = not necessary), added template.bat to create add-ons, improved launcher.bat (add-on primitive detection), added add-on installation detector (displays backup/reboot options only when add-on was installed), corrected folder "\" bug
v1.2 (13 may formely 14/5/2011) = added automated deleter/file checker for 3G+ tweak. Still early stage but looks to work. Automated batch thanks to http://www.dostips.com
v1.3 (16/5/2011) = added 3G+ enhancement lite mode (for networks like AT&T) and removed 1 step on auto deletion, fixed bug of false error when trying to download from device a build.prop.bak not existing, added management options to Backup (send local backup to device, delete backup on device), solved backup internal error
v1.4 (29/5/2011) = fixed window console size, enhanced menus, faster script closing, log file generator, several bugs fixed, enhanced help (readme in Notepad, direct open XDA thread in Firefox), added adb.exe process killer
v1.5 (6/6/2011) = added console title, fixed some menu bugs, updated Readme, weblinks now open in the default user browser, build.prop will now open in default notepad editor, improved interface, fixed unexpected exit bug, added contact me using default email (still experimental)
v1.6 (15/6/2011) = improved ADB process killing, deeply improved 3G tweak script with sed and no more TXT file, readme opens in your default editor, improved interface, updated template, unified common subroutines into BAKengine.bat, user-friendly explorer of build.prop (not great for now), deleted Substengine (deprecated), "0" in menues now refers to Go Back/Exit, improved missing engines detection, added general temp/log file purger/deleter ** To celebrate The Legend of Zelda series 25th Anniversary, my script is now tagged "Powered by Hyrule DOS"
DETAILLED 3G Addon update :
- detects presence of previous installation and files
- Sed command : fastest detection and subtitute of lines
- Optimized for fastest operation and fully clean build.prop file
- Several stuff...
External SED support thanks to GNU Utilities for win32 @ http://unxutils.sourceforge.net/
v1.7 (26/7/2011) = fixed no deletion of TEMP folder/files, fixed ADB command not found, new entries for XPlorer
Known bugs :
* (Main) Will not detect if build.prop.bak and build.prop.old are the same (not very important, I'll improve this later)
* Report anything you find
Click to expand...
Click to collapse
Hey mate...
lovely piece of work..!
saved me hours at my work...
thanks a lot works flawlessly on
sony xperia tipo dual with cm 10
Ur da bomb
As you probably already know, you are DA BOMB, BABY!
I just [snicker] used your tool to save my rather idiotic...er, 'brain' from suffering through a dumb, hard night re-flashing SlimKat 4.4.2 back onto my LG Optimus G e970 just to fix something I should've never done to begin with (change screen density to make it easier to read, of course, but without really knowing what I was doing)...
aherm...well, anyway, here I sit at a pre-midnight hour thanking you profusely, sir, because, as I said at the start...
UR DA BOMB!!!
Here's hoping you get bored a lot more often...it's a keeper, fer sure.:victory:
Good work dude... Nice toolkit, loved it very much... I am integrating your tool into my new upcoming toolkit. Dont worry i am not gonna steal it, will just use it. Will surely give you proper credits for that
Does this work with the stock recovery without root?
My device: Xperia XA2
thanks for this useful helper. i know how to modify build.prop - thats not the reason why i came here. what i don't know is the meaning of all this different entries in build.prop for example ro.expect.recovery_id - which there was a catalog with information about included in a build.prop Tweak GUI
sorry but the program cant detect/ acces build.prop
my device is rooted, has debugging on and is connected via USB
plz help

[INFO] dsixda's Android Kitchen (added ICS support)

dsixda's Android Kitchen
(The thread closed, but thankfully updated)
[KITCHEN][November 30 '11] Android Kitchen, v0.180 [Linux / Mac / Windows]
...This project was retired two months ago, but today I added some Ice Cream Sandwich (Android 4.0) support as a favour for some people. Unfortunately I have permanent damage to my right wrist and cannot continue updating like I used to. So please, no more requests.
Click to expand...
Click to collapse
Code:
===================================================================
Android Kitchen - by dsixda (xda-developers.com)
===================================================================
Main Menu
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
0. Exit
There is also support for the following non-HTC devices
Code:
...
Samsung Nexus S / Nexus S 4G
...
dsixda's Profile

"Roll your own" SKINNY MIUI - Revised 09/04/16

Skinny MIUI is all about preserving the good; Working premium drivers for Camera, CPU control, Notification LEDs, Bluetooth, FM Radio etc. while resolving what is bad in the stock offering.
All deletions assume the user has absolutely no interest in being part of the Xiaomi ecosphere. Leave now if that is not you.
This guide applies to MIUI stable versions 7.1.1 thru to 7.2.5 only. Developer, Beta or Eng versions are not good candidates.
STAGE 1:
Boot.img mods: (this is not creating a custom kernel!!!)
The stock boot.img is unpacked, init.d support added and many entries that are not relevant to our hardware removed.
Disabling lines trying to load non-existent services from init.rc, init.mt6795.rc and ueventd.rc etc. stops a bit of churning on each and every boot and frees up a bit of RAM.
There are intentionally no other tweaks contained within the boot.img. All tweaks are done in init.d scripts accessible outside the boot.img.
Note: This boot image made from 7.1.4 will work back to ver 7.1.1 and forward to 7.2.50 / 6.3.31 and is superior to the stock boot images contained in those ROMs.
At this point you can flash the modified boot.img to your phone if you already have a stock MIUI 7.1.1 to 7.2.50 installation that you are going to keep.
If you are going to do a clean install, replace the boot.img in your ROM zip file with this modified one. (backup the original first)
The boot.img is found here: (Now links to folder with all versions available)
https://drive.google.com/folderview?id=0BwdRTuyj12_yRk9Kcm1pZkxuZzg&usp=sharing
STAGE 2:
Full install:
I recommend you install my TWRP 3.02-2 version from here:
https://drive.google.com/open?id=0BwdRTuyj12_yWWp0SUpGV1pzT1k
Before installing your chosen ROM:
Check that the updater script found: \META-INF\com\google\android\updater-script is not going to install Preloader, Uboot (lk), Recovery or logo partitions. If so, edit the updater-script to prevent this happening. This is to reduce the risk of a soft-brick or being locked out of your phone.
Do a factory reset in TWRP (wipe Data, Dalvik, Cache) before installing any ROM.
Install your chosen ROM. Trying to slim down the ROM before install is an arduous affair which tends to end in bootloops so we leave the original ROM alone in this respect..
Do the install without connecting to mobile or WiFi networks and just skip at screens prompting for network connectivity and creating accounts.
Reboot into TWRP once finished with the initial Setup to avoid Recovery from being deleted on first boot.
Install an updated SuperSU zip package from TWRP recovery - V2.46 to 2.71 work equally well.
Do not install a root package other than SuperSU - most online ones are malware!
Update the outdated and incomplete Busybox installation. I have created a TWRP flashable zip to upgrade to the latest version 1.25.0. This is the second edition which has better binaries and no longer creates symlinks to busybox commands.
https://drive.google.com/open?id=0BwdRTuyj12_yd0s1QmNLRzdveFk
Now install a root capable filemanager (Root Explorer or Total Commander recommended). Open it and gain root permissions. Open /etc/perfservscntbl.txt in a text editor and edit as follows:
Code:
CMD_SET_CPU_FREQ, SCN_APP_TOUCH, 403000
CMD_SET_CPU_CORE, SCN_APP_TOUCH, 1
This will lower the number of cores used and the frequency at which it runs when a screen touch is detected (referred to as Touch Boost) Changes are activated on reboot.
Now create a file named 01_tweaks in the /etc/init.d folder. Change the permission of the file to 0755
Tips on creating scripts:
The EOL(end-of-line) characters must be in Unix format - not Windows. Make sure you are using a text editor that saves in Unix format.
Note also that many script files need a blank line at the end to work correctly. Get in the habit of always doing this whether needed or not.
Any line starting with a # character and anything after a # character on a line is not processed and is referred to as "commented out"
Script files must start with the header #!/system/bin/sh as the first line.
Init.d scripts are processed in alpha-numeric filename order hence the common usage of 01_xxx, 02_xxx format for names.
Copy these lines into the 01_tweaks file: Note: Different values for 2.2GHz cpu and freq limited operation.
Code:
#!/system/bin/sh
### Tweak Interactive CPU Governor
echo 806000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo "90 403000:80 806000:85 1326000:90 1625000:95 1950000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 32000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 10000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 15000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo 20000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
### Tweak IO Scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler ### choose between cfq, bfq or deadline
### Enable this line if using cfq or bfq scheduler only
# echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle
echo 256 > /sys/block/mmcblk0/queue/read_ahead_kb
### Enable zram swap
# echo 1073741824 > /sys/block/zram0/disksize ### 536870912 = 512MB 1073741824 = 1GB
# /system/bin/tiny_mkswap /dev/block/zram0
# /system/bin/tiny_swapon /dev/block/zram0
### Tweak Entropy to avoid regular depletion of available pool
echo 512 > /proc/sys/kernel/random/read_wakeup_threshold
echo 1024 > /proc/sys/kernel/random/write_wakeup_threshold
#Tweak for wifi router connection issues
#echo 1 > /proc/sys/net/ipv6/conf/wlan0/disable_ipv6
### FSTRIM: Enable once after installation is finalized and then monthly ##### needs an updated busybox installation to work
# busybox fstrim /data
# busybox fstrim /cache
# busybox fstrim /system
Options: Add / replace lines to do the following:
1. freq limit a 2GHz cpu to 1781MHz (recommended setting)
echo "90 403000:80 806000:85 1326000:90 1625000:95 1781000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 1781000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1781000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user
2. Full speed 2.2GHz cpu
echo "90 403000:80 806000:85 1326000:90 1664000:95 2158000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
3. freq limit a 2.2GHz cpu to 1885MHz (recommended setting)
echo "90 403000:80 806000:85 1326000:90 1664000:95 1885000:99" > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 1885000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1885000 > /proc/cpufreq/cpufreq_limited_max_freq_by_user
4. Add a limit to the maximum number of cpu cores allowed to come online (for possible battery saving maybe...)
#Limit max cpu cores available (range 2 - 8)
echo 4 > /proc/hps/num_limit_low_batt
echo 4 > /proc/hps/num_limit_power_serv
echo 4 > /proc/hps/num_limit_thermal
echo 4 > /proc/hps/num_limit_ultra_power_saving
Edit /system/build.prop. Change the line: ro.sf.lcd_density from the default 480 to a value between 400 (everything smaller, more on screen) to 520 (everything larger, less on screen) to suit your taste and eyesight. You can test this out first by issuing the wm density command in a terminal app. e.g wm density 440 will immediately change the density to 440dpi, wm density reset will put it back to whatever the build.prop setting is. Adjust the text size in Settings in conjunction with this to get the best result.
At this point you have a functional set of tweaks that are all tested and proven to provide a battery and performance improvement. There are a lot of detrimental or placebo tweaks out there so be a little bit discerning in what else you add to these tweaks - sometimes less is more. Now is not the time to load up those tweaks!
Do a TWRP backup of System, Data, Boot and NVram partition now to save your efforts up to this point.
STAGE 3:
Now its time to get Skinny: You will need an app that can uninstall and freeze system apps. I use SD Maids App Control feature for this purpose.
Warning: If you intend to use app lock, you will unfortunately need to keep some fingerprint service files. See the post below and a few before it to understand the problem. Thanks to @DarthJabba9 for his work.
I believe that app lock also disables MIUI Optimization if enabled.
http://forum.xda-developers.com/showpost.php?p=67242356&postcount=583
First phase is to get rid of the obvious bloat apps and Xiaomi in-house apps....these in the list below are safe to remove.
Tick off what you have removed and reboot each 10 or so deletions and backup, don't try to delete everything in one hit as you will end up stuck at boot.
WARNING: This removes some functionality that may be useful to some users. You either want the function or you don't - it is your finger pressing the buttons!
Some people may choose to keep the MIUI Home Launcher interface. In this case, keep MIUI Wallpaper as well.
Must keep these - Do not delete:
Updater - disable autostarts, do not freeze
Theme Manager - disable autostarts
Security (com.miui.securitycenter) - leave as-is
FwkPlugin
Network Assistant app
MiuiSDK - disable autostarts
AuthManager
Webview (update via Playstore once install finished)
Xiaomi service framework - disable autostarts, freeze app
Definitely O.K to delete list:
Wallpaper Apps:
Android Live Wallpapers
Black Hole
Bubbles
com.android.wallpaper.holospiral
Live Wallpaper Picker
Music Visualization Wallpapers
Phase Beam
Photo Screensavers
*Miui MiWallpaper * keep if also keeping MIUI Home Launcher.
Xiaomi/MTK Apps:
Analytics
Assistant
Back up Home screen layout (cloud backup)
Backup - delete if you don't use it (use TWRP instead)
Battery Warning - deleting this does not affect battery charging or display
Battery Saver - deleting this improves battery life
Blocklist (AntiSpam) - delete if you don't use it
com.miui.mipub
File Explorer - delete (you should already have a root capable file browser)
Find device - use the generic Google version if you really must, not the Xiaomi one supplied.
FingerprintService
FPCSensorTestTool
FTPreCheck
FWUpgrade
gallery (com.mfashiongallery.emag daily wallpapers)
Games
Home screen
JeejenMIUIContainer
com.securitycore.miui_t (Tencent virus scanner plugin to Security Center)
KLO Bug report
LocationEM2
Metok
MI Account
Mi Cloud
Mi Credit
Mi Drop
Mi Home
MI Service Security Framework
Mi VIP
Mi Voice
Mi Wallet
Miravision
MTKAndroidSuiteDaemon
MtkFloatMenu
MTKLogger
Music
MusicFx
Notes - if you don't use it, delete it.
PowerKeeper (Battery Saver) - deleting this improves battery life
Report Bug
Security service plugin (not securitycenter app)
SystemAd
System Launcher (Miui Home) replace with an alternative Launcher, allow autostart in Security first then delete. ADW Launcher recommended for lightweight and simple functionality (set to 4x6 looks good).
Traffic Control
Uniplay
UpgradeSys
VCalendar
Video
Voice Unlock
VoiceAssist
Weather
Weather provider
Whetstone delete app and delete folder /etc/WhetstonePermission ****Whetstone is linked with several other apps to make it hard to get rid of. It may cause some temporary FC issues - these will pass.
Xiaomi Assistant
Yellow Pages
com.jeejen.knowledge
com.jeejen.store
com.ximalaya.ting.android
com.xiaomi pass
com.xiaomi.o2o
com.xiaomi.jr
Cheetah Mobile CleanMaster SDK + Cleaner - delete
NetworkLocation (com.baidu.map.location) delete app, delete folder: /system/vendor/operator and delete corpses
Android/Google Apps:
Browser - suggest replace with Polarity Browser - minimal permissions required, Ad Blocking, lightweight and fast
Documents
Google Keyboard - replace with something lighter - Hackers Keyboard v1.38.2 recommended
Google Pinyin input
Google Feedback
Google partnersetup
HTML Viewer
Email
Mail
Pico TTS
Print Spooler
com.android.browser.provider
PacProcessor
Note: If you have apps reappear as if by magic, they are being reconstructed from cached information. SD Maid has an excellent "Corpse Finder" function that will delete the orphaned files and prevent this happening. Clear corpses after each reboot.
Second phase is to toggle off the autostarts (receivers) on the apps that do not need to start by default. This is not the same as freezing an app. Some apps will still start by themselves - do not worry too much about this.
Atci_service
Backup
Blocklist
com.mediatek.batterywarning
Download Manager
Google Contacts Sync
Google One Time Init
MIUI SDK (don't freeze)
MTK NLP Service
Notes
One Time Init
Sim Toolkit
Themes (Theme Manager)
Updater
Xiaomi service framework (should also be frozen)
Third phase is to clean up left behind folders and files
/data/miui/app/customized/ remove any app folders that you have uninstalled
/data/miui/app/noncustomized/ remove any app folders that you have uninstalled
delete folder /data/miui/mms
delete folder /data/miui/gallery
delete contents of /data/miui/cust
delete folder /etc/jeejen
delete etc/voicecommand and etc/voiceextension folders if you have removed voice related apps
delete /system/tts folder if you have removed Pico TTS
delete folder /system/etc/radv
/etc/fake_cdrom_install.iso - delete file
/etc/IAmCdRom.iso - delete file
/system/addon.d delete folder
/system/app/jjcontainer/ - delete folder
/system/app/jjhome/ - delete folder
/system/app/jjknowledge/ - delete folder
/system/app/jjstore/ - delete folder
Libs you can remove:
/vendor/lib
libfingerprint_tac.so
libfpcalgorithm.so
/vendor/lib64
libcom_fingerprints_productiontestmanager.so
libcom_fingerprints_sensor.so
libfingerprint_tac.so
/system/lib
libcaFingerPrintShared.so
libcom_fingerprints_service.so
libfamily_jni.so
libjeejenAisound.so
libjeejenmsc.so
libMiraVision_jni.so (if deleted MiraVision App)
libpatcher_game_jni
libvoicerecognition.so (if voice recognition apps deleted)
libvoicerecognition_jni.so (if voice recognition apps deleted)
libweibosdkcore.so
libwhetstone_jni.so (if deleted Whetstone App)
libwhetstone_sdk.so (if deleted Whetstone App)
libxiaomimediaplayer.so (if xiaomi media player deleted)
libxiaomimediaplayerwrapper.so (if xiaomi media player deleted)
/system/lib64
libairtunes_jni.so
libairtunes.so
libBankCardRecognizer.so
libcaFingerPrintShared.so
libcom_fingerprints_service.so
libduokantext.so
libjni_latinimegoogle.so (if deleted Google keyboard)
libjni_pacprocessor.so (if deleted PacProcessor)
libMiraVision_jni.so (if deleted MiraVision App)
libpatcher_game_jni.so
libttspico.so
libweibosdkcore.so
libwhetstone_jni.so (if deleted Whetstone App)
libwhetstone_sdk.so (if deleted Whetstone App)
libxmpass_sdk_patcher.so
xmpass_libweibosdkcore.so
Establish network connectivity.
If Gapps is required but not installed, download open_gapps-arm64-5.0-pico version. You can install individual extra Google apps at any stage later on.
Go through all MIUI Settings and turn off everything you do not need running.
Install your favorite media player, web browser etc. to replace the deleted original apps.
Can replace Calendar and Messenger with Google Calendar and Google Messenger to remove some more Xiaomi dependencies. Contacts & Dialer are much harder to replace - True Phone is the only viable option.
To further limit Xiaomi unsolicited communications, rename (or delete) /system/xbin/tunman to tunmanbak. (This is a tunneling protocol driver that Xiaomi uses without your knowledge or permission).
The startup is disabled in the boot.img but it can still be started after boot unless renamed.
To skinny the Themes footprint:
Go to /system/media/theme/
Delete elder-default folder if no use.
Delete entire contents of miui_mod_icons folder
Delete items in /system/media/theme/default/ that are not going to be used.
Delete items in /system/media/lockscreen/ and /system/media/wallpaper/ that are not going to be used.
Now install your favorite app for monitoring CPU parameters and make sure that on idle, there is only one cpu core running and it sits predominantly on 403MHz. It will jump a little bit but that is normal with the inevitable background activities. Increase the timer_rate if you want more stability at idle rather than cranking up the load figures too far. Up to 50000 or down to 30000 is O.K (remember we are talking microseconds here so 50000 = 50mS)
Congratulations! You now you have a "Super Skinny" MIUI installation. Do a backup now!!!!
Now you will feel the AOSP shining through - and still you have working everything!
This post will list useful tools and items that need further investigation.
Apps for finding and disabling things:
Wakelock Detector-Root - monitor and records wakelock activity
GSAM - monitors what apps / services are consuming battery
Disable Service - disable services started on an app by app basis
SD Maid, Titanium Backup - Freeze / remove apps, toggle autostarts (receivers)
Modify your quick start grid size:
https://drive.google.com/file/d/0BwdRTuyj12_yYlphU3A0UWprcXc/view?usp=sharing
Modify MIUI Homescreen grid:
https://mega.nz/#F!yJdkxbBa!WSIqrhwUQwD7qjzxOuo1Yw
Issues:
Find a way to completely disable XMPush service with and without Xiaomi services framework installed.
Xiaomi Services Framework causes Sim connectivity issues if deleted - do not delete. There will always be one XMPush instance running.
Find out what is causing Audio On wakelock reported by GSAM
Quote: Originally Posted by DarthJabba9
With regard to the "Audio On" wakelock (aka AudioMix Wakelock) reported bt GSAM, I found this somewhere in this forum: "The nexus 6 had the same wakelock and most of us got rid of it by unchecking "use NuPlayer" in developer options". I have now unchecked that option, and will see over the next day or so whether it resolves the problem. This appears to be the fix
What triggers no sim / no service errors
Removing Xiaomi Services Framework is the culprit
Why do some files / folders not show up in root filemanagers?
MIUI locks the files / folders to prevent them being used or shown.
Why does zram not work anymore?
Rename tiny_mkswap, tiny_swapon, tiny_swapoff to teeny_mkswap, teeny_swapon, teeny_swapoff
Make sure owner is root shell and permissions are 0755 for all 3 files.
edit the init.d script to reflect the change in filenames. Now it will work again!
Example full Skinny ROM based on MR7.2.30 ID:
This is how my phone is set up, it has 100% functionality, zero FCs and zero battery drain on idle. The init.d settings are exactly as provided. Compare the directory listings to your own to see what is deleted.
The other major variation to this is for people who want to keep MIUI Launcher (and MIUI Wallpaper), everything else should remain the same. This cost you a bit more RAM usage and slightly more cpu activity (less battery) but is still impressive compared to stock.
/system/app
ApplicationsProvider
AtciService
AutoDialer
BSPTelephonyDevTool
Bluetooth
CaptivePortalLogin
CertInstaller
DeskClock
DownloadProviderUi
DrmProvider
EngineerMode
EngineerModeSim
FM
GoogleCalendarSyncAdapter
GoogleContactsSyncAdapter
KeyChain
MTKThermalManager
MiuiCompass
NetworkAssistant2
NlpService
Omacp
PackageInstaller
Provision
SuperSU
SystemHelper
ThemeManager
Updater
UserDictionaryProvider
WebViewGoogle
XiaomiServiceFramework
YGPS
cit
mcRegistry
miui
miuisystem
/system/priv-app
AuthManager
BackupRestoreConfirmation
BarcodeScanner
CDS_INFO
CalendarProvider
ContactsProvider
DefaultContainerService
DownloadProvider
ExternalStorageProvider
FusedLocation
GoogleBackupTransport
GoogleLoginService
GoogleOneTimeInitializer
GoogleServicesFramework
InCallUI
InputDevices
ManagedProvisioning
MediaProvider
MiuiCamera
MiuiGallery
MiuiKeyguard
MiuiSystemUI
MmsService
OneTimeInitializer
Phonesky
PrebuiltGmsCore
ProxyHandler
SecurityCenter
Settings
SettingsProvider
SharedStorageBackup
Shell
Stk1
TeleService
Telecom
TelephonyProvider
VpnDialogs
WallpaperCropper
com.ghisler.android.TotalCommander ### Total Commander installed as system app
com.hb.dialer.free ### True Phone replacement for Xiaomi Contacts & Dialer
org.adw.launcher ### ADW Launcher installed as system app
Other base apps in /data/app:
com.google.android.apps.messaging ### replacement Google Messenger
com.google.android.calendar ### replacement Google Calendar
com.duokan.phone.remotecontroller ### stock IR remote controller app
pcr.browser.polarity ### Polarity Browser
com.grarak.kerneladiutor ### Kernel Adiutor * disable autostarts*
org.pocketworkstation.pckeyboard ### Hackerskeyboard-v1.38.2 replaces Google keyboard
jackpal.androidterm ### Android Terminal
Thanks a bunch for the info. This is exactly what I'm looking for (my slimming down attempts always resulted in bootloops, so I've been playing it pretty safe so far).
Is this something you repeat every time an update is being pushed to your RN2?
@elaurens By doing this you are forgoing the use of OTA Updates which will unravel everything you have achieved.
I had to go through quite a few bootloops before creating the "safe lists" - I suffer so you can all benefit.
If you are starting with 7.1.4 everything is perfect and needs no more updating
Keep your eye out for additions to these lists as I discover or remember them
I have tried this:
http://forum.xda-developers.com/red...d-enable-clearmotion-miui-based-roms-t3278552
to enable ClearMotion and can vouch for it being safe - as in no malware and no breaking things. It adds the following to Build.prop and puts some hacked drivers in /system/lib.
persist.sys.display.clearMotion=1
persist.clearMotion.fblevel.nrm=255
persist.clearMotion.fblevel.bdr=255
ro.mtk_clearmotion_support=1
ro.mtk_slow_motion_support=1
ro.mtk_16x_slowmotion_support=1
Is this a worthwhile thing to do? There are no negatives in doing so as far as I can see but I don't really have anything that can give this a proper workout.
Can anyone see a difference in video playback? (Must have hardware acceleration selected) I won't recommend this if there is no perceivable gain.
most of the stuff works fine, everything checks out, It's not really anything new, but i find it well written, and it's not just a "placebo build.prop tweaks edit" which is a +. its a smart thing to have it all in a single thread.
however there're some issues with init.d script. even if you get init working, sometimes it just simply wont apply any of the tweaks. interestingly enough, i forced it to create a new text file on every boot, and that works. not really sure whats causing this prob.
anyways, by some magic I eventually made it apply the script, not really sure if it was cause of the rom change, or just pure luck lol
@sikica133 and anyone else having init.d problems:
init.d problems are usually one of the following:
1. incorrect folder permissions.
2. incorrect file permissions
3. No line feed at the end of the file (blank line)
4. incomplete or missing Busybox install
5. missing header in the text
6. Loosing SU privileges
Check init.d folder has 0755 permissions
Check file has at least 0644 permissions
Check and/or insert a line feed at the end of the file
Install busybox on rails, run the cleanup and busybox install, uninstall busybox on rails after this (this gives you an up-to-date and more complete busybox installation)
First line of file must be exactly #!/system/bin/sh
Reinstall a fresh version of SuperSu through TWRP
I sometimes get caught out myself by editing a file on the PC and transferring it back without fixing permissions afterwards:silly:
I have the ultimate build.prop tweak that I will share with you all now, stand back, it is very powerful
persist.sys.use_qualcomm_performance_features_instead=1
nah, i was testing it with a updater-script doing 0755 on all scripts. busybox should be fine cause other scripts did their job. dunno, could be some funny issue on my end. works now, i was just wtf, everything works, this doesnt. no idea what was going one tbh, but it works
could be incompatibility with bbox and the script itself? im running it without feedline atm, and it applies it all. same script i used before when it didnt do anything.
MIUI 7.1.4 and I assume all other versions has a very old and incomplete version of busybox installed (I think it was v1.20?).
It does not have fstrim command (plus a few others) included which is why I recommend updating.
I tried init.d and 01_tweaks script (whith correct permissions).
The system is more time in 806 Mhz., deep sleep not works properly.
I use Stable 7.1.1 .
Deleting script, deep sleep works fine.
Need I install or update busybox for resolve my issue?
@Xabadou This script is the starting point. If you do not "skinny down" MIUI, there are so many things running in the background that you will find it difficult to sit on idle frequency.
How far into skinnying down have you gone?
Also, if you have a 2.2GHz cpu, the 2nd line below frequencies in bold must be modified to valid frequency for that cpu.
If you are not going to skinny down to a great extent, then it helps to bump some of the load settings up a touch.
These are the original lines:
echo 80 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 90 403000:70 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
# for 2.2GHz cpu: echo 90 403000:70 806000:81 1183000:84 1326000:87 1482000:90 1664000:93 1885000:96 2158000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
Modify to:
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 95 403000:75 806000:81 1183000:84 1326000:87 1469000:90 1625000:93 1781000:96 1950000:99 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
This is enough to get it to sit on 403MHz idle in most cases. If you go higher, you will start compromising smoothness. There are no problems at all with entering deep sleep.
If you are still having problems, you have an app running that is badly behaved - identify it and deal with it.
Refer back post #10, I mention why you should upgrade busybox.
I am running my phone beyond Super Skinny and loving it. Super stable and battery friendly while still being a performance beast. You should notice even at the point of trimming down to Skinny, this phone really starts to liven up.
jajk said:
I am running my phone beyond Super Skinny and loving it. Super stable and battery friendly while still being a performance beast. You should notice even at the point of trimming down to Skinny, this phone really starts to liven up.
Click to expand...
Click to collapse
Do you have a list of the apks (and directories) that you deleted in order to get the skinny ROM? Such a list would be useful for writing a script to automate the task.
P.S.: you might have noticed that I am a script fanatic - I generally find that it is less error-prone to automate such tasks with a script - and you only need to get the script right once.
I use stable 7.1.1 by xiaomi.eu whith your modded kernel and a lot of apps frozen (App Quarantine).
Modified kernel works very good.
Just now I have updated busybox.
I have 2.0 ghz version.
I will try again the script.
Clear Motion mod works fine in MIUI roms but you must use MX Player for play videos.
---------- Post added at 01:20 PM ---------- Previous post was at 01:11 PM ----------
persist.sys.use_qualcomm_performance_features_inst ead=1
Works qualcomm tweaks whith mediatek processors?
@DarthJabba9 The lists ares already mentioned - 1 to get to skinny, 1 to get to super skinny but if you do this in a script on a live system you will likely end up in a bootloop because there are too many odex and cache entries orphaned for Android to handle in one hit. If you intend to apply a script to the ROM files before installation, that is a different story. It takes a bit of effort to figure out how and where MIUI is loading a lot of its components from but is doable.
Why I have not offered a complete ready to go package? It is too easy for users to do it themselves and add their preferences along the way. For those that have actually followed through with the process, I can guarantee that they will instantly loose interest in any other custom ROM.
@Xabadou Thanks for the clarification on ClearMotion. I run VLC set to hardware acceleration and can't see the split screen test mode. Video looks fine regardless, so really hard to tell if anything has changed.
Do the apps that you quarantine stay not running? I had problems with quite a few apps running regardless of being frozen or not so had to uninstall.
You, along with everyone else are not running a modified kernel - the kernel remains intact since we do not decompile and recompile or compile it from source.
The "persist.sys.use_qualcomm_performance_features_instead=1" tweak is a sarcastic dig at the many tweak offerings that do absolutely nothing:silly:
You asked the question showing you were not ready to accept this at face value:good:
If there is no evidence of a tweak doing something positive, don't blindly use it!!!
This is a customized boot image that provides init.d support and has unnecessary entries removed. No tweaks are embedded.
It is built on 7.1.4 and can be used on stock 7.1.1 to 7.1.4.
https://drive.google.com/file/d/0BwdRTuyj12_yR3phb0Zxd05UQjQ/view?usp=sharing
credits to @DarthJabba9 for the alternate init.d support method adopted in this image. It circumvents using busybox run-parts method that appears to have some bugs.
jajk said:
@DarthJabba9 The lists ares already mentioned - 1 to get to skinny, 1 to get to super skinny but if you do this in a script on a live system you will likely end up in a bootloop because there are too many odex and cache entries orphaned for Android to handle in one hit. If you intend to apply a script to the ROM files before installation, that is a different story. It takes a bit of effort to figure out how and where MIUI is loading a lot of its components from but is doable.
Why I have not offered a complete ready to go package? It is too easy for users to do it themselves and add their preferences along the way.
Click to expand...
Click to collapse
Fair enough ...
jajk said:
I will share my custom Super Skinny MIUI boot.img based on MIUI7.1.4 since it is now stable ... It is unpacked and repacked using AndroidMasterChef (downloaded from Needrom). I do not have problems unpacking and repacking again. If you try to unpack and have problems, use the same tool.
Click to expand...
Click to collapse
Thanks for the image. It cannot be unpacked with standard linux tools, but it unpacks ok with AndroidMasterChef.

MTK Tools - An Application for Android Generic Devices

Disclaimer - I (KP) takes no responsibility for any fault or damage caused by using the MTK Tools. No warranties of any kind are given. Use at your Own Risk
Click to expand...
Click to collapse
Check Attachment for Images : :
Hey Gyzz This is my another Toolkit not only for coolpad but also for all android devices running mtk processores. What it can do is based on how you use it. SO read the instructions carefully while using the toolkit.
With This Tool you can easily able to hack into your phone with not an only ease process but also a simple gui interface tool for your phone. Give a try. If you like you can freely donate my work, so that i could make this site a an independent domain
# # Basic Tips to use # #
1. Make sure while using any option move your cursor onto it, to display its information.
2. If toolkit suddenly doesn't respond, make sure you first End its process from task manager then contact me from the toolkit - that why this happen (log)
3. Do not jump onto the options quickly, wait till the first process gets over.
4. That's it, ENJOY
# # Features # #
Let’s Talk About, What it can Do:
*Basic Options for Listing Device in ADB Mode or Fastboot Mode
*Get Full Device Info including CPU Information (all grab from build prop)
*Check Device Encryption, to view it ro.secure.model (Note if it is set to 0 you would not able to root and flash anything onto device)
*Get Whole Advanced Reboot Option (Reboot, Recovery, Bootloader and viceversa)
*Unlock And Relock Bootloader (Any Android Devic, basic method)
*Wipe Data And Factory Reset Phone, Simple via Fastboot
*Wipe System Partition like Dalvik cache, boot, recovery, System (One click)
*Install Root for Android 4.0+ and also 6.0+ via Sideloading
*Replace Kinguser with SuperSu, Fix Root and Any SuperSu error
*Universal Unrooter (guide)
*Install BusyBox App (One Click)
*Flash BusyBox via recovery (Ease)
*Flash Stock Firmware Image
-Boot
-Recovery
-System
-Radio
-UserData
-Cache
*Flash Zip files & Roms by Sideloading or by TWRP tweaks(Best One)
*Install Apk Directly via Toolkit
*Reset Pattern Password (Both Root & Non-Root Devices)
*Build Prop Mods
-Built-in Editor
-Prop Toolkit by Perceval & Hyrule @xda
-Install Build Prop editor Mods
*Android File manager (Copy, Move, Delete, Transfer Files and Do a lot of stuff)
*App Manager for Listing Packages & Targeting package
-Uninstall App
-Kill app
-Clear App Data
-List App Permissions
-Disable & Enable System Apks
-Pull an App to pc and save anywhere you want
*Save Battery Mod Option (This will force-stop all application running in background including some system apps)
*Capture Your Screen Shot without touching the phone
*Record your Android Screen with higher FPS and with Editable Bit-rates and Resoultions
*Tweaks For Android
-V6 SuperCharger (Pre-activated only run it Once)
-TweakDrypT Mod Script (A Script which will Increase Phones Performance by patching some libs, etc)
-Dolby Atmos (A mod which will Enhance System Volume leveler)
-Fly on Mod (An Apk Designed for tweaking android : read posts)
I found this much mod scripts, if you have more contact me I will add it
*Install Important Drivers (Universal ADB, Google USB & ADB/Custom one)
*Set Fastboot Vender ID
-No serial (For android 4.0.0+ and low sometimes)
-Default one (-i 0x1EBF : For Coolpad and some chinese phones)
-Custom Serial (Set your Own : Check this on web)
*Open Command Window and Android Shell Terminal
*Backup & Restore Options (For android 4.0.0+)
-Full App and Data
-Whole Device (-all)
-System (-system)
-Set Custom Backup name
-Restore using Advance Options
*Help And About Sections for
-Informations
-Checking for updates
-Contacting us
-Visiting main web for More Info and Plugins
-- Will add more
# # DOWNLOADS # #
MTK Tools Website :- Link removed
1. Go the main webpage from the video description
2. Head to release section and download the initial release...
All info provided in the video, watch the whole video
Like my WORK you can Donate me via Paypal or Via Directly Paytm on :- +91 7208565164
Any Bugs, Contact me
XDA:DevDB Information
MTK TOOLS, Tool/Utility for all devices (see above for details)
Contributors
[email protected]
Source Code: mode edit - links removed
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-01-05
Created 2017-01-06
Last Updated 2017-01-06
ChangeLog
ChangeLog
version 1.0 (January 5, 2016)
*Initial Release

Categories

Resources