Database Develop

[Q] Custom Image Boot Failure

I've compiled a Nexus 6 kernel from the msm source switching to the appropriate commit found in my Kernel Version string (eec2459). However, when I create a boot.img (using Pete Batard's bootimg-tools) with that modified kernel I get the following error:
Code:
[email protected]:~/android-sdk-linux/platform-tools$ ./fastboot boot myboot3.img
downloading 'boot.img'...
OKAY [ 1.219s]
booting...
FAILED (remote failure)
finished. total time: 1.282s
My bootloader is unlocked and I have been able to fastboot boot with the factory boot.img. Is it because my boot.img is unsigned? I thought unlocking the bootloader would allow that.
Device Info: Nexus 6, Android 5.1.1, Build number LMY47Z

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

(remote: invalid kernel address: not lie in memory) when booting the lg350z kernel

I have found the source for LG-350Z kernel over LG's opensource official website was successful when compiling despite some errors during compilation I was able to pass that by adding some fixes. It was compiled with GCC 4.8 compiler. Now the thing is that when trying to boot it with the following command:
fastboot boot zImage-dtb
as I tried another image without dtb extension:
fastboot boot zImage
I get this error:
creating boot image...
creating boot image - 6518784 bytes
downloading 'boot.img'...
OKAY [ 0.229s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.251s
Can anyone please tell me why it is not booting or how to fix it?
Note: the kernel is not modified yet, I am just learning how to compile a stock kernel from the source I am kinda new to this.

please any help same here infinix hot5 x559c[
C:\platform-tools>fastboot boot twrp-3.3.1-0-hammerhead.img
Sending 'boot.img' (13290 KB) OKAY [ 0.615s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed
]
could it be the use of the wrong recovery image which I pulled from the team win official page itself I have done a couple of times using different recoveries specific for infinix hot 2 from the same brand the problem is that can't find the one specific for my device please any advice on this thanks.

[ROM][ResurrectionRemix 8.6.x][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
​Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome ​
combination of performance, customization, power and the most new features, brought directly to your Device.​
​
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!​
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.​
​
​
Install the stock recovery.img if you have previously installed twrp.
1. Extract the zip to your adb/fastboot directory, reboot to bootloader and open a CMD window.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta images.
Code:
[/B][/B][/CENTER]
[B][CENTER]fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
​
4. Wipe userdata.
Code:
fastboot -w
5. Reboot, Profit.
(OPTIONAL)
6. If you want to install TWRP/gapps/magisk, do so after you continue through the installation steps to the home screen.
If you have the Moto G8/G Fast and your display cutout is not right, enable the overlay via ADB:
Code:
adb shell cmd overlay enable org.omnirom.overlay.moto.rav
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
1. Starting screen casting/mirroring causes a reboot.
2. The in-built screen recorder also causes a reboot when started.
Dodgy Screen Recorder Fix :laugh:: Download and install the attached apk below, change the quick setting tile to the new one at the bottom of the list, and you should be able to record. (Its the screen recorder app from BlissRom, nothing malicious )
3. Let me know :good:
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
​

To update to the latest version without wiping:
UPDATING FOR GAPPS/MAGISK USERS
1. Install the images as usual in fastbootd
2. Power off and boot to TWRP
3. Install GAPPS and/or Magisk
4. Reboot, profit.
UPDATING FOR NON GAPPS/Magisk USERS
Skip steps 2. and 3. from above.

Cant figure out which drive i uploaded the old files to at the moment
But heres the 8.6.9 May security patch update.
Not much new, added a KCAL enabled kernel as default, and added a color control app (root needed), fixed face unlock (g power) and added the moto clock widgets.
RR - May Patch - Google Drive
drive.google.com
TWRP zip and fastboot d images, no gapps only. Theres also some flame gapps in the folder too that i use and work well.

I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?

NeoSDAP said:
I can't install this ROM. It gives me the following error when flashing in fastbootd:
Code:
C:\adb>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.002s
C:\adb>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.005s]
< waiting for any device >
Finished. Total time: 18.053s
C:\adb>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.486s]
Writing 'boot_a' OKAY [ 0.406s]
Finished. Total time: 1.955s
C:\adb>fastboot flash system system.img
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've checked everything and I've got enough space on the HDD. What could be happening?
Click to expand...
Click to collapse
Try flashing product instead of system first.

Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.

_huck_ said:
Always appreciate the work you put in! I'm currently running the unofficial Lineage OS build, and I'm waiting to flash something new until an official ROM is released for this phone. Are you working on making any of your ROMs official? I know its a ton of work, but if nobody's planning on making anything official any time soon I may end up switching to one of your unofficial ROMs to get the latest security updates.
Click to expand...
Click to collapse
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.

I am SO HAPPY that resurrection remix has just come out for the Moto G Power. I have been waiting!!! I just saw this today, but I can't seem to get it to work.. As seems to happen when people are trying to root the moto G power.. The touch screen will stop working.. I did get mine to root, using this page:
Messed up trying to root
i know there are other threads on this topic. But after going through them I cant find the fix. I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works. I used lmsa to download the stock rom...
forum.xda-developers.com
But I do not know how to apply the same fix after I try to install resurrection remix? I do not have touch screen working after I load.
I am using adb, not sure it twrp is available for moto g power yet, and if that would be the way to get it to work?
I'm using moto g power, sofia variant (usa).. XT2041-4

I tried again and I'm actually getting the following errors:
PS C:\adb> fastboot flash boot boot.img
target reported max download size of 805263360 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.418s]
writing 'boot'...
OKAY [ 0.821s]
finished. total time: 2.248s
PS C:\adb> fastboot flash system system.img
target reported max download size of 805263360 bytes
sending sparse 'system' (786388 KB)...
OKAY [ 18.732s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.749s
PS C:\adb> fastboot flash product product.img
target reported max download size of 805263360 bytes
sending 'product' (575564 KB)...
OKAY [ 12.511s]
writing 'product'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 12.539s
PS C:\adb>

@cxskate
You aren't in fastbootd. You are in fastboot mode. From the screen you are at in the above screenshot, type fastboot reboot fastboot.
You should reboot to a new screen with fastbootd in red across the top.
Flash the images there.

I'm still having a problem...
My phone does not enter into FastBootD mode... The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following:
Please any advice? Very much appreciated.
PS C:\adb> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb>

Beetle84 said:
Personally, I'm not going to make official builds, but I believe the crdroid Dev is going to try.
Not sure about the other guys/girls.
Click to expand...
Click to collapse
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!

_huck_ said:
So, based on this I installed it last night, and so far so good! Couple little things don't quite work 100%, but its totally usable. Thanks OP!!
Click to expand...
Click to collapse
Awesome! What are the little things? I'll add to the bug list

I'm going for a Degoogled setup and this rom is the first one that worked with microg without hassles. I installed minMicrog standard and Majisk, toggled the baked in signature spoofing, and was up and running in minutes. VERY AWESOME!

Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks

etienne_9000 said:
Hello ! I would love to try your rom, but when trying to flash boot.img, i got this error : "FAILED (remote: Download is not allowed on locked devices)".
So i realized my bootloader was still locked.
To unlock the bootloader, i have to type "fastboot oem get_unlock_data", but it returns "FAILED (remote: Command not supported in default implementation)".
Do you have any idea how to fix this ?
Thanks
Click to expand...
Click to collapse
Google 'unlock Motorola bootloader'
You need a code from Motorola.

Beetle84 said:
Google 'unlock Motorola bootloader'
You need a code from Motorola.
Click to expand...
Click to collapse
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.

etienne_9000 said:
TX for answering. Thats what i did, and i was reading this official Motorola tutorial to get the code. It asks to type the command "fastboot oem get_unlock_data". So im stuck here for now...
I know this is a bit off topic, but i wonder you managed to do it somehow in order to test your build.
Click to expand...
Click to collapse
Did you tick the OEM unlock allowed option in developer settings?

Trying to figure out how to load gapps on with adb now??
I actually was finally able to enter FastBootD mode using a different method I found on youtube, but wasvstill getting errors when I tried to flash.. FAILED (remote: No such file or directory)
UPDATE I copied all the new files to the adb folder on the C: drive and i got it to work.. Got RR up and running, but still..
I'm trying to figure out how to load gapps on with adb now??
Method I used to get fastboot D:
(
),

Beetle84 said:
Did you tick the OEM unlock allowed option in developer settings?
Click to expand...
Click to collapse
Yes i did. Just tried again to "fastboot oem get_unlock_data" and still getting "FAILED (remote: Command not supported in default implementation)"

Problem flashing kernel

Hi all,
I'm doing some studies with the Pixel 4a 5g. I'd like to make some modifications to the kernel. For that reason, my first attempt was to build the original kernel (https://source.android.com/setup/build/building-kernels). I've compiled the source code with the following lines.
# repo init -u https://android.googlesource.com/kernel/manifest -b android-msm-bramble-4.19-android11-d1
# ./build/build.sh
The problem comes when flashing the image. Here's what I get:
./fastboot boot google-kernel/out/android-msm-pixel-4.19/dist/Image.lz4-dtb
creating boot image...
creating boot image - 9392128 bytes
Sending 'boot.img' (9172 KB) OKAY [ 0.372s]
Booting (bootloader) boot.img missing cmdline or OS version
At this points, the shell and the phone hang forever.
Any help will be much appreciated.
Thanks,
Adrian

Hi Adrian,
I've got the same error. Have you managed to address it?
Jon