yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] joeldroid:
Thanks for the kind words [MENTION=1481114]purian23[/MENTION]
[Android Software/Hacking General [Developers Only]] DarkAngel:
How is your "Path" set? I just recently switched to 8.1.

.NET Framework 4.5 is already included in the structure of Windows 8.1 so no need to worry there.

This is how I have mine and it works for me. Take in consideration of other things I may have already going on in my computer that you may not have and modify accordingly to your path variables by omitting or adding to it. Use it as you wish. Everyone's "Path" can or will be different. Modify your Java version accordingly.

I have laid it out as if it were one variable per line but they all should go together as one continuous line, back to back.

C:\Program Files (x86)\Intel\iCLS Client\;
C:\Program Files\Intel\iCLS Client\;
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
C:\Windows\SysWOW64;
C:\Windows\System32;
C:\Windows;
C:\Windows\SysWOW64\WindowsPowerShell\v1.0;
C:\Windows\System32\WindowsPowerShell\v1.0;
C:\Windows\SysWOW64\wbem;
C:\Windows\System32\wbem;
C:\adb;
C:\Program Files\Java\jdk1.8.0_40\bin;
C:\Android Studio\sdk\tools;
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
%SystemRoot%\system32;
%SystemRoot%;
%SystemRoot%\System32\Wbem;
%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;
C:\Windows\Microsoft.NET\Framework\v4.0.30319;
C:\Windows\Microsoft.NET\Framework64\v4.0.30319;

@joeldroid

Life comes first, as we all know already. Do what you got to do and TY for this tool. GL!
[Android Software/Hacking General [Developers Only]] :
This worked for me.
[Android Software/Hacking General [Developers Only]] Hen Ry:
Was a Problem with Symlink Path Oracle. Worked. [emoji106]
[Android Software/Hacking General [Developers Only]] mikeyxda:
Can't get 2.5 Beta to work either. I've made sure I don't have the Oracle path (the one that gets created after each Java install). I've tried both 32 and 64 bit paths. 2.5 Beta always says Java 7 required and can't find it. With the exact same path variables, 2.4 works fine. Hope this helps.

Mike
[Android Software/Hacking General [Developers Only]] carl1961:
+1
[Android Software/Hacking General [Developers Only]] :
+2 but to get java 7 go here and scroll to the bottom pf the page. You will have to make a account to download older versions.

If there is anyone who has successfully deodexed a Verizon ROM I need some help with this error.

VZWAPNLib - FAILED - Re-Compression Failed
[Android Software/Hacking General [Developers Only]] purian23:
It looks like I got a little further with 2.5 beta, but after what you see on the photo attached it wouldn't go onto the next command. I had to nail down my Java Path again to run the program.

Variable Name: PATH

Variable Value: C:\Program Files\Java\jdk1.7.0_76\bin;

Hopefully that'll help and we get some talented dev's to step in with Joel's great work here to keep it going while he's away.

[MENTION=5601139]Misterxtc[/MENTION] I was able to successfully deodex that file from the Verizon System image, I've attached this for you as well :good:
[Android Software/Hacking General [Developers Only]] :
Thank you, I'll give this a try soon. That's as far as I got with 2.5 beta too.
[Android Software/Hacking General [Developers Only]] mikeyxda:
Yeah, I managed to get that far too. It'll do boot.oat and then stop. What I ended up doing is just installing 2.4 and then copying oat2dex.jar from 2.5Beta to 2.4 and 2.4 works fine. I did find a problem with (even the latest) oat2dex.jar though which I reported in another thread. Kind of a show-stopper: in some cases, oat2dex.jar gets the field order wrong and ends up putting the wrong values in fields. I posted about that in this thread. Of course, the deodexed file usually crashes in these cases but fortunately it looks like it only has a problem with a fraction of files. Problem is, unless you decompile the result and compare to a known good deodexed version, you can't tell if it got deodexed properly or not and sometimes the result will still run but have strange errors that might not even be visible unless you look in logcat. So right now, deodexing 5.1 files is a bit of a crap shoot as the deodexing process is not 100%.

Edit: also, as far as I can tell, smali/baksmali 2.0.5 is not used in this utility. Smali/baksmali cannot deodex 5.1 files so I believe oat2dex is the "meat" here: that's what is deodexing the files. Used-to-be... you could just pull the dex out of the odex file with a hex editor and drop that raw chunk as classes.dex and it'd work. Not with 5.1, it looks like there's some sort of association table needed to massage some opcodes/data in the dex file. I don't envy those who have to reverse engineer that. If I had the oat2dex source, I could try my hand at it but as far as I can tell, that source is not available.

