• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Can't Get Partitions to Mount After TWRP/Root

Search This thread
Feb 6, 2013
17
1
Good Afternoon,

I got the Google Pixel XL from Google's Play Store. I unlocked the bootloader, installed TWRP, and tried to root the phone. I'm not sure what happened, but TWRP is now not asking me for my pin and not of my partitions /data /system /vendor are mounting. I'm thinking because the device is encrypted. Is there a way to force the pin unlock on TWRP?

Not sure what to do here...

Thanks,

Chris
 
Feb 6, 2013
17
1
The following is what TWRP is displaying when I try to select slot A or B for rebooting.

E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/system_image'
E:Unable to find partition size for '/vendor_image'
E:Unable to find partition size for '/misc'
E:Unable to find partition size for '/efs2'
E:Unable to find partition size for '/efs2'
E:primary block device '/dev/block/bootdevice/by-name/userdata' for mount point '/data' is not present!
E:Unable to set bootloader message
Updating partition details...
Failed to mount '/system' (Invalid Argument)
Failed to mount '/vendor' (Invalid Argument)
Failed to mount '/data' (Invalid Argument)
 

rustyjay

Senior Member
Jun 28, 2012
838
1,528
riverside
Flash stock images and start over.
If you set a pin in rom it will ask for it to decrypt your data. If you dont have the pin it wont decrypt and have issues like your having.
Nexus's or excuse me pixels are forgiving phones ha.
 
Last edited:
Feb 6, 2013
17
1
TWRP is not asking me for a PIN but I set a PIN. I was asking me for a PIN, then I tried to flash the stock rom and it booted into twrp w/o prompting for a PIN.

How can I flash a stock ROM if the phone doesn't have a partition for me to push the file to? It's showing 0mb available on the internal storage. I tried a USB OTG and it didn't recognize it either.
 

michaelbsheldon

Senior Member
Jan 12, 2011
785
231
Anaheim, CA
try this

Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.

Go to "https://developers.google.com/android/ota" and download the OTA you need. (X for Verizon)
Copy the OTA zip file to the same folder that ADB/Fastboot is in.
Reboot phone to the bootloader (Hold Power and Volume Down while powering on the phone) Use the volume keys and choose recovery.
Or at the No Command screen hold power and while holding power press and hold volume up for about 5 seconds, let go of volume up and power and it should take you to Recovery.
Choose "Update from ADB" in Recovery.
Open command prompt on your pc in folder that has fastboot and adb.
enter: adb sideload name_of_ota.zip (Replace name_of_ota with the correct file name.) (Don't have two " .zips" at end of name)
This will take a few minutes and will fix you up.
 
Feb 6, 2013
17
1
Thanks, but I keep getting "Could not find 'META-INF/com/google/android/update-binary' in the zip file." for every OTA zip. I didn't try the verizion one as this is not a verizon phone.

Best way to learn how to fix a device is to break it first right? haha...

I downloaded the factory NDE63P image from this link (https://developers.google.com/android/images) and ran the flash-all.bat. Below is what was ran and now I'm stuck at the loading screen.

C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.825s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.139s]
finished. total time: 1.965s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.434s]
writing 'radioa'...
OKAY [ 0.948s]
finished. total time: 2.383s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT6AW0201XXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26481 KB)...
OKAY [ 0.691s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.150s
Press any key to exit...
 

Veid71

Senior Member
Apr 1, 2015
550
42
OnePlus 9 Pro
Thanks, but I keep getting "Could not find 'META-INF/com/google/android/update-binary' in the zip file." for every OTA zip. I didn't try the verizion one as this is not a verizon phone.

Best way to learn how to fix a device is to break it first right? haha...

I downloaded the factory NDE63P image from this link (https://developers.google.com/android/images) and ran the flash-all.bat. Below is what was ran and now I'm stuck at the loading screen.

C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.825s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.139s]
finished. total time: 1.965s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.005s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.434s]
writing 'radioa'...
OKAY [ 0.948s]
finished. total time: 2.383s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 122633060352
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29939712
Block groups: 914
Reserved block group size: 1024
Created filesystem with 11/7487488 inodes and 518062/29939712 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: HT6AW0201XXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.049s]
sending 'boota' (26481 KB)...
OKAY [ 0.691s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.150s
Press any key to exit...

When you flashed/fastbooted the twrp image did you install the two you flashed/fastbooted?
 
Feb 6, 2013
17
1
So.... I tried to install the factory image.... now my phone is bricked and I have the Qualcomm HS-USB QDLoader 9008 in device manager.... anyone have the BoradDiag for Pixel Xl or the Image Files?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    try this

    Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.

    Go to "https://developers.google.com/android/ota" and download the OTA you need. (X for Verizon)
    Copy the OTA zip file to the same folder that ADB/Fastboot is in.
    Reboot phone to the bootloader (Hold Power and Volume Down while powering on the phone) Use the volume keys and choose recovery.
    Or at the No Command screen hold power and while holding power press and hold volume up for about 5 seconds, let go of volume up and power and it should take you to Recovery.
    Choose "Update from ADB" in Recovery.
    Open command prompt on your pc in folder that has fastboot and adb.
    enter: adb sideload name_of_ota.zip (Replace name_of_ota with the correct file name.) (Don't have two " .zips" at end of name)
    This will take a few minutes and will fix you up.
    1
    Nobody has anything? .... Am I just screwed?