[INFORM] [XT1575] Don't upgrade to Nougat stock!

[INFORM] [XT1575] Don't upgrade to Nougat stock! - X Style (Pure) General

Just a warning to fellow members on this forum that if you take the Nougat stock OTA you will NOT BE ABLE TO USE CUSTOM ROMS. Most roms you will find on this forum are developed for the MM bootloader, and there is no going back once you make this switch.
You will likely face INSTABILITY with your modem/wifi/sim activation, which all signs seem to point to the MM versions being more reliable. Additionally, you face the possibility of BRICKING your phone when using return-to-stock methods.
(Trust me, I've done it to 2 of my devices so far...)
I know this has been mentioned before, but I did not readily find this info in any of the stickies when I looked for it and wound up making my last mistake, so it's worth reiterating.

skuppej said:
Just a warning to fellow members on this forum that if you take the Nougat stock OTA you will NOT BE ABLE TO USE CUSTOM ROMS. Most roms you will find on this forum are developed for the MM bootloader, and there is no going back once you make this switch.
You will likely face INSTABILITY with your modem/wifi/sim activation, which all signs seem to point to the MM versions being more reliable. Additionally, you face the possibility of BRICKING your phone when using return-to-stock methods.
(Trust me, I've done it to 2 of my devices so far...)
I know this has been mentioned before, but I did not readily find this info in any of the stickies when I looked for it and wound up making my last mistake, so it's worth reiterating.
Click to expand...
Click to collapse
I went from Lineage OS to stock 6.0 to stock 7.0 to stock 6.0 to Lineage OS on the XT1575. You can absolutely go back and forth to custom roms. The bootloader and gpt files will fail to flash when downgrading, but that can be safely ignored.
You do have to flash back to stock 6.0 before installing a custom rom though. You cannot do it from stock 7.0 due to modem firmware mismatch. All custom roms use the MM 6.0 modem firmware because the current 7.0 firmware is not obtainable.

Thanks for the warning but It's 2017. None of the phones get Hardbricked completely
I was on Stock 7.0 for about 4 months now. And finally decided to flash the LOS Unofficial Build by Hashbang173, that build is based on Nougat Kernel and Modem.
It booted up perfectly and I used it for half a day. But it have some camera and mic issue so I had to go back to Nougat.
I was able to downgrade to Stock 6.0 and then get OTA back to Nougat successfully.
Here's my post on LOS Thread.
Also the Hardbricked issue has been solved.
In case of XT1575, ask any of the fellow forum member to create a silmilar dump for XT1575 devices.

antariksh said:
Thanks for the warning but It's 2017. None of the phones get Hardbricked completely
I was on Stock 7.0 for about 4 months now. And finally decided to flash the LOS Unofficial Build by Hashbang173, that build is based on Nougat Kernel and Modem.
It booted up perfectly and I used it for half a day. But it have some camera and mic issue so I had to go back to Nougat.
I was able to downgrade to Stock 6.0 and then get OTA back to Nougat successfully.
Here's my post on LOS Thread.
Also the Hardbricked issue has been solved.
In case of XT1575, ask any of the fellow forum member to create a silmilar dump for XT1575 devices.
Click to expand...
Click to collapse
I'm using xt1575 us variant. Is there any way you could send a link to the correct 6.0 i should flash? I'm stuck with bad cell service and the same problems you mentioned.

I can tell you that if you mess up the procedure in some fashion you can lose your SIM activation permanently. I updated to 7.0 before putting my SIM in and wasn't able to activate on 7.0. And after fastbooting/restoring back to 6.0 I still did not get it.
In another instance I upgraded the OTA after moving from 7.0 > 6.0 > back to 7.0. Bad decision because this hardbricked my phone. I was able to format an external SD card with a temporary bootloader to get it going again but I was still having problems with my modem (from what I've gathered, you can't revert back to 6.0 modem).
Best steer clear of 7.0 OTA entirely. There's a reason why almost all development is still happening with 6.0 base.

skuppej said:
I can tell you that if you mess up the procedure in some fashion you can lose your SIM activation permanently. I updated to 7.0 before putting my SIM in and wasn't able to activate on 7.0. And after fastbooting/restoring back to 6.0 I still did not get it.
In another instance I upgraded the OTA after moving from 7.0 > 6.0 > back to 7.0. Bad decision because this hardbricked my phone. I was able to format an external SD card with a temporary bootloader to get it going again but I was still having problems with my modem (from what I've gathered, you can't revert back to 6.0 modem).
Best steer clear of 7.0 OTA entirely. There's a reason why almost all development is still happening with 6.0 base.
Click to expand...
Click to collapse
Because they haven't finished implementing the changes in the code for the kernel source. As stated in many of the development threads over a month ago. So actually it will be made with the 7.0 source code but as of now it hasn't. As there aren't many truly active developers for the pure anymore.

Still seeing loads of irrecoverable problems for people updating to Nougat. Don't do it guys.
You can permanently lose your SIM access if you don't upgrade just right, and everyone has a different set of procedures.
And it you go to Nougat you can't go back.

I just can't get my sims to work on any custom rom after recovering from that hard brick. By any i mean both 6.0 & 7.0 compatible modems

Same..I ended up in the same boat where neither MM or Nougat based roms worked with my SIM after I recovered from hard brick using the external SD card bootloader trick
I needed to RMA...hence this warning
Sorry dude

If you ever used Magisk though make sure to uninstall from the app, then flash the uninstaller zip, then wipe, restore, and before booting flash the uninstaller zip again and then boot in
Old Magisk partitions cause the No SIM issue. I think this might have bearing on how upgrading to Nougat stock can break things. Like if you have a Magisk partition and then RSD back to stock without uninstalling first, and then take the OTA. That's my hunch...but not willing to test this this theory out..

Clarification...
skuppej said:
Still seeing loads of irrecoverable problems for people updating to Nougat.
Click to expand...
Click to collapse
I'm not. This is the first report I've seen of that, in fact.
skuppej said:
You can permanently lose your SIM access if you don't upgrade just right, and everyone has a different set of procedures.
Click to expand...
Click to collapse
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
skuppej said:
And it you go to Nougat you can't go back.
Click to expand...
Click to collapse
This is true.
skuppej said:
If you ever used Magisk though make sure to uninstall from the app, then flash the uninstaller zip, then wipe, restore, and before booting flash the uninstaller zip again and then boot in
Click to expand...
Click to collapse
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).

To the hatas
I figured I'd get some negative feedback for this warning.. I've had to RMA 3 separate XT1575's for this issue. I've definitely followed the guides listed on this forum on how to update to Nougat exactly, and I've gone through both the flashing each pre-packaged update route, as well as the OTA route.
I know you might like to dismiss this as user error, but the fact that we do not have a way to flash back to MM can leave you in a state where there is a BL/modem mismatch, and no way to flash a compatible modem. You can only really run into this situation from what I've experienced by going to Nougat at some point. It seems to be related to a bad flash, a restore of a MM rom over a N rom, leaving Magisk partition during restore, or something else. You'd think that RSD'ing back to stock should always return things to back to normal, but once the BL changes this simply is not the case.
If you check the Q/A board for "no SIM" and see the thread on Lineage OS 14.1, in particular, you will see enough mixed reports about SIM/WIFI access issues, and all of them recently moved to Nougat. I am not making this up.
(And, yes, having Magisk installed with a new rom flash/restoration *can* lead to No SIM Card Detected. In fact, I experienced this yesterday again while recovering from a bootloop for a separate ROM issue. The only way to fix this flavor of No SIM Card Detected was to flash the uninstaller, restore my backup, flash it again before booting, boot up, verify SIM was working, then flash the Magisk installer only after all those steps have been completed)

Bill720 said:
I'm not. This is the first report I've seen of that, in fact.
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
This is true.
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).
Click to expand...
Click to collapse
As for supersu, on nougat, magisk is bad? And I should switch to supersu?

