Changes

Jump to: navigation, search

Samsung Galaxy Tab S2 9.7 Wifi (samsung-gts210vewifi)

806 bytes added, 10:59, 2 April 2018
update: flashing works, but booting does not
</pre>
gts210vewifi:/ $ ls -la /dev/block/bootdevice <pre>lrwxrwxrwx 1 root root 39 2016-01-17 22:21 /dev/block/bootdevice -> /dev/block/platform/soc.0/7824900.sdhci</pre> gts210vewifi:/ $ ls -la /dev/block/platform/soc.0/7824900.sdhci/by-name/ <
<pre>
total 0
== Installation ==
ATTENTION - DEVICE DOES NOT BOOT YET, hereit hangs at the initial boot screen while displaying "KERNEL IS NOT SEANDROID ENFORCINGSet Warranty Bit : kernel SAMSUNGGalaxy Tab S2 POWEREd BY android" Not reachable via SSH/telnet - too early? Here's what I tried up to now, all with same result - hangs with message above:* had problems with "heimdall flash installed system on sdcard pmbootstrap install --no-fde --KERNEL sdcard=/dev/..." command used by ", pmbootstrap flasher flash_kernel"* or flashed both system and boot image to boot and system partitions* tried also via TWRP recovery zip file flashing works, read out boot partition after flashing via TWRP, and it did stop with "ERROR: Partition "KERNEL" does not exist in contain the specified PITpmOS boot image."* flashing via heimdall does not seem Not mentioned in the porting docu yet: Had to work - device uses lowercase use '''uppercase''' partition labels which in deviceinfo_flash_heimdall_partition_(kernel|system) variables in deviceinfo file, even if their symlinks are not supported by heimdall, lowercase (e.g. pmbootstrap flasher flash_rootfs "system --partition userdata gives: > /dev/block/mmcblk0p36"), otherwise get 'ERROR: Partition "userdatasystem" does not exist in the specified PIT.'  if using uppercase "USERDATA" then flashing ''seems'' to workboot.img compared with LineageOS 15.1 boot.img looks quite identical: pmbootstrap flasher flash_rootfs <pre>$ unpackbootimg -i boot.img -partition USERDATAo boot.img.dirBOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom androidboot.wificountrycode=00 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk buildvariant=userdebugBOARD_KERNEL_BASE 80000000BOARD_NAMEBOARD_PAGE_SIZE 2048BOARD_HASH_TYPE sha1BOARD_KERNEL_OFFSET 00008000BOARD_RAMDISK_OFFSET 02000000BOARD_SECOND_OFFSET 00f00000BOARD_TAGS_OFFSET 01e00000 '''but does not''', as userdata partition size is 0 after that command (seen by TWRP recovery)BOARD_DT_SIZE 800768 same for "SYSTEM" and "BOOT" partitions</pre>* flashing via TWRP recovery zip fileexcept that LineageOS boot image sets a BOARD_NAME, also installing the recovery zipfile via TWRP does '''not''' seem to work, system partition size is 0MB afterwards, seen in TWRP recovery in backup menuBOARD_OS_VERSION and BOARD_OS_PATCH_LEVEL. boot.img-dtb files inside are identical.. this explains why device does not boot after pmOS is "installed" - it isn't in reality?!   
== See also ==
46
edits

Navigation menu