Related
Information:
PLEASE USE THE SEARCH FUNCTION. Your question has already been answered. Use Google or the search function above. The Google link is a template for quicker searching of this site.
NC=Nook Color
stable=latest stable rom from Cyanogemmod. Your go-to ROM if you just want a good daily driver and do not want to worry about things not working.
nightly=the latest and greatest. Please only try if you are able to troubleshoot, understand basic computer concepts, are not a N00b.
N00b=A word I hate and you should never use. Please do not say I'm a noob that needs help. Simply ask can I please have some help.
rooting=This is NOT FLASHING A ROM. It is the act of taking a stock rom and installing super user privileges. Installing CM7 is NOT ROOTING.
CM=Short for Cyanogenmod. The amazing team of developers that make what you're reading and wanting to do possible. Thank them often and donate any way you can (in help, money, coding).
OP=original post (post #1 in a thread)
OC=overclocked
HC=Honeycomb
AOSP=Android Open Source Project
SD=SecureDigital storage (that little card that goes in your NC)
eMMC=internal memory (the "hard drive" of your NC)
ROM=the "operating system"
kernel="Translater" between your ROM and the NC hardware. You need the overclocked one to overclock. Flash after a rom is flashed. THERE WILL BE NO OC KERNEL FOR THE DEFAULT CM ROM, EVER. OVERVOLTAGES OF THE KERNEL WILL NOT BE INCLUDED.
FC=force close, or when an app crashes
SOD=sleep of death. When the NC will not wake from sleep. You need to hard shutdown, then reboot to fix this.
PBD=premature battery death. When the battery shows 3x-20x% battery life left, but shuts down without warning. This has been linked to people who updated their bootloader without first flashing to 1.2 stock and letting the battery drain all the way down. This is being looked into. You need to plug in your NC if you experience this.
Click to expand...
Click to collapse
Kernel Issues with CM7 stable:
Flashing OC kernel results in "ANDROID" hanging/bootloops on boot. You need to change the updater-script to ext4, or use this kernel. Here is information about the filesystems used.
Which OC kernel can I use with stable? The latest test (4/24) can be used. Both need the updater-script to be changed to ext4. Look here for information.
Please ensure you are running the latest Rom Manager and Clockwork Recovery. This will also fix problems with the kernel not loading and being stuck at "_ANDROID". Open market, download Rom Manager, install it, then flash the latest recovery for the NOOK COLOR (not NOOK COLOR (OLD), if that is still there). Now update your kernel/ROM.
I want to install an OC kernel to my SD rom! Head over here, Racks has all the kernels you could want.
Click to expand...
Click to collapse
CM7 Nightly Issues:
What overclocked kernel do I need?? The latest from dalingrin should do. Please read and understand (and use the search function) if you have questions/concerns. You're looking for the 5/23 .32 based kernel. Some may have issues with wifi, however.
I want to run this off of my SD card, not internal (eMMC) memory. Look at Racks for the answer.
Is it worth my time to upgrade to the latest nightly? You can check here. Changes specific to encore (the code name for the nook color) will have a slightly darker background, and if that is an issue you've had, it may be fixed now!
I want to run netflix on the NC! Download the netflix app and follow these instructions to have it run. If you don't know what it's asking to do, ask here!
I need the new uboot everyone is talking about! Get it here.
I want to try out USB Host support (VERY EXPERIMENTAL). Look here, read EVERYTHING, understand what you are doing!
Click to expand...
Click to collapse
Common Misconceptions/Questions:
Removing system apps (phone, mms, etc) will increase battery life! It has no effect. Stop it.
Using a task manager is a good idea in Android! That's not a good idea at all!
What do all these governors do/mean in setcpu/cyanogenmod performance settings? Look here for a great explanation. Also, DO NOT use setcpu PROFILES in CM7.
How do I install all these things? Check out eyeballer's awesome thread!
Click to expand...
Click to collapse
STOCK: NOOTER Distros:
For 1.0.1 ONLY. Look here.
For 1.1 ONLY. Look here.
For 1.2 ONLY. Look Here.
Click to expand...
Click to collapse
Honeycomb (Android 3.0):
Latest SDK (NOT AOSP) based ROM: Look here.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks for the OP's that saved me from retyping all the answers (Nemith, luciferii, and dalingrin, verygreen, and fattire (and others) that have made CM into the amazing piece of work it is.
Click to expand...
Click to collapse
Reserved for future awesomeness.
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Thanks for the feedback.
I'm going to keep it updated as long as I can. Since I'm on here pretty consistantly. When I can't afford the time to do so, I will pull the information.
I know no one reads these types of threads, but I just had 200+ views in under and hour, so hopefully this solved a few issues without added noise to the real threads.
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Geez...if I had a dollar everytime I messed up dalingrin's spelling... :S
Yeah, I figured there would be a few half-truths in there from me not totally understanding what is going on as well as you guys, but feel free to PM or post on here where I can change stuff. I'll try to simplify it as well.
I just read over the OP and holy SH*T that is confusing, no offense. Here are some tips for writing helpful FAQs/Guides:
Space it out. Everything all clumped together in one block of text helps no one. Space it out (ie like this list).
Add titles or headers in between sections (this goes along with the first point) to clearly guide people to where they need to read. People want to read what is pertinent to them; not read an entire block of text and then try to figure out which applies to their case. Help others help themselves.
For all this CM7-specific information, add version numbers in front of bullet points (for the same reason as the previous point).
Ironically, none of your "Common Questions" are actually Questions. Questions end with a "?". What you have are "Common Answers". Insert questions before them so people can quickly decide if reading that particular bullet point is pertinent to them.
[5/10] Since this is all changing at such a ridiculously fast pace, add dates in front of bullet points where necessary (like at the beginning of this bullet point), so people can clearly tell what is outdated and what is new. I really wish Dal etc did this for his threads since a TON of the info in his threads are ridiculously out of date.
Learn to use the [ list ] and [ * ] tags -- quote post #10 of this thread to see what I mean.
Just some friendly tips for writing helpful guides
Also the particular answers in the OP are very specific to the Alpha Test Builds of the last few days.
Those builds, like dalingrin's, are accompanied by FAQs right where the download link is.
The problem is that people talk about these things elsewhere, and even worse, put up mirror links without the FAQ - which just happened with the new Beta .32 build - one guy complained about not being able to download it because everyone else was hitting the same site at the same moment - so a mirror was posted later in the thread without dalingrin's FAQ.
Someone made a wise comment recently that people who cannot find the already posted detailed information, should not be installing these test builds in the first place, as they don't know what they are doing (and they never report enough detail in their bug feedback - such as exactly which build they have installed).
ADude said:
This is done with great intentions, but it is not going to work.
We know for a fact, that exactly those people who have questions, and post them in all the worst places, don't read any of the thread titles.
They don't read the information threads, they don't see "DON'T POST IN THIS DEVELOPMENT FORUM" warnings, and so on.
ALSO, this thread is just one more thing to rapidly become outdated - like the sticky thread that has months-old information.
All you have to do is go to a movie, go to sleep, or maybe even vacation, and immediately this has no longer correct information.
And it is one more thread pushing other development threads off the front page.
Fine idea, but it won't work in the real world.
Click to expand...
Click to collapse
Geez, Dude, you're harshing my mellow. At least Ace is trying to be helpful and doing something positive. Your negative attitude isn't helping anyone.
I for one, would like to say "thank you" to Ace. The OP couldn't have come at a better time as I was a little confused about the new 7.1.0 ROM and "2.6.32" thread was not helping at all. Keep up the good work!
Personally, I would love to see something like this:
7.0.2
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
7.0.3
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Nightly ##
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Other Builds etc
Date the below info was updated: 5/10
General Info:
Benefits of This Build:
Common Issues:
How to Flash / Download Location:
Supported Kernels / Download Locations:
Miscellaneous Questions Not Specific to a Particular Build
[5/10] How do I do X?
[5/10] Where do I get Gapps?
[5/10] Additional Questions
[5/10] Additional Questions
Unfortunately, I have a very limited understanding of all the stuff that is currently happening day-to-day. I run only stables (currently on 7.0.2 flashed weeks ago) for fear that I might mess up my NC because I may have missed a key detail in post #1238 in thread X, Y, or Z. A centralized thread with all this information run by someone dedicated to updating it daily would be a great help to everyone. People like Dal and other developers are busy developing, and rightfully so
Wow...
I dig it!
I'll see if I can start up something that in depth in a bit here...
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Actually, it occurred to me that a FAQ thread like this should be in "Nook General Forum", but that your OP, with all the information about nightlies and so on, should be posted to the end of the CM7 User General Discussion thread in this Forum.
That thread is where all these questions come up.
jzibit17 said:
When updating from 7.0.2 to 7.0.3 are you suppose to use rom manager? Or download the file from PC then transfer it over to SD and use recovery mode to update? Also your suppose to use titanium to back up apps and data only correct just incase. But as far as updating wipe cache and dalvik.... I just want to make sure I'm doing it correct that way all my apps stay. Fyi I'm running cm7 of internal
Click to expand...
Click to collapse
Personally, I find that ROM manager is another program that can have bugs, so I don't use it.
I just put the file on my SD card wirelessly using "Samba Filesharing App" (free in the market), and then use Clockworkmod Recovery to install it.
It looks like with many recent changes, it helps to first do "wipe system" and "wipe cache" before installing the new file.
Since our personal stuff is in "data", then I do not wipe that.
I also find that the "nandroid backup" on Clockworkmod Recovery is more reliable than Titanium Backup (same comment as for ROM manager). If you do a complete nandroid backup and then a complete recovery, it brings back everything - all the partitions - so it is a great thing to do when everything is working nicely.
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
psychoace said:
I can't seem to find the latest version of Gapps that you list. I checked throughout the site listed and only see for GB up to 03072011. Did it get deleted?
Click to expand...
Click to collapse
Looks like it was just deleted. I'll keep tabs on it.
fattire said:
I think what you're looking to do is make a FAQ or guide or something. Maybe a better place where people can all collaborate (and correct any errors you have made, and I see a few minor ones) would be set up a FAQ page on nookdevs.com or something..
Also, it may be a better idea to organize the bits of information by category so people can quickly find it. Use as few words as you can in the first sentence so that people scanning for their issue don't have to read the whole thing...
Finally, it's "dalingrin"
Click to expand...
Click to collapse
Agreed. Forums for information dissemination are just ****ty beyond belief. We, the NC/xda community, need to either start taking the NC wiki seriously, or fenagle the owners of this fine establishment into upgrading to something more collaborative. No offense, but the only thing worse than forums for a large community is an email mailing list. shudder ... lol
Seriously. Forums are areas for discussion. Not Q&A.
ace7196 said:
Looks like it was just deleted. I'll keep tabs on it.
Click to expand...
Click to collapse
You can google the file name to find it hosted elsewhere
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
hirano said:
I bought my Nook last week and since then i've been trying to learn how to tinker with custom roms and kernels but this subforum is total chaotic and newbie-unfriendly.
We (new users) need a wiki to get some basic knowledge about modding.9
All that stuff is scattered and buried in subtopics, I have took a lot of time just to install CWM on eMMC.
Now I'm running 1.2 rooted on emmc and CM7 nightly on SD, I couldn't get dual boot working on EMMC nor SD.
Click to expand...
Click to collapse
There is a Wiki stickied to the 1st page of the general section of the Nook Color Forum......http://forum.xda-developers.com/showthread.php?t=890549.
Ace created this thread in response to a rash of redundant questions.
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
anyone? I am quite serious about wanting to do and go into this but I have yet one thread that anyone's ever replied to.. (or post iirc) which puts a damper on me
Snake X said:
Lemme get some things out of the way.. I am a noob. I have searched. I have read some of the results from the search. I am overwhelmed by the 20+ pages of results (lol). I am not 100% sure this is the correct forum for this (not sure where else would be ).. I believe this is one of those things where I need help based on my situation.. Ok, so here I go.
I wish to start porting ICS to my phone. That's my goal. I have general understanding of how linux works, but I do not know much about the android specifics of how they work, or what needs to be modified for this to work. I do not plan to use the kitchen tool as I wish to learn this the hard way. I believe this will help me become more understanding in what I am doing. However, at this point I don't and that's why I'm here. My phone model is irrelevant almost because its prepaid and usually the communities don't even recognize their existence.. at least that's how I feel about it. But I digress. My phone is the zte warp by boost mobile and I am here to learn hopefully the things that will get me started on porting ICS to this phone. I right now believe that the best thing for me to learn is how the android related files work because as it is, I only looked at guides on how linux works and I understand most of it. I'm not sure that's the best thing that will help me port ics, but I'm certain it is important.
Please help me figure out where I should start in learning how to port ICS to my phone basically.
Thanks XDA
Click to expand...
Click to collapse
From my limited knowledge, I think it is a huge task undertaking, you can download Android source code from Google, the hard part will be the device driver development and porting for Linux kernel (and maybe portion of Android). If you are lucky, you can use the existing phone bootloader (or you have to port one). Understanding the inner of the phone (different chip set may need different device driver) will be another challenging task.
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Snake X said:
by the device driver development, you mean all the libs that go into the phone? Couldn't I just copy/paste the pre-existing libs that are already made for the phone? Also the phone im working with is a bit strange really.. noone has been able to compile the kernel from its source and get it to boot yet.. when it was compiled the zImage was different than that of the stock one.
And yeah, I have downloaded the aosp source.. I just need to know where to start at and the processes involved really
Click to expand...
Click to collapse
To answer you question no the drivers and lib files are different for aosp based rooms then they are for the stock OEM from. The first step will be to get a working kernel. Without anything you do will be pointless
I'm somewhat interested in the same thing, and from what I've gathered, you'll need to do these things to begin ROM development:
1. Read every page on the AOSP site and grab a copy of the AOSP source. It probably wouldn't hurt to read the regular Android developer wiki as well.
2. Learn about Linux driver development:
http://lwn.net/Kernel/LDD3/ (this is apparently considered THE BOOK on Linux driver development)
http://www.freesoftwaremagazine.com/articles/drivers_linux
3. Learn pretty much every detail about your phone and its hardware, especially when it comes to how ROMs are installed on it. For example, my phone (the Droid X2) has a locked bootloader, so 2nd init has to be used to boot new ROMs, and this makes it so that we cannot update the kernel.
You can usually find this sort of information on your phone manufacturer's website. Sometimes they even post the source code to their phone's drivers, which is helpful.
4. Look at other ROMs (preferably for your phone) and see how they work. The source code is freely available for most popular ROMs.
For example: CyanogenMod keeps their source code in a public git repository: https://github.com/cyanogenmod
5. Get to work on porting!
I would highly recommend starting with something smaller, however, just as a start. One good jumping-off point is probably this guide: http://forum.xda-developers.com/showthread.php?t=1272270
If any part of this was wrong, or if I left something out, somebody feel free to correct me, I'm still a noob.
Thank you so much for your direction, however,, android kitchen.. im not sure about that because isnt that only ment for htc devices? My phone is made by zte
what device do you even have?
if it's stuck officialy on 2.1 or 2.2 there's no hope that if you even port it that it'll work
its the zte warp from boost mobile (prepaid). Btw if I compile an aosp ics launcher and put that on my phone whats the chances of that working?
edit: it uses 2.3.5
Well Sebastian responded on android forums, apparently zte is very bad at version control with their kernel sources. So when they complete one project, they use the same source for the next project, and what they release could be for anything. Apparently the blade source had the same issues, it took him a while to get them to correct the source
Sent from my N860 using Tapatalk
Yeah I noticed that there were ppl saying there were things similar but I'm not sure what will work or what won't.. guess its time to start a petition on zte to release the source code lol
edit: seems like zte's bein a bad company and violated the GNU GPL license for not providing a complete source code.. I compiled an email and sent it to someone who can proof read it and send it to the right person for this kinda thing.. danggit zte
Hello everyone. I've updated my Xperia tablet Z4 lte to the 28.0.А,8,240. So does it means that I've lost the ability to make the root?((((( because the instruction of only one method for rooting says that it fits only for 28.0.A.7.24 or 28.0.A.7.27 builds.
?
get your version numbers straight
look up Androplus kernel here (read the whole thread)
give us some sources for
only one method for rooting
Click to expand...
Click to collapse
I know several methods, they all exchange the kernel on the boot partition and have a more or less tedious way to install SuperSU
Year, thank you for your answer. I see root is possible for our device, but I hesitate to do it as I don't know exactly which apps would stop working once and for all without drm keys and there are no good custom roms, even cyanogenmod. I wonder, this device was released ten months ago, and so little done.
It make me feel blue, as it kills the hope that something would change in the nearest feature((((((
If you need my help in testing new ways of root, some new roms, feel free to send a word to me, I would try to help as much as I can))))
How do you learn how to root a phone, I have no tech background
depends...
How do you learn how to root
Click to expand...
Click to collapse
for some people it is just "can haz video asap!?"
If you venture into uncharted territory you needs lots of technical background and some experience.
What works on one device may work with a little modification on another.
So you read a lot. xdadevelopers is a good starting point. There are books on the subject. Look for "reverse engineering" or "system security". Good Linux knowledge is very useful.
The tools you need are all free and come with more documentation than you want to read with your Linux distro.
Q&A thread for this thread
Well I guess I'll start by saying good job on making the news with this ROM!
http://www.androidheadlines.com/2016/02/lg-v10-t-mobile-lg-g4-get-cyanogenmod-nightlies.html
Ok I want to start with I'm not a programmer nor do I want to be but I was wondering about the second screen are you trying to get the functionality of the stock Rom second screen or just trying to push the status bar into that region of the screen?
It sounds like everyone is expecting you to be a code God and make a copy of the embedded framework app from the stock Rom and somehow make it work with CM.
Keep up the good work and thanks for the Rom.
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
b0taSs said:
Hi all,
With the risk of this being called a duplicate thread I just want to clarify that I'm in no way asking to port something for me, and I've read the 2 similar threads around, and felt like this should have it's own place.
So, straight to the point, I've been looking to get involved with android porting, and since LOS and AOKP for our device haven't quite filled my cup I was thinking of trying to port something else (trying to not get into much detail here )
Moving on, after searching around XDA and everywhere else, I've found a tuto or two where the process of porting was explained, and being an average user, I went to grab a "Base ROM", (thought the LOS/Stock ones would do, downloaded both)
To my surprise, files mentioned in the tutorials (framework-res.apk, framework.jar, ...) are nowhere to be found.
Finally the question, this just to save me from a reflash,
Am I supposed to install the "Base ROM" to dump /system to my PC?
Or am I perhaps misunderstanding something?
----
PSA: I'll probably find it difficult to get time to work on this (school stuffs) so even if I decide to go on with it, it might take a good while till something comes up.
Also, if there's someone with some experience in porting who'd be so kind to give me some pointers or show some availability to help with bug fixing/porting (not asking for labor, just explanations, in case I need 'em), please PM
Thanks, and sorry for the long post
Click to expand...
Click to collapse
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Ruben Craveiro said:
i wouldnt even try to port, its just confusing, files missing, preloader updates which makes you think which one to use, its all really just a mess, you will have better chance of getting something if you build from source, just fork our device, kernel and vendor trees and download a custom rom source of your choosing and build it, i wont say step by step, but i recommend that to download the vendor, device and kernel sources you make the local_manifest.xml so that when you do repo sync it downloads those sources aswell
Click to expand...
Click to collapse
And here I thought porting would be easier, but yeah, now that you mention that.. :silly:
Aw well, thanks mate :good: