[ROM][UNOFFICIAL] Lineage OS 13 For Obake [22/2/17]

[.: SID :.]

It's a pity, but I have bad luck with that rom. I'll describe almost all actions to understand what was done wrong.
1. I have unlocked bootloader, previously SU 6-7.3 was installed (KK 4.4.4)
2. I've boot in twrp (2.8.4.0), wiped data, dalvik, cache, system.
3. Installed rom and gapps-nano-arm-6.0, super-su-2.65.
4. Turned on, everything went fine.
5. After installation of some apps, activation developer options and root mode, I've disabled some apps I don't need with standard function.
6. After reboot there is constant bootloop.
So I've decided to reflash rom. Went to twrp, wiped data, dalvik, cache, system. Installed rom and gapps-nano-arm-6.0, but even after the first reboot I have constant bootloop.
Any advice what to do?

 

[monsterlucifer]

Wipe clean everything from TWRP. First flash cm12.1 nightly and reboot. After 12.1 initializes, go back to TWRP, do a factory reset and then flash this rom & GApps. That's it!

I posted all these steps after suffering from same issues that you've described on last page...

 

[notz76]

It's a pity, but I have bad luck with that rom. I'll describe almost all actions to understand what was done wrong.
1. I have unlocked bootloader, previously SU 6-7.3 was installed (KK 4.4.4)
2. I've boot in twrp (2.8.4.0), wiped data, dalvik, cache, system.
3. Installed rom and gapps-nano-arm-6.0, super-su-2.65.
4. Turned on, everything went fine.
5. After installation of some apps, activation developer options and root mode, I've disabled some apps I don't need with standard function.
6. After reboot there is constant bootloop.
So I've decided to reflash rom. Went to twrp, wiped data, dalvik, cache, system. Installed rom and gapps-nano-arm-6.0, but even after the first reboot I have constant bootloop.
Any advice what to do?

You don't need super su

Gesendet von meinem DROID Mini mit Tapatalk

 

[monsterlucifer]

When you clean wipe everything in TWRP (2.8.4.0), it installs SU - go ahead with it.

 

[.: SID :.]

Wipe clean everything from TWRP. First flash cm12.1 nightly and reboot. After 12.1 initializes, go back to TWRP, do a factory reset and then flash this rom & GApps. That's it!

I posted all these steps after suffering from same issues that you've described on last page...

Unfortunately this didn't help.
After some settings (developer options, root, status bar) and disabling of some apps, I have constant bootloop - blue CM face.
What radio do You have? I've flashed 23255.132.81.00R In CM12.1 I also have reboots if start applications which use gps.

I've decided to do some tests. So after activating developer options & root - normal boot, after disabling Browser, Mail, Calendar, Music - normal boot. I really afraid to check boot after changing settings of status bar (tiles).
If I edit them - unfortunately System UI has stopped. It's a disaster.

 

[SnipeR_TT]

Unfortunately this didn't help.
After some settings (developer options, root, status bar) and disabling of some apps, I have constant bootloop - blue CM face.
What radio do You have? I've flashed 23255.132.81.00R In CM12.1 I also have reboots if start applications which use gps.

I've decided to do some tests. So after activating developer options & root - normal boot, after disabling Browser, Mail, Calendar, Music - normal boot. I really afraid to check boot after changing settings of status bar (tiles).
If I edit them - unfortunately System UI has stopped. It's a disaster.

Did you still flash super su? I got bootloop when I did that. Try without super su.

 

[Johnny Wong]

Have not updated to the 29 Feb build but installed TycooKernel and the phone runs good.

Battery life might have improved

http://romwarehouse.com/megatron007/TycooKernel/

Sent from my DROID MAXX using Tapatalk

 

[kude87]

Have not updated to the 29 Feb build but installed TycooKernel and the phone runs good.



Sent from my DROID MAXX using Tapatalk

What did you notice most that the kernel improves upon from the stock CM kernel? I may try it, but right now it's running so well, I'm not sure where to even look for improvements.

 

[Johnny Wong]

What did you notice most that the kernel improves upon from the stock CM kernel? I may try it, but right now it's running so well, I'm not sure where to even look for improvements.

I would say it has marginally better battery life. I'll report back if there are any significant to report but like you said, can't go wrong with the stock. They made a big deal out of it in the Moto X forum so I gave it a shot.

Sent from my DROID MAXX using Tapatalk

 

[monsterlucifer]

Unfortunately this didn't help.
After some settings (developer options, root, status bar) and disabling of some apps, I have constant bootloop - blue CM face.
What radio do You have? I've flashed 23255.132.81.00R In CM12.1 I also have reboots if start applications which use gps.

I've decided to do some tests. So after activating developer options & root - normal boot, after disabling Browser, Mail, Calendar, Music - normal boot. I really afraid to check boot after changing settings of status bar (tiles).
If I edit them - unfortunately System UI has stopped. It's a disaster.

I have also disabled browser, mail, calendar but haven't disable music as I sometime use that app. I have also allowed root access to ES Explorer.

Haven't made any changes to radio but both GPS and mobile data is working perfectly fine for me. The GPS stays on high accuracy throughout the day and keeps a log of my location history. GPS is also working fine in Google Maps.

