Sailfish X install "writing oem not allowed" [answered]

Question

2

Sailfish X install "writing oem not allowed" [answered]

asked 2017-10-11 22:48:33 +0200

duque
89 ●3 ●5 ●12

updated 2017-10-12 10:37:10 +0200

jiit

2678 ●32 ●58 ●59

admin

Hi there, Just followed the instructions and everything worked well, until the very end of the Batch file. According to Android SDK, the Fastboot Device is found and unlocked warning Comes up when starting my Xperia X. Here is a log from the Batch Output.

This is a Windows flashing script for Sony Xperia X device.

Power on the device in fastboot mode, by doing the following: 1. Turn off your Xperia. 2. Connect one end of a USB cable to your PC. 3. While holding the volume up button pressed, connect the other end of the USB cable to your Xperia. 4. After this you should see the blue LED lit on Xperia, and it will be ready for flashing

Drücken Sie eine beliebige Taste . . . Searching a device with vendor id '0x0fce'.. Das System kann das angegebene Laufwerk nicht finden. MD5SUM '77ddc7a0b9dd95db593829b97bc9868a' match for hybris-boot.img.

C:\Users\Neu\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16_NEW>fastboot.exe -i 0x0fce flash boot hybris-boot.img target reported max download size of 536870912 bytes sending 'boot' (10842 KB)... OKAY [ 0.440s] writing 'boot'... OKAY [ 0.070s] finished. total time: 0.520s MD5SUM '611d0db74e6ffd22addf63318508b71d' match for fimage.img001.

C:\Users\Neu\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16_NEW>fastboot.exe -i 0x0fce flash system fimage.img001 target reported max download size of 536870912 bytes erasing 'system'... OKAY [ 0.170s] sending sparse 'system' 1/2 (524284 KB)... OKAY [ 23.420s] writing 'system' 1/2... OKAY [ 3.860s] sending sparse 'system' 2/2 (92428 KB)... OKAY [ 4.150s] writing 'system' 2/2... OKAY [ 0.670s] finished. total time: 32.290s MD5SUM '88d74c452de2521e3eebd4f4dcdb3851' match for sailfish.img001.

C:\Users\Neu\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16_NEW>fastboot.exe -i 0x0fce flash userdata sailfish.img001 target reported max download size of 536870912 bytes erasing 'userdata'... OKAY [ 0.630s] sending sparse 'userdata' 1/3 (524284 KB)... OKAY [ 23.610s] writing 'userdata' 1/3... OKAY [ 3.870s] sending sparse 'userdata' 2/3 (524284 KB)... OKAY [ 22.875s] writing 'userdata' 2/3... OKAY [ 3.785s] sending sparse 'userdata' 3/3 (252840 KB)... OKAY [ 10.813s] writing 'userdata' 3/3... OKAY [ 1.830s] finished. total time: 67.453s

C:\Users\Neu\Downloads\SailfishOS-2.1.3.5-1-f5121-0.0.1.16_NEW>fastboot.exe -i 0x0fce flash oem SW_binaries_for_Xper oire.img target reported max download size of 536870912 bytes sending 'oem' (163040 KB)... OKAY [ 15.220s] writing 'oem'... FAILED (remote: Command not allowed) finished. total time: 15.230s

ERROR: Failed to execute 'fastboot.exe -i 0x0fce flash oem SW_binaries_for_Xperia_AOSP_M_MR1_3.10_v13_loire.img'.

FLASHING FAILED

Please go to https://together.jolla.com/ and ask for guidance.

Drücken Sie eine beliebige Taste . . .

Thanks for your help hope it's easy to fix. I don't really know what else I could/Need to do. Cheers Alex

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:06:53.949846

Comments

are you sure there is no simlock on phone? you could also try to flash another firmware version with or flashtool.

breiti_oi ( 2017-10-11 23:15:59 +0200 )edit

2

Did you "Allow OEM Unlock" in Developer options? This wasn't mentioned in the instruction, but I allowed and flashed my sony successfully.

molly ( 2017-10-12 02:33:36 +0200 )edit

maybe this will bring you a step closer: http://sailfishmods.de/2017/07/howto-sony-xperia-x-teil-1-cda-drm-keys-bootloader/

breiti_oi ( 2017-10-12 09:30:38 +0200 )edit

This same thing happened to me. I was running android version what was installed (7.1.1 or something, did't check). I managed to get it working by installing Emma and flashing 34.3.A.0.228 -version it first. After successful android boot I tried Sailfish X install again and everything went smooth. So the problem might be too old stock android if I am correct?

itbaron ( 2017-10-14 16:52:48 +0200 )edit

I ran into the same issue. my version was already newer than 34.3.A.0.228. I try to flash 34.3.A.0.252 with emma now and hope everything is going smoothly.

Burcardo ( 2018-01-03 18:43:37 +0200 )edit

are you sure there is no simlock on phone? you could also try to flash another firmware version with or flashtool.
breiti_oi ( 2017-10-11 23:15:59 +0200 )edit
Did you "Allow OEM Unlock" in Developer options? This wasn't mentioned in the instruction, but I allowed and flashed my sony successfully.
molly ( 2017-10-12 02:33:36 +0200 )edit
maybe this will bring you a step closer: http://sailfishmods.de/2017/07/howto-sony-xperia-x-teil-1-cda-drm-keys-bootloader/
breiti_oi ( 2017-10-12 09:30:38 +0200 )edit
This same thing happened to me. I was running android version what was installed (7.1.1 or something, did't check). I managed to get it working by installing Emma and flashing 34.3.A.0.228 -version it first. After successful android boot I tried Sailfish X install again and everything went smooth. So the problem might be too old stock android if I am correct?
itbaron ( 2017-10-14 16:52:48 +0200 )edit
I ran into the same issue. my version was already newer than 34.3.A.0.228. I try to flash 34.3.A.0.252 with emma now and hope everything is going smoothly.
Burcardo ( 2018-01-03 18:43:37 +0200 )edit

Answer 1

3

answered 2017-10-12 09:45:34 +0200

duque
89 ●3 ●5 ●12

Hi Again,

You are correct, in the part that I did not have stock android installed. I was running Sony Xperia Conectp. which was the latest 7.1.x something release.

I flashed it with stock ROM and now it works, sorry for my mistake. I assumed that the Concept Version 38.X.X.XXX was higher then the stated 34.X.X

Now it works... what a joy what a joy, thanks for your Input. I tmade me question the concept ROM and reflash stock.

Cheers Alex

edit flag offensive delete publish link

Accepted Answer

2

answered 2017-10-12 08:47:03 +0200

Jurop
56 ●1 ●4

The issue is that you installed Sailfish not on the most current Android version, thus a partition needed for the install is not writable hence the issue.

This answer, linux instructions, is right until the 'telnet' part:

1- Turn off your device and while holding the volume up key plug it into the computer and wait for the light to turn blue. Check that it is connected:

fastboot devices

2 - You should get something like

CB1378RR4 fastboot

3 - From the zip you downloaded with SailfishX fish out hybris-recovery.img and copy it in some location on your computer, for example on the desktop. Remember the location.

fastboot boot /home/user/Desktop/hybris-recovery.img

4 - Your device will then tell you in very tiny font to telnet into some address. Do it:

telnet 10.42.66.66

Then issue the following commands, as per Hot HADK https://public.etherpad-mozilla.org/p/hot-hadk

mkdir oem
mount /dev/mmcblk0p28 oem
mkdir cache
mount /dev/mmcblk0p24 cache
rm -rf oem/*
cp -ar cache/* oem
umount oem
umount cache
rmdir oem cache

5 - reboot and install SFOS again

edit flag offensive delete publish link

Comments

Please correct me if I'm mistaken, but wouldn't reflashing the device with Emma provide the most recent and thus correct Android version, which in turn would lead to successful Sailfish OS X flashing?

EDIT: Already done like that, it seems :)

Direc ( 2017-10-12 23:20:22 +0200 )edit

Answer 3

0

answered 2017-10-12 00:54:14 +0200

oenone

1070 ●12 ●15 ●18

updated 2017-10-12 00:58:12 +0200

Instructions for Linux, but maybe you can make sense of them and replicate it on Windows?

Boot into recovery on the device with the help of the terminal on your computer and the restore the device to factory:

Turn off your device and while holding the volume up key plug it into the computer and wait for the light to turn blue. Check that it is connected:

fastboot devices

You should get something like

CB1378RR4     fastboot

From the zip you downloaded with SailfishX fish out hybris-recovery.img and copy it in some location on your computer, for example on the desktop. Remember the location.

fastboot boot /home/user/Desktop/hybris-recovery.img

Your device will then tell you in very tiny font to telnet into some address. Do it:

telnet 10.42.66.66

You will be presented with a menu in your terminal titled Jolla Recover v2.0 Chose option 1) Reset device to factory state:

Then agree with everything being erased:

When it is done laundering your device, it should tell you that it is done and the device is recovered and will encourage you to press [Enter] to reboot. Do that.

[Enter]

That should resolve the problem.

edit flag offensive delete publish link

Comments

Hmm tried this and it barfed.

-----------------------------
 Jolla Recovery v2.0
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Shell
4) Perform file system check
5) Run sshd
6) Exit
Type the number of the desired action and press [Enter]: 
1

ALL DATA WILL BE ERASED! Clears everything from the device and reverts the
software back to factory state. This means LOSING EVERYTHING you have added to
the device (e.g. updates, apps, accounts, contacts, photos and other media).
Are you really SURE? [y/N] y

/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
mount: mounting /dev/sailfish/root on /rootfs failed: No such file or directory
[WARNING] Root file system unaccessible, bypassing device lock check.
umount: can't umount /rootfs: Invalid argument
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
sh: /sys/class/block/mmcblk0p10: unknown operand
sh: /sys/class/block/mmcblk0p10: unknown operand
ls: /tmp/tmp.xrOnMD/Sailfish*: No such file or directory
[ERROR] Factory reset failed.  
Connection closed by foreign host.

I too am getting the OEM cannot be flashed

writing 'oem'...
 FAILED (remote: Command not allowed)

Trouble is I already have OEM unlocked because I had a custom OMNI rom on it. Of course if someone wants to bundle Sailfish into a zip I don't mind using TWRP to flash it ;)

veritanuda ( 2017-10-12 02:00:14 +0200 )edit

Answer 4

0

answered 2017-10-12 07:17:27 +0200

duque
89 ●3 ●5 ●12

I die follow the Instruktion Don how to oem unlock the Device . There was also a Video on the Jolla Website were you could see, how to go into Developer Mode and activate oem unlock. I then went to the Sony dev Website and followed the rest of the unlock instructions.

Regarding the question of simlock, i don‘t have a simcard installed at the moment

Cheers Alex

edit flag offensive delete publish link

Answer 5

0

answered 2017-10-12 11:13:42 +0200

Venty

710 ●23 ●34 ●40

http://www.hackerfunk.ch/

updated 2017-10-12 11:14:07 +0200

This hit me as well. As user molly already mentioned in a comment (should be THE answer):

You have to enable "Allow OEM Unlock" in Developer options!

This is missing from the flashing-instructions textfile. If enabled, everything works.

edit flag offensive delete publish link

Comments

Hi There, The OEM Unlock was enabled. but as I wrote. I was using Sony Concept ROM and that causes it not to work, after using the EMMA Tool and installing the Sony ROM. that is why I gave the "correct" answer to the hint about the ROM Version

duque ( 2017-10-12 11:18:45 +0200 )edit

Answer 6

0

answered 2017-10-12 14:24:41 +0200

SagaciousT
1399 ●31 ●42 ●44

I also had the problem that flashing (on Linux) stopped with "writing 'oem'... FAILED (remote: Command not allowed)". Then, I changed to Windows and Emma, updated the phone to the latest and Android version and changed back to Linux for a successful update. However, I updated Android manually from the phone (OTA) before which turned out that it was not the very latest.

edit flag offensive delete publish link

Comments

I don't do windows. So are you telling me I HAVE to use the EMMA tool to fix this OEM junk?

I feel a little offended at that a I have full access to the phone core otherwise. I could reflash the baseband the radio or any other nonsense given the correct imaged. The idea I have to flash a 'blessed' version of Android before I can install Sailfish feels dirty.

EDIT: Scratch that. Seems someone else pointed to This Thread and I am able to use Mono to download firmware directly.

So no. If you are a Linux purist, you don't need to get your fingers dirty faffing around with Windows VM's and the like.

veritanuda ( 2017-10-12 14:39:36 +0200 )edit

This issue FAILED: remote command not allowed is a different one than the OP, that happens when the bootloader still needs to be unlocked, and the solution is stated above - enable OEM unlock in settings. The OP had an issue due to a last minute partition scheme change that impacts mostly people that were already tinkering with their Xperias... True is, being the error spitted out the same, you need the whole log to determine the cause, so having more solutions is good anyway

Jurop ( 2017-10-12 19:35:40 +0200 )edit

In the end I struggled with installed a 'blessed' firmware image using the flashtool and then re-reun the sailfish flash.sh script and it worked!!

So I now have Sailfish X on the Xperia X F5121 and it looks very nice. And is as intuitive as I remember it.

Battery life looking good too so far.

If I have one gripe it has to be that the default browser seems very slow to render pages where as a android version on Fennac was astoundingly faster. Not sure what happened there. But it should not take about 15 seconds to render Reddit front page with the default browsers and 3 seconds with Fennac.

veritanuda ( 2017-10-13 03:07:23 +0200 )edit

Sailfish X install "writing oem not allowed" [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:06:53.949846

Comments

6 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Sailfish X install "writing oem not allowed" [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan close date 2018-11-16 14:06:53.949846

Comments

6 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by molan
close date 2018-11-16 14:06:53.949846