Here you go :good:
EFIDroid for the Samsung Galaxy Note 4/Note Edge (Snapdragon Variants)
- Thread starter abraha2d
- Start date
Here you go :good:
This seems fine, just like my setup. I don't know what's going on. Maybe @petbede could post his setup, and you guys could compare...
Honestly, without a logcat, I don't know where to start.
Sent from my Samsung Galaxy Note 4 using XDA Labs
It's working now but I had to set "Force selinux to permissive" in the EFIDroid boot loader settings. I tried with EmotionOS and LineageOS and both are working.
Thank you for your work :good:
Last edited:
No problem, but there's some deeper problem here... "Force selinux to permissive" is a sort of band-aid fix...
Maybe @m11kkaa can weigh in...
@abraha2d
Hi?
Everything is perfect on my side.
Just wanted to know, where does ROM boot from? If it's internal storage, then, I shouldn't be able to access internal storage on the secondary ROM. Or EFIDroid makes partition?
Is it okay to install heavy touchwiz ROM along with primary touchwiz and secondary AOSP?
How can I change stock name and icon on boot screen? Is there a way to add primary ROM option in app to change it's icon and name?
Well. No thanks is enough for your help. But again, Thank You!
Hi?
Everything is perfect on my side.
Just wanted to know, where does ROM boot from? If it's internal storage, then, I shouldn't be able to access internal storage on the secondary ROM. Or EFIDroid makes partition?
Is it okay to install heavy touchwiz ROM along with primary touchwiz and secondary AOSP?
How can I change stock name and icon on boot screen? Is there a way to add primary ROM option in app to change it's icon and name?
Well. No thanks is enough for your help. But again, Thank You!
The secondary ROMs are usually installed to the internal SD card (/data/media/0). You can install any combo of ROMs that you want. For the most part, they are completely separate. And no, as of now, there's no way to change the name/icon of the primary ROM.
Sent from my Samsung Galaxy Note 4 using XDA Labs
That worked for me too. Now I can boot fine lineage os after forcing selinux to permissive. Looks like the problem happens when you have the primary rom stock touchwiz which has selinux set to enforcing. The note 7 ports usually have selinux to permissive by default.
Sent from my SM-N910F using Tapatalk
I was also having issues with lineageOS not booting until I set it to permissive. Would be great if there was a way to set specific ROMs to permissive instead of all of EFIDroid.
As for migrating from DualBootPatcher I setup a new ROM through EFIDroid, moved the installed folders from MultiBoot folder to /data/media/0/multiboot/[secondary name] and edited the ini to make system a folder instead of a img. Works.
Also wouldn't it be possible to add a line to buildprop ie MultiBootName to set the name of primary. Just a thought.
Sent from my SM-N910W8 using Tapatalk
As for migrating from DualBootPatcher I setup a new ROM through EFIDroid, moved the installed folders from MultiBoot folder to /data/media/0/multiboot/[secondary name] and edited the ini to make system a folder instead of a img. Works.
Also wouldn't it be possible to add a line to buildprop ie MultiBootName to set the name of primary. Just a thought.
Sent from my SM-N910W8 using Tapatalk
Last edited:
That's weird, as I have completely stock (not even rooted) Samsung CQA1 as my primary (Selinux obviously enforcing)... @m11kkaa tells me this is a known issue, though...
Nice to hear that you migrated from DBP successfully... For some reason, I wasn't able to get bind-mount /system to work properly, so i ended up just moving the data folder to the EFIDroid multiboot folder, and reinstalling the ROM zip to repopulate /system...
For that last question, I don't know. You would be better off asking on the main thread. :good:
Sent from my Samsung Galaxy Note 4 using XDA Labs
I have tried installing EmotionOS on my N910T and TWRP also fails to mount/format the system partition. I tried all three different partition schemes (LoopSystem + BindOther, BindAll, LoopAll). The first one fails to format and mount the system partition both manually and by using the installation zip file for the ROM. The second one mounts and format manually, but fails with the ROM zip. The third one fails for all partitions (system, data, cache, etc) either manually or ROM zip. I noticed the installation fails on this line in the EmotionOS update-script
Code:
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");You don't need to format system partition.
Just let scheme be what it is, select internal storage for ROM installation and put ROM.zip on external SD.
After that when you reboot, select TWRP then Secondary ROM and then directly flash ROM.zip and GApps (if required).
Also, to mention, if it's your first time, try RR ROM (if available) or any other touchwiz ROM. I had problem after flashing EmotionOS... I mean bootloop.
I'm having this error on my n910v running the latest paulpizz. My build.prop is set to n910v and trtlevzw. I have tried installing, clearing data and cache, clearing the OTA override box, granting storage permission, installing the debug app, cleared data and cache and granted storage permission on the debug version as well.
Still no dice.
Thought maybe root cloak was preventing it from requesting root, but disabled it and I still have nothing. Any ideas?
As operator posted earlier, you can attach logcat to get quick response.
For logcat, you can use matlog app.
---------- Post added at 06:33 PM ---------- Previous post was at 06:30 PM ----------
Hello.
Head:
https://xdaforums.com/note-4/help/noob-friendly-question-t2866810/page189
for help related to TWRP, rooting and Odin.
Clear data, and try again... My server may have been down when you tried... It should be fine now...
Make sure your build.prop is trltevzw, not trtlevzw... This phone ain't a Verizon turtle... ?...
Sent from my Samsung Galaxy Note 4 using XDA Labs
Clear data, and try again... My server may have been down when you tried... It should be fine now...
Make sure your build.prop is trltevzw, not trtlevzw... This phone ain't a Verizon turtle... ?...
Oh. You're managing a server for that? Great!
Major update
Hey guys,
I've made some infrastructure changes which require some additional steps from your side to update. I've renamed the EFIDroid code name for the Note 4 from trltevzw to trlte, to better reflect the scope of this port (and possibly get this device as officially supported). I've also (partially) moved from hosting releases on my personal server, to hosting on GitHub.
Please update to the latest version by following these steps:
I will be releasing an updated version of the app soon, to complete the transition to GitHub hosting.
Hey guys,
I've made some infrastructure changes which require some additional steps from your side to update. I've renamed the EFIDroid code name for the Note 4 from trltevzw to trlte, to better reflect the scope of this port (and possibly get this device as officially supported). I've also (partially) moved from hosting releases on my personal server, to hosting on GitHub.
Please update to the latest version by following these steps:
- Clear the data of the EFIDroid Manager app. (Settings > Apps > EFIDroid Manager > Storage > Clear Data).
- Open the EFIDroid Manager app, and navigate to "Install/Update".
- Hit the orange "Install" button.
I will be releasing an updated version of the app soon, to complete the transition to GitHub hosting.
Some info i would like to know:
Will the next update fix the fact that the phone cannot charge while off because it will immediately go to EFIDroid? Or at leest put a screen off timeout so it prevents screen burn in.
Will the roms be totally separated, i still see some connection, is not a bad thing but just asking
Thanks for all the hard work you are putting into this buddy :good:
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
19I have ported EFIDroid (developed by @m11kkaa) to the Snapdragon variants of the Samsung Galaxy Note 4/Note Edge.
@m11kkaa's original EFIDroid thread here: https://xdaforums.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
Note: This has been tested with Samsung stock ROM, EmotionOS 7.1.1, and TWRP 3.0.2-0 on an SM-N910V/trltevzw. All other configurations are untested by me, but should work.
Confirmed working on:
- SM-N910V (trltevzw) (my device)
- SM-N910T (trltetmo) (thanks @viewsfromthepi)
- SM-N910G (trltedt) (thanks @Preet Juneja)
- SM-N910P (trltespr) (thanks @carlosggb)
- SM-N910W8 (trltecan) (thanks @d3multimedia)
- SM-N910F (trltexx) (thanks @cod_r) (possibly some issues with multiboot)
- SM-N915FY (tbltebtu) (thanks @jpearn)
- SM-N915F (tbltexx) (thanks @Juank2007)
I believe this works on all Snapdragon variants. If you're willing to test a variant not listed above, follow the instructions below, and post below if you had success, or if you encountered any issues.
Warning: There have been reports of the app failing to backup the boot/recovery partitions on other devices, leaving the device unable to boot to the OS and/or recovery. I have no way of testing whether this happens on the Note 4, so be ready with a working recovery/boot img on your computer...
I believe this issue does not affect the Note 4, as there have been successful installs with the app. However, I am leaving the related info on how to recover below, just in case this happens to one of you.
Installation
- Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work.
- Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
- Click the big orange Install button.
Post below with your variant/installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
- Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
- Under "Location", there should be a couple paths. Select the one containing "/data/media/0" if you want the new slot to reside on the internal SD card (recommended for speed). Select the one containing "/mnt/media_rw/" if you want the new slot to reside on the external SD card.
- You can give the slot a name/description by using the appropriate fields.
- Press the checkmark at the top right side of the screen to create the multiboot slot.
- Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
- Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
- Install all the zips you want on that slot.
- Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
Migrating from Dual Boot Patcher
Coming soon!
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img and recovery.img, right?)
This assumes you have fastboot properly setup.
- In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
- There should only be one entry in the Fastboot menu. Press the power key to select it.
- Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img> fastboot flash recovery <path/to/recovery.img> fastboot oem exit - In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
- Use the volume keys to navigate to "Reboot", then press the power key to select.
- If Maintenance Mode comes up, press the home button to reboot.
Known Bugs
- Aroma installers in TWRP may flicker, rendering them unusable.
Again, all credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
XDA:DevDB Information
EFIDroid, Kernel for the Verizon Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-19
Last Updated 2017-07-037Official Status!
Guys, good news! This port of EFIDroid has gained official status! The Note 4 will be included in the list of devices supported by the next official build.
I am not in control of the official builds, @m11kkaa is. Once he releases the next official build, you will be able to use the official EFIDroid Manager app from the Play Store to install/update official builds. I will release an announcement when that happens.
You will always be able to use my unofficial app to install my unofficial builds. I'll release new builds whenever a non-trivial change is made in the EFIDroid source code.4Major update
Hey guys,
I've made some infrastructure changes which require some additional steps from your side to update. I've renamed the EFIDroid code name for the Note 4 from trltevzw to trlte, to better reflect the scope of this port (and possibly get this device as officially supported). I've also (partially) moved from hosting releases on my personal server, to hosting on GitHub.
Please update to the latest version by following these steps:
- Clear the data of the EFIDroid Manager app. (Settings > Apps > EFIDroid Manager > Storage > Clear Data).
- Open the EFIDroid Manager app, and navigate to "Install/Update".
- Hit the orange "Install" button.
I will be releasing an updated version of the app soon, to complete the transition to GitHub hosting.4Thanks! So this allows you to dual boot 2 different roms?
One is primary installed as normal, i take. Now the second one, how is it installed? How is it saved?
Thank you. I'm just curious. This sounds convenient to have your daily driver as primary, and be able to test other roms without constantly backing up and restoring. Am i correct in thinking this way?
EFIDroid allows you to boot as many different ROMs as you want. You're only limited by the space on your phone.
The secondary ROMs can either be stored on the internal SD card (emulated on the data partition in our case), or external SD card. I wouldn't recommend the external SD though, as it is usually slower than the internal SD.
To install a secondary ROM, use the EFIDroid Manager to create a new OS slot (the plus button at the bottom right of the main screen). Then, reboot, and when EFIDroid shows up, select TWRP, and then select the newly created OS slot. Wipe the system partition in TWRP (to initialize it), and then install whatever ROM/Gapps zip you want.
EDIT: If you're using Dual Boot Patcher currently, there's a slightly involved method to migrate your setup to EFIDroid without loss of data. If anyone's interested, I might put up a how to.2
@cod_r, @goolby, @abraha2d,
It is working for me and my device is N910F.
I am using Dr Ketan ROM M12 by @dr.ketan as my primary.
I have used EmotionOS dated March 20, 2017 by @hsbadr as my secondary.
I have also used UNOFFICIAL LineageOS 14.1 by @jef_00 as my secondary.
I've got no issue at all...
EFIDroid for the Samsung Galaxy Note 4 Snapdragon Variants is working like a charm on my Samsung Note 4 N910F
Thanks so very highly much @abraha2d :good: :good: :good:
