Hi.
I'm trying to pull GenieWidget.apk and .odex from a XT925 firmware I dowloaded. I presume its in the system_signed file as its the only thing big enough to be /system.
I searched quite a lot and apparently its not the same as on previous models; I can't just mount it using -o loop because it asks for a filesystem type.
I have a GenieWidget.apk from an AOSP build of my previous phone that works quite well but I prefered the one on the RAZR HD ICS and am hoping it will still work in JB. It was removed in general from ICS to JB updates so its quite possible that I just need to put the files back.
If someone can upload those files from ICS that would be helpful. I would, however, like to know how to mount or extract this file though and I'd appreciate any info on that as well. I have OS X, Linux, and Windows to work with.
Any help?
Related
I don't know about you but I'm not a huge fan of the touchwiz lock screen and apparently neither are other touchwiz variant owners. So I decided to compile a jar for the stock vanilla launcher as a replacement. I haven't tested it yet, but if anybody can successfully get it to push to /system/framework and report back to me that would be great.
There are two files attached one is the modified jar to push and the other is any update.zip to flash back the original if the modded doesn't work.
You must also be using a deodexed and zip aligned ROM.
I will test this when I make it home thanks!
Sent from my SPH-D700 using XDA App
is it working working?
What is the likelyhood this could make a mess of the phone?
I can push it right now but I'm not sure I feel comfortable doing it not knowing what may happen.
I can't seem to get it to push. Do i need to change the file name at all? It says read-only file system and won't allow a push.
Spectral8x said:
I can't seem to get it to push. Do i need to change the file name at all? It says read-only file system and won't allow a push.
Click to expand...
Click to collapse
Couldn't make it more than 22min without having to try huh?
i extracted the jar from android policy.zip pushed it to /system/framework and my phone would not boot into the os, i had to restore my phone from a nandroid back i had, and yes i did have a deodexed and zipaligned rom on my phone.
Hi, i am interested to build a deodexed firmware for the G3 so we have a base for theming. for this i used xultimate to deodex the files which went well without problems. but when i try to cp the files to system it starts to thow error messages that there is no more space left. after this the system was frozen and did not reboot anymore. so i guess i have to mount the factoryfs.rfs file from the firmware i use (xxjk1 for now) to do everything in there. since i am to very used to linux console i have no idea how to do this, but i know some people (gsam101 and precurse) use this method to build their own firmwares, so maybe one of them can help me here.
for people interested i include the deodexed files here also: http://archiv.to/GET/FILE2C25F1FCDED48
FadeFx said:
Hi, i am interested to build a deodexed firmware for the G3 so we have a base for theming. for this i used xultimate to deodex the files which went well without problems. but when i try to cp the files to system it starts to thow error messages that there is no more space left. after this the system was frozen and did not reboot anymore. so i guess i have to mount the factoryfs.rfs file from the firmware i use (xxjk1 for now) to do everything in there. since i am to very used to linux console i have no idea how to do this, but i know some people (gsam101 and precurse) use this method to build their own firmwares, so maybe one of them can help me here.
for people interested i include the deodexed files here also: http://archiv.to/GET/FILE2C25F1FCDED48
Click to expand...
Click to collapse
You can do this:
1. rm /system/app/*.odex
2. cp /sdcard/done_app/* /system/app/
3. cp /sdcard/done_frame/* /system/framework/
4. rm /system/framework/*.odex
It's succeeded for me.
ah, ok... so you got a deodexd rom already?
FadeFx said:
ah, ok... so you got a deodexd rom already?
Click to expand...
Click to collapse
yes, but i can't mod the framework (for example: battery mod)
did you try metamorph or ninjamorph?
FadeFx said:
did you try metamorph or ninjamorph?
Click to expand...
Click to collapse
none of them
i tried the uot kitchen
can i do battery indicator in statusbar with meta or ninja morph?
Metamorph can exchange images inside the apk, not sure what ninjamorph can do more. If you need to do something else for the battery mod you'd still have to do it manually
FadeFx said:
Hi, i am interested to build a deodexed firmware for the G3 so we have a base for theming. for this i used xultimate to deodex the files which went well without problems. but when i try to cp the files to system it starts to thow error messages that there is no more space left. after this the system was frozen and did not reboot anymore. so i guess i have to mount the factoryfs.rfs file from the firmware i use (xxjk1 for now) to do everything in there. since i am to very used to linux console i have no idea how to do this, but i know some people (gsam101 and precurse) use this method to build their own firmwares, so maybe one of them can help me here.
for people interested i include the deodexed files here also: http://archiv.to/GET/FILE2C25F1FCDED48
Click to expand...
Click to collapse
Hi - I see in your signature that you have JPY @ Galaxy S.
Please which JP? had becomed the official 2.2 for Galaxy S. ?
Because now we have JPF and it looks like the versions and its issues are the same @ galaxy 3. thx
I don't think that the problems are related to the problems on sgs since the hardware is completely different. The first official froyo for the sgs was jp6 i think, but i am not entirely sure since first time i used kies to update was jpy and i did it using the registry hack.
try to use apktools to decode resources,
i have test 1.31 and Issue 100 ver is work decode
1.32 is not work
http://code.google.com/p/android-apktool/
is 5800 only can 100%-90%-80%,some phone is 1% move
maybe edit smali can work 1% move..
Good evening dev community, I'm trying to create a flashable .zip that will replace the wpa_supplicant file with one that can connect to Ad-hoc networks. Replacing the file is actually really easy to do but I want to make a flashable .zip for others who don't want to mess with root explorer or ADB.
I have taken a .zip that works for the CWM 2.x for my phone but that won't flash on the xoom because CWM 3.x doesn't support the amend language so I converted it using amend2edify by nubecoder and I was so excited when it seemed to work but it will look like it's flashing and not actually do anything.
I was wondering it someone who knows more than me might want to lend a hand.
Please take a look and see if you can see anything wrong with my updater-script
Here is what I have so far. (see attachment)
Disclaimer: I got bored with not getting anywhere so I changed some of the display text so it's goofy so try to ignore that.
You shouldn't need to be afraid to flash it, it's harmless... that's the problem.
But as always you do so at your own risk.
Bump?
Sent from my Xoom using Tapatalk
Take a look at this thread. There is a link to a generic update script that works on the xoom. Just put your file in the right folder / subfolder and you should be good to go.
http://forum.xda-developers.com/showthread.php?t=1041205
I'll take a look at it. Thanks.
Sent from my Xoom using Tapatalk
Thanks for the help. It's exactly what I needed. I put a thank you in my new thread on this http://forum.xda-developers.com/showthread.php?t=1106130.
Do you know where I can get the wpa_supplicant file that will work with my Toshiba Thrive Tablet running Android Stock ROM 3.1? Thanks!
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
I have a ZTE990 avail.
Currently I'm rooted with no other roms installed, simply stock, and odexed.
I've tried to manually de-odex using baksmali, Xultimate, etc. All were a pain, all wouldn't work properly.
I found someone and downloaded someone who just simply uploaded a Stock_Deodex.zip rom. Sounded perfect.
So I boot into CWM, try to update and...
assert failed: write_raw_image("/tmp/boot.img","boot" android
Click to expand...
Click to collapse
Since I have stock.. and am just trying to De-Odex.
Can I just unzip the Stock_Deodex.zip, delete the current (apparently faulty) boot.img, and replace it with one of the ones created with the cwm recovery, re-zip and attempt to update as usual?
Or since (if my understanding is correct), the only thing necessary for a system to become deodex is the files in /system/app and /system/restore.
Obviously when I un-zip stock_deodex.zip I have access to them. Could I possibly just replace the two folders (somehow?) and be properly de-odexed?
Any other options that I could use that'd be best?
Much appreciated to anyone who helps, thanks!