[General Questions and Answers] mike-s:
My wife has the above A1-830, it worked for years with little problem after rooting. Fast forward a few months and due to life/career changes, it gets put away for a while. I brought it out a few months ago to give it a top up charge before putting it away and it still worked fine. I go to bring it back out recently, only to find that it's stuck on the loading android logo (where the logo shimmers). Fast forward again after a couple weeksand when I now have the motivation to look into it further, it now no longer starts and the shimmering logo just sits there. I connected a USB cable and have full root access over ADB, however I now seemingly have no way to get into droidboot/fastboot/recovery on this device. All attempts simply hang, with "fastboot devices" not showing anything.

After looking into this a little (and finding this and this blog post) I realised that I can use dd to overwrite the recovery and boot volume and hopefully bring this tablet back to life. The snag is that the points suggested within that blog that I can identify what partition resides where, are absent on this device (I figure maybe it's due to it being intel and not ARM architecture).

My problem is I unfortunately I don't know which ones to mess around with, and would very much like to avoid overwriting the wrong one or risking mounting the wrong partition and managing to break something in an unexpected way while poking around and trying to figure out the partitions to overwrite with what.

Partition Table

user@android:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
.
179 0 15376384 mmcblk0
179 1 167936 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 32768 mmcblk0p3
179 4 131072 mmcblk0p4
179 5 131072 mmcblk0p5
179 6 786432 mmcblk0p6
179 7 262144 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 12275692 mmcblk0p9
179 40 8192 mmcblk0gp0
179 30 8 mmcblk0rpmb
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 1931264 mmcblk1
179 51 1931200 mmcblk1p1

/proc/mounts

user@android:/ $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /factory ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p8 /system ext4 ro,noatime,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,journal_checksum,journal_async_commit,data=ordered 0 0

/dev/block/mmcblk0p5 /config ext4 rw,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p7 /logs ext4 rw,nosuid,nodev,relatime,journal_checksum,journal_async_commit,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0

contents of "partition.tbl" within the ROM i wish to write.

partition_table=gpt
create -z /dev/block/mmcblk0
create /dev/block/mmcblk0
boot -p /dev/block/mmcblk0
reload /dev/block/mmcblk0
add -b 40 -s 335872 -t efi -u 80868086-8086-8086-8086-000000000000 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 335912 -s 16384 -t efi -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 352296 -s 65536 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 417832 -s 262144 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk
add -b 679976 -s 262144 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 942120 -s 1572864 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 2514984 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3039272 -s 3145728 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 6185000 -s $calc($lba_end-16384) -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0

reload /dev/block/mmcblk0

Now I'm sure I can figure out from this which partition to write it to, however I would much rather get the answer (or pointers on where to look) to get a more concrete answer than "i think boot.img/fastboot.img/recovery.img goes ..." as frankly I feel this thing is recoverable in it's current state, and I don't want to go digging myself a deeper hole than I already need to with this.

I've spent the better part of 6+ hours trying to figure this out looking at various threads on XDA and searching online in general, any pointers for myself? anyone?