Hitti2 said:
As for supersu, on nougat, magisk is bad? And I should switch to supersu?
Click to expand...
Click to collapse
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?

Bill720 said:
I'm not. This is the first report I've seen of that, in fact.
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
This is true.
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).
Click to expand...
Click to collapse
jason2678 said:
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?
Click to expand...
Click to collapse
Ok ty. I wouldn't know if bat drain would be normal for my daily use vs supersu usage.
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Definitely not a myth
Hitti2 said:
As for supersu, on nougat, magisk is bad? And I should switch to supersu?
Click to expand...
Click to collapse
Yes... on the stock Rom at least. It'll be made obvious by using various tools, so you can find out whether or not any other Rom is affected. See my long-running (and fully resolved) thread on the issue here.
jason2678 said:
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?
Click to expand...
Click to collapse
While it is a seldom-reported issue, I found it to be fully repeatable following hard resets. Again, this was just on the stock Rom where magisk daemon would hold the throttle slightly open. 5-15% CPU use might not sound like much, but it absolutely kills the screen-on-time by defeating the dynamic clocking and battery optimizations.
TL;DR? If Magisk daemon isn't killing your battery life, use it. Otherwise, Supersu is the way to go.

Bill720 said:
Yes... on the stock Rom at least. It'll be made obvious by using various tools, so you can find out whether or not any other Rom is affected. See my long-running (and fully resolved) thread on the issue here.
While it is a seldom-reported issue, I found it to be fully repeatable following hard resets. Again, this was just on the stock Rom where magisk daemon would hold the throttle slightly open. 5-15% CPU use might not sound like much, but it absolutely kills the screen-on-time by defeating the dynamic clocking and battery optimizations.
TL;DR? If Magisk daemon isn't killing your battery life, use it. Otherwise, Supersu is the way to go.
Click to expand...
Click to collapse
? how do i jump from magisk to supersu? Properly uninstall mag. And what version supersu should i use on stock nougat?