Mike
[Android Software/Hacking General [Developers Only]] berryman13:
Thank you Joel for all your work. We appreciate it.
[Android Software/Hacking General [Developers Only]] DarkAngel:
Will it support Java 8? v2.4 worked great and was working on

Windows 7

w/ Java 8 JDK. I recently switched over to Windows 8 w/ Java 8 JDK and it still works, just not v2.5 as it asks to install Java 7.

Just a heads up for people..... posted on the Oracle site but it shouldn't be to big of a deal. ( 7u79 & 7u80 )

Also, no need to make an account to DL Java 7. Just need to Accept the License Agreement and download. And for those people having issues with it not working this is one reason why it may not be for you.

So if you have for example JRE set in front/first of JDK, it will read JRE first. Also as member BigBot96 stated why one would remove the PATH variable in post#13, it calls the .EXE through that location first as it is the PATH via a

symlink

to the

JRE

bin folder. For those coming in here and not knowing, JDK (Java SE Development Kit) includes a complete JRE plus tools for developing, debugging, and monitoring Java applications. So all you need in the PATH variable is just the JDK unless you use both JDK 7 and/or 8. In this case set which one you want at the time. You can have both installed if you so desire, just set them accordingly.

Examples at the bottom:

Examples ( do not copy and paste to your system ):

[COLOR=Olive]#1[/COLOR]( [COLOR=DarkOliveGreen]32-bit Operating System[/COLOR] )
........;C:\[COLOR=DarkOliveGreen]Program Files (x86)[/COLOR]\Java\[U]jre[/U]1.7.0\bin;C:\[COLOR=DarkOliveGreen]Program Files (x86)[/COLOR]\Java\[U]jdk[/U]1.7.0\bin;C:\Windows\System32\;C:\Windows\;C:\Windows\System32\Wbem...........
or
[COLOR=Olive]#2[/COLOR]([COLOR=DarkRed] [COLOR=DarkSlateBlue]64-bit Operating System[/COLOR][/COLOR] )
........;C:\[COLOR=DarkSlateBlue]Program Files[/COLOR]\Java\[U]jre[/U]1.7.0\bin;C:\[COLOR=DarkSlateBlue]Program Files[/COLOR]\Java\[U]jdk[/U]1.7.0\bin;C:\Windows\SysWOW64\;C:\Windows\;C:\Windows\SysWOW64\Wbem...........

[COLOR=Olive]#3[/COLOR] ...[B]C:\ProgramData\Oracle\Java\javapath[/B];...........;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files\Java\jre1.7.0\bin;C:\Windows\System32\Wbem...........

Pictures of the #3 example in code right above:

(

ProgramData

is a hidden folder)

