Little Help With modifying ROMs.. - myTouch 3G Slide Q&A, Help & Troubleshooting

Last night I tried getting SlideMR1v4, my day to day ROM, and replacing it's MMS.apk with the one from Eugene's Froyo ROM. I did this because I want the Stock mms app, as I really hate the espresso one. Instead of adb pulling/pushing, I rather do everything in my computer, flash the new ROM, and restore my /data partition from Nandroid if it works.
While I was at it, I modded some icons from a thread I found in the Android theme forums.
I know I pushed the files right, as I added the .apk the same way I added the icons, but when I flashed the new ROM the mms app was nowhere to be found, but the icons worked. Is this because I grabbed the apk from a froyo ROM?
Sent from my T-Mobile myTouch 3G Slide using XDA App

Related

[Q][SOLVED] Market 2.3

I know people have been having issues getting this to work on cm6, I found a method that ALMOST works if someone can help me expand on this.
I thought maybe it had something to do with the phone being s-on, so it couldn't upgrade properly, so I force removed the existing market app via titanium with the recovery exploit that it uses with s-on phones, and then installed it through the app manager like I would any other app. It took a long time but it eventually installed, but the glitches were so extensive it was unusable. It opens the app, and displays the UI elements fine, but if you do anything aside from navigate and search, it force closes. If you try to open an app's link up, it force closes. Attempting to go to "my apps" force closes it.
I was thinking maybe it either had something to do with the fact that it needs the old market to update to the new one, like it's an update patch, not a full app. The other thing I was thinking was that it wasn't working because it installed to /data/app, like a user app, not to /system/app like the normal market.
Would it work to adb install or adb push the apk to /system/app rather than install it as a user app do you think? I would really love to get the new market working on cm6.
SOLUTION:
All thanks to KCRic; he has posted the flashable zips for the new market, which I re-attached in the OP.
KCRic said:
*The smaller version has hdpi file removed and all languages removed except english (US). If you use another language use the larger version or shoot me a PM and I'll try to get you a small version in your language.
Click to expand...
Click to collapse
There you go, just flash them through clockwork recovery, they should work just fine.
I'm on cm6.1 and used the recovery zip file that is floating around and installed and use it with no problems at all
Sent from my T-Mobile myTouch 3G Slide using XDA App
You don't even need the recovery zip. It works perfectly fine just installing manually.
While in recovery just plug your phone in, go into adb shell and install it from there.
"cp (Location of app) /system/app/"
IE for me I put "cp /sdcard/download/android_market.apk /system/app/" and it worked.
I didn't do anything to the original market.
All I did was apply any zip from sdcard in clockwork..no adb needed
Sent from my T-Mobile myTouch 3G Slide using XDA App
droopypillow said:
All I did was apply any zip from sdcard in clockwork..no adb needed
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Where did you locate this zip? I changed the apk i had to a zip and tried what you did and installed from clockwork but got nothing :/
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Where did you locate this zip? I changed the apk i had to a zip and tried what you did and installed from clockwork but got nothing :/
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
If you renamed the apk to a zip, you're doing it wrong.
If you downloaded the update zip containing the apk, it's wherever you downloaded it.
Its in the them and app section under new market app..
Sent from my T-Mobile myTouch 3G Slide using XDA App
Yeah I never found a flashable zip, I just found an apk in the apps section. Which doesn't work. If someone could post a link to the flashable zip that'd be cool. I don't have access to a USB cable right now so adb isn't a very good option haha.
Edit: nevermind, found it on the second page of the thread, here's the direct link to the zip: http://www.mediafire.com/?w7hcd0uadlndnwd, it works great, no more force closes everywhere like I was getting before
I found a flashable zip from a diff source so problem solved. But how do you change a .apk to a .zip if not simply renaming?
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
I found a flashable zip from a diff source so problem solved. But how do you change a .apk to a .zip if not simply renaming?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You have to create an update package with the apk inside zip_file.zip/system/app/apk.apk and you have to put an update script into meta-inf/android/blah blah blah, google it, I've forgotten, only had to do it once, I'm sure there's a tutorial out there if someone here can't directly answer you
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
You have to create an update package with the apk inside zip_file.zip/system/app/apk.apk and you have to put an update script into meta-inf/android/blah blah blah, google it, I've forgotten, only had to do it once, I'm sure there's a tutorial out there if someone here can't directly answer you
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
here you go how to make a flashable package
Here you go, this should work - feel free to post in the OP if it's useful to anyone still trying to install it.
I'm going to remove all the hdpi files from the apk (since we don't need them, it will save space) and poat that version up in a bit. I'll test it first to make sure it will still work.
Added 'tiny' market install zip
For those that don't know, you go into clockwork recovery - select 'install zip from sdcard' - find the zip and install it. Reboot and enjoy.
etu_aty said:
here you go how to make a flashable package
Click to expand...
Click to collapse
Thx, i'll give a look-see on some free time
Sent from my T-Mobile myTouch 3G Slide using XDA App
KCRic said:
Here you go, this should work - feel free to post in the OP if it's useful to anyone still trying to install it.
I'm going to remove all the hdpi files from the apk (since we don't need them, it will save space) and poat that version up in a bit. I'll test it first to make sure it will still work.
Click to expand...
Click to collapse
Awesome, thanks, I'll post it in the OP when I get on a computer
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
Awesome, thanks, I'll post it in the OP when I get on a computer
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
Ok, sounds good. I'm testing the 'tiny' version now and I'll update that post with the file if it works. Removing the files didn't drop the size much (~0.3MB) but smaller is still always better.
EDIT: Added tiny zip to that post, work flawlessly
*The smaller version has hdpi file removed and all languages removed except english (US). If you use another language use the larger version or shoot me a PM and I'll try to get you a small version in your language.
Edited the OP, included info, should all be good to go
Also, would this market work on eclair? The version is 2.2.6 so I'm thinking not, since it has froyo elements like auto app update, etc.
Edit: shortly after I installed cr_mod the market auto updated, but it did so to version 2.2.7, not 2.2.6. So yes, the new market does work on eclair, with auto updating. Kickass. If you'd all like I can pull the apk from my phone and post it if no one has it? Although aside from cm users everyone should be getting updated, I think.
MusicMan374 said:
Edited the OP, included info, should all be good to go
Also, would this market work on eclair? The version is 2.2.6 so I'm thinking not, since it has froyo elements like auto app update, etc.
Edit: shortly after I installed cr_mod the market auto updated, but it did so to version 2.2.7, not 2.2.6. So yes, the new market does work on eclair, with auto updating. Kickass. If you'd all like I can pull the apk from my phone and post it if no one has it? Although aside from cm users everyone should be getting updated, I think.
Click to expand...
Click to collapse
Awesome 2.2.7 may be an edited update version for eclair, or maybe the updated it again?
KCRic said:
Awesome 2.2.7 may be an edited update version for eclair, or maybe the updated it again?
Click to expand...
Click to collapse
I have no idea, but honestly I'm thrilled to have the new market AND auto update functionality on eclair. It was also nice that I didn't even have to flash anything, it updated itself. I had heard that the auto update worked fine with sense ROMs, only people running CM were having issues. You're probably right, it's probably an edited version for eclair. But cr_mod still has gmail v1, I really wish I could get version 2.3 :/ old gmail sucks. I'm going to try and just pull the apk and upgrade it with an app manager from one of the gapps packages, but I'm not sure, since google apps on sense roms is different.
Well stock android will generally always work on sense roms, just not the other way around. The issue you may run into are differences in os versions (2.1 vs 2.2.1). But with gapps it's usually not an issue, at least not yet since the versions aren't too far apart.
KCRic said:
Well stock android will generally always work on sense roms, just not the other way around. The issue you may run into are differences in os versions (2.1 vs 2.2.1). But with gapps it's usually not an issue, at least not yet since the versions aren't too far apart.
Click to expand...
Click to collapse
I actually googled around a bit, the gmail that's in the market, which is 2.3 at the moment, and before that 2.2.1, only shows up on froyo, since that's all it works on. Eclair and below are all stuck with version 1 :/
I'm pretty sure HTC loads gapps in a different way because there is actually a googleapps.apk or gapps.apk in /system/app, the flashable package just has all of the apks. I tried to open the flashable zip with astro and browse to gmail.apk and see if it would upgrade but it wouldn't parse the package. I could TRY flashing the eclair gapps and see if that works, but I'll definitely do a nandroid first. I guess I'll try that and post back.
I love how my threads always end up venturing off topic. I kind of "hijack" my own threads in a sense

[Q] Phone button glitch...

Ok, I have a 2.02 hBoot EVO running 3.30 Froyo.
I have been rooted for a few days now and I just installed Wifi Tether from the market... It all worked well and what not - but now when I hit the Phone Button on the bottom of the screen (Rooted Stock Froyo) it no longer pulls up my phone dialer or recent history... all it does is pops up a grey bubble with the word "phone" inside it... I attached a few pictures of it to this post - any one know if Wifi Tether had anything to do with this or what else could have caused it?
Thanks
Your phone apk is not in systems. You need to reflash the Rom as it did not flash correctly
Sent from my PC36100 using XDA App
But I didn't flash a ROM...it worked until a cpl hours ago... I did "back up ROM" on my Rom manager Also a nandriod BU... then installed WiFi tether and some time after that it stopped working...
Sent from my PC36100 using XDA App
does any one know where i can get the apk for the evo with out flashing my ROM...I tried to do a NAND restore but or some reason it fails every time...
anyway - the dialer.apk... it was called some thing like "htc.dialer" some thing or other...
any ideas?
Lol...ok...thanks guys
Sent from my PC36100 using XDA App
just reflash the same Rom with out wiping anything. that should give the phone apk back.
I didnt flash a rom... Im still running rooting stock...
Sent from my EVO while tethered into the Matrix thru Wifi...
Odexed? Deodexed?
You can extract the apk from SteelH's ROM (it is pretty much stock) Or hunt for the actual stock rooted ROMs (deodexed and odexed)

[SOLVED] Extract Swype .apk?

Hey all,
I've got a G2 running CM7 RC2. One of the things that I loved about the stock rom was that swype was included. Unfortunately, CyanogenMod only has the default on-screen android keyboard. I made a backup image of my stock rom right before I installed CM. Is there any way that, if I backup my current configuration and reflash my backup of the stock rom, I could copy the package for swype over to the SD card to be reinstalled on CM? Even better yet, could I directly extract it from that image?
I could take the easy (warez) way out, but that isn't as appealing.
Thanks,
-Trey
Swype is open Beta last time I checked. Just go get it for yourself.
Swype extract program
If you have a nandroid backup of a ROM with functioning Swype (which it sounds like you do), there's an app around somewhere on here called SwypeRestore.apk that does it for you. Sorry I don't have it right now.
http://forum.xda-developers.com/showthread.php?t=841603
Yeah go to swypes website and get it....takes less than time than making this thread
Sent from my T-Mobile G2 using XDA App

[Q] All my apps are dissappearing.....???

Hi, im running ec05 with the urban fury rom. I made a few changes to the rom and rezipped the file and flashed the zip with the new apks i added. I used the apks from midnight rom extras 5.2, all i did was take the apks from system/app from the extras and added them to urban fury roms system/app folder. The primary reason i did this was to fix the voicemail issue as midnights rom didnt require a text message. However i ended up adding all the apks over anyway instead of just that one apk. Im just trying to find out why is it everytime i power down my phone and boot it up all the apks i installed from the market are gone...???? Im going to undo what i did in a few hours but and just try the voicemail apk, but im just curious why this happens and is there a way i can fix it? Thanks for any help....
Did you modify the apks? Sounds like they are not signed.
Sent from my SPH-D700 using XDA App
I'm having the same problem on the Urban Legend ROM, I didn't edit anything in the ROM, but everytime I reboot my apps from the market are gone and have to download again. The data files seem to stay as I don't have to reenter any information, but the app itself goes away.
Sounds like YPIR to me.
Sent from my SPH-D700 using XDA Premium App
I had this problem on all Urban Fury variations that I tried. Only thing that didn't allow me to stay on them, as a matter of fact.
What is YPIR?
Im also having this problem every single time i reboot my phone all of my apps are deleted, i try to use titanium to bring them back but thats a hassle, is there anything i can do to make this stop? im a total noob plz help!

[Q] [FOR DEVS] Cooking ROM mods directly into ROMs? [SOLVED]