This is the version, but know what you are doing...
Hitti2 said:
? how do i jump from magisk to supersu? Properly uninstall mag. And what version supersu should i use on stock nougat?
Click to expand...
Click to collapse
I do believe that Magisk has a built-in uninstaller tool. I personally used SuperSu 2.82. Remember, this is only necessary if Magisk Daemon is constantly utilizing CPU resources. Checking that (using Simple System Monitor or a similar tool) aught to be your first step.

Bill720 said:
I do believe that Magisk has a built-in uninstaller tool. I personally used SuperSu 2.82. Remember, this is only necessary if Magisk Daemon is constantly utilizing CPU resources. Checking that (using Simple System Monitor or a similar tool) aught to be your first step.
Click to expand...
Click to collapse
I'm guessing under active processes I should monitor?

Guess im good.

Related

[stock firmware][D80020c] recovery friendly D80020c

This is for D800 (AT&T LG G2) users ONLY.
This package will update a phone with D80010d firmware to a "mixed" firmware that boots normally to D80020c (kitkat), but retains the older boot loader and compatibility with loki patched custom recoveries. The "normal" boot is 100% unmodified stock.
This "mixed" firmware is currently the only known way for a stock D80020c (kitkat) system that also allows custom recovery.
What's installed:
rpm, tz, modem, and system partitions from the stock D80020c (kitkat) LG G2 firmware.
LG's D80020c kernel, recompiled by @Savoca, and made compatible with the D80010d bootloader.
That will leave your existing D80010d boot loader (aboot) intact, as well as whatever custom recovery already installed.
This firmware package will (or at least should) refuse to install on ANY firmware other than the D80010d firmware. Please don't reply to this thread if you are using anything else. (That was as polite as I'll be on that issue...)
I STRONGLY suggest doing a full wipe on your device after flashing this. You don't have to, but it'd be a really good idea...
This is NOT my software. This is 100% LG's software and firmware. Don't ask for support in this thread. It won't be provided.
Instructions:
Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
Root the device and install recovery (recovery is required, root is not.) This is a link for rooting instructions. While you are welcome to use CWM for your recovery, this is a link for installing TWRP recovery. (Since cyanogenMod took freely given contributions to their codebasse and went private/for-profit, I have a personal bias against them - so my personal recommendation is for TWRP.)
Copy the d80010d_to_20c.zip package linked below to your phone.
Reboot into recovery and install the d800_to_20c.zip package.
Optionally, also install a superSU or other root package.
Optionally, but suggested, Perform a "factory reset" on your device.
Download Links:
The main package (about 1.7GB): Dev-Host (md5: 7cfe7de4ab31f727b72178b8fb618fd3)
SuperSU: Direct from Chainfire's webpage
Credits:
Several people spent countless hours working on finding a way to get recovery working with LG's kitkat. The kernel used in this package was made by @Savoca - who used the solution found by @JackpotClavin. Others involved are (as far as I'm aware) @AndroidUser00110001 and @jakew02. Of course, @Chainfire for the 'su' package.
Source:
All the images in the recovery package are completely stock with the exception of the kernel and kernel modules. The kernel is modified and recompiled with only the following patch: https://github.com/JackpotClavin/an...mmit/7b6187a0e5fb8ca59888cacf5f5b863baa8d1064. (The installer overwrites the kernel images in /system with those from the kernel compile.) The base kernel source is found on LG's opensource website under the D800 heading.
May 2014 Update:
I'm no longer able to tinker with my G2. My wife took it from me (for her own use), and she gets angry when I mess up all her settings.
(I ended up getting a HTC One M8 to tinker with.)
While I'll leave the thread unlocked so users can assist each other, please don't expect prompt responses from me or maintenance.

