Database Users

[Q] LG L3 e400 stock recovery, rooting, Link2SD, etc.

Hi everybody,
my sister has got this phone a month ago and she is obviously out of memory. So the most immediate step is to install Link2SD. I am used to my Galaxy phone where to root it one just needs to hold Vol UP+Home+Power to get into the stock recovery and install any zip files. So after founding nothing useful in Internet I decided to ask in here:
- Is there any similar "hotkey" for the e400 to boot in stock recovery?
- Can the stock recovery install any zip file?
- Does the 1click rooting for Galaxy phones really works? If so I can make a simple zip package with "su" only, she would get mad dealing with notifications and all crap like that (I know, it would be more insecure but we just give permissions all times, anyway don't we? )
- Would it break the official updates? I know that the rooting would be lost after updating, but it would be a matter of seconds to redo it if it works like above.
- Any idea about a custom kernel (better if the latest stock one with modified scripts in RAM disk) with support for /etc/init.d? I could port my script Switch2SD which operates like Link2SD but at boot time.
- Last but not least, why the heck the SD card has two FAT partitions?!? What's the point for Android to show the first SD partition as "internal memory" if it doesn't really use it? Well, it does, but with App2SD which is lame.
I am not really interested on CWM or Custom ROMs unless they are really needed. Thanks in advance for any help!!

First, the L3 doesn't have a stock recovery, the key combo only do a full wipe;
Second, use SuperOneClick to root the L3, it works very well;
Third, Rooting your device doesn't break the official updates (if there will be any);
Fourth, I am working on a kernel that supports init.d, and I don't know about any stock kernels with init.d (only overclock);
And at last, I don't know why we have two FAT partitions, but I know that we can merge these partitions with SDMergE400.
Hope I helped!

g.carvalho97 said:
First, the L3 doesn't have a stock recovery, the key combo only do a full wipe;
Second, use SuperOneClick to root the L3, it works very well;
Third, Rooting your device doesn't break the official updates (if there will be any);
Fourth, I am working on a kernel that supports init.d, and I don't know about any stock kernels with init.d (only overclock);
And at last, I don't know why we have two FAT partitions, but I know that we can merge these partitions with SDMergE400.
Hope I helped!
Click to expand...
Click to collapse
Thank you very much, very kind from you! But that introduces a new question: how can I install SuperOneClick if I can't get into the stock recovery?
EDIT: never mind, I thought it was the .zip for the root installation for the Galaxy phones..
Then will your kernel be ready soon? Will it be a stock one?

Well, I am modding the kernel on the SDMergE400 zip, just testing, then I will mod the Stock kernel!
But these are just plans, it will take a little time...

g.carvalho97 said:
Well, I am modding the kernel on the SDMergE400 zip, just testing, then I will mod the Stock kernel!
But these are just plans, it will take a little time...
Click to expand...
Click to collapse
Never mind, I managed to root the phone (with spectrum_root_linux_osx from OS X. It works!!) and I installed Link2SD. I must say that this phone seems amazingly fast! I have a Galaxy Pop Plus (it's equivalent to the Galaxy Y) and its performances are horrible. The LG e400 is a nightmare in terms of system administration, though. With our phone we can do everything from stock recovery.So I better leave it as it is. Hopefully Link2SD won't mess up. My sister seems confident enough with it now. But if it breaks it will pain a customer support pain (you know, sisters.. ).

If you don't feel good to mess up with your phone, you better leave it as it is, like you said!
Android isn't for the users who want everything simple and ready, we have to think a little when using it (and that's why there are much people with iPhones and stuff)

g.carvalho97 said:
If you don't feel good to mess up with your phone, you better leave it as it is, like you said!
Android isn't for the users who want everything simple and ready, we have to think a little when using it (and that's why there are much people with iPhones and stuff)
Click to expand...
Click to collapse
Sure. That would be true for me as well If only I wasn't the developer of the custom and stock modified (with /etc/init.d support) kernels for my Galaxy S5570I phone..
What I meant is that the way the filesystems/Partitions are organized in the LG e400 is totally different from everything I have seen before. For example I made now 3 partitions in the SD card for Link2SD with the first one of 20MB. Android still reports a first partition of 1GB. It's just that I don't have time to mess up with it, being my sister's phone. So i decided to leave it rooted with Link2SD and that's it. I checked SDMergE400 as well, but they talk about installing a CM 9 to make it working. I could do it if the phone was mine, but not with someone else phone. regarding my phone, it sucks. badly. Ask anyone with a Galaxy Y, which uses the same CPU BCM21553. We don't even have the source codes to make full use of the GPU Videocore IV and thus to port the CM. In Antutu benchmark the soldiers go at 10-14 fps.
The iPhone (iOS) has mods as well, anyway. People are doing some pretty neat stuff after jailbraking it. Which is not even needed to run some basic useful tools like Adblock, unlike Android that needs to be rooted.

