yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] niv3d:
Any downfalls to porting ROMs versus tweaking the custom TW JB ROM? As far as compatibility goes...
[Verizon Samsung Galaxy S III] tonu42:
Very little if any downfall. If you can make it work it'll act the same. I have a galaxy tab 8.9 and almost all the roms are ports from the 10.1 version and it runs like a champ.

Our phones are the same except for software and or radio restrictions.
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
Well that depends on what phones you are porting from...
[Verizon Samsung Galaxy S III] Dubin04:
I'm gonna give this a shot.
[Verizon Samsung Galaxy S III] 05Warrior:
So if I have a Verizon S3 that's rooted I could take a Sprint Rom and do what you wrote in the OP and then do what you posted in post 24 and my phone should work on Sprint Network?

EDIT: Or could I just install a Sprint Rom and use the Network?
[Verizon Samsung Galaxy S III] NightxFall:
I will attempt to port some touchwiz and aosp ROMs using this method later when I get home today and will report back on how it goes.
[Verizon Samsung Galaxy S III] Hero:
I just checked that ROM. The process in the OP should work perfectly. Make sure you're porting the S3 version and not the S2 version.

No, you will still use Verizon's network.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
ha ha right?! na i made sure it was the S3 vers.

so i did as you instructed..and it flashed BUT i continuously get the FC of "process.com.android.phone has stopped"

any idea how to fix that?

thanks.

EDIT: well apparently i have no type of data either.
[Verizon Samsung Galaxy S III] NightxFall:
Tried porting http://xdaforums.com/showthread.php?t=2053697 using this, will not finish booting.
[Verizon Samsung Galaxy S III] Hero:
I'll try it and let you know. No data is a result of the incorrect eri.xml.

Figures. The only guide I know for sure works is the TouchWiz one. Lots of changes were made to AOSP that may have resulted in my method to not work. Grab a logcat by doing "adb logcat > logcat.txt" and upload it here.
[Verizon Samsung Galaxy S III] aj8600:
This is why I love Pure! Thanks man for your continued support
[Verizon Samsung Galaxy S III] undarated:
I remember getting that FC when porting roms. Try swapping the Phone.apk for the stock one for verizon. I also remember the eri.xml and apns.xml had something to do with mms working and the roaming indicator. I've also been digging around in the international version which is probably a big mistake but, looking for what controls the usb and other hardware hoping to not brick this phone. I'm sure a lot of it is kernel related but I'm almost positive that there is a few other libs and bins within the rom itself to control the usb and sd cards. I'll probe into it some more later on and see if I can figure anything out
[Verizon Samsung Galaxy S III] Hero:
vold.fstab in system/etc/ controls the SD card mounting. If swapping this file doesn't work you will have to make the corresponding changes to the ramdisk as they are shown in vold.fstab. USB mounting should be in the ramdisk.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
SD card mounts perfectly fine. no issues there. i dont even have a roaming indicator. just no data at all..wifi works tho LOL.

so i read earlier in the thread PM posted something about the eri.xml so i swapped the one from the base i was using and now its not booting..its stuck on the Samsung Logo. so i batt pulled and realized i lost root access. so i fixed all that and am now sitting on rom that i flashed and am waiting for some input
[Verizon Samsung Galaxy S III] Hero:
If you are porting from Sprint you shouldn't need to swap eri.xml. Only swap if you are porting a GSM ROM.

Anyway, I've been getting a lot of PM's regarding successful ports so just wanted to say good job to those of you who had success :good:

Glad to see that we now have more ROMs available for our device.
[Verizon Samsung Galaxy S III] undarated:
My bad about pointing out the eri.xml. I shouldve stated the reason for swapping it over. My apologies.
[Verizon Samsung Galaxy S III] pyroemaniac:
You ported multi window?
[Verizon Samsung Galaxy S III] Hero:
Yes. I also ported the ink effect. I may release these mods to the community in the future.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
so ur the reason i soft bricked..

gracias!

- thank the dev's for Odin, ill tell you that much.
[Verizon Samsung Galaxy S III] pyroemaniac:
Well if you need help testing or debugging please let me know, I've been working on it for a couple days. I did some porting back in my razr days

---------- Post added at 03:39 AM ---------- Previous post was at 03:38 AM ----------

You know the risks when flashing things, his mistake wasn't irreversible so try not to be rude.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
exactly, I took the risk. I assumed full responsibility when taking the time to go the steps for porting. besides it was a joke man, should i have included the "LOL" for clarification?
[Verizon Samsung Galaxy S III] Dubin04:
After I re-zip the ROM and flash it just fails. Any ideas?
[Verizon Samsung Galaxy S III] Hero:
What error do you get in recovery when trying to flash?
[Verizon Samsung Galaxy S III] SoCalSpecialist:
im gonna be honest here guys..when i did the mods to port over a ROM .. i didnt unzip anything.

i just dove right in with winrar, 7zip and used Notepad++ for corrections...

no issues flashing either...just the data caca
[Verizon Samsung Galaxy S III] Dubin04:
Just saying installation aborted.
[Verizon Samsung Galaxy S III] Hero:
It should say error 6 or something similar. Depending on your error different fixes may be needed.
[Verizon Samsung Galaxy S III] Dubin04:
I did this and it worked. Thank you.

Thanks PM for the fast response and this awesome guide.
[Verizon Samsung Galaxy S III] undarated:
Its all good brother. I didn't take offense to it. I'm here to learn about the porting Samsung roms instead of HTC. Trust me it's a big difference
[Verizon Samsung Galaxy S III] x714x:
Good stuff PureMotive! Everyone else thinks so too cause it made the XDA Portal site :D http://www.xda-developers.com/android/port-us-galaxy-s-iii-roms-to-other-variants/
[Verizon Samsung Galaxy S III] BeansTown106:
this is no where even near what u have to do to port a rom and actually have it fully working.. if people want there sprint roms / themes on verizon they should port there mods/themes into our apps/framework files the clean way .. not to be a **** but this is just gonna fill up our dev section with half working roms.. which isnt that good imho..

my whole thing is "QUALITY" over "QUANTITY"

and i do not mean any digs at puremotive im just stating my opinion
[Verizon Samsung Galaxy S III] Hero:
No offence taken man. I am aware of everything you just said, however the code across all of the S3s are virtually the same and this guide does what it's intended to - boot ROMs from other carriers. It's up to those who port ROMs from other carriers to maintain them and provide bug fixes. At this point, the only issues that are seen on the ports are MMS and those that are present in the original ROMs. You are right in that this is not a clear cut way to eliminate bugs, but then again there is no universal, clear-cut process to port a ROM so that everything works. At least this gets people started and we can see more variety in the forum.

Nice lol. I'll add a guide to port International ROMs soon, but as you can imagine it'll be a lot more difficult.
[Verizon Samsung Galaxy S III] Hogarth:
[4.1.2] [XXELL4][Sotmax Jelly Bean Ultimate Stock V12] GT-i9300

I am new to this would someone look at this and see if I could port this to my i535? I am not asking for you to do it but more what problems I could run into.

http://xdaforums.com/showthread.php?t=1944035

Thanks
[Verizon Samsung Galaxy S III] aypeeootrek:
That's how you know you're doing something right ;)
[Verizon Samsung Galaxy S III] tprouty:
how do we fix the MMS issue?
[Verizon Samsung Galaxy S III] aypeeootrek:
Believe a few people are trying to figure it out being its a problem on the ports
[Verizon Samsung Galaxy S III] niv3d:
Well if people feel this is the "incorrect" way to port ROMs then maybe they should create their own how-to... Just throwing that out there.
[Verizon Samsung Galaxy S III] Hero:
+1

The fact of the matter is that this works when porting. I think it just throws people off because the method is so simple. Most porters are used to doing ramdisk edits, framework mods, and lib swaps - all of which is not needed when porting a ROM from one to device to the

same

device (code is nearly the same). But whatever, this works and people shouldn't shy away from a method that works only because they feel that it's "incomplete" or "too simple".
[Verizon Samsung Galaxy S III] srzero88:
Okay, I followed everything to the T. But when I go to flash the ROM I ported I get the red triangle with the exclamation mark. Does that mean that it just won't work?
[Verizon Samsung Galaxy S III] cdrice15:
Ive read through this whole forum and this seems sweet. I have a US Cellular S3 so I am assuming it should work the same. Been trying to port a Sprint rom but getting lost. Any thoughts as to it working for the US Cellular S3 before I dive in?
[Verizon Samsung Galaxy S III] countryfolk07:
I successfully ported FreeGS3 by Team Sonic. No issues with calls, MMS, video, anything. Stock look, but no issues. Battery was a little crummy, but otherwise smooth sailing. I used this method. Thank you Pure for your help and guidance! :thumbup:

