{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PDroid allows blocking access for any installed application to the following data separately:
Device ID (IMEI/MEID/ESN)
Subscriber ID (IMSI)
SIM serial (ICCID)
Phone and mailbox number
Incoming call number
Outgoing call number
GPS location
Network location
List of accounts (including your google e-mail address)
Account auth tokens
Contacts
Call logs
Calendar
SMS
MMS
Browser bookmarks and history
System logs
SIM info (operator, country)
Network info (operator, country)
For device ID, phone and mailbox number, SIM serial, subscriber ID and device location it also allows supplying custom or random values.
Why you would want to use it:
Applicaitons do NOT crash when access to private data is blocked (unlike with Permissions Denied or CM)
Fine-grained tuning of access to private data
No background service needed
Very small memory footprint (~700KB)
No impact on battery life
No impact on performance (5ms overhead on access to private data; yes, that's 0.005s)
100% reliable unlike ROOT applications (LBE), which need to start their background service on boot (see android underground to learn why this is an issue)
No ROOT required for the app to run
No Android permissions required for the app to run
Open-source
Download:
Automatic PDroid Patcher for Windows (XP/Vista/7):
JDK 6 or newer is required (get it here http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.html)
Install JDK 6 into the default directory (don't change anything when installing)
.NET Framework 2.0 or newer required (ships with Windows since XP SP2)
Currently only supports Gingerbread (Android 2.3)
Will only work with deodexed ROMs (take a look into your ROM's system/framework directory; if there are any *.odex files, your ROM is NOT deodexed)
You will need to re-create your settings backup after updating from version 1.27 (it is not compatible with the newer version)
Download PDroid Patcher v1.32 Beta 0.321 for Windows
Patch Installation Requirements:
ROOTED device
For HTC devices: S-OFF ([TOOL] One click ENG S-OFF for HTC Desire HD)
ClockworkMod Recovery 3.0.2.6 or newer
If you "integrated sys Dalvik into ROM" with Titanium Backup, you will have to undo it
Installation Instructions:
BACKUP YOUR ROM (HOWTO)
Make a PDroid Patch for your ROM with the PDroid Patcher and put the patch on your SD card
Boot your device into your custom (CWM) recovery (Desire HD: vol down + power)
If you flashed the patch before but PDroid said it still was not installed, then select "mount /system"
Select "install zip from sdcard"
Select "choose zip from sdcard"
Select the PDroid patch you have put on your SD card
After flashing is finished, reboot the device
Install the PDroid app from the Android Market
Rate the app at the Android market (let me know, if you have any issues beforehand)
Patch Changelog:
1.32: Fixed updating from version 1.27 and below
1.31: Fixed patching incompatibility with some ROMs (like Zeus v5)
1.30:
Fixed the alarm being put to snooze every time a call is received or made
Fixed FC for some applications (like Yandex Maps)
Fixed bootloops for AT&T and SonyEricsson devices (hopefully)
Many small tweaks
1.27: Fixed an issue, where the Touchwiz launcher (and probably others) would continuously crash
1.26: Fixed an issue, which would make Google Listen and probably other apps crash
1.25:
Fixed an issue, where PDroid would conflict with some ROOT applications making them freeze
Fixed random geocoordinates generation
Fixed other minor bugs
1.22: Fixed the patch version reporting bug (v1.21 reports that it's 1.2)
1.21: Fixed the bug where the device would sometimes boot loop right after the boot is finished
1.2: Added data access notification feature
1.1: Bugfixes
1.0: Initial release
Source:
Download: PDroid 2.3.4 source (v1.27) (yes it is based on 2.3.4 but also works with 2.3.3 and 2.3.5 flawlessly)
Get the 2.3.4 source from AOSP (branch: android-2.3.4_r1)
Extract the patches from the above archive to the 2.3.4 tree root
Run:
Code:
patch -p1 -i build.patch
patch -p1 -i frameworks.patch
patch -p1 -i libcore.patch
Building from source:
Make a clean build
Apply the patches (see above)
Run:
Code:
source build/envsetup.sh
make update-api
mmm frameworks/base
mmm frameworks/base/services/java
mmm libcore
make snod
FAQ:
I do not have Market access, where can I download the PDroid app?
Click to expand...
Click to collapse
Right here
What about controlling the internet access?
Click to expand...
Click to collapse
Controlling access to the network/internet requires either patching the kernel or using ROOT access within the PDroid app. I try avoiding the former due to portability and the latter due to user privacy/security reasons. I am looking into adding internet access control in a way, which would be the most acceptable/convenient for the user. However, this feature currently isn't on the top of my to-do list.
How do I make a patch manually myself?
Click to expand...
Click to collapse
For experienced developers the following basic steps for creating a PDroid patch should be enough to get you started:
Make a clean AOSP build (2.3.4, assuming that your ROM is based on 2.3.x)
Make another build with PDroid sources added
Decompile the framework.jar, services.jar and core.jar files inside the system/framework directory (of both above builds) using apktool
Diff the output so that you know, which parts were changed by PDroid
Decompile the above three files from your ROM, you want to patch
Add the missing code to your ROM files based on the above diff
Recompile your patched ROM files using apktool
Do you plan on adding Froyo/ICS support?
Click to expand...
Click to collapse
Yes. But I have not ported PDroid to Froyo or ICS yet. No ETAs yet. You'll need some patience there.
Will you provide a public source code repository for PDroid?
Click to expand...
Click to collapse
I might, when I get some more spare time
Can I backup the privacy settings with TitaniumBackup?
Click to expand...
Click to collapse
Yes, however you will need to backup your settings to internal memory (PDroid preferences) before making a backup with TitaniumBackup. After restoring with TitaniumBackup, you will need to restore the previously backed up settings. Alternatively you can backup privacy settings to the SD card.
Can I use LBE Privacy Guard together with PDroid?
Click to expand...
Click to collapse
Yes.
I have applied the correct patch but my device does not boot, how do I find out what the error is?
Click to expand...
Click to collapse
Restore your backup
Get the Android SDK
Install it (you don't need the eclipse part)
Enable USB-debugging on your device
Connect it to your PC
Start ddms, which is located in the android-sdk-[platform]\tools directory
Apply PDroid patch
Reboot the device
When your device appears in the ddms window, click on it to see the system log
Filter the log by "error"
Watch the system log for errors and post them here
I have flashed a patch but I am having very weird issues I didn't have before (like you cannot unlock the SIM card or there are weird graphics etc.)?
Click to expand...
Click to collapse
Have you flashed other mods to your ROM? If so, PDroid is most likely conflicting with them. You will need to create a patch for your customized ROM.
Also make sure that you are using a patch appropriate for your ROM (the CyanogenMod patches for stable 7.1 will mostly not work on nightlies unless the link says so).
How do I make a patch for my device after I have flashed some other mods?
Click to expand...
Click to collapse
If your other mods DO NOT replace any of the three files: framework.jar, services.jar or core.jar in /system/framework, you can just create a patch normally based on your original ROM file.
Otherwise you will need to extract those three files from your device (use a root file manager or adb pull), put them into your ROM zip (also in /system/framework) and then create a PDroid patch based on the ROM zip.
Reserved, just in case
Yes. This is awesome
Great !
But I have a Desire... Just for Desire HD?
I believe you need root to push those jar files... so you do need root. right?
So this will not run at all times, and thus not kill the batterytime?
Sent from my HTC Desire HD using XDA App
Seems interesting, I'll be happy to test out this app if it releases for SGS2.
Sent from my GT-I9100 using XDA App
Sybregunne said:
I believe you need root to push those jar files... so you do need root. right?
Click to expand...
Click to collapse
Correct, that's what the description says
no_johnr said:
So this will not run at all times, and thus not kill the batterytime?
Click to expand...
Click to collapse
That's right. It has virtually no impact on battery life / performance.
hallydamaster said:
Seems interesting, I'll be happy to test out this app if it releases for SGS2.
Click to expand...
Click to collapse
Which ROM do you use? Which one is the most popular for SGS2?
Hi,
in where should i set the 3 files?
platform-tools?
fe22st said:
Hi,
in where should i set the 3 files?
platform-tools?
Click to expand...
Click to collapse
Anywhere, you can run ADB from. And yes, you can place them in platform-tools (I assume, your adb files are located there).
svyat said:
Anywhere, you can run ADB from. And yes, you can place them in platform-tools (I assume, your adb files are located there).
Click to expand...
Click to collapse
i get a issue after these commands:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
adb push DHD-services-gr5.mod.jar /system/framework/services.jar
adb push DHD-core-gr5.mod.jar /system/framework/core.jar
its looke like:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
cannot stat 'DHD-framework-gr5.mod.jar': No such file or directory
what can i do to fix that problem?
fe22st said:
i get a issue after these commands:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
adb push DHD-services-gr5.mod.jar /system/framework/services.jar
adb push DHD-core-gr5.mod.jar /system/framework/core.jar
its looke like:
adb push DHD-framework-gr5.mod.jar /system/framework/framework.jar
cannot stat 'DHD-framework-gr5.mod.jar': No such file or directory
what can i do to fix that problem?
Click to expand...
Click to collapse
You should run the commands from the directory, where you have extracted those 3 files.
Hi, great stuff! Have been following this for some time hoping for the first version to be released. Which you did! Bummer you do need root access for changing some files, I had hoped it wasn't necessary...
Anyhow: great tool, now just to find a temporary solution to the rooting
Sent from my Desire HD using XDA App
I've uploaded an update script, which can be used to flash PDroid from the CWM recovery more conveniently. Have fun.
Is it possible to use this on gs2 with cyanogen?
On the fly of my Galaxy S2
RogueZet
Tried this on RunnyRCmix3d 4.0 and after flashing zip could not boot in rom. So it does not work on every rom based on 2.3.5 . Can you look into this?
Sent from my Desire HD using Tapatalk
vault1965 said:
Tried this on RunnyRCmix3d 4.0 and after flashing zip could not boot in rom. So it does not work on every rom based on 2.3.5 . Can you look into this?
Click to expand...
Click to collapse
You're right. It won't work with Sense 3.5 ROMs. I've added to the description that it currently only works with Sense 3.0. I might port it to Sense 3.5 soon.
That would be great. I am using LBE app now, but yours promises so much more.
Sent from my Desire HD using Tapatalk
Thanks for releasing code. Now the challenge is up for me to integrate it with MIUI ( no source available !!!!!)
cool app, but i feel it spend alot of CPU resource , maybe my phone is slow
Related
NAMELESS v1
based on the EP1F Gingerbread Leak
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------
About:
This ROM is currently in testing for Charge. As such, some things may not work - but not for long! Please report issues in the thread. This ROM is the EP1F leak with my personal touches and changes, and some common sense tweaking to present a smoother, faster, EP1F experience.
--------------------
Thanks:
I've gotten some great help! Here they are (in no particular order):
gunnermike53 (tester, modder)
c0ns0le (tester)
Grillrd (tester)
I'm looking to get more help all the time, because with more help the faster the process goes Join me on FreeNode IRC chat at #samsung-charge
--------------------
What you really want to know:
Refer to Post #2 for an explanation of the below features.
Kernel Features:
EXT4 Support
Extra Storage Support (mmcblk0p2 remap for personal use /extstorage folder)
DBDATA/DATADATA Symlink
init.d Script Loading Support
Auto root install
Built-in BusyBox
Built-in fix_permissions script
Built-in bash shell
Built-in nano editor
FC Prevention & Detection (e.g. if you get acore FC's on boot, just reboot the device)
SD Card Read Speed Tweak
CPU/VM/Kernel Tweaks
CWM4 Recovery
Charge Mode ADB access
Rom Features:
Supercleaned
De-odexed
Zipaligned
De-TouchWiz'ed
Go Launcher EX
Touchwiz Calendar/Calculator
GAPPS - Gmail, Maps, Street, Vsearch, Talk2 (with video chat)
Appwidgetpicker
EXT4 auto-format on install (all partitions converted to EXT4)
sysrw, sysro scripts for remounting /system r/w or r/o
zipapps script for zipaligning apps on the fly
bstats script for removing old battery stats to refresh battery life
build.prop tweaks
Malware exploit patch
--------------------
FAQ:
Q: Ok, I'm cool with it, so what should I know about installing it?
A: Just flash from CWM3 recovery, no data wiping or other actions are needed, the entire installation is automated. NOTE: Your data will be wiped.
--
Q: Ok, what kind of caveats can I expect from this ROM?
A: The ROM is currently open for testing. I don't own a Droid Charge so I have no idea if anything works or not without testers. Being a test build, you may run into issues with things not working or nothing working at all. If that is the case just report it here.
--------------------
FILES:
Test Build #3
http://www.mediafire.com/?fz11ex27qo2ho97
--------------------
If you like my work, consider donating, or thanking me by clicking the thanks button
NAMELESS ROM DICTIONARY
Kernel Features
EXT4 Support This is a filesystem, basically what organizes and makes sense of the data on your phone. This specific one, EXT4, is generally known for being reliable and fast, compared to the one that comes with the phone, RFS.
Click to expand...
Click to collapse
Extra Storage Support (mmcblk0p2 remap for personal use /extstorage folder) This is a custom feature of the kernel which takes the "preinstall" partition (used for over-the-air updates from Verizon) and turns it into an on-phone storage space where you can store files separate from your SD card.
Click to expand...
Click to collapse
DBDATA/DATADATA Symlink This is a custom feature of the kernel which creates a symlink (a connection between two different points of data, or a shortcut) from the DATADATA directory to the DBDATA directory. This is advantageous because you will be able to use scripts not originally written for TouchWiz based ROM's.
Click to expand...
Click to collapse
init.d Script Loading Support This is a built-in kernel feature which allows you to store script files in the /system/etc/init.d directory on your phone. This directory is special because it will run said scripts at boot time. Generally in this directory people put performance enhancing scripts to better their phone.
Click to expand...
Click to collapse
Auto root install This is a custom kernel feature which roots your phone upon every boot, practically forcing your phone to be rooted while using the kernel. Even if you accidentally delete root, you will be rooted again upon the next boot.
Click to expand...
Click to collapse
Built-in BusyBox BusyBox is a binary (a linux program) that is a conglomeration of multiple utilities packed into one. Basically it allows you to use lots of useful linux commands not originally available on the Android operating system. It allows you to be the master and commander of your phone.
Click to expand...
Click to collapse
Built-in fix_permissions script This is a special script which when run (using a program like terminal emulator, or adb shell) will try to fix the permissions on your phone. Sometimes permissions can be set wrong, and this can cause lots of problems. This script fixes that.
Click to expand...
Click to collapse
Built-in bash shell Bash is a linux program, or rather a linux "shell", which is an environment where you can control your linux system and execute linux commands. Bash is also known as the "Bourne-Again Shell" and is a more advanced successor to its older sibling shell environments like "SH".
Click to expand...
Click to collapse
Built-in nano editor NANO is a linux text editing program that can be used from a command prompt in a linux shell.
Click to expand...
Click to collapse
FC Prevention & Detection (e.g. if you get acore FC's on boot, just reboot the device) This is a custom feature of the kernel where upon every boot the kernel will run a special error fix/detection script that will try to find and fix a few critical TouchWiz elements before booting you into the operating system. This is advantageous because it eliminates not being able to wipe between ROM's, since doing so usually causes a lot of problems.
Click to expand...
Click to collapse
SD Card Read Speed Tweak This is a common kernel implementation which slightly speeds up the reading speed of data on the SD card. In other words, it makes stuff on your SD card work faster.
Click to expand...
Click to collapse
CPU/VM/Kernel Tweaks These are common kernel implementations which overall improve the performance of your phone.
Click to expand...
Click to collapse
CWM4 Recovery This is a famous "recovery" system created by a developer named Koushik Dutta. This has been around awhile and is now in its 4th evolution. The version included here is one of the latest available. The recovery system allows you to execute useful linux and Android specific elements so that you may modify, save, or otherwise control your phone outside of the normal operating system.
Click to expand...
Click to collapse
Charge Mode ADB access This is a custom feature of the kernel which allows you to access your phone via ADB shell while charging. Charge mode is when your phone is off, and plugged in, showing the battery icon.
Click to expand...
Click to collapse
ROM Features
Supercleaned This means that all of the stuff that most people do not want, that comes on your phone when you buy or over-the-air update it, has been completely removed.
Click to expand...
Click to collapse
De-odexed Any Android application is usually delivered in the form of an APK file. An APK file is pretty much just a ZIP file. Sometimes the Android application needs extra code to do things, and this is found inside of the APK file and called "classes.dex". An APK file can be "ODEXED", this basically means taking the classes.dex file OUT of the APK file. This is advantageous because it allows the Android system to access the code directly instead of having to decompress and recompress (take apart, put back together) the APK file every time to access the code. However, it has one downside, it is difficult to make themes or mods while using this process. So, the APK file is "DEODEXED", which basically puts the code back in the APK file, creating one single file again.
Click to expand...
Click to collapse
Zipaligned Each APK file has a certain alignment to the little bits and bytes that flow through the phone, this is pretty much the same concept as having your car tires aligned for a straight drive. It allows the application to use less memory and perform better, like a tire alignment would allow you to use less gas and drive faster and straighter.
Click to expand...
Click to collapse
De-TouchWiz'ed The removal of close to all but the best TouchWiz applications.
Click to expand...
Click to collapse
Go Launcher EX A home launcher application included in the ROM, instead of the standard.
Click to expand...
Click to collapse
Touchwiz Calendar/Calculator Quite useful and good looking TouchWiz applications.
Click to expand...
Click to collapse
GAPPS - Gmail, Maps, Street, Vsearch, Talk2 (with video chat) The Google suite of applications.
Click to expand...
Click to collapse
Appwidgetpicker This little program condenses the widgets list when long-pressing on your home screen. It makes it so that you don't have 500 widgets to scroll through.
Click to expand...
Click to collapse
EXT4 auto-format on install (all partitions converted to EXT4) A custom ROM feature written by me which formats/converts your phone to the EXT4 filesystem automatically when installing the ROM.
Click to expand...
Click to collapse
sysrw, sysro scripts for remounting /system r/w or r/o Useful scripts which allow you to "remount" your system partition to a read/writable or read/non-writable state so that you may modify files in the system area.
Click to expand...
Click to collapse
zipapps script for zipaligning apps on the fly A special script which will attempt to give any applications in the standard locations the aforementioned tire alignment.
Click to expand...
Click to collapse
bstats script for removing old battery stats to refresh battery life A script which will delete old battery stats allowing you to renew the stats so as to attempt to get more battery life.
Click to expand...
Click to collapse
build.prop tweaks This file contains important properties of which the operating system cannot live without. I have tweaked this file to optimum performance standards so as to better your phone as much as possible.
Click to expand...
Click to collapse
Malware exploit patch Quite awhile ago a tricky person found a way to mess peoples phones up through the Android market, and this fixes that problem from ever occuring (It has long been fixed by Google anyway).
Click to expand...
Click to collapse
Wow a lag fix for the leak ill have to give it a shot later
Sent from my SCH-I510 using XDA Premium App
Awesome that you have EXT4 on GB! Hopefully one of the folks with a spare Charge will test this out.
great to see this rom here! I was using this on my Fascinate!
thank you.
glad to see a new ROM pops up. The OP mentioned flashing it w/ cwm3, while I'm already on cwm4, do I need to downgrade cwm before loading this?
Sent from Droid Charge
Do you need to be on the official leak first? I was on humble 2.1 and flashed this. The phone just boots straight into recover now.
Tested but after several attempts to install only boots up in recovery
IamIkari said:
Do you need to be on the official leak first? I was on humble 2.1 and flashed this. The phone just boots straight into recover now.
Click to expand...
Click to collapse
Thanks for the info IamIkari, I expected this and am working on a fix.
New Rom
As much as I like what the other devs have brought to the charge this is exciting. I cant wait to see a working and stable build.
I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.
im having same issue when i go back to debloated using odin
IamIkari said:
I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.
Click to expand...
Click to collapse
You will need a PIT file to go along with your ODIN flash.
I have included another kernel to test, it is in the OP under files. Flash after flashing ROM. Report issues.
IamIkari said:
I tried going back to the debloated official leak using ODIN. I'm still stuck at a recovery screen.
It is not your average recovery screen. It says "Android system recovery <3e>" and uses the home key to select instead of the power button.
Click to expand...
Click to collapse
i think you want to follow these instructions to get back to a working state
http://forum.xda-developers.com/showthread.php?t=1111486
navenedrob said:
You will need a PIT file to go along with your ODIN flash.
Click to expand...
Click to collapse
Where would I find a PIT file? I searched the forum and didn't see anything.
Nevermind, Thanks robby88!
I just installed test version 2 and I am getting nothing but clockworkMod recovery v4.0.0.8 when I boot up. Still a no go.
timgt said:
I just installed test version 2 and I am getting nothing but clockworkMod recovery v4.0.0.8 when I boot up. Still a no go.
Click to expand...
Click to collapse
Did you install the test kernel too?
navenedrob said:
Did you install the test kernel too?
Click to expand...
Click to collapse
No, i figured if it wasn't going to boot then there was no reason to. Is the kernel what you worked on to fix this? I will try again in a few mins. I started to odin back.
Looks like a great start.
I'll be watching this thread closely.
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
NotesNote1: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application. (This is currently removed, but I plan to add it back in shortly)
Note 2: Fascinate builds currently boot and have data. NS4g builds are still causing issues. Also, before you flash anything that this creates, please do a CWM backup.
Prerequisites
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change LogVersion 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Version 1.0.3 - 11/25/2011
Fixed build.prop issue when using the nubernel kernel
Provided a cleaner and more informative error message when there is an issue unzipping (seems to only occur with things zipped on *nix)
Version 1.0.4 - 11/27/2011
Fixed issue with /system/lib/ which was pointed out by xboxfanj
Rom built with default kernel has been tested and proven to boot when using the latest (1.11.25) fascinate build
Version 1.0.5 - 12/3/2011
Fixed issue that would not allow you to use a different kernel than stock
Fixed some attributes in the build.prop - might make some things work a little better, but I dunno what those will be
Made the build version field shorter
Fixed issue with the NFC stuff not being removed
Added optional CM7 kernel from the 11/24 build
Fixed issue when building from Nexus S or Nexus S 4G
Fixed issue with writing over an already existing zip file
Fixed issue with part of the build.prop dissapearing
Version 1.0.6 - 12/9/2011
Fixed build.prop issues (mainly issues with certain kernels)
Fixed carrier name issues
Fixed issue with framework.jar and data not working
Version 1.0.7 - 12/22/2011
Updated GoSMS
MMS fix as long as you use GoSMS
Application will remember the build user name and file system chosen
Ability to choose if you want a startup sound as well as the mp3 file itself
MTD support with ability to choose EXT4 or MTD.
Removed ability to choose a kernel for now, but it might be added back in later
Version 1.0.8 - 12/22/2011
Should now have working 911 (I'm not 100% on this though)
Replaced latest CM7 kernel, which wasn't working, with the Beta 6 MIUI kernel
Version 1.1.0 - 4/7/2012 (Dropbox Mirror)
Updating to MIUI V4
Verified SMS and MMS work when built from a Fascinate Rom
Version 1.1.1 - 4/8/2012 (Dropbox Mirror)
Fixed annoying blank message boxes with just an OK button
Version 1.1.2 - WIP
Add advanced reboot menu
Add phantom VM fix
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Future Hopes and Dreams: (may never get accomplished but would be nice)
Multi-thread C# application
Create a java version, so that the program will be cross platform compatible
Thanks
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive. Also, providing instructions for MTD.
Nubecoder - For nubernel kernel
ugothakd for providing the default EXT4 kernel
Marcusant for getting MIUI V4 to its current awesomness
CM7 Team for CM7 Kernel
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Found a bug. Here's the screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Death259 said:
MIUI Builder (Windows Only Application)
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions:
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
Note: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application.
Note 2: I tested one rom that was built with the default kernel, and it flashed just fine, but it wouldn't boot. This could potentially be solved by flashing the RFS to EXT4 or EXT4 to RFS zips. With that in mind, before you flash anything that this creates, please do a CWM backup.
Prerequisites:
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change Log
Version 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Thanks:
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive
Nubecoder - For nubernel kernel which is currently the only included optional kernel (p.s. If you want me to remove your kernel I can)
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Click to expand...
Click to collapse
Please give credit to ugothakd too. His kernel is the default one.
Sent from my SPH-D700 using Tapatalk
xBTx said:
Found a bug. Here's the screenshot:
Click to expand...
Click to collapse
same thing wit me
ns4g build didn't give any errors.. but the fascinate did.
xBTx said:
Found a bug. Here's the screenshot:
Click to expand...
Click to collapse
Ahh... that issue, have a nicer solution in the next version. For now, extract the zip manually, and then rezip it with the built in windowszipping functionality to rezip it.
xboxfanj said:
Please give credit to ugothakd too. His kernel is the default one.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Whoops! Problem solved!
Death259 said:
MIUI Builder (Windows Only Application)
In a nutshell, this program is designed to allow the MIUI rom to be built more easily. Since there are updates quite often and the process of updating the rom can be tedious for the developers, I decided to help out where I could and create this application.
Instructions:
Download a rom of a similar phone from the http://roms.miui.us/ website. The Fascinate should be a good one, and the Nexus S and Nexus S 4g might also work.
Launch the MIUI Builder
In the "MIUI Source Zip File" section, browse to the freshly downloaded rom
Put in a build version (usually the version of MIUI being built)
In the "Build User" put in some name (could use your xda name)
In the "MIUI Destination Zip File" browse to where you would like the CWM flashable rom to be saved
Optionally, you can choose a kernel to use, if you don't want to use the default kernel
Note: More kernels can be manually added to the kernels directory (Default C:/Program Files/MIUI Builder/kernels/). You just need to make sure they are CM7 compatible kernels. Also, the base is the miui_port_ns.zip, so you can swap files out in there if you want, but that zip will probably get wiped every time you update this application.
Note 2: I tested one rom that was built with the default kernel, and it flashed just fine, but it wouldn't boot. This could potentially be solved by flashing the RFS to EXT4 or EXT4 to RFS zips. With that in mind, before you flash anything that this creates, please do a CWM backup.
Prerequisites:
Windows PC
.net 3.5 or greater
Java Development Kit (JDK)
Change Log
Version 1.0.0 - Initial Release
Basic Functionality
Version 1.0.1
Added splash screen
Fixed permissions issue on windows 7 PCs
Version 1.0.2 - Initial Public Release - 11/25/2011
Added ability to choose a different kernel
Any suggestions would be appreciated.
If you managed to come across a bug, which at this point wouldn't surprise me, let me know and I will try to fix it as soon as possible.
Oh and of course, the usual jargon that I am not responsible if you somehow managed to mess up your phone or for that matter your computer. This software has been tested on windows 7 and windows 8 and hasn't caused any issues after instillation.
Thanks:
bxfxf - Got the initial instructions from him
xboxfanj - For testing it some and helping keep MIUI on the epic4g alive
Nubecoder - For nubernel kernel which is currently the only included optional kernel (p.s. If you want me to remove your kernel I can)
ugothakd for providing the default kernel
Everyone else who makes this community what it is, including but not limited to ACS, Bonzai and CM7 teams.
Click to expand...
Click to collapse
This is pretty damn cool
sent from my, ya know cm7 epic
Uploade version 1.0.3, all changes are listed in the OP.
Jesus, stop quoting the entire op...
Awesome job.
Sent from my SPH-D700 using Tapatalk
marcusant said:
Jesus, stop quoting the entire op...
Awesome job.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Jesus can do whatever He wants,it's almost His birthday.
Seriously, though thanks from all of us non-dev miui lovers. Can't wait to see the results.
I'll stay off now and leave this thread for you developers.
Sent from my SPH-D700 using xda premium
Bug:
Applying fix for cdma data in framework.jar, this shows.
The system cannot find the file specified.
This happens on both the fascinate and the crespo4g files.
btw, for your sig, that says "I'm pretty sure that MIUI is pronounced meeooee and not M.I.U.I," it's actually my-you-eye or me-you-eye.
iwasaperson said:
Bug:
Applying fix for cdma data in framework.jar, this shows.
The system cannot find the file specified.
This happens on both the fascinate and the crespo4g files.
Click to expand...
Click to collapse
What OS are you on? If you are on windows 7 or 8 then you might try running as administrator.
im on windows 7 x64, and i AM administrator (thats the only active account on the computer).
iwasaperson said:
im on windows 7 x64, and i AM administrator (thats the only active account on the computer).
Click to expand...
Click to collapse
Aight, you might be administrator, but due to how permissions are done in windows 7 you might still have to run as administrator. So, try right clicking on the shortcut and selecting run as administrator.
curious
so my builds built perfectly, i tried optional kernel, and stock, i also tried rts and ext4 settings, and my builds wont boot!
they flash just fine, no errors on zipping, but for some silly reason they are stuck on the flash screen?
im an avid flasher, i flash roms daily, and im stumped.
and for all you trollers out there yes i wiped, data, wiped cache, and dalvik.
otherwise the process was flawless, you think its because of the recent 11.25 build?
i havent yet tried to build a 11.17 build.
your thoughts death? thanks again for all the heard work
Running as Administrator didn't help at all. I tried the GSM crespo, the CDMA crespo, and the fascinatemtd build, all 1.11.25.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
an AROMA based Touch UI Recovery Installer
As seen on Valhalla Black Edition and Team Acid AOKP
Please tell me if you're going to use this in your ROMs just so I know who is using it . Thank you.
This is for ROM chefs only, not for regular users. Regular users, you will see this in all your ROMs soon .
All the instructions below refer to the files in META-INF/com/google/android
You can change the splash image by replacing aroma/splash.png (make sure it's a PNG though)
As mentioned in the installation instructions, make sure your ROM's zip file matches that of Valhalla Black Final's for best results.
Full touch screen support
Allows for a typical install, using default settings
Allows the user to customize the ROM installation
Allows the chef to customize the user experience
Support for different themes/skins
Installs Busybox
Installs kernel if you desire
Installs modem if you desire
No need to check mounts, the installer properly mounts the partitions for you.
No need to format partitions, the installer can wipe them for you.
Download and extract the installer zip file
Edit aroma/installer.default.prop to set your ROM's information
Rename installer.default.prop to installer.prop
Edit aroma-config and updater-script to your liking
Extract your current ROM's zip
Delete your ROM's META-INF folder
Put the new SGS4G CWM Rom Installer's META-INF and tools folders in your ROM's root
Make sure your ROM's file structure matches that of AOKP Unofficial by TeamAcid, unless you know what you're doing
Create a new zip file
Flash away and test!
If you use this tool you have to link back to this thread and give me credit using the link. Example:
My ROM uses the SGS4G ROM Installer by FBis251
http://forum.xda-developers.com/showthread.php?t=1481228
installer.zip
Installer on GitHub
You can download installer.zip from the link above to get the latest version of the installer files to package into your own rom.
Octoboer 13, 2012
Remove touchscreen calibration fix /data extract bug
-- With aroma 2.55+ touchscreen calibration is no longer necessary
-- /data packages should get extracted properly after a /data restore
Updated to latest AROMA binary (2.56)
-- Much more stable binary in ICS recovery!
---- The newest binary hasn't crashed on me yet during testing unlike the older version (2.50) that was included in the last version of the SGS4G Installer.
Here is the AROMA changelog since the last version included in the SGS4G Installer
EDELWEIS - 2.56 - BUILD 121004-031
Fix capacitive button
Remove calibration tools
EDELWEIS - 2.55 - BUILD 121003-030
Completely new Input/Touchscreen Handler - Thanks to agrabren from TWRP
Remove all calibration need. calibtool(), calibrate() and calibrate_matrix() won't do anything now.
EDELWEIS - 2.51 - BUILD 120810-026
Supported Galaxy Nexus Touch Screen - And maybe other devices now supported
Click to expand...
Click to collapse
July 18, 2012
ICS public release
May 25, 2012
Fixed bug that wouldn't mount partitions
-- Added support for mounting /efs
Added /efs partition info to installer.default.prop
Fixed a bug that would cause redbend_ua to restart the phone while flashing
-- (Thanks to itzik2sh from xda-developers for the fix)
Updated efs-backup
Now only checks whether /efs is empty
-- Will be compatible with devices that don't use an nv_data.bin
May 23, 2012
Updated scripts for easier porting
-- aroma-config and updater-script now uses information from installer.prop
-- porting to new devices will now be a lot easier because of this
Updated efs-backup script
--Backups now only take up ~560kB of space, compared to 6.3mB before!
Added colors to the installation confirmation screen
May 2, 2012
Changed to using installer.prop file for controlling all the variables
-- Chefs no longer need to edit the main AROMA script
-- AROMA checks if the installer.prop file exists to prevent users who flash the zip from messing up their phones
Added an installation option confirmation screen to make sure users know what options were selected
April 15, 2012
Updated to aroma-2.00-120414-A7
Now checking for phone version using a kernel check. Should prevent Froyo users from installing a GB ROM
Fixed a bug that would always do a free space check even when the user didn't try to do a /data backup
Now doing a /data restore before the kernel flash. Some ROMs caused the phone to reboot once the kernel flashed which means the /data restore never happened.
March 11, 2012
Updated AROMA binary to 2.0a4
Changed busybox version back to busybox v1.19.0.git
Now using aroma's TrueType font support
-- Installer uses the rom's default font (DroidSans)
Updated ROM information screen
Reboot prompt moved to the end of the installation
Updated Agreement to add formatting
Added efs-backup script which makes a backup of the efs partition
-- Saved under /sdcard/aroma-backup
Now has UTF-8 and RTL support!
March 3, 2012
Forced installation of busybox
Updated busybox to bonsai's version v1.17.1 (2010-08-12 23:44:34 CDT)
Fixed a bug that wouldn't allow the data backup and restore scripts to run
Moved mke2fs.conf to tools directory
Updated the sdcard free space check for /data backup
-- Will now only warn users when they selected the backup option in customized installs
March 3, 2012
Cleaned up a lot of the aroma-config code for easier reading
Deleted duplicate busybox binary
Deleted changelog.txt since no one used it
Added .gitignore
Updated busybox binary to version 1.19.4
Added monospace font
Now using the latest aroma nightly Version 1.62 build 120303-030
Using the latest themes from the nightly
Added a check to disallow /data backup when there isn't enough free sdcard space
-- Added a warning for the user to know the backup isn't going to happen
Updated touchscreen calibration values
Now displays filesystem and ROM information on the same screen
-- Added sdcard filesystem information
Reboot no longer done in the updater-script
Changed symlinks in updater-script to use busybox for more functions
Feb 12, 2012
Added aroma theme support. Check aroma/themes/
Added three themes, sense, MIUI and ICS (default ICS)
Added MIUI icons
Added filesystem (disk free/total and percentage used) information viewbox
Added ext4 format from bonsai's installer script.
-- Now does a full ext4 format and tuning before the install
Now allows choice of splash animation instead of static splash screen
Removed a lot of whitespace from aroma-config
Removed options to do wipes since the format takes care of this
Added data backup option
Now using bonsai backup. Left compression enabled for minimal sd storage usage.
Backup may take up to 10 minutes to complete!
Removed color.prop (no longer needed due to themes)
Changed checking for SGH-T959V to allow you to continue in case there is no ROM installed.
Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser
Click to expand...
Click to collapse
FB
I was just gonna thank you for this over on Black thread. Glad you got this out for folks. Slick very slick. Who needs ROM manager(mangler) when you're around. So thanks to you and everyone else who worked on it.
I just used this a few hours ago I installed the black final rom with touch screen features is cool!
Sent from my SGH-T959V using XDA Premium App
FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.
airfluip1 said:
FB, I will be using it for the next edition of AOSP Style coming out soon. I have already built mos of the rom and its installer, but I needed verification.
Click to expand...
Click to collapse
Sounds good. Just follow the OP if you'd like. I'm sure you already looked through the scripts. You should theme the installer to make it look like your ROM .
airflip if u are using my rom as a base its already in there .... which u asked me to use so.....
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
Same error on my sgs4g I think it was a temp file error, didn't affect my rom booting though.
Sent from my Glacier using xda premium
bswann said:
FB, I just flashed Raver's final and everything flashed fine then when the installer was done it showed an error having to do with not finding a path for something. I was going to re do it and copy the error down but now the phone is stuck at the T-Mo screen and it won't go into recovery with the button combo. I'm going to Odin it in the morning and re-flash and see if it throws the error again and I'll let you know.
Click to expand...
Click to collapse
If it happens again, hit save log and send that to me. I'd really like to see it.
Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x
Thanks Guys!!!(Raver,FB)
FBis251 said:
If it happens again, hit save log and send that to me. I'd really like to see it.
Click to expand...
Click to collapse
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.
alon2 said:
Gr8 job FB - thank you very much.
We'll probably also use it in our next version
10x
Click to expand...
Click to collapse
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
putsometrebleinit said:
FB, awesome work man. Lovin it. I had an error on my install but the ROM installed fine and booted fine. I made a log anyway so I could send it to you. Maybe it can be of some use.
Click to expand...
Click to collapse
Yes I'd love to see that.
airfluip1 said:
Thanks Guys!!!(Raver,FB)
Click to expand...
Click to collapse
No problem. I'm guessing it's working fine?
Cool very very neat. Never seen this on a phone before
Sent from my SGH-T959V using xda premium
FBis251 said:
Awesome, don't forget to post here if you have any usage questions. I wound up taking out a lot of the comments for space, but I learned the syntax of the AROMA functions pretty well.
Yes I'd love to see that.
No problem. I'm guessing it's working fine?
Click to expand...
Click to collapse
You are right. I am making this installer so customizable, from kernel to bootanimation.
airfluip1 said:
You are right. I am making this installer so customizable, from kernel to bootanimation.
Click to expand...
Click to collapse
I'm gonna release an update soon. You should look into it once I'm done since I simplified the updater-script portion of it.
What do you mean by "soon" because i may release 4.0 tomorrow. I just need to test my new features.
I'm doing final testing of the installer so in about an hour.
Feb 5, 2012
Edited updater script to output all installer options to one prop file
Now using variables in aroma-config for easier writing of the final options.prop file
Cleaned up updater-script to only use one .prop file
Fixed a bug that would make the wipe /data dialog come up even when deselected in the customized install
The script will now ask the user if they want to reboot their phones in all instances before the install gets going.
Now using Roboto font
Added color.prop file to control theme colors
Updated the wording on the install type chooser
Panicking right now because I can't seem to PM you FB.
I hope I don't come off as a stickler for details, but there's just a single typo in what is the 6th screenshot posted in the OP. It's for the option where you can choose to Wipe Data.
"...another ROM. Don't select if you want to keep your ap"
I'm assuming it was supposed to say "apps."
Just wanted to make note of it as I saw that Raver updated the contents in the aroma folder within the META-INF directory for his Valhalla Black rom. I was just thinking the typo might've been updated or something somehow.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With this tool, you can completely backup your device without root or unlocked bootloader.
I have tested it so far only with my Galaxy Nexus, but it should also work with other devices running Android 4.0+.
So you can unlock your bootloader without losing your data.
With version 1.1, not all parts of the program will be downloaded, only the necessary.
The most tools in the "Tools" section are for the Galaxy Nexus, but more devices will follow soon.
Now the final release of v2 is out!
The UI is complete, it's much easier to use.
Screenshots
Tutorial (thanks to AndyCr15)
http://www.youtube.com/watch?v=Xa0vnq_ce-M
If you use v1.2.2 you don't need to copy the UBT to platform-tools.
It would be nice if someone would do a tutorial for v2
German Tutorial:*click*
Download
Windows
Ultimate Backup Tool v1
Ultimate Backup Tool v1.1
Ultimate Backup Tool v1.2
Ultimate Backup Tool v1.2.1
Ultimate Backup Tool v1.2.2
Ultimate Backup Tool v1.3
Ultimate Backup Tool v1.3.1
Ultimate Backup Tool v1.3.2
mod edit: Using pay per click links is against XDA rule 13
3. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
Click to expand...
Click to collapse
Mirror link (not always up to date; thanks to chip.de)
ROM Backup Digital Cryptor
Mac OS / Linux
Ultimate Backup Tool v1 (thanks to eyrienne)
mod edit" more pay per click links
Source
UBT
ROM Backup Digital Cryptor(Alpha, post bugs below; big thanks to Marijuana Legal/Marijsoft )
Changelog
v1
Initial release
v1.1
Added download feature
Changeable path for backup
Added "Tools" section
ADB preloads
Added pauses
Added ADB and fastboot check
changed Window size
returning to .bat because some virus scanners have indentified it as malware
v1.2
Path will now be saved
fixed problem with preloading ADB
added version number
added Option to backup a single app
added CWM for GS2 and GS3
fixed Option 2 to install CWM to Verizon
v1.2.1
hopefully fixed the bug with backup functions
v1.2.2
changed window size
spelling mistake corrected
advanced ADB and fastboot check (thanks to 2uk3y)
some UI adjustments (thanks to 2uk3y)
recognizes if it runs on x64 or x86
v1.3
full S2 and S3 support
german translation (thanks to TheMaurice)
added device and version check
added notification if backup has been finished
added device informations
added "Incorrect input" notification to all menus
added pop-ups
v1.3.1
fixed a bug with pop-ups
added pop-ups for backups of a single app
fixed a bug with path of backup of a single app
v1.3.2
option to capture a problem
added package list
added Galaxy Note support
ADB updated
Fastboot updated
v2.0
Added rootmethod for Samsung Galaxy S4
Added option to flash zip
Added rootmethod for many devices (Doom4lord4Root)
Updated option to block ads
Added cloudservice box
Added form to report bug in programm
Updated gpubli (google ads)
Add image to cloud (experimental) (save your photo sdcard cloudservice picasa or flikr - only donation***ImageToCloud) in this version zip file folder image and uploading to google drive
Added CloudManager to add upload to your cloud with a application you get if you donate
Added donationbutton (Marijuana Legal don't have a job, he's so sorry)
Fixed language(English language is default)
Fixed update search and download
Fixed Backup/restore list single app
Known problems
Problems with the HTC One series
Problems with Sony devices from 2011
When you have a problem make sure you have correctly installed drivers.
Donations
Nobody has donated so far, be the first
Our little team
Gigadroid (Scripting)
Marijuana Legal (GUI for Windows and Mac)
Well...tried this on my GF's Droid Razr Maxx but all it did was display the adb.exe help text and then re-start. Does this util require an ADB connection? Or maybe anything else? I'm thinking some more info would be helpful...
Great idea, though -- I really hope it works.
Sent from my halfway-decent Acer A100 running WDS's JB with godmachine's kernel v1.3a cranked up to a sweet "battery life is for chumps" 1.5GHz using xda premium...like a boss!
I have fixed the problem.
The compiler has built crap.
And yes, it requires a ADB connection
I would like to see your source on this, is it possible to create a git?
Sent from my Galaxy Nexus using Tapatalk 2
It's just a .bat file.
Here is the code:
http://pastebin.com/pCHm38Ry
Gigadroid said:
It's just a .bat file.
Here is the code:
http://pastebin.com/pCHm38Ry
Click to expand...
Click to collapse
Thank you
Maybe post it in the first post, as I am not the only one who will want to see the source on a developers forum
does NOT work on sprint's galaxy s III running CM10
A simple gift for this wonderful promising tool...
Since this uses ADB, if adb.exe is not found, it would not give any error/information to the user, of what is happening. It will just exit to the menu. Thus, I have added some ADB detection in the script here. http://pastebin.com/mFXJ3w36
PS: If @Gigadroid would put this up on github, more expansion and contribution is expected.
hai Gigadroid,
can u explain more about each option? coz i a little bit confuse about option 3,4 and 5.
if i need to backup game apps and data saved, which one should i choice ?
sorry for my English.
TQ
UI for your tool
Where can I contribute a simple Windows WinForms based UI for your tool? I am envisioning a save folder for backups, a file selection for restore. Backup name with date and time in file name if so desired, custom file name, ADB existense check, all garnished with explanative messages and an interminent progress bar so as to not block the UI while performing backup or restore.
BTW I just tried it on my SGS2 a day I after I rooted it for backups and it work fine
Now if I could only see how in ADB a package list can be retrieved with friendly names (Don't tell me... let me learn alone)
Does it work with<strikethrough> ICS 4.0.3(galaxy S2)</strikethrough> or even Gingerbread 2.3.6 (Galaxy Y) ?
I got this on galaxy S2
tapatalk سے لکھا گیا
drraptor said:
I got this on galaxy S2View attachment 1285550
tapatalk سے لکھا گیا
Click to expand...
Click to collapse
it's was an old issue with screenadjuster, just disable it. and tap back up my data.
What option to use to Backup everything like in a Nandroid?
bonell said:
What option to use to Backup everything like in a Nandroid?
Click to expand...
Click to collapse
It's data backupper, I think
jaguaralani said:
A simple gift for this wonderful promising tool...
Click to expand...
Click to collapse
Thank you, I will try to include it in the next version.
I have big plans.
It will not only be a backup tool.
ameer1234567890 said:
Since this uses ADB, if adb.exe is not found, it would not give any error/information to the user, of what is happening. It will just exit to the menu. Thus, I have added some ADB detection in the script here. http://pastebin.com/mFXJ3w36
PS: If @Gigadroid would put this up on github, more expansion and contribution is expected.
Click to expand...
Click to collapse
I will also include it in the next version.
Then I will put it up to github.
2uk3y said:
hai Gigadroid,
can u explain more about each option? coz i a little bit confuse about option 3,4 and 5.
if i need to backup game apps and data saved, which one should i choice ?
sorry for my English.
TQ
Click to expand...
Click to collapse
Option 3 is for backup device and app data.
That means when you restore you have only the system apps on your device.
The data of your apps is still present.
If you've done a mission in Dead trigger and install the app again, you're where you left off.
Option 4 is for backup your apps without data.
When you restore you aren't where you left off.
Option 5 is for backup music, pics, etc. hat are saved on your device
I would say you should choose 3 and 4, but with 1 you can do nothing wrong
AlbertoBN said:
Where can I contribute a simple Windows WinForms based UI for your tool? I am envisioning a save folder for backups, a file selection for restore. Backup name with date and time in file name if so desired, custom file name, ADB existense check, all garnished with explanative messages and an interminent progress bar so as to not block the UI while performing backup or restore.
BTW I just tried it on my SGS2 a day I after I rooted it for backups and it work fine
Now if I could only see how in ADB a package list can be retrieved with friendly names (Don't tell me... let me learn alone)
Click to expand...
Click to collapse
I had the same idea for a future release.
Maybe we can work together.
Send me a PM.
drraptor said:
Does it work with<strikethrough> ICS 4.0.3(galaxy S2)</strikethrough> or even Gingerbread 2.3.6 (Galaxy Y) ?
Click to expand...
Click to collapse
Please read the first post. :/
Does not work on stock ROM in Sprint Epic 4G Touch (SPH-D710) "adb: unable to connect for backup" every other adb functions work.
Nice script nonetheless.
bonell said:
What option to use to Backup everything like in a Nandroid?
Click to expand...
Click to collapse
You can't compare this tool with a Nandroid backup.
Option 2 is the closest Option.
Is there a restore data ONLY button for a specific app?
UnBloatMi - Xiaomi MIUI Bloatware Remover
I have been searching for a script to remove Bloatware from my Xiaomi Mi5s, and found a couple of different ones that do part of the job.
None were exactly what I was looking for, so I wrote a script of my own.
Although I tested the script on my MI5s only, it should be very usable for any Xiaomi device running MIUI 7 or 8.
In UnBloatMi I have combined multiple lists of MIUI 7 and 8 apps that should be safe to remove.
It also contains a couple that are less safe to remove, but the script will ask for confirmation before removing those.
Which is a big difference from other scripts; you get to choose what to remove and what to restore!
Backup location:
If you edit the script, you can change the backup location to use (by default "/sdcard/UnBloatMi")
You can of course also add more apps to remove to the list in the script. (instructions are in the comments)
It's not needed to remove files from the list, as it will not process files that are not on your device, and you can choose not to remove any app.
To Customize the Script:
Unzip the zip and edit the file under: META-INF\com\google\android\update-binary
This script is written in shell language (sh), so editing is somewhat different from "normal" EDIFY scripts that use the "updater-script" file.
I used part of the excellent template by osm0sis to create UnBloatMi
Install Custom Apps/Files:
You can also have the script install Custom files to /system folder. (So you can add another HomeLauncher, for example)
To have the script install Custom files, just add them to the Zip in "/system/app/" folder:
/system/app/YourCustomApp1/YourCustomApp1.apk
/system/app/YourCustomApp2/YourCustomApp2.apk
The script will automatically install them for you.
To use the Script:
You need to have TWRP Recovery installed.
BACKUP YOUR DEVICE BEFORE RUNNING THIS SCRIPT!!! (I recommend using TWRP Backup)
(even though the script allows you to restore your changes, something can always go wrong - press wrong button for example)
- Move the ZIP file to your SDCard, and install using TWRP Recovery
Basically, you can just follow the instructions on the screen, by pressing Volume buttons.
- The first run, you'll be asked what apps to remove. Backups are automatically made.
You can confirm each app, or choose to only confirm the more risky apps.
- If you run the script again (after testing your installation), it will detect the backups from the previous run.
You can then choose to restore the backup files, or delete them from your device.
- You can now also create a default UnBloat list, that can be used to UnBloat after flashing a (new) ROM.
It is created by checking for installed apps. If an app is not found on the device, it's added to the list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Feel free to edit and change the script.
If you make any improvements, please let me know so I can add them to the script.
This includes reporting what apps caused problems when removed, or comments about apps.
You can find the script in: /META-INF/com/google/android/update-binary (or on GitHub by clicking the "Source Code" link below)
Instructions can be found in the comments of that file.
--UPDATE--
Added Step by Step Restore: You can now choose which apps to restore, so it is easier to troubleshoot your installation.
--UPDATE v0.2--
Added warning to SecurityCenter App (so it has to be confirmed). It caused bootloop on my device when removed.
--UPDATE v0.3--
Bugfixes, Added Apps, changed and added some app comments. Changed download link (GitHub download creates a folder too many)
--UPDATE v0.4--
Changed/Added menu's - Allows you to do more actions at once
Added apps and comments.
Added ability to save a default UnBloat list. This can be used to UnBloat after flashing a ROM.
Download
Source Code
Unfortunately I got an error (missing files) under TWRP 3.0.2
luxim said:
Unfortunately I got an error (missing files) under TWRP 3.0.2
Click to expand...
Click to collapse
I'm using TWRP 3.0.2 as well...
Did the install reach the menu at all?
Can you look at the log file to investigate? (TWRP --> Advanced --> Copy Log --> Open log file from your SDCard)
Zappo said:
I'm using TWRP 3.0.2 as well...
Did the install reach the menu at all?
Can you look at the log file to investigate? (TWRP --> Advanced --> Copy Log --> Open log file from your SDCard)
Click to expand...
Click to collapse
Here it is. My recovery is the ZCX one and I wasn't able to enter the menu. I'm running the latest xiaomi.eu developer.
luxim said:
Here it is. My recovery is the ZCX one and I wasn't able to enter the menu. I'm running the latest xiaomi.eu developer.
Click to expand...
Click to collapse
Thanks for your bug-report and logfile!
It says it couldn't find the script, and after investigating I found the download link to GitHub creates a folder too many inside the zip.
I was hoping to have the available download automatically give the latest version...
I guess I'll have to create a release after every update, and update the link accordingly...
I adjusted the download link in the original post.
this is great! i made my own debloater script, but your is so much more elegant! i hope things dont change much when we update to 8.2....
wurstel said:
this is great! i made my own debloater script, but your is so much more elegant! i hope things dont change much when we update to 8.2....
Click to expand...
Click to collapse
I have just released version 0.4, which allows us to create a default UnBloat list.
This can be used to UnBloat again after flashing a new ROM.
(I'm hoping to use this in combination with OTA updates. I'll write a howto if I manage to get this all to work)
Thanks, i try it...
EDIT: i have removed many apps on my rn3se (kate), wipe davilcache but i've a bootloop :?
Good restore option
Hey @Zappo, did you already get the update to 8.2? Will you be updating the script for the new miui?
wurstel said:
Hey @Zappo, did you already get the update to 8.2? Will you be updating the script for the new miui?
Click to expand...
Click to collapse
I'm running the MIUI Global ROM 8.0.3.0....
As far as I know, no updates yet...
If anyone knows of new or other Bloatware, I'll update the script accordingly.
samurri said:
Thanks, i try it...
EDIT: i have removed many apps on my rn3se (kate), wipe davilcache but i've a bootloop :?
Good restore option
Click to expand...
Click to collapse
If you have found the app causing your bootloop, please let me know. I'll add it to the risky apps list.
I use the "restore one by one" option, and try to find the problem-app that way...
Zappo said:
If you have found the app causing your bootloop, please let me know. I'll add it to the risky apps list.
I use the "restore one by one" option, and try to find the problem-app that way...
Click to expand...
Click to collapse
Hi.
Big thanks for your hard work. At this moment i have personalized your list but i think that velvet.apk is a possible problem
This "# The file number doesn't have to be in order, but should be unique." is no true otherwise the script does not work well (es.: items 0-1-3-4)
samurri said:
this "# The file number doesn't have to be in order, but should be unique." is no true otherwise the script does not work well (es.: items 0-1-3-4)
Click to expand...
Click to collapse
You are both correct and wrong; they don't have to be in order, but do have to be ascending without interruptions (can't have missing numbers)
Ex: items 0-1-3-5-4-2 is OK.
I didn't think it would be a problem, as items don't have to be removed...
I will review your list, and add a comment to velvet.apk when I have the time. (however it didn't cause any problem on my Mi5s)
Ok, thanks.
Do you know where can i find mi apps description?
samurri said:
Ok, thanks.
Do you know where can i find mi apps description?
Click to expand...
Click to collapse
I've been Googling for those quite a bit...
It's hard to find good descriptions for those.
Zappo said:
I've been Googling for those quite a bit...
It's hard to find good descriptions for those.
Click to expand...
Click to collapse
No sorry, velvet is ok but it's need a litlle of attention.
EDIT: install /system/custom1/custom1.apk is impossible
hey @Zappo is this debloat script working for china stable?
wurstel said:
hey @Zappo is this debloat script working for china stable?
Click to expand...
Click to collapse
Yes, it should work for all MIUI 7&8 devices.
If software in the script is not found on your device, it will be automatically skipped.
samurri said:
EDIT: install /system/custom1/custom1.apk is impossible
Click to expand...
Click to collapse
I agree this kind of got lost in the code...
New software is only installed when removing bloatware the first time (or when no backups are found).
It should be automatically installed when choosing "Remove/Restore bloatware" from the first menu.
However when a backup is present on the device (folder "UnBloatMi" by default), this is skipped...
I did this, presuming new software is installed after the first run, and if a backup is already created it doesn't have to be installed again.
Hey @Zappo , found this project for redmi note 2, and it's so heavily debloated, i haven't seen anything like it. Maybe you can look over it and add a few more things to debloat? I tried to recreate it but I don't know which qualcomm apps are essential to our phone, i had only bootloops... Anyway here's the link https://forum.xda-developers.com/redmi-note-2/development/best-sot-t3434915
Edit: i can provide you with a list of all the contents of the rom, i extracted the system partition.