Hello,
I am learning about rom development, and want some information about porting a rom from one version of the Nexus to another. There are a couple roms that are on the GSM Nexus that I would like to see on the Verizon Nexus. Where can I find documentation on what the differences are between the same rom running on both versions of the phone? Is this just the binaries found on the Google Developer page, or is there more that would be required for porting from maguro to toro?
There's more to it. There's some lib files that might be needed in order for some stuff to work properly. But its real easy tho. Make sure the ROM u want to port is the same android version. So for example u want to port a 4.2.1 ROM make sure your base ROM is also a 4.2.1 like cm 10.1. Then u just copy some files from one ROM to another. So u go into your ROM that u want to port and u open it with 7zip go to system folder and copy app fonts framework and media folder and copy them to your base ROM. Then u go into the lib folder and copy libandroid_runtime.so and paste that into system lib folder of your base. Then it should work. That would be the basic way of doing it. As far as building from source I can't help u there lol. Good luck.
Sent from my Galaxy Nexus using xda premium
Ok, how do I know which lib files I need? Is there somewhere I can go that says this file does this, this file does that? For example if the camera doesnt work, or if sound doesnt work, how do I know which files are needed for those?
Also, why copy the app fonts framework and the media folder?
Wingdom said:
Ok, how do I know which lib files I need? Is there somewhere I can go that says this file does this, this file does that? For example if the camera doesnt work, or if sound doesnt work, how do I know which files are needed for those?
Also, why copy the app fonts framework and the media folder?
Click to expand...
Click to collapse
Because the framework folder has all the mods from the ROM. As far as camera u don't have to worry about that since they are both the same phone. The only lib file u need to change is the one I mentioned. That's the one that usually will give u a problem booting up. But that's what I was told u need to change and it works.
Sent from my Galaxy Nexus using xda premium
Is there a place that documents what all of these files do? I am trying to go a couple levels deeper than just "Do it because it works". I am hoping to find a place that will explain why, so I can track down bugs when they pop up.
Wingdom said:
Is there a place that documents what all of these files do? I am trying to go a couple levels deeper than just "Do it because it works". I am hoping to find a place that will explain why, so I can track down bugs when they pop up.
Click to expand...
Click to collapse
I see. I'm not to that level yet. Try Google search or maybe even YouTube see if u find something. I do know u will need knowledge on how to use adb so u can do logcats when errors occur. Good luck man.
Sent from my Galaxy Nexus using xda premium
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
I once ported a version of minco to Toro before there was an official version. I figured out which files to swap by comparing file by file two roms - one maguro one Toro. Any file that was divergent file size got swapped except systemui.apk and frameworkres.apk. I used two bugless beast roms as a base. It worked perfectly.
Wingdom said:
Hello,
I am learning about rom development, and want some information about porting a rom from one version of the Nexus to another. There are a couple roms that are on the GSM Nexus that I would like to see on the Verizon Nexus. Where can I find documentation on what the differences are between the same rom running on both versions of the phone? Is this just the binaries found on the Google Developer page, or is there more that would be required for porting from maguro to toro?
Click to expand...
Click to collapse
There are hardly any differences. I looked at it a lot when the jelly bean developer preview was released for gsm devices and I 'ported' it for toro. I had a list of the differences, but apparently lost it. I want to say that there are only 10-15 differences. The way I found out what the main differences were was by comparing the same build of CM for toro and maguro using Beyond Compare using a binary comparison. Some files may be different, but if you compare the bits directly...you can sometimes see it's only a build date/time and not a real difference.
edit 1 - To try to answer some of your questions, try libsec-ril_lte.so and libsecril-client.so (and the apn stuff listed below) for signal AND bcmdhd.cal and bcm4330.hcd for wifi. For camera, I think I remember fRom being needed. For GPS, you'll want sirfgps.conf, gps.omap4.so, gps.conf, and lib_gsd4t.so from toro.
edit 2 - Ahhh, I found a post where I listed the difference between maguro and toro that I found (it may not be all inclusive, but it should give you a good start!). These were from the CM roms, so toro factory images have a couple more things like MyVerizon.apk, VerizonSSO.apk, VZWBackupAssistant.apk, and libmotricity.so (needed for VerizonSSO.apk).
Code:
\system\app\BIP.apk
\system\app\RTN.apk
\system\app\VZWAPNLib.apk
\system\app\VZWAPNService.apk
\system\etc\gps.conf
\system\etc\permissions\android.hardware.telephony.cdma.xml
\system\etc\permissions\com.vzw.vzwapnlib.xml
\system\etc\permissions\com.vzw.hardware.lte.xml
\system\etc\permissions\com.vzw.hardware.ehrpd.xml
\system\etc\wifi\bcmdhd.cal
\system\etc\apns-conf.xml
\system\etc\NOTICE.html.gz
\system\lib\hw\gps.omap4.so
\system\lib\lib_gsd4t.so
\system\vendor\etc\sirfgps.conf
\system\vendor\firmware\bcm4330.hcd
\system\vendor\lib\libsec-ril_lte.so
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Wingdom said:
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Click to expand...
Click to collapse
You have to modify the android policy jar in framework from code. There is a modded jar in the apps and themes forum, or you could try and lift the file or of your favorite custom ROM, like cyanogenmod.
Wingdom said:
Thank you! That is exactly what I was looking for. I do have one more question. How is a power menu (hold power button to get reboot, recovery, hotboot, etc..) added to a rom?
Click to expand...
Click to collapse
Glad to see you have some initiative! If you want the .smali edits for the advanced power menu, I have attached a .zip containing the comparison of the mod for my 4.2.1 stock AOSP rom. You need to add the 3 GlobalActions$11xx.smali files (in the attached .zip) to \smali\com\android\internal\policy\impl when you decompile your android.policy.jar with apktool. The 2 .pdf's show the smali edits to the 2 files that need modified. There are just a few lines added/changed. The changes for GlobalActions.smali are on page 19 of the .pdf. If you need a working apktool for 4.2.1, you can get one the I compiled using paulobrein's patch HERE.
I'm glad to see people helping a fellow who whats to turn user-to-dev.
Sent from my Galaxy Nexus using Tapatalk 2
Wingdom said:
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
Click to expand...
Click to collapse
Try flashing the radios. Here is a link: http://forum.xda-developers.com/showthread.php?t=1890585
Wingdom said:
Alright, I got the rom to boot, but I am not getting any signal or wifi. What files do I need to get these working? I want specifics, not copy over all files in a single folder, because I dont want to lose any of the customization already in the rom.
Click to expand...
Click to collapse
I know this is old but... How did it go?
I was trying to port cm-Resurrection_Remix_LP_v5.3.9-20150319-maguro to toro by comparing Resurrection_Remix_KK_v5.1.5-20140609-toro with that maguro but CM12 structure and format is completely different than KK...
Related
Contents:
Android 4.0.4/IMM76D deodexed ROM in flashable ZIP format. Will not produce errors when decompiling APK/JAR files.
Includes Superuser and boot.img root-level access. Does not include radio or recovery.
Changelog:
[R1/02APR2012]: ROM base changed from 4.0.4/IMM26 to 4.0.4/IMM76D. Files updated from stock IMM76D listed below.
Updated File List:
system/app/GoogleEarth.apk (v.6.2.1.6363 :: Earth)
system/app/googlevoice.apk (v.0.4.2.54 :: Voice)
system/app/Maps.apk (v.6.5.0 :: Maps)
system/app/Phonesky.apk (v.3.5.15 :: Play Store)
system/app/Wallet.apk (v.1.1-R57v4 :: Wallet)
system/lib/libearthmobile.so
Notes:
The need to wipe data beforehand is dependent on which ROM you're already using, but is advisable when possible for the sake of simplicity.
[R1] http://www.mediafire.com/file/48w84r8v3qbb8bw/NS4G-4.0.4-IMM76D-DEODEX-R1.zip
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
ssconceptz said:
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
Click to expand...
Click to collapse
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Killasmoke said:
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The procedures are the same as for other ZIP-based ROMs: download, transfer to phone, and flash through recovery. You may or may not need to erase your data (depending on which ROM you're coming from), but backing up your data beforehand is advisable and never hurts.
I haven't received any feedback regarding this specific ROM yet (I don't know if that's a good or bad sign). The main difference is that it's deodexed and will decompile without errors. I'm sure there are other threads with more in-depth information on IMM26 changes/improvements/issues.
SuperUser
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
I went to nexusshacks.com and downloaded the nexussrootICS.zip file (I think that's what its called). There's a SuperUser.zip file within that zip file. I moved the file to my phone and flashed it in recovery (wipe cache and dalvik cache of course). And its working well.
Sent from my Nexus S 4G using XDA App
mvilla8 said:
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
Click to expand...
Click to collapse
Thanks for bringing that to my attention. Uploaded an updated version in the OP that addresses the Superuser issue. Sorry for the inconvenience.
satuday said:
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
Click to expand...
Click to collapse
This update is from ChainsDD's site and has the latest Superuser app and binary. Should accomplish the same thing.
XK72 said:
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
Click to expand...
Click to collapse
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
I guess the Google Apps are included?
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Been using this since the 9th and I have to say it's very smooth. Very stock too, which obviously is what it's supposed to be. Just saying that for anyone who comes in looking for something customized. This is basically pure vanilla ICS.
Sorry for the delayed replies. I've been hammered by other obligations lately.
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
mabry said:
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
Click to expand...
Click to collapse
I'll try my best to post the steps later today or tomorrow. Sorry to keep you waiting.
akabadnews said:
I guess the Google Apps are included?
Click to expand...
Click to collapse
The stock Google apps are included. There are now two choices: One has the apps that were included in the IMM26 release (R3) and I have also included the latest app updates and related binary files as (R4).
The Batman said:
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Click to expand...
Click to collapse
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
xamadeix said:
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Sorry about that. I don't know what happened there. Link fixed.
XK72 said:
Sorry about that. I don't know what happened there. Link fixed.
Click to expand...
Click to collapse
Thank you
Sent from my Nexus S 4G using xda premium
Does anyone have problems turning Bluetooth on?
Sent from my Nexus S 4G using Tapatalk
XK72 said:
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
Click to expand...
Click to collapse
I would rather have the straight vanilla experience. Thanks for responding.
Edit: Also, touch to focus would be nice for the camera if at all possible. Thanks.
Hello Galaxy Nexus Xda Users!
Informations:
Here is a simple apk to odex automatically, easily and securely deodexed roms.
This apk has been coded by the famous Paul Obrien from Modaco Roms and Forums.
This guy is just a genious.
The original apk has been done for Galaxy S II but it works on Galaxy Nexus (tested working). --> Original thread: http://forum.xda-developers.com/showthread.php?t=1215271
Paul is even using it in his own Galaxy Nexus 4.0.4 Custom Rom here: http://forum.xda-developers.com/showthread.php?t=1487056
But I tested the apk on other 4.0.3 deodexed roms that you can find in the development section of the Galaxy Nexus and it is working perfectly (Aokp odexed rom is wonderful...)
Odexing a deodexed rom is giving you a boost in smoothness (you can see it in the launcher or in scrolling through system apps), performance and battery.
It gives you the flexibility to have a custom rom with modified system, framework and design AND all the tweaks that come with a custom rom in addition to the performance of an odexed stock rom.
To use it:
1) make sure you have a custom rooted rom / kernel with init.d support (scripts must be able to run at boot: it is a folder in /system/etc). It is very important or it won't run pre-boot scripts... Thanks to open1your1eyes0 who remarked it.
You can try this useful application to add init.d support to your ROM / kernel: http://forum.xda-developers.com/showthread.php?t=1933849
2) make sure that you don't have transparent status bar before odexing or you will loose your bar after odexing... (for AOKP users for example). Thanks to frantic912 who noticed it.
3) simply put the apk in /system/app folder with a file browser like "Root Explorer" (the folder must be in RW mode to copy the file)
4) do a nandroid backup in cwm and / or titanium backup of all your apps (even the system ones like Gmail)
5) then go to the launcher
6) tap "Odex me"
7) follow the instructions
It will:
1) reboot your phone
2) odex all the system staying on a black screen or on the Google screen a bit longer than normally (but it's normal)
3) put a ".odex" file with each app in /system/app
4) reboot again
5) go back to home
--> You will then see your boost in smoothness!
For people who are not convinced: check that: http://android.stackexchange.com/qu...e-difference-between-odexed-and-deodexed-roms
To see if it worked:
- Go to /system/app folder and see if there is a ".odex extension" for each system apk.
I attached the apk to this thread for ease of use.
Please write here your tests, opinions, questions, and thank Paul (and me for giving you this info ) for this wonderful and simple apk.
P.S. Please read reports from other users in the thread before trying the apk as some users seem to loose their status bar if they set transparency effects or some of them are having "force closes" if the rom they are using is too much themed...
P.S.2. Pay attention please, as androidphone2012 intelligently noticed, this apk can only odex *.apk files. The system framework is not odexed by it. To odex the framework too, please use the following script instead. It odexes *.apk files and Framework *.jar files too.
--> http://forum.xda-developers.com/showthread.php?t=2278586
If you already ran the apk to odex apk files, do not flash that zip: re-flash your ROM, GApps and MODs you're using and then flash the zip.
For your information, I tested the CM10.1 zip from the thread on my AOKP latest nightly build version and it worked flawlessly.
Looks cool. Nothing is attached to your post though.
Can I use it on other devices? (Galaxy si900)
I don't think this works. It rebooted and when I booted back and checked, there were no .odex files in the /system/app folder. Has anyone else got it working?
FYI, tested on 4.0.4 stock deodexed ROM.
raing said:
Looks cool. Nothing is attached to your post though.
Click to expand...
Click to collapse
Oups Sorry.
I was at work, I attached it but maybe when I posted the thread, it didn't put it...
I reuploaded it...
It's ok now.
Disregard previous post...
Did not have init.d support. Very important or it won't run pre-boot scripts!
raXoN91 said:
Can I use it on other devices? (Galaxy si900)
Click to expand...
Click to collapse
You can try, it could work.
I will try this week end as I go to a friend who has a Galaxy S and I will test on his phone.
Will report after but you could do a nandroid backup, test by yourself and report here too
open1your1eyes0 said:
Disregard previous post...
Did not have init.d support. Very important or it won't run pre-boot scripts!
Flashed init.d boot image. All good now.
Click to expand...
Click to collapse
Thanks. I knew that. Just forgot to post it.
I modified OP to inform about that.
++
So apparently I spoke to soon...
The app ran this time but after the reboot and odex process, my SystemUI wouldn't load and I ended up with no notification bar up top or any soft-keys at all. Also it was back to stock wallpaper. Not sure what happened, it looked like everything went through fine but I guess my SystemUI is borked.
Recovering from backup now...
I am not sure what caused this issue. I did have modded soft-keys and battery icon however, but I don't see why this would matter if a lot of the custom ROMs have modded soft-keys anyway. I would like to point out this was on stocked deodexed 4.0.4 ROM. If this works for anyone else, I would surely like to know. MAKE SURE you backup before trying.
Thank you Flolep
It works great for me, but I don't know why Gmail disappeared. But it's still in /system/app, so I tried to install and I get this : Application not installed
k0yuki said:
Thank you Flolep
It works great for me, but I don't know why Gmail disappeared. But it's still in /system/app, so I tried to install and I get this : Application not installed
Click to expand...
Click to collapse
It's a system app so you can't "install" it. It has to be flashed into the ROM. I have a feeling this app is not exactly the most reliable in working with all the apks.
open1your1eyes0 said:
It's a system app so you can't "install" it. It has to be flashed into the ROM. I have a feeling this app is not exactly the most reliable in working with all the apks.
Click to expand...
Click to collapse
Well. I didn't have any problem with it... Gmail was still there and my framework and system ui didn't have any problem after reboot...
I tried with modaco 4.0.4 rom that is near stock 4.0.4 deodexed rom and I tried with heavily customized aokp latest aokp build 25 rom, configured for my needs, battery percent, toggles, navigation controls in blue, etc, etc, and all worked seamlessly...
I add to first thread to do a nandroid backup before launching the process.
+ +
open1your1eyes0 said:
So apparently I spoke to soon...
The app ran this time but after the reboot and odex process, my SystemUI wouldn't load and I ended up with no notification bar up top or any soft-keys at all. Also it was back to stock wallpaper. Not sure what happened, it looked like everything went through fine but I guess my SystemUI is borked.
Recovering from backup now...
I am not sure what caused this issue. I did have modded soft-keys and battery icon however, but I don't see why this would matter if a lot of the custom ROMs have modded soft-keys anyway. I would like to point out this was on stocked deodexed 4.0.4 ROM. If this works for anyone else, I would surely like to know. MAKE SURE you backup before trying.
Click to expand...
Click to collapse
same as me...i'm using AOKP M3....but odex file is created on /system/app....maybe i need to backup framework-res.apk & restore it back after deodexed...
Sent from my Galaxy Nexus using Tapatalk
frantic912 said:
same as me...i'm using AOKP M3....but odex file is created on /system/app....maybe i need to backup framework-res.apk & restore it back after deodexed...
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Or try build 25 of aokp... It works for me...
Sent from my Galaxy Nexus using xda premium
I will keep in view for this app until more success cases reported
But I definitely will try after back from my vacation, wouldn't risk to brick my device on a trip ;p
I finally found the problem...
I forgot that the custom ROM I'm using needs a sort of modded Gapps pack to be install via CWM.
I think here is the issue.
Worked fine for me. GSM GN on AOKP B25. Just make a backup in cwm before you do it. Worst case scenario: it boot loops, you pop the battery, boot into recovery and restore.
Do you know the muffin man?
need to wipe n install b25 from m3....it's worth..?
Sent from my Galaxy Nexus using Tapatalk
frantic912 said:
need to wipe n install b25 from m3....it's worth..?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Well, for me, it is worth it as the added functionalities are very good...
did u notice any different after odex....mine before this at Quadrant got score 3250, now just 2500....
Well i will share my knowladge to you people, two years of learning stuff about android....
If this guide dont help you (0,01 possibilities) LOGCAT YOUR BUILD!! I WILL TRY TO HELP
Tools needed /by saranhai/:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
First to port an ics rom you need winrar.
This are the steps:
grab an ics rom like cm9 or aokp to take the libs and hw folders
Never unzip the rom.
1-from cm9/aokp copy all outside system, i mean boot.img mtd etc..... and past it over the rom you are porting (nexus s rom)
2-enter system/app and remove torch.apk, crespoparts.apk and replace camera.apk with aokp camera.
3-enter system bin and replace this files with aokp/cm9 ones
*dhcpcd
*bluetoothd
*vold
*wpa_client
*wpa_supplicant
Click to expand...
Click to collapse
4-enter system etc and replace this files with aokp/cm9 ones
*bluetooth folder
*dhcpcd folder
*Apnconf.xml
*wifi
*vold.fstab
*vold.conf
Click to expand...
Click to collapse
5-Then we go to the libs, enter system/lib and replace:
*HW folders
*modules folders
*egl folders
*libril.so
*libsec-ril.so
*libreference-ril.so
*libsec-ril-client.so
*libbluedroid.so
*libbluetooth.so
*libbluetoothhd.so
*lib_cameraclient.so
*libcameraservice.so
*libhardware_legncy.so (very important to wifi to work) hell this caused me problems
*libEGL
*libgles (the 3 files)
Click to expand...
Click to collapse
--------------replace usr and vendor folders-------------------
And last edit build.prop, well first check if it boots then you change this and add this.
edit this:
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ADD THIS TO SIGNAL TO WORK!!
additional build propieties
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3
=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
Click to expand...
Click to collapse
ADVANCED USERS ONLY (dont ask me how) :
for working external sd (emcc) you need to decompile/recompile framework-res.apk
you need to change this:
xml/storage_xml with other storage xml from aokp or cm9
Click to expand...
Click to collapse
I´m not responsible for bricked devices (this shouldnt brick it) but i dont want anyone crying because i will laugh at you, it works for me..
Libs functions
Lib:
*Libhardware_legancy.so (makes wifi works)
*all libs with ril: DATA and SIGNAL
*LibEGL, modules, hw: hw aceleration, lights,etc...
*Libgles (Gpu and cpu)
Click to expand...
Click to collapse
etc:
*apns-conf.xml (all related to apn and services)
*dchcpd,vold.ftsab,vold.conf: internal sd
*wifi,bluetooth: wifi bluetooth lol
Click to expand...
Click to collapse
someone correct me if im wrong but im preaty sure what im writing...
Thanks for this thread. It should give many new possibilities!
amazing guide thx for sharing
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
EDIT: Forgot this...
If you are experiencing issues booting up, here's how to get a logcat so you can figure out what's wrong:
connect phone to computer
open up command prompt
navigate to your android sdk tools folder i.e C:/androidsdk/platform-tools (ADB MUST BE SET UP BEFOREHAND)
type in:
Code:
adb logcat
watch as a whole bunch of text scroll by, don't bother reading it right now, do it later.
If you want to stop the logcat, just disconnect phone from computer.
-Saranhai
saranhai said:
Things i would add:
7zip (alternative to winrar, doesn't matter which you choose to use)
Notepad++ (highly recommend if you're on windows, used to edit build.prop and other text files)
Android SDK/ADB (MUST HAVE, for troubleshooting and such)
dsixda kitchen (could come in handy)
I will add more if i think of any
-Saranhai
Click to expand...
Click to collapse
Okey i added them
Nice guide. Thanks.
Nice guide!!! Thanks!
Will try this out later
Sent from my PG86100 using xda premium
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Driv said:
i have a question ... How you can test your own ported rom ? Because i dont want to brick my phone (again) ))
Click to expand...
Click to collapse
oh, haha i dont think there is another way rather than using your device as a lab rat.... lmao
I give you an unbrickeable guide, if you dont forget to swapp the boot.img and hw and modules folder you wont brick it since recovery is on the kernel, so you can restore or do what you want, if you flash a nexus s kernel (as example you forgot to remove it) you will soft brick it
Madflapjack respond to your pm's, I need some help!
EDIT: resurrected a dead thread sorry..
Sent from my GT-I9000 using xda app-developers app
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
exactly what i want to ask for. since nexus S got the OTA official update.
malcho said:
Madflapjack,
Hope you are ok.
Does this guide works with jellybean roms?
Click to expand...
Click to collapse
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Madflapjack said:
im ok thanks for asking !! i moved to the galaxy nexus thats why im not posting much lol, im playing with the baby!
to the point, you should try, it wont harm, but if you do try, dont port aosp, they need special coding in framework or something similar and you will get a nice dark screen on booting, well if its cyanogenmod or aokp then yes it should work..
Click to expand...
Click to collapse
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
malcho said:
Nice to see that you are ok.
My constant struggle with codenameandroid,trying few guides butt none work.
It's ok i will wait till sources are out.
Many regards
Click to expand...
Click to collapse
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
T
Madflapjack said:
jb codenameandroid? it should work, worth the try!! but well remember to replace the kernel so you dont lose your recovery and your good to go.
if i dont bad remember my codename android port was booting and all ok, i was talking about pure aosp,
Click to expand...
Click to collapse
I tried butt it stuck on boot animation.
Trying tommorow again.
malcho said:
T
I tried butt it stuck on boot animation.
Trying tommorow again.
Click to expand...
Click to collapse
so it boots, try watever you know to make it boot, if not logcat. lol
I just wrote a script that would automatically port ANY carrier's gs3 roms to ANY other carrier's devices
So now u can use all the roms other carriers get
Let me know if there are any errors(not including not found errors)
THIS ON OMG! DROID
http://omgdroid.com/script-released...-iii-custom-rom-to-any-other-carriers-device/
The future of this:
1. Ill add all the proprietary files from all the carriers so u dont have to have a base. DONE
2. UNIVERSAL ZIPS FOR ALL US GS3S THIS WILL TAKE A LONG TIME CUZ I HAVE TO LEARN HOW TO USE AROMA OR WRITE AN UPDATER-SCRIPT BUT IT WILL COME!!!(If anyone wants to teach me how to do those just pm me.) DONE BUT NOT GONNA RELEASE YET
3.Ability to automatically port ANY phones ROM to ANY other phone as long as they have the same dpi, manufacturer, and arm version. WORKING ON THIS. LEARNING PYTHON
How to use:
Linux:
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. open a terminal and cd to the directory
5. run:
Code:
chmod +x portscript.sh
./portscript.sh
6. PROFIT
FOR WINDOWS I RECOMMEND CYGWIN AND THE LINUX VERSION. THE WINDOWS VERSION IS KINDA MESSED UP.
Windows(experimental):
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. rename the rom you want to port's folder to port
5. double-click on portscript.bat
6. PROFIT
How to port rom from galaxy nexus or any other xhdpi armv7 samsung device:
1. inside ur base rom, open META-INF/com/google/android/updater-script as a text file and copy the mount points (like mount(/dev/block/mmcblk0p8, /system) you would copy /dev/blockmmcblk0p8)
2. Download script and do the porting procedure
3. open up the rom u are porting's META-INF/com/google/android/updater-script and replace the mounting with the values u copied.
4. save and move the updater-script to ur base's META-INF/com/google/android/ and replace
NEW!!!
NO NEED FOR BASE:
1. download the nobase script zip and extract it somewhere
2. download a device's proprietary files zip and extract it into the folder of the script
3. run the script and follow directions!
how to add a device to the nobase script:
download and unpack the zip with ur desired carrier/android version
run the portdiffs.sh and follow directions!
Disclaimer:
Im not responsible for anything that might go wrong
Changelog:
v3: more fixes
v2: fixed update-binary being update_binary
DLs:
.bat s are windows, .sh is linux.
portscriptnobase is linux
https://docs.google.com/folder/d/0B2qlFDXo6JOreUY3RjFkRm1aeFU/edit
Thanks to d3athsd00r for helping
does this apply for international GS3????
ice3186 said:
does this apply for international GS3????
Click to expand...
Click to collapse
Probably
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
What!! No way dude!!
White Hot! GS3.
cpu999 said:
I just wrote a script that would automatically port ANY carrier's gs3 roms to ANY other carrier's devices
So now u can use all the roms other carriers get
Let me know if there are any errors(not including not found errors)
How to use:
1. download the rom u want to port and a rom on the SAME android version as the rom u want to port
2. unzip both of them and place both folders in the same folder
3. download the script and place it in the folder with the two rom folders
4. open a terminal and cd to the directory
5. run:
Code:
chmod +x portscript.sh
./portscript.sh
6. PROFIT
Disclaimer:
Im not responsible for anything that might go wrong
DLs:
Realease 1 (Prealpha)
Click to expand...
Click to collapse
I am probably treading into an area that I have no business going to - but I would love to try this - and don't have enough knowledge to follow your instructions - was hoping you could explain the last few steps - I am going to sound like a real noob - but I don't understand some of the language -
what do you mean when you say "open a terminal and cd to the directory" ? if you can simplify that a little - I think I can do this and would love to try -
I think it means that I need to put save the roms and the script you have provided and place them in my C drive - then open a command prompt in that file (shift and right click I believe) is that correct?
second question - when I tried to download the file you provided from the lnk - it opened GOOGLE DRIVE and said I needed to request permission to access the file - ? I clicked request and am now waiting for some kind of response
?
cpu999 said:
Probably
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
No that will not work. If this does simple recovery mount point changes & build prop changes that will work for the family of SGS3 that share the same hardware. It will not work for i9300 as that has a different set of hardware. Thus, different libs and what not.
I doubt this script has the ability to decompile & merge correctly smali. Or has a downloadable collection of libs for i9300. Probably only works for the SGS3 variants like AT&T, telus, tmobile, etc.
iBotPeaches said:
No that will not work. If this does simple recovery mount point changes & build prop changes that will work for the family of SGS3 that share the same hardware. It will not work for i9300 as that has a different set of hardware. Thus, different libs and what not.
I doubt this script has the ability to decompile & merge correctly smali. Or has a downloadable collection of libs for i9300. Probably only works for the SGS3 variants like AT&T, telus, tmobile, etc.
Click to expand...
Click to collapse
Thanks
will be adding that to the OP
mocsab said:
I am probably treading into an area that I have no business going to - but I would love to try this - and don't have enough knowledge to follow your instructions - was hoping you could explain the last few steps - I am going to sound like a real noob - but I don't understand some of the language -
what do you mean when you say "open a terminal and cd to the directory" ? if you can simplify that a little - I think I can do this and would love to try -
I think it means that I need to put save the roms and the script you have provided and place them in my C drive - then open a command prompt in that file (shift and right click I believe) is that correct?
second question - when I tried to download the file you provided from the lnk - it opened GOOGLE DRIVE and said I needed to request permission to access the file - ? I clicked request and am now waiting for some kind of response
?
Click to expand...
Click to collapse
this script only works in linux for now.
Ill create a windows one once I have time
LuRock said:
What!! No way dude!!
White Hot! GS3.
Click to expand...
Click to collapse
Its just an automation of my method of porting
yea it def will not work for 9300 youll have to change a lot of stuff just to get it booting
cpu999 said:
this script only works in linux for now.
Ill create a windows one once I have time
Click to expand...
Click to collapse
so if lets say i got a tmobile gs3 and want to port an att rom, will it add wifi calling too?
even if it ports the wifi calling from tmobile..it won't work on att. it'll not be recognized as it requires tmobile service to really work.
Sent from my SAMSUNG-SGH-I747 using xda premium
lazarat said:
so if lets say i got a tmobile gs3 and want to port an att rom, will it add wifi calling too?
Click to expand...
Click to collapse
no.
this is just a simple script that would port things.
it just makes the rom compatible wiht ur phone
cpu999 said:
no.
this is just a simple script that would port things.
it just makes the rom compatible wiht ur phone
Click to expand...
Click to collapse
Oh ok thanks..althogh up till this point i have had no problems using att roms on my tmo gs3
Being a windows user I have to wait until you create a version for that - can't wait to try i t- I am not a developer but if this works - it opens all kinds of opportunties to try new thing s- I am adventurous = and I ahve insurance on my phone - lol - looking forward to giving this a shot -
I was wondering when someone was going to do this. I was going to if I could ever get time away from my real job. Thanks for the contribution!
Sent from my GS3 using xda premium
Sorry of this is a dumb question but if this script works then I could use this to use T-Mobile roms on my att s3?
Sent from my htc_jewel using xda app-developers app
wwevoxnj said:
Sorry of this is a dumb question but if this script works then I could use this to use T-Mobile roms on my att s3?
Sent from my htc_jewel using xda app-developers app
Click to expand...
Click to collapse
its ANY us gs3 rom to ANY us gs3 rom
Wow I can't wait for a windows version of this!! I'm addicated to flashing roms haha.
Sent from my htc_jewel using xda app-developers app
I've flashed many T-Mobile roms on my at&t / rogers s3 already...
FreeGS3 r6, Gigajule, Wicked v5 all works great as long as you flash the right kernel and never flash a modem...
Sent from my SGH-T999 using Tapatalk 2
Morning managed to get 4.2.2 from the gsm version of galaxy nexus working on my vzw galaxy by changing the build prop and adding and deleting some files in the lib folder and adding and deleting xml's for the vpn.. the 4.2.2 I flashed isn't mine so I take no credit for it just used it to flash because it was deoxeded and rooted already... it was zipped by bigxie (bigxie_magurTA_JDQ39-signed.zip) just look in the gsm galaxy nexus thread. Flashed rom first then flashed current vzw radios and then moded files and set permissons. The files were:
sys-Vendor-lib" libsec-ril_lte.so from 4.2.1 and deleted libsec-ril.so from "lib"
"ECT" apns-conf.xml from 4.2.1 and deleted the original file
"ECT--PERMISSIONS" com.vzw.hardware.lte.xml from 4.2.1 and com.vzw.hardware.ehrpd.xml and deleted com.hardware.telephony.gsm.xml
Modded Build.prop for cdma and lte...(there wasn't to many but not gonna list them all)
wiped cache and dalvik and now have a strong 4G signal and fast data...not a developer here at all, just tried to figure out how to get lte and vpn on 4.2.2 so sorry for bad post...good luck..
Mwalt2 did a complete mod in zip form with bigxie rom that is a smoother and grabs signals better and no messing with permissions and everything like that so way easier...here is the link
http://forum.xda-developers.com/showthread.php?p=37928151&posted=1#post37928151
hmm somethings not right with a 909 KB file
proceed with caution
uninc4709 said:
hmm somethings not right with a 909 KB file
proceed with caution
Click to expand...
Click to collapse
the 4.2.2 rom isn't in there just the files I added, screen shots, and the modded build.prop, but just a weekend warrior here so not sure if I just got lucky but all is working good so far
pricematthew4143 said:
the 4.2.2 rom isn't in there just the files I added, screen shots, and the modded build.prop, but just a weekend warrior here so not sure if I just got lucky but all is working good so far
Click to expand...
Click to collapse
There are a few other things that will need changed. I'd think that your GPS and WiFi aren't going to work well or at all. I've posted a list of CDMA files that need to be included on this forum before and I think in the q&a gnex forum (search there first for posts by me and see of you can find it...I would but won't be on a PC for awhile).
Sent from my Galaxy Nexus using Tapatalk 2
mwalt2 said:
There are a few other things that will need changed. I'd think that your GPS and WiFi aren't going to work well or at all. I've posted a list of CDMA files that need to be included on this forum before and I think in the q&a gnex forum (search there first for posts by me and see of you can find it...I would but won't be on a PC for awhile).
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
They worked but weak better now though thanks for the help..I was just happy I got the 4g to work lol..thanks
Sent from my Galaxy Nexus using Tapatalk 2
notice any difference from 4.2.1.?
Yeah it seems to be smoother in the animations and the color band is a lot less..lock screen widgets are different, larger
Sent from my Nexus 7 using Tapatalk HD
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
jsgraphicart said:
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
Click to expand...
Click to collapse
i understand that thats a gsm version. but to get this going don't i have to flash that rom as a the base and follow the op by replacing the system files?
they would be set rw-r-r correct?
i may just hold off a few days but im anxious to get these bugs fixed :laugh:
andrewlax120 said:
i understand that thats a gsm version. but to get this going don't i have to flash that rom as a the base and follow the op by replacing the system files?
they would be set rw-r-r correct?
i may just hold off a few days but im anxious to get these bugs fixed :laugh:
Click to expand...
Click to collapse
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
yeah that's what worked for me, the rooted 4.2.2 and those files and i got 4g, and the correct vpn showing afterwards...even the baseband showed correct after the build prop changes so Yep...should work out just don't forget to set permissions and delete the gsm files..
jsgraphicart said:
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
Click to expand...
Click to collapse
yes the permission are set rw-r-r or 644 and it was kind of easy you just have to get lte/cdma files in the lib or ect so the rom knows to look for lte or cdma and not gsm...all they are are xml files and just have to add a bunch of ro.cdma and change the name in build prop..i was actually surprised how easy it was when the baseband showed correct and I got a blue 4g signal
jsgraphicart said:
That link is for the GSM Galaxy Nexus. I wouldnt flash that on your Verizon Galaxy Nexus. If I understand this right, the zip file given here are just the files you have to manually replace yourself in a file browser and not a flashable zip.
Click to expand...
Click to collapse
no...I did flash the GSM 4.2.2 on my CDMA VZW GN, there is NO GSM RADIO IMAGE on the 4.2.2 GSM ROM the dev removed it.. so there is not damage to the CDMA GN... so you are just flashing a ROM meant to pick up GSM, all you have to do is replace the files so the rom picks up lte/cdma...and all they are are xml files and one .so file and the build prop to tell the phone where to look...thats all...it was actually really easy
jsgraphicart said:
I just re-read the OP and I guess thats what he did. Flash the GSM zip and replace files with Verizon files. I havent tried it. I, personally, am going to wait for something else.
Click to expand...
Click to collapse
yep, just replaced the gsm .so and xml's with lte/cdma and changed build prop so the phone can figure it out..that's it.
andrewlax120 said:
cool, so for this to work should i flash
this:
http://forum.xda-developers.com/showthread.php?t=1737849
and then the zip you posted?
Click to expand...
Click to collapse
and sorry for the confusion that zip is NOT flashable just the files I used to get the rom over to lte/cdma..I used root explorer to add the lte/cdma files and for setting perms
Hij,
I tried doing the same on Sprint Galaxy Nexus.. But it didn't work. Do you have any tips?
Cheers
mkalter said:
Hij,
I tried doing the same on Sprint Galaxy Nexus.. But it didn't work. Do you have any tips?
Cheers
Click to expand...
Click to collapse
the only way i figured it out was to look at the build prop especially the RIL lines..they give the exact file that needs to be replaced
ex. on the gsm: rild.libpath=/vendor/lib/libsec-ril.so libsec-ril.so is the driver the rom is looking for
I replaced the file in the "lib" folder and build.prop line with rild.libpath=/vendor/lib/libsec-ril_lte.so so the rom will now look for the lte driver
make sure the "telephony.lteOnCdmaDevice" line equals 1 it tells the phone that it is a lte/cdma device..if there is a 0 the phone thinks it is a gsm device
also don't forget to set permissions as rw-r-r as they are in screenshots and to delete out the gsm files ...they aren't named the same so there is no overwrite or replace.. you have to delete them. I don't know how sprint files and radios are setup though but I hope this helps...
You guys may as well replace the files in the gsm zip before flashing it and save yourselves some time. There's no reason to do it after unless you just like using a file explorer on your phone. Also, an easy way to see what is different is to compare CM roms for the gnex.
Sent from my Galaxy Nexus using Tapatalk 2
Have binaries for 4.2.2 been released yet
Sent from my Galaxy Nexus using Tapatalk 2