[Release] xUltimate

[xeudoxus]

Running into an issue DeOdexing the ROM from my Thunderbolt. It doesn't even get past the first jar in system/framework. This is the error it's giving:

Attachment 39626

Any ideas?

It looks like it's trying to load a class path of com.htc.app.HtcListActivity, but I don't have any jar or odex files with that name. Furthermore, at the very bottom of the error, it says it's looking for said bootclasspath from the following string: .\origi.frame\com.htc.framework.zip

Once again, I failed to find a zip file named com.htc.framework. I am extremely confused at this point.

Any help would be greatly appreciated!

Send me the rom/dump and ill fix it.

[xeudoxus]

Running into an issue DeOdexing the ROM from my Thunderbolt. It doesn't even get past the first jar in system/framework. This is the error it's giving:

Attachment 39626

Any ideas?

It looks like it's trying to load a class path of com.htc.app.HtcListActivity, but I don't have any jar or odex files with that name. Furthermore, at the very bottom of the error, it says it's looking for said bootclasspath from the following string: .\origi.frame\com.htc.framework.zip

Once again, I failed to find a zip file named com.htc.framework. I am extremely confused at this point.

Any help would be greatly appreciated!

Fixed in version 2.2.9, but you will still run into problems deodexing 1 file "VzwLBSPerm.odex" from what I can tell, it is corrupted and should be deleted (Look at it with a hex editor, it does not even resemble a .odex file).

-Matt

[frantorm]

Your work is awesome! Thanks!!

[xeudoxus]

Hello my friend, thanks for your work, this is my error, can you help me?

Thanks!

Might be a problem with smali/baksmali, send me a link to the rom/dump and ill check it out.

[xeudoxus]

Hello my friend, thanks for your work, this is my error, can you help me?

Thanks!

Done, download xU v2.3.0 (It will deodex 100%, but I dont know if there will be problems or not when you actually run the rom "Let me know")

-Matt

[Boostjunky]

Fixed in version 2.2.9, but you will still run into problems deodexing 1 file "VzwLBSPerm.odex" from what I can tell, it is corrupted and should be deleted (Look at it with a hex editor, it does not even resemble a .odex file).

-Matt

Thank you kindly, sir!

[Boostjunky]

OK, so I went to give this a go with v2.3.0, and while we have progress (it actually begins the deodexing process as opposed to before the update) I'm running into another error with one of the system apks. It's EPST.apk/odex.

Here is the error it's spitting out:



Any ideas?

Thanks again!

[xeudoxus]

OK, so I went to give this a go with v2.3.0, and while we have progress (it actually begins the deodexing process as opposed to before the update) I'm running into another error with one of the system apks. It's EPST.apk/odex.

Here is the error it's spitting out:



Any ideas?

Thanks again!

I just tested again and its working 100% for me, make sure that there are no problems.

Make a new dir for xUltimate (c:\xu23\) and extract v2.3.0 into that folder.
Make sure you have "javax.annotation.jar" in the c:\*\jar\ folder.

-Matt

[arhtard]

hi there
i would like to thank you for this program before i begin
i have encountered a problem using test.exe
Main ADB
Android Debug Bridge version 1.0.26
****
PATH ADB
****
[ro.build.id]: [FROYO]

[ro.build.display.id]: [FROYO.UVKE7]

[ro.build.version.incremental]: [UVKE7]

[ro.build.version.sdk]: [8]

[ro.build.version.codename]: [REL]

[ro.build.version.release]: [2.2.2]

[ro.build.date]: [Thu May 19 22:29:39 KST 2011]

[ro.build.date.utc]: [1305811779]

[ro.build.type]: [user]

[ro.build.user]: [se.infra]

[ro.build.host]: [SEP-42]

[ro.build.tags]: [release-keys]

[ro.build.PDA]: [T589UVKE7]

[ro.build.hidden_ver]: [T589UVKE7]

[ro.build.changelist]: [1011308]

[ro.build.buildtag]: [jenkins-HUDSON_USA_GSM_JOYCEQ_FROYO-HW01-USER-587]

[ro.build.product]: [SGH-T589]

[ro.build.description]: [SGH-T589-user 2.2.2 FROYO UVKE7 release-keys]

[ro.build.fingerprint]: [samsung/SGH-T589/SGH-T589/SGH-T589:2.2.2/FROYO/UVKE7:user/release-keys]

****
****
-Windows x86-
-adb pull- **PASS**
-odex- **PASS**
-7z- **PASS**
-busybox- **PASS**
-java- **PASS**
-temp- **PASS**
-deodex- **FAIL**

i opened the frame.dep.txt and app.dep.txt in /jar and added my devices bootclasspath in both of these and still return the deodex fail message.
any suggestions for me?

[xeudoxus]

hi there
i would like to thank you for this program before i begin
i have encountered a problem using test.exe
Main ADB
Android Debug Bridge version 1.0.26
****
PATH ADB
****
[ro.build.id]: [FROYO]

[ro.build.display.id]: [FROYO.UVKE7]

[ro.build.version.incremental]: [UVKE7]

[ro.build.version.sdk]: [8]

[ro.build.version.codename]: [REL]

[ro.build.version.release]: [2.2.2]

[ro.build.date]: [Thu May 19 22:29:39 KST 2011]

[ro.build.date.utc]: [1305811779]

[ro.build.type]: [user]

[ro.build.user]: [se.infra]

[ro.build.host]: [SEP-42]

[ro.build.tags]: [release-keys]

[ro.build.PDA]: [T589UVKE7]

[ro.build.hidden_ver]: [T589UVKE7]

[ro.build.changelist]: [1011308]

[ro.build.buildtag]: [jenkins-HUDSON_USA_GSM_JOYCEQ_FROYO-HW01-USER-587]

[ro.build.product]: [SGH-T589]

[ro.build.description]: [SGH-T589-user 2.2.2 FROYO UVKE7 release-keys]

[ro.build.fingerprint]: [samsung/SGH-T589/SGH-T589/SGH-T589:2.2.2/FROYO/UVKE7:user/release-keys]

****
****
-Windows x86-
-adb pull- **PASS**
-odex- **PASS**
-7z- **PASS**
-busybox- **PASS**
-java- **PASS**
-temp- **PASS**
-deodex- **FAIL**

i opened the frame.dep.txt and app.dep.txt in /jar and added my devices bootclasspath in both of these and still return the deodex fail message.
any suggestions for me?

The deodex on the test fails, the Test.exe is old. The main thing to look at is the java and it passed, so you should be good to go (As far as deodexing). If you are having problems deodexing the rom/dump still then its prob a bootclasspath problem. If you send me a link to the rom/dump I can fix it for you.

-Matt