yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Android Development] SaschaElble:
None taken (*edit, I can have a dry sense of humor, translating that into "keyboard" doesn't work out so well) , efidroid is smooth sailing, many are making additions to the project, including porting devices. We have other 8974 devices that work. The only difference that is stopping us, is the Samsung display. It just takes the ONE right person to patch that up. Also, the dev has copies of the bootloader and device related files, and was there the whole time, with the team porting this device. Also, efidroid hasn't even been released yet. Don't give up hope just yet.

I even have the bootloader in ida, with a bunch of stuff figured out... if anyone who can fix the display wants a copy let me know... (This is where initial display support came from)

I even have a repo for the device online, and personal backups of more recent, but "testing this", "testing that" versions.
[Galaxy Note 3 Android Development] sub77:
hi. whats wrong with the display?
[Galaxy Note 3 Android Development] SaschaElble:
*edit: I see you are registered in the efidroid slack channel, my username there is Evo-Pulse

Well, how do I start...

Okay, I needed to write a GCDB Driver for lk, so I have at my disposal:

S6E3FA0 Panel CMD.dtsi (from source)

S6E3FA0 Panel VIDEO.dtsi (from source)

S6E3FA0 Panel CMD IDA* *This is a specially extracted lk driver from the note III's bootloader, aboot. Extracted by hand using IDA.

So, CMD and VIDEO DTSI, do not work in lk.... (black screen)

however.... CMD IDA version DOES work. But its broken... We can see the "penguin" but any attempt after the splashscreen to write to the framebuffer 0x03200000 produces no results on the screen. M1cha says we need a custom "flush" command for the framebuffer.

A little bit that I do know, we do appear to have a hardware based writebuffer for the framebuffer, (I could be wrong, this could just be software)

Also the CMD IDA driver does not agree with CMD.dtsi driver, some variables are not used, and the cmd on sequence changes a quite a bit between them. Both are supposed to init the display the same way.... All I can say is the driver that comes with the bootloader works more than the one dear old samsung gave us in sources.

I do realize that the dtsi files were intended to be used by a kernel, while the GCDB driver I extracted from the bootloader was meant for lk.

So basically, the only way I have been able to get this device to even show ANYTHING is by copying the lk driver from IDA/Aboot. But once it shows the lk splash screen it refuses to update the screen again.

PICS:
[Galaxy Note 3 Android Development] SaschaElble:
I'm making a 100$ bounty on whoever can fix our build for this device. Send the binary lk_nouefi_sideload and lk_sideload for verification of proof. Then payment of 100$ will be made for the source code fix you performed. I will provide all the initial device files as they currently are in this semi working state. Visit Evo-Pulse on efidroid's slack channel for support for initial setup. Or text/call me 903 900 3792.

I still haven't gave up, I just spent another weekend on it and I'm at my wits end as to why I cannot get this to work. Everything appears internally to function correctly... May the code compile for you!
[Galaxy Note 3 Android Development] trader418:
Deleted
[Galaxy Note 3 Android Development] immi:
Tons of RESPECT for you mate :good:
[Galaxy Note 3 Android Development] SaschaElble:
We shall see. MY WORK IS ONLY DEVICE SPECIFIC. I'm not taking any credit for efidroid itself.
[Galaxy Note 3 Android Development] SaschaElble:
Still working on display. So far it appears that LK shuts something down after display init, which is not allowing me to manually trigger the display to refresh after a memwrite to the framebuffer...
[Galaxy Note 3 Android Development] immi:
Any Luck with the graphics mate? :/
[Galaxy Note 3 Android Development] m11kkaa:
there's a 90% chance that the screen will work with the latest EFIDroid code. unfortunately [MENTION=1472608]SaschaElble[/MENTION] broke his phone so he won't be able to finish his port atm.
[Galaxy Note 3 Android Development] A.N.Droid:
great, i'm very interested in this project!
[Galaxy Note 3 Android Development] SaschaElble:
As soon as I find a reasonable lcd replacement (less than 100$) I will rebuild the project and test with results.
[Galaxy Note 3 Android Development] A.N.Droid:
do you have a donation address [MENTION=1472608]SaschaElble[/MENTION] ?
[Galaxy Note 3 Android Development] SaschaElble:
Updated build coming!

Thank you but I won't need it. I fit it into my budget. Will be here in a few days, and I will hopefully (no promises) update/recompile the new efidroid.

145$ for a brand new screen w/frame (Att/tmobile compatible frame), so I wont have to do any cleaning/adhesive work.

If the new build works the bounty will be removed. At this current time until the new screen comes in the bounty is on hold.
[Galaxy Note 3 Android Development] SaschaElble:
Great news!!! New screen came in and [MENTION=3530648]m11kkaa[/MENTION] fixed a small bug or two.

Everything appears to work, except touch of course.

Still learning about the multiboot aspect of it. I've gotten stock to boot, so here in the next day or two I will have a flash-able image and a tutorial for you guys!

A BIG THANK YOU TO m11kkaa!!!
[Galaxy Note 3 Android Development] SaschaElble:
This is BETA! Files have been uploaded, How to has been posted.

READ THE FIRST POST
[Galaxy Note 3 Android Development] A.N.Droid:
great! i would try but i don't have the tmo variant so a will wait and hope to see more of efidroid on note 3 in the future.

thanks for making it happen!
[Galaxy Note 3 Android Development] SaschaElble:
If you want to be a tester, I can add your variant and send you the updated files.

Open efidroid and send me a screenshot of the error. (it shows what deviceID it expects)
[Galaxy Note 3 Android Development] A.N.Droid:
thats nice!

i hope i can help in any way.

i do not know much about coding but i work in it-business, so you can expect at least basic understanding.

it's late in germany, where i live but i will have a look tomorrow and post the screenshot.

---------- Post added at 01:04 AM ---------- Previous post was at 12:51 AM ----------

the screenshot you need, is it from the efidroid manager app?

at least one of your assumptions are not met on my device: firmware.

i'm using the latest for hlte international,

also i use resurrection remix rom if that matters.
[Galaxy Note 3 Android Development] SaschaElble:
If you are running a custom rom that is a port of another phone, and it incorrectly reports the device id, a change needs to be made in the server files:

open the server zip, browse to

ota/master/

open devices.json in a text editor

edit the first item in the list:

"samsung/hlte" : "samsung/hlte"

the format is:

"samsung/DEVICEID" : "samsung/hlte"

DEVICEID is given by efidroid when opening it

So if you device is reported as hltenoble

"samsung/hltenoble" : "samsung/hlte"

Do not change spacing, do not try to add to the bottom of the list, just change the first one.
[Galaxy Note 3 Android Development] A.N.Droid:
theres something wrong.

missing seperator?
[Galaxy Note 3 Android Development] SaschaElble:
Edited

In respect to device compatibility see

Post #51

and

Post #55
[Galaxy Note 3 Android Development] A.N.Droid:
i thought that too, i had already tried thoose.

it doesn't work.

either i get the error in the first pic or when i add any character or remove the tmo line i get this:

pic removed

strange issue!
[Galaxy Note 3 Android Development] SaschaElble:
Should be fixed now.

I've updated the server_files to include SPR VZW TMO and HLTE (generic) variants

I've also updated the how to, making it much simpler.

[MENTION=5581598]A.N.Droid[/MENTION]

Can you remove the pictures from the last two pages to make things a bit cleaner?
[Galaxy Note 3 Android Development] A.N.Droid:
i still get:

invalid index 1, size is 1.

the deviceid, is it in build.prop?

there is no key named deviceid.

where to look for it?

i thought it would be:

ro.product.name=cm_hlte

and changed the devices.json to cm_hlte.

it didn't work.
[Galaxy Note 3 Android Development] SaschaElble:
The device id is given by efidroid, yours was samsung/hlte

I've since fixed it, and updated and changed the how to process. Please redownload the server files and the new app in playstore (simplehttpserver)

If you have root and want to change your /system/build.prop

find

ro.product.device=

and change it to any of these

hlte

hltetmo

hltespr

hltevzw
[Galaxy Note 3 Android Development] A.N.Droid:
i already re-downloaded the zip and used simplehttpserver but it does not work.

i looked into devices.json and saw that you added more devices. it just gives me the error i wrote above.

i was refering to post #51 where you talk about ports of roms that show wrong deviceid.

well, resurrection remix is not a port but cm based.

i assumed that efidroid reads the deviceid from the phone and that could be the problem.
[Galaxy Note 3 Android Development] SaschaElble:
try changing your build.prop as in the post above yours
[Galaxy Note 3 Android Development] A.N.Droid:
this key is not present in my build.prop.
[Galaxy Note 3 Android Development] SaschaElble:
try ro.rr.device=hlte
[Galaxy Note 3 Android Development] SaschaElble:
I've removed the efidroid manager from the how to, and uploaded another one in the how to. Please download this version and try

also, if it give you an error, press retry twice. Sometimes it does that.
[Galaxy Note 3 Android Development] A.N.Droid:
it's already present in my build.prop.

will try the nrw efidroid manager.

---------- Post added at 07:54 PM ---------- Previous post was at 07:45 PM ----------

parsingerror while trying to install the apk. could be a problem with my phone, not sure.

---------- Post added at 08:03 PM ---------- Previous post was at 07:54 PM ----------

dropped the apk into /data/app

and rebooted. it's installed now but giving me the same error.
[Galaxy Note 3 Android Development] SaschaElble:
That is just really weird, I see the app requested 2 files from the server, but somehow mangled the second request? 404 error (not found because that directory does not exist)

Meet me on slack? Its webbased if you dont want to install

Evo-pulse
[Galaxy Note 3 Android Development] A.N.Droid:
i registered 5 minutes ago but didn't get an email. maybe it needs more time.

---------- Post added at 09:17 PM ---------- Previous post was at 08:24 PM ----------

it works!

crazy, looks promising. hope to see more developement for efidroid in the future.

good work so far, thanks for sharing!
[Galaxy Note 3 Android Development] SaschaElble:
I would like to thank [MENTION=5581598]A.N.Droid[/MENTION] for helping me find an issue with the server files. Efidroid caches files from the server, so it went unnoticed.
[Galaxy Note 3 Android Development] anrydisappear:
Hi SacshaElble,and thanks for these tools.I have one problem,i want to revert back to normal boot,so what i've done:

i follow your way to installing,for short time i had problems with "no such file or directory"but i refresh simplehttpserver and the app run without mistake.Then i reboot the phone and on the screen shows one horizontal strip,but the phone won't boot.I right away flashing my device,the strange thing after flash it was that my apps are stay the same,they were not removed,however.I deleted efimanager with app.manager but on my sdcard(internal)have one folder UEFIESP,that folder i can't delete.So i installed again supersu and busybox because they are depends for twrp recovery,so have to i delete that folder(although she contains two files"partiton boot.img and "partition recovery.img)or not?I reading some methods on the first page in this thread how to back to normal boot,but for now the reaults=0

If you don't mine give me some advice?

note:Now i am with stock rom with stock recovery xxugng1 4.4.2

root and busybox are installed
[Galaxy Note 3 Android Development] m11kkaa:
if you hit the uninstall button, the app copies the contents of the UEFIESP back to the real partitions and deletes the partition_*.img files. It does not delete the UEFIESP directory or any of the multiboot directories because they may contain other important files.

flashing boot+recovery outside of EFIDroid's control(e.g. using stock's fastboot/odin flash, or using unpatched boot) is pretty much the same as uninstalling efidroid without deleting the partition_*img files.

