# Help installing on XA2 - stuck at - Flashing vendor_b partition.. < waiting for device >

Hello people, hoping someone can help - I have an XA2 - bootloader's unlocked, fastboot tools installed on linux, did the OEM unlocking bit and all the other steps - downloaded sailfish 3 file and put the SW binaries file in the same folder - opening a terminal as root - volume up and power key when I start, blue light - then when I type fastboot devices, I get : Found 1 devices: CQ30009HG8 - fastboot - when I them do bash ./flash.sh - I get the text below in terminal, it all seems to go fine at first, then after a minute or so the phone turns on, I get the black screen with the padlock and the warning, then the screen goes to the white background with the sony logo, and the indicator light goes white, then i seem to be hung on Flashing vendor_b partition.. < waiting for device > and I've tried it twice now and can't seem to get past it, any ideas please?? Terminal output below - Thanks

dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # bash ./flash.sh
Detected Linux
Searching device to flash..
Found 1 devices: CQ30009HG8
Fastboot command: fastboot -s CQ30009HG8
Flashing boot_a partition..
sending 'boot_a' (17772 KB)...
OKAY [  0.438s]
writing 'boot_a'...
OKAY [  0.000s]
finished. total time: 0.438s
Flashing boot_b partition..
< waiting for device >
sending 'boot_b' (17772 KB)...
OKAY [  0.448s]
writing 'boot_b'...
OKAY [  0.000s]
finished. total time: 0.449s
Flashing userdata partition..
< waiting for device >
erasing 'userdata'...
OKAY [  2.869s]
sending sparse 'userdata' (514030 KB)...
OKAY [ 12.609s]
writing 'userdata'...
OKAY [  0.000s]
sending sparse 'userdata' (513031 KB)...
OKAY [ 13.990s]
writing 'userdata'...
OKAY [  0.000s]
sending sparse 'userdata' (76364 KB)...
OKAY [  4.710s]
writing 'userdata'...
OKAY [  0.000s]
finished. total time: 34.179s
Flashing system_b partition..
< waiting for device >
erasing 'system_b'...
OKAY [  0.495s]
sending sparse 'system_b' (524284 KB)...
OKAY [ 13.166s]
writing 'system_b'...
OKAY [  0.000s]
sending sparse 'system_b' (61308 KB)...
OKAY [ 18.020s]
writing 'system_b'...
OKAY [  0.000s]
finished. total time: 31.681s
Flashing vendor_a partition..
< waiting for device >
sending 'vendor_a' (340 KB)...
OKAY [  0.015s]
writing 'vendor_a'...
OKAY [  0.001s]
finished. total time: 0.016s
Flashing vendor_b partition..
< waiting for device >


Update: searched & tried 'sudo' before the bash command, makes no difference - the end sequence before it hangs, if it makes any difference, seems to be - the black screen with the warning telling you to lock your device comes up, the blue LED changes to red as the screen chages to a white background with the sont logo, the LED then chages to solid white, for around 5 mins, then it blinks white, don't know if this has any bearing but added it just in case.........

edit retag close delete

Just a message to say that personnaly haven,t got any issue on linux. hope you'll find something.

( 2018-11-30 18:45:38 +0200 )edit

Sort by » oldest newest most voted

Hello! My experience (twice with XA2 4113 on windows 10) it sometimes take a LOOOOONG time for some flashing parts - like 15min or so - so try to wait and wait and wait

Also on both occations some flash parts never finished until i pressed ENTER (???!!! or maybe it was a h*of a co-incidence since this happend at least four times alltogether)

Also2 some of the links in the instructions were forwared by Sony to point to an image that was of wrong version, so please check the IMG version numbers carefully

more

Thanks for the comments, I got the SW binaries from the link in the readme file (on linux) and it linked to: https://developer.sony.com/file/download/software-binaries-for-aosp-oreo-android-8-1-kernel-4-4-nile/ And I can only assume this is the correct version ? I have no idea how I'd even be able to tell if this is right or wrong.....

( 2018-11-30 12:06:17 +0200 )edit

I've downloaded the SW binaries again and replaced the first one I downloaded, run through the procedure again and exactly the same result, stops in the exact same place, dowsn't matter if I leave it 10,20,30 minutes or press enter when the phone starts, tried all sorts, stopping now until I can get more info.....

( 2018-11-30 13:33:00 +0200 )edit

Do you have a possibility to try and flash with a windows PC? Maybe worth a try?

( 2018-11-30 13:48:29 +0200 )edit

No...................... the instructions are dreadful and I wouldn't trust windows to pull the skin off a custard.

( 2018-11-30 16:06:12 +0200 )edit

