----------------------------------------------------
I don't know if it's appropriate to post this here.
If not, please remove it.
----------------------------------------------------
I just found that Amon_Ra recovery moved to 1.9.0 alpha, and after some search, I saw no thread about it here. I think this post would help those who always like to taste something fresh, just like me. Sorry for no changelog here, since I have nowhere to find it. Just a download link, and that's all. Enjoy.
Version: 1.9.0 alpha
http://files.androidspin.com/downlo...VERY/&file=recovery-RA-nexus-v1.9.0-alpha.img
NOTE: It's still in ALPHA. While no bug is reported till now, flash it at your own risk. I'm not responsible for any damage you may do to your device, or yourself.
@rambolee: Thanks for the info and link. I flashed it and it works fine, only difference I saw was it had PSFreedom and the color was blue with a Care Bear background.
I have reverted back to 1.7.0.1, more of a choice of preference, I dont like the Care Bear graphic and prefer the Nexus background.
Just sharing my experience with it.
Been posted, just doesn't have a dedicated thread (at least not in the title, since Amon_Ra hasn't updated it yet). RinTinTigger has a thread with this, as well as it being posted in Amon_Ra's own thread.
rambolee said:
----------------------------------------------------
I don't know if it's appropriate to post this here.
If not, please remove it.
----------------------------------------------------
I just found that Amon_Ra recovery moved to 1.9.0 alpha, and after some search, I saw no thread about it here. I think this post would help those who always like to taste something fresh, just like me. Sorry for no changelog here, since I have nowhere to find it. Just a download link, and that's all. Enjoy.
Version: 1.9.0 alpha
http://files.androidspin.com/downlo...VERY/&file=recovery-RA-nexus-v1.9.0-alpha.img
NOTE: It's still in ALPHA. While no bug is reported till now, flash it at your own risk. I'm not responsible for any damage you may do to your device, or yourself.
Click to expand...
Click to collapse
Thanks, for getting this out there.
Anyhow, got some flash instructions?
I already know how, but it would just make this a more solid thread to have the basic instructions for flashing the recovery explained.
Trust me people will keep posting this question otherwise.
Already in the Amon_RA thread just wait to be update by amon_ra
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.
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
FosCoJ said:
There is a script with claims to odex a deodexed rom via a flash able script here for those who are interested
http://forum.xda-developers.com/showthread.php?t=2095922
[Script] Amestris Odexer V3.0 [4.1.2] Optimize your phone!
Is it possible for ROM-Creators who are using Aroma (like NeatRom by sale,where I originally liked to post but have not enough posts yet) to include this script into Aroma installer?
Reason for the question is the constant demand of different modifications for guys like sale, so instead to have time further optimizing their roms, providing custom versions of one rom for special demands could be avoided with a possibility like this.
Do not want to start a discussion about pro&cons of odex/deodex and zipalign as theres plenty to read on that topic online.
So let devs concentrate on optimizing their roms and users decide which color they think they need?
Please forgive me if I got something wrong, overlooked a post somewhere or just used the wrong keywords to search on that special topic
Would be happy with a short, technical answer if it is possible or not and why.
Click to expand...
Click to collapse
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
slaphead20 said:
I don't think any dev would be willing to incorporate this due to the number of problems it would cause.
If you read the relevant thread you can see what a hit and miss affair doing this is.
Click to expand...
Click to collapse
Yeah, I tried the script myself on sale's rom and it just never worked. I could never boot back into the home screen. The odex me app at modaco worked a lot better than this script - for me anyway.
Sent from my GT-I9300 using Tapatalk 2
AW: [Q] Integrate Odex script into Aroma
Thanks to pardoned I was able to test the odex me app and it just Workshop fine!
Topic can be closed.
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Ain't nobody is going to help you ^^ I am looking for that kind of knowledge too. I would like to start building roms from source and make some modifications to CM10's kernel
check out Legion modz team thread
it has a little info on it
http://forum.xda-developers.com/showthread.php?t=2314836
and make google your best friend
so much way to take...
theabnormalguy said:
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
My github account is MaxusPrimus
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Click to expand...
Click to collapse
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
---------- Post added at 08:51 PM ---------- Previous post was at 08:09 PM ----------
flipinfin said:
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
Click to expand...
Click to collapse
Heres some starting links that im using starting to build from source. the samsung open source page look for your model number http://opensource.samsung.com. Obviously. you can build your own kernel.
how to unpack repack img http://forum.xda-developers.com/showthread.php?t=1081239
http://www.kandroid.org/online-pdk/guide/index.html very useful link aswell as this one http://source.android.com/source/initializing.html.
heres a link to identify partition tables http://forum.xda-developers.com/showthread.php?t=1959445. . Heres another link that you prolly can pull files from if needed http://www.teamandroid.com/2013/04/...kp-build-6-android-422-jelly-bean-custom-rom/
Dont take this the wrong way but i think your getting confused how roms kernels etc r built its all open source. That rom is based off of jelly bean and alls they did was change the name. Though its open source so i would assume you can repo the rom at https://github.com/. In addition if i was you i would download the rom "which you prolly already have and do some investigating.. heres another useful link http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code. Never forget google is your best friend. Fogot to mention if you aint on linux i would switch os real soon. I think this link will be ver ver very helpful https://bitbucket.org/bigwillyg/buttered_toast_shooter
Is that Vibrant T-Mobile ? cuz if it is http://aokp.co/devices/vibrantmtd theres your starting point
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
I am in no way a developer, I simply edit files and put them in the right place so it boots for us. I do this to help fellow d803 users.
If I helped with a file, always make a nandroid backup just in case things go haywire. Anything that happens to your phone is your responsibility.
Everything I submit gets tested rigorously on my own G2 before being posted to ensure its working, but we all get different results, so the experience might vary. Just a heads up.
Click to expand...
Click to collapse
Any suggestions or edits by mods to the post are welcome.
[email protected] said:
Mods, if this is in the wrong section, please move it.
*sorry for the bad english*
Alright, the purpose of this thread is simple. I made this with the intention of uniting all of the d803 users, and give them the opportunity to post a request for a rom they would like to see on their d803's that is available for other variants such as the d802. At the moment, I've found a way to "port" only d802 roms to the d803, and by port I mean making some slight changes that allow the rom to boot in our devices without any or with the least issues possible. These two devices are very similar hardware-wise, so software wise it doesnt change much.
If there's any D802 rom that you would like to see on our D803, feel free to leave a reply and I will do my best to move my gears and upload it so you guys can have it! As we all know, the development scene for the Canadian variant isnt as active as the d801 or D802, and with this I aim to end that barrier by trying to make those roms available to our device
Too long didnt read version:
If the rom exists for the D802, post a reply and I will try to make it available for the D803
Disclaimer:
Any suggestions or edits by mods to the post are welcome.
Click to expand...
Click to collapse
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Well I meant it more in a way for those who don't understand much about editing the updater script and exchanging the boot.IMG. with what I'm offering all they have to do is ask the ROM and I'll post it online with said changes in case they don't know how to do it. Something like a small favor for everyone, but thanks for the reply!
Request
If you could please port this rom I would very much appreciate it
http://forum.xda-developers.com/showthread.php?t=2609355
---------- Post added at 08:48 AM ---------- Previous post was at 08:38 AM ----------
blazewit said:
To port any ROM to any version just download your devices patch from dr87's Mahdi ROM thread then all u gotta do is change out the boot IMG, a few lines in the build prop n updater script then flash ROM, gapps, the patch then your good. We had a similar patch for toro on the gnex forum and I was waiting for the day someone put one together for us seeing as all g2's use the same mainboard. The days of worrying about whether your variant will get support is finally over, for aosp Roms at least. I'm gonna try doing it w a stock ROM to see if that works cuz that's something I'd really love to see. Cuz as a vs980 owner I can say from experience that our stock ROM development is lacking compared to the d802 or f320
Click to expand...
Click to collapse
Could you possibly make a quick tutorial on how to do this? or possibly direct me to where i could find one?
Hi, I was looking at your old thread about how you could port d802 roms to d803. I was wondering if you could port cyanogenmod 11 snapshot m12. http://download.cyanogenmod.org/?device=d802 i would really appreciate it. and it seems like u are good at what u do so you should maybe consider building for d803 for cyanogenmod. thousands of d803 users have been waiting for cyanogenmod support but to this day have recieved none. anyways if u could port it i would really appreciate it! thanks!
can you make lollippop rom pls
http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
CM12 !
PLZ !