Samsung Galaxy Tab 2 10.1: which lunch?

Added by Holger Marzen over 11 years ago

I've set up a build environment on a Xubuntu 12.04.3 VM, 64 Bit.
I got the tools in sources as described in http://redmine.replicant.us/projects/replicant/wiki/GettingReplicantSources
I had to install ia32-libs because the binaries in prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin are only 32 Bit.

http://redmine.replicant.us/projects/replicant/wiki/GalaxyTab2101Build
tells me:

lunch replicant_p5100-eng

But my Galaxy Tab reports itself as GT-P5110. Shouldn't I use

lunch replicant_p5110-eng ?

Replies (3)

RE: Samsung Galaxy Tab 2 10.1: which lunch? - Added by Paul Kocialkowski over 11 years ago

Yep, you're right, we simply didn't update the instructions to take the wifi-only version in account.

RE: Samsung Galaxy Tab 2 10.1: which lunch? - Added by Holger Marzen over 11 years ago

So now I have:

 replicant@eis:~/replicant/replicant-4.0$ ls -l out/target/product/p5110
 total 219148
 -rw-r--r--  1 replicant replicant   4222976 Nov 24 20:39 boot.img
 -rw-rw-r--  1 replicant replicant     20709 Nov 25 17:26 clean_steps.mk
 drwxrwxr-x  4 replicant replicant      4096 Nov 24 20:52 data
 drwxrwxr-x  3 replicant replicant      4096 Nov 24 20:01 external
 -rw-rw-r--  1 replicant replicant     54651 Nov 24 21:01 installed-files.txt
 -rwxrwxr-x  1 replicant replicant   3859016 Nov 24 20:39 kernel
 drwxrwxr-x 18 replicant replicant      4096 Nov 24 21:01 obj
 -rw-rw-r--  1 replicant replicant       609 Nov 25 17:26 previous_build_config.mk
 -rw-rw-r--  1 replicant replicant   2846976 Nov 24 20:51 ramdisk-recovery.cpio
 -rw-rw-r--  1 replicant replicant   1971762 Nov 24 20:51 ramdisk-recovery.img
 -rw-rw-r--  1 replicant replicant    353298 Nov 24 19:47 ramdisk.img
 drwxrwxr-x  3 replicant replicant      4096 Nov 24 20:51 recovery
 -rw-r--r--  1 replicant replicant   5840896 Nov 24 20:51 recovery.img
 drwxrwxr-x  9 replicant replicant      4096 Nov 24 19:47 root
 drwxrwxr-x  7 replicant replicant      4096 Nov 24 20:51 symbols
 drwxrwxr-x 14 replicant replicant      4096 Nov 24 20:47 system
 -rw-------  1 replicant replicant 205096320 Nov 24 21:01 system.ext4.img
 -rw-------  1 replicant replicant     80256 Nov 25 17:28 userdata.img
 drwxrwxr-x  2 replicant replicant      4096 Nov 24 20:47 utilities

http://redmine.replicant.us/projects/replicant/wiki/ReplicantImages tells me to use
- p5110.md5
- boot.img
- recovery.img
- system.ext4.img

1.) How can I generate p5110.md5?
2.) Is "sudo heimdall flash --BOOT path/to/recovery.img --RECOVERY path/to/recovery.img"
correct or should it read "sudo heimdall flash --BOOT path/to/boot.img --RECOVERY path/to/recovery.img
?

3.) What files are needed on the micro-SD card? p5110.md5 and system.ex4.img only, because boot.img and recovery.img are already flashed?

RE: Samsung Galaxy Tab 2 10.1: which lunch? - Added by Paul Kocialkowski over 11 years ago

1. The script to generate the release files (including the md5sum) is at http://ftp.osuosl.org/pub/replicant/images/replicant-4.0/0005/scripts/release.sh
but the md5 can also be generated by hand using md5sum against the images (don't list more it it'll fail at recovery).

2. The correct heimdall line is:

sudo heimdall flash --KERNEL path/to/recovery.img --RECOVERY path/to/recovery.img

And --KERNEL using recovery is NOT a mistake! Note that I corrected it to use KERNEL instead of BOOT which doesn't work.
This is done so that the device reboots directly to recovery :)

3. The installation guide says to copy all the files we release to the sdcard, so you cannot avoid boot.img and/or recovery.img (first they are used and second, if you don't put them on the sdcard, the md5 check will fail and it will refuse installing Replicant)

(1-3/3)

Project

General

Profile

Replicant