So I read that ROM's can be ported by just copying files around and changing some files. So I downloaded the Firmware from Sammobile
sammobile (dot) com/firmwares/3/?download=24705 . And in the downloaded ZIP, there are 2 files.
ibin (dot) co/1LGXjBrlIyTG
When I change the first file to .tar and unzipped it, I got this
ibin (dot )co/1LGY1IbOpvFu
^Both are images. I Dont have enough posts. Sorry
Nothing that looks like the folder structure of the tutorials found here on XDA.
Also, I can try to build CM myself. But I don't know what to do. I have the source from opensource.samsung (dot) com/reception/receptionSub.do?method=sub&sub=F&searchValue=S7275R
*Replace the (dot) with a '.' I don't have enough posts yet. ><
Bump
Someone help[
If you don't know how to compile a rom from source, then you probably should start with compiling roms for phones that have a fully working cyanogenmod.
If you get the drill, then you could go on with compiling rom for this phone.
But take my advise, if you don't have embedded or Linux experience, then it will be nearly impossible, as the hardware still needs porting.
need more developers to support LTE variant of this phone
by the way, why this phone isn't actively developed?
Related
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily
When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!
Hi guys, I was wondering how you would go about personalizing ROMs for your own use. Nothing code-wise, but installed programs and such. Opening up the zip files of downloaded ROMs I see the apk files and the system apk files - is it really as easy as just removing those you don't want and plotting in the ones that you do?
If this rom is from the same board as you, can say so.
But, .. you still need to run a linux terminal the code to sign the package that you previously made with same special files..
Just the search tools and you'll find it!
...You can easily too start porting rom's too...
I would love to help the community by using your kernel for the newer radios to port any roms for the older radio... is there any help you can give me? should i use your boot.img from the test-donut.img/test-eclair.img?
Click to expand...
Click to collapse
first, a thing we must know for porting job is what boot.img included.
here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
the ramdisk do some initializing jobs, so if we port a ROM, we should ensure that the content in ramdisk and files which are included in ramdisk (like init.rc), have necessary things the ROM needed.
for the first step, we can just extract the boot.img from the ROM, and extract the ramdisk from the boot.img which extracted just now, then repack it with my kernel (you can extract the kernel from my boot.img with same tools).
(to execute the perl script in link above, you need linux or just cygwin. )
but if we are sure that the ROM we want to port have nothing special with ramdisk, just like common ROMs, we can use my boot.img files directly. for eclair ROM, I suggest you extract the boot.img from my ROM, and don't use the first boot.img (test-NOCDB.img) I had posted.
after this, make our update.zip (use other's ROM as an example, especially the update-script in META-INF directory). sign our zip with testkey and apply it, then we can make our phone booting into desktop.
(you can find information about sign and download tools here: http://forum.xda-developers.com/showthread.php?t=471586, though the thread is not talk about how to sign things)
the main troubles we may meet probably are symlinks and setperm* in the update-script. if there is already a file/link has a name we want to symlink to, or if there isn't a file we want to symlink from or setperm, we will fail. so check the files carefully.
the next step is make everything work properly. we can use file from a ROM which made for new radio (and work well of course) to replace the one in the ROM we are porting. we can find these files in my 2.x ROM for eclair, or other's 1.6 ROM for donut (and for new radio, since the maker of them tested them already).
the most important files are (to my knowledge):
system/lib/libhtc_acoustic.so
system/lib/libhtc_ril.so (if something wrong with mobile network)
system/lib/libcamera.so
system/lib/libcameraservice.so
system/lib/liboemcamera.so (for 2.x) or system/lib/libqcamera.so (for 1.6)
system/lib/libgps.so
system/bin/akmd
(are there something I missed?)
(if we want to use NCommander's work on CameraHardwareInterface with a 2.x ROM, we should use my kernel for DONUT instead. I didn't try it, and I don't recommend it.)
these files are some thing work with hardware partially, so different radio may need different files. but if something just work fine, don't hurry to replace the file for it.
and now...., I don't have more thing to talk about, since we have most things work well. but for further tweaks, there are lots of things to do.
everyone can post your question here. if I know the answer I will post it. if I don't or I am not online, I think others will response you. and if there are things I missed or made some mistake, plz point it out
I will update this post when we collection more info or correct something. I find that I don't organized everything in order . I will update it later.
Thanks for the post... what's the difference between your eclair/donut kernel? (This is based on your original post about your kernel... is there an updated kernel somewhere i should know about?)
Edit
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Thank you very much for this sanpei. This is the type of posts that really should be on this forum
Appreciated so much. waiting for your next updates.
Phil_McRevis said:
Nevermind i figured it out by reading your post more. carefully thanks for the detailed instructions
Click to expand...
Click to collapse
sorry for my poor ability of expression
asero said:
This is the type of posts that really should be on this forum
Click to expand...
Click to collapse
I expect more people can share their knowledge, and we can make a wiki for all
Hello!
I have to edit some lines of init.rc of your kernel. I've thus extracted the ramdisk, edited the file, repacked and tried booting with fastboot boot kernel-img ramdisk-img, but the phone hangs on the operator logo. I've tried even just extracting kernel+ramdisk and boot them - same result (the boot.img works well).
how can I fix it? Thanks
Wrong post
I saw a few people post that they built ROMs for this device using dsixda's kitchen. Just wanted to know if you had to create a 'hammerhead' file for the storage mount points since this isn't included in the supported devices (obviously because the tool isn't being updated anymore).
If you created a mount point file, can you please post the contents so I can reuse (fyi... I've installed this on a Mac, but should be able to reverse engineer one from a different OS)? I'm a bit of a noob using this kitchen and just got it configured on my mac yesterday. Just looking to mess around with it a bit for lack of a better thing to do.
I´ve also created device files for several devices, it´s not as hard as it sounds, as long as you´ve read the OP in this thread ?
http://forum.xda-developers.com/showthread.php?t=633246
You need to unpack one Stock Kernel of the device you want to add the support to the kitchen, check the contents of the RAMdisk for the required mounting points and add them yourself ?
teknomar7 said:
I saw a few people post that they built ROMs for this device using dsixda's kitchen. Just wanted to know if you had to create a 'hammerhead' file for the storage mount points since this isn't included in the supported devices (obviously because the tool isn't being updated anymore).
If you created a mount point file, can you please post the contents so I can reuse (fyi... I've installed this on a Mac, but should be able to reverse engineer one from a different OS)? I'm a bit of a noob using this kitchen and just got it configured on my mac yesterday. Just looking to mess around with it a bit for lack of a better thing to do.
Click to expand...
Click to collapse
Gorgtech said:
I´ve also created device files for several devices, it´s not as hard as it sounds, as long as you´ve read the OP in this thread ?
http://forum.xda-developers.com/showthread.php?t=633246
You need to unpack one Stock Kernel of the device you want to add the support to the kitchen, check the contents of the RAMdisk for the required mounting points and add them yourself ?
Click to expand...
Click to collapse
That's how I got to this point to begin with was by going through that thread. I just don't want to get the syntax wrong and I'm not 100% sure what all those parms mean in that template file. Plus the info in the recovery.fstab file seemed to be quite different from the ones already in that folder. I was hoping someone would be able to just give me a copy so I can check my syntax. Sort of a learning experience for me.
i will try
okay, so im flashing my nook with Cyanogenmod v.11....
i found what i thought was it but doesnt appear to be.
i have a zip for NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14) but it doesnt have the files that it is suppost to come with because people say that same thing should have more files and different files. some say it's a zip, some say it's a rar. but my question is: how do i find it? all the sources are so old that they refer to the site that shut down.
where can i get the proper version of it?