Hello, I think I had the problem too. "fastboot" was apparently the trigger. After I downloaded the "platform-tools" (https://developer.android.com/studio/releases/platform-tools) and used the included version, everything worked fine. I had to adapt the "flash.sh" slightly to use the downloaded version. Afterwards I had to deactivate the md5-test in the script - at least remove the "exit 1". I hope it helps. Good luck

more

Can you elaborate some more for me ? you downloaded platform tools and did what with it? what do you mean by " I had to adapt the "flash.sh" slightly to use the downloaded version" ? It's a folder with 16 files in it but no instructions ...........

( 2018-11-30 21:54:55 +0200 )edit

i will try:

2. you find the "fastboot" tool in the new folder "platform-tools"
3. now navigate to your extracted Sailfish OS folder (Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED/) and open the file "flash.sh" in an editor
4. go to line 34 and enter behind the "=" the absolute path of the "fastboot" tool form the downloaded "platform-tools" directory. In my case the line looks like: " FASTBOOT_BIN_NAME="/home/michael/Downloads/SailfishOS/platform-tools/fastboot"" If there is an whitespace in your path, escape it.
5. go to line 166 and deactivate the "exit 1". The line should looks like: " #exit 1;"
6. now try with the updated flash.sh
( 2018-11-30 22:03:07 +0200 )edit

The line (34) now reads FASTBOOT_BIN_NAME=/home/dave/Downloads/platform-tools/fastboot it had $1 previously at the end, I removed this, is that correct ? and no "" marks ? ( 2018-11-30 22:25:39 +0200 )edit the path ist correct. but you need the " at the beginning and end: FASTBOOT_BIN_NAME="/home/dave/Downloads/platform-tools/fastboot" and yes, replace$1 with the full path in quotation marks

( 2018-11-30 22:29:15 +0200 )edit

Hung again with a slightly different terminal result, top of the terminal this time I get this (even though it carries on)

dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # bash ./flash.sh


Detected Linux Searching device to flash.. Found 1 devices: CQ30009HG8 Fastboot command: fastboot -s CQ30009HG8

If you look at the original terminal output I posted first, it doesn't say this, so I should replce the sailfish image file off the Jolla site ?

( 2018-11-30 22:46:57 +0200 )edit

I had the same problem. I took a shortcut and flashed line by line and got it through.

sudo ./fastboot flash boot_a hybris-boot.img
sudo ./fastboot flash boot_b hybris-boot.img
sudo ./fastboot flash userdata sailfish.img001
sudo ./fastboot flash system_b fimage.img001
sudo ./fastboot flash vendor_a vendor.img001
sudo ./fastboot flash vendor_b vendor.img001
sudo ./fastboot flash oem_a SW_binaries_for_Xperia_Android_8.1.6.4_r1_v16_nile.img

more

Hello, thanks for the reply, so I just copy/paste the individual lines into a terminal and do them in that order 1 by 1 ? Never done this before on a phone, dozens of linux installs but only on laptops/pc's so I don't want to get this wrong ! I've never seen this option anywhere, is this just the shell script broken down as opposed to automated ? cheers. Dave

( 2018-12-02 21:54:18 +0200 )edit

Ahhh you've put both windows terminal commands in ? So for linux the command without ./ ?

Edit: Yes I worked out it was, still, it's hung at the third line ................. I'm giving it 5 minutes to see if it recovers but I've watched videos where the whole process doesn't take that long ..........

( 2018-12-02 22:08:44 +0200 )edit

If it stalls what do I do ? Stop the terminal/unplug the phone/power down and wait 15 seconds before starting again from scratch or run the last command again without closing the terminal?

( 2018-12-02 22:22:57 +0200 )edit

dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # sudo fastboot flash boot_a hybris-boot.img
sending 'boot_a' (17772 KB)...
OKAY [  0.439s]
writing 'boot_a'...
OKAY [  0.000s]
finished. total time: 0.439s
dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # sudo fastboot flash boot_b hybris-boot.img
sending 'boot_b' (17772 KB)...
OKAY [  0.461s]
writing 'boot_b'...
OKAY [  0.000s]
finished. total time: 0.462s
dave-desktop Sailfish_OS-Jolla-3.0.0.8-h3113-0.0.7.11-FIXED # sudo fastboot flash userdata sailfish.img001
erasing 'userdata'...
OKAY [  2.526s]
sending sparse 'userdata' (514030 KB)Stuck here now !
( 2018-12-02 22:37:31 +0200 )edit

This is practically lines 203-211 broken down to single lines. The problem in my case was that the phone started too early - just before the last line or just when the execution of the last line started - and ended up with white Sony logo. When I run commands line by line, black screen and blue led stays until finished.

( 2018-12-03 05:59:44 +0200 )edit

What worked for me: Jolla Zendesk suggested trying to update fastboot and trying again after, as I was using my PC running LTS (Mint 17.3) the adb was only version 1.0.30 (type " adb version " in terminal to find out) The instructions for that were these I think: <wget https://dl.google.com/android/repository/platform-tools-latest-linux.zip unzip \platform-tools-latest-linux.zip sudo cp platform-tools/adb /usr/bin/adb sudo cp platform-tools/fastboot /usr/bin/fastbootcode> Then a suggestions from the XDA forums: use only USB 2 Ports directly connected to PC mainboard (rear ports on access plate) and the flashing worked flawlessly first time after that and a week of struggling. The process took less than 5 minutes and in this ia a screenshot of the terminal output, I hope this may help someone else. SFOS-Flashing-05-12-2018.png

more

fastboot --version