PineNote Development/Booting Linux - Revision history

Mweigand: Add note that this page only refers to batch 1

2024-11-26T10:42:00Z

Add note that this page only refers to batch 1

← Older revision		Revision as of 10:42, 26 November 2024
Line 1:		Line 1:
			{{Note\|This page is only relevant for the first batch of PineNotes, sold in 2021/2022! Batch 2 (2024) PineNote come with linux pre-flashed!}}

	To boot Linux, the stock U-Boot has to be patched.		To boot Linux, the stock U-Boot has to be patched.

Fxc: corrections

2023-01-13T16:59:22Z

corrections

← Older revision		Revision as of 16:59, 13 January 2023
Line 12:		Line 12:
	$ chmod o+x pinenote-uboot-envtool.py		$ chmod o+x pinenote-uboot-envtool.py

	2. Write your U-Boot partition to an ~~img~~ file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>		2. Write your U-Boot partition to an image file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>

	3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>		3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
Line 22:		Line 22:
	# Open <code>boot-menu.patch</code> to get a feel for how that works		# Open <code>boot-menu.patch</code> to get a feel for how that works

	5. The boot-menu.patch makes assumptions about where your ~~linux~~ partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.		5. The boot-menu.patch makes assumptions about where your Linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.

	6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>		6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>
Line 32:		Line 32:
	8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>		8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>

	9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to ~~android~~. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.		9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to Android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.

	10. Reboot into Linux		10. Reboot into Linux

Fxc: code for commands

2023-01-13T16:40:17Z

code for commands

← Older revision		Revision as of 16:40, 13 January 2023
Line 26:		Line 26:
	6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>		6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>

	{{Info\|Note: Might fail with the following error: ~~<code>~~patch: **** unexpected end of file in patch at line 27~~</code>~~. In that case applying the patch manually is the solution.}}		{{Info\|Note: Might fail with the following error: "''patch: **** unexpected end of file in patch at line 27''". In that case applying the patch manually is the solution.}}

	7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>		7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>

Fxc: +cat

2023-01-12T20:49:04Z

+cat

← Older revision		Revision as of 20:49, 12 January 2023
Line 40:		Line 40:
	# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]		# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
	# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]		# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]

			[[Category:PineNote]]

Fxc: /* Steps to patch U-Boot */ Not suited as list

2023-01-12T20:27:14Z

Steps to patch U-Boot: Not suited as list

← Older revision		Revision as of 20:27, 12 January 2023
Line 4:		Line 4:

	== Steps to patch U-Boot ==		== Steps to patch U-Boot ==
	# Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the Python tool]:
			1. Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the Python tool]:

	$ mkdir pinenote-uboot && cd pinenote-uboot		$ mkdir pinenote-uboot && cd pinenote-uboot
	$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch		$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch
	$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py		$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py
	$ chmod o+x pinenote-uboot-envtool.py		$ chmod o+x pinenote-uboot-envtool.py
	# Write your U-Boot partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>
	# Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>		2. Write your U-Boot partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>
	# Poke around the files (or skip this if you don't like to learn...):
	## Open <code>uboot.env</code> -- see, it's just text at this point!		3. Extract the environment: <code>./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
	## Open <code>boot-menu.patch</code> to get a feel for how that works
	# The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.		4. Poke around the files (or skip this if you don't like to learn...):
	# Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>
	#* Note: Might fail with the following error: <code>patch: **** unexpected end of file in patch at line 27</code>. In that case applying the patch manually is the solution.		# Open <code>uboot.env</code> -- see, it's just text at this point!
	# Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>
	# Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>		# Open <code>boot-menu.patch</code> to get a feel for how that works
	# At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.
	# Reboot into Linux		5. The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.

			6. Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>

			{{Info\|Note: Might fail with the following error: <code>patch: **** unexpected end of file in patch at line 27</code>. In that case applying the patch manually is the solution.}}

			7. Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>

			8. Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>

			9. At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.

			10. Reboot into Linux

	== Sources and further reading ==		== Sources and further reading ==

Fxc: style fix

2023-01-12T20:16:48Z

style fix

