I started building a CM12.1 ROM by myself following the steps found in CM building site for the OPO.
The thing is that I get this error
Code:
No rule to make target «libmdmdetect»,
needed by «/root/android/system/out/target/product/bacon/obj/lib/libqmi.so»
I've read something about getting libmdmdetect from another device (from shamu, for example), but I don't know how and I don't know where to put it. I think the failure is not libqmi.so, since it needs the other one.
I'm a noob making my first steps on making ROMs by myself. Any help would be helpful.
Related
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
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?
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
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
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