All that means that you don't have to worry about any of that if you restores your boot+recovery partitions(either through the app or manually). If you want to free up some space you can delete the UEFIESP directory using a root file manager.

If you used the app's uninstall method and it failed for some reason(you even said the device didn't boot anymore) file a bug report on github after reproducing the bug yourself so we can be sure that it wasn't some random bug.
[Galaxy Note 3 Android Development] anrydisappear:
Thanks man,no place for worry about this.

keepyourself
[Galaxy Note 3 Android Development] immi:
[MENTION=1472608]SaschaElble[/MENTION] I'm trying to install this on Phronesis Note 7 Port (Marshmallow) V3.1, Device N9005(hlte), and Official LssKernel 3.7UX Fixed, twrp 2.8.7.0. Following are my issues...

1: I have two simplehttpserver apps from playsotre and don't know which one to use and how to use, but I have tried both (screenshots)

2: I don't know if I am typing a right command in terminal emulator (screenshot)

3: I faced an error in efidroid app and tried to rectify it but the error persists (screenshot)

1st of all I need to know whether if it is possible with my current rom and kernel and if it is possible then tell what I'm doing wrong and help me do it the right way. Thank You in advance ;)
[Galaxy Note 3 Android Development] m11kkaa:
in your 3rd screenshot I can see that the command failed(don't ignore failed commands ;) ), it's because you forgot a space between name and value.
[Galaxy Note 3 Android Development] immi:
All set and efidroid perfectly working on my current rom. Thanks mate. You (the original dev) and the owner of this thread are doing great work keep it up. I know I've just installed it and haven't tested it thoroughly, but the dev can add my rom and other stuff in OP for confirmed flash.
[Galaxy Note 3 Android Development] yyh991013:
Can't create a new OS image.....

通过我的 SM-N9300 上的 Tapatalk发言
[Galaxy Note 3 Android Development] A.N.Droid:
same here, i think efidroid for note 3 is not ready yet.
[Galaxy Note 3 Android Development] m11kkaa:
you probably need to clear data/cache of the app because I updated the app's internal busybox but I didn't add auto-updating yet.
[Galaxy Note 3 Android Development] A.N.Droid:
wow, i thought it wouldn't work right now because it's beta on n3 but...

thanks a lot!
[Galaxy Note 3 Android Development] Mroczny3:
Unfortunately i cannot create image in /data/media/0/

Dunno what's the problem.

Btw is there any native Ubuntu for note 3 with touchscreen support so it can boot with efidroid?

Thanks dev for your work its awesome!! :)

