• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Flashable mms fix?

nitestalkr

Android Enthusiast
Does anyone know if there is, or if its possible to make, a flashable mms fix?
I'm working on making a 100% Optimus S to Optimus V flashable porting patch, that can be used to port every and any Optimus S rom, to be used on the Optimus V, and the only thing my patch is missing is an MMS fix. It already contains a Data/sms/service fix, and a button swap fix. All it needs is an MMS fix that can be flashable.
It would be flashed directly after flashing an Optimus s rom.
I can already confirm that what I have so far works, but I wont release the 1 step flashable port, until it has the MMS fix in it.
Any help?
 
They had a flashable zip made by ath3nos about a year ago for flashing optimus s roms on the optimus v. You might want to contact him about it. Here is the old thread, it had since been archived.

forums.androidcentral.com/optimus-v-archived-roms-hacks/102027-rom-ish-ov-port-ath3noss-unofficial-cm7-gingerbread-7-15-a.html
 
They had a flashable zip made by ath3nos about a year ago for flashing optimus s roms on the optimus v. You might want to contact him about it. Here is the old thread, it had since been archived.

ARCHIVED: [ROM-ish] OV Port of ath3nos's Unofficial CM7 (Gingerbread) 7/15 - Android Forums at AndroidCentral.com

If he's still around that is..
And i guess I'm recreating something, unaware that it existed, for the new generation of optimus V users. :p
And his fix has been removed from media fire sadly.
 
If he's still around that is..
And i guess I'm recreating something, unaware that it existed, for the new generation of optimus V users. :p
And his fix has been removed from media fire sadly.


Maybe there was a reason he removed porting ZVJ to ZVD??? these libs we are using did not exist.......maybe the old ones had issues O.o
 
Have you tried pulling both framework.jar files from the ROM's, extract, decompile, swapp the necessary files, and then recompile the ROM your trying to port's framework.jar. Then put it back into the framework folder unsigned.

You will have to do this with every ROM as the framework.jar is a little different on each one.

Unless you can come up with a standard zip file that can be unzipped with a Text Document describing how to swap out the necessary file's that are included in the zip.

If there porting ROM's they need to learn how to deal with editing the .jar either with APK Tool or APK Multi-Tool.
 
Have you tried pulling both framework.jar files from the ROM's, extract, decompile, swapp the necessary files, and then recompile the ROM your trying to port's framework.jar. Then put it back into the framework folder unsigned.

You will have to do this with every ROM as the framework.jar is a little different on each one.

Unless you can come up with a standard zip file that can be unzipped with a Text Document describing how to swap out the necessary file's that are included in the zip.

If there porting ROM's they need to learn how to deal with editing the .jar either with APK Tool or APK Multi-Tool.

Thing is, I'm not doing a rom specific port. I'm doing a universal Optimus S to Optimus V port patch, to be used with any and all Optimus S roms (flash Optimus s rom, flash my patch over it). So anything rom specific (framework edits, build prop edits ) will not be added to my patch.
Some users have said MMS works with my patch, and data requires the phone to be reactivated.

sent from my un-dead sammich.
 
Refer to this to see my progress. (Same thread can be found at android central, and does contain a lot more feedback and testing reports)

http://androidforums.com/showthread...rting ANY OptiS rom to the OptiV in 1 Flash!!
 
I thought the files that I was referring to (can't recall their name's) were the exact same no matter what V ROM's framework.jar you pulled them out of.
I was just figuring it would just speed up the process. Instead of having to extract, decompile, pull from the host ROM's framework.jar and then extract, decompile , swap and then recompile for the Ported ROM's framework.jar; all you would have to do is extract, decompile and then swap the files from the zip into the Ported ROM's framework.jar and recompile. Mucho time saved.

Just bouncing ideas at you in response to your thread question.
 
I thought the files that I was referring to (can't recall their name's) were the exact same no matter what V ROM's framework.jar you pulled them out of.
I was just figuring it would just speed up the process. Instead of having to extract, decompile, pull from the host ROM's framework.jar and then extract, decompile , swap and then recompile for the Ported ROM's framework.jar; all you would have to do is extract, decompile and then swap the files from the zip into the Ported ROM's framework.jar and recompile. Mucho time saved.

Just bouncing ideas at you in response to your thread question.

I know, and I do appreciate it a lot, you've provided a lot more information than most users have, but like I said, trying to make a universal (Optimus S to V) MMS flashable fix, so if files are exactly the same in all Optimus S roms (GB, ICS, JB), then I can use them. AFAIK, build.prop, framework-Res.apk are ROM specific. If they aren't, they I can easily include Optimus V versions to be flashed over the Optimus S ones.
 
I don't think making a universal flashable zip to fix mms and data from one phone's ROM's to another phone is going to happen.
 
Back
Top Bottom