[Nexus 7 (2013) Q&A] crypticc:
Hi

I now have what I hope is a softbrick and came across this thread - I would be grateful if you could help me.

Thanks so much

Chris

Background

I was repartitioning to flash lineageOS on my ageing 2017 flo using the repartition make room to get twrp-3.3.1-1_UA-flo installed.

I got as far as completing and even after a couple wipe and fix of SYSTEM got the rom to flash. But I was still unable to format USERDATA. Nervous I didn't ever actually boot the rom to see if it worked. In hindsight I should've probably gone for it.

Long story short after a few attempts at formatting DATA from TWRP, including one that I terminated because seemed to be taking an age I then did Format of USERDATA in recovery. I think this is where the issue developed

Current Situation

I can still get into Fastboot.

I can boot from Fastboot into TWRP 3.1.1-1 UA recovery (the enlarged one) - so clearly that partition is okay. It does take an absolute age though, tens of minutes, not the usual several minutes.

Fastboot boot into .img isn't necessarily any quicker from what I can see. [update - the extra long delay to come into Recovery seems a bit temperamental - to the point that I'm now turning off to try another day - posted dmesg and recovery.log below]

However, that's about it I think.

Here's output from Recovery.log on one of the lengthy and still running boots into TWRP

https://pastebin.com/PtPnR0T3

Here's output of partition[30] from the oem gpt-info

(bootloader) partition[30].name = vendor
(bootloader) partition[30].first_lba = 4587584
(bootloader) partition[30].last_lba = 5099583
(bootloader) partition[30].size 256000 KB

I didn't do dd>> backup of eMMC in TWRP but I'm hoping the data is still there somewhere as in Fastboot I can see the partition tables that would have this data:

(bootloader) partition[1].name = radio
(bootloader) partition[1].first_lba = 131072
(bootloader) partition[1].last_lba = 306143
(bootloader) partition[1].size 87536 KB
(bootloader) partition[2].name = modemst1
(bootloader) partition[2].first_lba = 393216
(bootloader) partition[2].last_lba = 399359
(bootloader) partition[2].size 3072 KB
(bootloader) partition[3].name = modemst2
(bootloader) partition[3].first_lba = 399360
(bootloader) partition[3].last_lba = 405503
(bootloader) partition[3].size 3072 KB

Here's pastebin of the partition table using the partition table flash dump tool BEFORE I cooked it

https://pastebin.com/V17qUmvz

Have also attached output from dmesg run from adb shell when in TWRP, Pastebin for safe-keeping. The checksum errors for the various partitions is worrying. But I also remain hopeful this indicates a broken partition table rather than HW failure, is that a false-comfort?

https://pastebin.com/LUvRNzJU

Here's output of RESTOCK

Partitions had been changed.
Restore original partitions? [y/n]: y

Wait...

sending 'bootloader' (3911 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.224s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s

Wait...

sending 'gpt' (35 KB)...
OKAY [ 0.011s]
writing 'gpt'...
FAILED (remote: failed to write gpt)
finished. total time: 0.038s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s

If error, copy and post it, include restock.log

Here's the restock.log