Issue #699
closedCorrect Files for which flag durring install + role for system.ext4.img
0%
Description
In reading through the web page for the installation instructions for the Galaxy Tab 2 10.1 (http://redmine.replicant.us/ projects/replicant/wiki/GalaxyTab2101Installation) I have two questions that are somewhat related. The both deal with the files to be downloaded and installed.
First, in the it notes at the top in the "Downloading the files" section it says:
> "2. Download all the files listed for the device (including the checksum) on ReplicantImages for the latest image"
Going to the page that it says to download ALL the files listed for the current version of the Galaxy Tab 2 10.1. Going to that page there are 4 files listed:
- p5110.md5
- boot.img
- recovery.img
- system.ext4.img
I understand what the .md5 file is the md5 hash signatures of the other three files. My question is what is the system.ext. img file for? The instructions later down on the page never seem to reference or use the system.ext4.img file.
Second, at the bottom of the page are the command line instructions for using Heimdall with the "flash" action that you pass it two flags:
--BOOT path/to/recovery.img
--RECOVERY path/to/recovery.img
In both cases the directions point to the recovery.img file. I am guessing that the parameter to pass to the "--BOOT" flag is really the boot.img file that was one of the original four files to download.
Sorry for all the noob questions. I have used Fedora for years and love FLOSS but I have never experimented flashing ROMs before and just don't want to brick my device.
Thanks!
Updated by Paul Kocialkowski almost 11 years ago
- Status changed from New to Closed
- Resolution set to fixed
You should have used the forums to ask these questions -- we prefer to use the issues tracker for reporting bugs.
My question is what is the system.ext. img file for? The instructions later down on the page never seem to reference or use the system.ext4.img file.
It is the system, which is the most important part of it all, it's actually the Replicant userspace. It is installed through the recovery procedure and is not useless. All the files that need to be downloaded are important to the installation process, even though it seems like they're not used, they actually are.
In both cases the directions point to the recovery.img file. I am guessing that the parameter to pass to the "--BOOT" flag is really the boot.img file that was one of the original four files to download.
Your guess is understandable, but it's better to flash recovery on the BOOT partition too so that it can reboot directly to recovery without holding keys. Then the BOOT partition will be overridden by the actual boot.img contents during the installation process using recovery.
Updated by Paul Kocialkowski over 9 years ago
- Tracker changed from Support to Issue
- Target version changed from 21 to Any version
Updated by Denis 'GNUtoo' Carikli almost 9 years ago
- Category changed from 105 to Framework
- Device Galaxy Tab 2 10.1 (P51xx) added