[GUIDE][TUTORIAL]So, you want to port a rom to the MT4GS? - T-Mobile myTouch 4G Slide

Ok, porting roms to our device is actually very easy. i am going to put together a guide for those of you who wish to port a rom to this device. This may not be the best method and may not work 100% of the time but it does work. As long as you follow this guide you should not hurt your device. That being said i take no responsibility for your actions you are doing this on your own accord.
To get started you will need to make sure you have a few programs set up on your windows PC:
7zip - http://www.7-zip.org/
notepad++ - http://notepad-plus-plus.org/
ADB - http://forum.xda-developers.com/showthread.php?t=928370
Apktoolv3 - http://forum.xda-developers.com/showpost.php?p=32649311&postcount=4
Also, you will need to know the terminology for this guide:
base rom - the rom already designed for the MT4GS
port rom - the rom you wish to bring over to the MT4GS
First step is to extract (using 7zip) both your base rom and your port rom into seperate folders
In your base rom you need to delete the following folders from system: apps, fonts, framework, and media
in your port rom you need to copy the same folders: apps, fonts, framework, and media; then paste them into your base rom
next open up the bin folder from port rom and copy all; now paste in base rom bin folder. BUT we only want what is not already there so when you use the paste command windows should prompt you that multiple files are already present in that folder. you want to select DO NOT COPY and do that for all the files.
now you need to do the same procedure for the the xbin folder. (you will need to copy the su file from port rom and paste to base rom)
Then you will need to open the etc folder and you will need to do the copy & paste trick with init.d and permissions folders
stay in the etc folder. underneath all the folders you will notice several "loose" files. use the same copy & paste trick so all additional files will be in your base rom.
after that we move on to the lib folder. we will use the same copy & paste trick. when you have the extra libs moved you will need to copy the following libs from port rom and paste them to base rom: libandroid_servers.so and libmedia_jni.so
you will need to open both port rom and base rom build.prop with notepad++. you need to make these following lines match the port rom:
ro.build.id
ro.build.display.id
ro.build.version.incremental
ro.config.ringtone
ro.config.notification_sound
ro.config.alarm_alert
Last zip your rom and flash it. if it boots you will need to move on to the next post. if it doesnt boot you will need to get a logcat to see what the problem is. if you want anyone here to look at make sure you use pastebin.

OK, you got your rom to boot!!! except your keyboards are all jacked up. This is the known fixes for the MT4GS!
you will need the framework-res apk from your booted rom and paste it to the root of your apktoolv3 folder.
you will need to decompile framework-res with the following command:
apktool d framework-res.apk
this will create a folder inside apktool titled "framework-res". open this folder and navigate to res>values
you will need to open bools.xml and integers.xml with notepad++
lets start with bools.xml
<bool name="config_forceDisableHardwareKeyboard">false</bool> change false to true
save bools.xml
in integers.xml you need to make the following changes:
<integer name="config_lidOpenRotation">90</integer>
<integer name="config_lidKeyboardAccessibility">1</integer>
<integer name="config_lidNavigationAccessibility">1</integer>
save integers.xml
run the following command to rebuild framework-res:
apktool b framework-res
your finished product will be in the "dist" folder.
last step is to open your new framework-res.apk and the original with 7zip. (DO NOT extract only open archive)
copy META-INF folder as well as AndroidManifest.xml from the orignal and paste to your new framework-res.
add framework-res.apk to your rom and zip it up.

Points of Reference
http://forum.xda-developers.com/showthread.php?t=1777999
http://forum.xda-developers.com/showthread.php?t=1598713
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=2113479

MAN!! That is one AWESOME guide there Bro! Now THAT should be insprirational to anyone that's ever dreamed of pulling over a port! NICE JOB!!!!!:good:
....and unless I overlooked it, you should mention that any extra folders in "system" in your port ROM that don't exist in you base need to be copied over too. (I don't know of the times I've forgotten that one!)
OH....and BTW, I've found that a copy of Winmerge is a HUGE help in comparing the files you need to compare for continuity & content. Namely the build.prop & updater-script files. It will save back to the proper format like Notepad++ will. (thanks Strapped365) :good:

Re: [GUIDE]So, you want to port a rom to the MT4GS?
So is anyone trying this?
Sent from my SGH-T889 using Tapatalk 2

I am, but I don't think I count.

can it be done on a pre-made rom or gotta start from scratch?

Re: [GUIDE]So, you want to port a rom to the MT4GS?
crimedave1987 said:
can it be done on a pre-made rom or gotta start from scratch?
Click to expand...
Click to collapse
This is for AOSP. Its the same guide SWaRM uses for our ports.
Sent From SaberMod using my Nexus 4

Re: [GUIDE]So, you want to port a rom to the MT4GS?
Use any cm or aokp base.
Sent from my SGH-T889 using Tapatalk 2

cool thanks

crimedave1987 said:
cool thanks
Click to expand...
Click to collapse
Good Luck! ....and don't get discouraged!

