latest] Uberizer v1.7 21OCT2013

♠ Posted by ggg in All Android tools at 06:06

Uberizer v1.7 by HcH [www.TechKnow.me]
__________________________________________________ _________________________
.|ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ|.
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛ _____________ ÛÛÛÛÛÛÛ||
||ÛÛÛÛ .' '. ÛÛÛÛ||
||ÛÛ / \ ÛÛ||
||Û /', ,'\ Û||
|| | ' ' | ||
|| Uberizer | '. .' | TechKnow ||
|| --___' '___-- ||
|| . _ . ||
|| : /_\ : ||
|| "' " '" ||
|| "'"" .___. ""'" ||
|| "' /_____\ '" ||
|| " . . " ||
|| : : : : ||
|| "' '" ||
|| "'"" ""'" ||
|| "' '" ||
|| " " ||
|| : : ||
|| ||
||Û >!< DON'T HURT THE NERD >!< Û||
||ÛÛ ÛÛ||
||ÛÛÛÛ HcH[********Hacker] ÛÛÛÛ||
||ÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛ -presents- ÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛÛÛÛÛ||
||ÛÛÛÛÛÛÛ ÛÛÛÛÛÛÛ||
||ÛÛÛÛ ÛÛÛÛ||
||ÛÛ ÛÛ||
||Û \ / Û||
| ________________________/\ Uberizer v1.7 /\_______________________ |
.' / \ '.
| /T=---------------------------------=T=---------------------------------=T\ |
|| | .RLS.Date. : 21/OKT/2013 | ..Language.. : English | ||
|| | ....OS.... : WinALL | .Protection. : Does not apply | ||
|| | ...Type... : Android Manager | ...Hacker... : HcH | ||
| \I=---------------------------------=I=---------------------------------=I/ |
[ ] [ ]
/ \
| INFO: |
|| Uberizer is a tool to manage Android devices: ||
|| connect, backup, control, debug, unlock full play store, mod, optimize, ||
|| personalise, root, monitor, improve, and many more features! In total, ||
|| Uberizer offers 176 functions to mod/hack/optimize Android devices and ||
|| even Android apps! ||
| \ / |
[ ] [ ]
/ \
| |
| |
: :
:: ::
'" __________________________________________________ ___________<CRAPASCII> '"
]| / \ |[
||/ \||
|/ \|
: :

Quote:

Uberizer v1.7 by HcH [www.TechKnow.me]

The Uberizer 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) (This method can ROOT devices which aren't rooted)

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)"
download from here :Uberizer_v1.7_21OCT2013_Setup_[www.TechKnow.me]-HcH

Uberizer main menu overview:
a. Analyse / detect device
b. Build Menu
c. Root Menu
d. Backup Menu
e. Bootanimation Menu
f. Multi Mod Tool Menu
g. Application Manager Menu
h. Help me
i. AllWinner Firmware Menu
j. Google Play Store Menu
k. Various Menu
l. Files to SD
m. Donate to TechKnow
o. Open Uberizer directory
p. WiKey, PC Keyboard to Android Device
q. Quit
r. Reboot device
s. System analyzer
t. Install TechKnow ToolKit to device
u. Update Uberizer
w. Wireless Uberizer mode
x. Install Virtual OldPC 95 to device
z. ZDiR

Uberizer main menu details:
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.

Code:

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 WM8850/RK3066/google_sdk
+ 9.Android 4.0 ICS v2
+ 10.Android 4.0 ICS HTC
+ 11.Android 4.0.X ICS X86
+ 12.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
+ 13.Restore root backup
* Writes the \backups su bins and superuser.apk back to the device.
+ 14.Unroots device
* Removes su bins and superuser from device and sets default back.
+ 15.Check device root
* Installs and starts the latest free version of Joey Krim's Root Checker
+ 16.HcH's Brute-Root v1 (recommended) 2.x-4.x
* Tries to enforce a write-able FS so SU can be copied to it, works on most chinese tablets.
+ 17.HcH's Brute-Root v2 (only when v1 fails)
-Roots almost every device (HTC/LG/SAMSUNG/A20)
-Reboots your device twice for this procedure
-Safe root, it should not be risky to use this tool
-No busybox installation
-Superuser bin and app v3.1.3
+ 18.WM8880 Root
HcH's trick to get SuperSU properly working on a WM8880:
Instructions:
1. Enable ADB in settings \ developer options \ USB debugging
2. Enable SU in settings \ Superuser setting \ Always allow
3. Connect device to your PC and install the driver from Uberizer\usb_drivers
4. Follow the procedure
5. Run SuperSU once manually, upgrade the bin, and it should be fine!
6. Test it using TechKnow ToolKit
+ 19.Root Upgrade submenu
1. Root backup
Backups the current superuser and su bins on your device to changer_files\system
2. Root restore (only required if failed)
Restores backed up root files done with option 1. It does not write back symlinks however so you may need to manually link the bins together on the FS.
3. Enable ADB Root Mode
Tries to get full access to a device using adb root
4. Enable ADB Remount Mode
Tries to get full access to a device using adb remount
5. Remount RootFS
Tries to get full access to a device using remount command
5a.Remount RootFS busybox mode
Tries to get full access to a device using remount command
6. Remount System
Tries to get full access to a device using remount system command
6a.Remount System busybox mode
Tries to get full access to a device using remount system command
7. SuperSU-v1.65
SuperSU of Chainfire v1.65 including NoNag and SuperSU bins
8. Superuser-3.1.3-arm
SuperSU of Androidsu v3.1.3
9. Superuser-3.1.3-x86
SuperSU of Androidsu v3.1.3
10. Superuser-3.2-RC3-arm
SuperSU of Androidsu v3.1.3
11. Superuser-3.2-RC3-x86
SuperSU of Androidsu v3.1.3
r. RESET ADB
When you get "error: device not found" hit "r" to RESET ADB then try another way to get more access to your device.
h. ROOT HELP
Short Help Me for Using the Uberizer to root devices.

