View Single Post
Posts: 84 | Thanked: 146 times | Joined on Feb 2015
#1565
I have a problem (yeah, yeah, not just one, but this one is relevant):

I performed this surgery on the device via telnet to the Jolla Recovery image:

Code:
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
Now, trying to install the Official SailfishX I get this:

Code:
user@Kouvala:~/Documents/XperiaX/SailfishX/official/SailfishOS-2.1.3.5-1-f5121-0.0.1.16$ bash ./flash.sh
Detected Linux
Searching device to flash..
Found device with vendor id '0fce': Bus 003 Device 080: ID 0fce:0dde Sony Ericsson Mobile Communications AB Xperia Mini Pro Bootloader
Fastboot command: fastboot -i 0x0fce 
Flashing boot partition..
target reported max download size of 536870912 bytes
sending 'boot' (10842 KB)...
OKAY [  0.347s]
writing 'boot'...
OKAY [  0.068s]
finished. total time: 0.415s
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [  0.214s]
sending sparse 'system' 1/2 (524284 KB)...
OKAY [ 16.484s]
writing 'system' 1/2...
OKAY [  2.827s]
sending sparse 'system' 2/2 (92428 KB)...
OKAY [  2.969s]
writing 'system' 2/2...
OKAY [  0.500s]
finished. total time: 22.994s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [  1.372s]
sending sparse 'userdata' 1/3 (524284 KB)...
OKAY [ 16.490s]
writing 'userdata' 1/3...
OKAY [  2.820s]
sending sparse 'userdata' 2/3 (524284 KB)...
OKAY [ 16.516s]
writing 'userdata' 2/3...
OKAY [  2.825s]
sending sparse 'userdata' 3/3 (252840 KB)...
OKAY [  8.042s]
writing 'userdata' 3/3...
OKAY [  1.371s]
finished. total time: 49.436s
Flashing oem partition..
target reported max download size of 536870912 bytes
sending 'oem' (163040 KB)...
OKAY [  5.150s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 5.152s
Is there a remedy to this issue and where is likely to be the the issue?

EDIT: Interesting. Booted to Jolla Recovery and requested option 1) Reset device to factory state. Seemed to boot, strangely enough.

Last edited by oenone; 2017-10-11 at 18:07.
 

The Following 3 Users Say Thank You to oenone For This Useful Post: