|
|
Backing up the display firmware / data is generally not needed as pretty much all the important information comes from the phone during use. There are some situations where it may be useful however.
|
|
|
The display itself is running Android 5.1 and as such follows a fairly standard Android filesystem structure
|
|
|
* `boot` holds the system kernel and initial startup code
|
|
|
* `recovery` is a separate bootup system to provide functionality for upgrading, wiping etc.
|
|
|
* `system` holds the majority of the Android and Navdy code
|
|
|
* `data` has the user data, including bluetooth pairing, locale, dash layout etc. This is wiped during a factory reset
|
|
|
* `maps` this is the drive that's shown when plugging the display into computer as a usb flash driver, it is mainly used to hold map data.
|
|
|
|
|
|
On a pristine system from navdy, there's no known way to backup and of these partitions, other than copying files off the maps drive in usb mass storage mode.
|
|
|
|
|
|
Since my 3060 firmware pack however, I've modified the recovery partition to provide access to the entire unit when plugged into PC. This process requires you to be able to plug your navdy into computer on USB while it's powered by car / 12V. So you'll either need a laptop in your car or some way to plug 12V into your navdy cable eg
|
|
|
* https://www.kds-online.com/Shop6a/catalog/product_info.php/power-supply-for-obd2-interfaces-typ-12v-1000ma-p-3505
|
|
|
* https://www.amazon.com/SPARKING-Supply-Cigarette-Lighter-Adapter/dp/B078DXVJJK and https://www.ebay.com.au/i/202399023203
|
|
|
|
|
|
If you're not already running my firmware, you will need to update just the recovery partition to my version to proceed. This will allow you to backup your boot, data and system partitions which are the more important ones for navdy use generally.
|
|
|
|
|
|
|
|
|
#### Installing alelec recovery image
|
|
|
* Download latest firmware pack from https://gitlab.com/alelec/navdy/display-rom/-/tags and unzip it
|
|
|
* In the firmware pack folder, make a copy of `FLASH_WIN` or `FLASH_OSX_LINUX` as appropriate for your system (Windows or Mac/Linux).
|
|
|
* Open the copy in a text editor. On windows you can simply right click on the file and go to `Edit`
|
|
|
* Delete all the pairs of lines for boot and system install, leaving just recovery.
|
|
|
For Windows
|
|
|
```
|
|
|
fastboot.exe -i 0x9886 flash boot boot.img | | fastboot.exe -i 0x9886 flash recovery recovery.img
|
|
|
IF %ERRORLEVEL% NEQ 0 goto error | | IF %ERRORLEVEL% NEQ 0 goto error
|
|
|
fastboot.exe -i 0x9886 flash recovery recovery.img | becomes |
|
|
|
IF %ERRORLEVEL% NEQ 0 goto error | |
|
|
|
fastboot.exe -i 0x9886 flash system system.img | |
|
|
|
IF %ERRORLEVEL% NEQ 0 goto error | |
|
|
|
```
|
|
|
|
|
|
For OSX / Linux
|
|
|
|
|
|
```
|
|
|
$SUDO$FASTBOOT -i 0x9886 flash boot boot.img | | $SUDO$FASTBOOT -i 0x9886 flash recovery recovery.img
|
|
|
[ $? -eq 0 ] || flash_failed $? | | [ $? -eq 0 ] || flash_failed $?
|
|
|
| |
|
|
|
$SUDO$FASTBOOT -i 0x9886 flash recovery recovery.img | becomes |
|
|
|
[ $? -eq 0 ] || flash_failed $? | |
|
|
|
| |
|
|
|
$SUDO$FASTBOOT -i 0x9886 flash system system.img | |
|
|
|
[ $? -eq 0 ] || flash_failed $? | |
|
|
|
```
|
|
|
|
|
|
Everything else in the file remains the same.
|
|
|
|
|
|
Then follow [Install Instructions](https://gitlab.com/alelec/navdy/display-rom/wikis/home#install-instructions) above but run the edited script rather than the original one.
|
|
|
|
|
|
|
|
|
#### Booting into Recovery ADB
|
|
|
Once you've for a display with my current recovery image installed, simply start the navdy display as normal in your car (On on 12V cable).
|
|
|
|
|
|
Once it's started up, plug in the USB to computer. The navdy display shouldn't change, but you may get a "new device plugged in / installing drivers" popup on your computer.
|
|
|
|
|
|
If on windows, in the firmware pack folder run `WIN_INSTALL_USB_DRIVER`
|
|
|
|