Database Info

[how to port]inc 2 evo porting patch & tut(+3 roms)

2 METHODS OF PORTING BELOW posted by INCDOES
MANUAL
(FOLLOWING THE GUIDE BELOW)
&
INCDOES PORTING PATCH
(EVERYTHING YOU NEED IN A ZIP)=much easier,should be the obvious choice for most...
USE THE METHOD THAT SUITS YOUR NEEDS...
UPDATE:To avoid confusion, this thread was started before the porting patch was released...i chose to leave the MANUAL directions below posted on incdoes blog for those of us that like to know whats going on behind the scenes of the updater.script=what the patch is doing
UPDATE:
found this on twitter a bit ago...
(courtesy of incdoes)
CHECK OUT THE INCDOES INC 2 EVO PORTING PATCH
CAUTION:
This is not recommended for the ave everday user/know nothing/no time to fudge with my phone crowd...
that being said, now for the fun stuff
i take no credit for any of this other than typing(incdoes leaked most of these port bases). i am just posting links to roms i found in inc forum with the instructions for porting to evo from incs blog. just trying to initiate some more rom development. i am still trying to decide which i will be working on...but this is open source so i just put it here for evo users/devs to view and get porting
ROMS:
DESIRE Z
MT4G
LIquiDsENsE
(hybrid by mmmark111)
HOW TO PORT INC ROM TO EVO
-excerpt from incdoes blog-
Okay, to run an INC ROM on your EVO would be simple. There will be a few broken 'stuff' e.g. bt, wifi etc... but easy fixes!
First you will need the INC ROM you desire to run on your EVO. Now, if its an "INC Sense ROM" you will need a "EVO Sense Kernel" and if it's an AOSP ROM then you will need a AOSP kernel.
Now there will be a few things you will need to replace on the INC ROM to make it run on your EVO:
~We are going to use a sense 2.2 rom as an example~
"so grab these files from any EVO sense ROM, preferable stock 2.2 EVO"
- boot.img (for your phone to bootup)
- system/usr (for buttons)
- system/lib/hw (for lights)
- system/lib/modules (for wifi)
- system/etc/vold.stab (for sdcard readable)
- build.prop (for market and LED's fix)
please note: some prop files include different edits that can break market/data/network/LED's... but then again, easy fixes!
Now you have an INC Sense ROM and 'all the files listed above pulled from an EVO Sense rom, you will have to add/replace the files pulled from the EVO ROM into the INC ROM, sign the .zip and flash (via recovery).
Should/will bootup if its based on the same firmware i.e. 2.2 INC ROM and 2.2 EVO ROM.
DISCLAIMER:
I am not responsible for you bricking your wife's/son's/boss's/aunt's/grandpa's/girlfriend's/fiance's/mother's/etc....evo
good porting
&
happy flashing
THANK YOU
sorry mods if this doesnt qualify as dev, but i cant think of anything describing it better​

Nice post(s) mannn!!

too cool-- if i get time i'll definitely go thru this. Thanks!

Thanks. Going to be fun
Sent from my PC36100 using XDA App

I just have one question. So why can't we get the camera to work?
Sorry I'm thinking of the desire roms my bad..

Nice, I'm gonna play with this over the weekend!! Just hope I dont brick my phone

stanglifemike said:
Nice, I'm gonna play with this over the weekend!! Just hope I dont brick my phone
Click to expand...
Click to collapse
You can wait till the weekend, you've got patients man ..

Wonder if this process can be used to port nexus roms?
Probly a couple other things needed.

I had a idea, the Incredible version of the normal LiquidE ROM (not the sense hybrid) seems to have incoming calls working unlike our Evo version. What if we tried porting it using this method, anyone think that might work?

KERKEDAGAIN said:
Nice post(s) mannn!!
Click to expand...
Click to collapse
mkeena0305 said:
Thanks. Going to be fun
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
fun indeed...
stanglifemike said:
Nice, I'm gonna play with this over the weekend!! Just hope I dont brick my phone
Click to expand...
Click to collapse
i have faith in you
Igotsanevo4g said:
Wonder if this process can be used to port nexus roms?
Probly a couple other things needed.
Click to expand...
Click to collapse
you can try and post back. results would be appreciated.
crpercodani said:
I had a idea, the Incredible version of the normal LiquidE ROM (not the sense hybrid) seems to have incoming calls working unlike our Evo version. What if we tried porting it using this method, anyone think that might work?
Click to expand...
Click to collapse
this is dev, just like any here i put it up for you to try this out yourself(opensourcewin)...let us know how it goes, this is simple please report findings. this could turn into a sweet beta rom thread with a little help...

MagnusRagnarok said:
you can try and post back. results would be appreciated.
.
Click to expand...
Click to collapse
Gonna try, tonight or tomorrow. Fingers crossed...
Edit: I realized the boot.img would be for a sense rom, and nexus is aosp. So i can rip the boot.img from cyanogen out and stick it in the nexus rom and it'll purr?
Or... What?

zone23 said:
You can wait till the weekend, you've got patients man ..
Click to expand...
Click to collapse
OHHH I wish I had patients!! Quite the opposite actually.....just a really busy life.....but I may try to start tonight anyway .

So im flashing a nexus rom right now, that i switched out all the stuff + threw in a cyanogen kernel.
If this thing bricks...
___________
UPDATE: It booted up, but it doesnt register any touch on the touch screen. LOL.
Hmmm maybe if.. Any ideas guys? I switch some other stuff around too. Maybe i can figure this out...
UPDATE: I flashed netarchy universal kernel and now the touch works, i cant get any signal, i dunno what stuff needs to be switch out from GSM to CDMA.
Wifi WORKS! I dont have a keyboard for some reason, so i cant enter my password to test it but it looks to be fine. And since i have no internet connection i cant get astro to install one from my SD haha.

I flashed over sky raider 3.3 final and every thing is perfect. Theres a uncommon sense patch which I also ported because I remember reading that on the hd Rom the ego didn't like the 4 signal bars. Only thing not exactly right is the camera. It doesn't have the capture button but I can take pics by holding a finger on the screen. Video is a no go due to not having the nature button. This Rom is the smoothest I've used and I'm a flash a holic so I've used them all.

So if I use the flash patch do I need to do any of the other stuff listed in the op(replacing files)?

Sweet Magnus, may have to get back to you details of what i find wrong. But i got a porject due next week for school. I have to record us BMXing this weekend. Then make an edit. If i get that sweet alone time in the eveing, i'll be sure happy to port all three and give findings.

Everyone can check my original post, made this about Monday, September 27, 2010
ID
http://incredibledoes.blogspot.com/2010/09/how-2-inc-roms-one-evo.html

Tiffany84 said:
So if I use the flash patch do I need to do any of the other stuff listed in the op(replacing files)?
Click to expand...
Click to collapse
My flashpatch is the same thing,
This post is what i dont want to happen, like i said before there is no point in repacking a whole new zip file when we can just have a flash over patch zip that does all the work for us.
ID

IncredibleDoes said:
My flashpatch is the same thing,
This post is what i dont want to happen, like i said before there is no point in repacking a whole new zip file when we can just have a flash over patch zip that does all the work for us.
ID
Click to expand...
Click to collapse
That really saves a lot of time. Going to give it a test.
Sent from my PC36100 using XDA App

AWESOME! Thank u very much

[GUIDE] Porting Vibrant Roms To SGS4G

Porting Vibrant Roms To SGS4G
***EDITED FROM A GTALK WITH DR. HONK***
ALL CREDIT GOES TO DR. HONK FOR TEACHING ME AND FOR KRYLON360 FOR TEACHING DR. HONK!!!
THANKS FOR LETTING ME POST THIS AND FOR YOUR PATIENCE!!!
OK, Well CWM is now final and it's time to start PORTING!!!
***Most Vibrant roms are 2.2, so you will be downgrading your OS.
Also, if it's a i9k port, it might require more work. (button mapping, etc.)***
TOOLS
1. Install Android SDK
2. Download Smali.jar & baksmali.jar from http://code.google.com/p/smali/
3. Both files will have version numbers on the end. take those off.
4. Place both files in /tools directory in sdk.
5. Download Beyond Compare.
6. Download 7 zip.
7. Download A FLASHABLE SGS4G ROM.
8. Download the Vibrant Rom you wish to Port.
9. Download Ammend2Edify (somewhere on XDA)
INSTRUCTIONS:
Note: To DECOMPILE (FROM /TOOLS) "java - jar baksmali.jar -o directory_out/ classes.dex" To COMPILE (FROM /TOOLS) "java -Xmx512M -jar smali.jar source_directory/ -o New_Classes.dex"
1.)Okay, so there are four files that need to be edited. They are framework.jar, services.jar, Settings.apk and android_policy.jar.
2.)Using 7-zip, you need to extract the classes.dex from each file mentioned, for both the rom you want to port and the flashable SGS4g Rom you are comparing it to. This has to be done, since the vibrant and sgs4g have totally swapped partitions.
3.)Extract one at a time. Place classes.dex into /tools, Decompile to directory_out. ( i.e, if using KD1 flashable and extracting framework.jar, then name directory_out KD1_framework)
4.)Once you have extracted & decompiled the classes.dex from each of the four files, Open Beyond Compare.
5.)Load the two directoies you want to compare and hit the compare button. select binary.
6.)Look for anything with storage information. Either STORAGE info .. or anything for /sdcard. Here's the problem ... internal storage and external storage. those are swapped.
7.) you replace that part .. and only that part.
Example:
on framework.jar .. you want to look at Android\os\Environment.smali
everything there need to be swapped, from /mnt/sdcard to /mnt/sd/external_sd
and vice versa
Same goes with Landroid/os/Environment;->INTERNAL_STORAGE_DIRECTORY .. that needs to be Landroid/os/Environment;->EXTERNAL_STORAGE_DIRECTORY
8.)You will see a lot of differences .. ignore any line differences. ALL YOU NEED IS STORAGE.
9.)There might not be differences in every file, depending on the rom to be ported with the exception of settings.apk. USB Mounting will not work if not edited properly!
10.)Once edited, go back into command prompt and compile. the new_classes.dex will appear in the /tools category.
11.)Open the Vibrant Rom in 7 zip and go back to the location of the classes.dex file you extracted. delete it and copy over the new_classes.dex. rename it to classes.dex. you'll get a prompt from 7 zip that the archive has changed. accept to update the archive.
12.)Repeat this proces for each classes.dex edited.
so that's the jar and apk files!
WI-FI:
1.)You will need to copy over /system/etc/wifi from sgs4g ROM to the new port ROM.
2.)Then you also need to copy several files ... /system/bin/wpa*../system/bin/wifi* ../system/bin/*ril* .. /system/lib/*ril*
3.)Then you also need to copy over /system/etc/vold*
CHANGING THE MODEM & KERNEL.
1.)Open the Vibrant Rom in 7 Zip and Delete ZImage(kernel) and Modem.bin
2.)Open the SGS4G Rom and Copy over Modem.bin & Zimage.
3.)Thank Krylon360 for catching my brain farts.
AMMEND2EDIFY:
Most Roms you'll find for the vibrant are using ammend scripting. Download the Program & the updated phone database for it from XDA and follow the OP instructions to get it set up.
That's it! FLASH AWAY!!!
ALL CREDIT GOES TO DR. HONK FOR TEACHING ME AND FOR KRYLON360 FOR TEACHING DR. HONK!!!
THANKS FOR LETTING ME POST THIS AND FOR YOUR PATIENCE!!!

Reserved for later.

*cough* missed a credit.

krylon360 said:
*cough* missed a credit.
Click to expand...
Click to collapse
Dude! So Sorry, Honk just informed me! changing.....now!

robbbbit said:
Dude! So Sorry, Honk just informed me! changing.....now!
Click to expand...
Click to collapse
haha all good man, just messin with ya. in a good mood today.

ack.. you forgot the biggest part..
you will need to swap the kernel and modem from the vibrant rom you are porting with the SGS4g kernel and modem.
So for example,,
you are porting Bionix, you will want to take the KD1 kernel and modem (or Bali kernel for the SGS4G) and overwrite the ones that are in the Bionix zip

Dude this is great. Now I just need a computer to try and port some roms. Thank you guys
Sent from my SGH-T959V using XDA Premium App

krylon360 said:
ack.. you forgot the biggest part..
you will need to swap the kernel and modem from the vibrant rom you are porting with the SGS4g kernel and modem.
So for example,,
you are porting Bionix, you will want to take the KD1 kernel and modem (or Bali kernel for the SGS4G) and overwrite the ones that are in the Bionix zip
Click to expand...
Click to collapse
haha, and that was the ONLY part I didn't have to ask help for!!! thanks, dude.

In jumping on this as soon as I get home. Power just went out at work so someone has to tend to the servers
sent from my not so stock SGS4G

can you add to your post, that most Vibrant roms are 2.2, so they will be downgrading their OS.
Also, if it's a i9k port, it might require more work.

thanks again! edited.

Downloading the newest SDK right now.
Got another 2 hours just sitting around at my desk here at work while everyone else has left to enjoy their long weekends...might as well be productive with something I am actually interested in....
Going to try to port Bionix

krylon360 said:
can you add to your post, that most Vibrant roms are 2.2, so they will be downgrading their OS.
Also, if it's a i9k port, it might require more work.
Click to expand...
Click to collapse
This is STILL fantastic for sgs4g potential development to ramp up and get started. It really can't be overstated. I'm sure now we will soon have native roms built from scratch as well. There are a hell of alot of sgs4gs out there and all owners starving for mods lol. Heck I expect to see a native 4g rom ported to vibrants and i9ks.
Sent from my SGH-T959V using XDA Premium App

So does that mean CM7 love for SGS4G? And we'd be missing 4g on any vibrant rom we port wouldn't we?

Eric-1987 said:
So does that mean CM7 love for SGS4G? And we'd be missing 4g on any vibrant rom we port wouldn't we?
Click to expand...
Click to collapse
You will have to ask Team Douche or over on the official cyanogen site about their intentions regarding sgs4g. I can tell you this--it wouldn't happen without a working cwm. So my guess is yes we will see CM at some point.
Regarding 4g... we will still have 4g. Ports won't affect that. No worries in that regard, our phones will still be fast as hell on the net.
Sent from my SGH-T959V using XDA Premium App

Ill wait tillll we have flashable roms.
Sent from my SGH-T959V using XDA App

Harhar321 said:
This is STILL fantastic for sgs4g potential development to ramp up and get started. It really can't be overstated. I'm sure now we will soon have native roms built from scratch as well. There are a hell of alot of sgs4gs out there and all owners starving for mods lol. Heck I expect to see a native 4g rom ported to vibrants and i9ks.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
You do realize I did this before the phone was even out right? ;-) Look up Bionix Frost

krylon360 said:
You do realize I did this before the phone was even out right? ;-) Look up Bionix Frost
Click to expand...
Click to collapse
I stand corrected! I do recall now that you mention it you got access to a 4g build before this phone was even out! So you will be remembered as the first back port to the vibrant...the legend continues! ;-)
Sent from my SGH-T959V using XDA Premium App

Oh nice how come the evo couldnt get 4g without a properly working ROM? And whats a good rom to convert to my SGS4G? I cant stand touchwiz. The second I got it (Yesterday) I put on launcher pro and a kernel and oc'd.

Eric-1987 said:
Oh nice how come the evo couldnt get 4g without a properly working ROM? And whats a good rom to convert to my SGS4G? I cant stand touchwiz. The second I got it (Yesterday) I put on launcher pro and a kernel and oc'd.
Click to expand...
Click to collapse
No idea on the evo. I have no experience on that phone. As far as rom ports, there are alot to pick from. You can bet I will be looking them over now lol.
Sent from my SGH-T959V using XDA Premium App

[Q] Building custom ROM could use a couple pointers...

Like the title says I'm working on building a ROM of my own. I am new to this but am not stupid. I've looked around the forums and have bookmarked quite a few threads that will help me. My question is, how would I go about putting a custom CWM flashing screen in? Like on Eman..and ZTR where it says Collective, and flashing modem, etc. etc. And if anyone can point me to a better "ROMS for dummies thread that would be great Thanks for any help
Edit: Scratch that question, just found it lol. But any pointers will still be appreciated

So you are set?
Sent from an Emancipated Infuse bleeding Orange

Are you on linux? If you are, then i sugest installing android utility, its probably the simplest way of getting everything installed and organize it all together. It installs dsixda rom kitchen, apktool, simpla adb interface-im out of town at the moment but when i get back (friday night) i can upload some pics of the android utility
http://forum.xda-developers.com/showthread.php?t=1167623
Sent from my SAMSUNG-SGH-I997 using XDA

^ Alright man thanks. I'll have to install a linux partition on my HDD but that's easy enough. I do have one question that's confusing me...How do I add things to my rom? For example the camera mod where you can take pics with the power button? I have the apk but when I replace it at system/app it Fc's. Do I need to put the other files that come with it in my rom? Same problem with EPM. I have the settings apk but it doesn't work..

FauxAffliction said:
^ Alright man thanks. I'll have to install a linux partition on my HDD but that's easy enough. I do have one question that's confusing me...How do I add things to my rom? For example the camera mod where you can take pics with the power button? I have the apk but when I replace it at system/app it Fc's. Do I need to put the other files that come with it in my rom? Same problem with EPM. I have the settings apk but it doesn't work..
Click to expand...
Click to collapse
For camera I believe you will also need to pull the camera firmware apk too-so you need to put the modded camera.apk and camera firmware.apk in your from (both can be obtained from any of bigfaus roms
For epm you need more than just the settings apk, you also need to replace the frameworks that come with epm (policy.jar, framework-res.apk, and framework-res.jar) I believe that's all you need
As always, if you choose to upload your rom for others be sure to give credit-bigfau for camera, and I'm assuming you got epm from dman so dman for epm
Sent from my SGH-I997 using XDA

Also for battery mods (and other stuff too) a great place to go is a website called UOT kitchen-just choose your battery mod then upload your frameworks and it will place the modded battery in there for you, then replace your old frameworks with the new ones from uot kitchen
*do this after you have epm set up and running...unless you plan on doing it manually using dmans how to guide*
Sent from my SGH-I997 using XDA

AOKP for tab 7+

Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.

MacZzang said:
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
Click to expand...
Click to collapse
There are a lot of useful porting guides on the Chef Central sub forum on XDA. There's bound to be an AOKP guide there somewhere. Shouldn't be too hard considering we have CM9 mostly working thanks to locerra and aorth.
Sent from my SPH-L710 using xda premium

Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again

MacZzang said:
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
Click to expand...
Click to collapse
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium

Ceelos09 said:
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw

MacZzang said:
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
Click to expand...
Click to collapse
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.

Ceelos09 said:
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Click to expand...
Click to collapse
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens

MacZzang said:
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
Click to expand...
Click to collapse
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium

Ceelos09 said:
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files

MacZzang said:
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
Click to expand...
Click to collapse
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what I got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium

Ceelos09 said:
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what u got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?

MacZzang said:
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
Click to expand...
Click to collapse
You might wanna port mainly from the Galaxy S2, seeing as how we have more in common with them hardware wise.
And no. I'm about to start my college classes next month at DeVry. Gonna do their Computer Engineering course. I don't know much but as soon as class kicks in, I'm hoping it'll kick start my development here on XDA. For the time being, I usually lurk around n help. Maybe learn a thing or two by reading a random thread or guide.
Sent from my SPH-L710 using xda premium

Well things don't look so good from my end... I've put together about 16 different roms and they all won't go past the boot screen. And the galaxy s2 roms kept giving me the same fatal error... I'm hitting a wall here I don't know what to do.. I'm guessing we just have to get our hands dirty with this one.. I'm doing some reading on python and c hopefully I can figure this out...
So ur a student? That's cool I wanted to learn program and computer engineering before I got into university

Sweet God Almighty, if we got AOKP on this thing I... I... well... I think I might just cry for joy. :crying:

Hahahaha yeah same here I love AOKP based roms, they have more options! And aokp has a unicorn! But sadly we have been trying here for a few days and well I'm not really a Dec I'm just following porting guides and tutorials around xda trying out different things here and there hoping we can get passed the boot screen. Would definitely appreciate your help

Been having some trouble setting my build environment up, so I'm currently seeking some help from others who have experience building AOKP from source. Hopefully they can guide me through it and I find what I did wrong
Sent from my SPH-L710 using xda premium

AOKP == CM
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.

aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium

aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Aorth u broke my heart man I actually had lots of hope that this can be pulled off... so you're saying this is impossible to do? I like aokp because if the rom control menu I feel it has more options and customization. But cm9 is great too. Thank you so much for all the hard work u have put into bringing cm9 to our awesome tabs
Ceelos09 said:
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah I saw the Yamaha audio thingie too...? What's the problem? Is that a driver thing or something else? From the way you both mentioned it I'm guessing its something serious.. ?
Sent from my GT-P6200 using xda premium

aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Curious, what can CM do feature wise that AOKP can't?
I can think of quite a few that AOKP can do that CM can't.
Posted from my Galaxy S III.

Port a rom

Guys,I want port this rom: http://forum.xda-developers.com/showthread.php?t=1763514. Is there a guide for do this? Thanks in advance!
Sent from my nexus s using xda app

Spidergio said:
Guys,I want port this rom: http://forum.xda-developers.com/showthread.php?t=1763514. Is there a guide for do this? Thanks in advance!
Sent from my nexus s using xda app
Click to expand...
Click to collapse
The OP in that thread says:
4. No ports based on my ROM zip file, manifest.xml will be updated regularly and feel free to compile from source
Start elsewhere, unless you want to learn to compile. Come back with a ROM you're allowed to port and post it here. Then we'll help you

same
trying to port a rom also still working on it

Porting can be easy or hard depending on many factors.
First of all, if the rom type the you are porting (AOSP, Sense, AOKP, CM7/9/10, Touchwiz, Motoblur, etc.) already has similarly typed ROMs for your device your life will be much easier as you will have a base to work with.
The general idea for an easy port is to use the boot.img, keylayout, modules, and many libs from a similar ROM that already exists for your device. Also, the build.prop and updater-script will need edited (updater-script for most, but not all, ROMs).
If you are on an HTC device and you go grab a Touchwiz ROM to port, you're most likely going to have a bad time. Start with something that exists in large quantities for your device. AOSP ROMs are usually a great place to start.

estallings15 said:
Porting can be easy or hard depending on many factors.
First of all, if the rom type the you are porting (AOSP, Sense, AOKP, CM7/9/10, Touchwiz, Motoblur, etc.) already has similarly typed ROMs for your device your life will be much easier as you will have a base to work with.
The general idea for an easy port is to use the boot.img, keylayout, modules, and many libs from a similar ROM that already exists for your device. Also, the build.prop and updater-script will need edited (updater-script for most, but not all, ROMs).
If you are on an HTC device and you go grab a Touchwiz ROM to port, you're most likely going to have a bad time. Start with something that exists in large quantities for your device. AOSP ROMs are usually a great place to start.
Click to expand...
Click to collapse
I am on a nexus s and now i want TO port the touchwiz5. Can anyone help me? I am a student! I'm inexperienced, but I want to try.. Thanks .
Sent from my nexus s using xda app