Yes, you read that right. What we have here is a work in progress, yet semi-functional CM11 (Kit Kat 4.4.4) for those with the locked boot loader using Safe Strap. I have been working on this for about a month, and this is what has come of that work. However, I need some help. I am not Android savvy enough to fix all of these problems to make this a fully functioning phone.
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled accross one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not recieve that error and would move on to the next error. Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, it is okay to flash the modules for NB1/NC1, but it will (at this time) do no good.
When it starts up, skip through the initial install, as it is not ready at this time.
Optional: the screen will tear or be choppy looking when the graphics change, go to the settings->about phone->tap on build to enable developer mode. Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. This will drastically improve the graphical performance.
Download link:
http://ift.tt/1pAciQG
Screenshots:
Boot animation http://ift.tt/1pAciQI
Boot animation http://ift.tt/1pAciQK
Settings http://ift.tt/1pAcgZf
About phone1 http://ift.tt/1pAciQM
About phone2 http://ift.tt/1pAciQO
Dev. options http://ift.tt/1pAciQQ
Home screen2 http://ift.tt/1pAcgZj
Menu screen http://ift.tt/1pAciQS
Home screen1 http://ift.tt/1pAciQW
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
That being said, the phone does boot up and appears to mostly work. At this time, it is not a stable daily driver.
I did search all the threads, and I believe that this is not covered in another thread, so please forgive me if there is another CM11 thread that is for SS users on AT&T's locked boot loader phones. I don't see any.
How I got here:
Well, I wanted Cyanogenmod on my AT&T locked boot loader Safe Strapped phone. Every thread says we can't do that, and I just don't like hearing people tell me we can't do something and not provide any reasons. So I decided to try for myself. For the most part, they are right, but with enough perseverance, anything could happen.
I wanted to still use my phone as my daily driver, so I needed SafeStrap to work without
I was currently using Safe Strap with the NB1/NC1 kernels, and running Joe-Tech's GPE 4.4.4, so I decided that I should start with a 4.4.4 variant of CM, which lead me to CM11. I tried all of them, the nightlies, the home builds, the official builds, and I stumbled accross one particular CM11 nightly (20151115) that would boot and then crash as soon as it booted. So I decided to use that as a base.
Reviewing the situation/logs/errors after each crash, I slowly removed, edited, or replaced something until it would not recieve that error and would move on to the next error. Hence why the built in camera app is gone and replaced with open camera, etc.
If we get this working, we may be able to use these hacks or tricks to get higher versions such as CM12 or perhaps (fingers crossed) CM13. I know this is kind of lofty, but perhaps we could get something going here. Once we identify the key problems, perhaps we can also apply these tricks to other AOSP variants, such as Slim Roms.
However, let's stick to putting one foot in front of the other right now and focus on CM11.
The Setup:
AT&T boot loader locked phone with NB1/NC1 kernel and modules flashed.
Safe Strap 3.75, currently using Rom Slot 1 for this, as my daily driver is on the stock slot, however I have done it both ways, and it works either way.
Download the below CM11 zip and put it on your phone.
In Safe Strap, choose stock or rom slot, then wipe and flash the CM11 zip.
After flashing the zip, it is okay to flash the modules for NB1/NC1, but it will (at this time) do no good.
When it starts up, skip through the initial install, as it is not ready at this time.
Optional: the screen will tear or be choppy looking when the graphics change, go to the settings->about phone->tap on build to enable developer mode. Then, in developer menu, choose "Disable HW overlays" to always use GPU for screen compositing. This will drastically improve the graphical performance.
Download link:
http://ift.tt/1pAciQG
Screenshots:
Boot animation http://ift.tt/1pAciQI
Boot animation http://ift.tt/1pAciQK
Settings http://ift.tt/1pAcgZf
About phone1 http://ift.tt/1pAciQM
About phone2 http://ift.tt/1pAciQO
Dev. options http://ift.tt/1pAciQQ
Home screen2 http://ift.tt/1pAcgZj
Menu screen http://ift.tt/1pAciQS
Home screen1 http://ift.tt/1pAciQW
Check the following posts for issues and known working items. If you have an idea of how to solve the item, the best thing to do would be to download this CM11 and try it out. If you can't do that, or if you did and found a solution, just post your thoughts/trials/2 cents here in the forum and we can hopefully integrate it into the final product!
from xda-developers http://ift.tt/226PENS
via IFTTT
No comments:
Post a Comment