yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] lukss12:
Yep, I asked because it's common to see that error on twrp but that don't mean the flash failed, did you try to boot RR?
[Nexus 5 Android Development] willyinpr4u:
Nope, but I can give it another shot and let you know. I really don't mind.
[Nexus 5 Android Development] lukss12:
That would be great
[Nexus 5 Android Development] willyinpr4u:
Are you kidding me? Even thou I got error messages installing the ROM and nano gapps, it boots. I'm in my iPad again since I was working on the Nexus 5 (obviously), but here is the screenshot of the error messages.
[Nexus 5 Android Development] lukss12:
Yes, there is a problem with some scripts and twrp and the way system is mounted, but system gets mounted and modified by the scripts, so RR works, rigth?
[Nexus 5 Android Development] willyinpr4u:
Oh yes. All 3 ROMs are working and booting fine. No problem so far.

Right now I am downloading an update for Dark_Rom with open Delta, of I run into any kind of problem I'll let you know.

BTW, I forgot to mention, I'm from Puerto Rico, that's why I asked if you were from Argentina.
[Nexus 5 Android Development] lukss12:
I will need any sort of log to help you, or the exact files you have flashed and the order you flashed them..
[Nexus 5 Android Development] kmem:
Is it possible to pass safetynet with EFIdroid?

(Primary and secondary ROMs)
[Nexus 5 Android Development] willyinpr4u:
From my own experience, yes.
[Nexus 5 Android Development] BreckZeBoulay:
No problem ;)

Thanks for trying it !

Just for info, UntouchedAOSP works with EFI.

Just a weird recovery appaears after flashing it. A repair with EFI Manager restores the path to TWRP.
[Nexus 5 Android Development] lukss12:
On primary it should work "as is" (if your ROM is SafetyNet compatible) In secondary you probably will need Magisk because of SELinux permissive.
[Nexus 5 Android Development] sa4ni:
Any Idea for boot Ubuntu With EFIDroid .......???
[Nexus 5 Android Development] lukss12:
It's necessary to analize the way Ubuntu mounts the partitions to create a proper ramdisk patching for ubuntu kernels... for now the EFIDroid's dev is solving more importants things that will let EFIDroid to be ported to many devices, when he finishes that... requests like booting non Android ROMs will be implemented!
[Nexus 5 Android Development] Snoop05:
Amazing job dude. Works on official LineageOS and eng.stk kernel.

I'm just looking forward for 2 improvements.

- autoboot last selected rom (timeout option)

- usb-otg drivers so i can use keyboard for efi shell

Keep up! :good:
[Nexus 5 Android Development] lukss12:
Well these are things that are in UEFIDroid developer mind, I'm just a porter for now and trying to get involved in it! good to know it's working with another custom kernel
[Nexus 5 Android Development] AndroZeek:
[MENTION=5361265]lukss12[/MENTION]

How I can remove EFIdroid?
[Nexus 5 Android Development] lukss12:
just use the trash icon fron EFIDroid Manager or manually fastboot flash boot boot.img and fastboot flash recovery twrp.img
[Nexus 5 Android Development] BIade:
Would it be possible, to multiboot different recoveries with your efidroid?
[Nexus 5 Android Development] lukss12:
Yes, that's a feature that is going to be implemented in the new EFIDroid that m1cha is working on. This new EFIDroid does not relay in LK bootloader and it will take a while until he finish it so he can move to feature requests. Then I'm going to be able to port it for hammerhead.

For now if you want to try a different recovery you can:

a- Boot your actual recovery for Internal ROM and flash your new recovery​ from there.

b-Use a root browser and replace partition_recovery.img in /data/media/0/UEFIESP folder with your new recovery.
[Nexus 5 Android Development] morfances:
Because of this tool I almost to brick my device. I had to reflash the factory Image. I don't recomend!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Android Development] BreckZeBoulay:
Because you have done something wrong.