Wysłane z mojego SM-N930F przy użyciu Tapatalka
[Galaxy Note 3 Android Development] m11kkaa:
Does it show any specific error message?

Ubuntu is not supported by efidroid (yet), the option was just added when designing the UI and I forgot to remove it :D
[Galaxy Note 3 Android Development] Mroczny3:
Oh okay :D

It shows this:

Wysłane z mojego SM-N930F przy użyciu Tapatalka
[Galaxy Note 3 Android Development] m11kkaa:
are you using the latest version of the app? I though that I've fixed that kind of useless error messages.
[Galaxy Note 3 Android Development] Mroczny3:
Yup. Downloaded it about 15 minutes ago. and +1 for message beacuse it's hard to tell whats wrong :C
[Galaxy Note 3 Android Development] A.N.Droid:
so i tried to install a 2nd os but failed.

i rebooted to efidroid, selected twrp, then choose the generated image.

it just reboots back to efidroid.

---------- Post added at 09:39 PM ---------- Previous post was at 08:49 PM ----------

ok, this is obviously not rhe way it's meant to work but how? also i tried to replace the kernel in efidroid and got an error.
[Galaxy Note 3 Android Development] Mroczny3:
What about "can't find tagloader for type -1" error when i want to boot recovery? o.O
[Galaxy Note 3 Android Development] m11kkaa:
UEFI should show the error message, if not you may want to take a look at /proc/last_kmsg