switched main package link to dev-host
added "source" section.

As soon as it's done downloading I will let you know that it works unless someone beats me to it that is
EDIT: Finally finished downloading I already flshed back to 10d rooted installed recovery and am now installing kk.zip
Re-Edit: just finished installing also just so you know flashing system only took about 2mins a little bit over that in terms of seconds anyways everything seems to be running fine ill report back tomorrow when its not 1am my time and can test things more thoroughly but I can confirm that everything flashes like its supposed to and also I like the little check you added where it says d80010d bootloader good!
Sent from my LG-D800 using xda app-developers app

XxZombiePikachu said:
... and also I like the little check you added where it says d80010d bootloader good!
Click to expand...
Click to collapse
It's actually checking that loki_patch reports a d80010d bootloader. If not, it'll abort flashing.

Thanks man, now i have kitkat with root and recovery (D80020c)

Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2

DowntownJeffBrown said:
Damn I wish I had waited for this before flashing kit Kat last week. Of will I'll just have to wait on a recovery compatible with kit Kat or go back to 4.2.2 and then flash this when I have time.
>^·^< Sent From MEOW G2
Click to expand...
Click to collapse
This is the only way for now to have a recovery on kit Kat
Sent from my LG-D800 using XDA Premium 4 mobile app

Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?

FlyingColors said:
Okay, so let me get this straight before I do anything. I'm currently running a custom rom right now, do I still need to revert to stock and install a custom recovery again, or can I just copy the stock kitkat zip to my phone and install from my current recovery?
Click to expand...
Click to collapse
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.

Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?

garyd9 said:
What is step #1 on the instructions?
You can do whatever you want with your phone. It won't impact me whatsoever. However, that has nothing to do with what I posted.
Click to expand...
Click to collapse
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.

FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Would you rather be unaware of what your doing and then break your phone or be cautious and ask a question to the man in charge even if it makes you look like an idiot. I thought so...sorry for wasting your time.
Click to expand...
Click to collapse
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app

XxZombiePikachu said:
It clearly says on step #1-
Instructions:
1. Restore your phone to the stock LG G2 D80010d firmware. Please click "here" for directions. (remember that you have the AT&T device when reading that post...) If you don't like that post, here's a youtube video (not mine) for doing the same thing. Make sure you restore the D80010d firmware and _not_ the D80010o firmware!!
So obviously the first step is to flash back to 10d it cannot get any simpler than that
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
more people asking questions that have already been answered. then when you point out that their question has already been answered they say they are trying to clarify even though it's already been clarified in the OP. it's a phenomenon on xda.

xLordNitro said:
Sigh...on every single KitKat Stock ROM ive tried so far...Bluetooth kills the battery, i mean it massacres it. I really dont get what the issue is...some sort of wakelock?
Click to expand...
Click to collapse
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
FlyingColors said:
I'm just trying to get some clarification so I don't have to go out and spend $400 on a new phone.
Click to expand...
Click to collapse
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.

