How to go back to defaults but stay rooted... - EVO 4G Android Development

I want to go back to the ORIGINAL DEFAULT most up to date 2.1 version but stay rooted, is this possible?
I am on Fresh 0.3
Thanks!

http://wiki.xda-developers.com/index.php?pagename=HTC Evo ROMs

Stock (1.32.651.6) with root. Deodex and odex available (06/10/2010)
What does deodex and odex mean?
This is the correct file I am looking for right?

By TrevE from the DamageControl ROM post:
Deodex basically takes the odex file and stuffs it into the apk as a classes.dex. First boot it dissembles the file into /dalvik-cache (i believe). Now there is basically 2 copies of the odex, one in the apk one in cache. This makes it "portable". This allows modders to work on the apks & easily change stuff. If you want themes or stuff like lockscreen fixes you MUST use Deodex.
Odex is how things come stock. It takes up less room but making modifications or taking apks from other roms is hard. You cannot use themes with this version!!
Click to expand...
Click to collapse

Related

Auto-Deodexer 2.3 [SCRIPT] [FROYO SUPPORT] [Devs Only]

Hey guys, so this script de-odexe's a rom's apks and jar's.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming. This is crzyruski script updated with jesus freke's latest smali/baksmali update ver 1.2.3
It incorporates detecting the bootclasspath of the odex instead of the user specifying it. For non standard odex however a specific bootclass path must be defined. For example:
According to Jr33 for rosie deodexing u have to add class paths com.htc.framework.jar. Thank him for the new Sense bootclasspaths
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
*New Menu added
*Ability to specify custom bootclasspath (eg for sense ui)
*Added a java check at the beginning
*Added 1.2.3 smali/baksmali with froyo support(thank jf ofcourse )
*Modified it so if an error is encountered during deodexing, it leaves that file behind so once done you know what files encountered errors
*Added Ignore Mode
*Removed zipalign
*If apk doesnt have corresponding odex, it moves it to deodexed_APK instead of user manually moving it
*Added compression level option
*You can monitor the status of ignore mode / compression level right above the main menu
DISCLAIMER:
Its a batch file so it'll only work on windows.
Convince farmatito to bring this to linux
Thanks
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
enomther said:
So I checked this out and all ...
It's only apk's, right?
I only glanced but I didn't see anything in there for framework, etc.
If I'm right, then perhaps .. you should just say it de-odex's a ROM's apk's instead of the entire ROM.
~enom~
Click to expand...
Click to collapse
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Daneshm90 said:
Oh, yea so it takes the apk and odex and creates the classes.dex and repackages into the apk so u only need the apk. Ok, ill change the post a bit also yes, it doesnt do frameworks cuz i dont think they have odex's and the jar's do but i dunno of a method to do tht
Click to expand...
Click to collapse
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
enomther said:
Yea ... the jar's have dex's too and can be odex-d and can also be un-odex-d. I personally have never been able to successfully de-odex a fully odex'd framework (but I haven't tried hard enough either ). The main difference is once they are de-odex'd ... you insert the classes.dex into the jar and no re-signing required (as they aren't signed).
Either way, nice script mate. Good Job!
~enom~
Click to expand...
Click to collapse
Ah sweet, something i shall incorporate in the script later on. thanx
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Joe333x said:
so will this script allow you to take an app from say a cliq dump and allow it to run on any android device?
Click to expand...
Click to collapse
Emm...no im 99.99% sure it doesnt help tht way. I know that odex's cause customization problems in roms....there are other factors im sure
mrandroid said:
Will this allow you to grab the MyFaves from a TMO rom and de-odex it and install?
Click to expand...
Click to collapse
MyFaves == No Go ... it requires some other form of trickery ... I'm not sure what exactly ... as I did de-odex it and it would not work properly on test-key ROM's like CM, etc.
... So it requires more than a simple de-odex.
~enom~
does your phone need to be connected? I noticed some ADB commands in the script
Daneshm90 said:
Hey guys, so this script de-odexe's a rom's apks.
Many thanks to ofcourse JesusFreke who created this method and the way to do it. Also to coolbho for his apkopt script from which i learnt certain techniques of batch programming
For those who dont know, this essentially uses jf's method of baksmali'ing the odex file into smali files, and then recreating the classes.dex file and packaging it into the apk hence disregarding the need for the odex.
Oh also make sure to place only apk's that have their corresponding odex's. Dont place only apk's !!!!!
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
1. Download http://www.mediafire.com/?mwownkhzm4m
2. Extract to a folder
3. Place all your rom's apk's which have odex's attached to them into that folder
4. Run deoall
5. Copy all the apk's from the deodexed folder into ur corresponding rom app folder
Thanks
Upcoming:
Seperate Framework & apps folder
De-odex framework apk's and jar's (thanx for the tip enomther )
Click to expand...
Click to collapse
So the apk after that has the DEX built in or is dexopt still needed?
wesgarner said:
So the apk after that has the DEX built in or is dexopt still needed?
Click to expand...
Click to collapse
>.<.......................
kingklick said:
>.<.......................
Click to expand...
Click to collapse
Hey I am just double checking
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
---edit---
shoot me for not reading.
Daneshm90 said:
Instructions:[WINDOWS ONLY & Phone Must stay connected with adb WORKING]
Click to expand...
Click to collapse
jubeh said:
If you're having problems de-odexing the framework is because there's a particular order to it.
If you look at your bootclasspath you'll see the framework files necessary to boot the android system, the rest (whatever's not in there) can be dexopted in any order.
If you're trying to de-odex the framework, you're going to have to backtrace yourself.
Personally, I do:
for i in /system/app/*.apk
unodex
for j in /system/framework/nonCoreJar1.jar /system/framework/nonCoreJar2.jar /system/framework/...nonCoreJarN.jar
unodex
for k in /system/framework/bootClassPathJarN.jar /system/framework/bootClassPathJarN-1.jar /system/framework/...bootClassPathJarN-y.jar
unodex
it requires a couple of reboots along the way to deal with any created dalvik-cache so that it doesn't interfere with the next needed classes.dex
the only turn-off was that it requires a running system to do it (it's not that big of a problem, but porting and then flashing starts getting old after a while).
Has that changed?
Does OP mean you can take the apks, toss them into a folder, and then do it from the computer without the phone?
Click to expand...
Click to collapse
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
enomther said:
Yea I would figure as much ... simply b/c one must follow the BOOTCLASSPATH order when odex'ing ...
So Jubeh .. you're saying you've personally de-odex'd an fully odex'd framework b4?
Just looking for confirmation from someone who has personally ... since I'm too lazy to go through that hectik crappy process
~enom~
Click to expand...
Click to collapse
I did it with the tattoo build, but upon boot I would get all sorts of fc's, but I think that was due more to a bad, hasty port than the deodexing. It was also a long time ago when the tool first came out, dont know if there's been newer revisions, so I'll try it again on that funky tattoo rom.
K guys one problem i found after doing multiple apk's is that i need to give the listening dex command a bit delay so its ready for baksmali. I was doing it right after which it misses for some conversions. I'll upload with delay between the two commands. Hmm framework i gotta give a shot :/ Sounds interesting ...
Solid script! Should make deodexing A LOT easier
Ok so i uploaded with delay between, seems to work fine, tested a LOT of times
thanks for this! can't wait for frameworks to be de-odexed.
jubeh: Thanks for the info. I had no idea and have informed JF previously here: http://jf.andblogs.net/2009/11/08/smalibaksmali-v1-0/ (see comments)

DeOdexed system dump

Here is a deodexed system I couldnt get them all but did have luck with most if you can help it would be amazing.
FULL ROM
196.3MB
How do we apply this?
Sent from my PG06100 using XDA App
We don't. It's more of a template for themes. Besides we can't really apply anything till we get perm root and ideally a custom recovery
soon as my source compiles (taking forever) imma take the system.img out of the ruu and deodex that and pull sense out of it. is that what you did, with the ruu?
this will be mainly deodexed on a few things I couldnt deodex so just wait and you can try to deodex what I couldnt. will save you 2hours of deodexing what i did already.
and recovery has already been made they will post soon i think.
Full deodex'd system link
epitaphromance said:
soon as my source compiles (taking forever) imma take the system.img out of the ruu and deodex that and pull sense out of it. is that what you did, with the ruu?
Click to expand...
Click to collapse
Deodexing a system is only taking the odex files that are in the rom and placing them in their corresponding apk
This makes for a slower boot time but enables themeablitly whiich means if themers want they can get start on all there creations now n have them ready come perm rootage!!!!
Sent from my PG06100 using Tapatalk
gu1dry said:
Full deodex'd system link
Click to expand...
Click to collapse
did you use a kitchen or a tool? what did you use?
Used baksmali & smali for most of it & remaining ones that I was having issues with I did with Auto Deodexer that I manually uploaded to work with the newer version of baksmali & smali...
Number one rule of deodexing a stock rom, ALWAYS use dsixda's kitchen, it automatically runs any apks against each and every firmware jar and every firmware jar against another. That way you don't end up having extra files not deodexed.

[CLOSED][THEME] Stock Triumph Deodex Template[CLOSED]

Thread closed because I no longer own this device. The download links no longer work. Sorry for any inconvenience.
Hey man howd u get the wifi going? And do u mind if i link to this in my post in development for the stock odex and deodex roms? Because i and i know alot of people tend to skip over the theme section
Sent from my PG06100
I don't know what exactly fixed it for sure. I just took the stock system.img from the complete non powered on nandroid backup posted, extracted all the files(using unyaffs.exe) and went through and auto deodexed framework and app using an auto deodexer tool found on xda, then the files taht wouldnt auto deodex using that .bat script, I used the baksmali and smali jar files to manually deodex the rest. I kept geting erros on the DbgCfgTools.apk(but ir ead up on the erros i was gettinmg and some of the htc sense roms were getting erros on some of there files like that and they said to use the -I option when baksmali'ing the odex file and it ignores the errors I guess, but that app was refering to bootclass paths that are no where in any .jar file on the phone so it's likely that apk didnt work in the first place cause if it was called to, it would display the same bootclass errors.
Yeah you can link to this, and I will make a stock deodexed rom that also formats and replaces everything in the /hidden partition(i.e. all the bloatware) as well as a bone stock rom so someone who has messed up the hidden partition can get back to bone stock easily!
Mediafire is down, and I just lost wifi with my phone when installing your bone stock ROM... you know, the one that doesn't have working wifi.
So here I go bumping your thread and adding some mirrors. This thread needs to be stickied or something.
Yes, mirror would be good!
√ HTC Evo 3D GSM
√ Android JB 4.1.2
√ Disarmed Toaster
√ 4EXT Recovery Touch
√ Anthrax Kernel 3.7.0 @ 1.6ghz

[APP][CWM Flashable] Touchwiz Program Monitor Widget (deodexed)

I have created a flashable zip to install the Touchwiz Program Monitor Widget into any deodexed SGS2 Skyrocket ROMS (running Touchwiz) which are missing it such as boneSTOCKeteer.
Make sure you have /system/app/JobManager.apk installed, and are running Touchwiz prior to flashing the zip file.
This is my first go at deodexing and creating a CWM flashable zip, you can always extract the zip and push the .apk into /system/app via Root Explorer if you are nervous.
Hope you enjoy.
promiseofcake
i'm pretty sure that this widget can only be used on the twlauncher. is there another widget that is similar?
jnicks510 said:
i'm pretty sure that this widget can only be used on the twlauncher. is there another widget that is similar?
Click to expand...
Click to collapse
You are correct, this is for people who are running touchwiz but do not have the widget as per it missing from boneSTOCKeteer.
Thanks for making this!
I'm new to all this. I found that I couldn't install the apk just by opening it, but the zip installs via clockwork mod. I don't really know why but has something to do with deodexing, right? Is there a tutorial for learning about deodexing and creating flashable zips?
purgatoroid said:
Thanks for making this!
I'm new to all this. I found that I couldn't install the apk just by opening it, but the zip installs via clockwork mod. I don't really know why but has something to do with deodexing, right? Is there a tutorial for learning about deodexing and creating flashable zips?
Click to expand...
Click to collapse
System apps are not installed, they just need to be placed in /system/app with the correct permissions (644). You can use something like Root Explorer and you wouldn't have to flash. An odexed rom just means that for each APK there is a corresponding .odex file so: Phone.apk and Phone.odex for example. I think it would also work if I made a flash with ____.apk,_____.odex but well deodex is the trend for portability. A deodexed APK just has the .odex file basically placed inside of it.
I would start with ADB first and then once you are familiar with everything you can move on to flashing. Flashing is really only good if you want to share your changes, it's much easier to just push the file via ADB.
http://www.madteam.co/forum/tutorials/how-to-deodex-an-odex-file/

[Q] How to get GTAB P5113 Samsung Keyboard on CM10?

Not liking the Android Keyboard too much in CM10 JB for Galaxy Tab 2 10.1 wifi
so, looking for way(s) to get the Stock Samsung Keyboard app/apk from ICS to work on CM10.
Tried using Titanium Backup / restore, as well as, recovery update.zip options but no luck.
Any ideas on how to get this app as well as few other Samsung Stock apps to work on CM or other builds?
You need the APK (and odex if it wasn't deodexed) as well as the lib for the keyboard.
a bit mre detail plz
imnuts said:
You need the APK (and odex if it wasn't deodexed) as well as the lib for the keyboard.
Click to expand...
Click to collapse
Dude, is that an Audi? I am guessing you drive one, I do and Love it!
As for how to make the apps run, I have searched but confused about Smali, Baksmali etc. And don't think I am going the right direction here. So, if you could, plz post some steps as to how this is done. Also, where to find the lib and odex files...
I'd have to restore my original backup and extract the files and later restore the current running cm10. Since I have only one tab, it is not easy to experiment as it takes time for loading etc. If u can post some specific steps, I'll just take it from there for all the stock apps I need (I.e. calendar, memo etc.)
The easiest way to do it would be to pull the APK from a deodexed ROM, then you don't need to worry about an odex file. For the lib, I believe it is libXt9core.so or similar, and it will be in /system/lib/. Then all you would need to do is put the APK in /system/app and the lib in /system/lib and it should work for you.
Also, yes it is an Audi

Categories

Resources