do you have enough space, is the partition mounted readwrite, and do you have the permissions?(check dmesg for selinux denials).

I'm still working on improving the error messages but that you see this in first place is either a bug in the device port or the recovery image is invalid/unsupported.
[Galaxy Note 3 Android Development] A.N.Droid:
what are the correct steps for installing a second os?

i successfully created partition images but how do i mount it, how do i write anything to it.

i have no clue how and i found no documentation that explains it.

also i'm not sure what the recplacements section is for.

however, i can't set anything there.

btw. there is no last_kmsg, just kmsg.

will add screenshots when at home.
[Galaxy Note 3 Android Development] m11kkaa:
it sounds like you're trying to manually create multiboot ROM's. you should do that using the app.
[Galaxy Note 3 Android Development] A.N.Droid:
heres what i did:

1. open EFIDroidManager app

2. on the page "operating systems" i tap the + symbol

3. on the page "general" i choose a r/w location (/data/media/0/multiboot) and set a name

4. on the page "partitions" i reduce the size for data to 6gb.

5. sheme is set to "loopsystem + bind other"

6. i tap on the upper right symbol and the set of partitions is created correctly, no error here, animation shows 100% done.

i then assumed i had to continue in the bootloader.

1. i choose twrp

2. on the next screen i choose the newly created, empty system.