Custom Rom CM9
feel the Ultimate performance JellyCast-e400

Miche1asso said:
Sure. That would be true for me as well If only I wasn't the developer of the custom and stock modified (with /etc/init.d support) kernels for my Galaxy S5570I phone..
What I meant is that the way the filesystems/Partitions are organized in the LG e400 is totally different from everything I have seen before. For example I made now 3 partitions in the SD card for Link2SD with the first one of 20MB. Android still reports a first partition of 1GB. It's just that I don't have time to mess up with it, being my sister's phone. So i decided to leave it rooted with Link2SD and that's it. I checked SDMergE400 as well, but they talk about installing a CM 9 to make it working. I could do it if the phone was mine, but not with someone else phone. regarding my phone, it sucks. badly. Ask anyone with a Galaxy Y, which uses the same CPU BCM21553. We don't even have the source codes to make full use of the GPU Videocore IV and thus to port the CM. In Antutu benchmark the soldiers go at 10-14 fps.
The iPhone (iOS) has mods as well, anyway. People are doing some pretty neat stuff after jailbraking it. Which is not even needed to run some basic useful tools like Adblock, unlike Android that needs to be rooted.
Click to expand...
Click to collapse
Oh yes, filesystems on the L3 are REAL messy :/
But I got a chinese tablet (SK-3031 or GT-1230) and it's really, really complex to work in it's filesystems, so it's easy for me ;D
And Android have some neat features by default that the iDevices don't (freedom, for example) :laugh:

[Q] [Discussion] F2FS Support

First of all, I'am not a dev, so it isn't sure that this idea will see a future.
So, in the last month, I tried to use F2FS instead of the ext4 on my Nexus 7: I was curious to see if it is only a placebo mod like the Seeder entropy generator, and the good news is that it seems not to be the case.
It is already known to the raspberry pi community that infact this filesystem do a difference, and also on some devices seems to do the job (some benchmark, this of anandtech, or this done on a Z1 for example); maybe it is less reliable than the ext4, but we are talking of mobile device not web server (also I have seen lot of mods that disable the journaling of ext4 attempting to increase the performance, so I think that this is the minor problem).
To use it we need to add the driver into the kernel (here i find some backports, there is not a 3.4 backports but I think that adapting the 3.5 version would be quite easy), edit the fstab and if I understand correctly to build the recovery with the support for F2FS (here are the cyanogenmod tools), so we need to modify the kernel; @mikeioannina, maybe you can try this if it isn't too much work, if we use it only to the data partition we only need to format it, if we wont to use it also on cache and system we also need some edits to the rom.
If my explanation wasn't clear (sorry for my crappy English BTW), this is the topic for the Nexus 7, I took all of the information from that topic.

