Related
folks
I installed N preview 4 on my nexus 6 and it seemed successful but it's constantly booting back into recovery. What do I do so it boots into the actual OS?
Thanks
sam008 said:
folks
I installed N preview 4 on my nexus 6 and it seemed successful but it's constantly booting back into recovery. What do I do so it boots into the actual OS?
Thanks
Click to expand...
Click to collapse
reflash
Already did, didn't help
how are you flashing N?
Do a factory reset from recovery, that might help.
Edit: I'm assuming you're on stock recovery.
---------- Post added at 04:22 PM ---------- Previous post was at 04:21 PM ----------
simms22 said:
how are you flashing N?
Click to expand...
Click to collapse
This... what did you exactly do?
This phone has had quite a few modifications - it ran cataclysm before. Bootloader is unlocked. Then it ran preview 3. Now, I did a factory reset first and then did a flash-all using instructions on method 2 of this page
forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
On rebooting, it always comes back to Recovery (TWRP 3.0.2-2)
From recovery, I tried doing Reboot-System and it still comes back into recovery
Should I try flashing stock firmware - can someone provide me a link?
Thanks
sam008 said:
This phone has had quite a few modifications - it ran cataclysm before. Bootloader is unlocked. Then it ran preview 3. Now, I did a factory reset first and then did a flash-all using instructions on method 2 of this page
forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
On rebooting, it always comes back to Recovery (TWRP 3.0.2-2)
From recovery, I tried doing Reboot-System and it still comes back into recovery
Should I try flashing stock firmware - can someone provide me a link?
Thanks
Click to expand...
Click to collapse
the latest 6.0.1, it flashes the same way https://dl.google.com/dl/android/aosp/shamu-mob30m-factory-55e10749.tgz
I have the version of nexus 6 - will this link work or should I use another one? thx
Strange error at the end - I opened image-shamu-mob30m and it seems it does have all the required .img files
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.328s]
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.567s]
finished. total time: 0.898s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 4.698s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.524s]
finished. total time: 6.227s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2098202380 bytes
error: update package missing system.img
Press any key to exit...
It does have all the required img. How are you flashing it?
I flash it manually file by file and it never fails.
sam008 said:
Strange error at the end - I opened image-shamu-mob30m and it seems it does have all the required .img files
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.328s]
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.567s]
finished. total time: 0.898s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
sending 'radio' (115508 KB)...
OKAY [ 4.698s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.524s]
finished. total time: 6.227s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2098202380 bytes
error: update package missing system.img
Press any key to exit...
Click to expand...
Click to collapse
instead of using flash-all, flash each partition separate.
Flash all doesn't work. Flash each partition.
Eg:
Fastboot flash bootloader bootloader-xxx. Img
Fastboot reboot-bootloader
Fastboot flash radio radio-xxx.img
Fastboot reboot-bootloader
Fastboot flash recovery recovery.img
..... And so on.....
Sent from my Nexus 6 using Tapatalk
mannrecaged said:
Flash all doesn't work. Flash each partition.
Eg:
Fastboot flash bootloader bootloader-xxx. Img
Fastboot reboot-bootloader
Fastboot flash radio radio-xxx.img
Fastboot reboot-bootloader
Fastboot flash recovery recovery.img
..... And so on.....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The flash-all.bat file DOES work as long as you have the latest version of Fastboot, which can be obtained by following the instructions under "Flashing Instructions" here. That being said I prefer to flash each image file separately as mentioned above. That method has never failed me and it is easier to see what the error is if any occur.
I just used the flash-all.bat file
Hi guys.
My little cousin got an old XT1058 and he was very happy playing that new Pokemon game. Unfortunately, yesterday he come with the phone in bootloop.
Whats is hapennig:
Phone start boot procedure and a few seconds after animation is shown the phone turn off. I'm able to enter in fastboot mode.
What I tried so far:
- factory reset, wipe cache
- restore to 5.1 stock ROM
I live in Brasil, so this ROM was used XT1058_GHOST_RETBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml
Tried this 4.4.4 ROM but couldn't write it, it seens to be some sort of protections to prevent an older ROM to be installed XT1058_RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF
- install custom recovery
TWRP and CWM: both write fine but when I try to enter in recovery right after the install process stock recovery is shown. I even tried erasing recovery before writing custom and writing custom two times.
What I didn't tried so far:
- that procedure envolving RIFFBOX/QHSUSB_DLOAD drivers. I think it's for a last resource and at least in my case (fastboot working) would need opening and putting some test point to ground to enter in some special mode.
Maybe it can be useful, but in fastboot is shown:
AP Fastbooot Flash Mode (S)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
and
Device is UNLOCKED Status Code: 3
Battery OK
I would like to ask if anyone could please help me to make this kido happy again! Thanks in advance.
are you sure it is xt1058? check back of the phone or go to bootloader and check barcodes or "mfastboot getvar all"
if bootloader is unlocked, there are plenty of chances your phone will come back to life.
jameeldroid said:
are you sure it is xt1058? check back of the phone or go to bootloader and check barcodes or "mfastboot getvar all"
if bootloader is unlocked, there are plenty of chances your phone will come back to life.
Click to expand...
Click to collapse
Hi! I'm sorry for taking so much time to reply. I was working outside my area and I couldn't check those infos.
Here is a screenshot of "get var all":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for helping!
That var "product: ghost" comes from the hardware itself or it's coded on software? I mean, how could I say if it's really an XT1058?
That one is from software, the hardware one is SKU which has blanked out right now due to wrong flash maybe.
jameeldroid said:
That one is from software, the hardware one is SKU which has blanked out right now due to wrong flash maybe.
Click to expand...
Click to collapse
Is there anythning I could try?
dolence said:
Is there anythning I could try?
Click to expand...
Click to collapse
did you try to flash a Marshmallow rom such as AICP?
dolence said:
Is there anythning I could try?
Click to expand...
Click to collapse
Not yet. Would be possible to flash this ROM using stock recovery? Because everytime I flash CWM or TWRP it seens to be overwrited by stock. Even if I boot right after flashing it.
Trying to flash it via adb sideload. I will report back in a few minutes.
UPDATE: fail.
Oh, in the back of the phone I found the model. It was very hard to read but it says:
XT1058 ANATEL MODEL NO. 1323-13-0330
FCC ID IHDT56PA1 TYPE MODD7
dolence said:
Not yet. Would be possible to flash this ROM using stock recovery? Because everytime I flash CWM or TWRP it seens to be overwrited by stock. Even if I boot right after flashing it.
Click to expand...
Click to collapse
Can you mention other carrier names from BR? It will help find the right rom for your phone.
There must be Anatel specific rom for this because the one you flashed RETBR is not working.
Anatel is our regulatory agency. Main carriers are Vivo, Tim, Oi, Nextel and Claro. Thanks for helping.
Is there anything else I could try?
1. Initially Flash all Images using Fastboot except system image (system.img)
2. Flash TWRP in the same process, Reboot in recovery.
3. Now when TWRP is opened, wipe all (data, cache, delvik) and Perform a Factory Reset.
4. Reboot Device in Bootloader again, Now Flash System Image(system.img) and stock recovery (optional, only if u want stock recovery).
5. Reboot
(Strictly use the Images/Files meant for your Device Model.)
vijayid_94 said:
1. Initially Flash all Images using Fastboot except system image (system.img)
2. Flash TWRP in the same process, Reboot in recovery.
3. Now when TWRP is opened, wipe all (data, cache, delvik) and Perform a Factory Reset.
4. Reboot Device in Bootloader again, Now Flash System Image(system.img) and stock recovery (optional, only if u want stock recovery).
5. Reboot
(Strictly use the Images/Files meant for your Device Model.)
Click to expand...
Click to collapse
Code:
C:\adb fastboot mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.113s]
finished. total time: 0.115s
C:\adb fastboot mfastboot>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.259s]
writing '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
OKAY [ 0.442s]
finished. total time: 0.706s
C:\adb fastboot mfastboot>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.028s]
finished. total time: 5.401s
C:\adb fastboot mfastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (245 KB)...
OKAY [ 0.319s]
writing 'logo'...
OKAY [ 0.856s]
finished. total time: 1.179s
C:\adb fastboot mfastboot>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.947s]
writing 'boot'...
OKAY [ 1.337s]
finished. total time: 2.288s
C:\adb fastboot mfastboot>fastboot flash recovery twrp-2.8.7.0-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
finished. total time: 1.783s
C:\adb fastboot mfastboot>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54272 KB)...
OKAY [ 3.710s]
writing 'modem'...
OKAY [ 2.395s]
finished. total time: 6.110s
C:\adb fastboot mfastboot>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.447s]
finished. total time: 0.453s
C:\adb fastboot mfastboot>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.447s]
finished. total time: 0.449s
C:\adb fastboot mfastboot>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.358s]
writing 'fsg'...
OKAY [ 0.804s]
finished. total time: 1.169s
C:\adb fastboot mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.176s]
finished. total time: 0.178s
Hi! Thanks for helping me on my journey. I've tried to flash everything except system and booting into TWRP but dead Android picture is shown and after pressing "power+vol up" stock recovery still being loaded. I don't know if it's expected to be like this but recovery flashing seens to be taking less time then expected:
Code:
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
Any thoughts on this?
dolence said:
Code:
C:\adb fastboot mfastboot>fastboot oem fb_mode_set
...
OKAY [ 0.113s]
finished. total time: 0.115s
C:\adb fastboot mfastboot>fastboot flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'partition' (32 KB)...
OKAY [ 0.259s]
writing '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
OKAY [ 0.442s]
finished. total time: 0.706s
C:\adb fastboot mfastboot>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'motoboot' (1604 KB)...
OKAY [ 0.368s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
OKAY [ 5.028s]
finished. total time: 5.401s
C:\adb fastboot mfastboot>fastboot flash logo logo.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'logo' (245 KB)...
OKAY [ 0.319s]
writing 'logo'...
OKAY [ 0.856s]
finished. total time: 1.179s
C:\adb fastboot mfastboot>fastboot flash boot boot.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.947s]
writing 'boot'...
OKAY [ 1.337s]
finished. total time: 2.288s
C:\adb fastboot mfastboot>fastboot flash recovery twrp-2.8.7.0-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
finished. total time: 1.783s
C:\adb fastboot mfastboot>fastboot flash modem NON-HLOS.bin
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'modem' (54272 KB)...
OKAY [ 3.710s]
writing 'modem'...
OKAY [ 2.395s]
finished. total time: 6.110s
C:\adb fastboot mfastboot>fastboot erase modemst1
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.447s]
finished. total time: 0.453s
C:\adb fastboot mfastboot>fastboot erase modemst2
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.447s]
finished. total time: 0.449s
C:\adb fastboot mfastboot>fastboot flash fsg fsg.mbn
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'fsg' (226 KB)...
OKAY [ 0.358s]
writing 'fsg'...
OKAY [ 0.804s]
finished. total time: 1.169s
C:\adb fastboot mfastboot>fastboot oem fb_mode_clear
...
OKAY [ 0.176s]
finished. total time: 0.178s
Hi! Thanks for helping me on my journey. I've tried to flash everything except system and booting into TWRP but dead Android picture is shown and after pressing "power+vol up" stock recovery still being loaded. I don't know if it's expected to be like this but recovery flashing seens to be taking less time then expected:
Code:
sending 'recovery' (8498 KB)...
OKAY [ 0.853s]
writing 'recovery'...
OKAY [ 0.926s]
Any thoughts on this?
Click to expand...
Click to collapse
you need to use twrp-2.8.7.2
vijayid_94 said:
you need to use twrp-2.8.7.2
Click to expand...
Click to collapse
The same with 2.8.7.2, unfortunately.
dolence said:
The same with 2.8.7.2, unfortunately.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Dont reboot.. choose recovery from fastboot menu.. this will not over write it, or simply try fastboot boot twrp.img
Salik Iqbal said:
Fastboot flash recovery twrp.img
Dont reboot.. choose recovery from fastboot menu.. this will not over write it, or simply try fastboot boot twrp.img
Click to expand...
Click to collapse
I was choosing recovery from fastbbot menu. It doesn't work at all.... Booting via command doesn't work as well.
Code:
C:\adb fastboot mfastboot>fastboot boot twrp-2.8.7.2-ghost.img
downloading 'boot.img'...
OKAY [ 0.798s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.899s
C:\adb fastboot mfastboot>
dolence said:
The same with 2.8.7.2, unfortunately.
Click to expand...
Click to collapse
check your pm and get me over facebook. i am not much active on xda these days.
Hey guys,
I'm trying to get TWRP installed on my nexus 6 but it keeps failing.
I've unlocked the bootloader, but everytime I run the command I get the following:
C:\Users\Alex\Downloads\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp-3.1.0-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' (11681 KB)...
OKAY [ 0.368s]
writing 'recovery'...
OKAY [ 0.178s]
finished. total time: 0.546s
I can't find a similar example anywhere. Can anyone assist? My nexus is on 7.1.1
You could use the official TWRP app to install it. It does it without rebooting.
https://play.google.com/store/apps/details?id=me.twrp.twrpapp
I flashed an earlier version and got pretty much the same thing you got. When I booted into recovery, TWRP was there. Got the TWRP manager and used that to get updated to 3.1.x
Sent from my Nexus 6 using Tapatalk
I had my phone wiped already as I wanted a proper fresh install
anyway after a couple of more attempts even though if failed to install, for some reason it worked afterwards when I rebooted the phone, god knows why!
anyway, all sorted
Mephisto_POA said:
Hey guys,
I'm trying to get TWRP installed on my nexus 6 but it keeps failing.
I've unlocked the bootloader, but everytime I run the command I get the following:
C:\Users\Alex\Downloads\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp-3.1.0-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' (11681 KB)...
OKAY [ 0.368s]
writing 'recovery'...
OKAY [ 0.178s]
finished. total time: 0.546s
I can't find a similar example anywhere. Can anyone assist? My nexus is on 7.1.1
Click to expand...
Click to collapse
Boot TWRP from fastboot by entering
fastboot boot recovery twrp.img
Copy recovery.img in internal storage and then flash image from twrp by clicking on install and choose image.
Press thanks if i helped
Sent from my iPhone using Tapatalk
I have same isssue. Have you solved it?
I saw this one when it was first posted, but never got around to answering. Time to change that...
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
Click to expand...
Click to collapse
This part is something you'll see if using an up to date fastboot (which is something you should have or flashing stuff might not work). It's purely information that your bootloader is missing certain things that fastboot checks for. It's not an issue.
My guess (without doing any research or actually knowing anything about it) is that those slot-thingymabobs are for the Pixel.
What's important from the output in the OP is this:
sending 'recovery' (11681 KB)...
OKAY [ 0.368s]
writing 'recovery'...
OKAY [ 0.178s]
finished. total time: 0.546s
Click to expand...
Click to collapse
Taking a look at that output we see that the recovery image first has been sent to the device and then gets written to the device, both reporting OKAY. If it didn't work, a quite clear failure would have been reported.
Just be sure to use the hardware buttons to boot to recovery after flashing TWRP, then reboot system from TWRP. Otherwise, stock recovery may overwrite TWRP if you reboot system directly via Fastboot
I build and loaded an AOSP for my Nexus 6. I tried the procedure to put SuperSU and root it and got the following:
[email protected]:~/Downloads# fastboot flash recovery ~/Downloads/twrp-3.0.2-1-bullhead.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' (16433 KB)...
OKAY [ 1.148s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 1.154s
[email protected]:~/Downloads#
Not quite the right place... You're having issues installing TWRP, not SuperSU. There's a dedicated Nexus 6 forum on XDA where you'll find all the info you'll need.
Your device is NOT named "Bullhead", it's "Shamu". Go to twrp.me and download the correct file for your device.
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