3. it reboots and takes me back to efidroid bootloader.

what am i doing wrong?
[Galaxy Note 3 Android Development] m11kkaa:
all that's correct(but step 4 is useless since changing the scheme resets all values and data doesn't have a size anyway).

does twrp boot for the internal ROM?
[Galaxy Note 3 Android Development] A.N.Droid:
yes, when choosing internal rom, twrp loads as usual.

when i select the other slot it does load efidroid again and shows an error.

something about "cant stat" and that the previous os could not be loaded.

i made a screenshot but i have no idea where efidroid stores it.
[Galaxy Note 3 Android Development] m11kkaa:
well you didn't mention the error before, that's very important information.

You can dump the screenshot using fastbootwrapper oem screenshot or you can just use fastboot oem getnvvar EFIDroidErrorStrPrev
[Galaxy Note 3 Android Development] A.N.Droid:
i was not able to pull the screenshot but here is the error:

EFIDroidErrorStrPrev: Can't stat '/multiboot/bootdev/media/0/multiboot/test/system.img'
[Galaxy Note 3 Android Development] m11kkaa:
can you check if the file exists?
[Galaxy Note 3 Android Development] A.N.Droid:
/multiboot exists but there is not bootdev folder inside.
[Galaxy Note 3 Android Development] m11kkaa:
that's just the runtime path, you have to check /data/media/0/multiboot
[Galaxy Note 3 Android Development] A.N.Droid:
this is what it looks like:

†removed 4 keeping thread clean†
[Galaxy Note 3 Android Development] yyh991013:
Guys which rom is this

通过我的 SM-N9300 上的 Tapatalk发言

---------- Post added at 02:58 PM ---------- Previous post was at 02:55 PM ----------

and my twrp still can't boot for my rom...

通过我的 SM-N9300 上的 Tapatalk发言
[Galaxy Note 3 Android Development] A.N.Droid:
it's not a rom, just an empty system.

i wanted to install phronesis note 7 port there but i'm having trouble.
[Galaxy Note 3 Android Development] Mroczny3:
Yes i have enough space, after deleting folder 2 or 3 times it created the images, but it did it in 2 seconds? Little too fast, but maybe they will be working, now the problem is recovery.

Dunno whats wrong with that, i'm using twrp 2.8.7.0 Tried to reflash it and reinstall efidroid but it did not work. I will try with twrp 3.xx but it's sad that 2.8.7.0 is not working for me, cause it has aroma support :/

//edit