The recommended first try you attempt to get root is Brute-Root v1, it's safe
and should not harm your device. However you may run into error such as:
"adbd cannot run as root in production builds" when it tries to to get access.

If you already have root and just wish to update your superuser app
and superuser bin you can use the Root Upgrade submenu. These procedures try
to just write certain nice root apps and bins combinations.

Making a backup is always most wise Always do so BEFORE you start modding.
Option 1. dumps all the bins and apps it can find on your device to your pc,
if no error occurs on the screen. Option 2. restores whatever you have backed
up using option 1. It does not write back symlinks however so you may need
to manually link the bins together on the FS.

If you try to upgrade root and it fails, you can try options 3. to 6a. to get
access to the devices FS. After you have input one of these options just retry
the last procedure that has failed and it very well could succeed after one of
of these commands. When you get "error: device not found" hit "r" to RESET ADB
then try another way to get more access to your device.

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 from \amm_files\apksign_input_files\ to \amm_files\apksign_output_files\.
+ 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
+ 12.Update.zip signer, signs amm_files\updatezip_input_files\ zip files, warning, do not use spaces in the filenames.
+ 13.ZIP align (batch-mode), aligns all zips in amm_files\zipalign_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.
+ 7.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%
+ 8.System App Restore
* With this option you can restore previously removed system apps.

h. Help me
Connecting Wireless/Driverless (ROOT REQUIRED!):
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.

Connecting Wired/Driver:
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. AllWinner 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.11
Start LiveSuit for manual flashing or formatting your A10/A13 device
+ 6.Alternative IMG unpacker (by RedScorpio)
Brings up a IMG selection MENU that lists all IMG files in uberizer\rom_kitchen\_input for extraction.
The unpacked ROM will be stored in \rom_kitchen\_input\%ROMNAME%.DUMP\*, edit / modify the data, leave it in this directory!
Then run option 7 to repack it!
+ 7.Alternateive IMG repacker (by RedScorpio)
Brings up a selection MENU for .DUMP directories, select a number to rebuild the IMG from this directory.
If the original IMG file still exists while you're making the new ROM it will be renamed to .bak. A IMG file with the same
name as the directory will be output in: \rom_kitchen\_input\
+ 8.Dump script.bin (to uberizer root dir)
This command remounts the boot fs so it can pull the script bin from your device. The script bin contains valuable information about touchscreen and other hardware specs. This procedure is recommended before flashing A10 or A13 devices.
+ 9.Convert script.bin to script.fex
Converts the dumped script.bin into a fex file so you can edit it.
+ 10.Edit script.fex
Brings up WinVi32 and let's you modify the converted bin fex file.
+ 11.Script.fex to bin converter
Before you can use the modified bin you need to convert it back into a bin file with this command.
+ 12.Push converted script.bin to device
Writes back the modified script.bin to your device, reboot and the effects should be active.

