C:\Program Files (x86)\Minimal ADB and Fastboot\NX629J_Z69_EN_WPJ0O_V209>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system'...
OKAY [ 0.016s]
sending sparse 'system' 1/5 (768623 KB)...
OKAY [ 26.609s]
writing 'system' 1/5...
OKAY [ 0.010s]
sending sparse 'system' 2/5 (753639 KB)...
OKAY [ 31.166s]
writing 'system' 2/5...
OKAY [ 0.010s]
sending sparse 'system' 3/5 (776366 KB)...
OKAY [ 32.717s]
writing 'system' 3/5...
OKAY [ 0.008s]
sending sparse 'system' 4/5 (786429 KB)...
OKAY [ 32.807s]
writing 'system' 4/5...
OKAY [ 0.004s]
sending sparse 'system' 5/5 (138400 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 136.141s
Click to expand...
Click to collapse
i try use usb port 3.0, nothing, i try use usb port 2.0, nothing, i try another cable, nothing....
Related
As the title says the stock slot was wiped on this Bionic. I have tried using BionicRestorer to fxz to 5.5.893 and 5.9.901 and it encountered a couple of errors. I'm not sure exactly what the mean though. The phone boots to the Moto logo, then the screen goes blank and the soft keys stay lit. Nothing else happens and I have to pull the battery. I tried booting into recovery mode but after selecting recovery I get the android laying on his back with a triangle/exclamation point above him.
I'm not sure what else I can do with this and would greatly appreciate some help. I do have a charger so I'm not worried about the battery getting low. I'm using Linux but do have access to Windows as well.
Here is the command line output from the BionicRestorer script:
Code:
Here we go, I don't stop on errors, once it starts there is no stopping
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.007s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm allow-mbmloader-flashing-mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.023s]
writing 'mbm'... OKAY [ 0.453s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbmloader mbmloader.bin
sending 'mbmloader' (40 KB)... OKAY [ 0.009s]
writing 'mbmloader'... OKAY [ 0.289s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbm mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.024s]
writing 'mbm'... OKAY [ 0.451s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux reboot-bootloader
rebooting into bootloader... OKAY [ 0.006s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.007s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase cache
erasing 'cache'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux erase userdata
erasing 'userdata'... OKAY [ 0.012s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash lbl lbl
sending 'lbl' (16 KB)... OKAY [ 0.007s]
writing 'lbl'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash logo.bin logo.bin
sending 'logo.bin' (854 KB)... OKAY [ 0.061s]
writing 'logo.bin'... OKAY [ 0.267s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash ebr ebr
sending 'ebr' (16 KB)... OKAY [ 0.008s]
writing 'ebr'... OKAY [ 0.428s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash mbr mbr
sending 'mbr' (16 KB)... OKAY [ 0.007s]
writing 'mbr'... OKAY [ 0.397s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash devtree device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.041s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.514s]
writing 'system'... OKAY [ 21.258s]
sending 'system' (229120 KB)... OKAY [ 14.442s]
writing 'system'... OKAY [ 18.771s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.533s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.600s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash cdrom cdrom
sending 'cdrom' (12032 KB)... OKAY [ 0.771s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.499s]
writing 'preinstall'... OKAY [ 22.208s]
sending 'preinstall' (49152 KB)... OKAY [ 3.106s]
writing 'preinstall'... OKAY [ 3.931s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash webtop grfs.img
sending 'webtop' (262144 KB)... OKAY [ 16.516s]
writing 'webtop'... OKAY [ 23.794s]
sending 'webtop' (262144 KB)... OKAY [ 16.515s]
writing 'webtop'... OKAY [ 23.305s]
sending 'webtop' (262144 KB)... OKAY [ 16.507s]
writing 'webtop'... OKAY [ 21.253s]
sending 'webtop' (262144 KB)... OKAY [ 16.521s]
writing 'webtop'... OKAY [ 22.130s]
sending 'webtop' (262144 KB)... OKAY [ 16.514s]
writing 'webtop'... OKAY [ 22.110s]
sending 'webtop' (54016 KB)... OKAY [ 3.408s]
writing 'webtop'... OKAY [ 5.240s]
Running: /home/gundr/android_root/bionic/BionicRestorer/bin/moto-fastboot64.Linux flash radio radio.img
sending 'radio' (21768 KB)... OKAY [ 1.377s]
writing 'radio'... OKAY [ 3.805s]
I think I've tried flashing the wrong file in a mad case of Idon'tknowwhati'mdoingsoIshouldhaveleftittheheckalone. So I'm going to try flashing http://sbf.droid-developers.org/download.php?device=12&file=162 with RSD Lite as suggested in some other posts I've read today.
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Ryan11271 said:
Well, You could try holding vol down before turning it on, That should get you to ap fastboot, then use rsd
Click to expand...
Click to collapse
That's what I plan on doing. I can still get to recovery and ap fastboot mode. I'm going to d/l rsd now.
The biggest thing is that you cannot flash back to an earlier version than what had been installed. You can only flash the same version or newer.
How about this, I ordered a droid bionic, I'll root and put on safestrap, Once I do all that good stuff I'll make you a stock rom backup and send you the zip. I'll pm you when I get it
Probably doesn't have safestrap installed anymore, so a backup from safestrap wouldn't help.
Ohhh, I didn't think of that XD
Yeah I borked safestrap too but thanks for the offer though. I'm about to reboot into windows and try to rsd what I believe to be the correct version.
I was trying to install rom and something got wrong with phone it just keep restarting after huawei logo. I tryed to reinstall system through fastboot (FULL Huawei P7-L10C900B852)
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cust cust.img
target reported max download size of 536870912 bytes
sending 'cust' (400995 KB)...
OKAY [ 15.426s]
writing 'cust'...
OKAY [ 18.747s]
finished. total time: 34.176s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8072 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.970s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
sending 'cache' (8296 KB)...
OKAY [ 0.320s]
writing 'cache'...
OKAY [ 0.423s]
finished. total time: 0.745s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
sending 'userdata' (132497 KB)...
OKAY [ 5.089s]
writing 'userdata'...
OKAY [ 6.829s]
finished. total time: 11.921s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (523522 KB)...
OKAY [ 20.682s]
writing 'system'...
OKAY [ 24.469s]
sending sparse 'system' (523531 KB)...
OKAY [ 20.890s]
writing 'system'...
OKAY [ 24.489s]
sending sparse 'system' (454037 KB)...
OKAY [ 18.014s]
writing 'system'...
OKAY [ 21.367s]
finished. total time: 129.919s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13188 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 1.064s]
finished. total time: 1.577s
Now when i turn on phone it allways loads fastboot menu. When i try to load recovery menu it fails just keep restartint. Tryed curstom recovery like twrp and cwm, and also cant run.
danixlt said:
I was trying to install rom and something got wrong with phone it just keep restarting after huawei logo. I tryed to reinstall system through fastboot (FULL Huawei P7-L10C900B852)
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cust cust.img
target reported max download size of 536870912 bytes
sending 'cust' (400995 KB)...
OKAY [ 15.426s]
writing 'cust'...
OKAY [ 18.747s]
finished. total time: 34.176s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8072 KB)...
OKAY [ 0.312s]
writing 'boot'...
OKAY [ 0.654s]
finished. total time: 0.970s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
sending 'cache' (8296 KB)...
OKAY [ 0.320s]
writing 'cache'...
OKAY [ 0.423s]
finished. total time: 0.745s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
sending 'userdata' (132497 KB)...
OKAY [ 5.089s]
writing 'userdata'...
OKAY [ 6.829s]
finished. total time: 11.921s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (523522 KB)...
OKAY [ 20.682s]
writing 'system'...
OKAY [ 24.469s]
sending sparse 'system' (523531 KB)...
OKAY [ 20.890s]
writing 'system'...
OKAY [ 24.489s]
sending sparse 'system' (454037 KB)...
OKAY [ 18.014s]
writing 'system'...
OKAY [ 21.367s]
finished. total time: 129.919s
C:\Users\Donis\Desktop\asd\HUAWEI>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13188 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 1.064s]
finished. total time: 1.577s
Now when i turn on phone it allways loads fastboot menu. When i try to load recovery menu it fails just keep restartint. Tryed curstom recovery like twrp and cwm, and also cant run.
Click to expand...
Click to collapse
Have you tried doing a force update? Just create a folder on your SD card called "dload" then copy the update.app to that folder and when your phone is turned off, hold down all three buttons to perform a forced update.
After i i flash custom rom the i cant turn on the wifi so i decided to reset factory of my red magic 3 but after a rest i got stuck in FASTBOOT MODE no matter what i choice from reboot from recovery mode or reboot from system it will just restart and back again to FASTBOOT MODE can some one help me please is this permanent brick?
I USE ALL COMMANDS BUT DON'T WORK :
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ -0.000s]
writing 'vbmeta'...
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.819s]
writing 'dsp'...
OKAY [ 0.406s]
finished. total time: 2.230s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.219s]
writing 'splash'...
OKAY [ 0.031s]
finished. total time: 0.266s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144196 KB)...
OKAY [ 4.018s]
writing 'modem'...
OKAY [ 0.869s]
finished. total time: 4.888s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.780s]
writing 'boot'...
OKAY [ 0.469s]
finished. total time: 3.253s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.234s]
writing 'dtbo'...
OKAY [ 0.063s]
finished. total time: 0.297s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' (767446 KB)...
OKAY [ 24.161s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (786430 KB)...
OKAY [ 33.767s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (744616 KB)...
OKAY [ 30.043s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (786429 KB)...
OKAY [ 37.173s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (532404 KB)...
OKAY [ 26.319s]
writing 'system'...
OKAY [ 0.002s]
finished. total time: 151.675s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.800s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 3.339s
Instructions are everywhere. Follow them, or forever hold your peace.
after "fastboot flash recovery recovery.img"
write fastboot oem nubia_lock NUBIA_NX629J
and then fastboot reboot
u will get into recovery mode
Sir my Nubia red Magic 3 stuck on logo can any one help me please
Was trying to update the phone to latest stable version from mi ui 12 (coming from stable MI UI 12 eu rom), using the file xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.9.0.SKACNXM_v13-12-fastboot
Followed instruction to reboot phone to fastboot, then ran windows_fastboot_update_rom.bat
The update process then started, but when eventually ran into an error:
Sending sparse 'super' 1/9 (782984 KB) OKAY [ 17.766s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 2/9 (767500 KB) OKAY [ 17.408s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 3/9 (743364 KB) OKAY [ 16.967s]
Writing 'super' OKAY [ 0.006s]
Sending sparse 'super' 4/9 (767368 KB) OKAY [ 17.439s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 5/9 (770660 KB) OKAY [ 20.194s]
Writing 'super' OKAY [ 1.947s]
Sending sparse 'super' 6/9 (731176 KB) OKAY [ 16.536s]
Writing 'super' OKAY [ 0.005s]
Sending sparse 'super' 7/9 (779640 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Please help not too sure what to do next it's now stuck.
issue resolved - apparently problem was caused by the phone connecting via a usb hub.
reconnected phone directly to PC over usb, then reboot the phone back into fastboot and ran the command again to perform upgrade.
The second time upgrade was able to complete:
Sending sparse 'super' 1/9 (782984 KB) OKAY [ 17.292s]
Writing 'super' OKAY [ 0.008s]
Sending sparse 'super' 2/9 (767500 KB) OKAY [ 16.995s]
Writing 'super' OKAY [ 0.008s]
Sending sparse 'super' 3/9 (743364 KB) OKAY [ 16.452s]
Writing 'super' OKAY [ 0.011s]
Sending sparse 'super' 4/9 (767368 KB) OKAY [ 16.995s]
Writing 'super' OKAY [ 0.004s]
Sending sparse 'super' 5/9 (770660 KB) OKAY [ 19.580s]
Writing 'super' OKAY [ 2.559s]
Sending sparse 'super' 6/9 (731176 KB) OKAY [ 16.207s]
Writing 'super' OKAY [ 0.002s]
Sending sparse 'super' 7/9 (779640 KB) OKAY [ 17.281s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 8/9 (786356 KB) OKAY [ 17.358s]
Writing 'super' OKAY [ 0.008s]
Sending sparse 'super' 9/9 (396480 KB) OKAY [ 9.205s]
Writing 'super' OKAY [ 0.002s]
Finished. Total time: 160.147s
Setting current slot to 'a' OKAY [ 12.320s]
Finished. Total time: 12.454s
Rebooting OKAY [ 0.108s]
Finished. Total time: 0.112s
maybe that helps others when they have the same problem
We will flash the ubuntu touch boot image which is required temporarily. And the currently latest sfos build for the QX1050.
1. Download ubuntu touch build from here and extract the boot.img
Ubuntu for Pro¹ X build job 2830649718 artifact.zip
2. Download SailfishOS 4.4.0.64 build from here and extract the userdata.simg
SailfishOS for Pro¹ X job 2807435728 artifact.zip
3. Flash using fastboot
Code:
fastboot flash boot_a boot.img
fastboot flash userdata userdata.simg
4. Reboot using fastboot reboot or fastboot continue
Thanks for moving mods! Did not realize its more appropriate here in the guides section than in the development section.
fastboot flash userdata userdata.img
fastboot flash userdata userdata.simg Typo
Nope, the sailfish userdata is in sparse format. So its .simg correctly.
Thats why you will not have the infamous "Invalid sparse file format at header magic" message from fastboot when flashing that .simg. Since fastboot expects sparse images, but *****es about raw images like the ubuntu boot.img above.
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
bobnot said:
Weird I'm getting this error
fastboot flash userdata userdata.simg
error: cannot load 'userdata.simg'
But this command works
fastboot flash userdata userdata.img
target reported max download size of 268435456 bytes
sending sparse 'userdata' (258052 KB)...
OKAY [ 7.558s]
writing 'userdata'...
OKAY [ 1.624s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.864s]
writing 'userdata'...
OKAY [ 1.656s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 8.295s]
writing 'userdata'...
OKAY [ 1.634s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.826s]
writing 'userdata'...
OKAY [ 1.583s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.828s]
writing 'userdata'...
OKAY [ 1.617s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.858s]
writing 'userdata'...
OKAY [ 1.681s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.751s]
writing 'userdata'...
OKAY [ 1.655s]
sending sparse 'userdata' (258040 KB)...
OKAY [ 7.592s]
writing 'userdata'...
OKAY [ 1.694s]
sending sparse 'userdata' (147988 KB)...
OKAY [ 4.536s]
writing 'userdata'...
OKAY [ 0.971s]
finished. total time: 81.497s
It doesn't boot
Click to expand...
Click to collapse
what version of the android platform tools are you using? I'm on r33.0.2 and "fastboot flash userdata userdata.simg" works just fine for me
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
eltmosen said:
Ah, i guess you are flashing the ubuntu image then?
For sailfish, we need only the boot.img from the first posted ubuntu artifacted.
But the userdata.simg from sailfish contained in the second artifact linked below.
Click to expand...
Click to collapse
Neither SFOS or UT will boot
I also updated to latest fastboot from googles source. Still same issue as previously stated.