Where is classes.dex

Starting from version the format additionally allows space characters Unicode Zs category. A MemberName is the name of a member of a class, members being fields, methods, and inner classes. A FullClassName is a fully-qualified class name, including an optional package specifier followed by a required name.

A TypeDescriptor is the representation of any type, including primitives, classes, arrays, and void. See below for the meaning of the various versions. A ShortyDescriptor is the short form representation of a method prototype, including return and parameter types, except that there is no distinction between various reference class or array types.

Instead, all reference types are represented by a single 'L' character. This section includes definitions for each of the top-level items that may appear in a. The format of the data pointed at is left unspecified by this document; this header field and the previous are left as hooks for use by runtime implementations. Must be an even multiple of sizeof uint. A given type must appear at most once in a map, but there is no restriction on what order types may appear in, other than the restrictions implied by the rest of the format e.

Additionally, the map entries must be ordered by initial offset and must not overlap. It is up to higher-level uses of strings to reject such invalid encodings, if appropriate. Any additional arguments are constant values passed to the bootstrap linker method. These arguments are passed in order and without any type conversions. The method handle representing the bootstrap linker method must have return type java.

The first three parameter types are: java. Lookup java. String java. MethodType The parameter types of any additional arguments are determined from their constant values. This list should not include inherited methods unless overridden by the class that this item represents. The state machine consists of five registers. The line register represents what source line number should be associated with the next positions table entry emitted by the state machine. It is initialized in the sequence header, and may change in positive or negative directions but must never be less than 1.

Note: See the discussion under " dalvik. Signature " below for caveats about handling signatures. Opcodes with values between 0x0a and 0xff inclusive move both the line and address registers by a small amount and then emit a new position table entry. The formula for the increments are as follows:.

The list of flags described below may be extended in the future releases of Android. For more information, see restrictions on non-SDK interfaces. System annotations are used to represent various pieces of reflective information about classes and methods and fields. This information is generally only accessed indirectly by client non-system code. System annotations are represented in. AnnotationDefault appears on methods in annotation interfaces An AnnotationDefault annotation is attached to each annotation interface which wishes to indicate default bindings.

An EnclosingClass annotation is attached to each class which is either defined as a member of another class, per se, or is anonymous but not defined within a method body e. Every class that has this annotation must also have an InnerClass annotation.

Additionally, a class must not have both an EnclosingClass and an EnclosingMethod annotation. An EnclosingMethod annotation is attached to each class which is defined inside a method body. An InnerClass annotation is attached to each class which is defined in the lexical scope of another class's definition. Any class which has this annotation must also have either an EnclosingClass annotation or an EnclosingMethod annotation. A MemberClasses annotation is attached to each class which declares member classes.

A member class is a direct inner class that has a name. Note: This annotation was added after Android 7. Its presence on earlier Android releases will be ignored. A MethodParameters annotation is optional and can be used to provide parameter metadata such as parameter names and modifiers. The annotation can be omitted from a method or constructor safely when the parameter metadata is not required at runtime.

When including parameter metadata, compilers must include information for generated classes such as enums, since the parameter metadata includes whether or not a parameter is synthetic or mandated. A MethodParameters annotation describes only individual method parameters. Therefore, compilers may omit the annotation entirely for constructors and methods that have no parameters, for the sake of code-size and runtime efficiency. MalformedParametersException will be thrown at runtime.

Because MethodParameters describes all formal method parameters, even those not explicitly or implicitly declared in source code, the size of the arrays may differ from the Signature or other metadata information that is based only on explicit parameters declared in source code. MethodParameters will also not include any information about type annotation receiver parameters that do not exist in the actual method signature. As such, signatures are not generally parsed or verified by virtual machine implementations.

The signatures simply get handed off to higher-level APIs and tools such as debuggers. Any use of a signature, therefore, should be written so as not to make any assumptions about only receiving valid signatures, explicitly guarding itself against the possibility of coming across a syntactically invalid signature.

Because signature strings tend to have a lot of duplicated content, a Signature annotation is defined as an array of strings, where duplicated elements naturally refer to the same underlying data, and the signature is taken to be the concatenation of all the strings in the array. There are no rules about how to pull apart a signature into separate strings; that is entirely up to the tools that generate. You could also use tools ApkOneClick or ApkMultiTool to get Java source from the smali files but these would probably not be perfect and will require further fixing.

When you change the code you want you should build the classes. Note that then existing certificate files META-INF will not be valid anymore and you will need to delete this folder and resign the apk package in order to instal it on the phone or emulator.

Python Javascript Linux Cheat sheet Contact. Role of classes. I have questions about android apk file. I could find classes. If I can not find classes. Can the apk start without classes. Thank you. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Where is classes.

Our Dex file defines three Java types. Therefore, we can determine that the types in our file are as follows:. The TypeDescriptor syntax may look somewhat unfamiliar, but the L simply refers to a full class name, and V is the type void. Our types include our custom BugsnagApp class, and the Application class from the Android framework. A method prototype consists of information on the return type of a method and the number of parameters it takes.

The Method section also uses indices. Each method looks up the class ID where it was defined, the method prototype, and the name of the method from the strings table. This section contains the type, inheritance hierarchy, access metadata, and other class metadata such as annotations and source file indices. The public access modifier is determined from a bit field. The first four bytes of our BugsnagApp class data define the number of static and instance fields, along with any direct or virtual methods.

There is only one direct method defined in this class. If our class defined fields and other information, more data would be encoded in this section. Incidentally, if the method ID was a value larger than 65,, we would have encountered the infamous 64k method limit.

This corresponds to a register size of 1, 0 incoming arguments, outgoing arguments, and an offset of 16 where debug information is stored. The most important part, however, is the last few bytes.

We have an instruction list size of 1, which means that our method has compiled to one opcode: The Dalvik Bytecode table suggests that 64 corresponds to the sget-byte operation on a register, using the field reference index of 1. This seems to match up with our expectation that a singleton BugsnagApp field will be created for our application — but diving deep into Dalvik is a story for another day!

We can retrieve classes. Our Dex file is approximately 88 percent of its previous size when compiling with D8.