Related
Hi, I would like to De-Odex the rom I currently have on my phone.
Is there an easy way to do this?
I've read:
http://www.droidforums.net/forum/xeudoxus/47283-release-xultimate.html
and
http://www.droidxforums.com/forum/droid-x-themes/4620-how-manually-deodex-your-phone.html (there is also a post about this on here)
The xUltimate tool will not work for me, so I need another option.
Phone: HTC Evo
ROM: Stock 3.29 OTA
Rooted (ofc)
Thanks for the help.
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
TheMagicalSock said:
Sorry if this is no help, but a deodexed version of the 3.29 OTA is posted somewhere in the dev section. Is there a particular reason why you want to deodex it yourself?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I've been switching between roms but I keep coming back to my original stock one. It's still odex'd and I would like to theme the battery icon on the status bar without having to set everything back up on a fresh rom. Since it reads half when 80% of my battery is remaining.
Thanks for the quick response.
Sent from my Evo using XDA App.
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Max_Pain said:
and you said this didnt work for you?
i didnt even know you could deodex your own rom!
going to try this soon!
Click to expand...
Click to collapse
It wasn't that it didn't work.
I just got an error with Java, not sure how to fix it. Some said to re install java, but i've installed JRE and JDK from 5u20 to 6u21 (32 and 64 bit). Everything I tried gave the same error.
I am going to try asking on their forum and see if they can tell me what I did wrong.
I have a feeling it has to do with the 3.29 OTA update. :-/
Good luck and if you get it to work please let me know your setup.
and if you can't run step 3 let me know... that way I am not the only one to seem that crazy.
option 1 and 2 just adb pulls your /system/apps and your framework.
just got stuck starting option 3:
Starting AccountSyncManager.odex
*Deodexing...
Error occurred while loading boot class path files. Aborting.
org.jf.dexlib.Code.Analysis.ClassPath$ClassNotFoundException....
lower it says
at org.jf.baksmali.baksmali.dissambleDexFile(baksmali.java:103)
and it just gives some more errors until i close it down
i was sooo excited to get this done!
Ahhh! I'll see what I can find out on their forums.
Despite the tutorial saying "Manually De-Odex Your Phone" I think it may be just for droid phones. It was posted in the Moto Droid sections of the forums.
Here is the error I was getting:
Code:
Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.NullPointerException
at java.util.Properties$LineReader.readLine(Unknown Source)
at java.util.Properties.load0(Unknown Source)
at java.util.Properties.load(Unknown Source)
at org.jf.baksmali.main.<clinit>(main.java:69)
Could not find the main class: org.jf.baksmali.main. Program will exit.
Press any key to continue . . .
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Max_Pain said:
dang it...
i just updated my java and nothing, still same error. well let me know what they say. i was about to make an account to post over there but i'll let you do it then.
keep me updated!
Click to expand...
Click to collapse
If you want to add anything my post is located:
http://www.droidforums.net/forum/xeudoxus/85223-xultimate-errors.html
Both our problems have "org.jf.baksmali" involved.
Hopefully we'll have some answers soon.
well i ran a test and everything said pass, including the odex and deodex. i installed the latest java, and same problem. i had the phone originally as mass storage, so i tried under charge only, and still same problem.
i really hope we get a solution to this
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Max_Pain said:
I did some more reading and it seems that app is designed specifically for droid x phones.
I'm now going to try a more hands on approach using avabox...will update tonight.
Swyped from an HTC Evo on MetroPCS...
Click to expand...
Click to collapse
Were you able to get it DeOdexed?
I found this after some searching... It seems to be the LONG way to deodex an apk. It was written in 2009 so idk how reliable it will be.
http://androidnetwork.org/forum/viewtopic.php?f=11&t=55
Edit: Link to Avabox: http://forum.xda-developers.com/showthread.php?t=697459
[UPDATE] I tried Avabox and it de-odexed all of the files that I adb pulled. I copied the De-Odexed files back to their respective folder on the /system/, and deleted "rm /system/app/*.odex" (Removing all the .odex files) and rebooted.
I got stuck on the white "HTC Evo 4G" screen and could not get passed it.
I am not sure what I messed up. Maybe I need to resign the files? I'll try that tomorrow.
Let me know how your attempt went. :]
When I left for school I left the script deodexing my app folder...it seems to have done the job and there were no errors. It's doing the process for the framework files now.
Once I move it over to the phone we 'll see if it worked...
I'll update here when I find out...
Swyped from an HTC Evo on MetroPCS...
i just tried that too and i got stock in a bootloop.
the avabox script does deodex all the app files. it doesn't do that for the framework files...it seems it'll only deodex .apk files.
anyways, i deleted everything from my /system/app folder and then pushed over the deodexed apks...i also did this for the two apk files from system/framework and the phone did the bootloop thing. so i put back the original /system/framework files, effectively only leaving changed the contents of /framework/app/ and still, bootlooping.
i'm restoring right now...i'll try it some more at another time.
let me know if you figure it out!
I was reading some of the comments on this thread(http://forum.xda-developers.com/showthread.php?t=598026) They we're saying about problems with de-odexing the framework.
Do we need to resign system apps before we push them back?
I am optimizing my apks now, going to batch resign then try putting just the apks back on.
Well I messages avalaunchmods asking the same thing...if anyone knows it should be him...
Update if you get it working please!
Swyped from an HTC Evo on MetroPCS...
Unfortunately, I still don't have any good news. :[
I tried resigning the de-odexed apk's and replacing the ones on my phone.
This got stuck at the white HTC Evo 4G screen.
This failed
Then I optimized, signed, and zipaligned.
This threw me into an actual boot loop. (I was excited... It's the first boot loop i've gotten.)
This failed.
Here is some semi-less-bad news.
I used http://circle.glx.nl/ to make a flashable update.zip for theme-ing. I Flashed it with success and was able to get to the lock screen. Sense UI along with just about every other system app kept force closing.
But I was able to successfully (even though I got FC's) theme and boot using that kitchen.
I am going to mess around with the different settings there and see if I can atleast theme my phone.
Any luck with your attempts?
i was at school all day - no news from me. this is very discouraging though.
i'm surprised nobody else has chimed in! considering how many people are making and releasing roms, some people must know what's going on here
Good news (kinda)
I was able to theme my framework-res.apk without any errors or FC's.
I didn't do anything to De-Odex it but it accepted the theme when I manually edited it.
There must be an xml that scripts how the battery is displaying %'s
since I have 89% of my battery remaining but the themed battery is showing 80%.
I'll dig around and see where it is and add it to my next framework recompile.
We're you interested in just themeing or the whole de-odexing (apps & framework)
If you want to theme it i'll write up a decent tutorial on what I did.
If not I'll write up a quick tutorial for the next root newbie who wants to theme.
Going to test run it and make sure I didn't mess much up.
Edit3: The bad, it would appear that you can't modify the .xml's of the framework. You can only change the pictures.
So the battery wont be able to have the exact %.
Modifying of any .xml leads me to a boot loop.
Tips are appreciated on fixing this.
I'll keep trying.
so here is what i've learned.
i had modified both .com.htc.resources and framework-res before. those files, at least in my rom, are not odexed. everything else in the framework folder is a mix of files, .jar files and other formats, including services.jar, which is odexed. that's why if we change the services.jar file, without the phone being deodexed, it wont work.
that's why i want to deodex my rom. i have too many changes already and dont want to re-do them in another, deodexed rom.
my main interest in deodexing the rom is to have the working battery percentage on top (which used to work on THIS rom before, without deodexing???) and to have a transparent notification tray.
and from there being able to make any other changes as they come up...
i'll see when i have some more time to try out other options, but chances are you will have time before me, so keep updating!
Hey everybody. First time posting. Ive searched and searched and searched the forums but cant seem to find the answer i need. I have a rooted Verizon Gnex running stock 4.1.1. When the factory image for 4.2.2 was finally released, i DL'd is and tried to run the .zip. Only to find that it was erroring out. I decided to wait VZW pushed the official OTA update and try that. Well, it finally came through last night and, i wish i could say to my surprise, the same issue happened. After scouring the interwebs, the only thing i could find to fix it was to unroot my device. Now if that is the case, then so be it. But if i can avoid wiping my device, i would love that option far more. I also am attaching a pic of the error message that im receiving when i try and update.any help or advice would be greatly appreciated. Thanks in advance!
you modified your build.prop
the error message even says thats the problem.
you need the stock build.prop to be able to take the OTA.
The error tells you what is wrong, it detects something different about your build.prop file. You need to get it back to stock.
E2A: I am redundant, and slow.
Zepius said:
you modified your build.prop
the error message even says thats the problem.
you need the stock build.prop to be able to take the OTA.
Click to expand...
Click to collapse
Thank you for such a quick response!!!!! Is there someplace that i can DL that and, if so, how would i go about installing it to the phone? Would it be a simple drag and drop?
Thanks again so much
ibouchillon said:
Thank you for such a quick response!!!!! Is there someplace that i can DL that and, if so, how would i go about installing it to the phone? Would it be a simple drag and drop?
Thanks again so much
Click to expand...
Click to collapse
the easiest way to fix your problem is to just flash the system image and nothing else in fastboot. there are several guides on how to do this.
if you want to find a download for the build.prop and change the permissions, you're welcome to try and find it.
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
ik4evr said:
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
Click to expand...
Click to collapse
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
THEDEVIOUS1 said:
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
ik4evr said:
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
Click to expand...
Click to collapse
If that didnt work then it might be your updater-script...once again just copy the one from a known working deice with an exynos cpu & 4.4.2 (N9000 MAYBE?) then u should be ok. Also...did u swap the daemonsu file in xbin as well? Another thing...delete the su located in "bin" & make sure its in "xbin". The last thing i can think of...did u unpack the boot.img & change the value in the dfault.prop to make it non-secure?
edit: I was just thinking...i noticed u said "supersu" but every guide ive seen added "superuser" instead so swap that too. U should be able to include either but mine didnt work either until i switched them although it could have been coincidence since i also made all of the rest of the alterations around the same time...if u notice in my thread i told users to go download supersu AFTER they flash just to be safe but now that i have it working i'll probably try changing apps again for the next version to eliminate a step
where do I dl twrp for tab pro 10.1 wifi?
I only see 10.1 tab pro lte ...not wifi?
Thanks
Could someone hook me up with an untouched copy of lg framework apk and framework apk por favor??
C'mon someone else besides me has to be still running stock.. It is a very easy copy and upload, please help a brother out.
Im sorry, I tried to be patient. I am pretty sure Ive helped more than a few people out around here. All Im asking for is about 5mins or less for someone to copy and upload these. I didnt screw anything up, just want to remove some mods I flashed a long time ago in which I no longer have a copy of.
Swizzle82 said:
Im sorry, I tried to be patient. I am pretty sure Ive helped more than a few people out around here. All Im asking for is about 5mins or less for someone to copy and upload these. I didnt screw anything up, just want to remove some mods I flashed a long time ago in which I no longer have a copy of.
Click to expand...
Click to collapse
Idk what your currently running, if its bone stock or what but you should be able to rip what you need from a rom download/. I unfortunately am running aosp or else I would help you in a heartbeat. There are alternate methods though!! good luck... also just came to mind, try pulling it from a nand or twrp backup.
Yeah I flashed these so long ago I dont have that backup anymore. Im pure stock as far as rom goes Im on 10m. I found some from 10c but its the framework and one thing you most definetly need the matching version of. I dont have my computer for a while so I cant return to stock and start over.
Thanks for the reply though.
Downloaded and extracted from zone rom.. All good now.
I've been poking around this morning trying to figure out why my phone keeps coming to a screeching halt every once in a while. We all know about this memory leak in pre 5.1 lollipop. Looking at github I tracked down ColorFade.smali in our firmware. I also found what needs to be changed to "fix" the issue. I made the edits for the regular S6 firmware which I'm almost positive you guys would be able to use as well. But, you have to be deodexed, or delete the services.odex files. I'll wait for some feedback from other FS6 owners, and if it's positive I'll get you guys fixed up too.
Forgive me as I am ignorant on the process, but I need to be rooted to delete services.odex files?
nviz22 said:
Forgive me as I am ignorant on the process, but I need to be rooted to delete services.odex files?
Click to expand...
Click to collapse
I believe so.. You'll need a file explorer with root access to edit any system files.. Root explorer is my favorite
Very interesting. Wanna see how this develops
mikeyinid said:
I've been poking around this morning trying to figure out why my phone keeps coming to a screeching halt every once in a while. We all know about this memory leak in pre 5.1 lollipop. Looking at github I tracked down ColorFade.smali in our firmware. I also found what needs to be changed to "fix" the issue. I made the edits for the regular S6 firmware which I'm almost positive you guys would be able to use as well. But, you have to be deodexed, or delete the services.odex files. I'll wait for some feedback from other FS6 owners, and if it's positive I'll get you guys fixed up too.
Click to expand...
Click to collapse
Would love to give this a try
Feedback has been good, unfortunately this only fixes one of the problematic memory leaks in lollipop.
I could use it? Atleast one is fixed