Re: [GUIDE]So, you want to port a rom to the MT4GS?
Thanks for this guide. I've learned so much with this device & following the development threads from the solid developers we have(had). I truly appreciate your work & willingness to share.
Sent from my KFTT using xda premium

Re: [GUIDE]So, you want to port a rom to the MT4GS?
etom said:
Thanks for this guide. I've learned so much with this device & following the development threads from the solid developers we have(had). I truly appreciate your work & willingness to share.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
No problem. If you have any issues post them here
Sent from my SGH-T889 using Tapatalk 2

Re: [GUIDE]So, you want to port a rom to the MT4GS?
mattlowry said:
No problem. If you have any issues post them here
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Yeah one of us will get him right huh.
*
Has this worked for anyone yet? Or still no attempts
Sent From a Freaked out Nexus 4

strapped365 said:
Yeah one of us will get him right huh.
*
Has this worked for anyone yet? Or still no attempts
Sent From a Freaked out Nexus 4
Click to expand...
Click to collapse
I'll be trying during spring break. No time for me between work and school since the end of the term is creeping up.

strapped365 said:
Yeah one of us will get him right huh.
*
Has this worked for anyone yet? Or still no attempts
Sent From a Freaked out Nexus 4
Click to expand...
Click to collapse
It's given me another NICE one. I just haven't figured out where it recognizing external storage went. Don't I remember you saying you ran across this when you were building XE.....or is that just my "wishful" thinking?
Actually, I would have thunk people would have been all OVER this post!

Re: [GUIDE]So, you want to port a rom to the MT4GS?
I have midwinter break so I'll try this in a couple day just don't know what ROM to port
Sent from my MyTouch Slide 4G using Tapatalk 2

wiswis said:
I have midwinter break so I'll try this in a couple day just don't know what ROM to port
Sent from my MyTouch Slide 4G using Tapatalk 2
Click to expand...
Click to collapse
The very first thing to consider for simplicity's sake is to match one using the same processor. You can do that from HERE.
Secondly, gravitate to one with our screen size. (800x480) That will keep you away from ports that you'll have to resize a bunch of stuff in. You can find those HERE.
Then you just go to those developement threads & start shopping! LOL:laugh:
And GOOD LUCK! :good:

Re: [GUIDE]So, you want to port a rom to the MT4GS?
wiswis said:
I have midwinter break so I'll try this in a couple day just don't know what ROM to port
Sent from my MyTouch Slide 4G using Tapatalk 2
Click to expand...
Click to collapse
Could always try to port a pure Google ROM . I know anything that's Paranoid Android 3+ is based off Google source code as is much more stable than anything CM I've seen yet. It don't have as many tweaks and such BUT its pure
Sent from my Nexus 4 using Tapatalk 2

strapped365 said:
Could always try to port a pure Google ROM . I know anything that's Paranoid Android 3+ is based off Google source code as is much more stable than anything CM I've seen yet. It don't have as many tweaks and such BUT its pure
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Would that mean A base CM4.1 or 4.2 ROM or AOKP?

Related

[MOD]*done* Add reboot,recovery,download mode to power off menu

