Database Develop

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

ROM Flashing - Image is too large - Partition

Motorola G XT1072 -
Recovery: Clockworkmod v6.0.4.7 -
Bootloader: Unlocked
Problem: Failed in flashing rom to device.
What I did:
1. Install "Minimal ADB and Fastboot".
2. Download "mfastboot-v2" and extract it to the same directory I installed "Minimal ADB and Fastboot".
3. Deleted "fastboot.exe" to avoid possible confusion with windows.
4. Extracted the stock rom for the phone to the same directory as "Minimal ADB and Fastboot".
5. Enter the phone in Fastboot Flash Mode
6. Open "Command Prompt" in the "Minimal ADB and Fastbook" folder when the "mfastboot" and extracted ROM files are.
7. In "Command Prompt" I typed "mfastboot flash partition gpt.bin"
I get this error in "Command Prompt"
-------------------------------------------------------------------------------------------------------------------
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>
On my phone screen I get pink writing saying: VERSION DOWNGRADED FOR PRIMARY_GPT
-------------------------------------------------------------------------------------------------------------------
8. I typed "mfastboot flash motoboot motoboot.img" and get this error:
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.105s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.388s
On my phone screen I get writing saying: VERSION DOWNGRADED FOR TZ
-------------------------------------------------------------------------------------------------------------------
9. I typed "mfastboot flash logo logo.bin" and it came back as OKAY.
10. I typed "mfastboot flash boot boot.img" and it again came back as OKAY.
11. I typed "mfastboot flash recovery recovery.img" and it again came back as OKAY.
12. I typed "mfastboot flash system system.img_sparsechunk.0" and got this error:
-----------------------------------------------------------------------------------------------------------------
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261762 KB)...
OKAY [ 8.375s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.406s
On my phone screen it says: IMAGE IS TOO LARGE
-------------------------------------------------------------------------------------------------------------------
I think the partition maybe corrupted or something, possible suggestion please people.
Thanks in advanced

Please double check if you have downloaded the correct firmware zip corresponding to your phone model and region. Every region has a different firmware zip, so please verify it before downloading.

I'm positive its the right rom for my phone. I have also downloaded an EU one but get exactly the same errors. Thank you

Maybe try another custom recovery, twrp 2.8.5.0 worked perfectly for me.

thanks mate but ive tried that and still no good. Either recovery I get the same errors. Anyway to totally wipe the phone and redo the partitions?

I don´t know where but I read about the problem with too large images a few times in this forum lately....seems to be a new problem.

xt1103 Nexus 6 stuck on recovery

Hi,
i have 1 device Nexus 6 stuck on recovery
try to flash but no success always same error
i have attachment the pic as well.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4071 KB)...
OKAY [ 0.133s]
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.161s]
finished. total time: 0.296s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.674s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.523s]
finished. total time: 5.199s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
[COLOR="Red"]target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1513793712 bytes
error: update package missing system.img[/COLOR]
Press any key to exit...
any idea

Gsm UK said:
Hi,
i have 1 device Nexus 6 stuck on recovery
try to flash but no success always same error
i have attachment the pic as well.
any idea
Click to expand...
Click to collapse
Are you using the flash all.bat??
If so it doesn't work you need to flash each partition individually

Yes flash all.bat no luck
after that i have flash
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.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
all done when i press start phone reboot to recovery again .

Gsm UK said:
Yes flash all.bat no luck
after that i have flash
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.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
all done when i press start phone reboot to recovery again .
Click to expand...
Click to collapse
I remember somebody else having this problem but I dont remember what he did to correct it,somebody else wanna chime in

anybody know how to fix ?

Gsm UK said:
anybody know how to fix ?
Click to expand...
Click to collapse
Flash TWRP recovery and flash custom rom or custom stock rom. See its working or not.
Then try to flash factory images.

Code:
>fastboot flash recovery twrp-3.0.3-0-shamu.img
target reported max download size of 536870912 bytes
sending 'recovery' (11675 KB)...
OKAY [ 0.368s]
writing 'recovery'...
OKAY [ 0.183s]
finished. total time: 0.552s
just flash the twrp phone is not going to recovery when i press recovery mode its back to same screen bootloader

Are you using an old fastboot version?

I suspect his issue is related to his device. He has an engineering sample, and it's a pretty good bet that Motorola locked the /system partition down unless those files were present. A production device wouldn't be locked out like this because it's expected that owners will upgrade the firmware, but an engineering sample needs to adhere to certain parameters used in testing. Changing the ROM would violate those parameters, so when testing the test ROMs were signed.

latest version fastboot i have
really a strange issue after flashing complete phone stuck on .. fastboot
not even going recovery once i press recovery its back to fastboot

still have .. any solution .?

I fixed it by flashing latest ota zip, these latest ota zips contain the whole system instead of just the files that need to be updated.

the issue is how can i flash ota zip the phone is not going to recovery mode
even i have flash TWRP recovery

issue with flashing- Lineage 15.1

Hi Folks,
Need some help here. I'm new to flash and other stuff.
I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.
I tried below things.
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 18.385s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 18.400s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.422s]
booting...
OKAY [ 0.031s]
finished. total time: 0.469s
[PHONE GETS TWRP RECOVERY SCREENS]
I tried adb sideload as suggested in one of the pages and got this
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip
Total xfer: 0.01x
In Phone :
Starting ADB sideload feature ..
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument
Failed to unmount /system : No such volume
script aborted (no error message)
Updater process ended with ERROR: 7
Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.
Please help .. How can I overcome this and install OS in my phone.

Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.

mal13 said:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
Click to expand...
Click to collapse
Yes, I can boot into twrp using this command...
fastboot.exe boot twrp-3.2.1-0-shamu.img
This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..

I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s

vigkumar said:
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
Click to expand...
Click to collapse
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.

vigkumar said:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
Click to expand...
Click to collapse
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.

vigkumar said:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
Click to expand...
Click to collapse
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

vigkumar said:
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
Click to expand...
Click to collapse
That was your first error! You can't flash a nightly via fastboot.
You need to boot into recovery and select it there to install.

ktmom said:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Both method failed. :crying::crying:

vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

ktmom said:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.
Fastboot devices returns,
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices
ZX1G525DZX fastboot

Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.

ktmom said:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
Click to expand...
Click to collapse
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s

vigkumar said:
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Couple of questions.
You are working on a Nexus 6, right? Not a 6P or other device?
Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?
I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------
Additional question, when you reboot using only the key combination, does it always show unlocked?
If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.
If you haven't, try with the minimal version you downloaded the other day.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I

vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive
2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root @ND put TWRP on there, then flash custom Roms via TWRP

novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.

Good point. If fails on Windows, Linux PC may work

After unroot in Magisk "No command" while booting

Hi,
My brother wanted to unroot by Magisk phone and only whats happend is that while booting its No command screen. Ofc i tried factory reset and nothing.
I have installed minimal adb and drivers for x4, in device manager there is Motorola ADB Interface under Android Device.
By typing: fastboot devices, it shows my plugged phone. I downloaded official firmware but while flashing there are always errors:
fastboot flash partition gpt.bin
->
(bootloader) partitio: not found
sending 'partition' (37 KB)... and stays there forever
fastboot flash bootloader bootloader.img
->
(bootloader) max-downlo: not found
sending 'bootloader' (9520 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
fastboot flash dsp_a dspso.bin
->
sending 'dsp_a' (16384 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.005s
Any help?

Turns out, that I needed turn on my old notebook and use 2.0 usb, then it worked