can anyone on a leak v3/OTA please run the following commands and post the files here.
adb pull /system/etc/apns-conf.xml
adb pull /data/data/com.android.providers.telephony/databases/telephony.db
With those two files I HOPE to be able the MMS issues for all roms once and for all.
Note, if you ran APN Backup/Restore, you're no good to me . I need someone who is fully STOCK.
andrizoid already tried that. he put out an apn-conf.xml that includes the apns from ivans-apn, the stock eris, and the apns included in the conf file when built from source.
dont think its going to be that easy, but if you get it working i am totally switching
can you please post his apn-conf here? and its not exactly the same. I want these files from a fully non root untouched build.
i think he pulled it from the plain jane rom
stupid xml file
thanks... i think we have a winner... gonna test and see. the problem with his file is he left in all of cyanogens gsm apns, and thats probably mucking things up.
ha, now i know where i must of gotten the 935 apns (btw, never used WW... must of been from previous Cyanogen i guess).
in any case... bout to try something myself
good luck vinyl! thanks for all your hard work!
whatever your trying, be sure to report back
well mms works for me on sense based roms but its always broken on any rom where the dev replaced the apk with the stock android one. my theory is that its broken because the stock mms.apk the everyone is using is for gsm phones while the eris is a cdma phone. i may be wrong but who knows lol just wish i could get my hands on a stock one from an android phone on like verizon to test it out.
vinylfreak89 said:
can anyone on a leak v3/OTA please run the following commands and post the files here.
adb pull /system/etc/apns-conf.xml
adb pull /data/data/com.android.providers.telephony/databases/telephony.db
With those two files I HOPE to be able the MMS issues for all roms once and for all.
Note, if you ran APN Backup/Restore, you're no good to me . I need someone who is fully STOCK.
Click to expand...
Click to collapse
Have you reviewed what what TopazAaron has already done for the Ic3 ROM mms fix at http://forum.xda-developers.com/showthread.php?t=677715 ? If you look at his .zip flash fix it seems like a similar path to your effort...
I could be missing something but from my research watching the Dalvik monitor is that there is an issue with the Vanilla mms.apk for the ERIS platform and not nessessarily the apn values. the fact that Handcent works seems to support this. If helpful below is a dump of the error I get
Code:
06-15 21:44:28.044: ERROR/WorkingMessage(1039): Failed to send message: content://mms/drafts/7, threadId=1
06-15 21:44:28.044: ERROR/WorkingMessage(1039): java.lang.ClassCastException: java.lang.String
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at android.app.ApplicationContext$SharedPreferencesImpl.getInt(ApplicationContext.java:2607)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at com.android.mms.transaction.MmsMessageSender.updatePreferencesHeaders(MmsMessageSender.java:107)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at com.android.mms.transaction.MmsMessageSender.sendMessage(MmsMessageSender.java:76)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at com.android.mms.data.WorkingMessage.sendMmsWorker(WorkingMessage.java:1033)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at com.android.mms.data.WorkingMessage.access$000(WorkingMessage.java:64)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at com.android.mms.data.WorkingMessage$1.run(WorkingMessage.java:922)
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at java.lang.Thread.run(Thread.java:1096)
Do we know where the version of mms.apk we are try origionally came from?
Actually, White Widow is built from the newest cyanogen commits according to the wave. and if you check, it s the cyanogen 5.0.8 DS-test4 rather than test0
thats the apn conf from the ota.
can you upload that as a pure file, not a patch.
its not a patch. thats how it is in the ota .img
its an xml.p file
that file is in /system/etc?
Hello,
I had the same issue with the same exception in the log :
java.lang.ClassCastException: java.lang.String
06-15 21:44:28.044: ERROR/WorkingMessage(1039): at android.app.ApplicationContext$SharedPreferencesImpl.getInt(ApplicationContext.java:2607)
in fact looking in the code the issue is linked to acces MMS preferences. I fixed the pb by reseting to defaut prefs for MMS.
Hope it helps
Related
I managed to fix mms sending on cricket. I edited default.xml in /system/customize/MNS and Mms.apk. Now my picture message works perfectly on my phone.
So in order to install files you need to download them and then unzip default.zip.
You need to place both filies inc c:\ drive.
Now
adb push c:\Mms.apk /system/app/Mms.apk
adb push default.xml /system/customize/MNS/default.xml
adb reboot
Once your phone reboots it should work fine with picture messages.
Did anyone try this let me know how this works for you. I would post my apn settings but I use full android plan. Let me know how this works for you guys.
Now this is something we need to get the mms receive working in miui but for sprint
Sent from my HTC Evo using Tapatalk
This for cricket it allows to receive and send picture message. I tested with verizon and t mobile customers and works realy fast.
Could you fix the one for the miui rom it only sends mms but dont receive
Sent from my HTC Evo using Tapatalk
hmm interesting lemme try summin
Did you modify MMS.apk and fix what was causing it not to send properly? Is this a modified MMS from a Sprint rom? Or one from a Verizon roms like the rest of us have been using?
Would you mind sharing?
Also, are you capable of MMS while wifi is on by any chance?
NICE!
Thanks for sharing....
I will try and repost my results I also am on the android plan this is my apn settings..
<?xml version='1.0' encoding='UTF-8' standalone='yes' ?>
<apns count="1">
<apn name="CDMA-MMS" numeric="46605" mcc="466" mnc="05" apn="mms" user="your10digit#here@mycricket.com" server="NA" password="cricket" proxy="wap.mycricket.com" port="8080" mmsproxy="null" mmsport="null" mmsprotocol="null" mmsc="http://mms.mycricket.com/mycricket/mms.php" type="mms" />
</apns>
Thanks to deathsled... for the apn
WHOA, Im ecstatic!
You did it!
I confirm this solution to be working on my favorite ROM solution...
VirusROM BASE SENSE RC3 with Carbon Theme...
I could not use the adb push method as I am on the road and forgot to grab my micro usb cable...
1. I used Root Explorer to first delete mms.apk from /system/app
2. I copied mms.apk to /system/app
3. Using Root Explorer I over wrote default.xml/system/customize/MNS/default.xml
4. Reboot
5.
A. To my surprise I did not have a messaging app in the app drawer upon boot?
B. Using Root Explorer I navigated my SD card to folder I had placed mms.apk and launched mms.apk thus installing.
6. Downloaded and installed APN Backup, removed current apn.
7. I used the above posted APN.xml after modifying the "red" string with my info, thanks deathsled provided and apn.xml
8. Rebooted
9. SUCCESS!
I figure some of the steps may not be necessary how ever I documented the exact process and procedure in which I now have functioning MMS..
tritron777 Major props to you man!!! You just killed it man!!!!
This is from sprint rom mms.apk and default.xml. I did not try to send mms over wifi.
I believe that for someone using proxy they can use apn proxy by changing this mmsproxy="null" mmsport="null" to mmsproxy="wap.mycricket.coml" mmsport="8080"
Well I found out that modification to default.xml also changed the market. It restored download section. The problem with sending mms over wifi is that we mms server is protected by cricket or any carrier so it limited by range of ip addresses so we can't connect because we are not on a network. So the only way to make this work is to have stop wireless connection and start data the moment we eant to send mms.
What was the issue with the market download section?
I did not have an issue with it that I noticed?
tritron777 said:
This is from sprint rom mms.apk and default.xml. I did not try to send mms over wifi.
I believe that for someone using proxy they can use apn proxy by changing this mmsproxy="null" mmsport="null" to mmsproxy="wap.mycricket.coml" mmsport="8080"
Click to expand...
Click to collapse
Proxy information is not needed on cricket regardless of the plan. (im on a proxy plan and don't have any in there and its fine)
Question for you, was all that you modified was the:
Mms.apk>smali>com>android>mms>transport>HttpUtils.smali
X-SPRINT-MDN to X-Cricket-MDN?
Or were there other internal changes to the Mms.apk file needed? reason im asking is i would like to do the same for hero users as well since this seems to plague all sprint roms and i have been digging to find the root cause for awhile
That the change I made to mms.apk wasto change X-MDN to X-Cricket-MDN I guess metropc would need X-metropc-MDN. Now default.xml I changed all sprint references to
the way ZIO shows it self. Now that gets market back to the way it was before sprint section was added
tritron777 said:
That the change I made to mms.apk wasto change X-MDN to X-Cricket-MDN I guess metropc would need X-metropc-MDN. Now default.xml I changed all sprint references to
the way ZIO shows it self. Now that gets market back to the way it was before sprint section was added
Click to expand...
Click to collapse
Awesome thanks for the info. Going to try to correct this for hero's now as well
and now we know!
Next up, fix MMS under AOSP/non sense roms for Cricket. Or does that work and I'm retarded? I couldn't find anywhere to set the MMS size and I think that might be the only problem.
Just in case I have a backup of the Mms.apk from a brand new Samsung epic. Just email or PM me. no I do not charge for this. And if anyone can host the file i will be more than glad to share.
the Mms.apk does remove the Mms from the phone. when i try to reinstall it from the phone using root explorer it says "Parse Error there is a problem parsing the package." does anyone know what i can do to fix this error?
Not related but... anyone get Metro MMS working yet? I have a working APN from my bros Eris and I cant get it working at all... How would one edit the Mms.apk?
morbidj said:
WHOA, Im ecstatic!
You did it!
I confirm this solution to be working on my favorite ROM solution...
VirusROM BASE SENSE RC3 with Carbon Theme...
I could not use the adb push method as I am on the road and forgot to grab my micro usb cable...
1. I used Root Explorer to first delete mms.apk from /system/app
2. I copied mms.apk to /system/app
3. Using Root Explorer I over wrote default.xml/system/customize/MNS/default.xml
4. Reboot
5.
A. To my surprise I did not have a messaging app in the app drawer upon boot?
B. Using Root Explorer I navigated my SD card to folder I had placed mms.apk and launched mms.apk thus installing.
6. Downloaded and installed APN Backup, removed current apn.
7. I used the above posted APN.xml after modifying the "red" string with my info, thanks deathsled provided and apn.xml
8. Rebooted
9. SUCCESS!
I figure some of the steps may not be necessary how ever I documented the exact process and procedure in which I now have functioning MMS..
tritron777 Major props to you man!!! You just killed it man!!!!
Click to expand...
Click to collapse
I keep getting application not installed for step 5B when trying to install app any way around this?
I tried with Root Explorer, App Installer, and even adb install, non worked!
i need help, if someone could PM me asap it would be great. i've been searching for 15 hours and can't get this figured out. thanks.
brandon2x said:
i need help, if someone could PM me asap it would be great. i've been searching for 15 hours and can't get this figured out. thanks.
Click to expand...
Click to collapse
Hm... just a stab in the dark. I experienced a problem with RSD also, but don't remember the exact error code. Here is what I did:
Move .SBF file to C:/
Name it "X.sbf"
Run RSD, it will probably give an error
Go check the error log (sorry, don't remember where it is located)
In the logfile it will say something like "Xa few random characters here.sbf failed"
Let's say it says "Xµµµ.sbf failed"
Go back and RENAME the .sbf file to however many random characters there are
In my example, we would rename the file to "X123.sbf"
Now it should work
in the rsd lite file there is no error log. i don't understand, with all the errors i've gotten there should be one...
fixed. thread can be deleted.
Heres the instructions
androidforums.com/droid-all-things-root/74153-if-you-get-failed-flashing-process-0x7100-rsd-lite.html#post1274587
UPDATED 2012.09.05!!! Hey guys, if you can do some testing with the new version and give me some feedback, I fixed some errors with the drag and drop code, and included apktool versions (1.2.0, 1.3.2, 1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.10, 1.5.0) you can add as many others as you like to the _bin folder, just create a separate folder with the version number and place it in there (make sure the file is named "apktool.jar" or the code won't work), if you want to set a default apktool version to use, so that you aren't prompted all the time, you can change the name of the "apktool.manual" file to (for example) "apktool.1.4.9" and from then on it will use that version instead of prompting... and you can always change it back, or change it to a newer/older version number as needed...
if this works well for you guys I will update the first post...
Code:
Beta Changelog
2.0 Initial Beta
2.1b
cleaned up some code issues (defualt file wasn't working properly)
added the newer unofficial apktool builds (1.4.5 -- 1.5.0)
here's the mediafire link: http://www.mediafire.com/?td20i8cv8lfq90l
First of all, I did not create apktool (DUH!) that credit goes to: Brut.alll what a wonderful tool. I have included version 1.3.1 because that is the version that seems to work best right now...
Note: Brut.alll, if you happen to read this and would like me to remove apktool from being included with my batch scripts, please contact me and I will happily do so.
Alright... the easyFLASHABLEzipBUILDER gave me the idea to do this... Basically it's a way to "automagically" compile/decompile (smali/baksmali via apktool) apk's and jar's for all you dev's or wannabe dev's who want an easier way about this... These are windows batch scripts and should work with anything win2k or newer.
how it works: said:
Extract to a directory, for simplicity we'll say "apktool"
Place whatever file/folder(s) you would like to compile/decompile in the root of "apktool"
The filenames are pretty self explanatory... the drag and drop options file will prompt for the options only, this way you can still have the ease of drag and drop, but only need to input the more specific options
The manual file will only ask for options and filename, if you decompile it will change the last "." before extension to a "_" so framework-res.apk would output to _out\framework-res_apk.
When you (re)build with ANY of the files if the given folder name is framework-res_apk then the output file will be framework-res_REBUILTsigned.apk
The manual and drag and drop files always preserve the extension, so if you modify the folder name before rebuilding leave the "_apk" or "_jar" alone.
I will add some error checking in later versions, but at the moment you'd probably have to be trying, to create an error, and it would only be an error with the batch, you wouldn't actually mess a file up or anything.
now outputs all files/folders to a subfolder "_out"
core files are now in "_bin" folder... batch files must be one level above this folder to work properly.
Drag and drop works from ANY folder, but always outputs to the "_out" folder.
rebuilt files are now signed with a test key, so shouldn't have any "unsigned" or "improperly signed" errors when trying to install after being rebuilt.
Click to expand...
Click to collapse
Let me know if you have any requests, or questions... happy to help in any way I can...
MEDIAFIRE [LATEST]: http://www.mediafire.com/?cablu617ijq22ac
benjamminzIS said:
Note: Brut.alll, if you happen to read this and would like me to remove apktool from being included with my batch scripts, please contact me and I will happily do so.
Click to expand...
Click to collapse
I'm always happy to see that someone uses and/or improves my tools
Brut.all said:
I'm always happy to see that someone uses and/or improves my tools
Click to expand...
Click to collapse
I know this will probably only appeal to the "newer" devs who are just getting started... but I'm a fan of less typing to accomplish the same goal, so I figured why not =)
thanks for your blessing, it's appreciated!
Linux compatable?
Daughain said:
Linux compatable?
Click to expand...
Click to collapse
not currently... but if linux supports drag and drop on scripts, I suppose I could look into porting it for linux... or if not I could just make a "manual" version for linux? (as in one that just prompts for for the options and filename and does the rest) I need to start familiarizing myself with linux anyways... so it would be a good learning experience for myself...
c'mon guys, over a hundred takers already and pretty much zero feedback! If there is anything functionality wise you looking for please let me know, I would like to be able to improve this for you guys, but if no one says anything, then I don't even know if it's working for you or not... 30seconds of your time to write a post isn't asking much =P
Great tool
2 of the 4 bat files worked great. The other 2 gave me the syntax usage be fore it said GOODBYE.
Working for me:
DRAGandDROPbuild.bat
DRAGandDROPdecompile.bat
Not working for me:
DRAGandDROPoptions.bat
APKtoolMANUAL.bat
Thank you. This would save sometime.
IamSonoma said:
Not working for me:
DRAGandDROPoptions.bat
APKtoolMANUAL.bat
Thank you. This would save sometime.
Click to expand...
Click to collapse
thanks for the feedback, I'll check it out... hopefully will have an update asap...
EDIT: main post updated, this patch is now obsolete...
nice, when i decompile a apk and change one string and then recompile it gives me application not installed (i am thinking its not signing the apk correctly)
for that matter if i dont change anything and decompile then recompile, same issue
benjamminzIS said:
can you try this out for me, and tell me if it solves your issue? if it does I will add to first post and update the main download...
Click to expand...
Click to collapse
Firmware: Froyo 2.2.1 KP5
Phone: Samsung Captivate
OS: Windows 7 and Windows XP
Code:
Batch File Tested: APKtoolMANUAL.bat
File Tested: Settings.apk
Decompile Errors: 0
Recompile Errors: 0
Folder Output: Settings_apk
Decompiled File Tested: Settings_apk\res\values\bools.xml
Edit made: <bool name="has_intrusive_led">false</bool> --> <bool name="has_intrusive_led">true</bool>
Changes took: Yes - <bool name="has_intrusive_led">true</bool>
Code:
Batch File Tested: DRAGandDROPoptions.bat
File Tested: Settings.apk
Decompile Errors: 1
Recompile Errors: N/A
Option chosen: d
Folder Output: Settings_apk.out
Result: Exception in thread "main" brut.androlib.AndrolibException: brut.directory.DirectoryException: java.io.FileNotFoundException: C:\EASYapkTO
OLcompilerDECOMPILER_patch_v1.1" C:\EASYapkTOOLcompilerDECOMPILER_patch_v1.1\C:\EASYapkTOOLcompilerDECOMPILER_patch_
v1.1\Settings_apk (The filename, directory name, or volume label syntax is incorrect)
at brut.androlib.ApkDecoder.hasSources(Unknown Source)
at brut.androlib.ApkDecoder.decode(Unknown Source)
at brut.apktool.Main.cmdDecode(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.directory.DirectoryException: java.io.FileNotFoundException: C:\EASYapkTOOLcompilerDECOMPILER_patch_v1.1" C:\EASYapkTOOLcompilerDECOMPILER_patch_v1.1\C:\Downloads\EASYa
pkTOOLcompilerDECOMPILER_patch_v1.1\Settings_apk (The filename, directory name,
or volume label syntax is incorrect)
at brut.directory.ZipRODirectory.<init>(Unknown Source)
at brut.directory.ZipRODirectory.<init>(Unknown Source)
at brut.androlib.res.util.ExtFile.getDirectory(Unknown Source)
... 4 more
Caused by: java.io.FileNotFoundException: C:\EASYapkTOOLco
mpilerDECOMPILER_patch_v1.1" C:\EASYapkTOOLcompilerDECOMPI
LER_patch_v1.1\C:\EASYapkTOOLcompilerDECOMPILER_patch_v1.1
\Settings_apk (The filename, directory name, or volume label syntax is incorrect
)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.zip.ZipFile.<init>(Unknown Source)
... 7 more
Code:
More Testing
Batch File Tested: DRAGandDROPdecompile.bat
File Tested: Settings.apk
Decompile Errors: 0
Folder Output: Settings_apk
Decompiled File Tested: Settings_apk\res\values\bools.xml
Edit made: <bool name="has_intrusive_led">false</bool> --> <bool name="has_intrusive_led">true</bool>
Changes took: Yes - <bool name="has_intrusive_led">true</bool>
Batch File Tested: DRAGandDROPbuild.bat
File Tested: Settings.apk
Recompile Errors: 0
Folder Output: Settings_apk
Decompiled File Tested: Settings_apk\res\values\bools.xml
Edit made: <bool name="has_intrusive_led">false</bool> --> <bool name="has_intrusive_led">true</bool>
Changes took: Yes - <bool name="has_intrusive_led">true</bool>
Output File: Settings_REBUILT.apk
IamSonoma said:
Firmware: Froyo 2.2.1 KP5
Phone: Samsung Captivate
OS: Windows 7 and Windows XP
Click to expand...
Click to collapse
ok, will have to look into it... my apologies... looks like I'm handling the variables wrong...
No biggie. For the most part all is good. Plus I have been using cm7 and been busy.
Sent from my Captivate using XDA App
IamSonoma said:
No biggie. For the most part all is good. Plus I have been using cm7 and been busy.
Sent from my Captivate using XDA App
Click to expand...
Click to collapse
ok, looking at it a little closer, it looks as though you extracted the patch to a sub directory, if you ran the batch files from that subdirectory, then you will get errors as it is looking in that subdirectory for the _bin folder... try overwriting the original files, with the ones from the patch... then try again... let me know if you still get the error...
benjamminzIS said:
ok, looking at it a little closer, it looks as though you extracted the patch to a sub directory, if you ran the batch files from that subdirectory, then you will get errors as it is looking in that subdirectory for the _bin folder... try overwriting the original files, with the ones from the patch... then try again... let me know if you still get the error...
Click to expand...
Click to collapse
Ok. Thank you. Extracted the files again and moved folder to my e:\.
Working with contacts.apk it decompiled and recompiled fine. Contacts.apk did not work when I moved it to the system/app folder. I will test more later. the file was more compressed. I will recompile it later with winrar and the store command.
UPDATED!
fixed the syntax in DRAGandDROPoptions.bat and merged the fixes from the 1.1 patch...
also updated the thread name to be more proper... "compiler" instead of "builder" also updated the filename to match thread name... enjoy!
pyrator said:
nice, when i decompile a apk and change one string and then recompile it gives me application not installed (i am thinking its not signing the apk correctly)
for that matter if i dont change anything and decompile then recompile, same issue
Click to expand...
Click to collapse
I get the exact same problem no matter how I edit my apks and its confusing the hell out of me. Does anyone have any ideas on this? Happens with your tool here, and several others too.
Sent from my Nexus S
I have the same problem, and I think you are right about the signing.
I tried to resign the rebuilded file with autosign and I had the same resault. I mentioned that the file's size didn't change. I resigned again, using android commander' s sign option and at this time the file' s size incrased by 5K. The output file works without problems.
So, the problem seems to be with the apktoolj.
Thanks ill try that, it makes sense as I am trying to mod system apps such as camera and launcher2.
Thanks again! This could be what I'm looking for.
Sent from my Nexus S
strange, I thought apktool was supposed to sign as well? is it just not signing or is it improperly signing?
I am using the 1.3.1 version of apktool with this... I am using this version because 1.3.2 seems to have decompile/compile issues with many apk's...
I'm open to suggestions guys, please let me know if there is a "fix" I can implement and I will do so =)
hi there, im on firmware JDQ39.I9505XXUBMF8 DEODEXED Firmware, as far as im aware there's no mods to the system apart from being deodexed.. im wanting to disable the sms to mms conversion.. ive followed tutorials ive found on here using the mms_config.xml, and the smali files.. but nothing seems to work.. I can decompile, edit and recompile without any problems or errors, but when i transfer the file to the phone and set its permissions nothing changes, the messages still convert to mms when they get to 4 or above.. and im now at a loss as to why its not having an effect..
can anyone shed any light? i can decompile the file i transferred and see the changes ive made but the system just doesnt seem to register them...
would appreciate any help anyone could give me..
Hi
I try to decompile SecSettings by apktool and i get this:
Code:
C:\apktool>apktool d secsettings.apk SecSettings23
I: Baksmaling...
I: Loading resource table...
Exception in thread "main" brut.androlib.AndrolibException: Multiple resources:
spec=0x7f020052 drawable/avatar_default_6, config=-hdpi
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:65)
at brut.androlib.res.data.ResConfig.addResource(ResConfig.java:58)
at brut.androlib.res.decoder.ARSCDecoder.readEntry(ARSCDecoder.java:196)
at brut.androlib.res.decoder.ARSCDecoder.readConfig(ARSCDecoder.java:165
)
at brut.androlib.res.decoder.ARSCDecoder.readType(ARSCDecoder.java:130)
at brut.androlib.res.decoder.ARSCDecoder.readPackage(ARSCDecoder.java:10
5)
at brut.androlib.res.decoder.ARSCDecoder.readTable(ARSCDecoder.java:82)
at brut.androlib.res.decoder.ARSCDecoder.decode(ARSCDecoder.java:48)
at brut.androlib.res.AndrolibResources.getResPackagesFromApk(AndrolibRes
ources.java:315)
at brut.androlib.res.AndrolibResources.loadMainPkg(AndrolibResources.jav
a:50)
at brut.androlib.res.AndrolibResources.getResTable(AndrolibResources.jav
a:43)
at brut.androlib.Androlib.getResTable(Androlib.java:44)
at brut.androlib.ApkDecoder.getResTable(ApkDecoder.java:148)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:98)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)
What to do ??
Thanks
Please any help?
Same issue here
osherdadon said:
Please any help?
Click to expand...
Click to collapse
Using a Note 3 from T-Mobile, I pulled the file with the adb command, with root explorer, and extracted it from the stock ROM file all giving me the same error. For some reason I also don't get any smali files out of my SystemUI.apk which has been driving me crazy. I can't seem to find any working answers yet... Fail...
Basically bumping this thread a half a year later...
SOMEONE HELP US
You have the relevant frameworks installed and java in your path?
Learned a lot in 24 hours
DSA said:
You have the relevant frameworks installed and java in your path?
Click to expand...
Click to collapse
Summary/Lessons Learned in the last 24 hours:
I must have been too tired, went to sleep got up again and went at it. I realized a few things, main thing was deodexing, I learned all about that. Converting the .odex file to a class.dex file inside the SystemUI.apk and SecSettings.apk so decompiling would work properly (I was originally missing the smali folder without deodexing my app). Second I needed to pull all the framework files from my device instead of just the two I had, then I used "apktool if framework-res.apk" then "apktool if twframework-res.apk" then "apktool d SystemUI.apk" then "apktool d SecSettings.apk". This time it actually worked, I proceeded to try and re-compile them just to test. The SystemUI.apk worked flawlessly but the the SecSettings.apk had errors then I realized I needed to copy the AndroidManifest.xml and resources.arsc from the original app to the decompiled folder and the SecSettings.apk compiled with no issues. I had to get the original file out of the stock ROM, it had gotten damaged somehow with zipping/raring/7zipping so quicktip no one should be zipping the files you're about to work on get it fresh from the ROM.
Current Issue:
Now that all that's done I'm onto what I was trying to get at when I started this whole project. I need to modify both of these apps which are now perfectly deodexed and on my stock device. Every time I try to modify these files I lose my status bar and my settings stop working, I'm obviously breaking it, this is the XDA guide I was following.
Any help or redirection on where to post would be greatly appreciated, thanks
Easiest thing - put your mod back in and get the status bar to disappear/fc whatever
Then, pull a log (catalog from appstore works fine)
Post that log at pastebin and link it here
We won't be able to solve your issue without knowing what it is, in the first place
Like this?
This was before I restarted: Log 1
Then I recorded for a little after I restarted probably pointless but that's where the error would have been: Log 2
DSA said:
Easiest thing - put your mod back in and get the status bar to disappear/fc whatever
Then, pull a log (catalog from appstore works fine)
Post that log at pastebin and link it here
We won't be able to solve your issue without knowing what it is, in the first place
Click to expand...
Click to collapse
Not sure exactly how to record it and send it to you, I pressed record but when the phone finished rebooting CatLog was closed so I reopened it and it keeps scrolling endlessly.
Research progressed a little
I came across a post here in the Flashlight Mod development thread which made me realize I'm not getting the ID's correct. They suggest compiling the modded SystemUI.apk to get the ID's into the apk file under the /res/values/public.xml file, then decompiling it to read the ID values. I'm missing a step or doing something wrong, I can't replicate it to find the ID values I need so I can add them to the .smali file and recompile a final time. I'm sure this is the only reason for the missing status bar and the force closes. I guess I need help understanding, a different set of instructions or just more detailed?
I can't post in that thread yet so I'm getting my posts up over here, I already posted in the Q&A thread but no one has responded yet, any help is greatly appreciated!
I get this when decompiling the modded apk: Modded SystemUI ApkTool Decompile
All these errors look like the file is broken now or something, I'm just lost at this point. I tried ApkTool 1.5.2 and 2.0 as well.
EDIT:
Additional info below for troubleshooting purposes since it seems my issue recompiling at the end to get the values for my public.xml
STEPS:
1. deodex (universal deodexer v5)
2. decompile (apktool 1.5.2 & 2.0 separate tests)
3. modify (add flashlight .png's and .smali file from 4.4kk flashlight mod files)
4. recompile (apktool)
5. decompile (apktool)
=
Errors <<<<< These errors solved in edit below
EDIT:
I forgot to use "apktool if SystemUI.apk" when loading "framework-res.apk" & "twframework-res.apk" now I get through decompiling and recompiling like I thought I should be and I even located the values int he public.xml, replaced them in the .smali and everything went peachy. Only problem is I never get the status bar after I reboot, not really getting any FC's but the status bar, if my goal were to get it to be invisible I would be so happy omg lol If you're curious I've also tested by signing and even another test with zipalign, nothing zip/zero/zilch...
EDIT... Again I know still no sleep, durp durp:
So my main issue was not using apktool v1.5.2 to decompile and v2.0 to compile EVERY SINGLE TIME, NO EXCEPTIONS. When I followed that simple rule I get it onto my device and she has no status bar... Hmmmmm..... And a logcat for anyone smart enough to help me
EDIT:
Maybe I'm in the right direction with an error I saw in the log at this post? I thought it was so I installed the DisableSignatureVerification Mod from the Xposed Modules and still nothing.
Calling All Developers
It's been like 2 weeks just curious if anyone has even looked at this, I haven't been able to make any progress so I started learning how to develop apps. I made two small apps basic flashlight and a counter app but I really want to know why I'm totally unable to mod a file on my phone. I can't get the ink effect to work with finger input either I've been really trying to get this flashlight mod and the ink effect for months. If I could get pointed in the direction of a developer that can actually help me I don't see why I couldn't donate like $10 or $20 to the one who helps me. I'm on android 4.4.2 (NK3) on my Note 3 from T-Mobile.