Dex manager&Kernel flasher - General Topics

This is a program my friend and me created to improve our programming skill
and to make decompiling dex files a breeze.
How to use?
1) Start DexManager.exe
2) Place classes.dex in same folder as program and hit decompile
3) Edit files in the new folder "out"
4) Hit recompile, after recompile is complete it will be in the root directory, named "classes.dex".
Done!
Download and screenshot in attachments
Change log
Beta5
Added:
-Higher heap values to support larger files (512MB heap)
-optimised code a little
-Progress bar does not mis-lead values
Release 1
Added:
Added kernel flasher (fastboot)
Now has clear temp (Clears all temp files program created)
Requirements:
-5mb of System memory (FREE MEMORY)
-Internet connection for the updates.
To come:
Customizable config
You will now be able to receive the update via the program.
you will receive a notifacation when an update is avliable.

Thank you very much, plus easy to use, well

I shall update this later. Updater and more configurable for those that dont have PATH for Java installed.
-Scriptr

Thanks bro. I will give it a try.

Please report any bugs you encounter to me or Slethen,
thanks.

Update 407 (beta 5.1)
-Reads a config, customizable.
-Easier GUI
I'm open for features that could be added

Related

Droid Explorer - 0.8.7.0 [7/13/2010] - The Gibson

Droid Explorer is the #1 Open Source Android device manager for Rooted devices.
Device Requirements
Rooted Android Device with busybox
Guide to installing busybox on the Droid
PC Requirements
Windows (looking for a developer to help create UI for mono)
.NET Framework 3.5 SP1
Some plugins require Java Runtime Environment and Java Web Start
Confirmed Devices
All Devices have been rooted and busybox installed
HTC Dream / G1 / ADP1
HTC Sapphire / Magic / MyTouch 3G / ADP2 / Ion
HTC Hero / G2 / CDMA Hero
Google Nexus One
Motorola DROID
Samsung Galaxy / i7500
Acer Liquid
HTC EVO
Features
Includes the required windows USB drivers - you will be prompted to install the drivers during installation if running vista/7
Auto setup of Android SDK tools and drivers during install
Use an existing Android SDK if you already have one set up
Multiple Device Support
No need to mount SD card to access files
Copy any file on the device to PC
Copy files to clipboard
Copy update to device and auto-apply
Drag & Drop copying from Explorer to Droid Explorer
Auto detection of connected/disconnected device
Open files on PC
Plugin Framework
Application Manager
Right Click APK to install/uninstall
Take screen shots of device (landscape & portrait)
Open right from "My Computer" (a lot like how WinMobile is with active sync)
SQLite Manager Plugin
Uses System Icons for files displayed in explorer
Familiar Explorer like UI, including an Explorer like location bar
Android Screencast plugin
Install/Uninstall APK files right from explorer
Standalone plugin runner
Window 7 JumpLists for plugins
DesktopSMS plugin - Send SMS messages from your desktop
Service can be controlled now from the options dialog (can create the service if you do not use the installer)
Backup plugin for the "Bare Bones" Roms
Run shell scripts on the device by double clicking them
{
"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"
}
I'd like any thoughts you may have for other features to add to Droid Explorer. Report bugs or request features here or on the project issue tracker.
Web Installer (x86)
Requires internet connection to download android sdk tools
x86 Serivce will not work on x64 OS
Web Installer (x64)
Requires internet connection to download android sdk tools
Use this install if running a 64 bit OS
Standalone Installer (x86)
Does not require internet connection. Larger download.
Standalone Installer (x64)
Does not require internet connection. Larger download.
Use this install if running a 64 bit OS
Older Releases
Source Code Available at CodePlex
Change log 0.8.7.0
Can now use existing SDK instead of the "trimmed" version
Settings stored in the registry now check both Local Machine and Current User
Lots of other little fixes
Change log 0.8.6.0
fixed missing file in the standalone installer
added check for minimum .net framework version in to bootstrapper (v3.5sp1)
increased the service start/stop timeout in the bootstrapper from 30 seconds to 60 seconds
removed initial strings from download panel labels of bootstrapper
htc desire / bravo icon added for attached devices - thanks to beadza for identifying the device
added ability to only install the SDK Tools by running install with /sdk switch
sdk install mode checks if DE is installed, if not, it switches to full install mode
bart plugin now also checks the sd-ext mount point for the license.
added the sd-ext app paths as valid application paths
added sd-ext app paths to the application backup plugin
removed anda.pk plugin as the site is dead.
screencast plugin changed to pull the jnlp file directly from the trunk of the project. If there
is an error, it falls back to a "local" file
fixed issues with spaces in folder names
motorola backflip icon added for attached devices - thanks to zibiza for identifying the device
new screenshot app that handles all resolutions. Uses new methods to get the framebuffer data
adjusted the RGB565 class to better handle other devices for screenshots
started to implement communicating with adb over TCP like ddms does.
acer liquid icon added for attached devices - thanks to fyodor0218 for identifying the device
started working on the ability to use existing sdk (not yet an option, but soon)
Change log 0.8.5.1
Fixed typo in the final step when uninstalling
Fixed x64 issues for windows 7 x64 - still broke on Vista x64 & XP x64 (sorry people, i'm still working on it!)
Default button for bootstrapper changed to the "next" button instead of cancel
added incredible icon for attached devices
added nexus one icon for attached devices
added galaxy S (gt-i9000) icon for attached devices
added acer liquid icon for attached devices
updated the samsung moment icon
added a new "open" version of the moment - rename in the assets directory to "moment.ico" to use.
Change log 0.8.5.0
android screen cast updated to load the lastest build from the trunk
changed publish to use skydrive share instead of the api from the msbuild tasks
added platform tools 2.2
added sdk tools r6
updated repository.xml
added help video link when the device cannot be found
attempting to fix the registry read issues with XP SP3 x64 and Vista x64
removed the "fade out" of the expandos from the treeview to remove the flicker
fixed the issue with opening offscreen
fixed workitem:10275, changed "Close" to "Finish" in the description of the final step of installer
fixed the "hanging" of trying to delete a file. added the '-f' switch to never prompt.
Change log 0.8.4.3
Fixed the install / start up issues caused by the platform tools having a typo in the file name
Change log 0.8.4.0
Fixed issue with cyanogen 4.2.14.x
fixed issue with bart manager plugin license (sorry for the delay)
added 2.1 r1 platform tools
added usb drivers r3 - adds support for nexus one
fixed issue with install plugin crashing if application is already installed.
Change log 0.8.3.0
Fixed bug with device not identifying recovery mode
Display QR code to purchase bart manager if license not found.
mount partitions in recovery mode to find bart manager license
bart manager now attaches to process to output the info
another attempt to set as root when starting for non-adp devices
There is a known bug with droid explorer detecting a device already "connected" going in to recovery mode.
Flash recovery now works in any mode, not just recovery
bart manager license now available for purchase on market.
Change log 0.8.2.3
Drivers removed for windows XP until XP issue with the drivers can be resolved.
added device icon for the nexus one / passion
Code setup to allow some plugins to be purchased.
The .net 3.5 check has been removed for the time being until a better solution can be implemented.
build published via [url:MSBuild Deployment Tasks|http://mdt.codeplex.com]
some bugs fixed here and there
What happened to 0.8.2.2? - Windows locked the directory when I was building that version so it failed and I couldn't delete it to rebuild so I skipped it.
Change log 0.8.2.1
Fixed install issues with 0.8.2.0 - should install for x86 and x64
Change log 0.8.2.0
created a WiX custom action library for checking for the android usb drivers
install logging is now merged in to one file and off by default. use /l[og] to turn on logging
tools will always be downloaded/extracted during install. This lets the tool update to newer tools if needed
fixed delete file when the file name has a space in the file name.
sdk tools upgraded to r4
fixed bug in uninstall if the service did not exist on the machine
should now successfully check for the android usb drivers and install them if revision 2 is not installed.
remember location of "open file dialog"
added code that should check for .net 3.5 sp1 before "crashing" for not having it installed.
added check that the user is installing the correct version (x86 or x64) for their system
Change log 0.8.1.0
added a splash screen so the user is aware that the app is running right away
.NET Framework 3.5 SP1 check added to installer.
apk shell extension now uses the path stored in the registry for the tools.
added logging to the install process
kill all adb processes before attempting to cleanup the sdk path during install.
apk seems to not be working, still debuging the issues. it will be back.
defined a platform constant to the project scripts, x86: PLATFORMX86, x64: PLATFORMX64, ia64: PLATFORMIA64
fixed bug with reading / writing to the registry in x64. now looks in HKLM\Software\WOW6432Node\
fatal errors are now caught and user given option to restart app, close app, or report bug
there is still a bug with installing the driver, the check isnt working so the driver still needs to be installed manually.
Change log 0.8.0.1
fixed installer issue where it crashed if you do not have a proxy set up
x64 installer has issues. - Tempory Fix - Will fixed in next release
Change log 0.8.0.0
added the r2 windows usb drivers, which add support for droid and other devices
added new checks for the drivers. Checks for dream/magic/sholes - these are the devices that google defines in the .inf file.
images moved to external resources library
changed the installer images to be more "custom"
removed need for droid explorer to require "run as administrator" - Yay!
the bootstrapper now handles starting the service. This makes sure the sdk is setup before it starts.
bootstrapper is self contained, the msi is an embedded resource and all referenced assemblies are ILMerged
repository file is hosed on the droid explorer google code site, it is based on the same one that google uses for the android sdk setup
the tools are also hosted on the google code site, this is so the download size is smaller, since all unused bits are removed.
A fully standalone version of install is also available. No need for internet access to install.
boot strapper support uninstall - setup.exe /uninstall
removed reference to the "common.shared" assembly.
added a properites dialog for folders/files
properties dialog shows security settings as well.
fixed icons in context menu for new folder/file
Change log 0.7.12.0
fixed the error that anda.pk plugin logs when it starts because it did not implement "Runnable"
shell extension for apk files so the apk icon displays in explorer - based on http://code.google.com/p/apkshellext/
seems there is a bug in some APKs that dont display their icon, nor do they display the default icon.
registers and unregisters the shell extension on install/uninstall
driver check now works better in the installer
removed some tools menu items that have been replaced by plugins
Installer now gives "options" on what features to install
changed default apk icon to be the "android package" icon
fixed bug with launching ddms and hierarchy viewer
fixed bug launching the google applications backup plugin
added methods to the core command runner to make a mount point read/write and readonly
added icon for the motorola droid
added icon for the samsung moment
added icon for the htc droid eris
Change log 0.7.11.0
USB Drivers installed - This is still in "alpha", should only install them if you need them. please report any issues. It doesn't actually install the drivers, it places them in the driver store, when the device is attached, and the new hardware wizard displays, selecting "automatically install (recommended)" should find the drivers automatically. This installs the 1.6 drivers.
fixed logcat not starting
created a new logcat console that colorizes the log entries
save the logcat output (minus the log level indicator (W/I/D/E/))
support for android screencast 0.2
Change log 0.7.10.1
Fixed crash on device going from connected to disconnected state
Change log 0.7.10.0
Sign Package plugin (signs zip file with test keys)
modified IPlugin to now have methods for creating the toolstrip button and menu items
DroidExplorer.Core.Plugin.PluginHeler added. Contain default static methods for creating the toolstrip button and menu
and.apk now a plugin instead part of "core"
started a contacts manager
started a tool to export facebook contacts from official application to android contacts
added "recovery" as device state.
now "attaches" while in recovery mode.
screenshot now works in recovery mode.
screenshot rotates the current image before refreshing when switching between landscape & portrait
flash recovery image now a plugin - only active when in recovery mode
some bug fixes that I don't remember the exact details on
Change log 0.7.9.0
new shell console enhanced
getprop wrapped to get device properties
explorer icon now attempts to load an icon of the device
- Known devices:
- Bahamas (Tattoo)
- GT-I7500 (Galaxy)
- Hero (G2/Hero)
- Sprint Hero (do not yet know what it identifies itself as in ro.product.device may just show normal hero)
- cliq (need to verify what ro.product.device returns)
- Saphire (MyTouch3G/ION/Magic)
- Dream (G1/ADP1)
- Pulse (need to verify what ro.product.device returns)
- Zii Egg (need to verify what ro.product.device returns)
Device properties viewable in options->environment->known devices->[device-serial]->properties (only when device is connected)
fixed bug with screenshot image being landscape but window portrait.
fixed bug with large icons not always showing the right icon
Change log 0.7.8.0
Desktop SMS now launched from officially signed jar file
Plugin tool strip disabled / enabled when device disconnected / connected
SymLinks and Directories can now also be renamed
F2 starts file/link/directory rename
Executable files now run if double clicked (open from context menu)
Shell Console (could still be buggy so the normal shell window is still available)
double clicking sh scripts run them
plugins that are registered as a file type handler will show up in the right click menu for the file
Change log 0.7.7.0
Renaming of files (folders and links coming)
Google Application Backup (GAB) plugin added
GAB supports HTC's ADB1 update packages (containing system.img), pulling from the device or from normal update.zip
Screen shot plugin supports portrait & landscape modes (use button or right click image)
Screen shot threaded so it doesn't "hang"
Change log 0.7.6.0
Fixed screen shot plugin from opening off screen if droid explorer is maximized or positioned on the right of the screen.
Check for the USB Driver version and download the tool set based on that. If you select the sdk yourself, you must select the correct tools yourself.
USB Driver Version info available in Options->Environment->Android SDK
Speed up of navigating to different directory. Reduced the number of LS calls that are made to build the tree and listview
Change log 0.7.5.0
Fixed plugins executing when loading within Runner
Fixed bug with additional plugin getting the same changed values as other plugin.
Change the SDK path from the Options dialog (requires restart of application)
Fixed bug with apk's not displaying.
Fixed Batch Installer not "showing"
provided a way to manually install, start and stop the droid explorer service - for non-installer users
added ability to save debug output to a file
moved debug window filter buttons to the right
debug window will display below DE if there is room, otherwise, it will display at the top of the screen
added plugin to launch DesktopSMS. Requires the DesktopSMS Server APK be installed on the device - Currently usinging a signed jar by me, hopefully the developer will sign his version.
can now copy symlinks files to clipboard
Change log 0.7.4.0
Changed the SdkInstallDialog to use a WebRequest instead of the WebClient. Hopefully this will help some peoples issues...
Window settings are now saved and reloaded.
Remembers the folder view state (large icon, details, etc)
added --color=never to directory listing command. this should fix the issue people with Heros are having
moved the options dialog tree config to its own file, as it really isnt configured by the user.
added batch installer plugin (alpha) that can install/uninstall multiple apk's at one time.
added logging info for droid explorer. (saved in %USERAPPDATA%\DroidExplorer\logs)
it should also handle "unhandled" errors better
wired up Tools menu items
Added property to indicate if a plugin can be ran by the Runner
Jumplist items added for runnable plugins
Change log 0.7.3.0
app.manifest added to projects. requestedExecutionLevel = requireAdministrator. This means in Vista/Win7 it will prompt w/ UAC. I can not get around this at this time.
this is because in order for the service to use the same settings as the application, i need to save them in the install directory.
The sdk tools, if downloaded, is no longer stored in the user directory, it is stored in the install directory, see above for the reason.
Known devices moved back to HKLM for the same reasons above.
New Options form added.
Device manager now part of options dialog
plugins can now reside in any directory as long as it is added to the plugins settings
plugins can now be enabled or disabled from the options dialog
Service is now working because of the requireAdministrator change.
DroidExplorer.Runner added - a tool that can execute a plugin; usage: DroidExplorer.Runner.exe /type=Full.Plugin.Class.Name,Plugin.Assembly.Nam/any /additional /args
if the type argument is not specified, then it will display a plugin selection dialog.
Installer plugin. This is launched by the runner when an APK file is opened in Explorer.
Registry settings to register .apk files to open with DroidExplorer.Runner /Installer (create with MSI installer)
.apk files can be installed by double clicking them or by right clicking and selecting "Install"
.apk files can be uninstalled by right clicking and selecting "Uninstall"
the initial device selection dialog is only required if more then 1 device is connected.
If you have set up to use the SDK tools by downloading the tools and put them in your user application data directory, when launched, it will prompt you to re-setup the tools. They are not stored in the user directory because the Service can not access that directory.
Just realized the bug with the device name not showing in the titlebar/addressbar. This is already fixed and will be in the next release.
Future Features you will see in Droid Explorer
Complete integration with the Managed Android Debug Bridge. R
Root will not be needed, at least for copy file operations. Things like flashing recovery, and deleting from /system will still require root.
Busybox dependency will be dropped.
SQLite Database Manager to replace the feature lacking plugin that exists now.
Faster navigation when changing directories
What features do you want to see?

[APP|2010-07-31] ANDROID BOOTCAMP v1.1 - NOT just another Android-loader... :D

A few weeks ago when the Android-on-HD2-hype started i made this small app. This piece of software was inspired by GenYDualboot (author: YOZGATG) so some credit should go to him...
To make it clear: I wrote this software by myself (basic4ppc) from the scratch so no code or other intellectual property has been stealed.
ANDROID BOOTCAMP v1.1
System Requirements:
* WVGA (VGA/QVGA not supported!)
* WinMob 6.5.X (not tested on WinMob 6.5)
* min. NETCF 2.0
* a SD-card containing working Android-build
Basic Functionality:
* WinMob based Android loader
* possible to "boot" ANDROID or to stay in Windows
* possible to "autoboot" with countdown (10sec)
* possible to choose if CLRCAD.EXE is loaded prior to HARET.EXE or not
* Autodetection of HARET.EXE and CLRCAD.exe on the SD-Card (checks if files are present in root or "\Android")
* possible to modify the path to your Android-build by changing the path in the registry
* possible to boot at systemstart (the app puts itself to "launch52" in the registry)
* possible to save your settings
* fully functional on non-WWE-Roms (checks the registry for the name of your sd-card)
* full multi-language-support (by editing the "language.ini"; at this time only german an english are buildin)
* full landscape/rotation support
* fully skinable (by modifing the PNGs in the app-folder, i'm going to release a GTX based skin or some other skins if it's wanted by the community)
* new: change font color (black/white)
* new: switchable progressbar (showed during countdown)
* new: ClearAndroid! removes Android-related junk-/tempfiles and cache!
* new: TotalClean! totally ereases your Android environment (for a clean upgrade to a new build) - USE WITH CARE!
Disclaimer:
This piece of software is free and can freely be downloaded here. You are allowed to modify, cook in or distribute my work as long as you give me some credit.
YOU ARE NOT ALLOWED TO CHARGE ANY KIND OF FEE NEITHER FOR THIS SOFTWARE ALONE NOR BY INCLUDING IT OR ANY MODIFICATIONS OF IT INTO A ROM/ANDROID-BUILD OR ANY OTHER "SERVICE"!​
(see threat "STOP THE STEALING" in the Android subforum for more details...)
I'm not responsable for any kind of damage or data loss on your device. The software is provided as it is and you are going to use it on your own risk.
Credits:
* the developers here and at htc-linux.org for HARET.EXE/CLRCAD.EXE and for their amazing work!
* YOZGATG for GenYDualboot
Roadmap / future functions to come in Android Bootcamp v1.2 (if wanted by the community):
* GUI-overhaul to a nicer / modern look
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add support to select androit installation (if more than one installation present on SD)
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder) integrated into v1.1!
* add option "TOTALCLEAN" (ereasing all android related files and folders incl. thumbnails/cache/etc) integrated into v1.1!
More inf
o to come....
Feel free to make your suggestions!
FAQ / Userguide
Q: How do I install Android Bootcamp?
A: Just download the CAB attached to the firs post and install it to your device. It's recommended to put it into your phone-storage not to the sd-card.
Q: How do I boot into Android?
A: Click on the Android-button (the picture).
Q: The Android-button is greyed out and the app says "no Android!"
A: Make sure that there is a sd-card plugged into your device containing Android in the root or in the "\Android" subfolder. Also HARET.EXE/zHARET.EXE is required in the same folder to successfully boot Android. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to HARET.EXE/zHARET.EXE. If HARET not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder. If you want to modify the path to your own needs go to the registry and alter the value "Haret" in the key "HKLM\Software\Android Bootcamp".
Q: How do I make sure that CLRCAD.EXE is started prior to HARET.EXE
A: Click on the checkbox next to activate CLRCAD or select the option in the settings-menu. On program-start the app checks the registry ("HKLM\Android Bootcamp\") for a valid path to CLRCAD.EXE. If CLRCAD not found or existing the app checks the rootfolder of your sd-card and after that the "\Android" subfolder and after that it takes the CLRCAD.EXE in the Android-Bootcamp program folder. If you want to modify the path to your own needs go to the registry and alter the value "CLRCAD" in the key "HKLM\Software\Android Bootcamp".
Q: How do I stop the countdown?
A: Just tap on the countdown-message or tap on the checkbox next to "activate AutoBoot".
Q: How do i activate/deactivate AutoBoot?
A: Check or uncheck the checkbox next to "activate AutoBoot" or select the corresponding option in the settings-menu.
Q: What does "execute at Boottime" mean?
A: The App makes 2 entries to the registry ("HKLM\init\Launch52" and "HKLM\init\Depend52"). These entries make sure that Android-Bootcamp is started during the WinMob boot procedure with the saved settings as soon a possible. Please note that the boot process does not stop and continues loading system processes after Bootcamp is started. I suggest also to check the "AutoBoot" option so that Android/WinMob is loaded automatically after 10sec. To disable this option uncheck the option (registy changes made immediately - no "save settings" is needed)
Q: How do I save my settings? Why are my settings not saved?
A: Your settings are not saved automatically - choose "Save settings" in the settings-menu prior to booting Android or closing the app.
Q: How do I activate the landscape support?
A: Landscape and screen-rotation is fully supported by the app itself but it's possible that you have to add the app to the rotation-whitelist. If you don't know how to do this - google for TouchTools or BSB-Tweak. With the help of these apps you can enable rotation service easily to any program.
Q: The program gives me the error-message "No Registry-values found, create them now?"!
A: Possibly you deleted one/some reg-values needed by the app. Just click to "YES" and all settings/RegKeys will be created with default values.
Q: I'm not naturally speaking english/german. How do I add my own language?
A: This can be done very easily by modifing the file "language.ini" in the Android Bootcamp - program folder. Please make sure that the first line is the name of the language and that the ini's structure isn't altered (NO SPACES between value, "=" and translation!!)
Q: How do I add my own skin?
A: Modify the PNG-files in the Android Bootcamp prgram folder to your own needs after making a backup of the orginal files (recommended). Feel free to post your files compressed to a ZIP-file here!
Q: I still don't get "execute at Boottime" to work!!
A: First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless if Bootcamp is in fore- or background. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
Q: Is it possible if you can code it so it can find CLRCAD and Haret in the "cm6-htcleo" folder for the CyanogenMod release / in some other custom folder?
A: Yes, it's already possible - open your registry with a regeditor and go to the key "HKLM\Software\Android Bootcamp". Check and edit the VALUE "Haret" and put the FULL PATH to your HARET.EXE / zHARET.EXE in there. After this modification Bootcamp should be able to find your Android-Installation. The feature of selecting a custom folder is added with the next release of Bootcamp.
NOTE: Be aware that "CleanAndroid!" and "TotalClean!" doesn't work with custom Android folders - these two options look for an Android-environment in the root of your storage card or in the "Storage Card\Android" folder respectively. So keep an eye on those two (probably dangerous) features, so that not the wrong files get lost...
SKINS
Q: How do I install a skin?
A: Download the zipped skin-file here and extract all files to the Android Bootcamp program folder overwriting the orginal files.
Q: How do I add my own skin?
A: Modify the JPG/PNG-files in the Android Bootcamp program folder to your own needs after making a backup of the orginal files (recommended). Make sure that your files have the same dimensions and keep their file format! Feel free to post your files compressed to a ZIP-file - I will add them here!
NOTES:
* GTX-based skin is beta/for testing only and does not look very good - better version will be uploaded with the next program version (see text color issue above)
* Text color can't be changed a this time - going to add an option in the next version to switch between black/white fixed in v1.1
* there is some minor picture-misallignment regarding the android button. This is already fixed in the code an will be included in the upcomming update fixed in v1.1
nice work! good to see several alternatives out there for dual booting
Don't need it...
But really great job!
Pretty GUI !
beautiful my fav booting app so far,
thanks
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Best Dual boot for Android/Winmo out there at the moment.
essojay said:
hi, thanks for the nice app, but could you please include autoclean or auto delete of the "android" folder on sdcard as it tampers with rootfs when re booting.
thanks
bR
Click to expand...
Click to collapse
Please explain this issue to me because i don't have this kind of problem in my setting. Do you want to have an option to "automatically clean" the root/android folder of your sd-card after rebooting (to WinMob)? What kind files should be cleaned? I easyly could add an option to clean the "*.REC" files and the "LOST+Found" folder if this is wanted.
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
essojay said:
each time you reboot into windows and want to getback into Android, you have this complaint about rootfs not found , and the fix is to delete the "android" folder on the sdcard, this folder is auto generated. this happen each time you reboot and want to get back to android. There is a thread about this somewhere...
http://forum.xda-developers.com/showthread.php?t=736306&highlight=rootfs
bR
Click to expand...
Click to collapse
Hmm, I looked at the given threat and this issue seems strange to me. I never had this kind of problem and this could be BECAUSE my Android-installation resides in the folder "SD-CARD\ANDROID". Darkstone and Dani recommend to put their builds (Froyo) into the Android subfolder and not directly to the root-folder of the sd-card.
Adding a option to clear or to delete the android folder seems not acceptible to me because - like I said - many people including myself have their Android installation in this specific folder and consecutively would destroy their Android environment.
But i'm considering to add a TOTALCLEAN-feature so the user can easily prepare the sd-card for a new android build by ereasing his android installation and all corresponding files and folders (thumbnails, cache, etc.) without the need of formatting the sd-card.
Epic
Very nice GUI! I will be giving this a try. Seems like a good time to experiment with some different flavors of Android...Weekend Project! w00t!
Yes Ironheart...am going to try the sdcard/android way and let you know.. just read somewhere about everything in the android folder.. thanks.. will let you know
bR
really nice man, i will jump ship to your loader
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Zell Dinch said:
Sorry, i checked "Boot at bootime" option but the program is not run automatically on startup
Click to expand...
Click to collapse
First be aware of the fact that the "execute at Boottime"-option puts the Android Bootcamp app into the row of the startup processes (look at the regkey "HKLM\init\" for all processes loaded automatically at systemstart!). Also note that by loading Bootcamp the startup-process doesn't stop. That means the system starts Bootcamp and continues loading the remaining systemprocesses afterwards and probably puts Android into the background without the ability to bring it to foreground again (it's not listed in some task-managers). So it's recommended that not only " "execute at Boottime" but also "AutoBoot" is selected. These options enable Bootcamp to load at startup and to boot either into WinMob or Android (depends on your settings saved) and EXIT after the countdown gone to zero.
Here is a detailed guide:
1. make sure that a sd-card containing a functional android build is plugged into your hd2 (Android AND HARET present!)
2. start Android Bootcamp
3. select "Autoboot"
4. select Android as Autoboot-OS (tap the radiobutton below the androidbutton or select the corresponding option in the settingsmenu)
5. select "execute at boottime"
6. save your settings
When the system starts Android Bootcamp is loaded. If an Android-SD-Card is present Android will boot after 10 sec regardless whether Bootcamp is in foreground or or not. If no Android-SD-Card is plugged in, WinMob is selected automatically, System will boot after 10 sec and Bootcamp quits.
This should work for you.
If you still encounter problems check your registry after you checked the "execute at boottime" option. 2 new values should be in the RegKey "HKLM\init": "Launch52" and "Depend52" - If they are not present something went wrong. You can also try to change the valueNAMES from "Launch52" to "Launch62" and "Depend52" to "Depend62" respectively.
my contribution to the theming
ironheart said:
Future functions to come in Android Bootcamp v1.1 (if wanted by the community):
* add possibility to directly downloading latest zImage from the git or from cotulla's build to your Android-installation-folder
* add support to change background directly within the app
* add support for skin-changing directly within the app
* add support for checking for newer program versions
* add possibility to "clean" SD-Card when rebooting to WinMobile (deletion of REC-files and the "Lost+Found" folder)
* add option "TOTALCLEAN" (easy preparation of your SD-Card without formatting by ereasing all android related files and folders incl. thumbnails/cache/etc)
* add support to select androit installation (if more than one installation present on SD)
Click to expand...
Click to collapse
+1 Want have
[/QUOTE]
voiceofid said:
my contribution to the theming
Click to expand...
Click to collapse
Nicely done! going to put your skin to post#3...
Thank you!
EDIT:
I testet your theme and i had to lightly modify it to keep text-readability (blur filter, less light, htc-logo removed)... i hope you are ok with my modifications. Still good job done (added to skins)
HD2_Noob said:
+1 Want have
Click to expand...
Click to collapse
Some of the new features are already working in my beta-build und are going to be released to public soon (ETA for final 1.1-release maybe 1-2 days)...
Stay updated!

[APP] AFV File Verifier for Android™

Introducing the AFV File Verifier for Android™ app, now available (free) in the Market (search for "AFV"; QR code and screenshots are also below in the attached thumbnails).
The AFV File Verifier for Android™ application is a tool for helping to verify and validate that files transferred to your Android device are whole and uncorrupted.
Developers are welcome and encouraged to include this app in their custom ROMs to assist end-users with checking the completeness and validation of their (your ) downloaded custom ROMs.
The AFV File Verifier for Android™ app does this by offering:
- MD5, SHA-1, SHA-224, SHA-256, SHA-384, SHA-512 checksum calculation
- "jarsigner -verify"-type validation of signed jar-type files (.jar, .apk, .zip files)
- Nandroid backup directory verification via "md5sum -c"-type functionality
These functions are particularly useful for root users who want to verify/validate that their custom ROMs, themes, and installable .zip files are whole and uncorrupted. However, this app does not require that you be rooted and can also be useful for checking the validity of other non-root files such as application .apk files.
Features
- Includes function to calculate an MD5 or SHA1 checksum for a selected file
* Useful to verify completeness and integrity of files transferred to your Android device
* File size is also displayed
* Calculated checksum is copied to clipboard
- Includes function to perform jar file verification of signed jar-type files (true .jar files, .apk files, signed .zip files such as ROMs, installable .zips, etc.) via 'jarsigner -verify'-type functionality. This function will verify the SHA1 checksums of each file listed in the signed jar file's META-INF/MANIFEST.MF file.
- Includes function to verify Nandroid backup directories via "md5sum -c" type functionality. You navigate to the Nandroid backup directory that you'd like to check, long-press the nandroid.md5 file, and select the Verify Nandroid Backup option. The function will then calculate and verify the MD5 checksums of each file listed in the nandroid.md5 file against the files in the Nandroid backup directory. Additionally, I've added some special name audits for Nandroid backup directories to point-out any issues you might encounter should you attempt to restore a mis-named Nandroid backup.
How to use
- From main / home screen, press the "Select File" button to enter the file-selector
- Top row (folder icon with the green up arrow) always displays the currently selected directory (touch this row to navigate UP one directory level)
- Back key can also be used to navigate UP one directory level (will return to main screen when pressing back key at root directory)
- Navigate to other subdirectories by touching a directory row (folder icon)
- Touch screen and drag up and down to scroll through all files and directories in currently selected directory
- Long-press on a file to view the available functions:
* Calc MD5 Checksum
* Calc SHA1 Checksum
* Verify Jar-type file
* Verify Nandroid Backup (long-press nandroid.md5 file to use this function)
* Calc SHA224 Checksum
* Calc SHA256 Checksum
* Calc SHA384 Checksum
* Calc SHA512 Checksum
Miscellaneous
Works for any Android version 1.5 or higher; has been tested on:
* Motorola Droid X (v2.1, v2.2)
* Motorola Cliq (v1.5)
* HTC Droid Eris (v2.1)
* Samsung Epic 4G (v2.1)
Menu items supported (main screen only):
* Help
* Acknowledgements
* Change Log
* Filtering options (no filtering or show only zip/jar/apk/img-type files)
* Jar Verify options (normal / fast mode or beta / explicit SHA1 calculation mode)
* Current settings
* Exit App
More app details (additional screenshots, etc.) can be found here: https://sites.google.com/site/scaryalienware
Acknowledgements
- jcase at XDA for allowing me to view an example project co-authored w/eclips3 and for the starter MD5 Java code
- XDA's bftb0 (Android Forums' erisuser1) for his encouragement, review, feedback and suggestions for helping me improve this app
- AF and XDA doogald for his very helpful reviews, feedback, and continued support
- Robert W. Harder for his Base64 encoding/decoding classes (http://iharder.sourceforge.net/current/index.html)
Related threads:
- Verify your File's MD5 Checksums!
- On-phone ROM Checksum Verifier
- Devs - Please publish you MD5's - XDA
Please check out the app and let me know if you have any problems, questions, or comments. Cheers!
Change Log
[version 2.3 - 11-Jan-2014]:
- fix issue w/verifying TWRP Nandroid backups [thanks to Marc M. for the kind heads-up re. this]
[version 2.2 - 09-Nov-2013]:
- fix force-close (FC) issues for some devices (Google added new external storage read permission requirement in 4.1 and higher)
[apologies for the delay in fixing]
[version 2.1 - 24-Feb-2013]:
- support auto-verification of MD5 checksum in *.tar.md5 files (thanks for Mike D. for this excellent suggestion)
- better recognize .md5 file entries formatted by other md5sum utilities (i.e., other than busybox md5sum applet)
[version 2.0 - 18-Jul-2012]:
- support Nandroid backup verification for Team Win Recovery Project (TWRP) custom recoveries
- moved two checksum comparison options to the main screen from the menu
- several other minor tweaks and enhancements
[version 1.9 - 26-Jun-2012]:
- minor update to fix crash when non-.md5 file is selected for a Nandroid verification
[version 1.9 - 23-Jun-2012 Android 2.3 and up]:
- support .md5 files w/spaces in file names in 'Verify Nandroid Backup' and 'md5sum -c Type Check' functions
[version 1.8 - 21-Jan-2012 Android 2.3 and up]:
- better display support for tablets and other phone screen densities
- can now also invoke Verify Nandroid Backup function by long-pressing Nandroid backup directory name
- support orientation changes (previous orientation locks have been removed)
- display full information in landscape mode just is done in portrait mode
[version 1.7 - 12-May-2011]:
- display file size after file name in file selector (with menu option to disable)
- add 'Return to Main' menu option in file selector (so you don't have to hit back key)
- tighten-up Nandroid-verification function so that non-'nandroid.md5' files do not cause FCs [note/reminder: the 'Nandroid Verify' function is done against the nandroid.md5 file in your Nandroid backup's directory]
- revise/enhance results pop-up display for the Nandroid Verify function
[version 1.6 - 02-May-2011]:
- thanks to all who have donated or purchased the donate version (very much appreciated!)
- fix FC issue when null/empty URI is received via Send function (please contact me if you experience an FC or other issue)
- several other minor fixes
- dynamically identify external storage directory instead of hardcoding /sdcard
- make pop-up dialogs cancelable via back button
[version 1.5 - 11-Apr-2011]:
- fixed FC issue when last remembered directory is no longer present (renamed / deleted) and
app is re-launched (thanks to Michael C. for bringing this to my attention)
[version 1.4 - 7-Apr-2011]:
- display elapsed time for long-running operations
- allow app to be invoked from other applications (tested with Astro File Manager, Estrongs File Explorer, OI File Manager)
- added donate button (donate version of app will be published soon)
- added 'md5sum -c Type Check' function for .md5 files (equivalent to 'Verify Nandroid Backup') to make it clear that functionality exists for non-Nandroid .md5 files too
[version 1.3 - 2-Feb-2011]:
- now supports SHA-224, SHA-256, SHA-384, and SHA-512 digest/checksum calculation
- display checksum results in a pop-up to ensure viewing checksum results on all phones
- keep screen on while progress-bar is displayed in long-running calculations
- directory name is now remembered from last file selection
- added help menu function for file selection screen
[version 1.2 - 23-Jan-2011]:
- supported standard preferences / settings menu instead of individual menu items
- added SD card mounted check before allowing file selection
- added two methods for comparing MD5 or SHA1 checksums:
* auto-comparison of calculated checksums w/menu option to display comparison results
* manual input of checksum (or paste from clipboard) value to be compared w/next calculated checksum
- changed default sort order of file / directory names to ignore case
- added option to toggle ignoring of case when sorting file / directory names
- force all screens to portrait orientation to fix/prevent FCs (future version will handle orientation changes correctly)
[version 1.1 - 10-Nov-2010]:
- re-instituted checksum clipboard copy lost due to prior UI revamp
- locked orientation of main screen to portrait so checksum results are displayed on all phones (both issues kindly reported by AF's starflorida)
[version 1.0 - 25-Oct-2010]:
- initial Android Market release
nice work....
pls post apk files here thx man
Wonderful dude... this helps a lot for frequent "flashers"
androgiallo said:
nice work....
pls post apk files here thx man
Click to expand...
Click to collapse
androgiallo, you are very welcome! I've got some minor tweaks that I'm working on, so I'm hoping to keep using the Market's ability to let people know about updates (it got a little cumbersome w/publishing the older versions of the app in different threads, etc., lol).
Neo.Collin said:
Wonderful dude... this helps a lot for frequent "flashers"
Click to expand...
Click to collapse
Neo.Collin, thank you for the kinds words and feedback--I very much appreciate it. I know there's a lot of frequent flashers D) out that should be checking their downloaded ROMs and such...peace of mind, you know?
Please let me know if you have any suggestions and/or ideas for future improvements. Thanks!
v1.2 just uploaded to the Market
All,
Been awhile since I've updated this app and it was long overdue. Mostly minor fixes and updates. No real core functions changed other than upgrade the early (noobie-coded ) menu settings to the more professional and standard preferences and settings menu.
I've also made some changes that should eliminate any FCs you were getting (most related to orientation changes, I believe). I'll get the orientation handling properly done in a future version.
If you get any FCs, please email me at [email protected] and let me know the circumstances so I can make a fix (the crash reports don't often tell the whole story).
Here's the change log for v1.2:
version 1.2 - 23-Jan-2011:
- supported standard preferences / settings menu instead of individual menu items
- added SD card mounted check before allowing file selection
- added two methods for comparing MD5 or SHA1 checksums:
* auto-comparison of calculated checksums w/menu option to display comparison results
* manual input of checksum (or paste from clipboard) value to be compared w/next calculated checksum
- changed default sort order of file / directory names to ignore case
- added option to toggle ignoring of case when sorting file / directory names
- force all screens to portrait orientation to fix/prevent FCs (future version will handle orientation changes correctly)
Thanks again for using my app and for your support. As always, email me or post-up here for any comments, questions, issues, or suggestions.
Cheers!
Hey, great app. Not sure if I missed this feature, but it would be cool to copy paste a md5 before your app verifies the selected file, and simply says if it matches or not
titans808 said:
Hey, great app. Not sure if I missed this feature, but it would be cool to copy paste a md5 before your app verifies the selected file, and simply says if it matches or not
Click to expand...
Click to collapse
You are most welcome, thank you for the comments.
As a matter of fact, you can do this in this (new v1.2) version:
1. Press menu key
2. Select Preferences / Settings
3. Select Input Checksum (in the MD5 / SHA1 Comparison middle section)
4. Type (lol) or (more likely ) paste the checksum to be compared
5. Press back key to return to the main screen
6. Select your file and long-press the filename and select the appropriate checksum operation
7. After the checksum is computed, you'll get a pop-up indicating the status of the comparison of the newly-calculated checksum with the one you inputted in the menu
You can also check the Display Comparison Info checkbox to have the app display a pop-up message regarding the checksum comparison of the last two MD5 or SHA1 checksum comparisons that you perform. This would be helpful for checking two file successively.
Cheers and thanks again!
No, thank you, you did a great job of making a multifunctional app. Job well done
Sent from my ADR6300 using XDA App
v1.3 just published to the Market
All,
Just released version 1.3 to the Market. Nothing major--just some more things on the to-do list that I finally figured-out how to do.
version 1.3 - 2-Feb-2011:
- now supports SHA-224, SHA-256, SHA-384, and SHA-512 digest/checksum algorithms (along with the MD5 and SHA1 algorithms, these appear to be all functions that the MessageDigest API supports)
- will now also display checksum results in a pop-up to ensure viewing checksum results on all phones
- keep screen on while progress-bar is displayed in long-running calculations
- directory name is now remembered from last file selection
- added help menu function for file selection screen
Thanks and hope these changes are useful.
Cheers!
v1.4 of AFV (Android File Verifier) just uploaded
All,
I just uploaded my newest version of AFV to the Android Market.
Been working on this one for a while (sorry it took so long ).
Thanks again to bftb0 for suggesting the "launch / send" from other apps idea .
Hope you enjoy it!
Here's the change log:
version 1.4 - 7-Apr-2011:
- display elapsed time for long-running operations
- allow app to be invoked from other applications (tested with Astro File Manager, Estrongs File Explorer, OI File Manager); use the "Send" function
- added donate button (donate version of app will be published soon)
- added 'md5sum -c Type Check' function for .md5 files (equivalent to 'Verify Nandroid Backup') to make it clear that functionality exists for non-Nandroid
.md5 files too
AFV (Android File Verifier) v1.6 just published to the Market.
Change logs for v1.6 and v1.5:
[version 1.6 - 02-May-2011]:
- thanks to all who have donated or purchased the donate version (very much appreciated!)
- fix FC issue when null/empty URI is received via Send function (please contact me if you experience an FC or other issue)
- several other minor fixes
- dynamically identify external storage directory instead of hardcoding /sdcard
- make pop-up dialogs cancelable via back button
[version 1.5 - 11-Apr-2011]:
- fixed FC issue when last remembered directory is no longer present (renamed / deleted) and app is re-launched (thanks to Michael C. for bringing this to my attention)
Cool App
@scary alien : Cool app
Given you an award here
http://www.techofweb.com/google/verifying-android-files.html
techofweb said:
@scary alien : Cool app
Given you an award here
http://www.techofweb.com/google/verifying-android-files.html
Click to expand...
Click to collapse
Thank you very much!
I do very much appreciate the very nice article and your kind words.
Cheers!
version 1.7 just published
Change log (hope you enjoy!):
[version 1.7 - 12-May-2011]:
- display file size after file name in file selector (with menu option to disable)
- add 'Return to Main' menu option in file selector (so you don't have to hit back key)
- tighten-up Nandroid-verification function so that non-'nandroid.md5' files do not cause FCs [ note/reminder: the 'Nandroid Verify' function is done against the nandroid.md5 file in your Nandroid backup's directory
- revise/enhance results pop-up display for the Nandroid Verify function
Can I just say that I love your app, but I was a little disappointed that you don't post your apk anywhere. I was trying to help a user troubleshoot an issue on the CyanogenMod forums with not being able to get the Play Store installed, by verifying the md5sum of his ROM and gapps zips. I wanted to just send him to this thread to download the apk so he could manually install it, but it is nowhere to be found (including your google site page). Would you consider adding it as an attachment to this thread for those times that people can't get on the Play Store and need to use the app?
bassmadrigal said:
Can I just say that I love your app, but I was a little disappointed that you don't post your apk anywhere. I was trying to help a user troubleshoot an issue on the CyanogenMod forums with not being able to get the Play Store installed, by verifying the md5sum of his ROM and gapps zips. I wanted to just send him to this thread to download the apk so he could manually install it, but it is nowhere to be found (including your google site page). Would you consider adding it as an attachment to this thread for those times that people can't get on the Play Store and need to use the app?
Click to expand...
Click to collapse
Excellent suggestion, bassmadrigal and thank you for the kind words .
I've updated the OP with the v2.0b version that's currently available on the Play Market.
I'm actually up late working on a tweak to the app that will support the auto-verification of MD5 checksums in .tar.md5 files from a I request I received Wednesday. I hope to have this new version posted (and the OP updated) in a few days.
I'll also upload the Legacy version of the .apk here in a few minutes for those on older versions of Android.
Cheers and thank you again!
-SA
Version 2.1 just released
Just updated Play Store (and OP of this thread) with new v2.1 version.
Enjoy!
Thanks,
-SA
Change log:
[version 2.1 - 24-Feb-2013]:
- support auto-verification of MD5 checksum in *.tar.md5 files (thanks for Mike D. for this excellent suggestion)
- better recognize .md5 file entries formatted by other md5sum utilities (i.e., other than busybox md5sum applet)
I would really like to see a push for the sha-2 algorithm instead of md5 since its is subject to attack and they have found to create two files with same checksum ( https://en.wikipedia.org/wiki/MD5 ).
I am uncertain as to why the push for sha-2 checksum in the android community has not been taken up, instead of we rely on an 18 yr old algorithm that is subject to attack.
I think the main gist of publishing a MD5 and SHA1 digests for a file is not strictly for security or secrecy reasons but rather as one means of providing a way to help verify / validate the integrity of a downloaded file.
Certainly using a less vulnerable, stronger, more robust checksum is always desirable, MD5 and SHA1 sums are probably here to stay for a while (although I must admit to remembering the widespread use of CRC-16 and -32 in the not-too-distance past (well in the '80's anyways )).
Also, being aware of the file's known / expected size and the download source's author is helpful in vetting it's pedigree and authenticity.
Caveat emptor, etc. .
Great app...

[29 Oct 2012]v1.09 Remove Bloatware,Lite-ROM Creator-Windows Base Script Generator

v1.09 Should be final version ,at lease I have no idea what should I add right now.
Update from old version : copy userapp.dbf and userapp.cdx inside old one to new one. That's it
Update note aviliable at the bottom of this post
-------------------------------------------
[7 Nov 2012]
Upload new database
-------------------------------------------
Why Literom Creator ?
No recovery in need ,just Root ,everything fine
Easy to restore app
Define your own db with windows GUI interface
Switch between Phone with some clicks ,right now support N7000 and N7100
You can even make a new list yourself and share to your friend .Work on EVERY phones with ICS that have root.(For GB rom ,file script-begin must change something
Total free ,of coz you can buy me a beer
Download link : See attachment
[Inside package ,there is two EXE file
literom-creator.exe : Main Program
DBEdit.exe : Use this if you want to edit entry yourself]
DBEdit Readme aviliable here
Remark since v1.03
How can I switch database ?
1. Open dbEdit.exe
2. Inside dbEdit ,click Restore ,choose database that you want
3. Done
How can I make a lite-rom script quickly with new function : Combine App List?*
1. Open dbEdit.exe
2. Copy all apk files ,inside /system/app/ ,to folder [Place_System_App_Here]
3. Inside dbEdit ,click Restore ,choose file [FULL DB include everything] **You may want to backup the db you are using right now.
4. Click [Combine App List]
5. Done . Now you have a database that match your rom.
-------------- Readme of main program --------------
Before I wrote a windows base program that can create your own lite-rom script for N7000.
Now it's aviliable at Galaxy Note2
I think it should simple enough to use it yourself
{
"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"
}
Double click on any item that you want to remove
Filter : ALL mean list all / Remove mean list all you have choose to remove / Include mean that will keep in your rom
After select all you want to remove ,click [Export Lite-ROM Script] ,then you will get a file called [fish-literom.TXT]
Place [fish-literom.TXT] in your SDCard .
Now ,move to your phone ,download Script Manager from Market .
https://play.google.com/store/apps/details?id=os.tools.scriptmanager
You MUST browse as ROOT like this.
Browse to fish-literom.TXT ,choose Su
After that ,click Run.
After delete files ,it should have some force close .Ignore it .
Then ,restart your phone .
Finished .Now you may uninstall Script manager as well .
- Remark : File backup to folder /sdcard/fishliterom .If you want to restore ,simple copy file to /system/app ,set premission rw- r-- r-- ,reboot
- I search though XDA ,all the files listed should safe to remove ,if I make any mistake ,please tell me
- Hit Thanks if you like this
Release note.
- Add a pre-define db : Full DB include everything.txt ,you can use this to generate your script quickly.
dbEdit.exe v1.03 / Oct 29 2012
- Inside [Manage DB] ,add new function : Combine App List
After you put apk into folder [Place_System_App_Here]
It will compare folder items to database ,remove non-exist apk,add new apks ,keep item with same APK name .
So you can build a new lite-rom database quickly
- Double click on grid item ,it will copy apk name to clipboard ,and use default browser search XDA
- Add button : Clear Item - info2 ,
this will remove all item description in description 2
- Add button : Generate APK List ,
this will generate apk list into a text file call 'apk.txt'
Lite-Rom creator.exe v1.09 / Oct 29 2012
- Add multi lanaugae support .
You can place a file called [lauguage.txt] to default folder .
Then literom creator will read item layout from that .
If there is no language.txt inside ,program will show default language (English)
- Add Export Restore Script
Run this and restore all deleted file to system .
DBEdit v1.02 released Oct 27 2012
Thank Crushader for the idea .
Now it's much easy to create your own app list .Even switch between phones.
v1.08 Oct 26 2012
Change icon
Layout change
applist.dbf add remote control / change minimode-res.apk details.
Now you can edit the output script by
- Using Editplus (or sth like that) - open
script-begin : Inside this ,you can mount system ,set backup path ,and etc
script-main : main script to delete bloatware .Don't change keyword : #ThisIsApkToRemove that will replace with apk name when output
This two file MUST save as UNIX format
DB Reference : Search in XDA / http://goo.gl/8QSVX
v1.07 Oct 24 2012
Change DB from N7000 to N7100
goddamnit said:
Download link : http://goo.gl/l1GsE
- Remark : File backup to folder /sdcard/fishliterom .If you want to restore ,simple copy file to /system/app ,set premission rw- r-- r-- ,reboot
- I search though XDA ,all the files listed should safe to remove ,if I make any mistake ,please tell me
- Hit Thanks if you like this
Click to expand...
Click to collapse
minimode-res.apk : I found what is it now .
It's for mini popup browser .
Will change db details next time
v1.08 Oct 26 2012
Change icon
Layout change
applist.dbf add remote control / change minimode-res.apk details.
Now you can edit the output script by
- Using Editplus (or sth like that) - open
script-begin : Inside this ,you can mount system ,set backup path ,and etc
script-main : main script to delete bloatware .Don't change keyword : #ThisIsApkToRemove that will replace with apk name when output
This two file MUST save as UNIX format
great
will test it tnt
I checked your script, doesnt do anything to the libs, maybe u can improve on your script by adding or removing un-needed libraries also.
thanks.
nishbul said:
I checked your script, doesnt do anything to the libs, maybe u can improve on your script by adding or removing un-needed libraries also.
thanks.
Click to expand...
Click to collapse
Hi nishbul.
I have think about this too .
But ,if I remove the lib also ,user will hard to restore the apps.
And ,mainly ,this script is to stop that auto-load apps .
Maybe I will add delete libraries too if I let literom creator gen. restore script .
Anyway ,thanks for comment :laugh:
Regards,
Great tool! But would it possible to have an option to load the ROM into the tool and select list of bloatware you want to remove and export the script?
Crushader said:
Great tool! But would it possible to have an option to load the ROM into the tool and select list of bloatware you want to remove and export the script?
Click to expand...
Click to collapse
Hi Crushader,
It's easy to generate file list from ROM file.
But it's not easy to let literom creator think about which is bloatware.
Hmm.. maybe I will add import function then.Seem useful
Regards
Sent from my GT-N7100 using xda app-developers app
goddamnit said:
Hi Crushader,
It's easy to generate file list from ROM file.
But it's not easy to let literom creator think about which is bloatware.
Hmm.. maybe I will add import function then.Seem useful
Regards
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Cool, looking forward to that update =]!!!
Crushader said:
Cool, looking forward to that update =]!!!
Click to expand...
Click to collapse
I doubt if I should add function that read default db from internet.
So we can switch db ,like n7000-> n7100 more easy.
Or simple create a txt file to store db ,so can import / export.from txt ?
Or ...both of them ? lol
Because this script should work on ALL android system 4.0+ (2.3 too ,but need to modify script-begin)
Maybe there is Moto db ,HTC db and etc.. later
Sent from my GT-N7100 using xda app-developers app
goddamnit said:
I doubt if I should add function that read default db from internet.
So we can switch db ,like n7000-> n7100 more easy.
Or simple create a txt file to store db ,so can import / export.from txt ?
Or ...both of them ? lol
Because this script should work on ALL android system 4.0+ (2.3 too ,but need to modify script-begin)
Maybe there is Moto db ,HTC db and etc.. later
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Hmm I see, either way its a great tool =]
New version of DBEdit aviliable here :
http://forum.xda-developers.com/attachment.php?attachmentid=1435054&d=1351348939
Simple unzip ,place new file to folder Lite-ROM Creator
------------------------------------------------------------------------------------
I think this main screen is simply enough to use .
If you cannot understand what it do .Please skip this post
This version of DBEdit ,added a new function Manage DB
Now you can :
Backup your DB List
Import List
Restore to default list
Clear Database
and ,create your own list
---------------------------------------------
Backup : After you click this button ,current database with backup to a textfile with timestamp ,then open the directory location .You can feel free to change the file name you want.
Import : Read a text file ,all NEW entry will add into database .Old db will remain unchange
Restore : Read a text file ,old db will be delete ! And save all item aviliable inside text file . You can use this to switch between phones ,like from N7000 -> N7100 ,and vice versa .
Clear : All db will delete !
---------------------------------------------
Follow is test function ,read a list of apk and generate a new db.
it should work fine on EVERY Android Phones with ICS .
(Note : For GB rom ,you will need to modify file [script-begin] ,line4 ,then it will work fine .Message me if you need it)
First ,you must have a system dump (or something like that)
Method 1 ,Get from your phone : Great tutor here : http://forum.xda-developers.com/showpost.php?p=7204732&postcount=1
Method 2 ,download system dump files from XDA or somewhere else .I think you can download the system dump file before you get your new phone .
Method 3 ,download a CWM flashable ROM
After that ,
open the zip (RAR maybe) file
Inside the file ,there is a folder [system] ,open it
Inside [system] ,open folder[app]
Copy all files ,to folder [Place_System_App_Here] which is aviliable @ Lite-ROM creator folder
You can go back to Lite-ROM Creator now
Now ,click button Clear (depends)
click Generate App List in Lite-ROM Creator.
You will get a list like this .
Then start to create your own db.
If you want to know if the apk safe to remove . You can double click grid item ,
A search link to XDA will be opened with your stock browser .
If you created a new db .Please tell me so I can put it into db_list
---------------------------------------------------
Remark since v1.03
How can I switch database ?
1. Open dbEdit.exe
2. Inside dbEdit ,click Restore ,choose database that you want
3. Done
How can I make a lite-rom script quickly with new function : Combine App List?
1. Open dbEdit.exe
2. Copy all apk files ,inside /system/app/ ,to folder [Place_System_App_Here]
3. Inside dbEdit ,click Restore ,choose file [FULL DB include everything] **You may want to backup the db you are using right now.
4. Click [Combine App List]
5. Done . Now you have a database that match your rom.
Remove Bloatware in Sprint Galaxy Note2
Just download Sprint Galaxy Note2 system dump from here
http://forum.xda-developers.com/showthread.php?t=1875773
and make a /system/apk list of that .
You can set db to Sprint Galaxy Note2 by dbedit.exe ,using restore function .
Database file can found in OP .
Item with no details that I cannot comfirm if it's safe to remove .
I do not own a Sprint Galaxy Note2 :laugh:
--------------------
Right now target on T889 and Veizon
Release note.
- Add a pre-define db : Full DB include everything.txt ,you can use this to generate your script quickly.
dbEdit.exe v1.03 / Oct 29 2012
- Inside [Manage DB] ,add new function : Combine App List
After you put apk into folder [Place_System_App_Here]
It will compare folder items to database ,remove non-exist apk,add new apks ,keep item with same APK name .
So you can build a new lite-rom database quickly
- Double click on grid item ,it will copy apk name to clipboard ,and use default browser search XDA
- Add button : Clear Item - info2 ,
this will remove all item description in description 2
- Add button : Generate APK List ,
this will generate apk list into a text file call 'apk.txt'
Lite-Rom creator.exe v1.09 / Oct 29 2012
- Add multi lanaugae support .
You can place a file called [lauguage.txt] to default folder .
Then literom creator will read item layout from that .
If there is no language.txt inside ,program will show default language (English)
- Add Export Restore Script
Run this and restore all deleted file to system .
-------------------------------------------
[7 Nov 2012]
Upload new database
-------------------------------------------
Hi,
Not working on my standard 7100.
BusyBox 1.202 and SManager 2.6.0.2 installed. Stock rom and kernel XXDLL4, JB 4.1.2, root with CF-autoroot from Chainfire.
The script start, mkdir command ok then go to finished, I retry twice, second time mkdir logically failed and same, other commands did not apply (see attachment).
Anyway thanks for your work.
Pax_fr said:
Hi,
Not working on my standard 7100.
BusyBox 1.202 and SManager 2.6.0.2 installed. Stock rom and kernel XXDLL4, JB 4.1.2, root with CF-autoroot from Chainfire.
The script start, mkdir command ok then go to finished, I retry twice, second time mkdir logically failed and same, other commands did not apply (see attachment).
Anyway thanks for your work.
Click to expand...
Click to collapse
Please import full db using dbedit.exe,then try again.
I doubt if you are using the.right one
Sent by N7100

[IDE] ROMS][Windows] Poison Kitchen IDE [Dev Preview 2][2.3-8.1]

Poison Kitchen IDE
Development preview
{
"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"
}
​
Description
A powerful IDE for android ROM development
Runs native on WINDOWS, MacOS themed.
Its powered by my XanderUI class library for the .net framework
Currently Development preview builds are only available, meaning things may be broken, behave incorrectly or other
Click to expand...
Click to collapse
Features
-Full GUI coded in C# for fast runtime
-XanderUI based controls(My C# class library)
-Based on .net 4.5
-Support for every single android version
-Unpack rom from (.zip, .tar, .md5, .img, aml_upgrade_package)
-Pull all required files from device(root needed to copy kernel block)
-Adb, fastboot and drivers installater
-ROM information
-Explorer
-Deodexing(4.4.4 and lower ATM)
-Unpacking the kernel
-Converting file_contexts.bin to standard text
-Kernel explorer
-Repacking kernel
-Logging
-Auto-generating updater-script
-Use generic symlinks if files detected
-Use generic file contets if the kernel does not contain file_contexts
-/data/app auto transition to new rom(somewhat working)
-Wipe data excluding /data/media(/sdcard path)
-Auto kernel block detection
-Auto mounting /system and /data
-Packing rom
-Signing rom
-Updater-script editor
-Extansion support
-Emulated exension scripts(applied via C#)
-Degapps extension
-Deknox extension
-Custom emoji extension
-Enable sony apps extension
Click to expand...
Click to collapse
Features not yet implemented
-root via magisk(systemless) and superSU(standard)
-init.d
-deodexing 5.0 and up
-adbd insecure
-init.d tweaks
-build.prop tweaks
-change display I.D
-add sysrw/ro binary
-logging needs tweaking
-loading rom information updated in the background
-Unpacking RUU as project(HTC)
-Unpacking TFT as project(SONY)
-Unpacking system.dat(sparse)
-Setting your actual device as the project and apply changes in realtime
-/data/app auto transition to new rom
-Kernel may not unpack
-Convert line endings in explorer context menu
-Inbuilt file editor(with EOL auto-detection)
-Boot animation player/changer
-Auto flash rom with ORS(TWRP)
-Bluestacks as rom
Click to expand...
Click to collapse
Settings
Load settings()
-Set default startup project or startup menu
-Enable/disable logging
-Stop logger from detecting files or folders added, deleted, changed or moved
Installation settings()
-Change romname
-Change installation type(autodetect on unpack, User generated, Tool generated)
-Change file contexts method(Auto, extracted from kernel, assumed)
-Enable/disable safewipe
-Enable/disable data/app auto transition
-Enable/disable autodetect ernel blockpath(add path below)
Pack settings()
-Change compression level
-Add signing method(pack into presigned, sign on zip, none)
-Change java heapsize
-Exclude files and folders from being packed/detected by IDE
Default program settings()
Change default program to open image files
Change default program to open video files
Change default program to open audio files
Change default program to open prop files
Change default program to open archive files
Change default program to open jar/apk files
Change default program to open other type files
Current version and updates()
Cleanup settings()
Click to expand...
Click to collapse
License
GNU GPL V3
Downloads
Downloads page
XDA:DevDB Information
Poison Kitchen IDE, Tool/Utility for the Android General
Contributors
Ricky Divjakovski
Version Information
Status: Testing
Created 2018-04-19
Last Updated 2018-04-19
Creating extensions and documentation
Code:
Description -
As extensions are a great adittion to the IDE, whats the use if you cant make your own for automated building?
Information you need to know -
The tool looks for the file "extension.info".
In the extension.info file you will specify the extension name, description and the poison shell script file(.psh).
Package the folder containing the extension as a zip archive
------------------------------------------------------------------
Entension index
------------------------------------------------------------------
Sample extension -
https://github.com/Ricky310711/Poison-Kitchen-Extension-Example
extension.info -
Lines will only be read if starting with "Name", "Description" or "Run"
-------------------- code exmpla
# this sets the extension name
Name:Fake optimizer
# this sets the extension description
Description:Do not apply this to rom, its a fake extension to show an example
# this is the poison script to run(must be in same directory)
Run:FakeOpt.psh
------------------------------------------------------------------
Scripting language(.psh file)
------------------------------------------------------------------
Information
-Must be linux EOL(\n)
-Anything but recognised 1st args are ignored
-Any errors will be ignore by the shell
-Use full paths asif you are in the root(/)
Extracting content to rom
---------- code example
EXTRACT|myFolder
1st arg states we are extracting(copying) a folder to the rom
2nd arg is the folder to extract(must be in same directory as extansion)
NOTE: This will extract the folder to the root of the rom
Changing a line in a file
---------- code example
CHANGE|START|/system/build.prop|ro.product.device=|THIS IS STARTS TEST
1st arg specifies we are changing a file
2nd arg specifies where on a line to search for the string(arg4)
3rd arg specifies the file to change
4th arg specifies the string to look for
5th arg is what you would like to replace the line with
The second arg can be START, CONTAINS or END
Appending a file
---------- code example
APPEND|TOP|/system/build.prop|# A TEST FOR APPENDING TOP
1st arg specifies we are appending a file
2nd arg specifies if we are appending at the TOP or BOTTOM
3rd are is the file to append
4th arg is the content to append
Remove a line from a file
---------- code example
REMOVE|/system/build.prop|# end fota properties
1st arg states we are removing a line from a file
2nd arg specifies the file
3rd arg is the string to look for in the line
Delete a file or folder
---------- code example
DELETE|/system/preinstall
Pretty straight forward, will delete a file or folder called "preinstall" from /system/
Create a file or folder
---------- code example
CREATE|DIRECTORY|/preinstall
arg 1 states we are creating something
arg 2 specifies if a FILE or FOLDER
arg 3 is the file or folder to create
Rename a file or folder
---------- code example
RENAME|/system/bin/am|amRenamed
1st arg specifies we are renaming a file or folder
2nd arg is the file or folder
3rd arg is the new name
Changelog
Development preview 2
-Added pull rom from device in setup
-Smoother nvigation
-XanderUI 1.6.0 integration
-Message boxes are now themed like the app
-Extensions now show progress upon running
-Deodexing up to Android 4.4.4 implemented
Development preview 1
-initial release
reserved3
supports all versions of android and all devices, no manual input needed.
dev preview 3 possibly tommorow
Yay now I can at least try to build my own g6 ROMs. Nice work.
development on hold until the 30th as im on holiday, i have been dedicating little time to this as internet here is extremely slow
Magisk and SU support added aswell as deodexing 5.x > 6.0
Also working on disabling signature verification, adding sysrw(as binary)
hi, im trying out the program, it never completes the extraction, and the progress icon starts at 53% do i need to do anything when trying to start the program.
i haVE TRIed running as administartor and without running as admin.
thanks
Twisted714 said:
hi, im trying out the program, it never completes the extraction, and the progress icon starts at 53% do i need to do anything when trying to start the program.
i haVE TRIed running as administartor and without running as admin.
thanks
Click to expand...
Click to collapse
A dialog will more then likely poppup requesting permission to run imgextractor.exe, be sure to accept that to complete the process
Ricky Divjakovski said:
A dialog will more then likely poppup requesting permission to run imgextractor.exe, be sure to accept that to complete the process
Click to expand...
Click to collapse
i am attaching some pics to what happens.
please advise. thanks
there are a couple more that are insignificant
Twisted714 said:
i am attaching some pics to what happens.
please advise. thanks
there are a couple more that are insignificant
Click to expand...
Click to collapse
Could you please PM me with pics of the firmware your selecting or even a link?
I've gone ahead and tried this. I pointed the app to my system.img (not the fastboot zip) and ended up with "error extracting". Tool looks promising. ROM is available for download here:
http://en.miui.com/download-333.html
I extracted it and used the images/system.img
oreo27 said:
I've gone ahead and tried this. I pointed the app to my system.img (not the fastboot zip) and ended up with "error extracting". Tool looks promising. ROM is available for download here:
http://en.miui.com/download-333.html
I extracted it and used the images/system.img
Click to expand...
Click to collapse
Im going to test now, if the firmware has system.transfer.list, and system.dat, it will not be able to be unpacked until i make a native library or extension to perform the operation as i think it would be extremely stupid for the need to have python installed to run.
The only reason i havent rebuilt smali/baksmali etc is 1. Would take me months, 2. we are modifying a system that relies on java to operate.
in future, hefty operations like unpacking etc, will be coded in ASM/C code for faster operation, Im planning on making the whole project open source to allow changes and fixes submitted by other developers, So if anyones interested let me know and ill upload the source code(Written in C# for the .net 4.5 framework)
Ricky Divjakovski said:
Im going to test now, if the firmware has system.transfer.list, and system.dat, it will not be able to be unpacked until i make a native library or extension to perform the operation as i think it would be extremely stupid for the need to have python installed to run.
The only reason i havent rebuilt smali/baksmali etc is 1. Would take me months, 2. we are modifying a system that relies on java to operate.
in future, hefty operations like unpacking etc, will be coded in ASM/C code for faster operation, Im planning on making the whole project open source to allow changes and fixes submitted by other developers, So if anyones interested let me know and ill upload the source code(Written in C# for the .net 4.5 framework)
Click to expand...
Click to collapse
Not sure if this helps but I've run Imgextractor directly on my system.img with this result:
Code:
Mi-A1-Repository>Imgextractor Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img
ImgExtractor version 1.3.6 <Created by And_PDA (Based on sources ext4_unpacker)>
Extractor for images in EXT2\EXT3\EXT4\YAFFS2\CRAMFS filesystem formats
support SPARSE\SIN\MOTO structure formats
Open image file Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img (size 3221225472 bytes) successfull...
Analize format of file. Please wait...
Found SPARSE FORMAT
Found EXT4 FORMAT
free space in image 188895232 bytes
Extract started. Please wait...
Extract 750 folders and 6306 files successfull
Found 386 symlink files
File stats (uid, gid, permission) save to Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system__statfile.txt
Extract finish success
Press Enter to continue...
oreo27 said:
Not sure if this helps but I've run Imgextractor directly on my system.img with this result:
Code:
Mi-A1-Repository>Imgextractor Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img
ImgExtractor version 1.3.6 <Created by And_PDA (Based on sources ext4_unpacker)>
Extractor for images in EXT2\EXT3\EXT4\YAFFS2\CRAMFS filesystem formats
support SPARSE\SIN\MOTO structure formats
Open image file Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system.img (size 3221225472 bytes) successfull...
Analize format of file. Please wait...
Found SPARSE FORMAT
Found EXT4 FORMAT
free space in image 188895232 bytes
Extract started. Please wait...
Extract 750 folders and 6306 files successfull
Found 386 symlink files
File stats (uid, gid, permission) save to Mi-A1-Repository\Roms\Fastboot\tissot_images_V.9.5.10.0.ODHMIFA_8.0\images\system__statfile.txt
Extract finish success
Press Enter to continue...
Click to expand...
Click to collapse
Found the error, the img file is of a wierd format, as its named system.img, it actually contains files from the root, so within the system.img the the root of the image is actually the root of the device rather then the root of the system partition, its extremely odd but none the less extremely simple to fix
Issue is already fixed and will be included in dev preview 3, that is expected for public release in a day or so with much more additions
Ricky Divjakovski said:
Found the error, the img file is of a wierd format, as its named system.img, it actually contains files from the root, so within the system.img the the root of the image is actually the root of the device rather then the root of the system partition, its extremely odd but none the less extremely simple to fix
Issue is already fixed and will be included in dev preview 3, that is expected for public release in a day or so with much more additions
Click to expand...
Click to collapse
Yeah. I found it odd that the system.img had a /system directory in it. Awesome! Can't wait
Ricky Divjakovski said:
Could you please PM me with pics of the firmware your selecting or even a link?
Click to expand...
Click to collapse
its on mega.
https://mega.nz/#!dCA2mAYS!-GrKWuuTNODaYEbt3LWiw4LJzxkrz5wI3T94mQ4PU90
it is a android 6 to android 7 full update. its installed, but i am trying to learn cobble together a rom. this img is for a zoomtak upro, i have found today an image for the uplus/vplus. it has much more stuff in it.
thanks
Twisted714 said:
its on mega.
https://mega.nz/#!dCA2mAYS!-GrKWuuTNODaYEbt3LWiw4LJzxkrz5wI3T94mQ4PU90
it is a android 6 to android 7 full update. its installed, but i am trying to learn cobble together a rom. this img is for a zoomtak upro, i have found today an image for the uplus/vplus. it has much more stuff in it.
thanks
Click to expand...
Click to collapse
I will check it when i get home, if its an upgrade package, i cannot ad support for it..

Categories

Resources