Develop Bugs

[Q] Not booting anymore and no recovery

Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?

myxor said:
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
Click to expand...
Click to collapse
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.

beekay201 said:
Drop the toolkit, learn how to it proper or stop flashing stuff before you hurt your device.
Click to expand...
Click to collapse
I guess it's already to late
I just tried to install the CWM Recovery via fastboot
D:\gn\adt-bundle-windows-x86_64
sending 'recovery' (6214 KB)...
OKAY [ 0.631s]
writing 'recovery'...
OKAY [ 0.759s]
finished. total time: 1.392s
D:\gn\adt-bundle-windows-x86_64
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
But when i select Recovery from the bootloader menu i only get the charging battery icon.
Anything i can do?

I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.

iLeopard said:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
Click to expand...
Click to collapse
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:

Was this issued using flash-all.bat?
Sent from my Galaxy Nexus using xda app-developers app

myxor said:
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Click to expand...
Click to collapse
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?

beekay201 said:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
Click to expand...
Click to collapse
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:

myxor said:
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
Click to expand...
Click to collapse
Use omapflash to restore your bootloader. See this thread's post with useful links. http://forum.xda-developers.com/showthread.php?t=1812959

I sent in the device to the repair and got it back a few days ago.
Some "broken parts" were changed and i got a new battery.
Now my Galaxy Nexus works again like a charm
Don't really know what parts were broken but it seemed that it was a hardware failure.
Thanks to everyone who helped! :good:

[Q] Blinking Android Error Screen

I installed the new update on my rooted phone accidentally and it went into a bootloop. I went into recovery mode and clicked erase cache, but my phone died before it was done erasing. Now whenever I start my phone after the ASUS loading screen, and sleeping android with a red warning signal and the text 'ERROR' start flashing every three seconds. I can get to the bootloader screen fine, but when I click recovery mode and the phone restarts, its just shows the blinking android error screen and I can get the recovery mode option by pressing power+up.
When plugged into my computer, adb doesn't recognize a device is connected (I have all the drivers). So I'm stuck right now.
Please any help would be greatly appreciated!

Same thing happened to me, finally while in the bootloader I used fastboot to restore it, I used the big ZIP file from Asus website and did a fastboot sideload of it

fastboot?
How do I go into fastboot from bootloader?
Thanks!

You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.

Next
Magister54 said:
You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.
Click to expand...
Click to collapse
kk perfect it shows my device, what do I exactly type to sideload the zip? I placed the zip file in the adb folder. Do I type 'adb sideload xxx.zip' ?

argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first

Magister54 said:
argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first
Click to expand...
Click to collapse
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh

G0BI said:
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh
Click to expand...
Click to collapse
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!

Blinking Error Screen
rlaw said:
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!
Click to expand...
Click to collapse
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.

G0BI said:
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.
Click to expand...
Click to collapse
No, it's not a problem! I thought it was as well, no worries - easy mistake to make, especially since getting into recovery mode from that screen can be tricky!

Easy way
Works with problems regarding wipe cache sudden hang or reload and showing android robot with "error" message + no recovery options avilable.
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
get zenfone 2 into fastboot mode (volume + and power) and connect to your windows machine (usb)
install adb drivers and 15 sec package from the link
now go to c: drive and find the abd folder
in that drag fastboot and drop in command prompt *(administrator)
now type fastboot device
you sholud see a device
then type
1) fastboot erase cache
2) fastboot reload
now phone will restart and show error then remove usb cable and switch off the phone
after 10 sec turn on the phone and you will be back...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@varunanduri.......... You are a GOD! Nothing from the web helped me except this comment.

Hello.
I need your help.
I bought this phone (Asus Zenfone 2 ZE551ML 4GB/32GB 1.8Ghz) recently on online store. It is CN version but it already came with WW firmware, but not the latest (I believe it was WW 2.20.40.90 but I'm not sure).
Then I tried to update to the latest WW version 2.20.40.139 by putting firmware zip file from asus site in internal memory. The phone recognized this update and started to upgrade. When it reboot, I got an error of a blinking droid with the word "Error" below, and the phone doesn't boot anymore.
I can get to fastboot mode, but no to recovery mode. When trying to enter recovery, I got some errors (cannot mount /cache...) and it goes back to the blinking droid.
I cannot insert images and urls so the text errors include E:failed to mount /cache (Invalid Argument) various times
In fastboot mode I tried erase cache, format cache, format userdata, flashing latest WW recovery, boot, fastboot and system, but nothing resolved issue of blinking droid with error.
I tried other how to that uses a CWM recovery and I can get to that recovery, can clean and wipe, tried installing asus zip firmware from external sd (WW and CN) but without success (I believe it had CN recovery SKU but WW firmware -is this possible?). After rebooting the phone is still in the same error (blinking droid).
Here is fastboot messages (format userdata gave an error):
Code:
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 0.470s]
finished. total time: 1.080s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.450s]
finished. total time: 1.060s
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.700s]
writing 'fastboot'...
OKAY [ 0.460s]
finished. total time: 1.170s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.220s]
sending sparse 'system' (524056 KB)...
OKAY [ 18.310s]
writing 'system'...
OKAY [ 11.970s]
sending sparse 'system' (517822 KB)...
OKAY [ 17.540s]
writing 'system'...
OKAY [ 12.340s]
sending sparse 'system' (520627 KB)...
OKAY [ 17.560s]
writing 'system'...
OKAY [ 10.890s]
sending sparse 'system' (522703 KB)...
OKAY [ 17.630s]
writing 'system'...
OKAY [ 10.910s]
sending sparse 'system' (154528 KB)...
OKAY [ 5.450s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 127.320s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.110s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.490s]
finished. total time: 0.490s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.390s]
sending 'cache' (6248 KB)...
OKAY [ 0.410s]
writing 'cache'...
OKAY [ 0.390s]
finished. total time: 1.190s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.410s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.290s]
sending 'userdata' (139033 KB)...
OKAY [ 4.600s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 9.180s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.370s]
sending 'cache' (6248 KB)...
OKAY [ 0.420s]
writing 'cache'...
OKAY [ 0.380s]
finished. total time: 1.170s
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.050s]
sending 'userdata' (139033 KB)...
OKAY [ 4.490s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 8.840s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.108s
C:\adb>
Is there a way to get the phone working again?
Thank you very much.

After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.

KillerNo2 said:
After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.
Click to expand...
Click to collapse
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.

cdiogooliveira said:
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.
Click to expand...
Click to collapse
I think you should've updated to version .97 first. So download .97 recovery from here,and try it again.

Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.

cdiogooliveira said:
Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.
Click to expand...
Click to collapse
It works now.

KillerNo2 said:
It works now.
Click to expand...
Click to collapse
Hello. Recovery .97 didn't work also. It has always the blinking droid and doesn't boot.
I could run tethered (without install) TWRP recovery and tried to install full zip rom, but TWRP couldn't also access /cache partition. TWRP cannot mount cache and system partitions.
Anyone can help?
Thank you very much.

How to flash factory image?

I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?

Drivers. Search on how to verify your drivers are up to date and installed.

Am I able to flash the images separately though? I do I have to use the flash all script?

swapavi said:
Am I able to flash the images separately though? I do I have to use the flash all script?
Click to expand...
Click to collapse
Not usually.
And some dev's hate the bat due to Windows being stupid sometimes.
Many folks will flash individual files one at a time.
I however, am unfamiliar with the Pixel XL partition setup too, so I would totally wait for a higher level dev to come along and answer before I do anything.
I actually posted a similar question in the factory images thread over on the development sub forum for Pixel XL.

I am also having issue flashing the marlin-nde63p using the flash-all.bat with the 128GB Pixel XL phone from google. It keeps erroring out with the following [FAILED (remote: partition [boota] doesn't exist)]. Anyone know how to fix this?
C:\pixelxl\marlin-nde63p>
C:\pixelxl\marlin-nde63p>flash-all
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.823s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.046s]
finished. total time: 1.877s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.018s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.349s]
writing 'radioa'...
OKAY [ 0.895s]
finished. total time: 2.251s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.018s
< 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........:XXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.047s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boota' (26481 KB)...
OKAY [ 0.689s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.156s
Press any key to exit...

Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing

jscharf10 said:
Ok I literally just did this because I messed up my pixel xl 128gb after rooting it today.
First off I had my luck with minimum adb and fastboot, install it and go to your computer and find where its downloaded. (Ex. Mine was in C:> programs x86> minimal adb and fastboot folder). After you have located, find you image you just downloaded from Google and extract the files there should be 6 (I am a Verizon user and used the H update from the Google site). Copy all those 6 extracted files into that folder you located earlier (minimal adb and fastboot) and just click on the flash-all file you just dropped in there an sit back and let it do its thing
Click to expand...
Click to collapse
------------------------------
hi all semi-noob here... pls excuse any silly comments i make
background - i have twrp installed on my vzn pixel xl... bootloader is unlocked
so i copied all the 6 extracted files into the minimal adb and fastboot folder
i ran the flash-all file
cmd window popped up and just says "< waiting for any device >"
my phone is plugged into my pc via usb cable
question - what mode do i need to be in to flash the factory image?

@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!

jscharf10 said:
@peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
[/COLOR @peterlee928
2 simple things to make sure one you have all your drivers installed and two that you are in bootloader mode!
Click to expand...
Click to collapse
thx jscharf

Use The Unified Android Toolkit
swapavi said:
I'm not new to flashing the images... But Jesus Christ there's a lot going on with the pixel... There's not just a system, vendor, boot, recovery, and cache IMG now... There's a ****load and I'm not sure how to flash them... And when I run the flash all.bat I keep getting an error during the flash and it just pauses... Same goes for the skipsoft tool. Anyone know how to flash these?
Click to expand...
Click to collapse
I had the exact same issue that you are having, another user on here recommended that I use the Unified Android Toolkit to flash the factory image. It works perfectly, and also has a bunch of other useful features (some will be more useful as the community figures out this system partition thing).
The toolkit is great and no necessary features must be paid for. This will solve your error issue. Best of luck!
Find the toolkit here: https://skipsoft.net/

Can't Get Partitions to Mount After TWRP/Root

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

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'
Erimary 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)

Nobody has anything? .... Am I just screwed?

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.

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.

Cause your not gonna be using twrp to flash stock images. You need to go through bootloader and use fastboot.

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

try this
trout_of_death said:
Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.
Click to expand...
Click to collapse
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.

trout_of_death said:
Any good walkthroughs on flashing stock back on the phone then? Sorry for being a complete noob on this.
Click to expand...
Click to collapse
Actually, best bet is following directions here:
https://developers.google.com/android/images
because OTA is for updating, where factory image flash-all may be a more complete method.
Sent from my sailfish using XDA Labs

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...

trout_of_death said:
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...
Click to expand...
Click to collapse
When you flashed/fastbooted the twrp image did you install the two you flashed/fastbooted?

I'm not sure I understand the question?

In rereading the TWRP instructions, yes I booted to the img and ran the zip.

I fixed the issue with not being able to decrypt my partitions by fastbooting to the twrp image again.

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?

trout_of_death said:
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?
Click to expand...
Click to collapse
Is your bootloader still unlocked. Can you still boot to bootloader.

Bootloader is still unlocked, not I can't boot to bootloader.

I'm within my return window, I'm thinking about returning the phone to Google. Thoughts?

trout_of_death said:
Bootloader is still unlocked, not I can't boot to bootloader.
Click to expand...
Click to collapse
trout_of_death said:
I'm within my return window, I'm thinking about returning the phone to Google. Thoughts?
Click to expand...
Click to collapse
You can't boot bootloader with power and volume buttons? Does the phone turn on at all.

toknitup420 said:
You can't boot bootloader with power and volume buttons? Does the phone turn on at all.
Click to expand...
Click to collapse
No, it's bricked. When I plug it into my computer I get the chipset as a device, no ADB or anything.

Google Pixel XL - Soft Brick

Hi all!
I'm not so called an "expert" on android. (I work normally on Linux ) so, my *final* goal is to install a custom rom on Google Pixel XL (marlin).
For the moment i'm trying to install the official google 8.1.0 (OPM1.171019.016, Feb 2018).
I carefully followed these 4 links:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
I unlocked and rooted the "marlin" with no problems.
I installed TWRP (twrp-3.2.1-0-marlin): it works but seems do not persist and every time i want to use it i have to reinstall via fastboot (strange... what i missed?).
This is the guide followed: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I downloaded the official rom google 8.1.0 (OPM1.171019.016, Feb 2018) following these guides:
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
With flash-all-sh and OPM1.171019.016, Feb 2018 give me this error " fastboot too old " ( adb version revision 1:7.0.0+r33-2 )
If i write into shell this procedure at a certain point all stops and an error appears:
.......
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist) <----this
finished. total time: 1.801s
Please, what i did wrong?
how to recover this error?
how to make persistent TWRP?
Anyway, is it possible that the 8.1.0 version is too new for my configuration?
Thanks a lot for any advice!
Lele
Log
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (30149 KB)...
OKAY [ 1.404s]
writing 'boot_a'...
OKAY [ 0.695s]
finished. total time: 2.100s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30149 KB)...
OKAY [ 1.381s]
writing 'boot_b'...
OKAY [ 0.694s]
finished. total time: 2.076s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash bootloader bootloader-marlin-8996-012001-1711291800.img
target reported max download size of 536870912 bytes
sending 'bootloadera' (32248 KB)...
OKAY [ 1.505s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.811s]
finished. total time: 17.317s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash radio radio-marlin-8996-130091-1710201747.img
target reported max download size of 536870912 bytes
sending 'radioa' (57320 KB)...
OKAY [ 2.613s]
writing 'radioa'...
OKAY [ 1.053s]
finished. total time: 3.666s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot -w update image-marlin-opm1.171019.016.zip
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: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1710201747
Serial Number........: HT69H0207206
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.801s

UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele

Chancellor said:
UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele
Click to expand...
Click to collapse
Make sure you have the latest fastboot and ADB.
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.

borxnx said:
Make sure you have the latest fastboot and ADB.
Click to expand...
Click to collapse
adb version revision 1:7.0.0+r33-2 it's the latest version?
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.
Click to expand...
Click to collapse
ok i will do it
Thank you

Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk

Hi There.
After you installed fastboot and adb on linux (I installed adbLink for my aftv from https://www.jocala.com/ and that brings the necessary files, too. It creates a directory called adbfiles, where you can use ./adb and ./fastboot devices - worked for me), you can boot into recovery and install the 8.1.0 version for the pixel from here:
https://developers.google.com/android/ota -- you need marlin and 8.1.0 (OPM1.171019.016, Feb 2018). mv the image to the directory with the adbfiles. I find this way the easiest.
The update can easily be installed if you boot into fastboot and there chose apply update from adb and then follow the instructions on your mobile or steps 2 - 8 from the download page.
That is to update your firmware to 8.1.0 - twrp install comes after that.

OK friend, i will try !!! Thank you
borxnx said:
Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse