Could a At&t and / or sprint rooted user please be so kind to share the output of this command please? thanks from a VZW GS3 owner.
PHP:
ls -l /dev/block/platform/msm_sdcc.1/by-name
Forgot to add this is from diet ics rim. I don't know if that matters
Sent from my Samsung S3
Thank you very much.
Code:
lrwxrwxrwx root root 1970-01-01 17:58 aboot -> dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 17:58 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 17:58 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 17:58 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 17:58 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 17:58 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 17:58 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 17:58 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 17:58 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 17:58 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 17:58 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 17:58 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 17:58 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 17:58 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 17:58 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 17:58 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 17:58 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 17:58 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 17:58 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 17:58 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 17:58 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 17:58 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 17:58 userdata -> /dev/block/mm
cblk0p15
Let me know if there's anything else I can help you out with
Hi, anyone can help me to backup IMEI before flash ROM?
Please, I once made my IMEI lost after flash so i really glad to know how to backup IMEI first.
Thanks.
You can use TWRP-recovery to backup and restore your EFS partition (where the imei is stored) or use Samsung Tools (http://d-h.st/zGr)
can it also be done via ADB ??
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img
Code:
[email protected]:/dev/block/platform/dw_mmc.0/by-name # ll
ll
lrwxrwxrwx root root 2014-08-10 10:18 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-08-10 10:18 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-08-10 10:18 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-08-10 10:18 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-08-10 10:18 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-08-10 10:18 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-08-10 10:18 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-08-10 10:18 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-08-10 10:18 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-08-10 10:18 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-08-10 10:18 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-08-10 10:18 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-08-10 10:18 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-08-10 10:18 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-08-10 10:18 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-08-10 10:18 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-08-10 10:18 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-08-10 10:18 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-08-10 10:18 m9kefs3 -> /dev/block/mmcblk0p6
and if so how can it be restored ? (i am a Linux noob)
The output of
Code:
[email protected]:/ # ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name/
total 0
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2016-05-20 18:17 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2016-05-20 18:17 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 param -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 2016-05-20 18:17 system -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2016-05-20 18:17 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2016-05-20 18:17 xloader -> /dev/block/mmcblk0p1
says boot is
Code:
mmcblk0p7
but when unpacked, changed, and flashed to boot, I load up into CWM Recovery, when the recovery partition is clearly
Code:
mmcblk0p8
.
Am I doing something wrong? Is the (insert non-n00b word here) skipping the boot partition?
I was wondering how to create a flashable restore for the stock boot and recovery image I was exploring the partitions and this is where I got stuck(I'm aware that there are A and B partitions, but have no idea what they are(are they split across two partitions or is b a backup of a and vice versa?):
taimen:/dev/block/platform/soc/1da4000.ufshc/by-name $ ls -al .
total 0
drwxr-xr-x 2 root root 1280 1970-01-14 05:56 .
drwxr-xr-x 4 root root 1460 1970-01-14 05:56 ..
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 abl_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 abl_b -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 aes_a -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 aes_b -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 align_parti -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 boot_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 boot_b -> /dev/block/sde22
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 cdt -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib64_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib64_b -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 cmnlib_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 cmnlib_b -> /dev/block/sde23
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ddr -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devcfg_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devcfg_b -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 devinfo -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dip -> /dev/block/sde35
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dpo -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dtbo_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 dtbo_b -> /dev/block/sde27
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 frp -> /dev/block/sdg1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 fsc -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 fsg -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ftm -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 hyp_b -> /dev/block/sde17
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 keymaster_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 keymaster_b -> /dev/block/sde21
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 laf_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 laf_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 limits -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 logfs -> /dev/block/sde39
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 metadata -> /dev/block/sde41
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 misc -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modem_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 modem_b -> /dev/block/sde19
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 modemst2 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 persist -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 pmic_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 pmic_b -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 pstore -> /dev/block/sda9
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 rpm_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 rpm_b -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 sec -> /dev/block/sde33
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 ssd -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 sti -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 storsec -> /dev/block/sde31
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 system_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 system_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 toolsfv -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 tz_b -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 userdata -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vbmeta_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vbmeta_b -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vendor_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-14 05:56 vendor_b -> /dev/block/sde28
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-14 05:56 xbl_b -> /dev/block/sdc1
Click to expand...
Click to collapse
There is no recovery partition on this phone. The recovery image is contained within the boot image, which is why the TWRP site has flashable installers that you can download that patch the boot images so that they contain TWRP instead of stock. A and B partitions exist for Google's automatic seamless update feature. Your phone only boots off of either A or B at any given time. If your phone is using A and a software update becomes available, the update will download and install to B, and your phone will boot the B partition on the next reboot instead of A. When a future update is released, the same process will happen with A.
So if you want to backup boot and recovery, all you need to backup is boot of the partition that your phone is currently using (TWRP can tell you which one it is using).
Problem: My beloved 32GB Pixel XL froze while I was typing the other night and I hard reset it. It froze during the boot animation, then rebooted, and then froze during the boot animation again. Done this ~30 times with no joy. It's just over a year old so no warranty.
Background: Bootloader unlocked. Stock rom v 7.1 (build NPF26J). Rooted.
What I've tried:
Clearing Dalvik/cache in TWRP
Factory reset through recovery (both TWRP and stock)
Begging it to work
Flashing factory images for 7.1 and 8.1
locking and unlocking the bootloader multiple times before flashing above factory images
Formatting Data and doing an Advanced Wipe in TWRP to recreate partitions then flashing both of the above factory stock images
At this point, it won't even go to the boot animation. It just goes to black after the white screen that says, "Google" then reboots. If it's rebooting for the first time after a factory image flash, it reboots into stock recovery.
Tried running e2fsck -cfv on userdata and system. This is the output:
userdata:
Code:
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
userdata: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
userdata: ***** FILE SYSTEM WAS MODIFIED *****
172 inodes used (0.01%, out of 1630208)
2 non-contiguous files (1.2%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 165
146606 blocks used (2.25%, out of 6509568)
0 bad blocks
1 large file
21 regular files
141 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
------------
163 files
system:
Code:
/dev/block/platform/soc/624000.ufshc/by-name # [6n[Je2fsck -cfv system
e2fsck 1.43.3 (04-Sep-2016)
sh: badblocks: not found
/: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: ***** FILE SYSTEM WAS MODIFIED *****
2517 inodes used (1.95%, out of 129024)
13 non-contiguous files (0.5%)
4 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2310/7
472130 blocks used (91.48%, out of 516099)
0 bad blocks
1 large file
2043 regular files
273 directories
0 character device files
0 block device files
0 fifos
0 links
192 symbolic links (192 fast symbolic links)
0 sockets
------------
2508 files
Noticed something very odd about the partition table--there's no /cache! Gonna try to create it somehow.
Code:
/dev/block/platform/soc/624000.ufshc/by-name # [6nls -al
total 0
drwxr-xr-x 2 root root 1340 1970-01-01 02:09 .
drwxr-xr-x 4 root root 1440 1970-01-01 02:09 ..
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_a -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 aboot_b -> /dev/block/sda18
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_a -> /dev/block/sda29
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 apdp_b -> /dev/block/sda30
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 board_info -> /dev/block/sdf1
lrwxrwxrwx 1 root root 36 1970-01-01 02:09 boot -> /dev/block/bootdevice/by-name/boot_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_a -> /dev/block/sda19
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 boot_b -> /dev/block/sda20
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_a -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 bootlocker_b -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cdt -> /dev/block/sdd12
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib32_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 cmnlib64_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 ddr -> /dev/block/sdd11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_a -> /dev/block/sda23
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 devcfg_b -> /dev/block/sda24
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfo -> /dev/block/sdf4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 devinfobak -> /dev/block/sdd5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dip -> /dev/block/sdd7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 dpo -> /dev/block/sdd6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 frp -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsc -> /dev/block/sdd8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 fsg -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_a -> /dev/block/sda21
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hosd_b -> /dev/block/sda22
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_a -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 hyp_b -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_a -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 keymaster_b -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 metadata -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 mfg -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 misc -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_a -> /dev/block/sda25
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modem_b -> /dev/block/sda26
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 modemst1 -> /dev/block/sdd9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 modemst2 -> /dev/block/sdd10
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_a -> /dev/block/sda27
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 msadp_b -> /dev/block/sda28
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 persist -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg1fs -> /dev/block/sde3
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pg2fs -> /dev/block/sde4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 pmic_a -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 pmic_b -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ramdump -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve0 -> /dev/block/sda36
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 reserve3 -> /dev/block/sdd13
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve4 -> /dev/block/sde6
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 reserve5 -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_a -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 rpm_b -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 sec -> /dev/block/sdd4
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 ssd -> /dev/block/sdd2
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 system -> /dev/block/bootdevice/by-name/system_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_a -> /dev/block/sda33
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 system_b -> /dev/block/sda34
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_a -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 tz_b -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 userdata -> /dev/block/sda35
lrwxrwxrwx 1 root root 38 1970-01-01 02:09 vendor -> /dev/block/bootdevice/by-name/vendor_b
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_a -> /dev/block/sda31
lrwxrwxrwx 1 root root 16 1970-01-01 02:09 vendor_b -> /dev/block/sda32
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 02:09 xbl_b -> /dev/block/sdc1
Edit: NVM. Looks like the /cache partition is gone for the Pixel XL.
Do you work for the FBI?
I should also mention that I haven't been able to flash TWRP permenantly, either. I can get it to boot temporarily through fastboot but when flashing the zip in TWRP, it hangs and reboots at "Running boot image patcher on slot A". Not sure if that's because I haven't been able to get into Android and set a pin, though.
nabbed said:
Do you work for the FBI?
Click to expand...
Click to collapse
lol wut
Have you tried the Skipsoft Unified Android Toolkit? I have no association with the dev whatsoever, but I purchased the pro version, or whatever you call it, and it works flawlessly to update, install, backup, flash, etc. my Pixel.
https://skipsoft.net/skipsoft-unified-android-toolkit/
Sent from my SM-G955U using Tapatalk
Edit: double-post.
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
RT Wolf said:
I tried that out earlier today. Tried out flashing just the recovery and a 8.0 stock ROM. No joy. Doesn't even get to boot animation. Is there a particular option I should try in the pro version?
Click to expand...
Click to collapse
Have you tried to install factory update, using flash-all and edit flash-all by removing the -w
Make sure you open cmd and type fastboot reboot bootloader. Then just double click flash-all, a new cmd will open and just let it run, it will stop for a few minutes, let it sit, it will start again.
I know this is pretty old but im curious as to if anyone has had this problem and fixed it. Believe it or not Ive had this exact problem for a week now. This may seem like a joke when i say this but i actually fixed this by banging the phone against my knee out of frustration. I tried everything...diff boot slots, every factory image from 7 to 10, flash anything and everything in TWRP. TWRP would freeze anytime a ROM was flashed almost immediately. Factory images would never get passed the white screen with the single "G" on the sreen. Then one time i tapped the screen and the phone booted further. So i banged it against my knee and finshed the setup and made it to stock 8.1 with the bootloader locked *shrugs*
This kind of behavior looks like UFS failure. It's mostly caused by either condensation, liquid damage, or moisture. It can be none of these, and naturally happen with just time. The least you could try is putting it to a heat gun where the UFS chip is. If you live in US you can take it to a uBreakiFix center to repair, they know how to do chipset repair. If you dont, try to take a look around for shop, ask them if they know how to do chip repair.