xLordNitro said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. So i decided to rewipe everything, ReFlash stock Jellybean and reroot and do everything all over again and then i flashed this, same problem. Bluetooth is completely off, i rarely use it. It went from 100%-60% within 1 hour of just standby, didnt even use the phone. Look at the stats and Bluetooth has been keeping the CPU awake the whole time. So i did what someone suggested, turned it on and off and rebooted. Same problem. Went back to JB, no issues.
Click to expand...
Click to collapse
after you went back to jb then rooted and installed custom recovery then flashed this firmware, did you do a factory reset upon first boot? meaning did you get past the initial set up then go to settings/backup and restore and reset the phone? if not then that could be your problem. the factory reset does indeed reset everything after you initially install kitkat. it worked for me also, i had mms issues every time i initially installed kk. after a factory reset the mms is resolved.

Yep, did that. Still same problem. So im assuming its something to do with the files themselves, and maybe the fixes that are being done to keep recovery. I dont know. But im back on Jellybean for now, i cant let my battery take that huge a hit.

xLordNitro said:
Well i had this problem even when i had apps installed on a different Stock KITKAT rom created by someone. I DID NOT have this problem on the official OTA from AT&T, or on the PowerUser KitKat ROM but that had so many things missing that ireally did enjoy, maybe ill download the pack with the removed apps. ... . It went from 100%-60% within 1 hour of just standby, didnt even use the phone.
Click to expand...
Click to collapse
Wow. That's REALLY strange. I wonder why it's impacting only some users, and not all. (It would make sense that if it happens when BT is turned off, it would impact 100% of users.) Something else that's odd is that it happens with this, but not with the OTA. Even more strange is that it happens with that other "stock kitkat" firmware, as that essentially is the OTA with zero changes - it's even using the OTA provided bootloader and kernel.
I'm not really sure how to guide you on troubleshooting this. Anything I might suggest would take a few days of reverting and flashing various things, and I somehow doubt you'd want to spend the rest of your life doing random experiments for me. Perhaps you should try that poweruser firmware with things added one at a time - as you suggested.
Take care
Gary