I went ahead and changed both status bar icons and edited notification drawer icons, it did said system UI has stopped once but after that it worked fine. I reboot after that and it boot up fine.

PS: I made a backup using TWRP so in case if I get stuck on bootloop like you, I could restore back

 

[.: SID :.]

PS: I made a backup using TWRP so in case if I get stuck on bootloop like you, I could restore back

Finally it works! I think in my case there was useful to wipe internal sdcard.
But now I have 2 issues:
1. Adfree doesn't block ads in apps.
2. If I plug on charge phone which is turned off there is no battery animation as in CM12.1, only Moto logo.
But in other things it works perfect! Thank you very much for new life of my phone! And special thanks for LED patch!!! :good::good::good:

 

[s_u_n]

This is awesome news (I know I am jumping in quite late).
Just as I was about to restore from my NANDdroid backup, I got to know of CM 13 for the phone.
Somehow nobody is talking about it on the Maxx thread - and all users are discussing here. Well, never mind.

If the speakerphone issue is not there for a majority of the users, then I will be installing this one pretty soon.
I have always got the option to go back to my Exodus ROM which has been running fine (except for the occasional reboot, when the flash light is kept on a little longer than usual or something freezes - very rarely though).

Thanks to the OP for bringing in new life and bringing the 2013 Droids up to the latest security patch levels.
You and CM team have done what Motorola refused to do.

 

[monsterlucifer]

Flashing over cm12.1 after factory reset has seemed to fixed the speakerphone issue for me. I'm now on this rom for a few days and speakerphone is working well!!

 

[kude87]

Finally it works! I think in my case there was useful to wipe internal sdcard.
But now I have 2 issues:
1. Adfree doesn't block ads in apps.
2. If I plug on charge phone which is turned off there is no battery animation as in CM12.1, only Moto logo.
But in other things it works perfect! Thank you very much for new life of my phone! And special thanks for LED patch!!! :good::good::good:

Use Adaway instead. That has always been my go-to ad blocker since ICS. Working great on MM.

 

[Nido221]

Thanks to the OP for bringing in new life and bringing the 2013 Droids up to the latest security patch levels.
You and CM team have done what Motorola refused to do.

These developers are great men to bring the Droids at this stage...

 

[tom.etc]

has anyone tried F2FS with these CM13s? a quick google didn't really have much to tell me. imma poke around xda here and see if i can't answer my own question.

edit: so it seems CM13 will support F2FS on some devices. attempted. 15m on bootscreen, reflashed n reboot, 30 minutes. nada mas.
edit2: clean FXZ (well, mostly. since i'm unlocked i spliced TWRP2.8.7.0-ghost into to the FXz and removed the md5 from the xml inside. didn't know if that was gonna work but it did. #sweatingstops) not sure if i will persue this further. would be nice just to get cm13 running. i have the same difficulty with this unit as someone in a previous post said. just seems to find ways to screw up during a rather standard install process. ugh

 

[Nido221]

It's a pity, but I have bad luck with that rom. I'll describe almost all actions to understand what was done wrong.
1. I have unlocked bootloader, previously SU 6-7.3 was installed (KK 4.4.4)
2. I've boot in twrp (2.8.4.0), wiped data, dalvik, cache, system.
3. Installed rom and gapps-nano-arm-6.0, super-su-2.65.
4. Turned on, everything went fine.
5. After installation of some apps, activation developer options and root mode, I've disabled some apps I don't need with standard function.
6. After reboot there is constant bootloop.
So I've decided to reflash rom. Went to twrp, wiped data, dalvik, cache, system. Installed rom and gapps-nano-arm-6.0, but even after the first reboot I have constant bootloop.
Any advice what to do?

How did you manage to unlock boot loader at Su 6-7.3 and Android KK 4.4.4 while Sunshine v3.2.6 support says,
.''We currently support most HTC phones, and Droid Turbo, Moto X (2014), Moto X (2013), MotoG (2013) and Droid Maxx/Mini/Ultra on Android 4.4.3 and lower''.
Any help?

 

[.: SID :.]

How did you manage to unlock boot loader at Su 6-7.3 and Android KK 4.4.4 while Sunshine v3.2.6 support says,
.''We currently support most HTC phones, and Droid Turbo, Moto X (2014), Moto X (2013), MotoG (2013) and Droid Maxx/Mini/Ultra on Android 4.4.3 and lower''.
Any help?

I've unlocked bootloader before flashing 4.4.4. And it was a long story to keep phone ready for unlocking with Sunshine.

Flashing over cm12.1 after factory reset has seemed to fixed the speakerphone issue for me. I'm now on this rom for a few days and speakerphone is working well!!

For me speakerphone works also!

 

[petech81]

Alright so I am having a problem, installed cm-13.0-20160301-UNOFFICIAL-obake-led , and open_gapps-arm-6.0-stock-20160305.

The problem is that when I go to add my google account I get "There was a problem communicating with Google servers. Try again later"

I've looked and tried to fix it, but nothing works.

Is anyone else having problems with this?

My phone is a Maxx Developer Edition with an unlocked bootloader.

 

[Nido221]

I've unlocked bootloader before flashing 4.4.4. And it was a long story to keep phone ready for unlocking with Sunshine!

Thanks, is there any way to try my luck for having an unlock boot loader at this stage (Su 6-7.3 & KK 4.4.4) ???