(Right Clicking on one of them and then clicking on

Open File Location

shows you where it's located)

(Located in the JRE folder)

Just clarifying and helping any Devs/Contributors to relieve the problem with the JAVA situation..........
[Android Software/Hacking General [Developers Only]] SavanTorian:
why we have to use java 7, if theres java 8 already.... please update your stuff too.

java 7 is old and outdated.
[Android Software/Hacking General [Developers Only]] purian23:
Geesh dude that sounds a little harsh. It'll be awesome if he puts out another release at all since he put in the OP Development stopped BC he has personal time to tend too and real life work. Plus he put this out Free! ..for us.!

Other than that most likely a ROM you've ran or are running now was built with Java JDK 7 because this is what Google is still recommending on it's developer page. I'm sure they'll push Java 8 soon enough.

Lastly, Joel's work here has been Open Sourced to anyone and everyone to build and or contribute. Feel free to lend a hand.

I'm not trying to be rude, it's just not cool to see posts like this.
[Android Software/Hacking General [Developers Only]] mikeyxda:
I think it's doubtful that Java 7 versus 8 will make any difference WRT this tool being able to deodex. 2.4 works fine with Java 8 even if you pull oat2dex.jar from the 2.5 beta, so I think the problem(s) with 2.5 beta are something outside the realm of the Java version being used. What we really need is an updated oat2dex.jar because ultimately, that tool is what determines success/failure in deodexing more than anything else. Right now, oat2dex.jar is about 99% but it still needs a tweak or two in order to make it compatible with all the apk's and jar's out there. The latest version still has misaligned fields in some cases which causes the deodexed versions to crash (as I posted in my previous details).

Mike
[Android Software/Hacking General [Developers Only]] purian23:
I haven't had Successfully Booted ROM yet that is deodexed! No clue how you and Scott did it for the Stock N6 5.1 Roms. I have been able to get Odex going though. So yes, ultimately the oat2dex.jar is the most valuable. Not Java versions (at this point).
[Android Software/Hacking General [Developers Only]] DarkAngel:
Yes, so true. The path is what is important in Java and that is an easy fix as stated before and not the major concern at the moment.
[Android Software/Hacking General [Developers Only]] mikeyxda:
It was a painful process, at least the first time. It involved going through the deodexed version and finding the jars where oat2dex.jar failed, and replacing those with working equivalents from the AOSP builds (for the framework) or play store (for other apps). As of the last build, the main two that stopped it from booting were services.jar and framework.jar: those do not deodex properly with oat2dex.jar: even the most recent version. So those have to be replaced with the AOSP versions which are already deodexed. The AOSP versions are identical in every way: except without the deodexing errors. I decompiled and compared them to be sure!

Mike
[Android Software/Hacking General [Developers Only]] purian23:
Wow dude you aren't kidding that was painful! Our N6 Community certainly appreciated it! I have a similar setup to where I just compiled a new AOSP build today to see the raw files, plus skewering through the stock images. Thank you for pointing me in the right direction and as usual, you both did/do fantastic work with your ROMs!

Thanks again for this valuable input as 5.1.1 should be dropping soon too :eek:
[Android Software/Hacking General [Developers Only]] ticktock666:
used jre7u76 and the beta now works

just curious though : I've used the app to deodex the same rom files multiple times, but when comparing the md5 of the resulting files they are never the same, is this normal ? shouldn't the resulting files always be identical? like when compressing the same file twice.
[Android Software/Hacking General [Developers Only]] purian23:
In theory they should be the same, but either way i'd read the last page or two here, it's possibly why you're having some issues. I'm sure they're trying to get it nailed down for us.
[Android Software/Hacking General [Developers Only]] joeldroid:
Version 2.5 is out...

version 2.5 is out, please see the change log.
[Android Software/Hacking General [Developers Only]] Prior_Ori:
version 2.5-now everything is in order. Thank you.
[Android Software/Hacking General [Developers Only]] mikeyxda:
Yep. Works fine with Java 8 too. Only thing we need is an updated oat2dex.jar since that still fails on a few files. We need _riddle for that but not sure if he comes around here. He has 7 posts since December so this may not be his main hangout.

Mike
[Android Software/Hacking General [Developers Only]] PaulPizz:
Tool works great now on the update 2.5. Thanks! !!!
[Android Software/Hacking General [Developers Only]] carl1961:
[MENTION=4482551]joeldroid[/MENTION]

confirmed working Great
[Android Software/Hacking General [Developers Only]] tomkins0752:
Thanks for continuing to work with this man! :good:
[Android Software/Hacking General [Developers Only]] nico21311:
boot.art &amp; boot.oat

hello

I tried the tool on the ROM Samsung for G901F. During the tool process all work well. But when I create the zip file, the size of zip pass 1,1 GO to 980 mo. I tried to install with this file but the installation is block on the Samsung logo.

I checked the original file with the new one. and I found that both file is missing "boot.art & boot.oat". The both file are on \system\framework\arm folder. I trying to add the both file manualy with the folder arm and on the root in same time but the installation since the begining of reboot

Do you think are normal ? and the ROM doesn't work for an other reason ?

Thanks in advance for your answer.
[Android Software/Hacking General [Developers Only]] mikeyxda:
boot.oat and boot.art need to be removed after deodexing. Not only are they no longer needed, but if you put them in place, the system will actually use the odexed versions of the framework files in boot.oat instead of the deodexed ones that were created with this tool. I think it's more likely that oat2dex.jar just produced one or more invalid deodexed files. That happens on a few files. You'd have to do some research on that particular device to see which ones didn't deodex properly but I bet there's at least one that didn't. Sometimes you can pull a logcat while the device is booting even though it didn't complete booting: look in there and you might get an idea which jars/apks are throwing things like dexopt errors.

Mike
[Android Software/Hacking General [Developers Only]] nico21311:
Deodexer samsung rom G901F android 5.02

Thanks you for you explaination. The device is an galaxy S5+ (G901F) without QHD. The device is not really supported by lot of dev. So I try to make something to devellop it. I know one rom Deodexer for this device.

During the processing of Deodexer 2 or 3 task are faild.

Do you thinks it is the reason why the rom doesn't block on the samsung logo?

Just for information I try to deodexer the samsung rom android 5.02 : "http://xdaforums.com/galaxy-s5/development/rom-simplegx-rom-v1-0-0-t3072269"

Thanks in advance for your help.
[Android Software/Hacking General [Developers Only]] joeldroid:
thanks [MENTION=2712518]mikeyxda[/MENTION] for the reply I will add code to automatically remove the remaining boot.oat and boot.art

cheers
[Android Software/Hacking General [Developers Only]] joeldroid:
Thanks for the feedback everyone, your kind words and support are really good motivation...

Cheers.
[Android Software/Hacking General [Developers Only]] nico21311:
hello

For my case after the deodexing processing the file boot.oat and boot.art had been deleted by the tool directly. I just ask if it is normal. I search the reason why my rom deodexing not work.

the tool already delete these files.
[Android Software/Hacking General [Developers Only]] mikeyinid:
I have a Galaxy S6, the 920T and it runs fine but skips deodexing bluetooth and nfc. Why is it doing that?
[Android Software/Hacking General [Developers Only]] joeldroid:
it skips anything to which it cant find the odex file
[Android Software/Hacking General [Developers Only]] joeldroid:
ok thanks for clarifying that
[Android Software/Hacking General [Developers Only]] mikeyinid:
Yea I figured it out. Some of the odexed files are in arm not arm64. Renaming them gets them deodexed. Can't get it to boot though.
[Android Software/Hacking General [Developers Only]] nico21311:
application not deodexer

hello

rom android samsung 5.02

Please find the detail of file with a status fail below:

System\app

Maps.apk

SecEmail_K.apk

System\priv-app

SecGallery2014.apk

SHealth3_5.apk

System\Framework

Service.jar

What is the process to deodexer these file above ?

thank you in advance for your support.
[Android Software/Hacking General [Developers Only]] darkera13:
Hi mate, can you add a option to choose output folder, because i want keep original odexed folder.
[Android Software/Hacking General [Developers Only]] shahar2k9:
Sony Z3

Hey [MENTION=4482551]joeldroid[/MENTION],

Thanks for you great work!

I'm deodexing framework, app and priv-app from the 23.1.a.0.726 ROM for the Xperia Z3.

after i replace it with the odex one, i get Force Close for Google play service and Play store.

clean cache, art, and data does not help.

any idea how to fix?

Thanks.

* request - can you add for the batch the vendor folder as well?

* suggestion - change this thread into DEVDB.

Best,

Shahar.
[Android Software/Hacking General [Developers Only]] joeldroid:
Ok just to clarify, I did not make this deodexing core tool, this is just a batch tool to deodex bunch of apks for convenience. Asking me to fix an issues which might be due to an issue in the core oat2dex.jar will be pointless as it is made by [MENTION=6258761]_riddle[/MENTION] and I don't have access to his codebase.

But when I deodex, I kind of follow some simple rules, I do not deodex any third party apps like, google, samsung, dropbox, flipboard etc. coz they have a tendency to fail or force close after flash as sometimes they do not adhere to proper structure.
[Android Software/Hacking General [Developers Only]] joeldroid:
In fact I'm working on that...

Yes that is a good idea, but the way I have coded this, needs some modification and it will take some time.
[Android Software/Hacking General [Developers Only]] nico21311:
golden rules to deodexe a samsung rom

hello

Could provide us some recommendations to deodexer correctly a samsung rom ?

Thanks in advance.
[Android Software/Hacking General [Developers Only]] bdorr1105:
Great tool successfully deodexed my Note 4 Dev edition thanks
[Android Software/Hacking General [Developers Only]] s5610:
Error :(

Windows 8.1 x64, LBD2.5 (run as Administrator), Java 8, Android 5.1.
[Android Software/Hacking General [Developers Only]] :
U need x86 (32) to make it run properly
[Android Software/Hacking General [Developers Only]] s5610:
Have made fresh installation of my old Windows 7 SP1 x86 system with all whistles and bells and stuff:

Result is the same (

23-04-2015:21-06-12 => Framework Folder Exists

23-04-2015:21-06-12 => boot.oat Exists

23-04-2015:21-06-12 => App Folder Exists

23-04-2015:21-06-12 => Priv-App Folder Exists

23-04-2015:21-06-12 => Deodexing Started

23-04-2015:21-06-12 => Extracting Boot.oat

23-04-2015:21-06-12 => Copying Boot.oat to Working Directory - SUCCESS

23-04-2015:21-06-15 => Boot.oat Extraction Failed

23-04-2015:21-06-15 => Deodexing Failed

When deinstall Java 7 (to not confuse the app with double Java) - it fails. Deinstall Java 8 - fails. It fails on 64 bit, 32 bit, Windows 7 and Windows 8. I think problem is with this app, or my firmware. It's 5.1 test for Moto X Gen 1, dumped and checked for work on device. Won't deodex (
[Android Software/Hacking General [Developers Only]] ticktock666:
just install a new version of the google play services, I had the same problem on the Z2, so I updated the google play services then flashed the deodexed files and the erros didn't show up, or you can leave "gmscore" odexed, either way it works.

The problem with the sony devices is with the openGL drivers, Like [MENTION=2712518]mikeyxda[/MENTION] said, the problem is with oat2dex.jar processing services/framework jars, somehow messing them up and resulting in a broken rom, hopefully [MENTION=6258761]_riddle[/MENTION] will fix this soon
[Android Software/Hacking General [Developers Only]] s5610:
Installed latest, system dump, make_ext4fs unpack, get in v2.5 - didn't go any furher (

joeldroid, will you help me, please? Is my Motorola cursed? )
[Android Software/Hacking General [Developers Only]] joeldroid:
Hi,

I have no way of testing this with the multitude of devices out there.

I have a s5 and I can confirm it is working with s5 and so many other devices out there which the users have confirmed working, I have no way of checking for motorola.
[Android Software/Hacking General [Developers Only]] balla48801:
How do you go about leaving files out from being deodexed? Just cut the folder/files before deodex and copy back after? Is there anything else that needs to be left. I am struggling trying to figure out why im getting google play services has stopped working on note 4.
[Android Software/Hacking General [Developers Only]] IgorEisberg:
Deodexer works perfectly for Lollipop releases of Xperia Z1/Z2/Z3 but fails with Xperia C3 and Xperia T2 Ultra.

Very odd.
[Android Software/Hacking General [Developers Only]] DorianX:
Can you share deodexed .zip for Xperia Z1? Please. There's 2 deodexed .zips on Z1 forum but have some issues with Google Apps and Opengl
[Android Software/Hacking General [Developers Only]] Nimadroid:
It's work with Sony z ultra lollipop 14.5.A.0.242????
[Android Software/Hacking General [Developers Only]] bajasur:
[MENTION=4482551]joeldroid[/MENTION]

Is anyone else noticing that after using this deodex tool they still have 2 odex files in every arm folder withing app and priv-app?

Thanks
[Android Software/Hacking General [Developers Only]] :
It seems like thus apps that has two different arm folders will fail

arm

and arm64 in same app folder fails

ETC

G4 (Airdrive)

Has two folders with odex

arm/LGAirDrive.odex

arm64/LGAirdrive.odex
[Android Software/Hacking General [Developers Only]] jazzespresso:
From my personal experience, this tool always fails, that's because each device's lollipop setup so diffrent, so it will hard to create an universal lollipop deodexer unless this tool's developer takes into all possiblities into his code, it may work.

In addition, I actually have more success using Oat2dex convertor on windows, I know this one is manual process, but it always works since you manually control what to deodex, etc.

and like you said, having arm and arm64 folder, what I know is that if it has two folders, it looks like it is backward compatibility, means that app can work on both kitkat (4.4.X 32bit) and lollipop (5.x 64bit). I have tested this couple times, for example if I want to use that app on Samsung's kitkat 4.4.X ROM, I use odex file under arm folder to deodexed....it works like 90% of time....
[Android Software/Hacking General [Developers Only]] tomkins0752:
This tool actually works out great if you have it deodex the 32 bit files separately from the 64 bit.

It takes two passes because of that, but it works flawlessly.

Now I just need to find/make an update script that will let me flash the new files without error...
[Android Software/Hacking General [Developers Only]] quinielascom:
This utility seem works fine, but i have a question, how flash to my device the system deodexed folder?

Thanks.
[Android Software/Hacking General [Developers Only]] garynych:
has anyone tried this tool on android 5.1, and 5.1.1 ,is there any chance to get work files ? or not ? previously, the android 5.1 processing to complete successfully,but after installation the device back,it is no longer loaded so the program does not work correctly with android 5.1 Ari this with an older all is fine:confused:
[Android Software/Hacking General [Developers Only]] :
It should work just as it does on Android 5.1.0 procedure hasn't changed just updated the Android version and comes with some new stuff. Procedure uses all files that you have in bin and framework
[Android Software/Hacking General [Developers Only]] rrajesh:
[MENTION=4482551]joeldroid[/MENTION] Bro!! Not working for Xperia T2 Ultra (5.0.2)