Database Users

[Tool] adBeast - CrossPlatform ADB utiltiy (Updated 3/6/13)

Finally, a crossplatform ADB utility.
adBeast (Pronounced: Aye dee beast) is a program I'm developing in java to help automate some of the thing that ADB can do,
some of these things include:
-open web pages on your device
-pull/push files
-send key presses
-port forwarding
-reboot
-boot into recovery
-mute phone
and you'll be able to do all these much easier.
this will be open source, and I'll release the source code after the final alpha build (lots of housekeeping to do)
This is the beta release so a few things may not work all the way...
-------
Using:
Download the Base file for your OS,
Linux users get: adBeast_Base_linux.tar.gz
Windows users get: adBeast_Base_Windows.zip
Mac users:{
(I don't have a mac, so I can't make you a script, sorry)
download the linux base, and copy replace the provided 'adb' file with
your adb file, if your adb file had an extension, like .app or .dmg
then edit os.txt to match the name of your file,
then run the script from within your terminal
}
_________
Updating:
----------------
Once a new version is released,
If you have the Base files already
then all you'll have to do, is download the updated jar file,
and replace your old 'adBeast.jar' with the new one.
____________
Source code:
-------------------
If you want to be ahead of the curve,
you can get the preview version source code,
it may have minor bug fixes, or new features,
that have not been included in the release version yet!
You'll have to compile it yourself though.
https://code.google.com/p/adbeast/source/browse/#svn/src
The source code for the current release is attached to this post.