← Older revision		Revision as of 20:16, 12 January 2023
Line 1:		Line 1:
	To boot ~~linux~~, we need to patch stock uboot. I used [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f charasyn's method], based off work from Dorian as credited in the script. We'll use the script to pull the uboot environment out of the stock ~~uboot partition. We'll then apply the patch, recreate the image, add a configuration file, and flash the new image~~ to ~~the PineNote~~.		To boot Linux, the stock U-Boot has to be patched.

	== Steps to patch ~~uboot~~ ==		Here the method from [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f charasyn] is used, based of work from Dorian as credited in the script. We'll use the script to pull the U-Boot environment out of the stock U-Boot partition. We'll then apply the patch, recreate the image, add a configuration file, and flash the new image to the PineNote.
	~~<ol>~~
	~~<li>~~ Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the ~~python~~ tool]:		== Steps to patch U-Boot ==
	~~<pre>~~		# Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the Python tool]:
	$ mkdir pinenote-uboot && cd pinenote-uboot		$ mkdir pinenote-uboot && cd pinenote-uboot
	$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch		$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/boot-menu.patch -o boot-menu.patch
	$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py		$ curl https://gist.githubusercontent.com/charasyn/206b2537534b6679b0961be64cf9c35f/raw/cc513998a36fac0cea266260e3ca3e64abfe3696/pinenote-uboot-envtool.py -o pinenote-uboot-envtool.py
	$ chmod o+x pinenote-uboot-envtool.py		$ chmod o+x pinenote-uboot-envtool.py
	~~</pre>~~		# Write your U-Boot partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>
	~~</li>~~		# Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>
	~~<li>~~ Write your ~~uboot~~ partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code~~></li~~>		# Poke around the files (or skip this if you don't like to learn...):
	~~<li>~~ Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code~~></li~~>		## Open <code>uboot.env</code> -- see, it's just text at this point!
	~~<li>~~ Poke around the files (or skip this if you don't like to learn...):~~</li>~~		## Open <code>boot-menu.patch</code> to get a feel for how that works
	~~<ol>~~		# The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your Linux boot partition lives.
	~~<li>~~ Open <code>uboot.env</code> -- see, it's just text at this point!~~</li>~~		# Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>
	~~<li>~~ Open <code>boot-menu.patch</code> to get a feel for how that works~~</li>~~		#* Note: Might fail with the following error: <code>patch: **** unexpected end of file in patch at line 27</code>. In that case applying the patch manually is the solution.
	~~</ol>~~		# Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>
	~~<li>~~ The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your ~~linux~~ boot partition lives.~~</li>~~		# Write the image to the boot partition from the PineNote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>
	~~<li>~~ Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code~~></li~~>		# At this point, restarting your system will boot into Android -- this is because the patched U-Boot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot Android or Linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for Linux.
	~~<ol>~~		# Reboot into Linux
	~~<li>This doesn't work for me for some reason~~:
	<~~pre~~>
	~~$ patch uboot.env boot-menu.patch~~
	~~patching file env.original~~
	~~Hunk #3 FAILED at 24.~~
	~~patch unexpectedly ends in middle of line~~
	patch: **** unexpected end of file in patch at line 27
	</~~pre~~>
	~~I couldn't figure out what it's complaining about here, so I ended up~~ applying the patch manually. ~~It's pretty straight-forward.</li>~~
	~~</ol>~~
	~~<li>~~Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code~~></li~~>
	~~<li>~~ Write the image to the boot partition from the ~~pinenote~~: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code~~></li~~>
	~~<li>~~ At this point, restarting your system will boot into Android -- this is because the patched ~~uboot~~ we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot ~~android~~ or ~~linux~~, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for ~~linux~~.~~</li>~~
	~~<li>~~ Reboot into ~~linux and go "wow"</li>~~
	~~</ol>~~

	== Sources and further reading ==		== Sources and further reading ==
	# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]		# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
	# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]		# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
	# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing ~~uboot~~.]		# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing U-Boot.]

Aarondabomb: /* Steps to patch uboot */

2022-11-05T17:44:36Z

Steps to patch uboot

← Older revision		Revision as of 17:44, 5 November 2022
Line 32:		Line 32:
	</ol>		</ol>
	<li>Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code></li>		<li>Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code></li>
	<li> Write the image to the boot partition: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code></li>		<li> Write the image to the boot partition from the pinenote: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code></li>
	<li> At this point, restarting your system will boot into Android -- this is because the patched uboot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot android or linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for linux.</li>		<li> At this point, restarting your system will boot into Android -- this is because the patched uboot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot android or linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for linux.</li>
	<li> Reboot into linux and go "wow"</li>		<li> Reboot into linux and go "wow"</li>

Aarondabomb: /* Steps to patch uboot */

2022-11-05T17:19:47Z

Steps to patch uboot

← Older revision		Revision as of 17:19, 5 November 2022
Line 11:		Line 11:
	</pre>		</pre>
	</li>		</li>
	<li> Write your uboot partition to ~~disk~~: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code></li>		<li> Write your uboot partition to an img file: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code></li>
	<li> Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code></li>		<li> Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code></li>
	<li> Poke around the files (or skip this if you don't like to learn...):</li>		<li> Poke around the files (or skip this if you don't like to learn...):</li>
Line 36:		Line 36:
	<li> Reboot into linux and go "wow"</li>		<li> Reboot into linux and go "wow"</li>
	</ol>		</ol>

	== Sources and further reading ==		== Sources and further reading ==
	# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]		# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
	# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]		# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
	# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing uboot.]		# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing uboot.]

Aarondabomb: v1

2022-08-27T21:13:30Z

← Older revision		Revision as of 21:13, 27 August 2022
Line 2:		Line 2:

	== Steps to patch uboot ==		== Steps to patch uboot ==
			<ol>
	# Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the python tool]:		<li> Get the [https://gist.github.com/charasyn/206b2537534b6679b0961be64cf9c35f patch and the python tool]:
	<pre>		<pre>
	$ mkdir pinenote-uboot && cd pinenote-uboot		$ mkdir pinenote-uboot && cd pinenote-uboot
Line 10:		Line 10:
	$ chmod o+x pinenote-uboot-envtool.py		$ chmod o+x pinenote-uboot-envtool.py
	</pre>		</pre>
	# Write your uboot partition to disk: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code>		</li>
	# Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code>		<li> Write your uboot partition to disk: <code>dd if=/dev/mmcblk0p1 of=~/uboot.img</code></li>
	# Poke around the files (or skip this if you don't like to learn...):		<li> Extract the environment: <code> ./pinenote-uboot-envtool.py extract uboot.img uboot.env</code></li>
	## Open <code>uboot.env</code> -- see, it's just text at this point!		<li> Poke around the files (or skip this if you don't like to learn...):</li>
	## Open <code>boot-menu.patch</code> to get a feel for how that works		<ol>
	# The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your linux boot partition lives.		<li> Open <code>uboot.env</code> -- see, it's just text at this point!</li>
	# Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code>		<li> Open <code>boot-menu.patch</code> to get a feel for how that works</li>
	## This doesn't work for me for some reason:		</ol>
			<li> The boot-menu.patch makes assumptions about where your linux partition lives. Specifically, it will look at partition 0x11 (which is 17 in decimal). Change this in boot-menu.patch to reflect where your linux boot partition lives.</li>
			<li> Apply boot-menu.patch: <code>patch uboot.env boot-menu.patch</code></li>
			<ol>
			<li>This doesn't work for me for some reason:
	<pre>		<pre>
	$ patch uboot.env boot-menu.patch		$ patch uboot.env boot-menu.patch
Line 25:		Line 29:
	patch: **** unexpected end of file in patch at line 27		patch: **** unexpected end of file in patch at line 27
	</pre>		</pre>
	I couldn't figure out what it's complaining about here, so I ended up applying the patch manually. It's pretty straight-forward.		I couldn't figure out what it's complaining about here, so I ended up applying the patch manually. It's pretty straight-forward.</li>
	# Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code>		</ol>
	# Write the image to the boot partition: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code>		<li>Rewrite the new environment to the image: <code>./pinenote-uboot-envtool.py insert uboot.img uboot.env uboot-patched.img</code></li>
			<li> Write the image to the boot partition: <code>dd if=~/uboot-patched.img of=/dev/mmcblk0p1</code></li>
	At this point, restarting your system will boot into Android -- this is because the patched uboot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot android or linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android.		<li> At this point, restarting your system will boot into Android -- this is because the patched uboot we've just created looks for <code>/boot/which_os.txt</code> to determine whether to boot android or linux, and since it can't find this file (we haven't made it yet), the bootloader defaults to android. Create that file on the same boot partition you specified in the boot-menu.patch file, placing an <code>l</code> in the file for linux.</li>
			<li> Reboot into linux and go "wow"</li>
	Create that file on the same boot partition you specified in the boot-menu.patch file, placing an `l` in the file for linux.		</ol>

	== Sources and further reading ==		== Sources and further reading ==
	[https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]		# [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
	[https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]		# [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]
			# [https://matrix.to/#/!QtTzSRYMuozjbOQkzJ:matrix.org/$bVBxdD3E01da7w4LRm45-mwbw_jPk6CrJTQWGMG3B2I?via=matrix.org&via=kde.org&via=tchncs.de This conversation in matrix between pgwipeout, vveapon, and pinenewb about flashing uboot.]

Aarondabomb: almost done

2022-08-27T21:00:22Z

almost done

@@ Line 14: / Line 14: @@
 # Poke around the files (or skip this if you don't like to learn...):
 ## Open <code>uboot.env</code> -- see, it's just text at this point!
-## Open <code>uboot.
+## Open <code>boot-menu.patch</code> to get a feel for how that works
 == Sources and further reading ==
 [https://u-boot.readthedocs.io/en/latest/board/rockchip/rockchip.html U-boot with rockchip docs]
 [https://stackoverflow.com/questions/31244862/what-is-the-use-of-spl-secondary-program-loader Helpful stack overflow to learn a bit about the boot process/terminology]