Somehow, after some reinstalling, recovery started booting for stock rom, but another problem - when i want to boot recovery for secondary rom it just reboots phone

//edit2

About creating system, if i make system and data 1gb its working, but when system or data is more than 1gb it throws "error code was non zero"
[Galaxy Note 3 Android Development] A.N.Droid:
when i resize data and system to 1gb, i can see the twrp splashscreen for a few seconds. then the phone reboots and throws this error:

formatted ESP in multiboot mode
[Galaxy Note 3 Android Development] m11kkaa:
are you installing to a fat32 formatted sdcard?
[Galaxy Note 3 Android Development] Mroczny3:
/data/media/0

I know that fat has file size limit :D

Wysłane z mojego SM-N930F przy użyciu Tapatalka
[Galaxy Note 3 Android Development] A.N.Droid:
btw, when i install to my 128gb sd card, formatted with ext4, it is not showing up in the bootmanager.
[Galaxy Note 3 Android Development] m11kkaa:
how did you configure it, as portable or adoptable? the output of cat /proc/1/mountinfo would be very useful.
[Galaxy Note 3 Android Development] A.N.Droid:
portable.

here is the output:

†removed 4 keeping thread clean†
[Galaxy Note 3 Android Development] A.N.Droid:
tried usb.

the bootloader doesn't recognize it at all, no light blinking. no matter what fs.
[Galaxy Note 3 Android Development] m11kkaa:
don't expect usb(otg) support anytime soon(if ever).
[Galaxy Note 3 Android Development] SaschaElble:
Will do, thanks for testing and confirming!

I'm updating the ota server files to the latest version of efidroid. This may or may not fix any issues. (Give me 20 mins)
[Galaxy Note 3 Android Development] A.N.Droid:
[MENTION=1472608]SaschaElble[/MENTION] i made a mistake, the version of twrp is 3.0.2-1. sorry!

the part where you extract the server files.zip is missing in your guide.

there is something wrong also.

micha told me to choose twrp and then the slot to flash to. you wrote to choose the slot and then twrp.

to clearify, i can boot twrp internal but not for a slot.

[MENTION=5146687]immi[/MENTION] have you tried flashing to a slot or can you just boot your internal rom and twrp?
[Galaxy Note 3 Android Development] immi:
I haven't tried to flash other roms yet because I'm too bzy in my day job. I was able to boot into internal rom normally no issues. while I was unable to boot into my recovery in any ways (patched or unpatched). Due to shortage of time I didn't asked for any further assistance on that but I will surely be back when I have time for further tests.
[Galaxy Note 3 Android Development] PedroMarthon:
Well I installed it, but it did not let me boot into the system, it says: "can't find tagloader of type -1"
[Galaxy Note 3 Android Development] m11kkaa:
into your internal system or into a multiboot rom?
[Galaxy Note 3 Android Development] A.N.Droid:
what rom and recovery?

from page 1:

EFIDROID BOOT:

"can't find tagloader for type -1" - your recovery/rom is not supported
[Galaxy Note 3 Android Development] PedroMarthon:
I am on RR 5.7.3/twrp 3.0.2-1
[Galaxy Note 3 Android Development] A.N.Droid:
almost the same here but RR 5.7.4 using purify kernel 1.3.3
[Galaxy Note 3 Android Development] PedroMarthon:
Oh ok then, I will test it with CM14 and Ported TW ROMS and will reply soon :D
[Galaxy Note 3 Android Development] A.N.Droid:
to clearify:

are you talking about the internal rom that doesn't boot or were you able to flash anything to a slot?
[Galaxy Note 3 Android Development] SaschaElble:
You are correct, I've fixed the guide.

I would like to note that micha has told me that efidroid is not ready yet. I will continue to update/add to the guide just so everyone is one the same page. This has been a year on and off project for the note 3, and micha has been working on efidroid for years now. There are few regulars who contribute, the rest usually contribute fixes to get their device going and then dissapear. Other than that, its a one man team.