I agree with you that in f2fs is something which makes devices faster. Im using it on my tf300t and its awesome.
Would like to see it for our play, but truely on devices like ur nexus, my transformer and some other (which have possibility to use f2fs) /data is for apps and other files not only for apps like in our play, so I dont think it will give so much "speed".
However if there would be possibility to mount (fast) sdcard as both /data and /sdcard in the same time (and dont use real /data partition or repartition it as a part of /system for ie mods) and format it as f2fs? Here we could gain something.
It all was about /data partition, coz I dont know how works device with /system as f2fs. It should be faster too.

[Edit: Not SOLVED] Pulling /system via ADB doesn't pull WLAN/Wi-Fi modules.

Going to try and make this short and adequately detailed:
I've not worked on or directly tampered with ROMs for about 2 years (though I did with individual apps) now and when I felt like working an OxygenOS optimized & stripped 'base ROM' (with GApps, Swiftkey etc. properly exterminated from the ROM) to allow other devs (and myself) to make ROMs on top of (lack of OOS based ROMs makes me sad, even if CM is seen by most as superior). I have figured out a problem which has never occurred to me before in any of my devices or the experience I had a while ago.
I find that when I pull /system from the stock or modified stock OxygenOS ROM that WLAN/WiFi modules aren't being properly pulled for me. This is true for me both if I am pulling with the OS properly booted and functioning or if I am pulling when being in recovery.
This is a problem because I have to add them manually each time around I pull /system from my device to the dump which simply is inconvenient and wastes time for me.
Of course my other alternative is to take a nandroid and extract from nandroid but I don't know how to decompress backups made with TWRP 2.8+ with Windows (normally I'd run a unixlike system for work but I had to temporarily move Arch off my USB drive which I needed for an OS installation onto another system). (The ext4 backups don't open in the tools I traditionally used.)
(In case you are asking, I am running adbd as root in order to do the operations, I won't forget that after such a while.)
Oh and by the way, the ROM base itself otherwise once the missing libs are added runs fine, I've tested it already. I've still to zipalign my apps and optimize the images (JPGs & PNGs) inside the system apps as well as add some of my battery optimisations into the ROM (w/ default kernel config --> I'm shipping Boeffla [with all necessary credits due] w/ its config app given all other kernels are dead ATM, also shipping the SD810 tweaks). SuperSU, busybox and other common tools are obviously already integrated. In fact I'm posting from it right now though I'm in a rush typing this up because the frustration I had (trying to figure out why WLAN wasn't initially working and then not figuring out why the modules weren't pulling) has now reduced me to 4h of sleep :/.
Sent from my ONE A2003 using Tapatalk
Edit: Solved by using a different ADB version as admin and a shorter directory without spaces.
Edit2: Not solved
wlan.ko still doesn't pull when I pull /system.

[HOW-TO] Convert to F2FS on Nexus 6 (ALMOST - Any Rom)

BE WARNED - THIS WILL ERASE EVERYTHING ON YOUR PHONE. DO NOT ATTEMPT THIS IF YOU HAVE NOT MADE A BACKUP AND/OR ARE NOT READY TO REINSTALL EVERYTHING ON YOUR PHONE FROM SCRATCH.
Credit goes to bbedward for his initial thread regarding this concept.
STATUS:
2017/01/08 - Not liking the performance of my Galaxy S3, so I've ordered a new phone (Huawei P8 Lite) for $58 from eBay! Supposedly brand new. I figured I'd have to give it a try just to see. Once I set this phone up I'll start tinkering with my Nexus 6 again. Phone should arrive around 17 Jan!
FOCUS:
Getting F2FS on ANY ROM, but for my purposes, I'm focused on getting F2FS with Flash Kernel to work on Nitrogen OS (if this can be done, then it can be done with any ROM!)
BASICS:
- Need recovery & kernel that support f2fs (tools + kernel driver version must match or be compatible - not sure what the specifics are yet)
Latest New Info:
- The Flash has said that his kernel and crDroid work with F2FS (I haven't tested it myself yet - this version of crDroid actually specifies F2FS support)
2017/01/08
- Found this thread by NABENDU1. It's for Nexus 4, but it gives some good insight on how F2FS works.
- @vprasad1 found another working combination (post #15) - franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Explaining a few details:
The issue here is that the exact version of F2FS tools included in most modded recoveries isn't actually specified (that I have found) and the version of tools that end up in the ROM (/system/bin/), which come from the recovery unless built into the ROM, must be compatible. One of the following is true (not sure which one yet):
- the F2FS tools version must be the same or greater than the kernel driver support version
- the F2FS tools version must be the same or less than the kernel driver support version
- the F2FS tools version must match the kernel driver support version
Given that The Flash is consistently including the latest F2FS support in his kernel, and since I've had the most trouble getting F2FS support to work with his kernel and other ROMs that technically don't support F2FS (using bbedward's method mentioned above - link to thread included) I'm inclined to think that the F2FS tools must be the same or greater version compared to the kernel driver support, though I have no way of confirming this yet. Hopefully I'll have different luck with Flash Kernel v1.7!
========
I used:
- Nexus Root Toolkit v2.1.9
- Nitrogen OS 2016-11-19
- MagiKernel v1.1 Stable-1023
- TWRP 3.0.2-0 (modded by xanaxdroid - thread is here)
(TWRP v3.0.2-0 by xanaxdroid mirror) - the original link is down.
I'll take these down if xanaxdroid asks. I have yet to hear from him...
Steps for clean install (and initial install of F2FS recovery / conversion to F2FS):
1) revert to stock (Nexus Root Toolkit)
2) flash recovery with f2fs support (Nexus Root Toolkit)
3) boot into recovery on device
4) full wipe device (normal wipe)
5) convert /cache & /data to f2fs
6) copy over desired kernel and rom to /sdcard
7) install rom & then kernel
8) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
9) reboot
========
When changing ROMs/kernel (F2FS recovery already installed):
1) boot into recovery
2) do full wipe (f2fs should have stayed from the first time)
3) install rom & then kernel
4) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
5) reboot
========
More semi-lengthy explanation about fstab:
bbedward suggests a difference in the fstab as being the primary suspect causing the difference in compatibility. Here's the only difference I could find that seemed to be relevant:
- the fstab that worked (MagiKernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
/devices/*/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
- the fstab that didn't work (Flash Kernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
*block/sda* auto auto defaults voldmanaged=usbdisk:auto,noemulatedsd
Both fstab files did clearly have the lines needed to mount /data and /cache as f2fs, but they were identical.
NOTE: I also tried TWRP v3.0.0-0 (by xanaxdroid) with Flash Kernel and still no dice. I'm a fan of Flash Kernel since it's my first custom kernel I've played with. I hope to be able to use it some day with Nitrogen OS! Until then, thanks MagiKernel! (maybe I'll convert??? ) <- MagiKernel development has halted for now
========
What I've tried before:
All of the following implies that I've used the previously mentioned adb commands to copy over the f2fs tools and set the proper permissions.
In my experience, it seems that f2fs requires just the right combination of kernel + recovery. For example I used Nitrogen OS (2016-11-19) + Flash Kernel + mod TWRP 3.0.2-0 and it hasn't worked for me, but Nitrogen OS + MagiKernel + mod TWRP v3.0.2-0 did work. The failure for f2fs to work with Nitro OS + Flash Kernel is very reproducible, as is the success with Nitro OS + MagiKernel. (Again using TWRP v3.0.2-0 modded by xanaxdroid).
Keep in mind that the developer of Flash Kernel (developed by The Flash) has tested his kernel with crDroid (a CyanogenMod base ROM) and it worked for him, but I don't know what version of modded TWRP he was using and what version of f2fs tools were in that recovery. From what I've noticed, there seems to be a fundamental difference with CyanogenMod based ROMs when it comes to f2fs support, either that or there's just a version mismatch of f2fs tools between certain recovery + kernel combos. I don't know enough to understand the difference yet, but it is clear that just because a kernel claims to support f2fs doesn't mean that it will work with any ROM, even if you follow bbedward's tutorial mentioned at the top of this post.
The kernel and the recovery must work together (as in what version of mkfs.f2fs / fsck.f2fs supported by kernel & recovery must match (i think - thanks to bbedward again for this info)). The main issue here is that most modded recovery zips/imgs (that I have found) don't list the version of f2fs tools they have. On the other hand usually you can see this info on the main page of any given kernel developer.
I haven't found any specific rhyme or reason yet, but for those looking for Nitrogen OS (2016-11-19 - Android 7.1 - Nougat) + f2fs, this will help you.
NOTE: I'm a clean-freak, so I enjoy clean flashes, so my instructions are geared toward clean flashes, not dirty flashes. Having said that, doing this with a dirty flash is possible, but it will depend on the ROM/kernel you choose as to the details in how you upgrade/switch the ROM/kernel. Done properly, you should only have to switch file systems once and forego any future wiping of your /sdcard or internal storage.
========
NOTE : You'll know your recovery + kernel combo isn't working right when it takes longer than usual to get off the bootloader screen and start with your ROM's animation boot screen. If it's taking too long, you're probably having everything converted back to ext4.
*** WARNING *** WARNING *** WARNING *** WARNING ***
DO NOT INTERRUPT THIS PROCESS DURING BOOT. If you do then you'll render your /data partition inaccessible. It's still fixable with Nexus Root Toolkit > revert to stock, but that's a pain and it takes a while.
This OP will be updated as new info is uncovered!

Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm still researching a way to get Flash Kernel with Nitro OS + f2fs. I have some ideas. I'll update the first post with any new findings.
Edit: unfortunately MagiKernel is dead. So ill be hot on another trail soon. Also MagiKernel isnt as good as Flash out-of-the-box in my experience so far.

ozzmanj1 said:
Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Click to expand...
Click to collapse
I actually just tested the link to MagiKernel on my PC and my phone (on XDA Labs) and it worked fine. Are you using another (older) version of XDA forum viewer?
EDIT: OP updated. The "issues" we all run into is a version mismatch between RECOVERY & KERNEL mostly. As long as RECOVERY & KERNEL f2fs tools match, then you can copy over (mkfs.f2fs & fsck.f2fs) from /sbin/ to /system/bin/ and get any ROM to be compatible with F2FS.
EDIT: modified links and removed "" in URL tags. The quotes were necessary for proper display in the XDA Labs app, but not compatible with XDA Legacy app. I've switched to use XDA legacy!

Will this fix low battery throttling and video recording

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
LOL, no.
This won't "fix".... ANYTHING.
In fact, this will very likely BREAK things.

Lol how so

No not breaking things here ... Not any more than usual tinkering under the hood... I'm just trying to flush out bbedward's old thread with some more info...

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
To give you an answer, no it won't. This info will only "possibly" help you get a ROM to run on f2fs that was not initially designed to do so.

@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...

TheArkive said:
@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...
Click to expand...
Click to collapse
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?

ozzmanj1 said:
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?
Click to expand...
Click to collapse
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd

TheArkive said:
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd
Click to expand...
Click to collapse
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the news! I'll be checking that out as well.

FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Code:
mount | grep f2fs
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.

Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.

zelendel said:
Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.
Click to expand...
Click to collapse
Was that in response to my post???
Sent from my SM-N910T using Tapatalk

vprasad1 said:
FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.
Click to expand...
Click to collapse
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!

TheArkive said:
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!
Click to expand...
Click to collapse
Just a quick link I came across. Not sure if it's useful but as it pertains to f2fs I thought I'd share.
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my Nexus 6 using XDA-Developers Legacy app

What is F2FS
Can Ya Here Me Now

Info about loop support 7.0+ EMUI [magisk, supersu etc]

Since many people seem to ask continuously if magisk work with nougat and why supersu sr3 flashable zip by chainfire doesn't work ill try to explain it here.
Since M huawei has updated the kernel to work with nougat they seemed to break some important stuff. Or disabled it. I cannot tell for sure. And since sources aren't out we can't tell for sure if it's disabled or just broken.
Supersu and magisk is relying on loop to get it system less. This requires a .img which is being mounted to the path which is being executed on boot. But with loop being broken or disabled the phone will for some reason not handle this well.
But this is the reason why supersu and magisk isn't working when trying to install it reboots twrp notice that even if you manually patch boot so it contains all info related to magisk or supersu images it won't help you. Because you'll not be able to use magisk since the system will not boot. Due to loop is broken or disabled.
So there will be no magisk for nougat? And when will it come if it'll be working?
Wait until kernel sources are dropped.
So can we get magisk working?
Well yes.
Our best shot is to actually create a folder in /data which is being symlinked to / or if we do a similar approach on how supersu works on nougat. But for now we can't mount images and that's why everything fails.
Hope this sum up things for you.
Sent from my CUBOT_MANITO using Tapatalk

You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.

Telperion said:
You're far more competent with Android development than me -- is it possible to fork Magisk and modify it to use a ramdisk instead of loop mounting? The Honor 8 has plenty of free RAM, we would probably do a 256MB ramdisk with no issue. Ramdisks don't require loop mounting so conceptually we should just be able to modify the mount / unmount, flash, and image update sections of the script.
Click to expand...
Click to collapse
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk

LastStandingDroid said:
Hmm maybe. As said we could do a similar approach on how supersu and phh works on nougat. The only downside would be placing all in ramdisk due to lack of storage space. Since it'll be filled too fast.
It could work in theory but not sure if it'll actually work properly
Sent from my CUBOT_MANITO using Tapatalk
Click to expand...
Click to collapse
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.

hachamacha said:
Has anyone from XDA (or elsewhere) actually got a "contact" at Honor/Huawei that has ever done anything positive for them (in the engineering/development realm)?
It doesn't appear that Honor 8 nougat is supported at all to me, but some things that could easily done with their "private source" of the Nougat kernel would be of great use and would not cause them to look as if they were being generous with their code. (I don't know why they're such dorks about it, but they are).
For example: IF you have some "insider" at Honor, please ask them for the stock emui loadable module (via modprobe or lsmod) for mount.loop support. That would solve the problem as there's not some reason why we can't find a way to load it during startup. If you guys get that, then you probably won't care about them probably never releasing the kernel source. I have no expectations for this company. Nice phone, but they lied about their development support. Too bad, because Kirin 9xx's are becoming nicer and nicer and in some ways are nicer than the heavily supported SD's, which are supported to a much larger extent.
Oh hell. We have working TWRP, so in theory, (and if we get the magical module for loop mount) we could root edit from TWRP and add the modprobe {modname-loop.ko) to whatever is the equivalent of rc.local or one of the startups (rc1.d, etc).
Getting someone to fork, develop and test the magik (sp?) code for one case and one kernel seems like a lean chance.
Click to expand...
Click to collapse
Many people probably have but won't try get people fired because of leaks
Their working on to get in touch though
Sent from my CUBOT_MANITO using Tapatalk

Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.

Telperion said:
Perhaps @MishaalRahman can push on behalf of all of us as a representative of XDA to get the kernel source released faster, and built correctly for once.
Click to expand...
Click to collapse
I'm not sure how much clout I would have, but it wouldn't hurt to ask.

I think @svetius is more into this.
You should ask him about it tbh
Afaik he's the on that handles this
Sent from my CUBOT_MANITO using Tapatalk

in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method

@simo255 lol

simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing a modded boot.img created by @HassanMirza01 and by setting selinux to permissive
big thanks to @Paolo83 because he found this method
Click to expand...
Click to collapse
please state more info about which image you use, whether you have stock firmware installed and which steps you took in twrp to install supersu and consecutively, magisk.