[G 2014 Q&A, Help & Troubleshooting] cxxxx:
I just found a twrp I could boot directly using fastboot... I am now in TWRP... to be continued. I'll keep you informed, I want to backup now first.

For now, this is the one I finally was able to boot:

http://techerrata.com/file/twrp2/titan/openrecovery-twrp-2.8.5.0-titan.img

Some more findings:

# fastboot oem fb_mode_set
...
FAILED (remote failure)

In the flashfile.xml form stock firmware-package, this command is listed before all the flash-commands.

Another irregularity is that the device cannot be locked again:

[root@rtgcli1hwid400 ~]# fastboot oem lock
...
(bootloader) Phone is locked successfully!
(bootloader) Please flash valid signed system image now!
OKAY [ 1.020s]
finished. total time: 1.020s
[root@rtgcli1hwid400 ~]# fastboot getvar securestate
securestate: locked
finished. total time: 0.001s
[root@rtgcli1hwid400 ~]# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.251s
[root@rtgcli1hwid400 ~]# fastboot getvar securestate
securestate: unlocked
finished. total time: 0.034s

---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------

I already heard of it.

The symptoms we are facing seem to be very similar to what you experience after issuing this command, but it has not been run.

---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------

Backup is not possible.

Mounting /data fails all the time, no valid filesystem is recognized.

When using TWRP for "advanced format" it claims to create an ext2-filesystem, but it still cannot be accessed or overwritten.

I am able to open a shell using adb, but I'm unsure how to proceed.

---------- Post added at 11:19 AM ---------- Previous post was at 11:04 AM ----------

Could someone with a working device show me the output of

parted /dev/block/mmcblk0 print

?

I'd like to compare with my partitioning:

/system # parted /dev/block/mmcblk0 print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 131kB 67.2MB 67.1MB ext4 modem
2 67.2MB 67.8MB 524kB sbl1
3 67.8MB 67.8MB 32.8kB DDR
4 67.9MB 68.9MB 1036kB aboot
5 69.4MB 69.6MB 205kB rpm
6 69.9MB 70.4MB 410kB tz
7 70.5MB 70.5MB 32.8kB sdi
8 70.5MB 71.0MB 524kB utags
9 71.0MB 73.1MB 2097kB logs
10 73.1MB 75.5MB 2388kB padA
11 75.5MB 76.5MB 1036kB abootBackup
12 77.0MB 77.2MB 205kB rpmBackup
13 77.5MB 78.0MB 410kB tzBackup
14 78.1MB 78.1MB 32.8kB sdiBackup
15 78.1MB 78.6MB 524kB utagsBackup
16 78.6MB 79.7MB 1077kB padB
17 79.7MB 81.3MB 1573kB modemst1
18 81.3MB 82.8MB 1573kB modemst2
19 82.8MB 83.3MB 500kB hob
20 83.3MB 83.4MB 32.8kB dhob
21 83.5MB 85.1MB 1573kB ext2 fsg
22 85.1MB 85.1MB 1024B fsc
23 85.1MB 85.1MB 8192B ssd
24 85.1MB 86.1MB 1049kB sp
25 86.1MB 86.3MB 131kB cid
26 86.3MB 89.4MB 3146kB ext3 pds
27 89.4MB 93.6MB 4194kB logo
28 93.6MB 97.8MB 4194kB clogo
29 97.9MB 106MB 8389kB ext4 persist
30 106MB 107MB 524kB misc
31 107MB 117MB 10.4MB boot
32 117MB 128MB 10.5MB recovery
33 128MB 129MB 1049kB deviceinfo
34 129MB 146MB 16.8MB ext4 ftmlog
35 146MB 706MB 560MB ext4 cache
36 706MB 1863MB 1158MB ext4 system
37 1863MB 1872MB 8389kB kpan
38 1872MB 7784MB 5913MB userdata

Partitions are there, but something is wrong with userdata, there is no filesystem and I cannot create one:

/system # mkfs.ext2 /dev/block/mmcblk0p38
mkfs.ext2: lseek: Value too large for defined data type

---------- Post added at 11:24 AM ---------- Previous post was at 11:19 AM ----------

parted crashes when trying to format:

(parted) mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? Yes
Yes
Partition number? 38
38
File system type? [ext2]?

Error: Invalid superblock. Are you sure this is an ext2 file system?

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Error: SEGV_MAPERR (Address not mapped to object)
Aborted
/system #

---------- Post added at 12:13 PM ---------- Previous post was at 11:24 AM ----------

is /cache/kernel_last_log from recovery or from system-boot?

This is interesting:

<6>[ 627.767910,2] F2FS-fs (mmcblk0p38): mounting..
<3>[ 627.903098,2] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 627.903235,1] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 627.903687,1] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
<6>[ 629.503418,0] EXT4-fs (mmcblk0p36): mounted filesystem with ordered data mode. Opts:
<7>[ 629.503560,0] SELinux: initialized (dev mmcblk0p36, type ext4), uses xattr
<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr

I also am able to write data on the partition using dd, so it is no hardware-problem. //edit: Bull****? When I dd'd the filesystem, nothing should be able to mount.

It is strange, that I can use /cache on adb shell, while fastboot says there would be an invalid partition type "raw" for /cache and /data.

---------- Post added at 12:43 PM ---------- Previous post was at 12:13 PM ----------

~ # dd if=/dev/zero of=/dev/block/mmcblk0p38 bs=8192 conv=fsync
dd: writing '/dev/block/mmcblk0p38': No space left on device
721777+0 records in
721776+0 records out
5912788992 bytes (5.5GB) copied, 501.042553 seconds, 11.3MB/s

This is so weird. This command usually destroys any single bit on a partition. "conv=fsync" makes sure that the data is actually written to the device.

The command finishes, but still kernel claims to have mounted something here when system boots:

<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr

---------- Post added at 01:26 PM ---------- Previous post was at 12:43 PM ----------

during formatting, dmesg is full of messages like:

<3>[ 1289.062754,0] Buffer I/O error on device mmcblk0p38, logical block 262
<4>[ 1289.062838,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.062991,0] Buffer I/O error on device mmcblk0p38, logical block 263
<4>[ 1289.063075,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.063233,0] end_request: I/O error, dev mmcblk0, sector 3661824
<3>[ 1289.063328,0] end_request: I/O error, dev mmcblk0, sector 3661880

Not sure if this TWRP is broken or my internal storage.

I think I give up on this. Glad to live in EU where I still should have warranty as the device is not older than 6 months :D