Related
Hi everyone, i am just curious here since everyone said that phone with a locked bootloader is unable to flash a custom rom. But what does it means actually? aren't there are all the custom rom around for our motorola milestone?
From my understanding so far(please correct me if i am wrong, i am a very new to android), locked bootloader means that we can only used a sbf files that are signed officially by motorola only? how they actually made a latest version of gingerbread to milestone? there are tons of question mark in my head i hope someone will be kind enough to clarify to this newbie. Thanks alot.
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
234m said:
No one who can provide an answer?
I'm currently thinking about, flashing Cyanogen 7 on my Milestone. However I would like to understand, how it works to run a Rom on a signed boot loader.
Resp. what the drawbacks are (longer boot time?).
Thanks in advance to anyone who can shed a bit of light on this topic.
Click to expand...
Click to collapse
Basically what this is, is almost like a Froyo ROM that is running on the least amount of Froyo available (to bypass the signature verification of Motorola's locked bootloader). So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
If the bootloader was really unlocked, we would be able to change the kernel, which could improve optimizations for the phone, the CPU, etc. and it has true overclocking of the CPU.
Thanks skadude66, for your explanation
skadude66 said:
So even though the kernel shows that it's 2.3.7, it is based off of a Motorola kernel and exploited to port Gingerbread onto the Milestone.
Click to expand...
Click to collapse
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
234m said:
Thanks skadude66, for your explanation
So it is like turning a Dodge Neon into a Dodge Caliber just by changing it's chassis and leaving the engine?
Is the boot time of the exploited kernel longer than the vanilla version?
Click to expand...
Click to collapse
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
skadude66 said:
What do you mean by vanilla version? Comparing 2.3.7 to the stock Motorola 2.2.1 kernel in terms of boot times?
Click to expand...
Click to collapse
Yes, that's what I mean. I imagine this system somehow like an "Virtual Machine", where you have to boot the "host" (2.2.1) before you can boot the "guest" (2.3.7).
Is it like this?
I just bought my N6 yesterday from Verizon and I spent some time last night reading up on things but I would like some further confirmation from some experienced users. So I've read a few posts where some have bricked their devices by flashing cm12 while on 5.1. The Verizon N6 came with 5.1 already so is it advisable to not flash cm12? And while we're on that topic, is there anything else you should not do while on 5.1? I was looking through all the roms/kernels and some are not updated yet. So if I'm on 5.1, is it ok to flash a rom/kernel that is not 5.1? And the encryption stuff is confusing as well. I'm sure the device will be a little faster with encryption disabled but is it really that big of a difference? I apologize for being a total noob when it comes to Nexus devices. I've never owned one, I've always had HTC or Samsung. I haven't ran cm since I had my HTC Rezound lol so I'm anxious to run it again. So if someone could please tell me what roms I can and cannot flash and just give me some general advice about this phone I would greatly appreciate it.
highdro said:
I just bought my N6 yesterday from Verizon and I spent some time last night reading up on things but I would like some further confirmation from some experienced users. So I've read a few posts where some have bricked their devices by flashing cm12 while on 5.1. The Verizon N6 came with 5.1 already so is it advisable to not flash cm12? And while we're on that topic, is there anything else you should not do while on 5.1? I was looking through all the roms/kernels and some are not updated yet. So if I'm on 5.1, is it ok to flash a rom/kernel that is not 5.1? And the encryption stuff is confusing as well. I'm sure the device will be a little faster with encryption disabled but is it really that big of a difference? I apologize for being a total noob when it comes to Nexus devices. I've never owned one, I've always had HTC or Samsung. I haven't ran cm since I had my HTC Rezound lol so I'm anxious to run it again. So if someone could please tell me what roms I can and cannot flash and just give me some general advice about this phone I would greatly appreciate it.
Click to expand...
Click to collapse
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
shelooga said:
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
Click to expand...
Click to collapse
So that could be why people are messing their phones up? By flashing cm12 while on 5.1? I thought I read somewhere that cm hasn't updated to 5.1 yet. Thanks for the info. I didn't think I could flash anything other than 5.1 but this is not a familiar device to me so it could've been different.
shelooga said:
it is NOT ok to flash a rom for any other version than what youre on. so dont flash any 5.0.2 roms or kernels if youre on 5.1. (exception being the radio. i believe that can be swapped without incident, but youll have to do some extensive reading in the General and Development sections)
personally im on 5.0.2 for now until chroma gets realllll shiny and polished
i havent been encrypted since my first bootup, but my understanding any lag associated with that has basically been resolved
Click to expand...
Click to collapse
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
highdro said:
So that could be why people are messing their phones up? By flashing cm12 while on 5.1? I thought I read somewhere that cm hasn't updated to 5.1 yet. Thanks for the info. I didn't think I could flash anything other than 5.1 but this is not a familiar device to me so it could've been different.
Click to expand...
Click to collapse
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
akellar said:
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
Click to expand...
Click to collapse
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
highdro said:
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
Click to expand...
Click to collapse
That I'm aware of, yes
Sent from my Nexus 6 using XDA Free mobile app
highdro said:
So the only ROM that had the bootloader included was cm? So I can flash anything I want now? Thanks for clearing things up man.
Click to expand...
Click to collapse
Anything that is 5.1 yes, I would stick to ROMs based on the "E" build of 5.1, since that's what you're phone came on. Most ROMs are in process of updating to E.
akellar said:
Simply inaccurate. You can run 5.0.2 roms after updating to 5.1 without issue. Just don't touch the bootloader. You cannot downgrade the bootloader from 5.1.
The issue with CM was that they had a brute force bootloader flashing script built in. This has been removed.
Click to expand...
Click to collapse
my bad
I just picked up a Kindle Fire HD 7" 2nd gen I believe. It shows 12.2GB in storage model number x43z60, I want to put Android OS on it. Ive never done this before, and i see ALOT of info on here about it. Basically, im sure there is already a thread that will tell me everything i need with download resources.... just asking, can someone direct me to a link, with everything i will need to do this without a Boot cable, and include a stable version of the Android OS, something in the 4.x series.
I dont care if its the stock rom, or a custom rom, prefer a debloated custom rom made to run great, without any bugs or so.... Im confused by everything going on, its alot to take in when your not up to date on whats been going on. Thanks everyone!
robles4242 said:
I just picked up a Kindle Fire HD 7" 2nd gen I believe. It shows 12.2GB in storage model number x43z60, I want to put Android OS on it. Ive never done this before, and i see ALOT of info on here about it. Basically, im sure there is already a thread that will tell me everything i need with download resources.... just asking, can someone direct me to a link, with everything i will need to do this without a Boot cable, and include a stable version of the Android OS, something in the 4.x series.
I dont care if its the stock rom, or a custom rom, prefer a debloated custom rom made to run great, without any bugs or so.... Im confused by everything going on, its alot to take in when your not up to date on whats been going on. Thanks everyone!
Click to expand...
Click to collapse
If your Kindle doesn't have a camera, it won't work with the ROMs in this subforum.
That being said, for tutorials, check the stickied threads.
Yeah, you have the 2013 model sans camera (I think). Wrong forum.
robles4242 said:
I just picked up a Kindle Fire HD 7" 2nd gen I believe. It shows 12.2GB in storage model number x43z60, I want to put Android OS on it. Ive never done this before, and i see ALOT of info on here about it. Basically, im sure there is already a thread that will tell me everything i need with download resources.... just asking, can someone direct me to a link, with everything i will need to do this without a Boot cable, and include a stable version of the Android OS, something in the 4.x series.
I dont care if its the stock rom, or a custom rom, prefer a debloated custom rom made to run great, without any bugs or so.... Im confused by everything going on, its alot to take in when your not up to date on whats been going on. Thanks everyone!
Click to expand...
Click to collapse
You have the 2012 model of the Kindle Fire HD; you're in the right place. Read Seokhun and Hashcode's stickies above -- there's a lot of information here, but those are far and away the most important and have all the links you need to go from stock Amazon to Cyanogenmod 11 (Kit-Kat based), although you should refer to the post about installing TWRP 2.8.3.0 recovery below instead of installing 2.7.0.0. What you should know about development for the Kindle is that hybrid OSs (opening up Amazon's version of ICS) were followed byJelly Bean and then Kit-Kat based ROMs and there are now Lollipop-based ones too. CM11 is a good choice.
I'm pretty sure the x43z60 is 2013 model
Our Kindle is Model No. X43Z60
Rushead said:
I'm pretty sure the x43z60 is 2013 model
Click to expand...
Click to collapse
No -- my Kindle Fire HD 2012 model says "MODEL No. X43Z60" on the back.
solar satellite said:
No -- my Kindle Fire HD 2012 model says "MODEL No. X43Z60" on the back.
Click to expand...
Click to collapse
Do you have a camera?
Rushead said:
Do you have a camera?
Click to expand...
Click to collapse
Yes. I don't understand the confusion -- what does your Kindle Fire HD 2012 model say on the back?
solar satellite said:
Yes. I don't understand the confusion -- what does your Kindle Fire HD 2012 model say on the back?
Click to expand...
Click to collapse
No confusion, just confirmation. I haven't seen the back of my kindle since I bought it.
I am just curious, with us being able to use Flash Fire now, what is the future of potential custom roms for our S5's ? It always seems when a new device comes out the older ones are forgotten. Personally i love my S5 i have no intention of getting an S6 because of the non removable battery and non expandable storage. I used Flash Fire to put the pre rooted version of 5.0 on my phone. I would love to see some custom roms in the future.
darthmalus said:
I am just curious, with us being able to use Flash Fire now, what is the future of potential custom roms for our S5's ? It always seems when a new device comes out the older ones are forgotten. Personally i love my S5 i have no intention of getting an S6 because of the non removable battery and non expandable storage. I used Flash Fire to put the pre rooted version of 5.0 on my phone. I would love to see some custom roms in the future.
Click to expand...
Click to collapse
Check the Android Development thread, We now have a custom ROM for Lollipop. Very active thread, sounds like there will be more. Good for us who appreciate out S5s
What's the name of the ROM?
I have finally begun my ROM project for the G900A. I was waiting for Lollipop to start it. No ETA.
CAG-man said:
I have finally begun my ROM project for the G900A. I was waiting for Lollipop to start it. No ETA.
Click to expand...
Click to collapse
Any help you need just ask. :good:
I have released TMS5. Its not much yet but its a start. I have plenty more to do and it will see a lot of improvements as I get the time to build upon it.
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
channing173 said:
Does anyone know when cm13 will start rolling out for quark? I love this phone, and I think marsmallow would be amazing on it, especially with that huge battery.
Click to expand...
Click to collapse
The CM Quark dev @Skrilax_CZ just bought a 2nd phone so he can test CM13 while still keeping CM12.1 going on his main phone.
http://forum.xda-developers.com/mot...xx-xt1225-cm12-0-pre-release-t3060089/page100
Rule #1 of Fight Club: Never ask for ETAs.
Sent from my DROID Turbo using Tapatalk
Patiently waiting here too ...
Patiently waiting here too. Marshmallow changes look interesting.
and Thanks in advance,
You'll know as soon as you see a changelog here http://www.cmxlog.com/13/quark/
Sent from my XT1254 using Tapatalk
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
EnderKR said:
I'm waiting on it, too. I thought about flashing CM 12.1, but I don't really know what i gain by doing that over unlocked w/ Xposed and the stock Moto features. Marshmallow, though, would make it worth it. Unless there's something i'm missing.
Click to expand...
Click to collapse
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was released.
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have -- or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with that ROM let me use my phone the way I wanted, giving me choice back while still using that ROM. The problem with using xposed + custom ROMs is xposed modules are only guaranteed to work on AOSP ROMs that have not been heavily modified. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in the example I gave, "clear all recents".
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options... but I'm comfortable with CM12.1. (CM dev @Skrilax_CZ brought the first custom ROM and kernel for our Quarks, all others that followed are based his work -- especially the kernel.) I'm running CM12.1 on both my Quarks and have been for months. But the point is both Resurrection Remix and CM12.1 are way more advanced than Motorola stock 5.1, as they are both 5.1.1 + custom features.
NOTE: There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else, but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus, Resurrection Remix and even CM12.1 would have the security updates stock ROM does not.
I'm running CM12.1 plus Moto Camera because someone ported the Moto camera for CM users, and CM12.1 has all the other functionality I need (just different names).
ChazzMatt said:
I've done rooted stock + xposed.
I've done custom ROM + xposed.
I've done custom ROM by itself.
Here's my opinion based on experience...
I did rooted stock + xposed only when there was no custom ROM available. It's the least preferable choice, due to security risk. Rooted stock + xposed is just a simulation of a good custom ROM. It's better than nothing -- but good custom ROMs are updated frequently to close malware holes. Both CM121. and Resurrection Remix have blocked the Stagefright risk. Does Motorola's current stock ROM block that risk? Are there Xposed modules that block that risk? That's just ONE security threat, there are many others since stock 5.1 ROM was .
I've done custom ROM+ xposed, when there was one or two features an otherwise excellent ROM did not have or in one specific case where the ROM devs on purpose locked users into a specific choice where they previously gave user options. Installing xposed with the ROM let me use the phone the way I wanted, giving me choice back while still using that ROM. The problem with that is xposed modules are only guaranteed to work over ROMs that have not been heavily customized already. There may be a conflict somewhere. I would only use it for one or two features you could not live without -- like in my case, clear all recents.
I've done custom ROM only. CM12.1 has been the first ROM where I didn't need xposed to add any functionality to the ROM I was using. Resurrection Remix actually has even more options, but I'm comfortable with CM12.1. BOTH are way more advanced than stock 5.1, as they are both 5.1.1 + custom features.
There really aren't any stock Moto features that are not replicated by custom ROMs. It may be called something else but it's the same feature. Resurrection Remix even has the permissions integrated to let you to install MOST Moto apps if you absolutely need to have the same name. See this page: http://forum.xda-developers.com/droid-turbo/general/to-motorola-features-t3266646/page5
Plus Resurrection Remix would have the security updates stock ROM does not.
Click to expand...
Click to collapse
Fair enough, I appreciate the input. I'm still pretty new to the custom ROM scene, so there's lots to learn. Why not, I'll give Resurrection Remix a try. Sounds like people love it, and I really like the Moto features so I'd want to keep those. Thanks for the advice
I honestly just like the "all my devices are the same" so all my devices that can run cm.
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Hurts not having stock mm I'm guessing?
Sent from my XT1254 using Tapatalk
Skrilax_CZ said:
As for CM-13.0, there is still a lot to be done to get it to a daily driver state.
Click to expand...
Click to collapse
koftheworld said:
Hurts not having stock mm I'm guessing?
Click to expand...
Click to collapse
Not necessarily. That didn't stop @Skrilax_CZ from giving us Lollipop (March 2015) before Motorola released stock Lollipop for any of the Quarks. April 2015, Moto Turbo XT1225 was released with stock Lollipop 5.0.2 -- that was the first Quark with stock Lollipop from Motorola. @Skrilax_CZ beat them by using CM12.0 (Lollipop 5.0.2) with Kitkat 4.4.4 kernel, until Motorola publicly released Lollipop 5.0.2 kernel code. (Even though Motorola gave the Moto Turbo XT1225 5.0.2 in April 2015, they didn't release their Lollipop 5.0.2 kernel code publicly for devs to use until a few weeks later.)
Point is, we had Lollipop for Quark before Motorola gave Lollipop to Quark!
And we had CM12.1 (Lollipop 5.1.1) months (mid-April 2015) before Motorola finally gave just 5.1 to the Droid Turbo XT1254 in July 2015:
Skrilax_CZ said:
15th April 2015, 03:37 PM
Done. I have also moved to CM12.1 from now on, so I'll not be backporting latest set of patches back to CM-12.0
Click to expand...
Click to collapse
@Skrilax_CZ used CM12.1 (Lollipop 5.1.1) first with Motorola's 4.4.4 kernel code and then Motorola's 5.0.2 kernel code, until Motorola finally released Lollipop 5.1.x kernel code (September 2015).
Motorola never gave the other Quarks Lollipop 5.1 -- the Moto Turbo XT1225 and Moto Maxx XT1225 officially still have 5.02. and the U.S. Moto Maxx XT1250 (same identical device as the Droid Turbo XT1254, even the same FCC ID) is still "officially" stuck on Kitkat 4.4.4 -- unless you root and install custom Lollipop 5.1.1. ROM. But thanks to devs like @Skrilax_CZ we've had Lollipop 5.1.1 since April 2015!
So, NO, we do not have to wait for Motorola's slow roll-out of stock MM for our Quarks.
____________
mrkhigh said:
I honestly just like the "all my devices are the same" so all my devices that can, run cm.
Click to expand...
Click to collapse
Same here. When I help friends and family, I install CM so I know exactly where all the settings and options are. Two LG G2 phones, a Nexus 7 tablet all owned by other friends or in-laws. My wife's and my Quark XT1225. For some reason I never rooted my wife's Nexus 9 (yet) -- but when I do, it will have CM.
I also install Nova launcher and set all those options the same all all devices (including non-rooted Nexus 9). My wife said, "But my tablet looks like my phone." I replied, "Exactly." That was my intention.
If something isn't acting right, I can quickly diagnose it without having to remember it's set up differently or has an entirely different ROM.
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
IonAphis said:
Quick question, out of ignorance, not wanting to seem unappreciating... Doesn't the nexus 6 have very similar hardware to the turbo? And does MM change that much from the framework of lollipop? I have no idea about rom building, but shouldn't the process be more... Seamless? I've done some building on Linux itself and have some idea of how an OS works, shouldn't drivers be separate from the framework itself? I don't mean this for the turbo exactly, or trying to minimize the awesome works skrillax has done, but I mean this in the more general non-UI-modified-vanilla-ROMs sense.
Click to expand...
Click to collapse
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
http://forum.xda-developers.com/showpost.php?p=64573429&postcount=1050
cadenmiller60 said:
I believe the it's the kernel that takes a lot of work. Could be wrong thou
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
kitcostantino said:
not that it is the right way to do things or anything less than half baked kanging, but
i sucessfully got carbon rom (shamu) to boot on my xt1254. several things *appeared* broken, the worst of which was a 180° flip on the screen that kept buttons (touch response) in a spot it is visually not. i tried to simply add the inverse mounted line from the cm12.1 build.prop but that didnt change anything. i used the cm12.1 kernel.
if any of you that actually have a clue have pointers, insight, or know what i need to do tp port shamu roms to the quark, im all ears
Click to expand...
Click to collapse
Few things to note and remember that the DPI for the two devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
GreaterLesser said:
Few things to note and remember that the DPI for the too devices are different (may be the cause of the rotation bug or not) For Quark is 640 for Shamu I think is 560 (will have to verify) Also what changes did you make to the existing build prop (if any) to get the ROM to boot?
Click to expand...
Click to collapse
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
kitcostantino said:
the dpi looked right, but you are correct that technically, 560 is not correct for the quark. ultimately, i didnt have to change anything to get it to boot aside from swapping in the cm12.1 boot.img. it seems like someone could make a script or kit to easily port shamu roms to the turbo if the issues (bluetooth, screen, audio, radios lol) were ironed out. probably easier to build something else than to fix existing roms for another (similar, yet widely different) device. i have no answer for the screen issue aside from adding the inverted display line to build.prop, which changed nothing. principally, the fact that it didnt just blackscreen and soft brick is more promising than i had expected still, i do not know a tenth of what to do, so it isnt gonna work for me anytime soon. lol.
Click to expand...
Click to collapse
Well for WiFi, Radios, Bluetooth, etc doesn't the drivers need to be added to the build.prop for the system to actually use them? If possible you could use a build.prop for the turbo in Carbon and just tailor it a bit, theoretically of course. I know it's more complicated than I'm making it sound.
lol. yes, but i get what you mean. in older roms (cm10, cm11) to port, youd copy/paste all of the set perm recursives. in cm12.1 i dont know where to start pulling things from. mind you, i know its not as simple as it used to be because of the new dat format. guess i should read up a bit. lol