I'm looking to get some assistance with a Sense ROM development question. I am a big fan of ca1ne's Sense 1.0 ROM modifications, mainly:
Quick Settings Notification: http://forum.xda-developers.com/showthread.php?t=1266626
-and-
Advanced Power Menu: http://forum.xda-developers.com/showthread.php?t=1314428
I've been working on a Sense 1.0 (stock) -based ROM and am trying to incorporate these mods directly into the build. So far I have only attempted the Quick Settings mod, but since I have not been successful, I have not moved forward yet with the other. Whenever I try to add the Quick Settings mod into the ROM, I lose the statusbar all together. I know that other devs have incorporated quick settings mods into their ROMs (Swagged Out comes to mind, IIRC), so I know that it is possible, but I have been unsuccessful.
Could anyone who has done this give me an idea of what I might be doing wrong? I've tried everything I can think of, from adding the SystemUI.apk directly to the ROM, pre-cook, to building a ROM from a NANDroid backup with the mod already installed. Each way it is the same result: no status bar. Same thing that happens if you don't allow the ROM to boot once before flashing the update.zip.
Kinda stumped! Thanks!
Perhaps this should be posted in the Development forum? Yes? No?
*bump*
I suggest pm'ing a dev about your question so you can get a direct response from them. Plus, they might be able to help you further into the development of your ROM. Just a suggestion
Sent from my PC36100 using xda premium
Not sure what your issue is. What is your starting base? A ruu or a compiled ota?
Here is a collection of EVO mods. click here
All of these came from my Rom, EVO classic. You should be able to cook any mod into a Rom. When testing, you need to perform fill wipes.
Also, are you using dsixda's kitchen to build zip?
Are you certain the apk you're testing works?
Do you know how to use apktool?
Which operating system do you work on?
These are just some general questions and troubleshooting technique.
Sent from my PC36100 using Tapatalk
tommytomatoe said:
Not sure what your issue is. What is your starting base? A ruu or a compiled ota?
Here is a collection of EVO mods. click here
All of these came from my Rom, EVO classic. You should be able to cook any mod into a Rom. When testing, you need to perform fill wipes.
Also, are you using dsixda's kitchen to build zip?
Are you certain the apk you're testing works?
Do you know how to use apktool?
Which operating system do you work on?
These are just some general questions and troubleshooting technique.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I tried a couple different starting bases. First I tried a RUU for 4.53.651.1 as pc36img.zip. Second a nandroid dump of 4.54.651 unrooted/modded installed via RUU and OTA on fresh SD card. Lastly, figuring I was messing up the base somehow, I used NinjaWolf's Rooted Stock 4.53.651.1.
I have been performing 3x cache, 3x dalvik and 1x userdata/factory reset wipes from recovery prior to each flash. Thing is that the rom that i end up with before trying to implement ca1ne's quick settings mod all flash properly and load perfectly. No issues at all. It's only after I try to combine the quick settings mod into any zip to flash that the issue arises. That being said, whenever I flash the mod over the custom rom, it works flawlessly. Just can't figure out how to get it cooked into the flashable zip.
Yes, I am using dsixda's kitchen for compiling the zips. I am still pretty new making roms, so I've not dived too far into the commands behind the scripts contained within.
To be honest, I've only used apktool a couple times. Mainly to decompile the stock SystemUI.apk and the one in ca1ne's zip, to diff. I would not say that I am fluent in it's use, by any means.
My primary machine is a Linux Mint Debian Edition box, with a Windows 7 Ultimate partition that I use for gaming and any time I need Windows (revonutionary.io, for example). Secondary is MacBook Pro (work machine), running 10.6, setup with dsixda's kitchen as per the tutorial. I work in IT/IS, so I am more than comfortable with each OS, I just prefer Linux/UNIX. I am also not a stranger to various programming and shell scripting languages, but I am not a master developer.
Hope that explains a bit more. Thanks, tommytomatoe, for your time. I really appreciate it! Also, I will take a look at your mods collection as soon as I get to my rig.
If you're using the ruu or pc36img you ate playing with odex. Ca1ne's uploaded systemui is deodex. That could explain the lack.of status bar.
Sent from my PC36100 using Tapatalk
tommytomatoe said:
If you're using the ruu or pc36img you ate playing with odex. Ca1ne's uploaded systemui is deodex. That could explain the lack.of status bar.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Yeah, I saw that was one of the requirements, but I always deodex /system/framework and /system/app on my personal builds so that the .apks can be modded or themed, should I desire to do so. When using the RUU and pc36img, I let it boot, do the OTA updates, then sync a test google account and update apps through the market. After that is done, I boot into recovery (after flashing it back with fastboot... thank you HTC) and do a nandroid backup to use as a pure stock base. Once I have the system.img and boot.img I take it to the kitchen to root, deodex, etc..
I am wondering, though, why the effect is the same if you extract the SystemUI.apk manually and drop it into the ROM as it does if you immediatly flash the quick settings zip directly after a fresh rom flash, without allowing the rom to boot up completely first. I can see a minor coorelation, but if I can figure out whatever dependancy I am missing, then I know I should be able to get it to work.
grayn0de said:
Yeah, I saw that was one of the requirements, but I always deodex /system/framework and /system/app on my personal builds so that the .apks can be modded or themed, should I desire to do so. When using the RUU and pc36img, I let it boot, do the OTA updates, then sync a test google account and update apps through the market. After that is done, I boot into recovery (after flashing it back with fastboot... thank you HTC) and do a nandroid backup to use as a pure stock base. Once I have the system.img and boot.img I take it to the kitchen to root, deodex, etc..
I am wondering, though, why the effect is the same if you extract the SystemUI.apk manually and drop it into the ROM as it does if you immediatly flash the quick settings zip directly after a fresh rom flash, without allowing the rom to boot up completely first. I can see a minor coorelation, but if I can figure out whatever dependancy I am missing, then I know I should be able to get it to work.
Click to expand...
Click to collapse
Why use the nandroid images? Just use the pc36img.zip
If the file itself gives you that issue then I would recommend duplicating that mod on your own systemui. There are always traces of signature and permissions issues using a different file than your own, unless you know how to disable signature verification.
I don't ever recommend creating roms from nandroid image. Just stick with the pc36img
Lastly. And I truly wish this rumor was never created. Odex can be themed, modded, and customized just like deodex
Sent from my PC36100 using Tapatalk
Not clear on how exactly to apply the OTA patches to the pc36img without going the route I have been taking. Although, I really don't think there was much to this latest OTA security update that actually benefits the user anyway, so I might just stick with the 4.53 base for now. At least until I figure out this quick settings stuff.
I'll decompile the two apks and diff them to see if I can duplicate the mod, as you suggest.
You know I kinda thought that it was odd that people said that, as there have been themes since early ADP1 days. Guess I figured it was just something to chalk up to changes across OS versions. So is deodex just easier to theme/mod, since the dex file is recompiled into the apk? One less piece, so to speak?
Look here.
http://forum.xda-developers.com/showthread.php?t=1320660
Pull those files from the 4.54 ota. Use the pc36img from latest available, 4.53. In kitchen, select the pc36img.zip as your working rom. Then apply the changes as laid out in the thread I linked you. Hope that helps.
Sent from my PC36100 using Tapatalk
Seems simple enough. Thank you!.
I found this while looking for something else and gave it a shot hoping that it would, on the off chance work, but no love:
http://forum.xda-developers.com/showthread.php?t=1290753
I'm still digging into the original and modded SystemUI.apk files to see what I need to do to duplicate the quick settings. Also, I've been checking out your android-utility. Awesome work, man!
I figured it out the issue.
I decompiled both the original and modded apk files, then used DiffMerge to diff the project folders for the apks. This brought up a list of files that had been modified, one of which was:
res/drawable-hdpi/statusbar_background_transparent.9.png
After merging changes in all of the .smali files, this file was the only one that remained to be modified but, since it is a binary png, I could not do so. The first time I tried to reconstruct the mod, I simply copied the modded .png file into the proper spot of my SystemUI.apk, then recompiled with original META-INF, signed it and dropped it into the ROM's working folder. Failure...
Second time around, I simply omitted the .png and tested. Worked perfectly!
tommytomatoe: Thanks a ton for all of your insight and advice (in this thread and others). It has really helped me out. Now that this little hurdle has been leaped, I can continue on with the ROM revisions!

Categories

Resources