Develop Bugs

[How To] [GSM] Getting started with porting

Ok, so after having a million questions I thought I'd write up a quick little 'how to' with regards to porting.
And now the warning
Read and learn first, doing this could cause serious issues with your tab or even brick it. The tab is really tough, and hard to brick if you do everthing right but it could still happen. I'm not responsible if it does.
Where to start
Get good at reading, google searching and searching XDA. Lots of porting discussion regarding other phones can apply to the tab.
Learn to use Heimdell
Have a linux distro available, either by virtual box, or natively.
Technomancer where it all began
I've said it before and I'll say it again, without techs work miui wouldn't have been possible.
Reference technomancers thread here: http://forum.xda-developers.com/showthread.php?t=931857 on how to download the cm7 + sgt source, you're also going to want to follow the kernel making part, cause most likely you'll need to make adjustments to the init.rc which is inside the initramfs and requires building the kernel again.
porting x build
Get X build onto your computer and extract the update.zip for it.
Copy the boot.img into your linux environment and extract it using splitbootimg.pl script (note: Google it, plus this doesn't work with samsung builds). Compare the init.rc to your init.rc (from the sgt cm7 kernel source root folder). Specifically the most important part here is the PATH, LD_LIBRARY_PATH statement and BOOTCLASSPATH lines.
Build your kernel with the updated init.rc and flash with heimdell, it should still boot your cm7/miui build (if you were running it before) albeit with errors.
The system
Now following the awesome list of proprietary files (either from your source folder or technomancers github link) check the galaxytab-common-vendor-blobs.mk for the GT-P1000. It lists every file you need that's propreitary to the tab and where to put it.
Also you'll probably need the debuggerd from /system/bin on the cm7 build.
Compare the /system/build.prop of the cm7 build to your port, make sure the ril info is the same as well as the ro; model, brand, device, board, and platform lines.
Create an update.zip (or whatever you want to call it.zip) and try it.
It's not booting
Logcat is great, but I really suggest using the ddms from the android sdk tools. It's color coded, and gives a much nicer view of what's happening.
Using winmerge in windows or a linux file compare program start checking what other bin files may be missing that you require. Special notice to the xbin folder.
It works! I want to post it!
Ok, first up, make sure you have permission if this is someone elses custom build you've ported. Most people/groups are really good about it assuming you ask first and give them credit in your post.
Also credit everyone who helped, answered a question or sent you in the right direction. (it's just polite)
Second your going to want to make sure your update.zip flashes the kernel, read the update_script from the cm7 build to understand how it works.
So that's it for a start. roll up your sleves, gather your courage and get to it!
Please if you have other tips, add them to the thread, what's better 1 or 2 'developers/porters' or 100?

Thanks. This is very useful for me.

Thanks,
Following this method, with slight alterations to adjust, I was able to port an i9000 phone build to the tab in about 10 minutes, it's really not terribly that difficult once you have the right steps.
The first couple times are usually frustrating but after that you get the hang of it

Hi mssmison Thank you for your guide,it will be very useful in the future! I have only one request,how can I contact you? I have a proposal for you about a dev team (regarding an old think tank)

Thanks for the guide...
Is there any ROM left to port by the way?
Sent from my GT-P1000 using XDA Premium App

Camera not working on 4.1.1. AOSP VZW full_toro ROM

Please accept my apologies if this has been answered before. I did a search and did not find a similar problem. I am a noob and will read any guide or how to that you refer me to in order to learn how to get better. I am new to Ubuntu/Linux and terminal but if you point me in the right direction I can probably figure it out. I will try to provide as much detail as possible.
I have recently built a Jelly Bean AOSP ROM following this XDA Guide.
I am using Ubuntu 10.04 LTS x64.
repo synced with this branch
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r3
which is build JRO03H
I downloaded and extracted the binaries on the Nexus Binairies page. I did notice that prior to building that unlike the ICS branches the JB device/samsung/toro folders do not have a extract-files.sh file
I made an otapackage using the full_toro-userdebug command.
I flashed the rom using ClockworkMod 6.0.1.0. I did a factory reset and wiped the cache prior to flashing. I also installed gapps-jb-20120726. Everything booted up fine and for the most part everything works except for the camera app. When I press the camera button I receive a message that says "Unfortunately, Gallery has stopped working." Or I get a black screen and nothing happens then I'm back in the app drawer. I have tried fixing the permissions and that did not fix the problem.
Can you explain to me what I need to do to get my camera and gallery app working? This is the only issue I have with my rom thus far. Do I need to extract the camera binary some how?
The camera and everything works fine my AOSP IMM76L build but not with my JB Build.
I have flashed other roms such Peter Alfonso's JB rom and his camera works fine, so any directions or links would be greatly appreciated.

Seeing the same.
I have this same JRO03H build (except I use CentOS 6.3 to compile AOSP 4.1.1_r3) with the EXACT same issue you describe. When the camera applet is selected it complains "Unfortunately, Gallery has stopped". Everything else in the build (24hours+ fresh) appears okay so far.

I fixed it.
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.

could you please share your Rom? I also have the same issue. but still not fix it.
paternal_techie said:
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.
Click to expand...
Click to collapse

wangyu7988 said:
could you please share your Rom? I also have the same issue. but still not fix it.
Click to expand...
Click to collapse
I am uploading to mediafire as I don't think I have a high enough post count to post the rom here.

I need a smart Dev to dummy something down for me...

I have been in love with all things Android for years but there is a certain level of proficiency that I don't think I'll ever reach. I'm reaching out to anyone who can provide me with some assistance in this issue. I have a Nexus (my wife's) that constantly crashes the Talk and Camera apps. I've tried dozens of solutions posted online but I think the only one that actually addresses my issue is provided in the link below. Unfortunately, when it comes to compiling Android source code I get in over my head.
Could someone please give me instructions on how to implement this fix? I would like to run AOKP JB Milestone 1. It appears I need to swap out the binaries before compiling and flashing this ROM but that's about as much as I can tell.
Please help!
Link describing the fix -------------> http://anders.com/cms/435

Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium

mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
See, this is where I'm confused. I'm not compiling the ROMs or any of the gapps myself. I'm flashing a copy of AOKP that I used on other nexus devices and had zero issues. For some reason this phone won't work quite right. I've wiped, clear data, fixed permissions, blah blah blah.
From hefty googling I have found a decent number of other threads with my exact problem but none of the threads actually have a solution.

mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
ANY AOSP rom should have these binary files.
http://forum.xda-developers.com/showthread.php?t=1386615

So in other words, it doesn't sound like this will solve my problems then, huh?

cartisdm said:
So in other words, it doesn't sound like this will solve my problems then, huh?
Click to expand...
Click to collapse
Check logcat/dmesg right after you reproduce the issue. (ref: http://forum.xda-developers.com/showthread.php?t=1812959)
We need more insight/details as to why it is failing.
Your wife's phone currently runs:
carrier: ______
rom: _____
rom build number: _____
kernel: _____
bootloader: ______
radio: ______
Have you tried starting fresh, flashing nexus factory image through fastboot, as per (ref: http://forum.xda-developers.com/showthread.php?t=1626895) ?

[Q] Compile CM9 help

After following this tutorial I compiled CM9 for my r800x and everything works fine but since I first compiled I have edited the SystemUI sources. The problem is when I compile it doesn't compile the new sources. Anyone know what I'm doing wrong? Sorry if this is a noob question.
Extra information (not sure if important but might help find the cause):
Using Xubuntu 12.10
Oracle Java 6
I edited /frameworks/base/packages/SystemUI
I compiled for zeusc instead of zeus

What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
http://source.android.com/source/initializing.html said:
export OUT_DIR_COMMON_BASE=<path-to-your-out-directory>
Click to expand...
Click to collapse
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop

Trooper_Max said:
What more specifically did you modify? Not sure why it would not rebuild, unless there's some kind of issue with the timestamps or your system clock. (It knows to rebuild if the source files have a newer timestamp than the compiled files they produced)
You can always just do a clean build. You can even just change the output directory without messing up your current build:
You can set that to a different directory and it will build it all over again, putting all the output in that directory instead. With this different, it won't affect the output of your current build and you can always clear this variable to go back. Then you can use this for comparison. Alternatively you can just wipe out your output directory and build it over. You may also be able to dig into your output directory and delete the compiled files for the sources you have modified and then it should definitely notice and rebuild those.
EDIT: Also note that there are build instructions on the CyanogenMod wiki: http://wiki.cyanogenmod.org/w/Build_for_zeus
On the repo init line you can also say '-b jellybean' instead of ics and it will build CM10 (which is pretty good too but not fully stable, it's CM10.1 that is more unstable)
I also noticed that in the 'stable' release of CM9 for zeus the proximity sensor does not work, but there are patches for it in the repo and I've built from source with CM10 and it works fine.
~Troop
Click to expand...
Click to collapse
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.

bandoncontortion said:
Never even thought about changing the location it is output to or anything like that. Kinda feel dumb not trying that but I will soon. Also I've looked at CyanogenMod's wiki already. And is CM 10 working on zeusc? I thought it was still only zeus but I haven't checked in a while.
Click to expand...
Click to collapse
Cj360 made a zeusc version and uploaded it to fxp cm10 page. I've tested it and it works great
Sent from my Xperia Play (r800x)

Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.

bandoncontortion said:
Also all I did to SystemUI was add one .java file. I didn't know zeusc had cm 10. I'll check it out.
Click to expand...
Click to collapse
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop

Changing the timestamp didn't do anything. I'll try deleting the already compiled files and recompile everything over again tomorrow. Also CM10 is a lot better in my opinion too so I'll try it now so hopefully it'll work and fix the problems I'm having.

Trooper_Max said:
Make sure the timestamp of the file you added is newer than the time you built. Otherwise, make will not realize there is a new file. Seems like you must have modified some other source file though to make use of the new source file.
A simple way to update the timestamp of a file is the "touch" command. If you touch a file before your build, it should always rebuild that file unless you have more serious problems.
Also, I forgot about the zeusc not being as well supported... so hopefully all the fixes for CM10 on the zeusc are in the repositories.
I do like CM10 better than CM9... especially since I figure if we're going to ditch stock-based GB, there's even less reason to live in the past.
~Troop
Click to expand...
Click to collapse
CM10 works good on zeusc. Haven't found any bugs and I added the changes to it's SystemUI and it compiled it for me and works great. Thanks for the help!

[Q] RIL Development sgh-t999

Hi everyone,
recently I have built and flashed on my sgh-t999 (galaxy S3 US tmobile version) CM11 Nightly. For my pro0ject however I need to modify two libraries of the Radio Interface Layer (RIL), libril.so and libreference-ril.so. I tried to modify the ones in the forlder /hardware/ril/ and build everything again with no results. Any change that I made to those files (such as ril.cpp in the folder libril) would not affect the functionality of the phone.
Finally yesterday I understood that when I build those libraries for the target cm-d2tmo-eng, those files that I have modified are not considered at all! When the libraries are built indeed, the system automatically takes the libril.so and libreference.so present in the vendor folder!
The problem is that those libraries in the vendor folder and already compiled and I cannot modify them. The question is:
Is there any way that I compile those libraries from the source code that I have modified?
Thanks,
brok85

Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
Click to expand...
Click to collapse
Well, as fisrt I just wanted to insert some log to be able to follow the code execution from the logcat or do something similar.
Perseus71 said:
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
Click to expand...
Click to collapse
Sorry but I am kind of new on this things. I have already downloaded the source code from the device tree and made my modifications in the files ril.cpp contained in [path-to-android-source]/hardware/ril/libril/ril.cpp. What I did was commenting the whole code within the function RIL_onUnsolicitedResponse() and listenCallback() such that in theory, the phone is not able to display incoming calls for example. However after flashing the re-built android I am still able to receve calls. How can I "check in the changes if they boot ok on my device"?
Perseus71 said:
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
I tried to remove the libril.so in the vendor folder and compile again using
# . build/envsetup.sh
# lunch (and select d2tmo)
# mmm [path-to-android-source]/hardware/ril/libril".
The problem is that when I indicate the target after lunch, the compiler looks for the vendor libraries and stop the build. What I am doing wrong?

Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.

Perseus71 said:
Given that there is a unified D2LTE Build on CM, can you elaborate on what changes you wish to make to these libraries ?
To answer your question, You can do one of two things.
Grab the CM Source Code from the Device Tree of D2LTE. Make your relevant changes and check in the changes if they boot ok on your device. That way those changes will be included in future builds of CM and other Roms that use it.
If you do not wish to do so, then you will have to compile those libraries using C++ Compiler on a *NIX box and replace them in the Vendor folder.
Click to expand...
Click to collapse
Perseus71 said:
Sounds like Compiler Dependacy path is set different from the code base. I will look further before commenting.
For when your changes are for the benefit of the community of users, you check in the changed code back to the Device Tree with detailed comments within the code and while checking in.
Click to expand...
Click to collapse
Actually this is what I get after deleting
libril.so in vendor/samsung/d2tmo/proprietary/lib/
and after executing mmm /hardware/ril/libril :
No private recovery resources for TARGET_DEVICE d2tmo
make: *** No rule to make target `vendor/samsung/d2tmo/proprietary/lib/libril.so', needed by `/home/brok85/Documents/android/system/out/target/product/d2tmo/system/lib/libril.so'. Stop.
make: Leaving directory `/home/brok85/Documents/android/system'

If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links

blackbeard said:
If u want to build from source, delete the line that copies in vendor-blobs.mk
If u want to copy the blob instead of building it from source, keep the line
It'll be better if u provide us the device and vendor trees links
Click to expand...
Click to collapse
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?

brok85 said:
I am not sure to understand what should I provide Sorry, as I said I'm kind of new here...
Also, I can not find vendor-blobs.mk...Where it should be?
Click to expand...
Click to collapse
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
And vendor-blobs.mk would be present in the vendor folder under your device folder

blackbeard said:
You said you built a cm11 for ur device. So for that you needed the device and the vendor trees. Give the link of those, if they are on the git
Click to expand...
Click to collapse
Well I have followed the guide in the following page
http://wiki.cyanogenmod.org/w/Build_for_d2tmo
The link from where I have obtained the repository is
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
and then
$ breakfast d2tmo
blackbeard said:
And vendor-blobs.mk would be present in the vendor folder under your device folder
Click to expand...
Click to collapse
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
thanks a lot for the help guys

brok85 said:
Actually now I think I was able to compile the library following your instructions. Unfortunatly, when I have built and flashed everything in the galaxy S3, I was not able to use the network. Probably some compatibility issue?
When I compiled libril.so, I have obtained it from the folder /hardware/ril/libril which should contain google source code, maybe not compatibale with my device...is it right?
Click to expand...
Click to collapse
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all
I have compiled CM11 as it is and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
The procedure I have followed is the following one:
1) Delete the llibril.so and libreference-ril.so from the vendor library. These are the pre-compiled vendor libraries that I need to modify.
2) commented the lines from the vendor-blobs.mk that were including those two precompiled libraries.
3) go to android/system/ and run "mmm /hardware/ril/libril" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so respectively.
4) copied the new libraries just obtained in the vendor folder where the pre-compiled libraries were
5) re-include the lines commented in point 2).
6) run brunch d2tmo
7) flash the .zip obtained
Any mistake?

Perseus71 said:
You know, silly question. But just so we can rule out. Did you at any point compiled the CM11 code as is and flashed to the phone ? How did Network behave ? Was everything ok ?
Click to expand...
Click to collapse
No silly question at all. Yes I have built everything out of the box and worked perfectly. I could use the network.
Perseus71 said:
Galaxy S3 is a very open platform with standard hardware and chipsets. So the Default google code should work out of box with it. If you have network issues, then just for kicks you can flash a custom Kernel on top of your compiled CM 11. See how that goes.
Click to expand...
Click to collapse
I followed the following procedure to include my modified libraries:
1) Eliminate precompiled vendor libraries: libril.so and libreference-ril.so from the vendor folder
2) comment lines in the vendor-blobs.mk that included those two precompiled libraries
3) from /android/system/ executed command "mmm /hardware/ril/librail" and "mmm /hardware/ril/reference-ril" to obtain the modified libril.so and libreference-ril.so
4) copied the new libraries in the vendor folder in the same places were the precompiled libraries were positioned
5) re-include the two lines that were commented in point 2)
6) build everything again with brunch d2tmo
7) flash the .zip obtained
Any mistake?

Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?

Perseus71 said:
Unless I am having a brain fart that process seems about right. I wonder if your RIL changes are related to the network
What kind of issues do you see ?
Click to expand...
Click to collapse
It cannot even find the network operators. It says that it is impossible to connect and to try later...
mine is the Tmobile version of S3. May this influence?

That would depend on the changes you made. But otherwise not really. The underlying Device tree is unified for all US S3 devices.