garyd9 said:
I've seen that people have reported that issue on the D802, but I have to admit that I haven't seen the issue whatsoever on the my own D800. I have bluetooth on 100% of the time, and connected twice a day (on my commute to work and my commute back - each about 45 minutes.) My battery on 4.4.2 is about the same as what it was on 4.2.2 - however, "bluetooth" does show up higher on the battery app list of what is using power. Yet, it doesn't seem to have any real impact on overall battery life.
What are you basing the statement that BT is killing the battery on? Some of those OEM batter apps (like the LG one and even the android built-in one) are often misleading. For example, at least with 4.2.2, my phone wouldn't show "pandora" as a battery user (instead blaming 'android system.)
Of course, it's also possible that, for your environment, something really is causing BT to use up more battery than it should. There are several services related to BT, including the newer GATT/ATT (not related to AT&T) calls. (They are related to low power profiles.) It's possible that *something* in your environment is interacting with the phone or one of those services in such a way to cause issue... I'd suggest getting betterBatteryStats, install the piece needed for it to work properly with kitkat, and getting more detailed information from that. (When I say "environment", I mean the physical space around you, the software on your phone, or anything that may influence RF, light, sound, etc around your phone.)
...and I'm trying to give EXTREMELY clear and detailed instructions so that people don't have to replace their phone. In fact, my instructions take a paranoid approach.
However, your question is essentially asking if you could skip steps. Does a "cautious" person skip steps?
Well, you can - assuming you know EXACTLY which partitions are installed on your phone, EXACTLY where they came from, EXACTLY what version they are, and you are 100% sure that they all match what is required. Of course, if you already had all that information, then you wouldn't feel the need to ask the question, as you'd obviously be "geeky" enough to not even really need a recovery package to install it.
Don't come into this thread asking if you can skip steps and then say you want to protect the investment in your phone. As well, don't get an attitude with me if I don't put my entire life on hold, and spell out to you the very same directions that are on the first post on this thread. Don't want to follow them? Fine. Don't. Honestly, I could NOT care less what happens to your phone if you don't want to follow the instructions I typed out.
You can read. I know this, as your question was in the context of the thread. Are you one of those people who will install kitkat, won't bother to "factory reset" the phone, and then complain that things don't work properly?
Edit: On second thought, FlyingColors, please don't install the package from this post. I get no benefit if you do, but you've already been a burden. I'd rather you continue to use whatever "custom rom" you are using. It's obviously something you are happy with (as you don't want to restore your phone to stock), and I don't have the patience to answer questions when I've already taken the time to give the answers.
By the way, as you want "clarification": It's not a "rom." It's not even a "ROM." At best, it's "firmware." If it was "ROM", you wouldn't be able to change it. Read Only Memory.
Click to expand...
Click to collapse
Too late, I've already installed it and successfully have Kitkat. Even though you probably don't like me, thank you.

Problems going back to other rom
I was running flex rom before end flash kk end the motion sensor calibration work but doesn't work on my other roms only work on kk only. please fix

Android 7.0 (Nougat) + XT1575 + Systeless Root = ??

When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..

All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.

Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted

Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!

CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.

I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.

roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.

Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.

I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.

roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.

Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.

Rooting PK1 and unlimited Tmobile Hotspot

I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !

I'm not on the PK1 firmware yet, but I just upgraded from PG1 to PIA.
As far as performance goes, I found this thread VERY helpful: http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
Maybe it will serve well for you as well. As far as rooting is concerned, not too sure from personal experience, but I heard the ENG boot works with the newest firmware and I'm guessing the modified SU should work for it too.
If you would like to try reverse engineering the files yourself, maybe these guides will help out:
http://arm.ninja/2016/03/04/reverse-engineering-samsung-s6-modem/
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
http://www.fortisfio.com/extract-android-rom-for-reverse-engineering/
In regards to removing bloatware, I prefer removing apps over services because you never know when you might need a service that you accidentally removed from a previous time. Also I've been going through many cases of trial & error with removing bloatware and a few times ended up messing up other apps in the process that would force crash, but with my current setup everything seems to be working well.
If you need help with removing bloatware, there are 3 apps that really helped me out.
https://play.google.com/store/apps/details?id=com.piriform.ccleaner <-- Surprisingly ccleaner is awesome for the android as well as the PC.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en <-- this is very useful as well
Another tool I found very great and you run this from your computer is Debloater: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Hope this helps. I'm trying to currently work on a way of creating custom odin flashable roms so I can optimize roms to the best of my ability and provide the community with more options as well. This is still a work in progress though. :S
EDIT:
Here is an output of my program list. It was too long for me to post directly in the message
adb shell pm list packages -f

thanks a lot!
I have read about ENG boot being an improvement as well, yet nobody is stating that it is stable as it is prior to root, just improved lag, performance and stability. I know in my experience, root, for the first time in 8 years of rooting is not worth the benefits. This is sad. Must be stable. (in addition -no roms, no nanroids, no samsung Sumsung Pay..etc..etc..) So I'm hopeful things will change soon, or will be forced away from Samsung. Tmobile privacy invasion issue, and bait-and-switch with their plans is even further less encouraging news. Imagine "unlimited" = less.... wow.

Well said, and I completely agree. I've been a BIG fan of previous Samsung models, but it seems with every new model that comes out there are less and less options for customizations. I'm currently in the process of trying to figure out how to repack tar.md5 files *properly*.
I've gotten close, but then it fails right at the very end. I'm still waiting for a response from someone hopefully with more knowledge than I, but I guess I have to be patient. Here was my thread: http://forum.xda-developers.com/tmobile-galaxy-s7/help/creating-flashable-odin-file-t3500139
Any way, I'd love to see more customization for the S7. I think it's a great phone and it has so much potential. I also love android and always felt it gave users more ability for customization as opposed to Apple. Like you, I just hate all the bloat ware and all the crap that comes on phones these days. Not only that but the markup price is ridicules. Having to pay $600+ for a phone that is "laggy" due to all the bloat on it is frustrating to say the least. This is why I'm trying to give the community more options or at least steer them in a direction to customize their devices easier. Currently despite all the various amounts of software that is provided through this community I feel like there aren't too many people that know how to properly use it.
Any who, good luck with your phone. Let us know if you figure anything out with it. Also, are there any significant advantages with the newest firmware over the PIA? I usually like to hold off from upgrading right away so that all the "kinks" get worked out first since it's difficult to downgrade afterwards.

xena499 said:
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
Click to expand...
Click to collapse
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.

Its bootlooping because you accepted the security update popup.

You know what, that happened to me once, I forgot. What I needed to do is reflash the ENG boot file then when I got back into the phone, remove and reinstall SU. After your phone restarts, go into playstore --> you apps --> and uncheck "Auto Update" for Super User.

KillerClaw321 said:
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Click to expand...
Click to collapse
thanks I tried going back to PIA and used fixes only, as the debloater might be the culprit !

I got it work now here:

@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.

m0d hipp¥ said:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
Click to expand...
Click to collapse
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.

xena499 said:
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
Click to expand...
Click to collapse
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?

m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
NO you need the Tmobile files, available in links here, or better from the sammobile.com site i mentioned above.
I would never flash verizon firmware on a tmobile-connected phone.
In addition, are you following the verison unroot method from the verizon s7 rooting guide? the verizon root references for me were just where the best info is for all S7 people, but the software links are to older firmware that didnt work...
Basically, you are using odin to flash ALL files at once (ie AP, BL, CP, CPC), then you are back at tmobile stock as per date of package used (PIA, PG1..etc).
Earlier versions before PIA do not flash, for me. I believe this is b/c i took an OTA security update that did something to prevent this. PIA worked fine for me, and is working not bad.
I'm satisfied for now, and I will wait for stable Nougat before anything else, and done with customizing and playing.
I hope this helps you

m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....

Any luck?
sardor_x_z said:
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Click to expand...
Click to collapse
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.

silversusanoo said:
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
Click to expand...
Click to collapse
I just rooted mine this morning. I played around with it a few times. What worked for me was run root.bat with my phone unplugged then plug it in. It took a few minutes for everything to go through. Hope this helps.
Sent from my SM-G935T using XDA-Developers Legacy app

Also would like to know bypass for limited tether greatly appreciated
Sent from my SM-G935T using XDA-Developers Legacy app

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

Do you really need the latest security patch? and other thoughts for newbies et al

By all means, read @Neffy27 's FAQ if you are starting out. even as a refresher for stuff you may have forgotten.
-But do think a bit about what you are doing:
-Do not modify your phone unless you are willing to toss it into the trash, as that could well be the result, no matter how well planned.
-Always have a spare on hand. I used my old Moto G3 when my MZP died suddenly. Worked just fine. You know, things really haven't changed all that much since Gingerbread...
-If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like.
- Be aware that if you modify ANYTHING on your phone, even as little as a new boot logo to cover up the unlocked bootloader message, you will prevent your phone from taking any further OTA updates. Some mods, like adding TWRP, may still allow it to try to download and install an OTA, but when it reboots to finish that install, it will fail since it needs to re-boot through stock recovery to complete. And it will continue offering you that update.
- There is a difference between the partition structure in our phones on 8.x, and those on 9. 9 is not full Treble, only a "partial" Treble, and really only the addition of a second set of partitions which OTA updates can use to update the system - instead of modifying the single partition set, it modifies the other (a or b) set and boots to that on update completion. If it fails it can always boot the other set. Theoretically! Makes it safer than the old way of doing OTA updates, but this may cause problems if you try to flash a 2 partition set phone with a single partition set ROM. I don't believe anyone has run any experiments on this, so YOU, when you flash things without thinking about the situation, may get an unusable phone. I do not know the answer here. If you read these forums which detail other's problems, you may trod a bit more hesitantly!
-The idea here is to have fun, and sometimes to experiment with new things. To a newbie, losing the use of a $200 phone can be a tough life lesson. Let's help them out by helping them to be cautious!

Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk

SR3TLAW said:
Agreed. I've been running stock with January 2018 patch, TWRP installed and Magisk for root and successful safety net bypass.
I'm looking to see if running Lineage will help streamline any update processes. It looks like they have their own recovery too.
Maintaining root has become a pain in my ass the past few years.
Sent from my moto x4 using Tapatalk
Click to expand...
Click to collapse
I would be careful about lineage as folks don't seem to be able to get back to stock from it.
I agree about maintaining root. I will likely just stay on stock with this one.

Database Info

welcome