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!
Related
youADB (formerly called adb gui) is, as the old name suggests, a graphical user interface for adb.
It allows you to easily perform numerous actions without using cmd. No more typing, no more typos - use adb's main functions...plain and simple!
Some features:
-1-Click Reboot (Regular/Recovery)
-Partition-Manager (1-Click partitioning!) - using parted in rec-mode
-Save & view logs!
-File-Manager (push, pull, delete files...)
- App - Manager (install / uninstall applications!)
-shows device state and serial number
-custom adb commands
soon to be added: -pie chart for partitioning tool
-setup wizard
Screenshots:
---THIS PROGRAM IS HIGHLY EXPERIMENTAL. USE IT AT UR OWN RISK---
New release: Build 01611
Just minor changes (which result in a way better user experience though), a quick&dirty build - please report bugs
Changelog:
-added vertical scroll bar to all file/app-lists (better for long filenames)
- file- and applists are sorted alphabetically
- double-click a folder to enter it (file manager)
________________________
New release. Build 01711.
Changelog:
-Scalable gui. you can adjust the fileviewers size to the size you want. very useful, especially if there are many long filenames.
as requested by evilkron.
______________________
build 01711b
changelog:
-fixed filebrowser's "..." button
_______________________
build 02111
changelog:
-push/pull file function updated
-MAJOR speed and stability improvements: app starts in less than 1sec and uses multitasking so that it will stay stable and is faster (especially when pushing files or searching fo .apks on ur computer!)
new release
________________
build 00412
changelog:
-bugfix (no more crashed when adbserver is already running)
-feature to install recovery images (.img's) fully working
DOWNLOAD:
youadb.4shared.com
no GUI now
ADB File Explorer
Perhaps this application is what you are looking for.
http://forum.xda-developers.com/showthread.php?t=523960
Edited 1st post.
Initial release of "ADB GUI"
Droid Explorer is the best:
http://de.codeplex.com/
st0kes said:
Droid Explorer is the best:
http://de.codeplex.com/
Click to expand...
Click to collapse
Thx for the link. Screenshots look really good - the program isnt working for me though. I get errors when starting it...
i will continue developing my program. It's (going to be) more of a light-weight alternative
EDIT
New release (Build 00611)
Changelog:
-minor bugfixes
-added a progress bar to the partitioning tool
-progress is shown in the custom command window too
http://ul.to/13dx5r
New build (00811).
+ UI changes
+ better performance (concerning sd tool)
+ new splashscreen
+ progressbar for sd tool
DOWNLOAD: http://ul.to/mysbts
EDIT: Looks like the latest build has a lil bug. if it's stuck at the splashscreen, use the tast manager (alt+del+ctrl) to end the adb.exe task. I'm gonna fix it.
C#,
Would you like opensources?
Thanks.
wellbug said:
C#
Click to expand...
Click to collapse
It actually is written in VB.NET (2008)
I might release the SourceCode...i have to tidy it up a bit though and i still couldtn completely get rid of the bug.
I'm working on some nice features (easy app installation and deinstallation) right now.
Alright guys,
this is a MAJOR update.
Changelog:
+program starts in milliseconds
+added filebrowser (with push, pull & delete feature!)
+added app - manager (install & delete apps - easily !)
+improved ui
+improved look
+fixed many bugs
DOWNLOAD (build 01311)
I accidentally selected the wrong SDK folder at the very first startup of the application. But I can't change it.. When I try to start the it I get the following error message:
Unhandled exceptio has occurred in your application. If you click Continue, the application will ignore this error and ettempt to continue. If you click Quit, the application will close immediately.
The system cannot find the file specified.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at adbgui.Form3.startserver()
at adbgui.Form3.Form3_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.ContainerControl.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: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
youADB
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/HTC%20Roms%20(Android)/youADB/youADB1.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.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.
Hopefully you can fix this with my given information.
I am very curious what this application can do!
Thanks in advance.
Haha, I forgot to think of that I'll today add a feature to reset the config-file.
What you can do: Have a look at your C:\ harddrive. there should be a adbgui or youadb folder. simply delete it! at next startup you'll be able to chose the adb.exe (NOT the folder) again.
EDIT: I released a new build which prevents you from chosing a wrong file.
DOWNLOAD BUILD 01411
If you used an old version and chose the wrong file, just delete die folder C:\adbgui\ !
changelog: -improved setup dialog
thanks! great job
New release: Build 01611
Just minor changes (which result in a way better user experience though), a quick&dirty build - please report bugs
Changelog:
-added vertical scroll bar to all file/app-lists (better for long filenames)
- file- and applists are sorted alphabetically
- double-click a folder to enter it (file manager)
DOWNLOAD:
youadb.4shared.com
New release. Build 01711.
Changelog:
-Scalable gui. you can adjust the fileviewers size to the size you want. very useful, especially if there are many long filenames.
as requested by evilkron.
_________________
build 01711b
changelog: fixed filebrowser's "..." (go back) button.
Thanks,
If i have your sources,maybe it's easy to write a version for mac.
i will release the sourcecode once i think i'm done with the program.
im guessing this wont work for linux...
jamezelle said:
im guessing this wont work for linux
Click to expand...
Click to collapse
unfortunately not. actually you could try to use wine.
NEW RELEASE: build 02111
changelog:
-push/pull file function updated
-MAJOR speed and stability improvements: app starts in less than 1sec and uses multitasking so that it will stay stable and is faster (especially when pushing files or searching fo .apks on ur computer!)
Download: youadb.4shared.com
new release
________________
build 00412
changelog:
-bugfix (no more crashed when adbserver is already running)
-feature to install recovery images (.img's) fully working
download:
youadb.4shared.com
Hi,
I wouldn't create this thread if i'm not REALLY REALLY DESPERATE..
Basically i'm writing a very simple app (a game) that sends SMS to a particular number every time a button is pressed. But the thing is I get SecurityException although I already requested it in the Manifest file. Signing with the debug keystore nor my own publisher keystore won't grant the permission.
The message from SecurityException is "Users 10036 does not have android.permission.SEND_SMS.ID = 0"
Here's my setup:
Win 7 64-bit
JDK 1.6.0_25 64-bit
Android SDK Revision 10
Eclipse Version: 3.7.0 Build id: I20110310-1119 64-bit
ADT 10.0.1
My entire project source file is available as an attachment to this post.
PLEEEEEAZZEEE... Someone save my arrrrseeee...
You need to use <uses-permission> and not <permission> in your AndroidManifest.xml.
<permission> declares a new permission, while <uses-permission> means that your application requires a certain permission.
More about <uses-permission>: http://developer.android.com/guide/topics/manifest/uses-permission-element.html
// A
I love you!!!!!
Thank you sooooooo muchhhh!!!!!!!
APK to Java Beta
Description:
Since I'm into making Android Apps nowadays, I thought of making this tool to save me (and you) time. So I started coding it and it worked out pretty well so far. The tool can decompiles your selected apk to Java code, to learn from it, so as an educational purpose.
Additionally it also can decompile to smali code and it can decompile the resources of the app. It's currently a very early beta but it works successfully (at least at my computer)
Used External Tools:
- 7za
- apktool
- baksmali-1.4.0
- jd-gui
- dex2jar
Requirements:
- JRE 6/7 (I think that's all, but maybe android-sdk is needed, I guess not)
Screenshots:
{
"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"
}
Added very basic help file, various code fixes (no errors should occur on decompiling java/smali/resource. the Eclipse projects are still bugged though)
Download:
Version 0.9 beta (check github for changelog):
Mirror #1: broodplank.net
Mirror #2: Mediafire.com
Version 0.8 beta (check github for changelog):
Mirror #1: broodplank.net
Mirror #2: Mediafire.com
Version 0.7 beta (check github for changelog):
Mirror #1: broodplank.net
Mirror #2: Mediafire.com
Version 0.6 beta (check github for changelog):
Mirror #1: broodplank.net
Mirror #2: Mediafire.com
Version 0.5 beta:
Mirror #1: broodplank.net
Mirror #2: Mediafire.com
Github Sources:
https://github.com/broodplank/APKtoJava
Please let me know how it runs!
Thanks! Was looking for a tool like this. I need to learn a lot about developing android apps. Will download this as soon as i get on my PC this evening.
Sent from my GT-S5360 using xda premium
anasdcool71 said:
Thanks! Was looking for a tool like this. I need to learn a lot about developing android apps. Will download this as soon as i get on my PC this evening.
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
You're welcome! Please let me know your experience with the app, it still needs a lot of testing!
Alright, so i tested the 0.6 beta. I chose my app from eclipse, as i already knew its source code. Decompiling into resources and smali files are working totally fine, but it is not able to generate the java code. I got that message :-
I went to jd-gui and did what i was told, but nothing happened. After clicking OK, an error message came that the input file was invalid. After that the tool won't close. I had to open the task manager to end it.
anasdcool71 said:
Alright, so i tested the 0.6 beta. I chose my app from eclipse, as i already knew its source code. Decompiling into resources and smali files are working totally fine, but it is not able to generate the java code. I got that message :-
I went to jd-gui and did what i was told, but nothing happened. After clicking OK, an error message came that the input file was invalid. After that the tool won't close. I had to open the task manager to end it.
Click to expand...
Click to collapse
Thanks for your feedback, I had the same error once, it seems there is a problem with this file "dex2jar.bat". somehow I just doesn't get executed the right way, the strange thing is that it's executed the same way as the other batch files, and if I do it manually: "dex2jar.bat classes.dex" then it also works..
So I though maybe the working directory needs to be set.
edit:
Code:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit
Press any key to continue . . .
so that's the problem . Will lower the heap ^^
Open the /tools/dex2jar.bat file and paste this contents into it:
Code:
@echo off
cd /d %~dp0
REM
REM dex2jar - Tools to work with android .dex and java .class files
REM Copyright (c) 2009-2012 Panxiaobo
REM
REM Licensed under the Apache License, Version 2.0 (the "License");
REM you may not use this file except in compliance with the License.
REM You may obtain a copy of the License at
REM
REM http://www.apache.org/licenses/LICENSE-2.0
REM
REM Unless required by applicable law or agreed to in writing, software
REM distributed under the License is distributed on an "AS IS" BASIS,
REM WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
REM See the License for the specific language governing permissions and
REM limitations under the License.
REM
set CLASSPATH=
FOR %%i IN ("%~dp0lib\*.jar") DO CALL "%~dp0setclasspath.bat" %%i
java -Xms512m -cp "%CLASSPATH%" "com.googlecode.dex2jar.tools.Dex2jarCmd" %*
new version released! the option to convert to an Eclipse project is now available (still beta though)
See changes here
Btw i forgot a critical fix. Check latest commit for fix
Awesome apk.
tapatalked² from cowsquadGnex®
cowsquad said:
Awesome apk.
tapatalked² from cowsquadGnex®
Click to expand...
Click to collapse
Thanks.
btw, V0.8 released!
Changes: 1 2 3
It's becoming much more stable luckily
Alright bro, i've to yet try the 0.8 version (using the 0.6). Your solution worked. My source was decompiled to the java files. But i see there were some changes :-
1) I saw that the 'this' keyword was used before almost every variable even if i hadn't included it (but that's not much of a problem, though).
2) I had used that tag R.id.editText1, R.id.radioButton1, etc. to use my views from the res folder. But in place of those, there were some numbers.. I really find it hard to work with them.
anasdcool71 said:
Alright bro, i've to yet try the 0.8 version (using the 0.6). Your solution worked. My source was decompiled to the java files. But i see there were some changes :-
1) I saw that the 'this' keyword was used before almost every variable even if i hadn't included it (but that's not much of a problem, though).
2) I had used that tag R.id.editText1, R.id.radioButton1, etc. to use my views from the res folder. But in place of those, there were some numbers.. I really find it hard to work with them.
Click to expand...
Click to collapse
Hmm the random numbers as variables kinda sucks, I know, but that's just the way the program (jd-gui) works unfortunately, it makes things a lot harder to read but at least it's a working java source. Unfortunately jd-gui doesn't have any commandline tool with several switches. (I saw some other jar to java decompilers, but they gave a source code even more strange, so I think jd-gui is the best solution for now, of course I will update it if possible)
Looking forward to more updates for this great tool!
emd2009 said:
Looking forward to more updates for this great tool!
Click to expand...
Click to collapse
v0.9 released
Changes: 1 2 3
With all versions of your tool, including v9, I get an error whenever I export as an Eclipse project:
Line 4503 in APKtoJava.exe
Error: Subscript used with non-Array variable
emd2009 said:
With all versions of your tool, including v9, I get an error whenever I export as an Eclipse project:
Line 4503 in APKtoJava.exe
Error: Subscript used with non-Array variable
Click to expand...
Click to collapse
Thanks for letting me know. Ill take a look at it ^-^
I think i know what to change
Attached a screenshot of the error when trying to get an eclipse project (happens after the JD-GUI thing)
Jonny said:
Attached a screenshot of the error when trying to get an eclipse project (happens after the JD-GUI thing)
Click to expand...
Click to collapse
Thanks, more people reported that problem, I think changing this: "$namearray[0]" to "$namearray" and "$tarsdkarray[0]" to "$tarsdkarray" will do the trick, but I'm not sure since it always works at my computer no matter if I put [0] or nothing.
Ill upload new version soon
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) ?
{
"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"
}
This software will ask for sudo permissions in your machine to download and install all required tools for this program to run correctly, also, it'll execute chmod and chown to this program files and ~/.megarc (if exists) for the correct functioning of all the code, I'm not responsable if this program breaks your Machine (which it shouldn't be able by no ways). When you run for the first time this program, it will proceed to his first run configuration after the user authorization.
Welcome, I've been developing this program a long time ago with my free time after college, this is my first project made in Bash, the main purpose of all this software is to make a lot easier the process of building a Kernel, no matter which device you're building to (excluding MTK and those without source). This program will automatically download all required tools for Kernel building (~1.5GB), including the CrossCompiler (GCC arm/arm64) and other misc tools. You don't need a lot of knowledge to build your kernel with this software and it has all the tools for automatically build everything in just one command!
Requeriments:
A machine with Linux
Git
This program
Once you've downloaded the program to your Machine, you have to cd with Terminal to where you downloaded all the files and execute "core.sh" (bash core.sh or . core.sh) (Like this Example), this is indispensable every time you want to run the program, because it sets the program paths (Otherwise it'll not work)
Now, How it works?
Once you run the program, if it's for the first time then it'll automatically download all required tools and install them, after this it's time to setup your environment. You'll see a folder named "source", you have to put there the folder with the Kernel source contents like this and another folder named "templates" where you can set your AnyKernel (only AnyKernel for now) templates for different devices (Or just use the local one).
That's all, this program only needs you to set the Kernel source, now you've to run again core.sh and it'll prompt to you all the data needed for that session, like the name of the kernel, target android, version, kernel source folder, etc... When you've to select the architecture of your device, arm or arm64 and it'll download the correspondent CrossCompiler (GCC 4.9), after this, it'll promt to you how to set Kernel Installer template, the first option is to extract the local AnyKernel source into "./out/ak_template/" (Thanks to @osm0sis), second option is for select a user template from "./templates/" folder and the third option requires you to set manually the installer template inside "./out/ak_template/" similar or like this (Remember to configure it).
When it promt to you the variant, you've to put preferably the codename of your device (For example: Oneplus One codename is "bacon") and then select a defconfig for that device (For example: For Oneplus One it would be "lineageos_bacon_defconfig"), now that the program knows for which device It's going to compile, (You can add more variants) then, you can enable the KernelDebug option to enable the creation of the Device tree image (Applies for arm devices only) and allow the kernel source cleaning on every compiling process...
Now, let's get into the commands:
Command: "essentials <flag>": Here is where you start once you finish setting all the configs, 'essentials' is the main command of this program, but it only works with flags, otherwise it'll display the flags information that I'm gonna show right now:
Flags:
--kernel (Start the process of compiling your kernel)
--dtb (Generates the device tree image, applies to arm devices only)
--anykernel (Builds a installer for your kernel based on Anykernel by @osm0sis)
--upload (Uploads your Kernel installer to the root of your MEGA storage)
--all (This flag does all processes mentioned above)
You can combine all the flags except for "--all", because this one already does everything, also, no matter in which order, all the functions are going to be done in order to prevent an error (For example: 'essentials --anykernel --kernel' will build the kernel and then build the installer).
Also, after the first run, theres a file named: "defaultsettings.sh", it has a variable inside named "DSENABLED", if you set it to 1, the program instead of prompt you for information when you run "core.sh", it'll take all the config directly from that file, just make sure you've configured it first. :good:
Command: "auto <device> <flag>": This command allows you to make pre-configured files for a specified device, it requires that you have executed the program core.sh for the first time because it stores some config in your ~/.bashrc file, then, you can turn on or restart your machine and this command will still be available for it's use.
When you run 'auto' and next to it you specify the device (for example: auto oneplus), if the device (oneplus) doesn't exist in the device database (./resources/devices/) then, it'll promt to you all the data required for kernel, dtb (if applies), anykernel and upload process.
Once you have configured your device it'll be stored and when you run again the command 'auto' followed by the device name you configured before, (for example: auto oneplus) it'll load that device config file and build everything automatically (Kernel, dtb if applies, anykernel and upload if its enabled).
The Flags for this commands are:
--edit (Opens you the <device> config file for editing with nano)
--remove (Simply removes the <device> config file)
For more information I highly recommend to read the README.md in this program source on Github (It contains a more datailed and complete information).
This program has been tested and used on the following Linux distributions:
Ubuntu
Debian
I will really appreciate any feedback about how it performs on other Linux distributions
You can contact me with a PM (private message) here or in my Telegram group! (I'm @ArtxDev)
Me, @Stayn (Artx)
@osm0sis for his AnyKernel
This project on Github is open to pull requests, I will not hesitate to dedicate you a space here if you contribute for this project :good:
I'll be updating this program fixing bugs and bringing new features :good:
If you like it and want to do a small donation it for sure is gonna help me a lot and keep me motivated! :laugh:
Thank you and enjoy it!
XDA:DevDB Information
Kernel Building - Essentials, Tool/Utility for all devices (see above for details)
Contributors
Stayn
Source Code: https://github.com/KB-E
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-07-30
Created 2018-07-09
Last Updated 2018-07-30
In progress...
Mini Guides for absolutely newbies in progress...
Thanks
I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected
dancer_69 said:
I just tried it and I get an error:
./core.sh: line 125: .: defaultsettings.sh: file not found
This file exists in Kernelbuilding-essentials directory though.
EDIT:
I tried to change ". defaultsettings.sh" with the full path of this file in line 125 and then I get another error on line 126
err: unary operator expected
Click to expand...
Click to collapse
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"
Stayn said:
Don't use sh to execute core.sh, use ". core.sh" or "bash core.sh"
Click to expand...
Click to collapse
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.
dancer_69 said:
Thanks, I'm using arch linux and zsh as default. With "bash core.sh" the script runs fine.
Click to expand...
Click to collapse
Thanks for the feedback! If you have any other problem tell me
Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash
osm0sis said:
Cool project! You should specify bash in the shebang (normally the first line of a shell script) to fix issues where bash isn't default:
Code:
#!/bin/bash
Click to expand...
Click to collapse
Done! Thanks
Hey guys, now Kernel Building - Essentials it's stable!
I've been working on fixing a lot of bugs and updating the program structure, now that the structure is totally defined and I don't need to change it anymore, I'll upload the first release at GitHub, version 1.0 and the next versions will be coming with a file to update your old version on KB-E (In this way there's no need to clone the repo again and again and merging your devices or configuration...)
There is all the updates and changes:
- Added a folder for Multiple Installers Templates: I've been thinking that anyone could have various kernel projects for different devices, so this means, that the templates for the installers needs to be different, so, now you can trow all the templates you want inside "templates" folder and the program will prompt to you which one you'll use for the current session (using core.sh "essentials" command) or a pre-configured device (using auto.sh "auto" command)
- Replaced option 2 in the program installer template config method, removed the ability to download the template from your MEGA Cloud and replaced by a selection of user templates inside "./templates/" folder
- Changed the "setuptools.sh" file name to "programtools.sh" because, all program misc functions are going to be stored there and "programtools" makes more sense
- Fixed a bug that happened when you didn't gave to the program the device variant (or codename) and then, "essentials" and "auto" command were not working, now the program forces you to set it (You can set your device name as device variant but it's preferably the device codename)
- Now when the program downloads the correspondent crosscompiler, it shows you the process
- Added the package "device-tree-compiler" into the download list of the function "installtools" (Executed when you run the program for the first time), this package is necessary for some arm64 sources to build device tree
- Fixed a annoying bug that cd's you to your "~/" directory instead of the current directory you were after executing "essentials" or "auto" command
- Now core.sh doesn't change the whole file permissions of your sources (sorry for this)
- Added a boost functionality for "auto" command that sums 2 threads to the compiling jobs when compiling the kernel (Recommended for machines with more than 2 real cores)
- Updated README.md
I would really apreciate some feedback guys, if you have any problems or you need help, feel free to contact me via my Telegram Group, enjoy!
Hi, it looks good so far...I have an MT6580 that I play around with but it's been stuck on kernel 3.10 for a long time. I've spent weeks trying port kernel from other MT6580 devices but haven't gotten any success yet. I got through the core.sh part. Is the essentials commands next ? I don't see it anywhere in the program.
Now I know how you automatically upload kernel to Mega Drive using code.. Unfortunately my G3 was Died...:crying:
Anyone know how to remove unwanted feature from a cooked/compiled kernel?
Excuse me, does this work on Ubuntu that runs on Windows Subsystem for linux?
By the way, thank you for the amazing artx-powered TWRP on my G3.