j. Google Play Store Menu
+ 1.Install Normal Mode
Deploys Google Play Store version 4.3.11 to device without any form of remount/root request.
+ 2.Install Remount Mode
Deploys Google Play Store version 4.3.11 to device with adb remount for write access. Use this option when a normal install fails.
+ 3.Install Root Mode
Deploys Google Play Store version 4.3.11 to device with adb root for write access. Some distros require you to write the new Play Store this way. Use this option when a normal install fails.
+ 4.Fake Nexus10 build for full access
Makes a backup of your current build.prop file to %UBERIZERDIR%\backups\ and modifies the build.prop on the device to emulate a Nexus 10 in order to get full play store access unlocked. This procedure also automatically clears out the Google Services Framework Data and Google Play Store cache.
+ 5.Clear Market Cache
This procedure also automatically clears out the Google Services Framework Data and Google Play Store cache.

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. Market and Framework Cache clean
* performs the "market flush" for you.
+ 12. Clean dalvik-cache
Deletes everything in the dalvik-cache, reboot is required after this procedure, so
the system can rebuilt the cache on boot.
+ 13. HcH's Android Lock Crusher
* HcH's Lock Crusher will remove passwords, lockscreen and locks from Android devices,
it will attempt to get the best access to a connected device and tries to remove them
all, but not before making backups of the files that are deleted in this procedure to
\backups.
+ 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.

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.

s. System analyzer
+ Analyzes connect Android devices and give a true load of information about anything like processor, ram, memory, storage, modules. Dumps a text file in the Uberizer root directory with all your device's system specs.

t. Install TechKnow ToolKit to device
+ TechKnow ToolKit Features v2.0:
* WM8505 Analyzer
* A10 / A13 Dump Firmware to SD
* A10 / A13 Pull and Push script.bin
* Shutdown
* Reboot
* Reboot into Recovery
* Hidden feature
* Wireless Uberizer / ADB control panel
* LogCat viewer (plus write log to SD function)
* Error LogCat viewer (plus write log to SD function)
* Root Check
* BusyBox Check
* Analyser
* WM Analyser
* Remount FS RW
* IP Config

TechKnow ToolKit Function overview:
+ Wireless Uberizer / ADB control panel
Enjoy the wonders of wifi running driverless ADB to your computer. This way, you can also use the Uberizer Wireless to manage your device! (root is required for this function)
+ WM8505 Analyzer
Before you flash your WM8505 be sure to run this tool! It will save essential recovery information in the case you flash the wrong ROM! With some extra command and the created text file by this function you can easily fix your non function touch screen, no sound and crashes on the camera for example!
+ A10 / A13 Dump Firmware to SD
Before you flash any A1X device, it is most wise to make a backup of your current firmware. The bootloader, recovery, system, etc will be written to your SD card, make sure you have one present at the time of dumping!
+ Shutdown, Reboot and Reboot into Recovery
On the MK802 and the MK808 we don't have a nice shutdown function. This results in losing data after a reboot due the FS didn't synchronize when you powered off. Apps can get lost and data will be lost when you disconnect the power. These functions safely sync the FS and try to shutdown your device. Root access is required.
+ A10 / A13 Pull and Push script.bin
The script.bin file of the A1X models contains essential information of your device's configuration. With this function, you can very easily recover from a bad flash in most cases. Make sure you run this command before you write the new firmware!
+ LogCat viewer (plus write log to SD function)
Easily view your logcat for debugging problems. This option also offers you to dump the logcat output to your SD for further investigation on your desktop or to post the logcat output on TechKnow so the TechKnow Technicians can investigate your problem with all the required details.
+ Hidden Feature
I'm sure you'll quit looking for it.
+ Root Check
Simply asks superuser permissions, real handy to have when you're developing a ROM or when you are trying to root your device using the Uberizer to test superuser permissions. This also outputs the error on the su command.
+ BusyBox Check
We can not live without BusyBox, it will expand your device functionality greatly and it's required for some apps, such as the TechKnow ToolKit. This command simply checks if a busybox bin is present, then it displays what version is available. However, do note that this output does not mean busybox is properly installed. Some devices require you to execute "busybox --install" to get in the system, be warned however, there are reports of members losing root access by installing busybox. Busybox carries it's own su binaries which could overwrite the ones your firmware require!
+ Analyzer
Generating a device report was never this easy! This option also offers the user to write the report to SD, so the user can post the analyser output for specifications when requesting help/firmware etc. Details include: cpu info, partition info, build.prop and much more! NEW in v2.0: Extended partition/FS/module info.
+ WM Analyzer
A must have for anyone thinking of installing a Universal WonderMedia Uberoid version. This functions allows you to save the essential parameters of your device and for 8850's it will tell which FWC (model) you will need to flash! Always write the output of the WM Analyser to your SD BEFORE installing Uberoid will ensure you won't have problems that can not be fixed after flashing.
+ Remount FS RW
Devices such as the 8850 have the system set to RO, this is due security measures which are fine. However, sometimes you will need to remount the FS RW so you can edit some files. This function tries to remount your system, it works on my devices but it's possible this function will not work on all devices.
+ IP Config
Shows your IP easily without having to go to all those menus.

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.

Shamim

latest] Uberizer v1.7 21OCT2013

0 comments:

Post a Comment