Database Develop

[Q] bricked?

hey i may have messed up my nexus 6 already. unlocked the bootloader, rooted it with no problem. downloaded the twrp from play store and installed. got an install error. i looked online for someone having the issue and they said they got error and booted into recovery and it was working. i did the same. once in recovery i did a hard reset just to see if it was working, it worked. after that i hit fix permissions. and then phone would never boot. i was a little drunk so i went into recovery again, and wiped but this time i checked system. not smart i know, but what can i say. now phone boots upto google screen with unlock icon? what do i do?

Reflash factory imagine

Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

El Daddy said:
Boot into the bootloader and flash the factory image.
Follow this guide: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.

uncfan44 said:
when i downloaded factory image and flash all like in guide i keep getting an error saying fast boot is not recognized as an internal or external command. i have adb set up because when i did the test and got an adb version back.
Click to expand...
Click to collapse
Sometimes you have to install the drivers on your computer again while your phone is connected and in the boot loader.
Also, if you don't have your environment variables set up correctly, you'll have to open the command prompt from the same folder in which fastboot.exe lies. As well as putting the image files in that folder.
Sent from my Nexus 5 using Tapatalk

and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.

uncfan44 said:
and when i try to do the method 2 it says can not load file when i issue the flash bootloader command as in the guide.
Click to expand...
Click to collapse
Make sure you have fastboot selected in bootloader and try this tool to make sure fastboot is installed in your machine properly.
http://forum.xda-developers.com/showthread.php?t=2588979

ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!

uncfan44 said:
ok i went through the steps in method 2 again this time like u said with all the files in one place and got error saying data size exceeds download buffer when i went to flash the system file. phone still does the same thing where it boots to google screen whether i want it to turn on or not. ps thanks for all your help i really appreciate it!
Click to expand...
Click to collapse
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!

Make sure you have the newest fastboot and flash everything manually. If you don't have the newest fastboot it'll throw errors.

12MaNy said:
Yep. I get the same thing saying it exceeds max download size on system.img
EDIT: Nevermind. You have to wait and let it send sparse file.
Long method works great! Thanks!
Click to expand...
Click to collapse
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>

