mirror of
https://source.denx.de/u-boot/u-boot.git
synced 2026-05-05 04:36:13 +02:00
doc: board: tegra: improve documentation
Remove redundant chapters, clarify and reword confusing sections. Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
This commit is contained in:
Svyatoslav Ryhel
parent
eb00c71050
commit
ef1501932b
@ -5,7 +5,8 @@ U-Boot for the Acer Iconia Tab A500
|
||||
|
||||
``DISCLAMER!`` Moving your Acer Iconia Tab A500 to use U-Boot assumes
|
||||
replacement of the vendor Acer bootloader. Vendor Android firmwares will no
|
||||
longer be able to run on the device. This replacement IS reversible.
|
||||
longer be able to run on the device. This replacement IS reversible if you have
|
||||
backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -13,6 +14,7 @@ Quick Start
|
||||
- Build U-Boot
|
||||
- Process U-Boot
|
||||
- Flashing U-Boot into the eMMC
|
||||
- Flashing U-Boot into the eMMC with NvFlash
|
||||
- Boot
|
||||
- Self Upgrading
|
||||
|
||||
@ -36,61 +38,45 @@ in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
to recover the device in case of a failed update. You need to know your device
|
||||
individual SBK to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev a500
|
||||
$ ./re-crypt.py --dev a500 --sbk <your sbk> --split
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
where SBK has next form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it either by pre-loading vendor bootloader into RAM with the nvflash.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ nvflash --setbct --bct picasso.bct --configfile flash.cfg --bl bootloader.bin
|
||||
--sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --sync # replace with your SBK
|
||||
$ nvflash --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and ``volume up`` buttons on
|
||||
turned off tablet connected to the host PC. Host PC should detect APX USB
|
||||
device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./utils/nvflash_t20 --setbct --bct ./bct/picasso.bct --configfile ./utils/flash.cfg
|
||||
--bl u-boot-dtb-tegra.bin --sbk <your sbk> --sync
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -104,6 +90,37 @@ After, on host PC, do:
|
||||
|
||||
Device will reboot.
|
||||
|
||||
Flashing U-Boot into the eMMC with NvFlash
|
||||
------------------------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
This method is discouraged and is used only if fastboot commands from previous
|
||||
chapter failed with ``Writing '0.1' FAILED (remote: 'too large for partition')``
|
||||
error. This error means that your tablet has 512 Kb boot0/boot1 partitons which
|
||||
is too small to contain U-Boot image as the minimum boot partition size must
|
||||
me 1 MB. This situation can be workarounded but self-update will not work and
|
||||
flashing to eMMC will wipe U-Boot. This should not be a big issue since installing
|
||||
OS on microSD is a preferred method anyway.
|
||||
|
||||
This method involves use of Nv3p. Nv3p is a custom Nvidia protocol used to
|
||||
recover bricked devices. Devices can enter it by pre-loading vendor bootloader
|
||||
into RAM with the nvflash.
|
||||
|
||||
With Nv3p, ``repart-block.bin`` is used (produced by re-crypt without ``--split``
|
||||
key). It contains BCT and a bootloader in encrypted state in form, which can just
|
||||
be written RAW at the start of eMMC. Place your ``repart-block.bin`` and vendor
|
||||
bootloader with name ``bootloader.bin`` into fusee-tools folder and run:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./utils/nvflash_t20 --setbct --bct ./bct/picasso.bct --configfile ./utils/flash.cfg
|
||||
--bl ./bootloader.bin --sbk <your sbk> --sync
|
||||
$ ./utils/nvflash_t20 --resume --rawdevicewrite 0 512 ./repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Boot
|
||||
----
|
||||
|
||||
@ -113,8 +130,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,8 @@ U-Boot for the ASUS/Google Nexus 7 (2012)
|
||||
|
||||
``DISCLAMER!`` Moving your ASUS/Google Nexus 7 (2012) to use U-Boot assumes
|
||||
replacement of the vendor ASUS bootloader. Vendor android firmwares will no
|
||||
longer be able to run on the device. This replacement IS reversible.
|
||||
longer be able to run on the device. This replacement IS reversible if you
|
||||
have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -39,65 +40,45 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update. You need to know your
|
||||
tablet's individual SBK to continue.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update. You need to know your device
|
||||
individual SBK to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev grouper --sbk <your sbk>
|
||||
$ ./re-crypt.py --dev grouper --sbk <your sbk> --split # or --dev tilapia
|
||||
|
||||
where SBK has next form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with the Fusée Gelée.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/grouper.bct -b android_bootloader.bin
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device. Note that if you have cellular version,
|
||||
use ``tilapia.bct``.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and ``volume up`` buttons on
|
||||
turned off tablet connected to the host PC. Host PC should detect APX USB
|
||||
device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/grouper.bct --b u-boot-dtb-tegra.bin # or tilapia.bct
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -120,8 +101,8 @@ bootmenu. Bootmenu contains entries to mount eMMC as mass storage, fastboot,
|
||||
reboot, reboot RCM, poweroff, enter U-Boot console and update bootloader (check
|
||||
the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,8 @@ U-Boot for the ASUS Eee Pad Transformer device family
|
||||
|
||||
``DISCLAMER!`` Moving your ASUS Eee Pad Transformer/Slider to use U-Boot
|
||||
assumes replacement of the vendor ASUS bootloader. Vendor Android firmwares
|
||||
will no longer be able to run on the device. This replacement IS reversible.
|
||||
will no longer be able to run on the device. This replacement IS reversible
|
||||
if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -40,61 +41,46 @@ in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
to recover the device in case of a failed update. You need to know your device
|
||||
individual SBK to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev tf101
|
||||
$ ./re-crypt.py --dev tf101v1 --split # or tf101v2 or sl101 as --dev
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it either by using ``wheelie`` with the correct ``blob.bin`` file or by
|
||||
pre-loading vendor bootloader with the Fusée Gelée.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ wheelie -1 --bl bootloader.bin --bct tf101.bct --odm 0x300d8011 || break
|
||||
$ nvflash --resume --rawdevicewrite 0 2048 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and ``volume up`` buttons on
|
||||
turned off tablet connected to the host PC. Host PC should detect APX USB
|
||||
device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./utils/nvflash_t20 --setbct --bct ./bct/<dev>.bct --configfile ./utils/flash.cfg
|
||||
--bl u-boot-dtb-tegra.bin --sbk <your sbk> --sync
|
||||
|
||||
Where <dev> is your devie codename, either ``tf101`` or ``sl101`` and <your sbk> is SBK
|
||||
of your device in the form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -117,8 +103,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,7 @@ U-Boot for the ASUS Transformer device family
|
||||
|
||||
``DISCLAMER!`` Moving your ASUS Transformer to use U-Boot assumes replacement
|
||||
of the vendor ASUS bootloader. Vendor Android firmwares will no longer be
|
||||
able to run on the device. This replacement IS reversible.
|
||||
able to run on the device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -45,65 +45,51 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update. You need to know your
|
||||
tablet's individual SBK to continue.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update. You need to know your device
|
||||
individual SBK to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev tf201 --sbk <your sbk>
|
||||
$ ./re-crypt.py --dev tf201 --sbk <your sbk> --split
|
||||
|
||||
where SBK has next form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
``NOTE!`` If you have TF700T it may have different sizes of boot0/boot1 partitions,
|
||||
re-crypt sets default boot partition size to 2MB and if you have different size
|
||||
add ``--bootsize`` key with yout boot partition size in bytes to the command.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with the Fusée Gelée.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/tf201.bct -b android_bootloader.bin
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device. Note that you should adjust bct file
|
||||
name according to your device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and ``volume up`` buttons on
|
||||
turned off tablet connected to the host PC. Host PC should detect APX USB
|
||||
device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/<dev>.bct --b u-boot-dtb-tegra.bin
|
||||
|
||||
Where <dev> is your devie codename (``tf201``, ``tf300t``, ``tf700t`` etc.).
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -124,6 +110,14 @@ Some of Transformers use a separate 4 MB SPI flash, which contains all data
|
||||
required for boot. It is flashed from within U-Boot itself, preloaded into RAM
|
||||
using Fusée Gelée.
|
||||
|
||||
Create ``repart-block.bin`` using re-crypt without ``--split`` key:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev tf600t --sbk <your sbk>
|
||||
|
||||
After creating your ``repart-block.bin`` you have to place it on a 1st partition
|
||||
of microSD card formated in fat. Then insert this microSD card into your tablet
|
||||
and boot it using Fusée Gelée and U-Boot, which was included into
|
||||
@ -147,8 +141,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -3,9 +3,9 @@
|
||||
U-Boot for the HTC One X (endeavoru)
|
||||
====================================
|
||||
|
||||
``DISCLAMER!`` Moving your HTC ONe X to use U-Boot assumes replacement of the
|
||||
``DISCLAMER!`` Moving your HTC One X to use U-Boot assumes replacement of the
|
||||
vendor hboot. Vendor android firmwares will no longer be able to run on the
|
||||
device. This replacement IS reversible.
|
||||
device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -35,61 +35,42 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev endeavoru
|
||||
$ ./re-crypt.py --dev endeavoru --split
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with the Fusée Gelée.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/endeavoru.bct -b android_bootloader.bin
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. For HTC One X (endeavoru) this mode can be entered using ``fastboot oem rcm``
|
||||
command from modified S-OFF bootloader or using testpad on motherboard. Host PC
|
||||
should detect APX USB device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/endeavoru.bct --b u-boot-dtb-tegra.bin
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -112,8 +93,8 @@ bootmenu. Bootmenu contains entries to mount eMMC as mass storage, fastboot,
|
||||
reboot, reboot RCM, poweroff, enter U-Boot console and update bootloader (check
|
||||
the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,7 @@ U-Boot for the LG Optimus 2X P990
|
||||
|
||||
``DISCLAMER!`` Moving your device to use U-Boot assumes replacement of the
|
||||
vendor bootloader. Vendor Android firmwares will no longer be able to run on
|
||||
the device. This replacement IS reversible.
|
||||
the device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -35,62 +35,42 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev star
|
||||
$ ./re-crypt.py --dev star --split
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue. Additionally you must install ``tegrarcm``.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with nvflash.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./nvflash_v1.13.87205 --bct star.bct --setbct --odmdata 0xC8000
|
||||
--configfile flash.cfg --bl android_bootloader.bin --sync
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 2048 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and both volume buttons on
|
||||
turned off phone connected to the host PC. Host PC should detect APX USB device
|
||||
in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ tegrarcm --bct ./bct/star.bct --bootloader u-boot-dtb-tegra.bin --loadaddr 0x108000
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -113,8 +93,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,7 @@ U-Boot for the LG X3 T30 device family
|
||||
|
||||
``DISCLAMER!`` Moving your LG P880 or P895 to use U-Boot assumes replacement
|
||||
of the vendor LG bootloader. Vendor android firmwares will no longer be able
|
||||
to run on the device. This replacement IS reversible.
|
||||
to run on the device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -38,62 +38,42 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev p895
|
||||
$ ./re-crypt.py --dev p895 --split # or --dev p880
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with the Fusée Gelée.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/p895.bct -b android_bootloader.bin
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device. Note that if you have Optimus 4x HD,
|
||||
use ``p880.bct``.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered by holding ``power`` and both buttons on turned
|
||||
off phone connected to the host PC. Host PC should detect APX USB device in
|
||||
``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/p895.bct --b u-boot-dtb-tegra.bin # or p880.bct
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -116,8 +96,8 @@ bootmenu. Bootmenu contains entries to mount eMMC as mass storage, fastboot,
|
||||
reboot, reboot RCM, poweroff, enter U-Boot console and update bootloader (check
|
||||
the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -33,7 +33,7 @@ directory with
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/surface-2.bct
|
||||
$ ./run_bootloader.sh -s T114 -t ./bct/surface-2.bct
|
||||
|
||||
To boot Linux, U-Boot will look for an ``extlinux.conf`` on MicroSD and then on
|
||||
eMMC. Additionally, if the Volume Down button is pressed while loading, the
|
||||
|
||||
@ -67,9 +67,26 @@ Flashing U-Boot into the eMMC
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. For Motorola Atrix 4G (MB860) and Droid X2 (MB870) this mode can be entered
|
||||
from vendor bootloader menu and with special cable from prerequisites chapter.
|
||||
Host PC should detect APX USB device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./utils/nvflash_t20 --setbct --bct ./bct/olympus.bct --configfile ./utils/flash.cfg
|
||||
--bl u-boot-dtb-tegra.bin --sbk <your sbk> --sync
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -92,8 +109,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,7 @@ U-Boot for the Ouya Game Console (ouya)
|
||||
|
||||
``DISCLAMER!`` Moving your Ouya to use U-Boot assumes replacement of the
|
||||
vendor bootloader. Vendor android firmwares will no longer be able to run on the
|
||||
device. This replacement IS reversible.
|
||||
device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -35,62 +35,44 @@ Process U-Boot
|
||||
in re-crypt repo issues. NOT HERE!
|
||||
|
||||
re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
usable by device. This process is required only on the first installation or to
|
||||
recover the device in case of a failed update. You need to know your device
|
||||
individual SBK to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev ouya
|
||||
$ ./re-crypt.py --dev ouya --sbk <your sbk> --split
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
where SBK has next form ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX`` ``0xXXXXXXXX``
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM. Regardless of the method bct and bootloader
|
||||
will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
|
||||
``DISCLAMER!`` All questions related to NvFlash should be asked in the proper
|
||||
``DISCLAMER!`` All questions related to fusee-tools should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Devices can
|
||||
enter it by pre-loading vendor bootloader with the Fusée Gelée.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/ouya.bct -b android_bootloader.bin
|
||||
$ ./utiils/nvflash_v1.13.87205 --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered from testpad on motherboard with device connected
|
||||
to the host PC. Host PC should detect APX USB device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
fusee-tools:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ ./run_bootloader.sh -s T30 -t ./bct/ouya.bct --b u-boot-dtb-tegra.bin
|
||||
|
||||
While pre-loading U-Boot, interrupt bootflow by pressing ``CTRL + C`` (USB keyboard
|
||||
must be plugged in before U-Boot is preloaded, else it will not work), input
|
||||
@ -113,8 +95,8 @@ bootmenu provides entries to mount eMMC as mass storage, fastboot, reboot,
|
||||
reboot RCM, poweroff, enter U-Boot console and update bootloader (check
|
||||
the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -5,7 +5,8 @@ U-Boot for the Samsung N1 device family
|
||||
|
||||
``DISCLAMER!`` Moving your Samsung Galaxy R (GT-I9103) or Samsung Captivate Glide
|
||||
(SGH-i927) to use U-Boot assumes replacement of the sboot. Vendor android firmwares
|
||||
will no longer be able to run on the device. This replacement IS reversible.
|
||||
will no longer be able to run on the device. This replacement IS reversible if you
|
||||
have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
|
||||
@ -5,7 +5,7 @@ U-Boot for the WEXLER QC750 tablet
|
||||
|
||||
``DISCLAMER!`` Moving your WEXLER QC750 to use U-Boot assumes replacement
|
||||
of the vendor bootloader. Vendor Android firmwares will no longer be able
|
||||
to run on the device. This replacement IS reversible.
|
||||
to run on the device. This replacement IS reversible if you have backups.
|
||||
|
||||
Quick Start
|
||||
-----------
|
||||
@ -38,26 +38,13 @@ re-crypt is a tool that processes the ``u-boot-dtb-tegra.bin`` binary into form
|
||||
usable by device. This process is required only on the first installation or
|
||||
to recover the device in case of a failed update.
|
||||
|
||||
Permanent installation can be performed either by using the tegrarcm or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
|
||||
Processing for the NV3P protocol
|
||||
********************************
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ git clone https://gitlab.com/grate-driver/re-crypt.git
|
||||
$ cd re-crypt # place your u-boot-dtb-tegra.bin here
|
||||
$ ./re-crypt.py --dev qc750
|
||||
$ ./re-crypt.py --dev qc750 --split
|
||||
|
||||
The script will produce a ``repart-block.bin`` ready to flash.
|
||||
|
||||
Processing for pre-loaded U-Boot
|
||||
********************************
|
||||
|
||||
The procedure is the same, but the ``--split`` argument is used with the
|
||||
``re-crypt.py``. The script will produce ``bct.img`` and ``ebt.img`` ready
|
||||
to flash.
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Flashing U-Boot into the eMMC
|
||||
-----------------------------
|
||||
@ -65,31 +52,24 @@ Flashing U-Boot into the eMMC
|
||||
``DISCLAMER!`` All questions related to tegrarcm should be asked in the proper
|
||||
place. NOT HERE! Flashing U-Boot will erase all eMMC, so make a backup before!
|
||||
|
||||
Permanent installation can be performed either by using the nv3p protocol or by
|
||||
pre-loading just built U-Boot into RAM.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Flashing with the NV3P protocol
|
||||
*******************************
|
||||
You have to clone and prepare fusee-tools from here: https://gitlab.com/grate-driver/fusee-tools
|
||||
according to fusee-tools README to continue. Additionally you must install ``tegrarcm``.
|
||||
|
||||
Nv3p is a custom Nvidia protocol used to recover bricked devices. Tegrarcm is
|
||||
used to handle such state.
|
||||
|
||||
With nv3p, ``repart-block.bin`` is used. It contains BCT and a bootloader in
|
||||
encrypted state in form, which can just be written RAW at the start of eMMC.
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ tegrarcm --bct qc750.bct --bootloader android_bootloader.bin --loadaddr 0x80108000
|
||||
$ nvflash --resume --rawdevicewrite 0 1024 repart-block.bin
|
||||
|
||||
When flashing is done, reboot the device.
|
||||
|
||||
Flashing with a pre-loaded U-Boot
|
||||
*********************************
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered via testpad on unpopulated RCM button on motherboard
|
||||
on device connected to the host PC. Host PC should detect APX USB device in ``lsusb``.
|
||||
|
||||
U-Boot pre-loaded into RAM acts the same as when it was booted "cold". Currently
|
||||
U-Boot supports bootmenu entry fastboot, which allows to write a processed copy
|
||||
of U-Boot permanently into eMMC.
|
||||
of U-Boot permanently into eMMC. This is how U-Boot can be preloaded using
|
||||
tegrarcm:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
$ tegrarcm --bct ./bct/qc750.bct --bootloader u-boot-dtb-tegra.bin --loadaddr 0x80108000
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
@ -112,8 +92,8 @@ device will enter bootmenu. Bootmenu contains entries to mount MicroSD and eMMC
|
||||
as mass storage, fastboot, reboot, reboot RCM, poweroff, enter U-Boot console
|
||||
and update bootloader (check the next chapter).
|
||||
|
||||
Flashing ``repart-block.bin`` eliminates vendor restrictions on eMMC and allows
|
||||
the user to use/partition it in any way the user desires.
|
||||
Flashing ``bct.img`` and ``ebt.img`` eliminates vendor restrictions on eMMC and
|
||||
allows the user to use/partition it in any way the user desires.
|
||||
|
||||
Self Upgrading
|
||||
--------------
|
||||
|
||||
@ -60,11 +60,15 @@ installation or to recover the device in case of a failed update.
|
||||
|
||||
The script will produce ``bct.img`` and ``ebt.img`` ready to flash.
|
||||
|
||||
Permanent installation can be performed by pre-loading just built U-Boot
|
||||
into RAM via tegrarcm. While pre-loading U-Boot, hold the ``volume down``
|
||||
button which will trigger the bootmenu. There, select ``fastboot`` using
|
||||
the volume and power buttons.
|
||||
Permanent installation can be performed by pre-loading just built U-Boot into RAM.
|
||||
Bct and bootloader will end up in boot0 and boot1 partitions of eMMC.
|
||||
|
||||
Bootloader preloading is performed to device in APX/RCM mode connected to host
|
||||
PC. This mode can be entered via testad on motherboard on turned off device
|
||||
connected to the host PC. Host PC should detect APX USB device in ``lsusb``.
|
||||
|
||||
While pre-loading U-Boot, hold the ``volume down`` button which will trigger
|
||||
the bootmenu. There, select ``fastboot`` using the volume and power buttons.
|
||||
After, on host PC, do:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user