Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
dblackburn965 said:
Okay, so I haven't really posted a whole lot,and I'm not sure I'm posting in the correct place, but I've been reading these forums for a long time. I've unlocked my bootloader, installed custom roms, kernels, etc. I'm currently trying to get AOSP kit kat to build for the tf300t. I've got my device tree set up and everything and I've synced the repos for the device and the kernel.
I'm using Cyanogenmods file structure which I've read is okay for AOSP. Whenever I go to compile the rom it can't get past build the boot.img. It says that it's missing the manifest for the kernel. Can anyone here give me an idea of where the kernel source should go in my android directory?
Thanks! Hopefully I can learn quickly and actually start contributing!
I think I may have figured it out. I've got 4.4 compiling for our tab now. Hopefully I don't run into any more problems. And hopefully it doesn't take too long!
Click to expand...
Click to collapse
Good luck, did WiFi work out for you?
Related
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
nerdman said:
Hello people,
This is my first post here, so I hope I am putting this in the right place. If not, sorry, please move it.
Anyway, as you all are aware, ICS source code was released a couple days ago, so I decided that I would see if I could begin constructing a ROM based off AOSP for the G2x.
As predicted, it did not go well. I pulled the build makefiles and the like from CyanogenMod (hope that's okay), and tried to use those as device-specific build instructions. I got everything to compile with no errors, and the ROM successfully installed, but does not boot.
Best I can tell, the phone gets through the kernel boot alright, but halts at the "A N D R O I D" screen (no boot animation file is included). The touch panel seems to be responsive.
Does anyone have any suggestions as to what might be wrong? Any help is greatly appreciated.
Click to expand...
Click to collapse
I think there were two other devs in this thread trying to get ICS up and running as well. They could probably help.
http://forum.xda-developers.com/showthread.php?t=1309620&page=3
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
nerdman said:
Thanks for the link. I am working on changing the init.rc as per one particular post. I'll see if that works.
Click to expand...
Click to collapse
We have 3 people working on it... your assistance would be of great help
Okay, so I tested the idea of changing the bootclasspath in init.rc, and it didn't seem to be helping much. In fact, it may have hindered things. Before the modifications, the phone would finish going through the two lg splash screens. Now, it hangs on the second. Suspect bad merge of ramdisk and kernel. But as for now, sleep is calling. I will work on it more tomorrow.
And I'm glad I can be of help. If you would like, I could throw what I have on megaupload, see if what I have is valuable.
You don't have ICS built device drivers and the kernel needs to be built for ICS. If you do not get it to boot nothing will work except maybe the touchscreen if you are lucky.
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
nerdman said:
Right. Device drivers. But we were able to port Gingerbread to this device with Froyo drivers, yes? What about compiling the ICS kernel source (if it is out) for the G2x. Would that yield any kind of results?
Click to expand...
Click to collapse
This is sounding a lot like the Hackintosh driver hacks, which I've done, to get the Mac OS to run on PC hardware of various kinds. In that world, drivers from previous iterations and versions of the Mac OS are merged into the Mac OS to enable various PC hardware which Apple didn't support in the new OS version. One example is the video drivers which Apple supplies for very few video cards but have been hacked to run other, non-supported video cards. As well, Apple is notorious because it orphans perfectly useable and upgradeable Apple Mac hardware by not providing video drivers for it in new releases of the Mac OS. When Mac OS 10.7 was released some people used the Mac OS 10.6 hacked and/or unhacked video drivers and hacked video drivers for OS 10.7 to keep their PC display hardware working. Keep trying.
Got the kernel source. I'll start messing around with it today.
Hey guys, I was trying to port a ROM called the Nexus Beam 5.0.0 from the Nexus S. Its an ICS CM9 based ROM. However, when I installed it, i got a bootloop, so I decided to copy the libandroid_runtime.so, libandroid_servers.so, libmedia_jni.so from the Ported ROM to the base ROM. Now it doesn't even get past the Team Kick Ass bootimage. (I used your kernel Erik XD) Do you have any ideas what could be wrong?
Why would you port it when we already have a ported one?
If you can access the recovery flash this:
http://forum.xda-developers.com/showthread.php?t=1794413
If not then flash back to stock:
http://forum.xda-developers.com/showthread.php?t=1358498
I also don't suggest following any porting guides because they are sometimes incorrect and sometimes mislead you. I learned that, now I'm waiting for XDA-University to go online. Also don't ask people on how to port stuff, they'll just reply with google this, learn by yourself, typically they're not going to give you a clue on how to start on the right foot. I bet XDA-University will fix that
You should check what the bootloop is about with adb logcat
ok. i am most likely asking this in the wrong back alley for this particular set of questions, if so please inform me to stfu, n ask <insert correct forum here> and ill then be on my way.
so, i have three of the same fairly dated, samsung galaxy s (4g) / us.cellular [not hooked up] not the point.. up until this post, many attempts to create a custom recovery for this has proven useless.. my question is this, if samsung has provided the "source code" for this particular model, shouldnt the i guess, particular informaton required for building of a custom recovery should be avalible, correct?
hell, i am most likely wrong but i am curious to know..
-deadseth
"i die alot"
Follow this thread from the post I linked to, I explained to another forum member how to compile a custom boot image, which will in turn allow you to edit the recovery before you compile. This will compile a KitKat kernel, which should technically work with other KitKat ROMs but will not work with anything older.
http://forum.xda-developers.com/showthread.php?p=57558013#post57558013
well
the phone is working off gingerbread.
deadseth said:
the phone is working off gingerbread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1828171
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V
Good luck.
this phone has no current custom recovery yet for it, that is what i am trying to work on here.
here is samsung's open source release of the phone's os
opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=r930
These are the forums for the SGH-T959V and SGH-T959W. The link to the open source release you posted is for the SCH-930.
If you really ARE looking for SGH-T959V information read on.
We have several versions of CWM available, as well as a few TWRP versions. They are all integrated into a bootimage. They aren't built for a separate recovery partition.
Anyway in this commit, bhundven imported the samsung open source kernel files.
https://github.com/bhundven/blastof...mmit/03b6581e79545d2e40e41d0f4bedf165bb39b183
Then several people added more commits to the kernel samsung. You can read the commit history yourself:
https://github.com/bhundven/blastoff_kernel_samsung_galaxys4g/commits/gingerbread
AT&T locks us out, is safestrap the way in?...
Total noob here. Will be researching how safestrap works. If anyone knows where I can find out how safestrap works please share. I am also going to try see if I can enlist help from devs who got it working on sgs5 and similar devices... has anyone tried safestrap for t337a?
Any help/info is appreciated
Already got a dev trying to port it for our 337a. [emoji106]
Hey guys. I have the t377a. Is there a root method for NK2? I have looked everywhere and have found nothing.
pre4speed said:
Already got a dev trying to port it for our 337a. [emoji106]
Click to expand...
Click to collapse
Happy New Year !
okay, i tried faking it with safestrap and so far it's booting me to my actual recovery....which is annoying.
scouring through hashcode's stuff on git and wondering if there's enough there to put together,
i got one boot to hang and was hopeful , adb logcat showed a dead stop at unable to find /sys/class/backlight blah blah
should be interesting ! yay.... :silly:
m
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
moonbutt74 said:
okay,
i've rounded up what source i could and after overcoming a VERY silly mistake on my part,
i am now trying to stitch a build together.
What i'm not certain of is if i can test it correctly on a device that isn't locked.
When/if/when i get it working and tested as far as i can take it, i will still need testers.
I am working from the hltexx device source since my initial mod attempts seemed to grab with that safestrap version.
The problem with that mod/test seemed to be that the recovery could find /data and /cache but, not /system.
My guess is that even though i can modify the *apk's configurations and repack it, the partition scheme and/or some of
the hardware specifics [display/backlight] are hard coded/built in to this particular build/binary.
Anyway, :silly:
m
Click to expand...
Click to collapse
You know how to get ahold of me and you also know I'll test anything. I'm ready! [emoji106]
Hi everyone!
Details: Oppo F9 Pro CPH1823
So, I have installed Lineage into one of my phones that is officially supported. There was not problem I faced doing that. Now, my new phone is not officially supported, so I decided to build from source for which I started doing research. I found guides and have many of the things figured out. There is a step that build Lineage for my device identity. After hours of research, I found the device vendor and the device tree (Dummy device tree). What remains is the device kernel which gave me a lot of pain. So, after not finding the kernel available on the internet, I gave up and said I guess I will have to make a custom one. But here is where the permission paradox comes in. I looked up guides to make custom kernel as I couldn't find one for CPH1823, but it turns out I need a 'source kernel' from the vendor website to even build a custom kernel. Every guide I see says I need to go to the developer website and download the source kernel code which my ****ty vendor has not made available. I mean there is a GitHub repo but my device seems to be lucky enough to not be on that list. What looks like a good option for me right now? Links should be enough as I willing to work and do more research. BTW, hope my first post is worthy!
-Mackenzie