Disclaimer: I am not responsible for what happens to your phone-use at your own risk. Always do a nandroid backup before using mods
This is a port of untermensch's vibrant mod found here: http://forum.xda-developers.com/showthread.php?t=811532
*completed mod now available with aosp lockscreen included*
*note: these mods include framework-res.apk and need to be included in the base of a theme or rom/flashing over the top of one will overwrite previous theming done to framework-res with stock images and break some pre-existing mods*
Thanx and credit to him for getting me this far, I have made a few changes to his instructions to make it work on epic. The below mod only has the reboot option added. I have yet to try his latest instructions to add reboot recovery but it might work too. Just wanted to get this over to the Epic side for discussion and help if it isn't as easy to port the rest of it.
Add reboot option to power off menu http://www.mediafire.com/?hoetfjbq77hm77s flash in clockwork recovery (its only android policy.jar) and make sure your system is deodexed. We can add more things into it to get android policy jar mods to play together later.
Here's a .zip that has both the AOSP lockscreen mod and reboot button mod together: http://www.mediafire.com/?010dchn522nxge9
Complete mod port plus aosp lockscreen click here
Note: this .zip includes framework-res.apk,framework.jar and android.policy. jar. The recovery function gets you to stock recovery but you can still get into clockwork by flashing the update.zip you should have on your sdcard already. If any one knows how to get it to go straight to clockwork like rom manager does I would like to have it do that.
Complete mod port plus aosp lockscreen-no full battery popups click here
All three in one now, this is just like the one above but also has services.jar
Complete mod port only click here
Includes framework-res.apk,framework.jar and android.policy.jar
Complete mod port with no popups click here
Includes framework-res.apk,framework.jar,services.jar and android.policy. jar
Works Perfect.....Ty
Sent from my SPH-D700 using Tapatalk
raiderep said:
This is a port of untermensch's vibrant mod found here: http://forum.xda-developers.com/showthread.php?t=811532
Thanx and credit to him for getting me this far, I have made a few changes to his instructions to make it work on epic. The below mod only has the reboot option added. I have yet to try his latest instructions to add reboot recovery but it might work too. Just wanted to get this over to the Epic side for discussion and help if it isn't as easy to port the rest of it.
Add reboot option to power off menu http://www.mediafire.com/?hoetfjbq77hm77s flash in clockwork recovery (its only android policy.jar) and make sure your system is deodexed. We can add more things into it to get android policy jar mods to play together later.
The reboot recovery mod looks like it will need framework mods as well if you are interested in trying to get the rest of this going. Care to jumpin?
Click to expand...
Click to collapse
Has this been tested?
just asking cause yesterday I flashed a normal app! flash 10.1 and my phone was stuck blackscreened lol and had to odin ect AND I am very happy with the phone now so I dont wan't to result to that again
I've been waiting for this to get ported - thank you!
It flashed with no problem, but it replaced my Vanilla lock screen with the TouchWiz one. If I flash the Vanilla lock screen back on, will the reboot option still be there?
Holdin down power+voldown+camera after touching reboot gets you into recovery. I know a software button is better but in the mean time.
Sent from my Android using CDMA or WIFI
265ada said:
Has this been tested?
just asking cause yesterday I flashed a normal app! flash 10.1 and my phone was stuck blackscreened lol and had to odin ect AND I am very happy with the phone now so I dont wan't to result to that again
Click to expand...
Click to collapse
I've been using it for a few days with no issues. The only thing that might happen is what happened to ragnarox, read his quote below...
ragnarokx said:
It flashed with no problem, but it replaced my Vanilla lock screen with the TouchWiz one. If I flash the Vanilla lock screen back on, will the reboot option still be there?
Click to expand...
Click to collapse
Until both are put into the same AndroidPolicy.jar then its one or the other. I will get them both together eventually, this is just a start
and here you go, both together now: http://www.mediafire.com/?010dchn522nxge9
raiderep said:
I've been using it for a few days with no issues. The only thing that might happen is what happened to ragnarox, read his quote below...
Until both are put into the same AndroidPolicy.jar then its one or the other. I will get them both together eventually, this is just a start
and here you go, both together now: http://www.mediafire.com/?010dchn522nxge9
Click to expand...
Click to collapse
You are amazing, thank you!
OP updated with completed mod coupled with aosp lockscreen
Is that a soft key to get into download moss I see?
Sent from my Emotionless Beast of an Epic using the XDA App
mysteryemotionz said:
Is that a soft key to get into download moss I see?
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
Yes indeed not sure how much need there is for it but it was in the mod so I added it also.
Mediafire not working for me. Using Opera, ie and epic to try to dl.
raiderep said:
Yes indeed not sure how much need there is for it but it was in the mod so I added it also.
Click to expand...
Click to collapse
That's nice. I know we talked in private but u got an idea to make this work with my theme. This is going to be interesting
Sent from my Emotionless Beast of an Epic using the XDA App
What update.zip gets you into clockwork by using stock recovery?
Sent from my spot on the earth
deciple said:
What update.zip gets you into clockwork by using stock recovery?
Sent from my spot on the earth
Click to expand...
Click to collapse
It should haber been installed when you flashed CWM on you're phone
Sent from my Emotionless Beast of an Epic using the XDA App
Ok, yeah, in my clockworkmod folder I found the (recovery-update.zip) file, however, for those who don't know, you have to rename it just update and it works
Sent from my spot on the earth
mysteryemotionz said:
That's nice. I know we talked in private but u got an idea to make this work with my theme. This is going to be interesting
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
The only way for certain is to re-theme this framwork-res with your images. You might try swapping just your drawable-hdpi folder into this one and if there is anything left out track it down and add it back. I am not sure where values folder goes when it re-compiled so you don't want to write over it as it will cause issues.
OP has a new .zip with all three mods in one now, let me know if there are any issues with it.
sent by an Epic4g through the cosmos
raiderep said:
The only way for certain is to re-theme this framwork-res with your images. You might try swapping just your drawable-hdpi folder into this one and if there is anything left out track it down and add it back. I am not sure where values folder goes when it re-compiled so you don't want to write over it as it will cause issues.
OP has a new .zip with all three mods in one now, let me know if there are any issues with it.
sent by an Epic4g through the cosmos
Click to expand...
Click to collapse
This was my plan but I also edited some xml files. So if I just drop the hole contents of my framework in yours replacing everything but the values folder in theory I should be good?
Sent from my Emotionless Beast of an Epic using the XDA App
mysteryemotionz said:
This was my plan but I also edited some xml files. So if I just drop the hole contents of my framework in yours replacing everything but the values folder in theory I should be good?
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
What xmls did you edit? What I was getting at is use this as a base and re-do the theme to it but if you accidentally over write the values folder it will not work properly. Since I don't know where valuse goes when its been compiled(it only shows when decompiled) you run the risk of breaking the mod. Its certainlgy worth a shot though.
sent by an Epic4g through the cosmos
raiderep said:
What xmls did you edit? What I was getting at is use this as a base and re-do the theme to it but if you accidentally over write the values folder it will not work properly. Since I don't know where valuse goes when its been compiled(it only shows when decompiled) you run the risk of breaking the mod. Its certainlgy worth a shot though.
sent by an Epic4g through the cosmos
Click to expand...
Click to collapse
I moved the clock down on the tw lock screen. Its in the layout folder named zz_keyguard_clock.xml I believe this is coming off the top of my head
Sent from my Emotionless Beast of an Epic using the XDA App

