Hi all,
I recently began editing the Galaxy S kernel, from the downloadable open source package.
After some time I compiled my changes into a zImage. My problem is, it won't flash when i put it in the most recent PHONE_I9000XWJG5.tar.
Odin3 just hangs at Flashing zImage...
My zImage is about 2.5MB in size, and the original JG5 zImage is 4.6MB, so I guess I am missing something.
I think I am missing the modules (which you can also compile). But I'm not sure.
Does anyone know how to compile a working kernel for the Samsung Galaxy S?
Thanks in advance!
First:
Read here: http://www.cianer.com/androidg1/28-building-android-kernel-images
Then here: http://www.receptorblog.com/wordpress/howto-compile-a-linux-kernel-for-samsung-galaxy/
and finally here: http://forum.samdroid.net/f9/dev-vmware-image-build-i5700-kernel-2-6-29-android-2-1-a-984/
not update.zip,why?
In recovery, no sd update.zip option, how can I tune out?
I'm also trying to make a new kernel based on JM5.
My goal is to fix the BlueTooth issues.. I think i've found the problem in a kernel's .c file...
I'm following this link:
HERE
I'm downloading the GT-i9000 opensource ZIP from Samsung, but i don't quite understand where can i get the Android Toolchain....
Is It really 6GB as it says HERE ?
I wish there was a XDA-like tutorial for this
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.
Hey XDA!
I've been trying to learn to compile AOSP so I can customize ROM's from scratch instead of having to steal someone else's compile and make modifications from there. I definitely don't want to take the work of others and back track to make changes.
I've got a Nexus 7 2013 LTE and I've setup a Linux build environment. I've installed the correct packages, followed all the instructions on the AOSP site, and downloaded the proprietary binaries (both the current 4.4.4 and preview binaries) to try and create a AOSP Lollipop 5.0.2_r1 build. I know there are ones out there that are working almost flawlessly, but I can't seem to get it to boot. My file sizes for system.img and all other packages are the same after compiling, I "make clobber" once executing the shell scripts to create the vendor folder in my source root, and I see the vendor files being processed during the build, but once the package (both ota and manually built attepts) are fastboot loaded, I get a boot loop, and I'm not sure why, it instantly hangs and reboots as soon as the "ANDROID" screen appears.
If anyone can give me any guidance, I want to start building ROMs for the community, but I just can't seem to get a bootable build to compile.
I may have missed some details, so if anyone can help me with figuring this one out, feel free to PM me, or leave a note on this topic.
Thanks!
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
daWeeZel said:
Hi folks,
i build my own unofficial lineageOS 14.1 roms for my oneplus 3 and this roms working fine.
I also extracted the device specific blobs directly from the latest OxygenOS rom image.
Unfortunately, the DASH charging functionality dont work. During the extraction of the blobs, the extract files script shows an error, that the "dashd" blob couldnt be found from the script. I decided to look into the proprietary-files.txt for any dash related things and there is this line:
-sbin/dashd:rootfs
I cannot find the dashd file in the official Oxygen rom and yeah...i messed up a little bit...
Has someone already implemented the DASH functionality in his own unofficial build? Can someone give me a hint, where to get the missing blob?
Thanks, WeeZel
Click to expand...
Click to collapse
I have found the files in this repository : github.com/OnePlusOSS/android_vendor_oneplus_oneplus3/blob/oneplus3/6.0.1/sbin/dashd
Sorry the forum doesn't allow me to post link ...
Hi,
I am trying to port LineageOS to an unsupported device, an IBall Slide Cuddle A4.
Here's the guide I'm following : https://fat-tire.github.io/porting-intro.html
This is the part where I need help:
"Add the blobs to the vendor/ directory
Once you have a working recovery, it's now time to get CyanogenMod building and working.
The first thing to do is to get all the proprietary, binary blobs into the vendor/ folder, along with a .mk file that will include them in the final build.
This requires three steps:
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Create an .mk Makefile to copy those files to the $OUT folder during the build process and put them in the right place. Again, use other devices as a guide for what this Makefile should look like. An example filename might be BoardConfigVendor.mk
Make sure that the Makefile you just created is included from your main BoardConfig.mk via a command such as -include vendor/[vendor]/[codename]/BoardConfigVendor.mk. Again, existing devices can illustrate how this is done.
Now revise the device/ directory
Since you have a working recovery, go back and start modifying the files in the device/ folder. As always, use other similar devices as a reference.
You now have a easy means to do backups and test your builds. So start tweaking the device folder itself, and see if you get it to boot... Once you do, from there its a matter of building and supporting the various parts and peripherals, one-by-one. "
Click to expand...
Click to collapse
Q #1: Where all should I look on my device for the proprietary blobs, and what do they look like? Can I manually extract them out of my existing ROM and paste them into the proper folder of the new one?
Q #2: What do I modify in the device/ folder?
Q #3: What does it mean to "build and support the various parts and peripherals" Does this mean to add the necessary drivers? If so, can I get these drivers from the stock ROM?
The reason I have to ask this here is because my device has NO similar LineageOS-supported devices with the same chipset for me to refer to. My tablet has a MediaTek MT8392 chipset, and I couldn't find any supported devices with an MT8392 (or an MT6592, which is very similar). Also, there is NO code available from the manufacturer, at all. The only resource I have is a stock ROM.
Are there any other ways in which a device can be similar enough for me to use as reference?
It would be really nice if someone could provide links to articles explaining the above 3 things, or if someone has already gone through this process, share their experience.
Also, will my kernel (v3.4.67) be compatible with the latest LineageOS 16 / Android 9 or will I have to build an earlier version?
I am very new to Android development, but that doesn't mean that I can't learn!
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
I understand that it is quite difficult. So instead of doing a full port myself, I am now trying the method of taking an image made for a similar MTK device and transferring the device-specific files from my stock ROM, as shown in the following guide:
https://www.techubng.com/2017/09/how-to-port-lineage-os-14-nougat-rom-on-mtk.html
It says:
"From System/lib/hw: Delete all mt6572.so blobs and replace with these blobs: DOWNLOAD BLOBS
Now copy these files from stock to port:
System/lib/hwcomposer.mt65xx.so
System/lib/gralloc
System/lib/lib.audio.primary.so
Systemlib/lib.mali.soS
System/Etc
System/lib/libcameracustom.so
System/etc/firmware
System/lib/libfeatureio.so
boot/kernel
boot/unventd.rc (only if you are getting stuck at logo)
boot/Replace only camera lines under #Camera from stock boot.img init.rc to init.mt6572.rclib/libcamdrv.solib/libcamalgo.so"
But my stock ROM does not have any of the files he listed uner /system/lib! Can I ignore these files, or is there some other place where these files could be? (I checked /vendor)
Also, what about all the other files in /system/lib? Which ones are device-specific and does anything else need to be copied into the new ROM?
As for the TWRP, I have found tools like Easy Magic TWRP Installer ( https://forum.hovatek.com/thread-5162.html ) which will automatically do the porting given the boot.img and recovery.img from the stock ROM. Are these safe to use, as long as I provide the right info to the tool?
I want to use LineageOS on this tablet because the stock OS has some annoying bugs and is quite old (Android 4.4.2) considering how recent the tablet is and how much capability the tablet's hardware has. The manufacturer (IBall) has provided no updates at all.
Lineage OS on Samsung Galaxy J3 Achieve (SM-J337P)
Can I pay a developer to make a working ROM to put Lineage OS on the Samsung Galaxy J3 Achieve (SM-J337P) ?
If so, how do I find a developer who can do it?
hey, i have a sm-t280 that have a similar supported device. how i port to it?
i have a sm-t280 that i wan't to update the android. the only exit i found it's build linegeos or aosp for it, can anyone help me?
here is the source tree:
vendor tree: huttps://github.com/gtexswifi/android_vendor_samsung_gtexswifi
-----
device tree: huttps://github.com/gtexswifi/android_device_samsung_gtexswifi
-----
kernel tree: huttps://github.com/pfent/sm-t280-kernel
[i writed huttps because i don't have posted 10 posts already]
Porting similar device mt6750t
vinaypundith said:
I understand that it is quite difficult. So instead of doing a full port myself, I am now trying the method of taking an image made for a similar MTK device and transferring the device-specific files from my stock ROM, as shown in the following guide:
https://www.techubng.com/2017/09/how-to-port-lineage-os-14-nougat-rom-on-mtk.html
It says:
"From System/lib/hw: Delete all mt6572.so blobs and replace with these blobs: DOWNLOAD BLOBS
Now copy these files from stock to port:
System/lib/hwcomposer.mt65xx.so
System/lib/gralloc
System/lib/lib.audio.primary.so
Systemlib/lib.mali.soS
System/Etc
System/lib/libcameracustom.so
System/etc/firmware
System/lib/libfeatureio.so
boot/kernel
boot/unventd.rc (only if you are getting stuck at logo)
boot/Replace only camera lines under #Camera from stock boot.img init.rc to init.mt6572.rclib/libcamdrv.solib/libcamalgo.so"
But my stock ROM does not have any of the files he listed uner /system/lib! Can I ignore these files, or is there some other place where these files could be? (I checked /vendor)
Also, what about all the other files in /system/lib? Which ones are device-specific and does anything else need to be copied into the new ROM?
As for the TWRP, I have found tools like Easy Magic TWRP Installer ( https://forum.hovatek.com/thread-5162.html ) which will automatically do the porting given the boot.img and recovery.img from the stock ROM. Are these safe to use, as long as I provide the right info to the tool?
I want to use LineageOS on this tablet because the stock OS has some annoying bugs and is quite old (Android 4.4.2) considering how recent the tablet is and how much capability the tablet's hardware has. The manufacturer (IBall) has provided no updates at all.
Click to expand...
Click to collapse
I saw Lineage OS 16 for HomTom S99….
I have HomTom HT70 with same Chipset of HomTom S99 MT6750T….
Im trying to read and follow carefully your guide but still i have bootloop..
Is it Possible to Port it to Homtom HT70 so we can have Android 9 too??
https://forum.xda-developers.com/ge...tom-ht70-6-0-hd-189-mt6750t-4gb-64gb-t3803052
hey, I have a samsung j7 j700t (t-mobile), and if it has a similar version that is the j700f / h / m, but I have tried it and it does not work for me. What do I have to do to make it work for me? Help me please!!!
AlexRsl1999 said:
hey, I have a samsung j7 j700t (t-mobile), and if it has a similar version that is the j700f / h / m, but I have tried it and it does not work for me. What do I have to do to make it work for me? Help me please!!!
Click to expand...
Click to collapse
Different processsor. J700t is Qualcomm. J700f is exynos
kurtn said:
Different processsor. J700t is Qualcomm. J700f is exynos
Click to expand...
Click to collapse
But my processor is Exynos 7580 to 1.5GHz
AlexRsl1999 said:
But my processor is Exynos 7580 to 1.5GHz
Click to expand...
Click to collapse
If you haven't already, I'd recommend checking in Geekbench as there's a lot of conflicting information on the web. Usually, Samsung only puts the Exynos chip in GSM only devices sold outside the US.
There is a custom rom for a variant of my device (Huawei g760) please how can i make it work on my device (Huawei g7-UL20) they both have the same specs and processor everything is the same
YomaAroriode said:
There is a custom rom for a variant of my device (Huawei g760) please how can i make it work on my device (Huawei g7-UL20) they both have the same specs and processor everything is the same
Click to expand...
Click to collapse
Have you unlocked the bootloader, before huawei stopped allowing it?
kurtn said:
Have you unlocked the bootloader, before huawei stopped allowing it?
Click to expand...
Click to collapse
Yes my bootloader is unlocked
kurtn said:
Have you unlocked the bootloader, befes ore huawei stopped allowing it?
Click to expand...
Click to collapse
Yes my bootloader is unlocked
I followed this guide: https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
And ported the twrp recovery made for huawei g760 to my g7-UL20
Now how do i modify the custom rom for it to work on my device. Please i need your help!!
kurtn said:
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
Click to expand...
Click to collapse
Hi there, I just noticed this reply you had made and I have a question about a device that may have had Lineage support.
What I would like to do, once I have my new phone that is, is to take my current phone Motorola Edge+ (2020) and turn it into a small Lineage tablet.
However, there is one slight problem with this, and that is rhat there is currently no Lineage support for this device, but there is support for it's younger brother the Motorola Edge (2020).
Now I do know that porting is possible between devices, but I've seen a lot of guides says they should have the certain similarities such as processor and such.
However the CPU, GPU and Chipset are slightly different (Same brands though), will this pose a problem in porting?
I of course do realize that I will of course need the proprietary blobs from Motorola for this device and I believe I have found them.
Finally, I am curious if you know of any up to date guides on porting? I will of course continue researching myself, however I thought I would make an enquiry anyway.
Any help you may be able to provide would be greatly appreciated.
Bloodstalker
Bloodstalker82 said:
Hi there, I just noticed this reply you had made and I have a question about a device that may have had Lineage support.
What I would like to do, once I have my new phone that is, is to take my current phone Motorola Edge+ (2020) and turn it into a small Lineage tablet.
However, there is one slight problem with this, and that is rhat there is currently no Lineage support for this device, but there is support for it's younger brother the Motorola Edge (2020).
Now I do know that porting is possible between devices, but I've seen a lot of guides says they should have the certain similarities such as processor and such.
However the CPU, GPU and Chipset are slightly different (Same brands though), will this pose a problem in porting?
I of course do realize that I will of course need the proprietary blobs from Motorola for this device and I believe I have found them.
Finally, I am curious if you know of any up to date guides on porting? I will of course continue researching myself, however I thought I would make an enquiry anyway.
Any help you may be able to provide would be greatly appreciated.
Bloodstalker
Click to expand...
Click to collapse
Install a gsi
GSI Rom´s For Motorola Edge +?
Hi for everyone! I have been looking for custom rom for our Motorola Edge +. But I haven't found any yet. However there is the option of the GSI rom's, this smartphone has an A / B system partition. 64-bit ARM CPU architecture. (information...
forum.xda-developers.com
Thank you very much for your reply. I had seen that I could uae a GSI, however I had not realized it is actually possible with Lineage. I clearly misread the topic.
kurtn said:
That's a hard task for getting started. A mtk device with no twrp available. I recommend to start with low hanging fruits. Like buying an old phone with dropped lineageOS support and building an updated version.
Click to expand...
Click to collapse
yo i have a phone with an unofficial version of lineageos 15.1 (Lenovo K8 Note) how would i go about building that newer version