Google it
Sent using some kind of device I modified
You're not helpful.
And you are being a jerk.
I'd like you to point out where someone else asked the same question as I did? Right never happened.What would you like me to do google it my self then copy and paste the definition for you. Your asking me what something is you don’t understand then try to find out. If you have no clue what edl 9008 mode is then you may want to read up about it before trying it. Im not being unhelpful I have many people ask the same questions over and over when the answer can be found with a simple search. Here is what a google search found for me
https://www.96boards.org/documentation/consumer/guides/qdl.md.html
Sent using some kind of device I modified
And you are being a jerk.
elliwigy, I did Google it before I asked my question. I did not understand the results and explanations I found, so I came here and asked.
Maybe you don't understand everyone that comes here is on your level on knowledge and they way you treat people has an effect on this forum of whether new people feel welcomed to asking questions or not.
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
I'd like you to point out where someone else asked the same question as I did? Right never happened.
I did "Google it" before your unhelpful first reply. But I did't understand the answers. SO If it bothers you so much to reply to people like me then you should have simply ignored my question instead of being rude.
So any time soon we can have a root for s10 on snapdragon.. goodto add, eng bl doesnt do much of anything as was the case on s8 s8+ and even s10+ (yes i got eng bl on s10+).. s10+ has a lot more security however so eng bl will work but vbmeta doesnt allow it to boot even with stock
of course it allows flashing unsigned img, how u think flashing a system.img works and getting safestrap? they modify the system.img therefore breaking sig..
edl needs the signed programmer and properly formatted xmls.. on n8 you can then flash anything pretty much..
problem is it doesnt disable secure boot.. so unsigned boot.img for example will flash but will not boot as it is checked by secure boot process whereas system isnt on n950u allowing to boot modified system..
reason why pie root is difficult on n8 is bcuz theres no pie combo which would have permissive boot.img so pie needs to use stock boot.img which will block root stuff bcuz of selinux enforcing
but yes, ur post is correct
I'm pretty sure this thread has been abandoned since it's been over a month with no work or replies of any kind. I think everyone has moved to bigger and better devices.
Sent from my Pixel 3 XL
Maybe has more than one device like many people[emoji6][emoji106]
Sent from my SM-N950U using Tapatalk
You do realize Note 8s are already 2 generations behind and most people have moved on to newer devices right? I do have multiple devices including my beloved Note8. However, after using it for a while, I moved on. I still wish a solution would be found if anything just to defy Samsung. After the frustration with Samsung's locked bootloader and limited root, I went to a pixel 3XL which has served me well so far. I periodically check here for updates but notice the lack of development which I attribute (perhaps erroneously) to developers moving on.thats a pretty bold statement coming from someone with a Pixel 3
Because his signature says Pixel could mean he posted with that. Easy cowboy..lol
Hey Mike...things never change bro...[emoji1787][emoji23]Maybe has more than one device like many people[emoji6][emoji106]
Sent from my SM-N950U using Tapatalk
Instant Optimizing Embedded System Using BusyBox
[SIZE="5"][COLOR="Green"]#1[/COLOR][/SIZE][COLOR="RoyalBlue"] it sets up the command line vairable that gets passed to the kernel. Same as commandline in android boot.img.[/COLOR]
bootargs=root=/dev/mmcblk1p1 rw rootwait console=tty0 console=ttyMSM0,115200n8 rootfs=ext4 noinitrd selinux=0
[SIZE="5"][COLOR="SeaGreen"]#2[/COLOR][/SIZE] [COLOR="DeepSkyBlue"]used by u-boot to know what addresses to load the kernel and device tree too.
"bootm" is the command that executes the loading.
[COLOR="red"][SIZE="5"]"ext4load" [/SIZE][/COLOR]and "[SIZE="5"][COLOR="Red"]bootm[/COLOR][/SIZE]" -->> Functions that execute from the loaded u-boot.bin (important)
[/COLOR]
bootcmd=ext4load mmc 1:1 ${kernel_addr_r} /boot/uImage; ext4load mmc 1:1 ${fdt_addr_r} /boot/apq8016-sbc.dtb; bootm ${kernel_addr_r} - ${fdt_addr_r}
[COLOR="SeaGreen"][SIZE="5"]#3[/SIZE][/COLOR] [COLOR="RoyalBlue"]the uenvcmd is executed by the u-boot.bin and is just the variable that is equal to the bootcmd.[/COLOR]
uenvcmd=run bootcmd
U-Boot implements tftp command to download the kernel and filesystem (in case of ramdisk) images to SDRAM. You can then choose to directly boot the newly downloaded images or write them to non-volatile memory using U-Boot commands and then copy the the images to SDRAM from this memory for subsequent boots.
http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot
Common Examples
u-boot.bin
[COLOR="Red"][SIZE="5"]A common example of using the tftp command is loading up a U-Boot binary to test:[/SIZE][/COLOR]
bfin> tftp 0x1000 u-boot.bin
Using Blackfin EMAC device
TFTP from server 192.168.0.2; our IP address is 192.168.0.15
Filename 'u-boot.bin'.
Load address: 0x1000
Loading: ############################
done
Bytes transferred = 141016 (226d8 hex)
bfin> go 0x1000
## Starting application at 0x00001000 ...
Here we loaded the u-boot.bin file into external memory at address 0x1000. Then we proceeded to simply start executing at that address.