I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Agrajag27 said:
I just flashed the latest CM12 and it's great. Also installed TWRP.
The only issue is that now when I boot my P900 shows in red: Kernel is not seandroid enforcing.
Is this a problem and, how do I get rid of it?
Click to expand...
Click to collapse
your bootloader detects that, so there is no way to get rid of it.
my note 4 does this but I have actually never seen it on my P900, could you give more details on your exact model, rom, and kernel? I'm curious.
one way around that, I think, would be a kernel that is enforcing at boot, then use a script or an app to toggle it back to permissive (if necessary for your purposes)
edit: oops I see now -- CM 12, but still.. are you using the lollipop bootloader from the official update?
Hmmm.... I just rooted my Note Pro last night, stock rom with TWRP (latest). And though it boots up fine otherwise, I'm also getting the "Not SEAndroid enforcing" message. Would like that gone. And it is interesting that CM12 is having the same issue, because I was beginning to think about flashing it and ditching stock Lollipop.
Specifics: I used Odin 3.10 from a Windows 7 laptop for my initial boot flash of the CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 file to the tablet. No errors were reported. I also flashed TWRP 2.8.7 that way. Again, no errors. There was a beta version of SuperSU (2.49) but I didn't install that. Think I'll try it next... and hope for the best. I did install SuperSU Pro (2.46) once I'd booted the tablet, but maybe that's not available on boot?
Sterist said:
could you give more details on your exact model, rom, and kernel? I'm curious.
Click to expand...
Click to collapse
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Agrajag27 said:
SM-P900 like you.
CyanogenMod Version: 12.1-20150707-UNOFFICIAL-v1awifi
Android version 5.1.1
Kernel version: 3.4.104-g7e89e2e
[email protected] #1
Tue Jul 7 19:20:11 MSK 2015
Click to expand...
Click to collapse
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Sterist said:
but did you at some point OTA or odin to Samsung lollipop before CM12.1?
Click to expand...
Click to collapse
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Agrajag27 said:
Yes. I OTA 5.0.2.
I guess the big questions are:
1. Is there a fix that doesn't involve jumping back to KitKat?
2. Is having this issue in any way bad other than seeing that message on boot as everything else seems to be working.
Click to expand...
Click to collapse
I don't think there would be a way to go back to kitkat, even if you wanted to, after having installed the lollipop bootloader (happens when you OTA or Odin to stock lollipop)
to the user it's no problem at all -- it's just a visual notification to stores when you take the device back that it's been customized / modded, and voids the knox warrantee hence "Set warrantee bit: kernel"
knox, despite popular belief, is just a form of security and productive software for corporations to rely on when giving their employees a "work phone" to use, so they know that any potentially sensitive corporate information is safe from the security risks of rooting (though virtually never exploited, rest assured)
that's the most relevant answer I can give you, without repeating what I explained in my previous post *hint* lol
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Agrajag27 said:
Slightly confused about something I'm seeing. The error is that it's NOT enforcing, but Settings, About Tablet says it IS enforcing.
Also, you mention setting to Permissive with an app (which I've found) but that sounds like it won't be enforcing either and thus we'll still have the message.
Click to expand...
Click to collapse
the display at boot is not an error, just a notification of sorts.
the only thing I can think of is the CM maintainer may have compiled the kernel to boot as permissive and switch back via script for compatibility.
I have seen some roms that do this. not many, nor recently. I wouldn't worry about it though, especially since it's a Wi-Fi device that doesn't have any reason to visit a carrier store.
also note that the notification will show when booting a permissive recovery kernel -- these notifications are not permanent nor need to be "cleared" or "reset" they just inform the user (or technician) of the S.E.A. mode of the respective kernel at the time of boot.
Thanks. I can live with that. I'm a bit OCD and an old QA professional so it'll give me pause every time I reboot and see it, but I'll get over it. <grin>
Otherwise, I have to say, the tablet is working better than EVER with CM 12.x. Apps that caused crashes no longer do. Bluetooth keyboard works again. It's faster. I have only a single bug (the running apps list sometimes has graphic issues).
Related
After flashing a GPE ROM on a non-GPE device, I get these results: http://webmup.com/naZUn/vid.webm
Basically it is a weird horizontal transparent line that moves down the screen... After flashing the 4.4 GPE ROM got those symptoms -- But even after going into TWRP recovery, the line is still there!
Also, once I decided to revert to stock to try and fix it, there is still this annoying line after booting!! This includes stock ROM, CM, and TWRP ( But once booted, locking and unlocking will fix it temporarily)
I don't think its a hardware problem because the fastboot screen does not face the issue :\
Please can anyone give me some guidance? Im really desparate.
The cause of this phenomenon is the Bootloader (BL) included with Lollipop. Your current BL is 41.18, the KitKat version is 41.13. There is no way to return to the KitKat BL, and I suggest you avoid trying. The issue will disappear when using a Lollipop ROM and Kernel.
right now i'm on GPE 5.0.1 and when ever i flash cm12 over it i get like this screen flickering
and my question is we wont be able to use cm12 over 5.0.1 or what? Please some one explain
The issue is kernel-related and I expect can be resolved with a custom Lollipop Kernel. Current CM12 ROMs need to take into account the new bootloader - then the problem will be fixed.
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
marcoms said:
Thanks for the explanation!
Shouldn't CM 12 already be using a lollipop kernel though? What sort of changes to the kernel are required to fix the issue?
Click to expand...
Click to collapse
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
lost101 said:
Yes, but as you have observed; CM12's current Kernels (or any KitKat Kernel) are not fully compatible with the new Lollipop Bootloader (v41.18). The display problem does not occur with Stock Motorola Lollipop Kernels.
Perhaps @TeamMex can suggest what changes are needed.
Click to expand...
Click to collapse
well i don't have time to investigate what i need change to make fully compatible with new bootloader.
maybe when motorola release his kernel for lollipop I can check...
for now we need wait.
Can someone experiencing this issue try the following?
Settings > Developer options > Tick "Disable HW overlays"
Reboot may be necessary.
Unfortunately ive flashed back the gpe rom, but if no one else can do it then I guess I can try at home with CM
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
lost101 said:
Apparently disabling 'HW overlays' makes no difference. I guess the only way to remove this effect is to use a Kernel that is fully compatible with the 41.18 Bootloader included with Stock Lollipop. As suggested above, we have to wait for Motorola to release Lollipop Kernel sources before DEVs can figure out a solution.
Click to expand...
Click to collapse
Thanks for finding this out lost101 - we can expect a kernel release in early 2015 then
Hi there! First of all thank you guys for all the effort you're putting into this. I've got the same problem with the horizontal line looping down and wanted to ask if anything changed since the last post of december. I don't really like Lollipop, flashed back to 4.4.4 and am stuck with the line issue.
Thanks for any updates!
:good:
is there no update on this issue as of 18/02?
funster_ said:
is there no update on this issue as of 18/02?
Click to expand...
Click to collapse
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
lost101 said:
Nothing will change until custom kernels for stock are available. Maybe then a kernel DEV can find a work around. Motorola have not yet released any kernel sources for Lollipop - which they legally have to.
Click to expand...
Click to collapse
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
funster_ said:
yeah, that was what i mean.. is there no updates about motorola releasing the source for the kernel anytime soon?
Click to expand...
Click to collapse
After bricking my moto g by "downgrading" from Android 5.0 to 4.3, I recovered it by going to 4.4.2, but got this horizontal line issue. However, it seems to have pretty much cleared itself up. The last time it occurred, I allowed the screen to enter sleep mode, then woke it and the problem had fixed itself.
Just leave it for a while
Hey bro don't worry about a thing. I had the same issue. Just leave your phone for a while and the looping will disappear. From experience.
I got horizontal line on recovery.
I have 41.18 bootloader.
What is the problem?
Im on cm12.1 xt1033.
There is no problem on Rom though, its only on the recovery.
Here is a fix for the issue:
http://forum.xda-developers.com/moto-g/help/solution-to-moto-g-2013-tearing-t3408447
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.
Phone stuck on "Recovery is not seandroid enforcing" - Sprint 5.1.1 G920P Galaxy S6
I thought that after waiting nearly 2 full years of having my Sprint Galaxy S6 G920P droid version G920PVPU2BOF7 on Droid 5.1.1 that I'd be able to "easily" root it and then ROM it or put recovery on it etc.. whatever... and as it seems that was far from the case. I backed up "most of the phone" and realized when its too late that I missed a couple things.
Anyways, is there no way back from this "Recovery is not seandroid enforcing" to get into the UI for 5.1.1 OS to resume normalcy, other than to use ODIN to restore to a factory stock ROM?
Would you at this point instead restore to a Rooted rom?
If so, what is a good one that ya'll feel will work on the first shot?
I can't believe how much trouble I had rooting it or finding a good reliable root. I must not know where to look. Should I have started at CWM, CF or TWRP instead of googling around?
First time I tried, I lost all networking abilities. I wish now I had "backed up the stock Kernel somehow" before experimenting.
Right after that I got networking back trying a different 2nd Kernel root, but on boot it said "kernel is not seandroid enforcing", then the phone would start normally except for this "Unfortunately NetworkSystemProvider has stopped." popup that constantly was in my way and wouldn't allow me to get rid of it permanently. I could "OK" it away for 1 second to tap other things between it popping up and then I was able to shut the phone down for another root try with what I hoped would be the right Kernel.
On the 3rd attempt I got this "recovery is not seandroid enforcing" at the boot screen and accompanied with an infinite reboot loop where I could still see the Samsung and Android logo etc.. black screen. Loading to the stock recovery or stock bootloader preboot menu system no longer worked (up arrow + home + power) either.
Now I've got it at the downloading bluish screen waiting for me to either flash it with another Kernel (that I can only HOPE will work) or to completely wipe it out and reflash stock firmware or one that ya'll tell me will be worth trying.
This is very aggravating because I have 20 years of I.T. experience under my belt, but the resources on the web have gotten very difficult to navigate with so many ads, popups and CPU consuming pages while I'm trying to read.... its insane. I finally caved in and downloaded a stock rom from stockroms.net and sammobile.com (1 from each to compare) and I'm waiting before I wipe the phone out to see if there is a way to get it to boot again without wiping my data.
Any way to navigate the phone and mount it via USB to grab files before I wipe it?
Here's the phone info I was able to get off the About screen before I soft-bricked it:
Software version G920PVPU2BOF7
Hardware version G920P.02
Model #: SM-G920P
3.10.61-S6_UniKernel_v9-0000_beta
[email protected] #1
The Oct 8 19:35:09 MST 2015
Baseband version G920PVPU2BOF7
Build number LMY47X.G920PVPU2BOF7
SE for Android status
permissive
Security software version
MDF v2.0 Release 3
VPN v1.4 Release 5
KNOX version
knox 2.4
Standard SDK 5.4.1
Customization SDK 2.4.0
Container 2.4.1
CEP 2.0.1
SE for Android 2.3.0
SSO 2.4.1
TIMA 3.0
VPN 2.2.0
RATED
DC 9V; 1.67A
searcherrr said:
I thought that after waiting nearly 2 full years of having my Sprint Galaxy S6 G920P droid version G920PVPU2BOF7 on Droid 5.1.1 that I'd be able to "easily" root it and then ROM it or put recovery on it etc.. whatever... and as it seems that was far from the case. I backed up "most of the phone" and realized when its too late that I missed a couple things.
Anyways, is there no way back from this "Recovery is not seandroid enforcing" to get into the UI for 5.1.1 OS to resume normalcy, other than to use ODIN to restore to a factory stock ROM?
Would you at this point instead restore to a Rooted rom?
If so, what is a good one that ya'll feel will work on the first shot?
I can't believe how much trouble I had rooting it or finding a good reliable root. I must not know where to look. Should I have started at CWM, CF or TWRP instead of googling around?
First time I tried, I lost all networking abilities. I wish now I had "backed up the stock Kernel somehow" before experimenting.
Right after that I got networking back trying a different 2nd Kernel root, but on boot it said "kernel is not seandroid enforcing", then the phone would start normally except for this "Unfortunately NetworkSystemProvider has stopped." popup that constantly was in my way and wouldn't allow me to get rid of it permanently. I could "OK" it away for 1 second to tap other things between it popping up and then I was able to shut the phone down for another root try with what I hoped would be the right Kernel.
On the 3rd attempt I got this "recovery is not seandroid enforcing" at the boot screen and accompanied with an infinite reboot loop where I could still see the Samsung and Android logo etc.. black screen. Loading to the stock recovery or stock bootloader preboot menu system no longer worked (up arrow + home + power) either.
Now I've got it at the downloading bluish screen waiting for me to either flash it with another Kernel (that I can only HOPE will work) or to completely wipe it out and reflash stock firmware or one that ya'll tell me will be worth trying.
This is very aggravating because I have 20 years of I.T. experience under my belt, but the resources on the web have gotten very difficult to navigate with so many ads, popups and CPU consuming pages while I'm trying to read.... its insane. I finally caved in and downloaded a stock rom from stockroms.net and sammobile.com (1 from each to compare) and I'm waiting before I wipe the phone out to see if there is a way to get it to boot again without wiping my data.
Any way to navigate the phone and mount it via USB to grab files before I wipe it?
Here's the phone info I was able to get off the About screen before I soft-bricked it:
Software version G920PVPU2BOF7
Hardware version G920P.02
Model #: SM-G920P
3.10.61-S6_UniKernel_v9-0000_beta
[email protected] #1
The Oct 8 19:35:09 MST 2015
Baseband version G920PVPU2BOF7
Build number LMY47X.G920PVPU2BOF7
SE for Android status
permissive
Security software version
MDF v2.0 Release 3
VPN v1.4 Release 5
KNOX version
knox 2.4
Standard SDK 5.4.1
Customization SDK 2.4.0
Container 2.4.1
CEP 2.0.1
SE for Android 2.3.0
SSO 2.4.1
TIMA 3.0
VPN 2.2.0
RATED
DC 9V; 1.67A
Click to expand...
Click to collapse
Well I can see the problem straight away, the kernel unikernel is not designed for the g920p variant. The only way to get back to is to make sure you have twrp if you haven't got it already and then flash a kernel that is compatible with 1. Your variant and 2. For the version of android you are running, through twrp.
Might be an idea to have a look in the sprint s6 forums in here to see if there is a kernel which will work. I have a g920f so not sure what the situation is over in that forum.
Thank you for your response. Means a lot.
What about reflashing my kernel with a stock kernel as you said for: 1. My variant and 2. For the version of android I am running?
Would that regain me stock access as I had before?
Also is there a way to just "mount like usb drive" the phone in the state its in now bypassing all the Android stuff?
What sources do you trust to know what ROMs, Kernels etc.. correspond to correct phone models and droid versions?
Ok, so I regained "most control" of the phone by using twrp-3.0.0-0-zerofltespr.img.tar 25.3M 2016-02-18 09:46:55 EST for my build of droid and having the G920P. EURKEA!
I loaded into TWRP and mounted the drive to USB and got the rest of my data off it (I had most of it, but forgot a few things before I started since how Android works is all data is saved scattered across the file system per app).
I think I had been thinking that RECOVERY and KERNEL = SAME thing, but now I get that the recovery portion is separate because I'm running the TWRP 3.0.0-0- and I see as you said I have the wrong UniKernel which is still yielding the "Recovery is not seandroid enforcing" message at boot (but it does BOOT into lollipop again) as well as the neverending "Unfortunately NetworkSystemProvider has stopped." popup once I'm in lollipop 5.1.1.
So now that I have TWRP onboard all I am interested in at this point is finding the right ROOT KERNEL that will run 5.1.1 for G920P so that I can customize the ROM I already have .. trim it down etc... save it etc.. I just seem to be having a lot of problems finding Kernels from a reliable source especially for Spring 5.1.1 for my G920P.
Just a tid bit of added info, I looked at my System Update menu and saw this:
Last update: 8/17/2015
So I'd need a 5.1.1 Kernel that works just at or after that timeframe. All I'm seeing is Marshmallow or Nougat Kernels herein this forum and on google. Basically .... is there anywhere that I can look for older Kernels that would work?
Ok, I'm again a model G920P on droid 5.1.1
I got my phone on twrp-3.0.0-0-zerofltespr.img.tar - so I can load TWRP recovery.
I'm on kernel Unikernel-v9-BOJ7-G920P-120615.tar - the latest and best choice I could find for my G920P.
I am stuck at "Unfortunately NetworkSystemProvider has stopped." and it will not go away despite my best efforts. Otherwise the phone seems to be working well except for the "recovery is not seandroid enforcing" error on boot.
Did anyone ever get past the "Unfortunately NetworkSystemProvider has stopped." error without having to REflash the entire phone? and did that even work?
Good afternoon,
I have a N915FY with marshmallow 6.0.1. I had the Rom installed [ROM] [AROMA] Multi-CSC] Micky387_MM_V3.0 for 915F-FY-G, with which I was delighted, but did not fall into the error message until the battery began to cause problems. Following the steps:
- I tried to install the [AROMA] Multi-CSC again] Micky387_MM_V3.0 for 915F-FY-G, the file Micky387_MM_V3.0 for twrp recovery, but nothing else restarting the error still appears ... and after testing all the kernel I saw, nothing at all, so .. next step
- Install the rom of SamMobile N915FYXXU1DQB2_N915FYPHE1DQB1_PHE, which is the latest version to date, the PHE Black Edition. So far the new phone and without errors.
- Problems begin when installing twrp-3.1.1-0-tblte.img.tar, latest version today with Odin307, Odin_V3.09, odin3_v3.11.1, odin3_v3.12.7 ... and already appears when entering recovery the error "Set warranty bit: recovery". I also installed TWRP-3.1.0-for_915F_915FY_915G.tar, twrp-3.0.3.1_915F_915FY_915G.zip ... with the same result. The truth is that the error of the recovery I think gives a little the same, the problem is the kernel.
- Install the file SuperSU-v2.82-201705271822.zip, latest version today, and restart if "Set warranty bit: Kernel" appears .....
I ran out of ideas, time (I've been with the phone for 2 days, reading and understanding) and I do not know what to do.
I do not want to finish the post without thanking the work of all the experts who, unintentionally advise and support us.
Thank you very much.
Perhaps try RamKernel in the forums, not my favorite but works. I can also say AKLU works really well also. It is hit and miss with ROMs on this thing. I just got fed up and ordered a Note 8 Thurs. I cannot remember exactly it might be either a Signing issue or a SELinux issue. I'm wanting to say a signing, as it says something about SELinux. Its normally not an issue and a Samsung thing used for warranty/support purposes. I have never had issues, is there something specific other than this splash at boot?
I had problems because the battery only charged up to 67%. Then I read in a forum that this problem was due to a kernel error and I was investigating ... but I can not remove it in any way ...
martinetevfr said:
I had problems because the battery only charged up to 67%. Then I read in a forum that this problem was due to a kernel error and I was investigating ... but I can not remove it in any way ...
Click to expand...
Click to collapse
Normal for rooted phones. You can safely ignore it.
Sent from my SM-N915G using Tapatalk
arbit12 said:
Normal for rooted phones. You can safely ignore it.
Sent from my SM-N915G using Tapatalk
Click to expand...
Click to collapse
arbit12, thanks for solving my doubt. I remain calm
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.