[ROM][OFFICIAL][T713][7.1] LineageOS 14.1

Trying to install using TWRP 3.1.0-1_ashyx on my SM-T713 and I have a couple issues, I think it may be related to encryption but I can't even flash the ROM. Here's what I'm getting:
This package supports bootloader(s): T713ZSU2AQA1; this device has bootloader T713XXU2APK6.
Updater process ended with ERROR: 7
Failed to mount '/data' (Invalid argument)
 

klm2349

Member
May 26, 2016
25
3
0
Trying to install using TWRP 3.1.0-1_ashyx on my SM-T713 and I have a couple issues, I think it may be related to encryption but I can't even flash the ROM. Here's what I'm getting:
This package supports bootloader(s): T713ZSU2AQA1; this device has bootloader T713XXU2APK6.
Updater process ended with ERROR: 7
Failed to mount '/data' (Invalid argument)
Go to twrp.me find sm-t713 device and download twrp 3.1.0-0. Flash that using Odin the same way as root was described in OP. You can then mount /data and format, install, etc.
 
Go to twrp.me find sm-t713 device and download twrp 3.1.0-0. Flash that using Odin the same way as root was described in OP. You can then mount /data and format, install, etc.
Downloaded twrp-3.1.0-0-gts28vewifi.img.tar, which matches my device (SM-T713), flashed using ODIN3 v.3.10.7 under the AP tab, no reboot, straight to recovery.
Still can't mount /data, can't change the filesystem on it, repair it, or anything.
When I try and flash the ROM (lineage-14.1-20170418-nightly-gts28vewifi-signed.zip) it gives me the same messages...
 
Last edited:

0blivi0n

Member
Jan 13, 2017
11
9
3
Downloaded twrp-3.1.0-0-gts28vewifi.img.tar, which matches my device (SM-T713), flashed using ODIN3 v.3.10.7 under the AP tab, no reboot, straight to recovery.
Still can't mount /data, can't change the filesystem on it, repair it, or anything.
When I try and flash the ROM (lineage-14.1-20170418-nightly-gts28vewifi-signed.zip) it gives me the same messages...
You need to flash the below firmware first, then flash TWRP, do a full wipe (/system as well) and then Lineage:

https://www.sammobile.com/firmwares/download/124441/T713ZSU2AQA1_T713OZS2AQA1_BRI/
 
Last edited:
Go to twrp.me find sm-t713 device and download twrp 3.1.0-0. Flash that using Odin the same way as root was described in OP. You can then mount /data and format, install, etc.
You need to flash the below firmware first, then flash TWRP, do a full wipe (/system as well) and then Lineage:

https://www.sammobile.com/firmwares/download/124441/T713ZSU2AQA1_T713OZS2AQA1_BRI/
I would but I don't really want to sign up for a hosting service to download one file, do you have a link to a publicly available image?
 

joshnolt777

Member
Apr 18, 2014
26
4
0
So quick question. I have the t713 but it's the USA version, which doesn't have the aqa1 bootloader update yet and sammobile and update both don't have the update files. Would it be ok to flash a UK or Taiwan image then flash LOS? Thanks in advance.
 

0blivi0n

Member
Jan 13, 2017
11
9
3
Ok, so I've downloaded the above image, flashed it, then flashed the Lineage image, and it boots now, but it says something like 'data' is corrupt and it tries to keep wiping the data partition. I tried to manually wipe it, also format it as ext 4, repair it and change the size, no luck :(
Did you do a full wipe (Dalvik, System, Data and Cache) before installing Lineage?
 
Did you do a full wipe (Dalvik, System, Data and Cache) before installing Lineage?
Yup, and the odd thing is if I wipe everything, including system, but then reboot, it still boots to lineage and gives me the Encryption unsuccessful screen, no soft brick as you would expect.
Here's the logcat I get when I try and wipe everything except for micro SD card:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
unable to mount storage

etc.
 

LuK1337

Recognized Developer
Jan 18, 2013
8,103
16,369
253
Yup, and the odd thing is if I wipe everything, including system, but then reboot, it still boots to lineage and gives me the Encryption unsuccessful screen, no soft brick as you would expect.
Here's the logcat I get when I try and wipe everything except for micro SD card:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
unable to mount storage

etc.
Select data in twrp and change it's file system to ext4.
 

pclewis

Senior Member
Nov 23, 2010
102
11
18
Still no workie, but I actually chose 'Format Data' instead of going into advanced wipe and doing it there and it worked... Now I know :)
Thank you!
Hmm, I thought I was doing something crazy, but Format Data worked for me too. I wonder if A1 is out in something besides Chinese?

Phil
 

joshnolt777

Member
Apr 18, 2014
26
4
0
Yup, and the odd thing is if I wipe everything, including system, but then reboot, it still boots to lineage and gives me the Encryption unsuccessful screen, no soft brick as you would expect.
Here's the logcat I get when I try and wipe everything except for micro SD card:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (invalid argument)
unable to mount storage

etc.
Did you try formatting your data partition in twrp? I had to do that because of encryption once. Click wipe and then format data instead of advanced wipe
 
  • Like
Reactions: nickspiker

fiver5

Senior Member
Aug 13, 2010
53
34
0
I don't want to get too far off topic in this thread, but it sounds like you are using Windows. My suggestion is to install Ubuntu 16.04 in a virtual machine and build Heimdall in that. Building with Linux is much easier than with Windows. I am only using Linux. The README for building Heimdall in Linux is only a few steps and you do not have to worry about installing any special drivers, like Windows requires.
FWIW I got Heimdall built on Windows today. It is indeed a PITA.

If anyone else tries, here's what I had to do to get it to work in addition to what is listed in the README file in the win32

-use pacman to get the additional packages mingw-w64-x86_64-jasper mingw-w64-x86_64-toolchain
-run the cmake command from the top level build directory with . as the final argument, not from inside the build directory with .. as the final argument as in the instructions. There are some broken paths somewhere in the structure and cmake will barf looking for stuff if you run it from the build directory.

I didn't have to install any special drivers but I've flashed so many android devices from this machine in the past year that I already had the samsung ssusdbus.sys driver installed and that was leveraged.