[TOOL][PORT] Autodeodexer 2.3a for the Epic 4G Froyo - Windows

Honestly, I do not know how much interest there will be in this, but throughout my own exploration and experimentation with Android and the Epic 4G I feel like sharing my finds with the community.
I kanged this tool from HERE so thanks to Daneshm90 among other people who are thanked in the tool itself. All I really did was add a few BOOTCLASSPATHS to the *APK.bat files to get it to deodex all the apks, and update smali/baksmali to version 1.2.6 (newest as of 3/25/11).
Basically this is a one click tool to deodex stock, odexed system/framework and system/app folders on a windows machine. I tested on the ACS Untouched Stock EC05 ROM and got clean runs where everything became deodexed.
Tips: I found it best to do system/framework first in one run, then leave the output in deodexed_JAR, and THEN process system/app as many of the files in the app folder have dependencies on the jars.
After processing system/framework you will have framework-res.apk and twframework-res.apk which do not need deodexing.
In early testing, I found certain files leftover after a run processed on the next run. This stopped after updating smali/baksmali. I doubt I'll be of much help if you run into problems, you are doing EVERYTHING at your own risk. I barely understand the details here, I just ported it to work on our phone, so good luck!
Deodexed 2.3a Download
Thanks for this!
Good tool for those that want stock with.a theme.
Sent From My Evo Killer!
Mind if I throw this in the EPIC 4G cookbook?
amosher13 said:
Honestly, I do not know how much interest there will be in this, but throughout my own exploration and experimentation with Android and the Epic 4G I feel like sharing my finds with the community.
I kanged this tool from HERE so thanks to Daneshm90 among other people who are thanked in the tool itself. All I really did was add a few BOOTCLASSPATHS to the *APK.bat files to get it to deodex all the apks, and update smali/baksmali to version 1.2.6 (newest as of 3/25/11).
Basically this is a one click tool to deodex stock, odexed system/framework and system/app folders on a windows machine. I tested on the ACS Untouched Stock EC05 ROM and got clean runs where everything became deodexed.
Tips: I found it best to do system/framework first in one run, then leave the output in deodexed_JAR, and THEN process system/app as many of the files in the app folder have dependencies on the jars.
After processing system/framework you will have framework-res.apk and twframework-res.apk which do not need deodexing.
In early testing, I found certain files leftover after a run processed on the next run. This stopped after updating smali/baksmali. I doubt I'll be of much help if you run into problems, you are doing EVERYTHING at your own risk. I barely understand the details here, I just ported it to work on our phone, so good luck!
Deodexed 2.3a Download
Click to expand...
Click to collapse
This is awesome...... GREAT WORK.....
Okay so this sounds interesting and all...But how does one use it??
tphillips said:
Mind if I throw this in the EPIC 4G cookbook?
Click to expand...
Click to collapse
Go right ahead!
sent from my mind to yours
youngpro83 said:
Okay so this sounds interesting and all...But how does one use it??
Click to expand...
Click to collapse
Just take an odexed frame work, put it in the folder and run deoall.bat, then repeat for app. Pretty much it, if you don't know the point then you probably don't need it, lol
sent from my mind to yours
Thanks dude
Thanks bro good work
Anyone give this a shot yet?
blazinazn said:
Anyone give this a shot yet?
Click to expand...
Click to collapse
Yea I tried using it to deodex my eco5 stock rom, and it ran clean and gave output, but the output wouldn't boot.. I ended up going a diff route which included using a tool made for another phone and doing some by hand...
Sent from my SPH-D700 using XDA App

[MOD] AOSP JellyBean Carrier Name Change