uncfan44 said:
here is my command line log maybe someone can see the error im having from this.
C:\android\platform-tools>fastboot flash bootloader C:\android\platform-tools\bo
otloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.122s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.391s]
finished. total time: 0.515s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash radio C:\android\platform-tools\radio-s
hamu-d4.0-9625-02.55.03a.img
sending 'radio' (67170 KB)...
OKAY [ 2.106s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.931s]
finished. total time: 3.039s
C:\android\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system
.img
sending 'system' (1640227 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.005s
C:\android\platform-tools>
Click to expand...
Click to collapse
You have the latest fastboot installed? Also the system image from Google was extracted to platform tools? And lastly did u check md5 of original download?
Definitely not something wrong with the commands your using.

yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.

uncfan44 said:
yep installed latest fastboot like they told me b4 and i put it in platform tools just to have it in same folder i opened cmd in, someone suggested that too i think so i did it. thats why im baffled as to y it wont work.
Click to expand...
Click to collapse
I know im a little late but you can just use wugfresh nexus toolkit and flash back to stock.

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Noob difficulty in flashing stock marshmallow

I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
Code:
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 4.620s
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.

spudbynight said:
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
Click to expand...
Click to collapse
Looks like your fastboot binary is out of date. Did you get it from the latest sdk?

I've downloaded the SDK, but (yes, noob alert) I can't figure out how to actually install it.
I've downloaded fastboot from the terminal and it says I have the latest version.

OK - I installed the SDK. I followed the instructions here
When attempting to flash it seems to go a little bit further but is still failing.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.394s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.693s]
finished. total time: 1.087s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.084s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.555s]
finished. total time: 5.639s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.15
Baseband Version.....: D4.01-9625-05.27+FSG-9625-02.104
Serial Number........: ZX1G425T8L
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8197 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.125s]
sending 'recovery' (8915 KB)...
OKAY [ 0.300s]
writing 'recovery'...
OKAY [ 0.133s]
sending 'system' (2043261 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.841s
From there I went into the "long way" and flashed the files individually from system.img
I selected recovery and rebooted. I got an Android with a red triangle but held power and volume up. The phone rebooted without me being asked to wipe data/factory reset.
Currently booted up and restoring. How do I check this is stable? I want to make sure I get OTA updates...

So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.

KnifeSkills said:
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
Click to expand...
Click to collapse
Sorry, I edited my post with an update...

This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?

spudbynight said:
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
Click to expand...
Click to collapse
Nope. Just stay 100% stock. No root, no mods.

Cheers

Suddenly hang at the "booting into fastboot" message when flashing.

Hey, I've been searching all through XDA and google to find someone with the same issue, but I can't find it. Plenty of experience flashing/rooting/etc. I've had a Pixel 4XL for a while now, never had an issue with custom roms. But lately I can't get it to take ANY flashes except official OTA sideloads or the online Android Flash Tool. Anytime I try to do a normal ./flash-all.sh it will flash normally UNTIL it hits the "booting into fastboot" (fastbootd) command. Then it will bring up the fastbootd screen and do absolutely nothing no matter how many hours you let it sit there while you resent its existence. Has anyone had experience with this? I'd really appreciate the help. Here is the full read out of my terminal when I flash (I've tried zsh and bash, i've made them executable with chmod +x, and have used them both with sudo and without):
bash-3.2$ sudo -s ./flash-all.sh
Password:
Sending 'bootloader_b' (8845 KB) OKAY [ 0.330s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.4-7617419
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 0.963s
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
Sending 'radio_b' (82708 KB) OKAY [ 2.099s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00111-210817-B-7650554
(bootloader) Flashing partition modem_b
OKAY [ 0.617s]
Finished. Total time: 3.006s
Rebooting into bootloader OKAY [ 0.079s]
Finished. Total time: 0.079s
Erasing 'avb_custom_key' OKAY [ 0.220s]
Finished. Total time: 0.370s
Sending 'avb_custom_key' (1 KB) OKAY [ 0.140s]
Writing 'avb_custom_key' OKAY [ 0.231s]
Finished. Total time: 0.590s
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
--------------------------------------------
Bootloader Version...: c2f2-0.4-7617419
Baseband Version.....: g8150-00111-210817-B-7650554
Serial Number........: 9A251FFBA00481
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.070s]
Setting current slot to 'b' OKAY [ 0.079s]
extracting boot.img (64 MB) to disk... took 0.224s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 1.670s]
Writing 'boot_b' OKAY [ 0.431s]
extracting dtbo.img (8 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.121s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_b' OKAY [ 0.077s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.140s]
Writing 'vbmeta_system_b' OKAY [ 0.077s]
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.070s]

I forgot to mention that I've also manually flashed a bunch of bootloaders and boot images to see if would help, but still nothing. Also twrp doesn't load when I boot a twrp img.

ashtonv59 said:
I forgot to mention that I've also manually flashed a bunch of bootloaders and boot images to see if would help, but still nothing. Also twrp doesn't load when I boot a twrp img.
Click to expand...
Click to collapse
I have nothing to offer but the obvious which is to confirm the latest binaries, new data cable (not C-C) and try a different (windows) machine you have adb/fastboot set up on. With an unlocked bootloader, flashing the untouched script/batch file should return ANY device to the OOB state.

v12xke said:
I have nothing to offer but the obvious which is to confirm the latest binaries, new data cable (not C-C) and try a different (windows) machine you have adb/fastboot set up on. With an unlocked bootloader, flashing the untouched script/batch file should return ANY device to the OOB state.
Click to expand...
Click to collapse
I actually figured it out last night. I still don't know the cause of it, but if anyone ever has this issue this is the solution.
Extract the download. Notice there is a ZIP FILE (this is important as it is the userspace data for each partition) within the extracted folder along with the bootloader, radio, flash-all, flash-base, etc. Execute the flash-all script like normal. It will hang like I described. Once fastbootd loads, hit CTRL+C so you have control of your terminal again. Type the command
Code:
fastboot update -w ZIPFILETHATIMENTIONEDEARLIER.ZIP
MAKE SURE YOU TYPE -w, otherwise the phone will hang on the Google logo screen until you turn it off. The reason the phone gives is the "no valid boot slot" message. Anyway, once you hit enter after that command, you'll see it flash each partition, then it boots the system automatically. BOOM you'll be at the setup screen in no time.
I don't know why it hangs. It seems to related to my computer or terminal. I have the newest MacBook Air. But yeah, that's the solution. Happy flashing. I hope this might help people in the future.
Peace out.

@ashtonv59
Glad you got things working. That line is already in the untouched script (and the DOS *.bat file) The -w flag is an instruction to wipe the user data partition. This flag is often removed by users to "dirty flash" or otherwise update without losing their data. For users like me who manually update every single month using the full factory image, it is always removed. Leaving the -w flag in (or using it manually on the command line is used to remedy flashing issues when all else fails and the user is willing to lose all their data.

See below reply.

v12xke said:
@ashtonv59
Glad you got things working. That line is already in the untouched script (and the DOS *.bat file) The -w flag is an instruction to wipe the user data partition. This flag is often removed by users to "dirty flash" or otherwise update without losing their data. For users like me who manually update every single month using the full factory image, it is always removed. Leaving the -w flag in (or using it manually on the command line is used to remedy flashing issues when all else fails and the user is willing to lose all their data.
Click to expand...
Click to collapse
Yeah, the problem though is the script only actually executes the first part, what would be considered flash-base.sh. Since the terminal hangs when it boots to fastbootd, it never executes the the userspace update, let alone the -w variable at the end of the script. So since you have to manually execute
Code:
fastboot update
, you also have to manually add the
Code:
-w
variable in:
Code:
fastboot update -w USERSPACEZIP.zip
, or else you still have a pretty paperweight. It's an easy thing to overlook, but it is absolutely necessary to successfully flash and have a functioning device.

Question Help Recovering Data From Device with no Display/Touch

Hi there. My Pixel 5a has a motherboard issue, and needs to be returned to Google for warranty. I am trying to recover my files from the device before I send it in, but I'm having issues. For some reason, even though I have enabled usb debugging and issued commands through this laptop before, it says adb unauthorized when I issue the command "adb devices". So I downloaded my factory image, removed the "-w" from the flash all bat file, and attempted to flash to see if that would fix issue. However, it appears that for some reason I'm missing fastboot d. Here is the screen I get when attempting to flash.
Sending 'bootloader_b' (8762 KB) OKAY [ 0.122s]
Writing 'bootloader_b' (bootloader) Flashing Pack version b9-0.4-7758098
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition featenabler_b
(bootloader) Flashing partition logfs
OKAY [ 0.343s]
Finished. Total time: 0.771s
Rebooting into bootloader OKAY [ 0.029s]
Finished. Total time: 0.056s
Sending 'radio_b' (149780 KB) OKAY [ 0.970s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g7250-00161-211008-B-7807492
(bootloader) Flashing partition modem_b
OKAY [ 0.782s]
Finished. Total time: 2.058s
Rebooting into bootloader OKAY [ 0.038s]
Finished. Total time: 0.053s
--------------------------------------------
Bootloader Version...: b9-0.4-7758098
Baseband Version.....: g7250-00161-211008-B-7807492
Serial Number........: 19241JEG503250
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.061s]
Checking 'version-bootloader' OKAY [ 0.057s]
Checking 'version-baseband' OKAY [ 0.055s]
Setting current slot to 'b' OKAY [ 0.071s]
extracting boot.img (96 MB) to disk... took 0.384s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 0.623s]
Writing 'boot_b' OKAY [ 0.472s]
extracting dtbo.img (16 MB) to disk... took 0.104s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (16384 KB) OKAY [ 0.192s]
Writing 'dtbo_b' OKAY [ 0.120s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.126s]
Writing 'vbmeta_b' OKAY [ 0.062s]
extracting vbmeta_system.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.122s]
Writing 'vbmeta_system_b' OKAY [ 0.059s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.536s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot_b' (98304 KB) OKAY [ 0.625s]
Writing 'vendor_boot_b' OKAY [ 0.469s]
extracting super_empty.img (0 MB) to disk... took 0.002s
Rebooting into fastboot OKAY [ 0.049s]
< waiting for any device >
And then it hangs there indefinately. The only way I can get out of here is by pressing the power and volume down simutaneously. Then the dialogue adds this line
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Press any key to exit...
Can anyone help me get to a point where I can recover my data? Please, and thanks in advance.

Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.

danielhatzor said:
Edit: Was obviously assuming your bootloader is unlocked, but I guess it's not your case if your'e returning your phone to Google.
Experiencing a similar problem. adb unauthorized means you need to approve the adb connection on the android device, which you unfortunately can't.
If you haven't set a password/pin/pattern on your lock screen and your data is not encrypted you can:
1. Reboot to bootloader (Power + volume down for 15-20 seconds)
2. Use fastboot to boot TWRP (Do not flash)
3. Use ADB there
However if you have set a lock screen password/pin/pattern then your data will be encrypted and you wont be able to decrypt it as TWRP does not support encryption/decryption for A12+. What you can probably do is backup your encrypted data partition to your PC (Using the twrp command in shell) and restore it when your phone is back.
Click to expand...
Click to collapse
Hi there, thanks for responding. Actually, yes, my bootloader is unlocked. The phone is rooted. I have enabled usb debugging in the past, but for some reason it is still unauthorized. I currently cannot even get the os to boot, but I cannot figure out why because no screen. When I try to flash the factory image, removing the "-w" so my data isn't wiped, the process hangs att the portion where it boots to fastbootd and will not go any further.
I'm going to try to boot into twrp again. I seem to remember that I tried this, but let's see.
If you have any other info or advice, it would be greatly appreciated.
Edit: I just tried to boot into twrp, and I get an error message. It is : (bootloader) boot.img missing cmdline or OS version
I have attached a picture of the command line messages. Maybe someone here can see something that would point to something that would help

Is it possible you flashed an incompatible / corrupted factory image for your phone?
https://www.reddit.com/r/LineageOS/comments/kn257b

Yeah, I just went and double checked, and then reflashed to see. I def have the July barbet image, which is for the 5a, my device. It just won't work.
Google is trying to get me to either take the device to ubreakifix, which when I try tell me that they do not do motherboard issues, or send the device to them, which I am hesitant to do because I feel they are going to wipe the device. Very frustration situation. I've always used nexus/pixel devices becuase of the readily available info on here, but this just doesn't seem to be a popular development device, and I can't seem to find a way. I know there is some command or series of commands that will fix this issue, I just can't seem to find it.
Thank you again for replying and attempting to help. Truly appreciated. Hopefully someone will stumble across this and let me know.