chebe: (Default)
2019-12-09 09:24 pm
Entry tags:

Sailfish X for Xperia 10

Jolla confirmed that they wouldn't be upgrading the version of Android that Sailfish X for the Xperia X handset from 4.4 to 8. Slack had sent me an email telling me to upgrade my Android version because it doesn't have TLS built in. Jolla had an offer on Sailfish X. The new handset, the Xperia 10, was one-third off in Black Friday sales. So, in short, I have a new phone.

There are new instructions for flashing, but I found myself needing to use my own instructions from last time to get the drivers working. I'm not sure if it's just because I had the previous version installed or not. Main difference is you don't need to use Emma. But I still had to do the Disable Driver Signature Enforcement dance. Fun. But it is up and running now. And a lovely handset to go with the security improvements.
chebe: (Default)
2019-03-02 02:08 pm
Entry tags:

Sailfish X for Gemini

Jolla finally released Sailfish X for Gemini. Gemini are old school PDAs. Or, customised Android smart phones (with or without the phone bit) with physical keyboards. I've been using Sailfish as my phone OS for a few years now, and I love anything with physical buttons, so I was all in.

I'm glad I got some practice in with the Community edition before the official release, because it is not the smoothest process. Here's the current state of things;

- Following the Planet Computers guide download the flashing tool.

- Go to the Partition Tool and set up your partitions. This is the main pain point. With the Community edition of Sailfish I was able to treble-boot my Gemini; #1 Android, #2 Debian, #3 Sailfish. But now it appears that Sailfish must be in the first partition, and you can't boot linux alongside it. It could be an error in the tool, but it is frustrating. Okay, so my new partitions are #1 Sailfish, #2 Android. Fine, now I'll download the Scatter File, the Gemini base firmware, and Sailfi... err... the download link goes to the Jolla shop. When you've paid for the OS you get an email telling you to use the Planet Computers documentation, which is what led us to this circle. Luckily there's a way out. The "Firmware List (including older versions) and MD5 checksums" link under the poorly named "Download Sailfish OS firmware" button is what you want. Follow it and download the sailfish.zip.