I made many tests, never bricked my N5.
[Nexus 5 Android Development] willyinpr4u:
How in the world can you "almost brick" your device with EFIDroid?
[Nexus 5 Android Development] morfances:
Especially when the instructions are not clear.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Android Development] willyinpr4u:
Ok, totally understand.
[Nexus 5 Android Development] phpbb3:
Does anybody know if ElementalX 8.00 works properly? I know 7.09 was tested and failed to cooperate, but 8.00 is a rebuild from scratch.
[Nexus 5 Android Development] willyinpr4u:
[MENTION=5361265]lukss12[/MENTION]. What would happen if I decide to replace the primary rom flashing another rom? Will EFIDroid be affected in any way? I was thinking of flashing another rom.
[Nexus 5 Android Development] lukss12:
If you are going to despise someone else work, you may need to be more constructive, because I can't see here what your problem was. This is a very supportive community and I'm sure that one simple post could have solved your problem. About "bricking" the phone, with this app is impossible to brick a N5. FYI the only way to brick a N5 is flashing the bootloader a.k.a aboot with a defective one and EFIDroid does NOT mess up with bootloader level stuff, it just run as a kernel... and its modifications are ROM level. In the worst case scenario you'll need a PC with fastboot and a little brain to solve problems.

Whatever addition that you think is necessary to mention in the OP is welcome.

If you start TWRP from EFIDroid and select the internal ROM there shouldn't be any problem!!! :)

EDIT: btw [MENTION=6558666]willyinpr4u[/MENTION] I update my LOS 14.1 primary like that every week (well... every 2 weeks hehe)
[Nexus 5 Android Development] lukss12:
If you haven't tested it yet, send me link to the version you want to test and I will test it as Internal and Secondary with LOS 14.1
[Nexus 5 Android Development] willyinpr4u:
That's what I thought, but I just wanted to be sure. Thanks.
[Nexus 5 Android Development] phpbb3:
I tested it with a partially damaged hammerhead, but it died while I was rebooting so I never got to test. Thanks for your work!

https://www.androidfilehost.com/?fid=745425885120721069
[Nexus 5 Android Development] lukss12:
Installed as Secondary works (so it should work as primary... it is very unlikely not to say impossible that works as secondary and not as primary)!

There is some trouble with Aroma GUI installers in TWRP can someone confirm if this is happening without EFIDroid??
[Nexus 5 Android Development] phpbb3:
What kind of trouble? Aroma works perfect for me, as long as the screen doesn't reach the set timeout in TWRP while its running. If it goes to sleep while Aroma is open, I have to hard reboot and start again.

--Thank you for testing for me!
[Nexus 5 Android Development] lukss12:
Are you using EFIDroid to boot TWRP? My screen starts to blink between AROMA and TWRP GUIs, but I haven't tested without booting TWRP from EFIDroid.

EDIT : Yes it's an EFIDroid bug, somehow EFIDroid is causing that...
[Nexus 5 Android Development] phpbb3:
No, I'm at work right now so I haven't installed it yet in case I screw it up hahaha
[Nexus 5 Android Development] phpbb3:
Tested/working as Primary with AICP 12.1 7.1.2 and ElementalX 8.00 [MENTION=5361265]lukss12[/MENTION]
[Nexus 5 Android Development] willyinpr4u:
I was running Dark_Rom add internal ROM, then I flashed AICP as secondary, I found it so amazing that I flashed AICP as primary, deleting Dark_Rom. And as secondary I have OctOS, also a great ROM.
[Nexus 5 Android Development] kmem:
A bit off topic but can you briefly explain what's better?
[Nexus 5 Android Development] willyinpr4u:
You mean which ROM is better?

Is kind of hard to explain because it all depends on your experience testing the ROMs. And because of this is why I love EFIDroid, that way I can test various ROM. Dark_Rom is an awesome ROM, and so is AICP and OctOS. There is also a new ROM that was just build, SAOSP (Simple AOSP), give it a try.

And I apologise for the typo on the last post.
[Nexus 5 Android Development] mixmoto:
hi all!

i'm very happy for this new tool! i'm asking here...

it's possile to install ubuntu t on n5 with efidroid?

[MENTION=5361265]lukss12[/MENTION] thanks for your worrk!
[Nexus 5 Android Development] lulli1:
No, not until now.
[Nexus 5 Android Development] phpbb3:
Tested not working (bootloop) with slim 0.19 even with selinux forced permissive

[MENTION=5361265]lukss12[/MENTION] how is plasma? I use KDE as my primary environment on both my desktop and laptop, but I haven't looked into the mobile platform yet.. Is it hard to install?
[Nexus 5 Android Development] lukss12:
I love plasma for desktop but the mobile versión is far away from the usability, stability and beautifulness of his desktop counterpart :(

About slim 0.19, may be the same problem than stock MM... I need to take some time to compare SMEM booting from stock bootloader and from EFIDroid, it would be very strange that SMEM gets corrupted but the logs I got from MM indicates a problem there :/
[Nexus 5 Android Development] phpbb3:
The lack of graphical design I guessed based on the video on their website, but its unfortunate that it's also unstable. I use a rolling release beta distro (opensuse tumbleweed) and even with the latest packages I find KDE/plasma to be very stable.

Do let us know what you learn about the SMEM issues with MM builds, as well as whether this is the problem with Slim. Let me know if there's a way I can help (although I'm only a PC enthusiast, my android knowledge is limited) I'll do my best. Thanks for all your hard work!

EDIT: Slim's most recent MM build was 03-29-2017 (they've been working on both for a few months now), so I will give that a try using EFIDroid and post the results.

Oh, and using Aroma with EFIdroid results in constant flickering on my device, just like you experienced on yours.
[Nexus 5 Android Development] lukss12:
My big problem is that I use the N5 as daily driver and the imposibilty of enabling adb. So I need to install MM as primary, then boot it for first time, enable adb and authorize my pc and then test it with adb enabled to get logs. I managed to enable adb editing build.prop and manually add my notebook's certificate to the ROM for adb but it seems like adb is not loading the certs for some reason ( may be it detects that the ROM is booting for first time). If someone knows how to enable adb without booting MM it would be helpful, but I tried all the methods that I could find in the web.
[Nexus 5 Android Development] phpbb3:
[MENTION=5361265]lukss12[/MENTION] have you had the opportunity to look into the Aroma flickering bug? I'd be willing to test for you
[Nexus 5 Android Development] Alexandroid99:
How would you go about flashing Plasma Mobile or Ubuntu Touch? You said you tested Plasma, but I have no idea how to install it.
[Nexus 5 Android Development] lukss12:
I needed to flash it manually because plasma upstream installer is broken... Plasma works because it uses the same mountpoints than android... but UTouch will not.. it needs a different ramdisk patching.
[Nexus 5 Android Development] Alexandroid99:
Then where do I get the images or a flashable zip if not from the installer? The link on the N5 plasma wiki page for a manual download seems to be broken. Could you give me a link or maybe even the files themselves? Much obliged! (Plus maybe a quick howto in case these aren't your standard twrp flashable zips, might even be worth putting on the OP)
[Nexus 5 Android Development] lukss12:
-First you need to create a new slot and flash a "stripped" AOSP from here http://neon.plasma-mobile.org/devices/hammerhead/hammerhead-20170110-083543.zip in that slot.

-Then the installer has a fatal bug because "tar" tool is not installed in that "stripped" AOSP - So you need to add it manually:

-Download tar for arm from here https://mocko.org.uk/projects/armbinaries/gnutar.gz

-Start TWRP for this new slot and copy tar binary using adb to /system/bin or other folder in $PATH

-Use adb to chmod 777 the tar bibary you just copied to enable it to be executed, then test it by executing tar (inside adb shell) (you should see tar's help notes)

-With TWRP booted for this slot and connected to PC run this script from wichever folder you want, it will download plasma rootfs files and hammerhead udev.rules under a "cache" folder and and attempt to install it using adb (ofc you need adb in your $PATH) https://github.com/plasma-phone-packaging/pm-flashtool/blob/master/flash-multirom

By the way Plasma Mobile is very far from usable... but if you want to test it... good luck :)
[Nexus 5 Android Development] KittenSauce:
I don't know if this has been documented or not, but AOSP 4.4.4 (KTU84P) works as a secondary ROM (my primary is LOS 14.1). However, it will only function with the "SELinux Force Permissive" setting disabled. Though, I can't get cellular data working; I try setting an APN, but it won't show up, no matter how many times I tap "save". Do you know what's up with that?

Thanks for compiling EFIDroid for our device; it certainly is a lot easier to use than MultiROM :)
[Nexus 5 Android Development] Redrield_:
Not sure if it's been said before, but I just gave this a try on my device running ResurrectionRemix 5.8.3. I only tried it twice, and it seemed to be 50/50. First time I tried it, it seemed to hang on the menu that said "Booting Android 7.1.2 (Internal)". On the second time it booted fine

Bit of feedback, not sure if I should direct at you or the original creator, but the UI in the actual boot menu is a bit slow when it comes to registering clicks from my volume/power buttons.
[Nexus 5 Android Development] IgelRM:
ElementalX Compatibility and Uninstaller question

Hello, this is really useful for rom testing, thanks for porting this.

I tested this with ElementalX 6.XX which doesn't work. 7.XX also doesn't work according to other users. I asked flair2 and he pointed out that we can use 8.XX on Marshmallow, which works nice. Maybe add that to the original post.