For those of you who are using cm10 builds and are tired of seeing Verizon Wireless on your lockscreen and notification pulldown this will allow you to remove or change it to something else. I take no credit for this all credit goes to spunks3 for making the post over in the nexus forums, I just tried his method and it happened to work on our phone, also belair56 for the original find as well as dakota0206 for his post on the thread giving the correct eri.xml.
PLEASE NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE, MAKE A NANDROID BACKUP BEFORE ATTEMPTING ANY MODS SUCH AS THIS!
1) Download eri.xml onto your desktop or some folder you will remember where it has been placed.
2) Open "eri.xml" with something such as NotePad or WordPad and edit everywhere you see "Whatever you want or delete this and nothing will show up". You can simply change the text or delete the text between the quotations and nothing will show up.
3) Save "eri.xml" and copy it to the root of your SD Card.
4) Open Root Explorer or an app similar, copy "eri.xml" from your SD card to "/data" directory. Please make sure you are not placing it in /sdcard/data
5) Also make sure that eri.xml has the same permissions as in the thumbnail below.
6) Reboot, and Enjoy!
eri.xml here http://www.mediafire.com/?x0x8kqyapnws4sc
Confirmed working on paranoid android version 2.13
Hey thanks for this! I'm also using PA2.13 so should be easy. May I ask where you got that battery circle mod? In the meantime I'll search it. Thanks again.
http://forum.xda-developers.com/showthread.php?t=1851311&highlight=circle+battery
was this it? Sorry to crowd the thread.
BTW got it working =D
Glad you got it working and actually I just pulled the images from an old copy of my systemui.apk when I had syngergy rom. Just modded my current systemui.apk, swapped out the images and edited the appropriate xmls.
Just tried on Paranoid 2.13 and it didnt work for me
Hanoverfiste said:
Just tried on Paranoid 2.13 and it didnt work for me
Click to expand...
Click to collapse
It shouldn't really make any difference but what kernel are you using and did you follow the directions exactly? Also make sure you are putting eri.xml in /data and not in /sdcard/data also make sure eri.xml has the following permissions in the picture below.
Hanoverfiste said:
Just tried on Paranoid 2.13 and it didnt work for me
Click to expand...
Click to collapse
It wasn't working for me either until I changed the permissions to above. Do any of the other comments in that file do anything? Kinda weird that it isn't there in the first place. Thanks, op.
natethegreat86 said:
It shouldn't really make any difference but what kernel are you using and did you follow the directions exactly? Also make sure you are putting eri.xml in /data and not in /sdcard/data also make sure eri.xml has the following permissions in the picture below.
Click to expand...
Click to collapse
Thanks I didnt have it in /data had it in /sdcard/data. and look what happens when you put things where they are supposed to go they actually work
Imatoasta said:
It wasn't working for me either until I changed the permissions to above. Do any of the other comments in that file do anything? Kinda weird that it isn't there in the first place. Thanks, op.
Click to expand...
Click to collapse
Its just how the original xml was it doesn't do anything in fact if you really wanted to you could delete all the text above this first line
<EriFile VersionNumber="1357" NumberOfEriEntries="19" EriFileType="1">
And glad the permissions fixed it for you
This is pretty cool. Thanks for testing it and posting.
Sent from SCH-I535 (CM10 0920) via XDA Premium
Glad to see so many people using and enjoying this I know I was tired of seeing verizon anything lol.
Thanks. I used to use this on my HTC Hero, but had forgotten how to do it.
Works on Sprint CM10 S3 :good:
If anyone has any issues or questions feel free to post so I can answer etc.
natethegreat86 said:
If anyone has any issues or questions feel free to post so I can answer etc.
Click to expand...
Click to collapse
It works for me
natethegreat86 said:
If anyone has any issues or questions feel free to post so I can answer etc.
Click to expand...
Click to collapse
Is this only for AOSP JB ROMs? It doesn't seem to work on Synergy JB v.2.
mapatton82 said:
Is this only for AOSP JB ROMs? It doesn't seem to work on Synergy JB v.2.
Click to expand...
Click to collapse
Is that a touchwiz Rom? Sorry I'm not familiar with Verizon roms but Touchwiz roms need to have a value changed in the framework. Not as easy as this eri.xml
Sent from my Samsung Galaxy SIII using Tapatalk
Bizdady said:
Is that a touchwiz Rom? Sorry I'm not familiar with Verizon roms but Touchwiz roms need to have a value changed in the framework. Not as easy as this eri.xml
Sent from my Samsung Galaxy SIII using Tapatalk
Click to expand...
Click to collapse
Yeah it is a Touchwiz rom based on AT&T's JB leak. I will take a look in the framework.
Anyone wanna make a flashable zip for just Verizon Wireless. That would be awesome
Sent from my SCH-I535 using xda app-developers app
mapatton82 said:
Yeah it is a Touchwiz rom based on AT&T's JB leak. I will take a look in the framework.
Click to expand...
Click to collapse
\res\values\Strings.xml
last line at the bottom (at least for Sprint it is)
Bizdady said:
\res\values\Strings.xml
last line at the bottom (at least for Sprint it is)
Click to expand...
Click to collapse
I just ran a search for eri.xml and string.xml on my Verizon S3 running JellyWiz and didn't find either file.
Sent from my SCH-I535 using Tapatalk 2

[HOW-TO] Port US S3 ROMs between carriers

Porting TouchWiz ROMs​
This guide is intended to help you port ROMs from AT&T, T-Mobile, and Sprint over to the Verizon S3. The guide will be split into two different parts. Porting CDMA to CDMA and porting CDMA to GSM.
Just so there's no confusion:
CDMA Carriers:
Verizon
Sprint
GSM Carriers:
AT&T
T-Mobile
REMEMBER: If you choose to port a ROM from another carrier, be sure to ask permission to post from the developer.
What you need
7zip
Notepad++ (If on Windows)
A ROM you want to port
A ROM from your carrier/device
Knowledge on how to compile and recompile .jar files (I will not cover this)
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.2) and have the same chip (e.g. MSM8960). You will be able to determine the chip type from the build.prop​
PORTING CDMA TO CDMA (i.e. SPRINT TO VERIZON)​
Download the ROM you want to port
Download a ROM from your carrier
Unzip both ROMS
In the ROM you want to port - delete /system/etc/apns-conf.xml
Replace the apns-conf.xml you just deleted with the one from the ROM for your carrier
In the ROM you want to port - delete /system/framework/GlobalConfig.jar (This .jar file contains a lot of carrier information)
Replace the GlobalConfig.jar you just deleted with the one from the ROM for your carrier
In the ROM for your carrier, locate the following lib files in system/lib and copy them over to the ROM you want to port
libreference-ril.so
libril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libsecril-client.so
If your carrier is Verizon and you're porting a Sprint ROM, delete all the apps with "Sprint" in the name including these:
SecContacts.apk
SecPhone.apk
PhoneInfo.apk
Replace SecContacts.apk and SecPhone.apk with the Verizon ones.​
In the ROM you want to port - open up /system/build.prop in Notepad++
Locate every instance of d2att, d2tmo, or d2spr and replace it with d2vzw (Use CTRL+F if you have to)
Save the build.prop after all changes are made
In system/framework/ of BOTH ROMs, decompile framework.jar and framework2.jar
In the framework.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/android/service
smali/com/android/internal/telephony
Replace them with the folders from the ROM for your carrier
In the framework2.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/com/android/internal/telephony
smali/com/google/android/mms
Replace them with the folders from the ROM for your carrier
Build all of the jar files when finished (Please note that replacing the above folders will make the ROM operational to the point where MMS will work, but you may encounter other weird superficial errors. It's just too much work to go into the specifics.)
Re-zip the ROM you want to port
Flash in recovery
PORTING CDMA TO GSM (i.e. VERIZON TO T-MOBILE & ATT / SPRINT TO T-MOBILE & ATT)​
Download the ROM you want to port
Download a ROM from your carrier
Unzip both ROMS
In the ROM you want to port - delete /system/etc/apns-conf.xml
Replace the apns-conf.xml you just deleted with the one from the ROM for your carrier
In the ROM you want to port - delete /system/framework/GlobalConfig.jar (This .jar file contains a lot of carrier information)
Replace the GlobalConfig.jar you just deleted with the one from the ROM for your carrier
In the ROM for your carrier, locate the following lib files in system/lib and copy them over to the ROM you want to port
libreference-ril.so
libril.so
libril-qc-qmi-1.so
libril-qcril-hook-oem.so
libsecril-client.so
Delete the following apps and replace them with the ones from your carrier:
SecContacts.apk
SecPhone.apk
In the ROM you want to port - open up /system/build.prop in Notepad++
Locate every instance of d2att, d2tmo, or d2spr and replace it with d2vzw (Use CTRL+F if you have to)
Save the build.prop after all changes are made
In system/framework/ of BOTH ROMs, decompile android.policy.jar, framework.jar, framework2.jar, and services.jar
You need to go through every smali file in all of the .jars and replace all instances of "Sprint" with "Verizon" or "Verizon" with "Sprint" depending on your carrier
In the framework.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/android/service
smali/com/android/internal/telephony
Replace them with the folders from the ROM for your carrier
In the framework2.jar of the ROM you want to port - delete the following folders:
smali/android/provider
smali/android/telephony
smali/android/server
smali/com/android/internal/telephony
smali/com/google/android/mms
Replace them with the folders from the ROM for your carrier
Build all of the jar files when finished (Please note that replacing the above folders will make the ROM operational to the point where MMS will work, but you may encounter other weird superficial errors. It's just too much work to go into the specifics.)
Navigate to system/framework/ in both ROMs
Open framework-res.apk from both ROMs in 7zip
In framework-res.apk in both ROMs navigate to /res/xml/
Delete eri.xml from the framework-res in the ROM you want to port
Replace the deleted eri.xml with the one from the ROM for your carrier
Save and close the modified framework-res.apk
Re-zip the ROM you want to port
Flash in recovery
Obviously this guide will not work on more difficult ports such as bringing Sense to the S3, but the end result is that we will hopefully see more ROMs in the thread.
Thanks TrevE
Porting AOSP ROMs
================================ START ================================​
What you need
7zip
Notepad++ (If on Windows)
An AOSP ROM you want to port
An AOSP ROM from your carrier/device
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.1)​
I will do the AOSP porting section with an example. Say I want to port Paranoid Android:
Download Paranoid Android (Android 4.2)
Download CM10.1 (Android 4.2)
Unzip both ROMs
In the CM 10.1 folder delete the following folders/files:
/system/framework
/system/app
/system/lib/libandroid_runtime.so
/system/media (optional)
/system/fonts (optional)
Add the following folders from the PA ROM into the CM10.1 ROM:
/system/framework
/system/app
/system/lib/libandroid_runtime.so
/system/media (only if you deleted from CM10.1)
/system/fonts (only if you deleted from CM10.1)
Only do the following if you are porting from GSM to CDMA or CDMA to GSM (i.e. Porting an AT&T ROM to Verizon)
Navigate to system/framework/ in both ROMs
Open framework-res.apk from both ROMs in 7zip
In framework-res.apk in both ROMs navigate to /res/xml/
Delete eri.xml
Replace the deleted eri.xml with the one from your base ROM
Save and close framework-res.apk
Re-zip and flash in recovery
================================ END ================================​
If the ROM does not boot up, try a different ROM. For example, if you tried to port Paranoid Android 4.2 from AT&T and it didn't work. Try Paranoid Android from T-Mobile or the Galaxy Nexus, etc.
Wicked Sensation: http://www.androidfilehost.com/?fid=9390248398092763137
This ROM is completely based on Sprint's OTA. It will work with KindaCrapMods due to the framework being about 95% similar to the Verizon version. However, the 5% difference may induce abnormal behavior such as irregular lockscreen clock readings. Also, the ROM does not include any tweaks outside of what is present in the original release.
I WILL NOT be maintaining this ROM so if you want to see updates, start a thread for it.
Great writeup pure. Truly an asset to this community
Sent from my SCH-I535 using xda premium
epicroot said:
Great writeup pure. Truly an asset to this community
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hopefully we will see more ROMs in the future.
Wicked Sensation is uploaded.
Did you happen to do a test flash? Or just edit, zip and go
Sent from my SCH-I535 using xda premium
epicroot said:
Did you happen to do a test flash? Or just edit, zip and go
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Flashed it. Booted up. I did a reboot just to test, and then reverted to my ROM to continue development lol.
PureMotive said:
Flashed it. Booted up. I did a reboot just to test, and then reverted to my ROM to continue development lol.
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda premium
Cool deal
---------- Post added at 08:12 AM ---------- Previous post was at 08:02 AM ----------
Tryd flashing.. It failed immediately.. Gonna try redownloading
Sent from my SCH-I535 using xda premium
i just tried this hoping that it would work with this PA rom from AT&T. sadly this didnt work for me. it says update aborted when i try to install it. i was coming from PA 2.52 but it has some BT issues and occasional loose of signal for me so ifigured this would work. Maybe someone would like to try this and get it to work? :angel:
epicroot said:
Sent from my SCH-I535 using xda premium
Cool deal
---------- Post added at 08:12 AM ---------- Previous post was at 08:02 AM ----------
Tryd flashing.. It failed immediately.. Gonna try redownloading
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which mirror did you use?!
Sent from my SCH-I535 using xda premium
rossida said:
i just tried this hoping that it would work with this PA rom from AT&T. sadly this didnt work for me. it says update aborted when i try to install it. i was coming from PA 2.52 but it has some BT issues and occasional loose of signal for me so ifigured this would work. Maybe someone would like to try this and get it to work? :angel:
Click to expand...
Click to collapse
It's better to build AOSP from source if you can. In any case I'll update my reserved post with a how-to for AOSP ROMs (may or may not work for you).
EDIT: AOSP guide is up
Pure did you use twrp to flash?!
Menardo said:
Pure did you use twrp to flash?!
Click to expand...
Click to collapse
Yes. I always use TWRP. If you're trying to flash the Wicked Sensation ROM - it takes a long time to boot up.
EDIT: I just saw your post. If the ROM keeps failing I may have had a bad upload. Let me know and then I can correct it orrrrr you can try your hand at porting
PureMotive said:
Porting AOSP ROMs
================================ START ================================​
What you need
7zip
Notepad++ (If on Windows)
An AOSP ROM you want to port
An AOSP ROM from your carrier/device
Make sure the ROM you want to port and the ROM you are using as a base are the same Android version (e.g. 4.1.1) and have the same chip (e.g. MSM8960)​
I will do the AOSP porting section with an example. Say I want to port Paranoid Android:
Download Paranoid Android (Android 4.2)
Download CM10.1 (Android 4.2)
Unzip both ROMs
In the CM 10.1 folder delete the following folders:
/system/framework
/system/app
/system/media (optional)
/system/fonts (optional)
Add the following folders from the PA ROM into the CM10.1 ROM:
/system/framework
/system/app
/system/media (only if you deleted from CM10.1)
/system/fonts (only if you deleted from CM10.1)
Re-zip and flash in recovery
================================ END ================================​
If the ROM does not boot up, try a different ROM. For example, if you tried to port Paranoid Android 4.2 from AT&T and it didn't work. Try Paranoid Android from T-Mobile or the Galaxy Nexus, etc.
Click to expand...
Click to collapse
SO just to clear things up... if i download this and CM10.1 for verizon i just do the guide above and this should work even tho its not the same phone? The PA is coming from Google Nexus and trying to port to VZ GS3
PureMotive said:
Yes. I always use TWRP. If you're trying to flash the Wicked Sensation ROM - it takes a long time to boot up.
EDIT: I just saw your post. If the ROM keeps failing I may have had a bad upload. Let me know and then I can correct it orrrrr you can try your hand at porting
Click to expand...
Click to collapse
I just tried TWRP like 3 days ago... Have to say I'm digging it... Yea I tried to flash from the main server... Just downloaded from a mirror... About to give it another go will let you know...
rossida said:
SO just to clear things up... if i download this and CM10.1 for verizon i just do the guide above and this should work even tho its not the same phone? The PA is coming from Google Nexus and trying to port to VZ GS3
Click to expand...
Click to collapse
Yes, that's correct. However, if it does not work try porting PA from another device like one of the other US S3s.
PureMotive said:
Yes, that's correct. However, if it does not work try porting PA from another device like one of the other US S3s.
Click to expand...
Click to collapse
but the PA from other US devices are not running 4.2.1 which CM10.1 is. All PAs are running 4.1.x on US GS3. So would it not be possible to port them since they are two different JB versions?
Can this help us bring Premium Suite over to us? Want it bad
rossida said:
but the PA from other US devices are not running 4.2.1 which CM10.1 is. All PAs are running 4.1.x on US GS3. So would it not be possible to port them since they are two different JB versions?
Click to expand...
Click to collapse
You don't have to port PA from the US S3s. You can port 4.2 PA from the GNex forums if you want.
TokedUp said:
Can this help us bring Premium Suite over to us? Want it bad
Click to expand...
Click to collapse
Unfortunately not. Porting that is much more complicated than what's described in this thread. I pretty much already ported multi-window and the ink effect so doing the rest doesn't seem too far fetched.
Thinking it's a bad upload... Same immediate failed message...

[GUIDE] How to Port ROM's to the HTC Explorer

I know there are many Guides out there but most of them don't work for Pico!
so i decided to make one myself...
Things you will need installed on your PC
Notepad++
Winzip/Winrar
Q) What device should i port from?
A)These Devices are the Best!
Xperia S
HTC Sensation
HTC Sensation XL
HTC Desire
HTC Desire HD
Feel Free to try other devices
Base ROM and PORT ROM
Base ROM is what is Developed For Pico
Port ROM is what ROM you want to port for pico
Note: If you are porting a CM(PORT) which is ICS the BASE should Be cm9... same for JB
Now Let's start Porting!
Extract the BASE ROM to a Folder named Base
Extract the PORT ROM to a Folder named Port
Open Base ROM and go to system folder
DELETE "app,fonts,framework,media"
Open Port ROM and go to system folder
COPY "app,fonts,framework,media"
and paste it in System folder of the Base ROM
Open Port ROM and go to etc folder
Open Permissions Folder copy everything EXCEPT handheld_core_hardware.xml and platform
and paste it in the etc folder of the BASE ROM
Open Base ROM and go to system/etc/init.d folder
DELETE all files except 00banner
Open Port ROM and go to system/etc/init.d Folder
COPY everything Except 00banner
and paste it in the init.d folder of the BASE ROM
Now open build.prop And edit
ro.build.display.id=add what you want here
ro.modversion=add what you want here
Now open build.prop of PORT ROM and find
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
COPY there 3 lines and replace them in the BASE ROM's build.prop
Now Open updater-script
scroll down and find the lines starting with set_perm (there will be lots of them!)
Copy only those lines From PORT ROM's updater-script to BASE ROM's updater-script
If You find any extra file or folder in system folder of PORT rom than copy them to your base rom system folder.
Open updater-script from PORT ROM and copy all the set_perm lines and replace them with the lines in BASE ROM
To prevent bootloop copy
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
from system/lib in PORT ROM and REPLACE it with the files in system/lib of BASE ROM
Now ZIP the ROM and flash it
If you have a error read second and third post
Thanks
Status error 7 : Remove some apk's from system/app
NOTE: Zip should be below 145 MB to flash!!
Set_perm error : check recovery log and you will get your answer I'm serious
symlinks failed error : clean install ROM - wipe dalvik cache**
reserved
Good
Well done.. good work
but many other same guides are available on the forum so why did you did so much effort..
artistaditya said:
Well done.. good work
but many other same guides are available on the forum so why did you did so much effort..
Click to expand...
Click to collapse
60 % of them did not work 4 me!
shouldnt ideal devices be: Htc wildfire S, HTC desire C, Samsung Galaxy mini,gio and ace?
good job in explaining about what causes the errors and how to fix them!:thumbup:
This tut worked for me very well!
codexblack said:
shouldnt ideal devices be: Htc wildfire S, HTC desire C, Samsung Galaxy mini,gio and ace?
good job in explaining about what causes the errors and how to fix them!:thumbup:
This tut worked for me very well!
Click to expand...
Click to collapse
^^
You are too fast codexblack
Sent from my HTC Explorer A310e using xda app-developers app
Personally.. Porting for me is :
Code:
adb logcat
Sad there is no mention of it.
Ps : Unpacked ROM should be less than 235 mb.. Zip size may vary.. but ultimately unpacked size is what we care about..
There is no particular method afaik. All "methods" fail at some point or the other. Nothing is foolproof.
Anywho :good:
Explain
How this guide is different from
Rishabhraj and dance off guide of porting rom ???
No disrespect intended !!!!!
Sent from my HTC Explorer A310e using xda premium
Thread Closed​
As requested by OP​

Categories

Resources