Release notes:
change log:
March-6-2013
-Push/pull/install APK no longer work (not sure why, should be fixed in the next release.)
+New option to lauch webpage on device
+New (very basic) GUI
+Option to reboot device into recovery
*Fixed port forward
+Enhanced text transfer ability
+Ability to send a string of text to device
+Quit option in GUI/Text mode
+bug fixes
+read adb's stout.
Feb-7-2013:
+source code released.
+Basic text based menu (I forgot a quit option lol)
+push files to device
+ability to reboot device
-removed the "lol lol" print
+Added cross platform ability,( linux version should work on mac, but you'll need to switch out the ADB executable)
Feb-5-2013:
+initial release (tech demo) Linux only.
+Prints "lol lol" to your device

in progress
Done:
-cross-platform (support)
-reboot device option
-basic menu
-provide source code
-push files
-user interface (text based)
-port forwording
-exit program option
Next Release:
-chose text to be sent
-pull file
-Install apk files
-make text type faster
-allow user to set text
-GUI
currently working on:
- translate adb feedback (device offline=ADB cannot connect to your phone)
-Fix adb push/pul
-get feedback from adb (failed/success)
Maybe later:
-Remote file browser, using CD/LS to read files from the device and allow the user to search through them.

Dose anyone out there have a mac?
I need some one to get me the ADB executable,
And I may need them to test some scripts.

about Ouya Toolbox 1.0

creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real

m03m1x said:
creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real
Click to expand...
Click to collapse
i Can't post in that threat but when i click on Root it says that my ouya is rooted, after install supersu and busybox it seems that i don't have root privileges.

Passing this along from the General tab for those of you with Windows 8:
m03m1x said:
creator says it doesn't work on windows 8. I can confirm the root feature and the two install features DID work for me. NO PROBLEM. Thank you! i could not post in the thread i hope maybe a mod can merge my post to that or something. (my post count wont let me post there). You just need to make sure you install the drivers with DEO (Driver Enforcement Override) after editing the Ouya lines. Then boot back to normal windows. Thanks to the creator of Ouya Tool Box im further than I was with his help than i was on my own . Creator: foil and gratitude to the other devs that also participated to make Ouya Tool Box real
Click to expand...
Click to collapse
Sent from my OUYA Console using xda app-developers app

inch oilamgD
Oscar_david said:
Passing this along from the General tab for those of you with Windows 8:
Sent from my OUYA Console using xda app-developers app
Click to expand...
Click to collapse
My root didn't work with this app on windows 7

Libleir years
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me

tonyeltriton said:
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2351782

tonyeltriton said:
i Can't post in that threat but when i click on Root it says that my ouya is rooted, after install supersu and busybox it seems that i don't have root privileges.
Click to expand...
Click to collapse
Just to confirm, do you then go into SU and BB and make sure they are activated?

dully79 said:
http://forum.xda-developers.com/showthread.php?t=2351782
Click to expand...
Click to collapse
twent4 said:
Just to confirm, do you then go into SU and BB and make sure they are activated?
Click to expand...
Click to collapse
My su file is listed, but if i open with a text editor it seems to by empty.
Su and BB are activated, when i open SuperSu and choose install i get the message"there was an error installing Superuser".

tonyeltriton said:
My su file is listed, but if i open with a text editor it seems to by empty.
Su and BB are activated, when i open SuperSu and choose install i get the message"there was an error installing Superuser".
Click to expand...
Click to collapse
Open a cms and type
adb shell
su
If it's granted then you have su.
Try manually updating just the su binary using the method provided in the dev forum, then try to install super user again.

dully79 said:
Open a cms and type
adb shell
su
If it's granted then you have su.
Try manually updating just the su binary using the method provided in the dev forum, then try to install super user again.
Click to expand...
Click to collapse
shouldn't i get a " # ", when i type su in shell? Nothing appears when i type su:
[email protected]:/ $ su
su
[email protected]:/ $
If i try to start again step by step the installation of Superuser, Su binaries and busybox this is what i get when i type these command:
[email protected]:/ $ su
su
[email protected]:/ $ mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/
by-name/APP
ev/block/platform/sdhci-tegra.3/by-name/APP <
mount: Operation not permitted
255|[email protected]:/ $

tonyeltriton said:
shouldn't i get a " # ", when i type su in shell? Nothing appears when i type su:
[email protected]:/ $ su
su
[email protected]:/ $
If i try to start again step by step the installation of Superuser, Su binaries and busybox this is what i get when i type these command:
[email protected]:/ $ su
su
[email protected]:/ $ mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/
by-name/APP
ev/block/platform/sdhci-tegra.3/by-name/APP <
mount: Operation not permitted
255|[email protected]:/ $
Click to expand...
Click to collapse
Then you have lost su, you just have a ghost file in your folder. You need to re-install the official firmware with the method i linked you.
I can guarantee it works as i purposely deleted su from bin and xbin to test the method.
Feel free to post on my thread and leave this on topic.

tonyeltriton said:
I have just figured out that i have screwed up my Su file, i will have to wait to another OTA update or sildeload actual firmware to install it again. Factory reset didn't help me
Click to expand...
Click to collapse
Try the new Ouya ToolBox version 1.1 that I've uploaded, it should push the correct SU file into your Ouya and take care of it.

foil said:
Try the new Ouya ToolBox version 1.1 that I've uploaded, it should push the correct SU file into your Ouya and take care of it.
Click to expand...
Click to collapse
Hi,
I have the same problem on 1.1. It says it has done it, but when I´ve tried to run superuser on the ouya and select "Install" (NOT install from recovery!) from the options I got an error that says "there was an error installing Superuser. Please send a log of the error to the developer". Unfortunately the log is blank.
Any advice?
Thanks very much for your work, I´m looking forward to making it work!

tonyeltriton said:
My root didn't work with this app on windows 7
Click to expand...
Click to collapse
mine either says access to adb.exe denied very frustrating tried task manager method but when i hit root it says adb is out of date and blinks cmd screens then i close and try again and again plz help
Sent from my N861 using xda app-developers app
---------- Post added at 07:01 PM ---------- Previous post was at 06:14 PM ----------
I keep getting adb.exe denied it just blinks cmd screens and i caught a glimpse of one and it said su exec failed im using toolbox 1.1
Sent from my N861 using xda app-developers app
---------- Post added at 07:08 PM ---------- Previous post was at 07:01 PM ----------
Can u give me a list of everything i need before running this toolbox? I have ADT sdk manager google driver is there more that i need because ive been at this since yesterday. im forum camping lol. havent been to sleep just slaving over this going on 15 hours
Sent from my N861 using xda app-developers app

superfly2hi2die said:
mine either says access to adb.exe denied very frustrating tried task manager method but when i hit root it says adb is out of date and blinks cmd screens then i close and try again and again plz help
Sent from my N861 using xda app-developers app
---------- Post added at 07:01 PM ---------- Previous post was at 06:14 PM ----------
I keep getting adb.exe denied it just blinks cmd screens and i caught a glimpse of one and it said su exec failed im using toolbox 1.1
Sent from my N861 using xda app-developers app
---------- Post added at 07:08 PM ---------- Previous post was at 07:01 PM ----------
Can u give me a list of everything i need before running this toolbox? I have ADT sdk manager google driver is there more that i need because ive been at this since yesterday. im forum camping lol. havent been to sleep just slaving over this going on 15 hours
Sent from my N861 using xda app-developers app
Click to expand...
Click to collapse
Try the new version 1.1.1 that I just uploaded. All problems should be fixed now.

Great, I will test the new version as soon as I go back from work. I let you know if it works.
Thanks for your awesome work!

Hi F0il,
Unfortunately, version 1.1.1 doesn´t work for me at all. When I click on the application it does nothing. I don´t even see the popup saying it´s going to check for connected devices as 1.1 did, but the process is running in the background. I unpluged the ouya, I this error showed up (Don´t know if related
Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at RegawMOD.Android.BatteryInfo.Update()
at RegawMOD.Android.Device.Update()
at RegawMOD.Android.AndroidController.GetConnectedDevice(String deviceSerial)
at OuyaToolbox.Form1.Form1_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.296 (RTMGDR.030319-2900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
OuyaToolbox
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/casa/Desktop/OuyaToolBox_v1_1_1/OuyaToolbox.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 10.0.30319.1 built by: RTMRel
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.233 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1002 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1001 built by: RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
AndroidLib
Assembly Version: 1.5.1.0
Win32 Version: 1.5.1.0
CodeBase: file:///C:/Users/casa/Desktop/OuyaToolBox_v1_1_1/AndroidLib.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
I used Win7 64bits

fenano said:
Hi F0il,
Unfortunately, version 1.1.1 doesn´t work for me at all. When I click on the application it does nothing. I don´t even see the popup saying it´s going to check for connected devices as 1.1 did, but the process is running in the background. I unpluged the ouya, I this error showed up (Don´t know if related
I used Win7 64bits
Click to expand...
Click to collapse
I'm wondering - do you have Microsoft .Net Framework version 4 installed?
I just ran it on 3 computers here at my shop, all on Windows 7 64bit, and I plugged in about 10 different Android devices, and each of them ran it perfectly.

foil said:
I'm wondering - do you have Microsoft .Net Framework version 4 installed?
I just ran it on 3 computers here at my shop, all on Windows 7 64bit, and I plugged in about 10 different Android devices, and each of them ran it perfectly.
Click to expand...
Click to collapse
Hi,
I had one program called .NET framework 4 client profile, don´t know if it´s the one.
Anyway, I downloaded and installed Microsoft .NET Framework 4 (Web Installer) from the Microsoft site, which I think it´s the good one, but no success (I rebooted the pc after installing it, just in case)

fenano said:
Hi,
I had one program called .NET framework 4 client profile, don´t know if it´s the one.
Anyway, I downloaded and installed Microsoft .NET Framework 4 (Web Installer) from the Microsoft site, which I think it´s the good one, but no success (I rebooted the pc after installing it, just in case)
Click to expand...
Click to collapse
Yeah, that's the one you need. Hmm...I'm really having a hard time figuring out what it could be that's throwing those exceptions that it's showing.
Try to run it in compatibility mode, like in this picture. I've got it on another computer at the shop right now, with a Motorola Droid Razr XT912 hooked up, and it's reading it perfectly fine, on Win7 64bit, again!
{
"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"
}
Edit: Also, are you able to communicate with the phone through ADB outside of my program?
ie: adb devices > XXXXXX (device id is displayed) ?

QT Adb GUI

This is a project to make installing/uninstalling packages, file transfers, and running terminal commands via adb easier with a GUI. Currently this project is in beta, there are some issues.
List of known issues:
- No warnings when an operation fails
- Window cant be resized
- UI pauses when running operations such as sideloading and file transfers
Features coming soon:
- Drag and drop file transfers
- Multiple file selection
- Display app names in package manager
- Fastboot functionality
XDA:DevDB Information
QT Adb, Tool/Utility for all devices (see above for details)
Contributors
ioshomebrew
Source Code: https://github.com/ioshomebrew/QTAdb
Version Information
Status: Testing
Current Beta Version: 1.0
Beta Release Date: 2018-06-06
Created 2018-06-07
Last Updated 2018-06-06

[TOOL/UTILITY] Qt ADB

QTADB is a program that is cross-platform and written in QT. The purpose of QTAdb is to provide a better way of transferring files for Android phones as well as other tasks like sideloading packages.
Current issues:
- No warnings for failed task
- Only MacOS build is ready
- UI thread pauses when executing tasks
- Window doesn't properly resize
Features coming soon
- Drag and drop
- Progress bar when transferring files
- Selecting multiple files in file manager
- Fastboot interface
XDA:DevDB Information
QtADB, Tool/Utility for all devices (see above for details)
Contributors
ioshomebrew
Source Code: https://github.com/ioshomebrew/QTAdb
Version Information
Status: Testing
Current Beta Version: 1.0
Beta Release Date: 2018-06-10
Created 2018-06-11
Last Updated 2018-06-10

Unified Deodexer - Support deodexing upto 9.0

This tool is a part of ADK software, thread can be found here (For summary read Introduction part below). Links to download this program will be found at the end of this post. Usage info can be found in second thread.
Click to expand...
Click to collapse
{
"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"
}
Introduction
Deodexing ROM is not so simple task since the recent changes in Android 9 introducing .vdex files. Thanks to anestisb for his vdexExtractor, now deodexing android 9.0 is not quite a difficult task. But hey, let me tell you not all APK, JAR can be deodexed as OEMs god knows adds what's so ever classpath in their vdex, odex, etc. to prevent it from converting to classes.dex
The tool requires build.prop file & app, priv-app, framework folder of either system or vendor partition. Browse it, check if it's supported by the tool. Hit Play button that's it. It may not take much time deodexing your ROM. The tool just process files and deodex them for you, it can be easier if you use an kitchen with it i.e first unpack ROM or decode system.img then run this tool on it. Well I'll recommend you to use ADK kitchen as it's currently made for that
What is ADK?
Well if I've to say, ADK (Android Development Kit) is a complete Windows based GUI application which allows you to edit Android apk files, ROM zips, boot or recovery images, Android Firmware and also to create TWRP/CWM flashable recovery zips easily. It's like a complete Android Kitchen with lots of mods, patches, scripts, templates, rich text editor, etc. like an IDE. For more info visit official thread here.
Click to expand...
Click to collapse
[/QUOTE]
Features
Well here you go,,,
Supports Android 9 ROM.
Powerfull analyzing or ROM structure.
Logs all the process in tools\deodex.log and shows summary within tool.
Manually set tool dir through settings.
Click to expand...
Click to collapse
Changelog and Known Issues
Changelog as per release 1.0.0.0 (19th January 2019)
*Initial Release
Click to expand...
Click to collapse
Downloads & Instructions
To use these tool you must have ADK to be installed. So read steps below (noob friendly) in order to get it. If you want to know what is ADK read Introduction Part above. Also this tool supports deodexing from Android 5.0 to 9.0.
Step 1: Install ADK
Grab a latest release of the software from above link (should be greater than 1.0.4.6).
Step 2: Extract the ZIP and install setup.exe as we normally do.
Do not install the software in C:\Program Files or Program Files (x86) folder.
Step 3: Launch ADK from desktop shortcut, check & download updates if available for ADK.
Step 4: Now open the Deodex Tool.
The tool can be opened from Tools > Deodex Tool or create a ROM Project in ADK then select Project > Deodex Project.
Step 5: Read Usage Instructions below.
Click to expand...
Click to collapse

Using the Program
Standard way
Once you've successfully installed and updated ADK to the latest version. Click on Tools > Deodex Tool option. A window will pop up as shown in first post.
Now click on browse button. The three dot button and select a folder containing apps, priv-apps, frameworks folder & build.prop file. The tool will load all the details.
Now click on the Play button to start the deodexing, it will not take much time (as shown below).
In above image Green text showing number 18 is the success rate, Orange showing 0 is warning messages & Red showing number 21 is Error i.e the number of failed to deodex files.
Logs along with the exception will be generated in tools\debug.log file. A summary will be shown within the output in the tool.
It will notify you once the task is Finished.
Click to expand...
Click to collapse
Using ADK
First we are going to create a ROM project. Not only this will allow us to deodex ROM but also to add more mods and tweaks to ROM.
So let's start ADK, then click File > New > New project a window will pop-up from there select ROM/Update.zip. Give your project a name and browse for the ROM zip file from below three dot button (as shown below).
In above image, 360OS_LP is my project name and C:\Users\Dell\Documents\Roms\360_OS_VF1.zip is the location of ROM zip.
Now click create button to start the project creation. The process will take time according to your ROM structure. Once done you will see something like below.
Now directly click on Project > Deodex Project then simply hit Play button as we do. Done...!
Also you to load updater-script from your ROM, you can click Project > Load updater-script. See Project tab or read the current Getting started Page to know what cool things you can do to your ROM project.
Click to expand...
Click to collapse

[email protected] said:
Using the Program
Click to expand...
Click to collapse
Hi, thanks for the tool.
one question , can it be used to deodex an apk with (odex,vdex) files and then recompile it as single apk file ?
in fact i want to port an apk from an odex stock Rom to custom rom
EDIT:
mh this tool seems to powerful to convert a single App lool

rodolphe06 said:
Hi, thanks for the tool.
one question , can it be used to deodex an apk with (odex,vdex) files and then recompile it as single apk file ?
in fact i want to port an apk from an odex stock Rom to custom rom
EDIT:
mh this tool seems to powerful to convert a single App lool
Click to expand...
Click to collapse
Single APK option is not added yet, I will add an update to it as quick as I can!

nice job... how to know deodex rom or not ?

zynonimoux said:
nice job... how to know deodex rom or not ?
Click to expand...
Click to collapse
That's a good question! This feature is not implemented yet. I will implement it soon.
If you manually want to check if ROM is deodexed or not! Go to folders like app, priv-app. Check if there exist files like .odex or .vdex. If they exist then it means ROM is not deodexed.

@[email protected]
Can't deodex this ROM:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip
for build.prop see attached file.
For more information about calling real-time (JIT) debugging instead of this dialog box,
See end of this message.
Exception text **************
System.IndexOutOfRangeException: The index exceeds the array boundary. In ADK_context.
Classes.Tasks.GetPropValue (String ID, String filename)
In DeodexTool.Form1.loadinfo (Boolean first)
In DeodexTool.Form1.button1_Click (Object sender, EventArgs e)
In System.Windows.Forms.Control.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
In System.Windows.Forms.Control.WmMouseUp (Message& m, MouseButtons button, Int32 clicks)
In System.Windows.Forms.Control.WndProc (Message& m)
In System.Windows.Forms.ButtonBase.WndProc (Message& m)
In System.Windows.Forms.Button.WndProc (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message& m)
In System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
Mscorlib
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Deodex
Assembly version: 0.5.0.0
Win32 version: 0.5.0.0
Basic code: file:///D:/ADK/deodex.exe
----------------------------------------
System.Windows.Forms
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---------------------------------------- ADK.
FastColoredTextBox
Assembly version: 2.16.23.0
Win32 version: 2.16.23.0
Basic code: file:///D:/ADK/ADK.FastColoredTextBox.DLL
----------------------------------------
System.Configuration
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
---------------------------------------- ADK.
Progress
Assembly version: 1.0.0.0
Win32 version: 1.0.0.0
Basic code: file:///D:/ADK/ADK.Progress.DLL
----------------------------------------
Mscorlib.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
JIT Debugging **************
To enable real-time (JIT) debugging,
Must be set in the system.windows.forms section of the application or computer's. config file (machine.config)
JitDebugging value.
You must also enable the application when compiling the
Debugging.
For example:
<configuration>
<system.windows.forms jitdebugging=""true""></system.windows.forms>
</configuration>
When JIT debugging is enabled, any unhandled exceptions
Will be sent to the JIT debugger registered on this computer, Instead of processing from this dialog box.

qqzwc said:
@[email protected]
Can't deodex this ROM:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip
for build.prop see attached file.
For more information about calling real-time (JIT) debugging instead of this dialog box,
See end of this message.
Exception text **************
System.IndexOutOfRangeException: The index exceeds the array boundary. In ADK_context.
Classes.Tasks.GetPropValue (String ID, String filename)
In DeodexTool.Form1.loadinfo (Boolean first)
In DeodexTool.Form1.button1_Click (Object sender, EventArgs e)
In System.Windows.Forms.Control.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnClick (EventArgs e)
In System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
In System.Windows.Forms.Control.WmMouseUp (Message& m, MouseButtons button, Int32 clicks)
In System.Windows.Forms.Control.WndProc (Message& m)
In System.Windows.Forms.ButtonBase.WndProc (Message& m)
In System.Windows.Forms.Button.WndProc (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message& m)
In System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message& m)
In System.Windows.Forms.NativeWindow.Callback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
Mscorlib
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Deodex
Assembly version: 0.5.0.0
Win32 version: 0.5.0.0
Basic code: file:///D:/ADK/deodex.exe
----------------------------------------
System.Windows.Forms
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
---------------------------------------- ADK.
FastColoredTextBox
Assembly version: 2.16.23.0
Win32 version: 2.16.23.0
Basic code: file:///D:/ADK/ADK.FastColoredTextBox.DLL
----------------------------------------
System.Configuration
Assembly version: 4.0.0.0
Win32 version: 4.7.3324.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly version: 4.0.0.0
Win32 version: 4.7.3362.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
---------------------------------------- ADK.
Progress
Assembly version: 1.0.0.0
Win32 version: 1.0.0.0
Basic code: file:///D:/ADK/ADK.Progress.DLL
----------------------------------------
Mscorlib.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly version: 4.0.0.0
Win32 version: 4.7.3190.0 built By:net472rel1last_c
Basic code: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_zh-Hans_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
JIT Debugging **************
To enable real-time (JIT) debugging,
Must be set in the system.windows.forms section of the application or computer's. config file (machine.config)
JitDebugging value.
You must also enable the application when compiling the
Debugging.
For example:
<configuration>
<system.windows.forms jitdebugging=""true""></system.windows.forms>
</configuration>
When JIT debugging is enabled, any unhandled exceptions
Will be sent to the JIT debugger registered on this computer, Instead of processing from this dialog box.
Click to expand...
Click to collapse
I got how to solve this problem.
1. your tool expect [ro.build.version.release=9.0.0] but actually it is [ro.build.version.release=9 and ro.rom.version=9.0]
2. your tool expect [ro.product.name=OnePlus3T] but actually it is [ro.product.device=OnePlus3T]
So this tool crashes.
But it still cann not deodex the provided rom for me, you can have a try:
http://download.h2os.com/OnePlus 3T...8_OTA_060_all_1903310222_b76c39af1e5d4362.zip

This tool does not deodex boot.oat?

lieuliau said:
This tool does not deodex boot.oat?
Click to expand...
Click to collapse
I tried deodexing it for some ROMs for 2 of my devices using latest oat2dex, but it does not work and sometimes failed to boot (Roms were above 8.1), so I thought of removing deodexing of boot.oat from release! But in future I will add an option for user to choose if they want to deodex them at their own risk.

Does not support deodexing up to 9.0

Hello
[email protected] said:
Introduction
Click to expand...
Click to collapse
Features
Changelog and Known Issues
Downloads & Instructions[/QUOTE]
Great tool !!! very beautiful! on the roms android 8 everything ok, perfect !!! while on the rom android 9 I have an error in unzipping the file "system.new.dat.br ... so with another program I converted it to:
"system.new.dat". Now your tool executes the Unzip of "filesystem.new.dat", but when I run the deodex tool it gives me an error in all the apks. (Error: or: "Could not deodex!")

ankh3 said:
Great tool !!! very beautiful! on the roms android 8 everything ok, perfect !!! while on the rom android 9 I have an error in unzipping the file "system.new.dat.br ... so with another program I converted it to:
"system.new.dat". Now your tool executes the Unzip of "filesystem.new.dat", but when I run the deodex tool it gives me an error in all the apks. (Error: or: "Could not deodex!")
Click to expand...
Click to collapse
Do this:
1. Yesterday i release a new version of ADK so update it from website https://androdevkit.github.io by downloading latest release and perform an overwrite install.
2. Now create a ROM project in ADK (i fixed the issue you are facing).
3. Once you have your system folder in Solution, select Tools > Deodex Tool.
4. Now try deodexing it. (Note: when you are trying to Deodex framework folder some of the apk and binaries will remain odexed due to incompatibility)

[email protected] said:
Do this:
1. Yesterday i release a new version of ADK so update it from website by downloading latest release and perform an overwrite install.
2. Now create a ROM project in ADK (i fixed the issue you are facing).
3. Once you have your system folder in Solution, select Tools > Deodex Tool.
4. Now try deodexing it. (Note: when you are trying to Deodex framework folder some of the apk and binaries will remain odexed due to incompatibility)
Click to expand...
Click to collapse
Thanks! I tried your procedure but during the deodex I have the same error ...

ankh3 said:
Thanks! I tried your procedure but during the deodex I have the same error ...
Click to expand...
Click to collapse
Send your ROM zip so that i can check it!

[email protected] said:
Send your ROM zip so that i can check it!
Click to expand...
Click to collapse
OK thank you very much!
I tried with 3 Rom with android 9, same error. try this:https://drive.google.com/open?id=1DqY6zTScWU4F1TpDd4FcoaiEDs1dkSFI

ankh3 said:
OK thank you very much!
I tried with 3 Rom with android 9, same error. try this:https://drive.google.com/open?id=1DqY6zTScWU4F1TpDd4FcoaiEDs1dkSFI
Click to expand...
Click to collapse
Hello this could take a while! Due to busy work schedule.

[email protected] said:
Hello this could take a while! Due to busy work schedule.
Click to expand...
Click to collapse
Do you get the same error?
Did I do something wrong in the process?

ankh3 said:
Do you get the same error?
Did I do something wrong in the process?
Click to expand...
Click to collapse
Check PM

Hi! and thank you for this app.
I've same error with LineageOS for Sony xz1 compact (this Rom: lineage-16.0-20191118-UNOFFICIAL-RC6-lilac, By Modpunk on XDA. Sorry, I can't to post external links because I'm new user).
"Error: Could not deodex!" in all the apks.
Have you got a solution?
Thanks!