Also it would be nice if there was an uninstall method available.
[Nexus 5 Android Development] lukss12:
Uninstall option is there in the EFIDroid Manager app
[Nexus 5 Android Development] willyinpr4u:
Hey lukks12, I have a question stuck in my mind for a long time, and I result didn't want to bother you with it.

I was thinking if there's any chance of creating a back up from any of the secondary ROM and restore it as primary. Give me your opinion or your guess on this one.
[Nexus 5 Android Development] lukss12:
It should work, back up system, data, and kernel.

Remember that when TWRP is started for a secondary ROM the Internal Storage aka. sdcard is mocked so you will need to move your backup made from TWRP booted for secondary to be recognized by TWRP booted for primary.

In case you need more datailed process with full paths wait me to get home tonight
[Nexus 5 Android Development] willyinpr4u:
Thanks, no problem.
[Nexus 5 Android Development] willyinpr4u:
OK, this what I got so far, and I hope this work.

I created a back up ( everything but caches) from the ROM I want to swap with primary. Moved that back up to multiboot/data/media/0/TWRP/Backups.

I guess the next step would be to clean wipe the primary ROM ( Dalvik, System, Data, Cache) and then restore from the Backups.

Should that work?

EDIT: I've done it. Moving the backup didn't work, it never display when restoring. So I went with an USB. Created another backup and saved it to the USB drive, then after wiping primary, results from USB, and it worked.
[Nexus 5 Android Development] lukss12:
Great, multiboot/data/media/0 is where sdcard gets mounted to prevent a secondary ROM to wipe internal storage. When booting primary you need the backup to be placed in the internal storage root. It generates a bit of confusion sometimes but if you place it the correct way you can do it without the USB for sure.

Thanks for sharing your experience!
[Nexus 5 Android Development] KittenSauce:
I'm not exactly sure what's causing this, but while installing very recent builds of OpenGApps (for example, builds from yesterday), the phone reboots during the installation, and EFIDroid gives this error:

Can't allocate child memory: -9 0xfffffff7

I'm using TWRP 3.1.1-0 and the latest nightly of LineageOS, though this error occurred on the recent build of Oreo as well (which I suppose isn't a very good example :p ). It seems like this project is fairly dead, but I would at least like to know what's causing this issue. Perhaps it was just a faulty install?
[Nexus 5 Android Development] willyinpr4u:
Do you get the error while flashing Gapps using TWRP or do you get the error while using EFIDroid?
[Nexus 5 Android Development] KittenSauce:
While flashing GApps, the installation seems to error out, and the phone reboots. Afterwards, EFIDroid shows the error. I am not given a chance to do anything in TWRP, as the phone reboots while the flashing is happening; the GApps installation, of course, ceases to continue afterwards. Also, when trying to boot into LineageOS or AOSP Oreo directly after the error occurs, the boot animation plays without end.
[Nexus 5 Android Development] willyinpr4u:
I really have no idea what to say here, but to me it sounds as if there is a bug in TWRP. I could be wrong of course, but in other threads they were complaining about their devices randomly rebooting, an XDA member made a custom TWRP that fixes those bugs. Then again, I'm just speculating. But you lose nothing if you flash it, you could give it a try if you want.

The Oreo boot animation takes a long time, around 10 minutes, as said by Santsosh.
[Nexus 5 Android Development] KittenSauce:
When I uninstall EFIDroid (after manually flashing the boot.img and recovery.img), I am able to flash GApps once again. Perhaps TWRP is incompatible with EFIDroid? I doubt that's the case, but it's possible...

Do you happen to have a link to this custom TWRP? My phone randomly reboots as well. Though I don't believe it's a problem with TWRP; it only happens on LineageOS with the franco.kernel.

When booting LineageOS after the failed GApps install, instead of taking 1-2 minutes like it usually does, it was booting for approximately 6 minutes. I suppose I could've waited longer, but I doubt it would have had any effect.
[Nexus 5 Android Development] willyinpr4u:
I had some troubles with TWRP and EFIDroid in the past, but my problem was that I couldn't get into recovery because I was using TWRP from Multirom, which was not compatible. Right here in the thread OP help me how to fix it.

Here is the link to the modify TWRP.

https://www.androidfilehost.com/?fid=745425885120754390
[Nexus 5 Android Development] lukss12:
As I said before, EFIDroid is being rewrited by its main developer to be more friendly with non Qualcomm SoCs and with debugging, that's the reason why the project seems to be dead, but actually it's more alive than never before. This approach by EFIDroid developer is a big step into a general solution for multiboot.

However I will try to help you if I got some time (precious time -it's never enough-), please tell me the ROM you were trying to flash the Gapps on and the exact Gapps package. As I understand you failed flashing Gapps on LOS and not only Oreo, so I discard a ROM problem.

It seem like TWRP crashing, I guess due to being executed by EFIDroid because a normal ROM + TWRP setup is working for you.
[Nexus 5 Android Development] KittenSauce:
I do remember that the GApps for Oreo was the 8.0 Micro build from August 24th, though I do not exactly recall the build date for the 7.1.2 Nano GApps I had tried installing on LOS. It might have been the August 29th build. The LOS build was from August 29th as well, if I remember correctly (I was in the process from updating from the August 22nd build). It was the hammerhead build, not hammerheadcaf.
[Nexus 5 Android Development] KittenSauce:
I suppose we can rule out a faulty install, as I've reinstalled EFIDroid (to try out the new Oreo build), and I get the exact same error trying to install the exact same GApps package. Since I've tried this, however, I've updated TWRP to the beta version linked by someone above me (too lazy to check on mobile). Perhaps it was even a bug in OpenGApps, and has since been fixed. I'll back up my ROM, when I get the chance, and try updating to the latest LineageOS version (again).
[Nexus 5 Android Development] cyprien T:
can we ask under Linux?
[Nexus 5 Android Development] kmem:
Can any users who are familiar with both EFIDroid and MultiROM comment on the pros and cons of each?

I have been running MultiROM for quite some time and the only real issues that I have encountered is that secondary ROMs can't seem to pass safetyNet and that since development has ceased, new versions of the customized TWRP are unavailable. I also haven't had any luck installing NanoMod on a secondary ROM but this may be user error on my part.

I am especially interested if EFIDroid might solve the above issues.

I've been wanting to try EFIDroid since it was ported to the n5 but because this device is currently my daily driver and I have a pretty established setup, I haven't yet tried it.

It seems that development and interest in EFIDroid has slowed recently and I worry that soon it might die off like MultiROM has.

I would appreciate any input. Thanks in advance.
[Nexus 5 Android Development] lukss12:
EFIDroid is been rewrited, the release here uses LK microkernel to provide UEFI the components it needs to run. The new version drops LK completely and implements UEFI drivers for the differennt chipsets. It's a very hard work and that's why it is taking so much time for the dev however it is in a pretty advanced state by now. You can go efidroid.slack.com
[Nexus 5 Android Development] voyagerair:
I'm on DarkROM and not seeing anywhere to set Kernel to Permissive. Currently it's Enforce....any ideas pls help
[Nexus 5 Android Development] cubandanger05:
Any plans on porting this over to OP5T? Thanks.
[Nexus 5 Android Development] lukss12:
In EFIDroid move with volume buttons to the config wheel at the top, there you will find the force permissive option
[Nexus 5 Android Development] lukss12:
I don't have an OP5T and we are talking about a bootloader solution here, it is very difficult to port whitout the device. You may ask some OP5T dev when EFIDroids rewrite is finished
[Nexus 5 Android Development] voyagerair:
Thank you
[Nexus 5 Android Development] kmem:
Thank you for the information. I will definitely check out the slack channel. I assumed development was stalled because his original post hasn't had any updates in a long time.
[Nexus 5 Android Development] voyagerair:
THANK YOU VERY MUCH

My N5 now has 7 OS. All of the OS are Nougat.

Primary: ViperOS 7.1.1

Secondary: PureNexus

3rd OS: NX-AOSP

4th OS: EuclideanQualcomm

5th OS: crDroidROID

6th OS: AOSP Extended

7th OS: Simple AOSP (my kind of ROM = simplicity and functionality)

8th OS: RUNNING OUT of DISK SPACE (only 3 GB left)

Status: Rock Solid

Battery: Screen Off Time is about one day and 25 hours

Bugs: Flawless

I should've done/used this MULTIBOOT since day one.
[Nexus 5 Android Development] M Asad Khilji:
wow :D

i wanna taste oreo can you guide me to configure multirom

i'm on dark rom Nougat ;)
[Nexus 5 Android Development] voyagerair:
i am on all Nougat too

I heard multiboot doesn't officially support mismatch bootloaders yet.

some said it works, i tried Oreo ...can't boot.

OP has given guidline very clear ..step by step...
[Nexus 5 Android Development] linuxteddy:
I migrated from MultiROM to this, and I'm running Euclidian OS with Android 7.1.2 as internal and Lineage OS 15 as second. Don't know about the other way round, though.

LT