- Okay, so do follow the documentation, but in summary; Create a folder called 'Gemini' (the flash tool is configured to look for it). Put the Scatter File in there. Unzip the Gemini firmware into there too (make sure not in a folder). Also unzip the sailfish.zip into the same folder. Then run the tool. (If you're having difficulty 'restarting' Gemini just disconnect/reconnect the USB cable.)

- Boot up and configure your new OSs.

Good point, the paid-for Sailfish version has access to the basic Jolla apps, unlike the Community version, which are really useful. But, neither version has an Android compatibility layer, so no Android apps, which does limit its potential. You have to turn on 'Developer Mode' to get a terminal, and most of the screen is obscured by an unnecessary on-screen keyboard. It's not Android-compatible, it's not a fully featured linux, and I can't multiboot with a linux either? It is great to see Sailfish working on more devices, and hopefully these are all just teething problems, but it is frustrating.
chebe: (DarkStare)
2017-11-20 12:13 pm
Entry tags:

Sailfish X, part 5

The other time sink was my Sailfish X smartphone.

Saturday morning I attempted to check my email. The phone became unresponsive. I turned it off. It took a very long time doing this, as demonstrated by the red LED staying lit for, it seemed, an age. I left it alone for a while, then tried to turn it back on. Nothing. I attempted to charge it. Nothing. Utterly unresponsive.

Well, since I'd paid for it I contacted Jolla Support. The automated email reminded me that they don't work weekends.

Monday morning I get a reply telling me the whole system seems unstable and that I should reflash with the latest image (it also appears the ota update didn't take). This confused me, as my device was still refusing to either turn on or charge.

The crucial bit of information was that the holding down Volume-Down or Volume-Up while plugging in to your computers USB port requires less power than even charging the battery directly from mains.

So after it had siphoned off a trickle of power I could charge it from mains once again. The battery was 0%. (It had been somewhere around 80% before all this happened.) Once charged up enough I could boot into the unstable system and get a data backup. Once fully charged I'll reflashed with the newer image.

I am extremely disappointed that this happened after I followed all Jolla's and Sony's official instructions. But hey, software does strange things. Here's hoping it was a once-off.

In related news, life without a smartphone is really pleasant.
chebe: (Default)
2017-10-11 05:13 pm
Entry tags:

Sailfish X, part 4

Once you got the Emma tool you need to make sure the phone is running a high enough version of Android (before you replace it). Connect the phone to Windows while holding the Volume Down key. LED will go green. Select a service of at least build version 34.3.A.0.228, and Apply Service to phone. Disconnect, boot it up, go through Setup Wizard, turn it off.

Download Sailfish OS (or buy it if you haven't already) and the Sony binaries (for an older version of Android). Extract both into one folder.

Connect phone to Windows while holding the Volume Up key. LED will go blue. Run the flash-on-windows.bat script. Follow on screen instructions, then reboot phone into SailfishX.

Also, there are official instructions now.
chebe: (Default)
2017-10-06 11:46 am
Entry tags:

Sailfish X, part 3

It's confirmed that you will have to use Windows, and Sony's tool Emma, to put Sailfish X on your Xperia X. (It's nice to see that Xperia X has been added to the flash tools list of supported devices.) So next step is installing that, and learning how to use it. Of course, you can try installing other ROMs now. You only have to wait for Sailfish X.
chebe: (Default)
2017-10-04 03:17 pm
Entry tags:

Sailfish X, part 2

Sales have opened, if you are due a refund and you get the email offering you to exchange part of your refund for a voucher. Look at it, so close, and yet...

Servers are currently 502-ing when I attempt to login in to redeem my voucher. Downloads don't start for a week, so I suppose there's plenty of time...

But. If you happen to be at 404 this weekend, and need your Xperia X unlocked, but lack a Windows OS, I can help out.

edit
After two hours I finally got through to purchase my copy.

If you are in the refund scheme but didn't get an email about the voucher, search your email for 'Jolla tablet refund survey access link'. It's the same link for the voucher option.
end edit
chebe: (HandAgainstGlass)
2017-09-29 11:54 pm
Entry tags:

Sailfish X, part 1

I'm preparing for SailfishX. It isn't on sale yet, but there's a lot to do before you get there. This is part 1; unlock the bootloader. On Windows 10. (I do like a challenge.)

First thing is first, Jolla are only supporting one model initially; the Sony Xperia X (F5121), single SIM version. And it needs to be network unlocked, so grab a SIM-free version.

The next part is also known as, how to void your warranty and factory reset your device while following Sony's official instructions. Doesn't that sound like fun? Note; this is not reversible.

Visit the Sony unlock bootloader page, read all the horrible notices, select your device from the dropdown menu, and click Continue.

Sony want your email address. They'll give you a keypad combination you can use to make sure your bootloader can be unlocked.
edit
1. In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
2. Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says “Yes,” then you can continue with the steps below. If it says “No,” your device cannot be unlocked.
end edit
And a code to get your IMEI. They want that too. They'll email you a link to your own personal unlock code, and instructions on how to use it.

1. Download the Android SDK. You don't need Android Studio, I mean, you really don't, unless you want to write Android apps and spend the rest of your life installing massive updates.

2. I'm on Windows, so I need to get Sony's modified fastboot driver. Extract this, copy android_winusb.inf to C:\Users\$USER\AppData\Local\Android\sdk\extras\google\usb_driver, replacing the existing one.

3. Boot up your Xperia X. Prepare it;
Settings > About Phone > Build number (click on this quickly multiple times until it tells you you've unlocked Developer mode)
Settings > Developer options > USB debugging (enable)
Settings > Developer options > OEM unlocking (enable)
Turn off phone.

4. Hold down the Volume Up button on your phone, as you connect it via USB to your computer. The phone's LED will go blue.

5. On your computer go to C:\Users\$USER\AppData\Local\Android\sdk\platform-tools and run fastboot devices.

Possibility A. This lists your device with no errors, go to 6.

Possibility B. This lists nothing. Go to Device Manager. You will see an Exclamation Point over a device, called something like S1FastBoot. Open up it's Properties, then Upgrade Driver, search specific path on your computer, and point to the Sony fastboot driver from before (C:\Users\$USER\AppData\Local\Android\sdk\extras\google\usb_driver). This might work, but it probably won't, giving an error about a lack of signature and that the driver was probably altered. It was, by Sony. So now you have to Disable Driver Signature Enforcement temporarily.

Disconnect the phone. Hold down a Shift key as you Restart your computer. When it reboots it will offer you the Advanced Startup Options menu. Select through; Troubleshoot > Advanced Options > Startup Settings. Then you'll have to press 7 to select Disable Driver Signature Enforcement. Let it boot back into Windows. Go back to Device Manager and Upgrade Driver again. This time it should succeed.

Run fastboot devices again, and it should also succeed.

6. Time to actually enter the bootloader unlock key. Still in C:\Users\$USER\AppData\Local\Android\sdk\platform-tools run the command with the code Sony provided. -i 0x0fce is the manufacturer code. oem unlock is what you want to do. The rest is your device code.
fastboot -i 0x0fce oem unlock 0xABCDEF0123456789
(If you get a FAILED (remote: Command not allowed) at this point you probably haven't enabled OEM unlocking on the phone. Go do that.)

OKAY [ 0.188s]
finished. total time: 0.188s


This undramatic output confirms you have successfully unlocked your bootloader. And probably voided your warranty. And reset your device to factory state, wiping internal memory. Losing some of their keys, possibly disabling some of their hardware and optimisations. Unable to undo. And you still don't have root. But you're closer to a freer device. Right?