Sent from my Unleashed GalaxyMODed ...... um ...... phone?
[Verizon Samsung Galaxy S III] Droid2drummer:
Make sure your super user is up to date and maybe reflash recovery or check or relock boot loader. :)
[Verizon Samsung Galaxy S III] lowg:
A wise man once said "Everything should be made as simple as possible, but no simpler."

Nice work PureMotive. :good:
[Verizon Samsung Galaxy S III] srzero88:
This is the ROM I was attempting to port over. Could you ask the OG dev for permission to post and share the wealth?
[Verizon Samsung Galaxy S III] countryfolk07:
I really didn't want to maintain a thread. I just did it for myself to try something different. I really like Pures ROM, which I'm currently running. I could upload for you if you want to maintain the thread. Just ask the DEV and give a little credit. I think the battery was horrible no matter what kernel I ran. I have a theory that the increased signal on the ROM was depleting the battery. More power being used for the radio possibly? Just PM me if interested.

Sent from my Unleashed GalaxyMODed ...... um ...... phone?
[Verizon Samsung Galaxy S III] cdrice15:
I tried porting a sprint rom over to us cellular following these instructions and got in a boot loop. Dont have any idea from here.
[Verizon Samsung Galaxy S III] Notorious:
Could you post a log cat it might help trouble shoot why it bootlooped :thumbup:
[Verizon Samsung Galaxy S III] cdrice15:
Ill get a logcat in few.
[Verizon Samsung Galaxy S III] srzero88:
If battery life was that bad then I'll pass
[Verizon Samsung Galaxy S III] Droid316:
It could have been just his phone.Try it on yours.Do a nandroid then flash away
[Verizon Samsung Galaxy S III] gypsy214:
Ok let me get this straight. OP I seen on some of the post some files xml. that have to be change too. Can you please put that on your OP.

And We can port any rom that is based on cm or aokp from the galaxy nexus over to the s3? Now I figure there would be some bugs because these roms were made to be stable for the gnexus not the s3! Also I have a gms tmobile version of the s3 and in your post you mention that if you are porting another s3 rom from a gsm version to the verizon there are more work around with the files than are just in your op. I wonder if I like a rom from the verizon version to my gsm tmobile I have to do more changes that are not in the op but you mention it on some of your post.

Just wanted to clearify these
[Verizon Samsung Galaxy S III] Notorious:
PM tried porting MIUI from d2VZW to D2SPR booted up fine but cant get past installation screen. I pick the language then com.android.provision stops. Here is a log of the rom booting(i realize alot of things are broken within the rom even if i get through installation screen) http://pastebin.com/WL7cTWCa
[Verizon Samsung Galaxy S III] Hero:
Added eri.xml instructions to OP. To answer your questions:

Yes, you can port any AOSP ROM from the Galaxy Nexus over to the S3 (The AOSP ROM doesn't even have to be from the Galaxy Nexus. It can be from ANY device)

If you are porting an AOSP ROM, all of the bugs that are present in the original ROM will exist in your port.

You can port a Verizon ROM over to T-Mobile by following the instructions in the OP. No extra steps are needed. But because T-Mobile is GSM and Verizon is CDMA, you will have to swap eri.xml.
[Verizon Samsung Galaxy S III] Hero:
There are more steps needed to porting MIUI since that is not your everyday AOSP ROM. I believe there are MIUI bin files among other things that need to be given correct permissions in order for the ROM to work correctly. Use the d2vzw MIUI updater-script. Don't worry - the partitions are the same among all of the carriers so you won't have a brick. Double check to make sure.
[Verizon Samsung Galaxy S III] gypsy214:
Thank you for your reply. It just sometimes the op doesnt update the thread and its confusing in going by every page looking for the answers lol. Thanks for making it clear that any aosp rom from any device can be ported! Thats a relieve. So guy over the tmobile forum said that he flash a aosp rom from att and it worked fine by only changing the d2att to d2tmo. also some in the tmobile forum says that we can flash tw roms from att without changing anything. But a lot of people have said that it cant be done. This is a very good thread and I thank you for putting this up. It would also be awesome if this thread should be a sticky for all us variant galaxy s3 lol. So people will have more ideas in porting roms.
[Verizon Samsung Galaxy S III] BeansTown106:
yes it boots roms but there is alot of stuff different between the carriers, ril, gps, many many id's which then makes all of the "mods" for verizon unusable.. for one verizon towers will see it as an unauthorized device, most verizon based apps wont work, network extender will see it as unauthorized and it will be "roaming" csc files have the complete wrong stuff for verizon, and the list can go on forever..

please dont do this.. people who are using ur guide are more or less everyday users and not devs they need to learn the same way we did.. if you do this i almost gaurantee ppl will hardbrick thier devices.. and that will all be on you :(

im debating doing this just so we can clear up all these half working roms.. but once you see what is actually put into porting a rom and making it so everything works you wont wanna do it......

its not that its incomplete or too simple its just not the real way todo it.. its a

very very very hacked way

about going about it.. i could understand using the sprint base if it was 4.1.2 but that itself will take alot more to get it working the right wayy.. another thing is all these roms are built off an older base than verizon has.. and i dont get your logic on the code is nearly the same its completely different.. just look in framework.jar at the radio smalis among many other smalis that have verizon code in them.. even the build.prop code is completely different..

dont think im craazy i have been porting roms forever off of a base that has NO source aka MIUI(which is just one big port).. i know the right and wrong way to port a rom..

again im not trying to hate on u i just think this method has cluttered up the vzw forum with a bunch of roms that are full of bugs and most of the ports are by users who have no idea what they are doing.. which means nothing will be fixed.. and another reason im not to fond of this is because the probability of people bricking there devices using this method is way to high

its late and im tired i will finish my rant tomorrow after u guys say what u have to say..
[Verizon Samsung Galaxy S III] StrumerJohn:
This.

It takes much more than what is said to get an AOSP ROM fully ported as well. I have nothing to dis you for, you're a great dev to our community PureMotive, but this is only creating a mess out of our development forum.

AOSP having foreign files from other carriers can lead to people getting bricked devices, loss of IMEI, Corruption of DATA/Service/"ERI Roaming Issue", and inability to fully use the Verizon Network (e.g. Network Extenders).
[Verizon Samsung Galaxy S III] Felnarion:
Has anyone tried it with porting something from somewhere else to d2spr? Does the rotation issue still exist, or does this somehow take care of it?
[Verizon Samsung Galaxy S III] Hero:
Apologies for not quoting everything, but it was just too much.

I didn't say that this guide was a fool proof method of porting ROMs as there is no way to to port ROMs that ensures everything will work. The purpose of these guides is not to make a ported ROM bugless. The purpose is to get a ROM built for another device booted on ours. Generally that's what guides do anyway. For example the guides by proxuser in the Android Development and Hacking section of XDA are not meant to make a ROM bugless. He posts his guide so that people can get different ROMs on their phones. The same goes for this guide - I am teaching people how to get ROMs working on this device. Perhaps I should add a disclaimer in the OP that says "This guide will not get everything working properly".

In any case, when I made this guide I did not intend it to be used by people to just try porting and post broken ROMs. However, if users did boot their ports and were willing to work on them so that every feature works, then why not let them post? We all started developing at one point or another and I can say that for myself, when I started I hardly knew what I was doing, but I did research and learned. Why can't others do this as well? I don't automatically assume that "newbs" who don't know what they're doing can't learn and get better...

A developer isn't the only person who has the rights to posting a ROM. If someone gets one booting, is sure that it won't permanently damage another's device, and is willing to work on it to fix all the bugs then they should be allowed to post it. It is just up to those who port to continue fixing bugs, not just boot the ROM and call it a day.

Just to reiterate my points:

This guide is not intended to get everything working (no universal guide can do that as each ROM is different)

Don't think you're holier than anyone else just because you have dev experience. Others can learn...just as we all did.

It is up to the porters to fix the bugs associated with their ports. If they have questions, they can ask for help.

Also, no offence taken. I appreciate all of your opinions, but just wanted to express mine. I hope I didn't offend anyone and that we are still on good terms :)
[Verizon Samsung Galaxy S III] makmoneynslp:
Well said my friend I want to learn badly and I want to become an valuable to gs3 community so can we exchange gmails and whenever I have an question I can ask on demand.....I believe that the greatest devs and many successful people learn by try and error. You never know what your mind capable of until you try...but like he said research and teach yourself before you just dive into something

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

Im going to send you an pm of my Gmail ok
[Verizon Samsung Galaxy S III] born1690:
Awesome
[Verizon Samsung Galaxy S III] gypsy214:
Guys you actually thought that by porting a rom to your device it will be stable??? My gosh get some brain. Dont flame the op either. His guide its awesome it gives people an idea on how to get a rom from another device booted on this device. If porting a aosp rom from another device to this one of course you will get bugs. Because that rom is made to be stable to the other device!!! Not even miui will work properly if ported it needs work to be done. Back in my galaxy s2 days (tmobile version Hercules) we could flash roms from the att s2 (skyrocket) but it would break some stuff. Like auto rotation and call echo. But thanks to the devs they had these fixes as sticky. Auto rotation was due to kernel and echo due to some radios and drivers. And that it.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
see what happens when u try to make things fun LOL.

i dont know what all the fuss is about..he (PM) was only trying to give us users "something different" to do besides waiting for updates and releases.

i actually thought it was a great idea to put this out there...i asked a few questions, got some answers, and actually linked up with a couple others to get some ports working.

all in all without the b.s stories and whats wrong with you posts, i found this one to be informative.
[Verizon Samsung Galaxy S III] Skeeter35:
Would either of you, or both, be willing to help me or show me where to start to be able to do a proper port so I can learn. I'd really like to start with porting roms and work my way to eventually building my own. Thanks in advance.
[Verizon Samsung Galaxy S III] scarygood536:
All I got to say is this guide worked for me porting a ATT Note II rom to the verizon S3. Of course I ran into a problem, but pure helped me and I solved the problem. He pointed me in the direction of water, now it is up to me to learn what I can do with it.
[Verizon Samsung Galaxy S III] michaeldizzowns:
tried to port galaxy s fre3 using clean rom le 4.5 basically just to see if i could make it work.

followed guide and when i flashed in CWM installation was aborted.

if clean rom is k3 and fre3 rom uses LJ7

it should still work correct?
[Verizon Samsung Galaxy S III] tprouty:
I did this and could not get mms working. Everything else was very smooth tho.
[Verizon Samsung Galaxy S III] michaeldizzowns:
ha well thanks for heads up. wouldnt have used it anyways unless it some how flawless
[Verizon Samsung Galaxy S III] jawonder:
How do i replace the eri.xml with the one from carrier it's not allowing copy and paste or drag and drop with 7zip ?. I did get it to drag and drop but i get and error in TWRP with the zip in made . I'm trying to port Synergy to At&t GS3 using LoserRom as my Carrier rom .
[Verizon Samsung Galaxy S III] pyroemaniac:
Winrar is your best friend ;)
[Verizon Samsung Galaxy S III] jawonder:
I tried doing it on my Mac i followed the steps and everything seem to come together fine but after zipping the file i get an error in TWRP when flashing seem something is wrong with making the zip .
[Verizon Samsung Galaxy S III] Hero:
What is the error? It should say something like "Status 6", "Status 0", etc
[Verizon Samsung Galaxy S III] pvndpk:
Can i port jellybam v3.3.0 from here..http://xdaforums.com/showthread.php?t=2053697..

Please help
[Verizon Samsung Galaxy S III] jakereeves31:
Why not? Try it and see:P
[Verizon Samsung Galaxy S III] jakereeves31:
Why did you just post this question again?
[Verizon Samsung Galaxy S III] pvndpk:
Please help
[Verizon Samsung Galaxy S III] what be up:
Lol? Read the op the help is right there...
[Verizon Samsung Galaxy S III] Notorious:
Yes if you follow directions in the OP. If it doesn't work post a log cat
[Verizon Samsung Galaxy S III] upndwn4par:
Great info. Thanks!

Two questions:

1) Do the partitions (system, boot, etc) have the same designation (mmcblk0pXX) across all carriers?

2) Is META-INF (certs, manifest, binary, etc) the same across all carriers?

(Search is down at the moment. But I didn't see these questions asked while scanning the thread)
[Verizon Samsung Galaxy S III] gypsy214:
Good question
[Verizon Samsung Galaxy S III] Hero:
Yup. The system, boot, data, etc partitions are all the same across the US S3 carriers AFAIK. I haven't checked US Cellular or Metro PCS but I am pretty positive they are the same.
[Verizon Samsung Galaxy S III] tprouty:
Has anyone figured out mms issue when porting from sprint?