برنامج لعمل نسخة احتياطية والتحكم في أجهزة أندرويد Uberizer V1.4
السلام عليكم ورحمة الله وبركاته
اعضاء منتدي خبراء المحمول الكرام اليوم اتينا لكم بي
برنامج للتحكم باجهزة الاندرويد
تحميل البرنامج
www.mediafire.com/?6wnvzxmeepc11o1
وهذا الفيديو شرح تنصيب واستعمال البرنامج
This tool aims to support many android devices. Use the Uberizer to:
Uberizer Quickstart Guide:
Connecting your device to your computer:
To get started using the Uberizer you will need to connect to your computer. This can be done 2 ways:
* Wireless (RECOMMENDED) (REQUIRES ROOT!)
* Wired (Advanced users only) (Can ROOT devices)
The reason why wireless is recommend is because it's easy! Wired installation requires you to install
the ADB driver which can sometimes have problems, some devices have wierd ADB ports so you will have
problems finding the proper cable for it and some devices don't have ADB ports at all.
** Setting up your device for Wireless Uberizing (RECOMMENDED)
1. Go to the Wireless Menu (w)
2. Enable Wireless ADB using ONE of these options: 2, 4 or 5, whichever is most easy for your situation.
3. If you use an app (4 or 5), start the app on your Android device.
Use option 6 to connect to the given IP in the app.
If you chose option 2, you must find your device IP, go to Settings, About device, Status, to see the IP.
** Setting up your device for Wired Uberizing (Advanced users only)
1. Install ADB drivers (from dir usb_driver) for wired ADB
2. Boot Android, connect device (on the device, the statusbar will display "usb debugging mode is activated")
3. Run this tool, analyse device so this tool can seek info of your device
and will check if your model is supported by mods
NOTE: Your device must have "ADB Debugging" checked in: "Settings \
Developer options \ USB debugging (Debug mode when USB is connected)"
Uberizer main menu:
a. Analyse device (find model)
- Rescans for a device, use this after connecting another android device to your computer.
b. Build Menu
+ 1.Auto Mod build.prop
* Automatically adds several build.prop tweaks and enhancements.
+ 2.Edit build.prop and push it back
* A handy way to quickly check or edit a few build properties.
+ 3.Market build.prop fixes
* Strips out the current market fingerprint and copies the modded build.prop to the
device. Currently this emulates a Samsung for full market (Google Play) access.
+ 4.Backup current build.prop on device
* Dumps a copy of your build.prop to \backups, the prop dump name includes your model
name, the current date and time of dump. To easily restore these backups, run 5.
+ 5.Restore a build.prop backup
* Indexes all backupped build.prop files on the system and allows the user to chose
which file (s)he wants to restore on the tablet.
c. Root Menu
+ 1.Android 1.6 Donut (tested on WM8505)
+ 2.Android 1.6 Donut MAA (tested on WM8505)
+ 3.Android 2.2 Froyo (WM8650)
+ 4.Android 2.3 GingerBread (WM8710)
+ 5.Android 3.0 HoneyComb
+ 6.Android 4.0 ICS (tested on A13)
+ 7.Android 4.0 ICS MIPS (tested on Ainovo)
+ 8.Android 4.0 ICS (tested on WM8850)
+ 9.Android 4.0 ICS v2
+ 10.Android 4.0 ICS HTC (alpha)
+ 11.Backup current root bin and su app
* Backups the system\(x/s)bin\su bins and superuser.apk to \backups\system (x/s)bin and \app
+ 12.Restore root backup
* Writes the \backups su bins and superuser.apk back to the device.
+ 13.Unroots device
* Removes su bins and superuser from device and sets default back.
+ 14.Check device root
* Installs and starts the latest free version of Joey Krim's Root Checker
d. Backup Menu
+ 0.Full device "unmod" backup to backups\%MODEL%_%DATE%_%TIME%
* Creates a set of files that the uberizer tries to mod on your android device.
+ 1.Backup build.prop to backups\
* Dumps a copy of your build.prop to \backups, the prop dump name includes your model
name, the current date and time of dump. To easily restore these backups, run 5.
+ 2.Restore build.prop
* Indexes all backupped build.prop files on the system and allows the user to chose
which file (s)he wants to restore on the tablet.
+ 3.Backup bootanimation.zip to backups\
* Dumps a copy of your bootanimation to backups\bootanimation.zip
+ 4.Restore bootanimation.zip
* Displays a selection menu of bootanimation.zips from \backups and pushes the animation to your android device.
+ 5.Backup data\ to backups\data.tgz
* REQ ROOT. This will backup your full /data partition, very nice to backup all your
downloaded apps with their settings if you are planning to reflash your device.
+ 6.Backup data\app to backups\data_app.tgz
* REQ ROOT. This will backup only data\data\apps, your "downloaded" apps. Very useful
for sharing apps with your friends or when you are planning to reflash your device.
+ 7.Backup data\data 2 backups\data_data.tgz
* REQ ROOT. This will backup only all the app settings on your device.
+ 8.Restore 5. data.tgz backup
* Easily restore backups done with option 5.
+ 9.Restore 6. data_app.tgz backup
* Easily restore backups done with option 6.
+ 10.Restore 7. data_data.tgz backup
* Easily restore backups done with option 7.
+ 11.Backup current root bins and su app
* Backups the system\(x/s)bin\su bins and superuser.apk to \backups\system (x/s)bin and \app.
+ 12.Restore backed up root bins and su app
* Writes the \backups su bins and superuser.apk back to the device.
+ 13.Backup hosts file
* Backups your current hosts file of your device to backups\hosts_%date%_%time%.
+ 14.Restore hosts file
* Easily restore a previously backupped hosts file.
+ 15.Backup init files to backups\init.tgz
* This will take all init rc files from your device and stores them into \backups seperately,
but also this will make a tgz of the original files. This tgz is easy to recover using
option 16, because it's a tgz the original attributes remain. You can mod the seperately
dumped init files and adb shell chmod 750 them when you push them back.
+ 16.Restore init files backups\init.tgz
* Brings up a selection menu to easily select your previously created init backup.
e. Bootanimation Menu
+ 1.Backup current bootanimation.zip
* Dumps a copy of your bootanimation to backups\bootanimation.zip.
+ 2.Copy new bootanimation.zip
* Write back backups\bootanimation.zip to your android device.
+ 3.Delete bootanimation.zip on device
* This removes the bootanimation.zip from your device, this might slightly improve your
boot time.
+ 4.Recover backed up bootanimation.zip
* Brings up a selection menu with current backed up bootanimation.zip files in \backups.
f. Multi Mod Tool Menu
+ 1.undex (baksmali)
* Undex amm_files\undex_input_files\classes.dex to undex_output_files.
+ 2.dex (smali)
* Rebuilts dex from \dex_input_files and writes to dex_output_files.
+ 2a.dex (smali) dex default undex output dir
* Rebuilts dex from \undex_output_files\out and writes to \dex_output_files.
+ 3.Jar maker
* Creates one .jar file from \jarmaker_input_files dir, a generated .jar file will appear in jarmaker_output_files.
+ 3a.Jar maker using existing meta-inf\manifest.mf
* Creates one .jar file from \jarmaker_input_files dir, a generated
.jar file will appear in jarmaker_output_files with manifest.mf.
+ 4.APK sign (batch-mode)
* HcH's Microsigner, a simple way to sign a load of apks.
+ 5.Update.zip maker
* Creates simple update.zip file. Input dir \updatezip_input_files, Output zip file will be written in \updatezip_input_files
+ 6.Jarsigner
* A tool to sign jar files, certs/keys included! Input file: \amm_files\jarsigner_input_files\unsigned.jar
+ 7.OptiPNG
* Optimize those PNG files for maximum loading speeds! Dump all your pngs in optipng_files and run this option.
+ 8.framework-res.apk OptiPNG (alpha)
* A attempt to automatically optimize a framework-res.apk. This rebuilts the framework and signs it.
+ 9.batch extract and decrypt manifest from apks in \aapt_input_files
+ 10.batch generate APK application details from apks in \aapt_input_files
+ 11.batch generate APK extreme details from apks in \aapt_input_files
g. Application Manager Menu
+ 1.Batch install apps (from \install_apk)
* This installs all the apk files you have stored in \install_apk on your device.
+ 2.Install1app (select from \install_apk)
* This brings up a selection menu of all the apk files you have
stored in \install_apk on your device. You can select one you want to
install.
+ 3.Backup system apps to backups\sysappstgz
* Backups the system apps of your device to backups \system_apps.tgz
+ 4.Backup data apps to backups\data_appstgz
* Backups the data apps of your device to backups \data_apps.tgz
+ 5.Restore 4. data apps package to device
* This easily restores a previously created backup with option 4
+ 6.Backup 1 app to backup\ .apk
* Creates a list of all your downloaded apps, enter the generated number of the app
you wish to backup, and the app will be downloaded to \backups.
h. Help me
1.Go to the Wireless Menu (w)
2.Enable Wireless ADB using ONE of these options: 2, 4 or 5, whichever is most easy for your situation.
3.If you use an app (4 or 5), start the app on your Android device.
Use option 6 to connect to the given IP in the app.
If you chose option 2, you must find your device IP, go to Settings, About device, Status, to see the IP.
1.Install ADB drivers (from dir usb_driver) for wired ADB
2.Boot Android, connect device (on the device, the statusbar will display "usb debugging mode is activated")
3.Run this tool, analyse device so this tool can seek info of your device
and will check if your model is supported by mods
i. A1X Firmware Menu
+ 1.IMG unpacker
* unpacks rom_kitchen\original.img, the main files are stored in _input.
+ 2.IMG packer (rom_kitchen\_input)
* rebuilts your modded files that are previously extracted to a IMG file (output.img)
+ 3.Dump A1X firmware to Uberizer dir
* this will dump your A10 or A13 firmware in a sub directory of Uberizer.
+ 4.Restore A1X firmware from \rom_dumps
Restore a previously created rom dump with option 3. Special Thanks
to Satcomranger for risking his tablet's life and coding fixes for the
procedure.
+ 5.Start LiveSuit Pack v1.09
Start LiveSuit for manual flashing or formatting your A10/A13 device
j. Install full market
+ installs a hacked market apk with unrestricted market access, plus fake
the fingerprint of galaxy tab to gain more access. NOTE: if you have a
different cpu model than armeabi-v7a, like mips for example, you won't
see all available apps, you will see everything fit for your
"product.cpu.abi", you can see your cpu in the build prop (option b/2)
k. Various Mods Menu
+ 1. Sync device FS
* syncs android device's FS, for safe shutdown for example.
+ 2. Clean Dalvic Cache
* cleans the dalvic cache
+ 3. Add Tar 1.23 bin (auto backups old)
* this adds the real deal TAR binary to your android device!
+ 4. Install anti ad and malware hosts file
* adds the MVPS hosts file to protect you against the most known malware servers.
+ 5. Add GREP/EGREP/FGREP 2.6 bins
* adds the GREP binaries to your android device, enjoy full grep functionality!
+ 6. Add PHP v5.3.2 and Groomdroid webserver
* copies needed files and installs a PHP pre-configured Groomdroid web server.
+ 7. ICS Screen Capture to /screenshots
* takes a screenshot of your screen and stores it in /screenshots
+ 8. Add Capture ICS bin to device
* adds the ICS capture bin to your device, EXPERIMENTAL FEATURE . UNTESTED
+ 9. Add bash 4.1 bin to device
* for those Shell Ninjas out there, here it is ... BASH 4.1 on android!
+ 10. Config Groomdroid on device
* easily edit your config.
+ 11. Auto Market and Framework Cache clean
* performs the "market flush" for you.
+ 12. System App Remover (with auto backup)
* Makes a list of all the system apps with numbers, input the prefixed number and
the system app will be automatically backed up to /backups/%APKNAME%_%DATE%_%TIME%
+ 13. System App Restore
* With this option you can restore previously removed system apps.
+ 14. Remove Phone (with auto backup)
* This option will remove phone.apk and TelephonyProvider.apk from /system, without
any extra switches this will backup the removed items.
+ 15. Realtime LOGCAT Monitor 1024x768
* Starts a new command prompt window fit for 1024x768 resolution.
+ 16. Dump LOGCAT to TXT file
* Dumps the LOGCAT output as a TXT file in the Uberizer dir. After the dump has
completed, WinVi editor will open the generated TXT file.
Output file example: LOGCAT_npm702_NOVO7PALADIN_20122511_0202.txt
+ 17. Generate full device and bug report
* Dumps dumpsys, dumpstate, and logcat to a TXT file in the Uberizer dir. After
the dump has completed, WinVi editor will open the generated TXT file.
Output file example: BUGREPORT_npm702_NOVO7PALADIN_20122511_0205.txt
NOTE: This dump can take quite a while. If your device has vibration it will go
off once at the start of the dump and will go off twice when it's completed.
This dump can take up to one minute to complete.
+ 18. Dump DMESG (Diagnostic messages) to TXT
* Dumps out of DMESG in the Uberizer dir and opens the output file in WinVi,
Output file example: DMESG_npm702_NOVO7PALADIN_20122511_0234.txt
+ 19. Fix /data/local permissions
* Needed on some ICS roms when ADB installation fails.
+ 20. Backup and remove batterystats.bin
* Handy for re-calibrating your battery. Batterystats is file that actually follow
the usage of power by android apps. However, some problems conserning calibration
and indication can relate to this file.
+ 21. Backup and remove Unlock Pattern
Simply removes the settings.db so you can use your device again.
+ 22. Enter device's ADB shell
For all the shell ninja's out there
+ 23. Enter device's ADB shell (remountmode)
This remounts data system and root to be read write, consider this option as
browsing under root privileges, be careful what you mod! After you have closed
this shell session, the remounts remain active in the adb session. In other words
if you have problems modding your build prop for example, run this option, close it
and retry, good chance you can now edit system files.
+ 24. Edit init.rc and push back
For pro's only, allows you to modify your init.rc and copy the modified init.rc back
to your device. Handy for developers who are debugging.
+ 25. Edit init.%MODEL%.rc and push back
For pro's only, allows you to modify your init.rc and copy the modified init.rc back
to your device. Handy for developers who are debugging and people who have problems
with touch screen or gsensor on sun5i / a13 models to swap drivers.
+ 26. Clean dalvik-cache
Deletes everything in the dalvik-cache, reboot is required after this procedure, so
the system can rebuilt the cache on boot.
l. Files to SD (extsd)
+ This will write files from \files_to_sd to your device /mnt/extsd or /sdcard
m. Donate to TechKnow
+ How very kind of you to consider!
u. Update Uberizer
+ Connects to TechKnow and downloads the latest version, and installs it over itself.
q. Quit
+ A very common command that should not require explanation. However, quitting the
Uberizer cleans up it's temporary files and shut downs the adb server properly.
r. Reboot device
+ While your device is connected you can reboot it to see if certain mods are accepted
or other testing purposes. Uberizer will play pong with itself until your ADB is back online.
w. Wireless Menu
+ 1. Help and HowTo
* Short intro and HowTo on connecting your device
+ 2. Enable Wireless ADB through wired ADB
* When you are already ADB connected, you can start Wireless mode
+ 3. Disable Wireless ADB
* Wired or wireless, disables Wireless ADB server
+ 4. Wired install of Wireless ADB APP
* Install a ADB APP of choice to your device (2 loaded)
+ 5. Copy Wireless ADB APP to SD
* Prepare a SD card for the Uberizer
+ 6. Connect
* Connect your device to your computer/uberizer to use it. Your IP-address and you can specify
if desired a custom port, default port = 5555, leave the default port empty to use 5555.
x. Install Virtual OldPC 95 to device
+ This will copy the oldpc95 hd image with dos6.22, win2.3, win3.11 and win95, with 17 small games.
Run this image using the slightly modified aDosBox that will be installed with this command. To
enhance the screen quality, go to menu, sdl settings, video settings and select smooth the video.
A reboot is required, if your device is powerful enough you will have no delays. To start Win3.11
or 2.1 or Dos 6.22, on booting the dosbox image hit F5 and select option 5 from the boot menu, or
exit windows to command prompt in the shutdown menu. Run "autoexec" once you are in the prompt and
a helpful menu with the games will appear.
Changelog:
v1.4 (128 functions):
* uberizer various: added: 22. Enter device's ADB shell
* uberizer various: added: 23. Enter device's ADB shell (remountmode)
* uberizer various: added: 24. Edit init.rc and push back
* uberizer various: added: 25. Edit init.%MODEL%.rc and push back
* uberizer various: added: 26. Clean Dalvik-cache
* uberizer root: added x86 root with busybox 1.20
* uberizer root: fixed busybox bugs in root 7 and 9
* uberizer A1X fw: fixed step 3 on the restore function (recovery.img)
* uberizer main: fixed reboot routine
* uberizer main: fixed autodetection
* uberizer backups: fixed a bug in option 10
* uberizer main: added presetup for advanced system specific modifications (upcoming v2.0 feature)
Using the rom_kitchen:
This is the flash kitchen v2 modded to work with A1X IMG files and updated livesuit to 1.0.9, made
easy by some added scripts and automation.
Preparations:
1. a x64 Ubuntu or other linux system
2. a Windows system
3. \rom_kitchen\a10_tools.tar.gz extracted on your linux system
4. a base rom
5. a modkit, a set of files you have modded or wish to add/remove
6. ia32-libs, exe on your x64 ubuntu/linux system "sudo apt-get install ia32-libs"
HowTo:
1. put original.img in the root of the kitchen
2. run the uberizer to extract the original.img
3. mod the files in _input
-recovery.fex (see "Modding the recovery partition" in this document)
-root.fex (see "Modding the root" in this document)
-bootfs.fex (see "Modding the bootfs" in this document)
-system.fex (see "Modding the system partition" in this document)
4. rebuild running uberizer's create image function
Modding the root:
1. Extracting:
tools/split_bootimg.pl _input/root.fex
* this will give you root.fex-kernel the root.fex-ramdisk, check "Modding the ramdisk" in this document for details
2. Rebuilding:
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
tools/mkbootimg --base 0x40000000 --kernel root.fex-kernel --ramdisk
ramdisk-new.gz --cmdline 'console=ttyS0,115200 tw init=/init
loglevel=8' -o modded-root.img
this will give you a new file, modded-root.img
Modding the ramdisk:
1. Extracting:
mkdir ramdisk
cd ramdisk
gunzip -c ../root.fex-ramdisk.gz | cpio -i
2. Rebuilding:
check "Modding the root" part 2. in this document
Modding the bootfs:
1. Make some directory:
mkdir bootfs
sudo mount -t ext4 -o loop _input/bootfs.fex /bootfs
2. Edit files in /bootfs
3. Unmount the bootfs
umount bootfs
Modding the recovery partition:
1. Extracting:
tools/split_bootimg.pl ./_input/recovery.fex
rm -rf ramdisk
mkdir ramdisk
cd ramdisk
gunzip -c ../recovery.fex-ramdisk.gz | cpio -i
2. Rebuilding:
*sudo apt-get install ia32-libs
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
tools/mkbootimg --base 0x40000000 --kernel recovery.fex-kernel
--ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init
loglevel=8' -o modded-recovery.img
Modding the system partition:
1. Mounting:
sudo mount -t ext4 -o loop system.img /mnt
start modding! (SU permissions required!)
*sudo nautilus (will execute "explorer" with root permission)
2. Unmounting:
sudo umount /mnt
if this fails, you need to use simg2img:
1. convert system IMG (SIMG) to ext4 IMG:
tools/simg2img ./_input/system.fex ./_input/system.img
2. make a system dir for mounting the converted IMG:
mkdir system
3. now mount the IMG to the newly created system directory:
sudo mount -o loop ./_input/system.img system
4. do you modding in the /system dir:
sudo nautilus (will execute "explorer" with root permission)
5. rebuilt the SIMG:
cd tools
sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
6. unmount the /system dir:
sudo umount system
Troubleshooting / FAQ:
*** Can I use an SD to wireless connect? ***
Yes you can! Go to the Wireless Menu (w) and choose option '5' (Copy Wireless ADB APP to SD), this will copy a wireless ADB
app to your SD (insert your SD in your computer before running this option). After the APP is copied to your SD:
1. Insert the SD in your device
2. Enable WLAN and connect to your home network
3. Start a file browser
4. Locate the SD in your device in the file browser
5. Install one of the copied APKs on your device
6. Start the installed APK
7. Take note of the IP the APP displays, this is your device's IP
8. In the Uberizer, go to the Wireless Menu (w)
9. Select option '6' (Connect to Wireless ADB device)
10.Enter the IP of your device
11.Enter the Port the Wireless ADB is running (leave blank for default port of 5555)
12.Uberizer will automatically rescan for connected devices, and should return the device model
*** Full Market / Google Play Store Function gives error: Error while retrieving information from server. [RH-01] ***
This usually happens when you start the google play store for the first time on the first reboot. Wait a minute, and retry.
*** Livesuit: Install the driver fail! The program will exit ***
if you have problems starting livesuit.exe, and receive the error message "Install the driver fail! The program will exit.":
1. You must connect your device to the system IN "flash mode" before starting the tool. On a MK802 MiniPC, Use a paperclip
to press the "upgrade" mode button located under the LED (small pinhole) WHILE connecting the MK802 to your computer. On
A1x tablets, this can happen when you don't press the volume up button of your device while connecting it to your PC. Shut
down your tablet, press the volume up WHILE connecting the usb to your computer, and retry to start Livesuit again. If you
did held the volume up button, and the device still is not recognized, you need to hold the power button of the A1X for
about 10sec, then retry the procedure.
2. Then, once the tool has started, browse for your IMG file that you want to flash.
3. Reconnect the device using the same method as described in 1. to automatically get the wizard for flashing a ROM, here
you can choose to format the device before flashing or to install the firmware keeping your current apps/data in tact.
*** HowTo Flash the A13 ***
1. Start Livesuit (see TechKnow's Downloads section for this app)
2. Power off the device
3. Press and hold the volume up button
4. Insert the USB connection cable to your computer while holding the volume up button
5. LiveSuit will detect a device being connected and will ask you what to do, you can format the device if you desire.
6. Follow the onscreen instructions
*** The A13-F9 is not recognized or has problems in Livesuit ***
1. Turn off your tablet
2. Press the key combination to start it in the upgrade mode
a. Press the "Vol -" key, then press the "Power" button, hold two buttons at the same time
b. Connect the USB cable to tablet and computer
c. After connecting the USB cable, press the power button 6 times quickly or hold the "Vol -" keys and the "Power" button
for more than 6 seconds (you should get a pop up window if done correctly , if not repeat step 5 from beginning)
d. DON'T release the "Vol -" button till the LiveSuit window pops up
e. You can now release the "Vol -" button
(Note: If you install the driver at this time the pop-up dialog box, the path to point to installation directory UsbDriver
LiveSuit folder, click Next to complete the driver installation prompts).
3. Select the format to force upgrade
Livesuit prompt "force format", click "Yes" (Y). All of the original
apps installed will be removed. We highly recommend mandatory format! !
!
Otherwise the update is not complete and may brick! ! !
Special switches:
c = cue fix, fixes cue files so you can easily cut the mp3's inside it using a tool
such as cuecutter. Can remove INDEX00 or INDEX01 entries in a sec for you. Use the
'ui' switch to integrate this feature in XP
i = install drivers, this pre-installs a lot of android drivers to your windows
inf directory so you can connect a device and it's automatically recognized
if the device is supported.
u = uninstall the driver files written to your INF directory.
ui= Uberizer Integrator, intgrates the Uberizer's special features in your system. E.g.
NFO files can viewed, CUE files can be fixed, ZDiR can be called from any directory
in the explorer, etc... currently only tested in XP, might fail using Win7.
n = nfo viewer, displays a black/green proper sized nfo file, use the 'ui' switch to
integrate this feature in XP
o = offline, does not try to scan for a device, this is handy when you use the
uberizer for amm (android multi mod) features to work with APK files for
example.
z = ZDiR, the directory manipulation tool. Generate directory indexes, directories,
filtered indexes and more!
help = a short help on howto connect your device, this documentation however is
recommended for trouble shooting / uberizer usage.
1-7 timer = pauses for the chosen amount of seconds. Since Microsoft stripped the
pause "seconds to pause" feature I needed to get my own timer for this
script to work.
Download:
www.mediafire.com/?6wnvzxmeepc11o1
السلام عليكم ورحمة الله وبركاته
اعضاء منتدي خبراء المحمول الكرام اليوم اتينا لكم بي
برنامج للتحكم باجهزة الاندرويد
تحميل البرنامج
www.mediafire.com/?6wnvzxmeepc11o1
وهذا الفيديو شرح تنصيب واستعمال البرنامج
This tool aims to support many android devices. Use the Uberizer to:
- * connect
* improve
* backup
* control
* debug
* unlock full play store
* mod
* optimize
* personalise
* root
* and more!
Uberizer Quickstart Guide:
Connecting your device to your computer:
To get started using the Uberizer you will need to connect to your computer. This can be done 2 ways:
* Wireless (RECOMMENDED) (REQUIRES ROOT!)
* Wired (Advanced users only) (Can ROOT devices)
The reason why wireless is recommend is because it's easy! Wired installation requires you to install
the ADB driver which can sometimes have problems, some devices have wierd ADB ports so you will have
problems finding the proper cable for it and some devices don't have ADB ports at all.
** Setting up your device for Wireless Uberizing (RECOMMENDED)
1. Go to the Wireless Menu (w)
2. Enable Wireless ADB using ONE of these options: 2, 4 or 5, whichever is most easy for your situation.
3. If you use an app (4 or 5), start the app on your Android device.
Use option 6 to connect to the given IP in the app.
If you chose option 2, you must find your device IP, go to Settings, About device, Status, to see the IP.
** Setting up your device for Wired Uberizing (Advanced users only)
1. Install ADB drivers (from dir usb_driver) for wired ADB
2. Boot Android, connect device (on the device, the statusbar will display "usb debugging mode is activated")
3. Run this tool, analyse device so this tool can seek info of your device
and will check if your model is supported by mods
NOTE: Your device must have "ADB Debugging" checked in: "Settings \
Developer options \ USB debugging (Debug mode when USB is connected)"
Uberizer main menu:
a. Analyse device (find model)
- Rescans for a device, use this after connecting another android device to your computer.
b. Build Menu
+ 1.Auto Mod build.prop
* Automatically adds several build.prop tweaks and enhancements.
+ 2.Edit build.prop and push it back
* A handy way to quickly check or edit a few build properties.
+ 3.Market build.prop fixes
* Strips out the current market fingerprint and copies the modded build.prop to the
device. Currently this emulates a Samsung for full market (Google Play) access.
+ 4.Backup current build.prop on device
* Dumps a copy of your build.prop to \backups, the prop dump name includes your model
name, the current date and time of dump. To easily restore these backups, run 5.
+ 5.Restore a build.prop backup
* Indexes all backupped build.prop files on the system and allows the user to chose
which file (s)he wants to restore on the tablet.
c. Root Menu
+ 1.Android 1.6 Donut (tested on WM8505)
+ 2.Android 1.6 Donut MAA (tested on WM8505)
+ 3.Android 2.2 Froyo (WM8650)
+ 4.Android 2.3 GingerBread (WM8710)
+ 5.Android 3.0 HoneyComb
+ 6.Android 4.0 ICS (tested on A13)
+ 7.Android 4.0 ICS MIPS (tested on Ainovo)
+ 8.Android 4.0 ICS (tested on WM8850)
+ 9.Android 4.0 ICS v2
+ 10.Android 4.0 ICS HTC (alpha)
+ 11.Backup current root bin and su app
* Backups the system\(x/s)bin\su bins and superuser.apk to \backups\system (x/s)bin and \app
+ 12.Restore root backup
* Writes the \backups su bins and superuser.apk back to the device.
+ 13.Unroots device
* Removes su bins and superuser from device and sets default back.
+ 14.Check device root
* Installs and starts the latest free version of Joey Krim's Root Checker
d. Backup Menu
+ 0.Full device "unmod" backup to backups\%MODEL%_%DATE%_%TIME%
* Creates a set of files that the uberizer tries to mod on your android device.
+ 1.Backup build.prop to backups\
* Dumps a copy of your build.prop to \backups, the prop dump name includes your model
name, the current date and time of dump. To easily restore these backups, run 5.
+ 2.Restore build.prop
* Indexes all backupped build.prop files on the system and allows the user to chose
which file (s)he wants to restore on the tablet.
+ 3.Backup bootanimation.zip to backups\
* Dumps a copy of your bootanimation to backups\bootanimation.zip
+ 4.Restore bootanimation.zip
* Displays a selection menu of bootanimation.zips from \backups and pushes the animation to your android device.
+ 5.Backup data\ to backups\data.tgz
* REQ ROOT. This will backup your full /data partition, very nice to backup all your
downloaded apps with their settings if you are planning to reflash your device.
+ 6.Backup data\app to backups\data_app.tgz
* REQ ROOT. This will backup only data\data\apps, your "downloaded" apps. Very useful
for sharing apps with your friends or when you are planning to reflash your device.
+ 7.Backup data\data 2 backups\data_data.tgz
* REQ ROOT. This will backup only all the app settings on your device.
+ 8.Restore 5. data.tgz backup
* Easily restore backups done with option 5.
+ 9.Restore 6. data_app.tgz backup
* Easily restore backups done with option 6.
+ 10.Restore 7. data_data.tgz backup
* Easily restore backups done with option 7.
+ 11.Backup current root bins and su app
* Backups the system\(x/s)bin\su bins and superuser.apk to \backups\system (x/s)bin and \app.
+ 12.Restore backed up root bins and su app
* Writes the \backups su bins and superuser.apk back to the device.
+ 13.Backup hosts file
* Backups your current hosts file of your device to backups\hosts_%date%_%time%.
+ 14.Restore hosts file
* Easily restore a previously backupped hosts file.
+ 15.Backup init files to backups\init.tgz
* This will take all init rc files from your device and stores them into \backups seperately,
but also this will make a tgz of the original files. This tgz is easy to recover using
option 16, because it's a tgz the original attributes remain. You can mod the seperately
dumped init files and adb shell chmod 750 them when you push them back.
+ 16.Restore init files backups\init.tgz
* Brings up a selection menu to easily select your previously created init backup.
e. Bootanimation Menu
+ 1.Backup current bootanimation.zip
* Dumps a copy of your bootanimation to backups\bootanimation.zip.
+ 2.Copy new bootanimation.zip
* Write back backups\bootanimation.zip to your android device.
+ 3.Delete bootanimation.zip on device
* This removes the bootanimation.zip from your device, this might slightly improve your
boot time.
+ 4.Recover backed up bootanimation.zip
* Brings up a selection menu with current backed up bootanimation.zip files in \backups.
f. Multi Mod Tool Menu
+ 1.undex (baksmali)
* Undex amm_files\undex_input_files\classes.dex to undex_output_files.
+ 2.dex (smali)
* Rebuilts dex from \dex_input_files and writes to dex_output_files.
+ 2a.dex (smali) dex default undex output dir
* Rebuilts dex from \undex_output_files\out and writes to \dex_output_files.
+ 3.Jar maker
* Creates one .jar file from \jarmaker_input_files dir, a generated .jar file will appear in jarmaker_output_files.
+ 3a.Jar maker using existing meta-inf\manifest.mf
* Creates one .jar file from \jarmaker_input_files dir, a generated
.jar file will appear in jarmaker_output_files with manifest.mf.
+ 4.APK sign (batch-mode)
* HcH's Microsigner, a simple way to sign a load of apks.
+ 5.Update.zip maker
* Creates simple update.zip file. Input dir \updatezip_input_files, Output zip file will be written in \updatezip_input_files
+ 6.Jarsigner
* A tool to sign jar files, certs/keys included! Input file: \amm_files\jarsigner_input_files\unsigned.jar
+ 7.OptiPNG
* Optimize those PNG files for maximum loading speeds! Dump all your pngs in optipng_files and run this option.
+ 8.framework-res.apk OptiPNG (alpha)
* A attempt to automatically optimize a framework-res.apk. This rebuilts the framework and signs it.
+ 9.batch extract and decrypt manifest from apks in \aapt_input_files
+ 10.batch generate APK application details from apks in \aapt_input_files
+ 11.batch generate APK extreme details from apks in \aapt_input_files
g. Application Manager Menu
+ 1.Batch install apps (from \install_apk)
* This installs all the apk files you have stored in \install_apk on your device.
+ 2.Install1app (select from \install_apk)
* This brings up a selection menu of all the apk files you have
stored in \install_apk on your device. You can select one you want to
install.
+ 3.Backup system apps to backups\sysappstgz
* Backups the system apps of your device to backups \system_apps.tgz
+ 4.Backup data apps to backups\data_appstgz
* Backups the data apps of your device to backups \data_apps.tgz
+ 5.Restore 4. data apps package to device
* This easily restores a previously created backup with option 4
+ 6.Backup 1 app to backup\ .apk
* Creates a list of all your downloaded apps, enter the generated number of the app
you wish to backup, and the app will be downloaded to \backups.
h. Help me
1.Go to the Wireless Menu (w)
2.Enable Wireless ADB using ONE of these options: 2, 4 or 5, whichever is most easy for your situation.
3.If you use an app (4 or 5), start the app on your Android device.
Use option 6 to connect to the given IP in the app.
If you chose option 2, you must find your device IP, go to Settings, About device, Status, to see the IP.
1.Install ADB drivers (from dir usb_driver) for wired ADB
2.Boot Android, connect device (on the device, the statusbar will display "usb debugging mode is activated")
3.Run this tool, analyse device so this tool can seek info of your device
and will check if your model is supported by mods
i. A1X Firmware Menu
+ 1.IMG unpacker
* unpacks rom_kitchen\original.img, the main files are stored in _input.
+ 2.IMG packer (rom_kitchen\_input)
* rebuilts your modded files that are previously extracted to a IMG file (output.img)
+ 3.Dump A1X firmware to Uberizer dir
* this will dump your A10 or A13 firmware in a sub directory of Uberizer.
+ 4.Restore A1X firmware from \rom_dumps
Restore a previously created rom dump with option 3. Special Thanks
to Satcomranger for risking his tablet's life and coding fixes for the
procedure.
+ 5.Start LiveSuit Pack v1.09
Start LiveSuit for manual flashing or formatting your A10/A13 device
j. Install full market
+ installs a hacked market apk with unrestricted market access, plus fake
the fingerprint of galaxy tab to gain more access. NOTE: if you have a
different cpu model than armeabi-v7a, like mips for example, you won't
see all available apps, you will see everything fit for your
"product.cpu.abi", you can see your cpu in the build prop (option b/2)
k. Various Mods Menu
+ 1. Sync device FS
* syncs android device's FS, for safe shutdown for example.
+ 2. Clean Dalvic Cache
* cleans the dalvic cache
+ 3. Add Tar 1.23 bin (auto backups old)
* this adds the real deal TAR binary to your android device!
+ 4. Install anti ad and malware hosts file
* adds the MVPS hosts file to protect you against the most known malware servers.
+ 5. Add GREP/EGREP/FGREP 2.6 bins
* adds the GREP binaries to your android device, enjoy full grep functionality!
+ 6. Add PHP v5.3.2 and Groomdroid webserver
* copies needed files and installs a PHP pre-configured Groomdroid web server.
+ 7. ICS Screen Capture to /screenshots
* takes a screenshot of your screen and stores it in /screenshots
+ 8. Add Capture ICS bin to device
* adds the ICS capture bin to your device, EXPERIMENTAL FEATURE . UNTESTED
+ 9. Add bash 4.1 bin to device
* for those Shell Ninjas out there, here it is ... BASH 4.1 on android!
+ 10. Config Groomdroid on device
* easily edit your config.
+ 11. Auto Market and Framework Cache clean
* performs the "market flush" for you.
+ 12. System App Remover (with auto backup)
* Makes a list of all the system apps with numbers, input the prefixed number and
the system app will be automatically backed up to /backups/%APKNAME%_%DATE%_%TIME%
+ 13. System App Restore
* With this option you can restore previously removed system apps.
+ 14. Remove Phone (with auto backup)
* This option will remove phone.apk and TelephonyProvider.apk from /system, without
any extra switches this will backup the removed items.
+ 15. Realtime LOGCAT Monitor 1024x768
* Starts a new command prompt window fit for 1024x768 resolution.
+ 16. Dump LOGCAT to TXT file
* Dumps the LOGCAT output as a TXT file in the Uberizer dir. After the dump has
completed, WinVi editor will open the generated TXT file.
Output file example: LOGCAT_npm702_NOVO7PALADIN_20122511_0202.txt
+ 17. Generate full device and bug report
* Dumps dumpsys, dumpstate, and logcat to a TXT file in the Uberizer dir. After
the dump has completed, WinVi editor will open the generated TXT file.
Output file example: BUGREPORT_npm702_NOVO7PALADIN_20122511_0205.txt
NOTE: This dump can take quite a while. If your device has vibration it will go
off once at the start of the dump and will go off twice when it's completed.
This dump can take up to one minute to complete.
+ 18. Dump DMESG (Diagnostic messages) to TXT
* Dumps out of DMESG in the Uberizer dir and opens the output file in WinVi,
Output file example: DMESG_npm702_NOVO7PALADIN_20122511_0234.txt
+ 19. Fix /data/local permissions
* Needed on some ICS roms when ADB installation fails.
+ 20. Backup and remove batterystats.bin
* Handy for re-calibrating your battery. Batterystats is file that actually follow
the usage of power by android apps. However, some problems conserning calibration
and indication can relate to this file.
+ 21. Backup and remove Unlock Pattern
Simply removes the settings.db so you can use your device again.
+ 22. Enter device's ADB shell
For all the shell ninja's out there
+ 23. Enter device's ADB shell (remountmode)
This remounts data system and root to be read write, consider this option as
browsing under root privileges, be careful what you mod! After you have closed
this shell session, the remounts remain active in the adb session. In other words
if you have problems modding your build prop for example, run this option, close it
and retry, good chance you can now edit system files.
+ 24. Edit init.rc and push back
For pro's only, allows you to modify your init.rc and copy the modified init.rc back
to your device. Handy for developers who are debugging.
+ 25. Edit init.%MODEL%.rc and push back
For pro's only, allows you to modify your init.rc and copy the modified init.rc back
to your device. Handy for developers who are debugging and people who have problems
with touch screen or gsensor on sun5i / a13 models to swap drivers.
+ 26. Clean dalvik-cache
Deletes everything in the dalvik-cache, reboot is required after this procedure, so
the system can rebuilt the cache on boot.
l. Files to SD (extsd)
+ This will write files from \files_to_sd to your device /mnt/extsd or /sdcard
m. Donate to TechKnow
+ How very kind of you to consider!
u. Update Uberizer
+ Connects to TechKnow and downloads the latest version, and installs it over itself.
q. Quit
+ A very common command that should not require explanation. However, quitting the
Uberizer cleans up it's temporary files and shut downs the adb server properly.
r. Reboot device
+ While your device is connected you can reboot it to see if certain mods are accepted
or other testing purposes. Uberizer will play pong with itself until your ADB is back online.
w. Wireless Menu
+ 1. Help and HowTo
* Short intro and HowTo on connecting your device
+ 2. Enable Wireless ADB through wired ADB
* When you are already ADB connected, you can start Wireless mode
+ 3. Disable Wireless ADB
* Wired or wireless, disables Wireless ADB server
+ 4. Wired install of Wireless ADB APP
* Install a ADB APP of choice to your device (2 loaded)
+ 5. Copy Wireless ADB APP to SD
* Prepare a SD card for the Uberizer
+ 6. Connect
* Connect your device to your computer/uberizer to use it. Your IP-address and you can specify
if desired a custom port, default port = 5555, leave the default port empty to use 5555.
x. Install Virtual OldPC 95 to device
+ This will copy the oldpc95 hd image with dos6.22, win2.3, win3.11 and win95, with 17 small games.
Run this image using the slightly modified aDosBox that will be installed with this command. To
enhance the screen quality, go to menu, sdl settings, video settings and select smooth the video.
A reboot is required, if your device is powerful enough you will have no delays. To start Win3.11
or 2.1 or Dos 6.22, on booting the dosbox image hit F5 and select option 5 from the boot menu, or
exit windows to command prompt in the shutdown menu. Run "autoexec" once you are in the prompt and
a helpful menu with the games will appear.
Changelog:
v1.4 (128 functions):
* uberizer various: added: 22. Enter device's ADB shell
* uberizer various: added: 23. Enter device's ADB shell (remountmode)
* uberizer various: added: 24. Edit init.rc and push back
* uberizer various: added: 25. Edit init.%MODEL%.rc and push back
* uberizer various: added: 26. Clean Dalvik-cache
* uberizer root: added x86 root with busybox 1.20
* uberizer root: fixed busybox bugs in root 7 and 9
* uberizer A1X fw: fixed step 3 on the restore function (recovery.img)
* uberizer main: fixed reboot routine
* uberizer main: fixed autodetection
* uberizer backups: fixed a bug in option 10
* uberizer main: added presetup for advanced system specific modifications (upcoming v2.0 feature)
Using the rom_kitchen:
This is the flash kitchen v2 modded to work with A1X IMG files and updated livesuit to 1.0.9, made
easy by some added scripts and automation.
Preparations:
1. a x64 Ubuntu or other linux system
2. a Windows system
3. \rom_kitchen\a10_tools.tar.gz extracted on your linux system
4. a base rom
5. a modkit, a set of files you have modded or wish to add/remove
6. ia32-libs, exe on your x64 ubuntu/linux system "sudo apt-get install ia32-libs"
HowTo:
1. put original.img in the root of the kitchen
2. run the uberizer to extract the original.img
3. mod the files in _input
-recovery.fex (see "Modding the recovery partition" in this document)
-root.fex (see "Modding the root" in this document)
-bootfs.fex (see "Modding the bootfs" in this document)
-system.fex (see "Modding the system partition" in this document)
4. rebuild running uberizer's create image function
Modding the root:
1. Extracting:
tools/split_bootimg.pl _input/root.fex
* this will give you root.fex-kernel the root.fex-ramdisk, check "Modding the ramdisk" in this document for details
2. Rebuilding:
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
tools/mkbootimg --base 0x40000000 --kernel root.fex-kernel --ramdisk
ramdisk-new.gz --cmdline 'console=ttyS0,115200 tw init=/init
loglevel=8' -o modded-root.img
this will give you a new file, modded-root.img
Modding the ramdisk:
1. Extracting:
mkdir ramdisk
cd ramdisk
gunzip -c ../root.fex-ramdisk.gz | cpio -i
2. Rebuilding:
check "Modding the root" part 2. in this document
Modding the bootfs:
1. Make some directory:
mkdir bootfs
sudo mount -t ext4 -o loop _input/bootfs.fex /bootfs
2. Edit files in /bootfs
3. Unmount the bootfs
umount bootfs
Modding the recovery partition:
1. Extracting:
tools/split_bootimg.pl ./_input/recovery.fex
rm -rf ramdisk
mkdir ramdisk
cd ramdisk
gunzip -c ../recovery.fex-ramdisk.gz | cpio -i
2. Rebuilding:
*sudo apt-get install ia32-libs
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
tools/mkbootimg --base 0x40000000 --kernel recovery.fex-kernel
--ramdisk ramdisk-new.gz --cmdline 'console=ttyS0,115200 rw init=/init
loglevel=8' -o modded-recovery.img
Modding the system partition:
1. Mounting:
sudo mount -t ext4 -o loop system.img /mnt
start modding! (SU permissions required!)
*sudo nautilus (will execute "explorer" with root permission)
2. Unmounting:
sudo umount /mnt
if this fails, you need to use simg2img:
1. convert system IMG (SIMG) to ext4 IMG:
tools/simg2img ./_input/system.fex ./_input/system.img
2. make a system dir for mounting the converted IMG:
mkdir system
3. now mount the IMG to the newly created system directory:
sudo mount -o loop ./_input/system.img system
4. do you modding in the /system dir:
sudo nautilus (will execute "explorer" with root permission)
5. rebuilt the SIMG:
cd tools
sudo ./mkuserimg.sh -s ../system ../new-system.fex ext4 ../tmp 300M
6. unmount the /system dir:
sudo umount system
Troubleshooting / FAQ:
*** Can I use an SD to wireless connect? ***
Yes you can! Go to the Wireless Menu (w) and choose option '5' (Copy Wireless ADB APP to SD), this will copy a wireless ADB
app to your SD (insert your SD in your computer before running this option). After the APP is copied to your SD:
1. Insert the SD in your device
2. Enable WLAN and connect to your home network
3. Start a file browser
4. Locate the SD in your device in the file browser
5. Install one of the copied APKs on your device
6. Start the installed APK
7. Take note of the IP the APP displays, this is your device's IP
8. In the Uberizer, go to the Wireless Menu (w)
9. Select option '6' (Connect to Wireless ADB device)
10.Enter the IP of your device
11.Enter the Port the Wireless ADB is running (leave blank for default port of 5555)
12.Uberizer will automatically rescan for connected devices, and should return the device model
*** Full Market / Google Play Store Function gives error: Error while retrieving information from server. [RH-01] ***
This usually happens when you start the google play store for the first time on the first reboot. Wait a minute, and retry.
*** Livesuit: Install the driver fail! The program will exit ***
if you have problems starting livesuit.exe, and receive the error message "Install the driver fail! The program will exit.":
1. You must connect your device to the system IN "flash mode" before starting the tool. On a MK802 MiniPC, Use a paperclip
to press the "upgrade" mode button located under the LED (small pinhole) WHILE connecting the MK802 to your computer. On
A1x tablets, this can happen when you don't press the volume up button of your device while connecting it to your PC. Shut
down your tablet, press the volume up WHILE connecting the usb to your computer, and retry to start Livesuit again. If you
did held the volume up button, and the device still is not recognized, you need to hold the power button of the A1X for
about 10sec, then retry the procedure.
2. Then, once the tool has started, browse for your IMG file that you want to flash.
3. Reconnect the device using the same method as described in 1. to automatically get the wizard for flashing a ROM, here
you can choose to format the device before flashing or to install the firmware keeping your current apps/data in tact.
*** HowTo Flash the A13 ***
1. Start Livesuit (see TechKnow's Downloads section for this app)
2. Power off the device
3. Press and hold the volume up button
4. Insert the USB connection cable to your computer while holding the volume up button
5. LiveSuit will detect a device being connected and will ask you what to do, you can format the device if you desire.
6. Follow the onscreen instructions
*** The A13-F9 is not recognized or has problems in Livesuit ***
1. Turn off your tablet
2. Press the key combination to start it in the upgrade mode
a. Press the "Vol -" key, then press the "Power" button, hold two buttons at the same time
b. Connect the USB cable to tablet and computer
c. After connecting the USB cable, press the power button 6 times quickly or hold the "Vol -" keys and the "Power" button
for more than 6 seconds (you should get a pop up window if done correctly , if not repeat step 5 from beginning)
d. DON'T release the "Vol -" button till the LiveSuit window pops up
e. You can now release the "Vol -" button
(Note: If you install the driver at this time the pop-up dialog box, the path to point to installation directory UsbDriver
LiveSuit folder, click Next to complete the driver installation prompts).
3. Select the format to force upgrade
Livesuit prompt "force format", click "Yes" (Y). All of the original
apps installed will be removed. We highly recommend mandatory format! !
!
Otherwise the update is not complete and may brick! ! !
Special switches:
c = cue fix, fixes cue files so you can easily cut the mp3's inside it using a tool
such as cuecutter. Can remove INDEX00 or INDEX01 entries in a sec for you. Use the
'ui' switch to integrate this feature in XP
i = install drivers, this pre-installs a lot of android drivers to your windows
inf directory so you can connect a device and it's automatically recognized
if the device is supported.
u = uninstall the driver files written to your INF directory.
ui= Uberizer Integrator, intgrates the Uberizer's special features in your system. E.g.
NFO files can viewed, CUE files can be fixed, ZDiR can be called from any directory
in the explorer, etc... currently only tested in XP, might fail using Win7.
n = nfo viewer, displays a black/green proper sized nfo file, use the 'ui' switch to
integrate this feature in XP
o = offline, does not try to scan for a device, this is handy when you use the
uberizer for amm (android multi mod) features to work with APK files for
example.
z = ZDiR, the directory manipulation tool. Generate directory indexes, directories,
filtered indexes and more!
help = a short help on howto connect your device, this documentation however is
recommended for trouble shooting / uberizer usage.
1-7 timer = pauses for the chosen amount of seconds. Since Microsoft stripped the
pause "seconds to pause" feature I needed to get my own timer for this
script to work.
Download:
www.mediafire.com/?6wnvzxmeepc11o1