Reply
Thread Tools
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#211
Originally Posted by karlos devel View Post
Yeap I will. I also see people here like protecting xperia DRM. please I not one of these.
As far as I understand the process of the oem move, it should be ok for you, if you do only the second part within the recovery shell and try reboot after that.
 

The Following User Says Thank You to meemorph For This Useful Post:
Posts: 14 | Thanked: 25 times | Joined on May 2015 @ Leuven
#212
Hi,

Originally Posted by deprecated View Post
Depending on your distro, you need to install 32-bit libraries. As example, for Ubuntu:

Code:
sudo dpkg --add-architecture i386
For Fedora:

Code:
sudo dnf install glibc.i686
I use Linux Mint what i have done and found on the net is sudo apt-get install ia32-libs, and that worked out.
__________________
---
Best regards!

Rudi Timmermans.
 

The Following 3 Users Say Thank You to Xray2000 For This Useful Post:
karlos devel's Avatar
Posts: 137 | Thanked: 392 times | Joined on Mar 2013 @ Guate
#213
Originally Posted by meemorph View Post
As far as I understand the process of the oem move, it should be ok for you, if you do only the second part within the recovery shell and try reboot after that.
Thank u very much. I already did that but same not boot.
 

The Following 2 Users Say Thank You to karlos devel For This Useful Post:
Posts: 84 | Thanked: 146 times | Joined on Feb 2015
#214
Originally Posted by meemorph View Post
@oenone: others wrote it before, do it from recovery shell. You need a recovery image "hybris-recovery.img". It's build in the syspart environment.

First read and understand this

Then start the phone in fastboot mode (vol-up + plugin usb). Your led sould light blue. To boot the recovery do this:
Code:
sudo fastboot boot hybris-recovery.img
Your phone boots to recovery (very small text displayed). You do
Code:
telnet 10.42.66.66
Select topic 3 (shell)
Continue in doing the change with my parameters. Maybe you do not want to enlarge the rootfs by 4GB (I have my home on sd card and do not neet the phones internal home partition). 2GB are enougth, change the 4096M to 2048M. Do all the steps !at your own risk! before you reboot.
Thank you for these instructions. Also thank you to the others that also provided advice on my predicament.

I flashed via fastboot a boot image supposedly claiming to be 34.3.A.0.238 and then restored the TWRP recovery partition, and Sailfish reinstalled just fine.

However, I have encountered a problem. I can place the device into fastboot mode (from power: off Volume-Up button depressed + insert USB cable. Light turns a delightful shade of blue and device is listed in fastboot) but I am unable to boot it into recovery.

Neither
Code:
sudo fastboot boot $ANDROID_ROOT/hybris/mw/droid-hal-img-boot-f5121/installroot/boot/hybris-recovery.img
nor
Code:
sudo fastboot boot hybris-recovery.img
did anything except for print me a complaint of "cannot load '[hybris-recovery.img]": No such file or directory.

I tried to use the terminal in the TWRP recovery, but lvm seems to be missing from that.

Is there anything else I can try?

Also, is there a way to confirm that one is on 34.3 (bootloader version, I suppose} without an installation of Android?
 

The Following 2 Users Say Thank You to oenone For This Useful Post:
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#215
https://sailfishos.org/wiki/Sailfish_X_Build_and_Flash

If you build the sailfishX you find it under syspart, not that ANDRIOD_ROOT. But I think, you never made your own build.
 

The Following 2 Users Say Thank You to meemorph For This Useful Post:
Posts: 300 | Thanked: 962 times | Joined on Jun 2010 @ USA
#216
Originally Posted by oenone View Post
Thank you for these instructions. Also thank you to the others that also provided advice on my predicament.

I flashed via fastboot a boot image supposedly claiming to be 34.3.A.0.238 and then restored the TWRP recovery partition, and Sailfish reinstalled just fine.

However, I have encountered a problem. I can place the device into fastboot mode (from power: off Volume-Up button depressed + insert USB cable. Light turns a delightful shade of blue and device is listed in fastboot) but I am unable to boot it into recovery.

Neither
Code:
sudo fastboot boot $ANDROID_ROOT/hybris/mw/droid-hal-img-boot-f5121/installroot/boot/hybris-recovery.img
nor
Code:
sudo fastboot boot hybris-recovery.img
did anything except for print me a complaint of "cannot load '[hybris-recovery.img]": No such file or directory.

I tried to use the terminal in the TWRP recovery, but lvm seems to be missing from that.

Is there anything else I can try?

Also, is there a way to confirm that one is on 34.3 (bootloader version, I suppose} without an installation of Android?
The problem here is that hybris-recovery.img isn't included with the image in the first post. I went through that myself, and decided to just build the HADK/Platform SDK to compile the prerequisites and images.

I've uploaded the hybris-recovery.img here:
http://truthcrime.com/hybris-recovery.img

Let me know if that works for you (or if this is a violation of software distribution rights).

Edit: fixed link, this recovery img works, just tested it.
__________________
Sony Xperia XA2 Ultra SFOS 3 + Sony Xperia X SFOS 3, Nokia N810

Last edited by deprecated; 2017-10-09 at 20:18.
 

The Following 4 Users Say Thank You to deprecated For This Useful Post:
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#217
"or if this is a violation of software distribution rights"

thats the question.
 

The Following 2 Users Say Thank You to meemorph For This Useful Post:
Posts: 84 | Thanked: 146 times | Joined on Feb 2015
#218
Originally Posted by deprecated View Post
The problem here is that hybris-recovery.img isn't included with the image in the first post. I went through that myself, and decided to just build the HADK/Platform SDK to compile the prerequisites and images.

I've uploaded the hybris-recovery.img here:
http://truthcrime.com/hybris-recovery.img

Let me know if that works for you (or if this is a violation of software distribution rights).

Edit: fixed link, this recovery img works, just tested it.
Thank you most kindly. Yes, I did not compile it myself but I chose instead to trust complete strangers from the internet.

But now where (and how) do I place it such that
Code:
sudo fastboot boot hybris-recovery.img
works?

I am really sorry for so many questions!

Maybe I will just wait until Wednesday? Oh, right, the only Windows machine I have is a server and Emma in Sony's infinite wisdom does not want to run on Server 2008 R2. It installs just fine, but doesn't want to run.
 

The Following User Says Thank You to oenone For This Useful Post:
Posts: 300 | Thanked: 962 times | Joined on Jun 2010 @ USA
#219
Originally Posted by oenone View Post
Thank you most kindly. Yes, I did not compile it myself but I chose instead to trust complete strangers from the internet.

But now where (and how) do I place it such that
Code:
sudo fastboot boot hybris-recovery.img
works?

I am really sorry for so many questions!

Maybe I will just wait until Wednesday? Oh, right, the only Windows machine I have is a server and Emma in Sony's infinite wisdom does not want to run on Server 2008 R2. It installs just fine, but doesn't want to run.
Doesn't matter, as long as it's a directory you can read. How have you installed fastboot on your computer?
__________________
Sony Xperia XA2 Ultra SFOS 3 + Sony Xperia X SFOS 3, Nokia N810
 

The Following User Says Thank You to deprecated For This Useful Post:
Posts: 84 | Thanked: 146 times | Joined on Feb 2015
#220
Originally Posted by deprecated View Post
Doesn't matter, as long as it's a directory you can read. How have you installed fastboot on your computer?
It is just the fastboot/adb that one installs on Xubuntu. I added the nilarimogard/webupd8 repository and then apt-got (past tense, haha) android-tools-adb and android-tools-fastboot.

Somehow I get the feeling that I need to have hybris-recovery.img in a directory on my computer and not on the Xperia device. . .

. . .Let me check. . .

. . .Yes, and I found that to be my problem, thank you. Now in age-discriminating font it is telling me to telnet into 10.42.66.66.

Now, the question is what are all these warnings and can I safely ignore them?

Code:
-----------------------------
     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]: 
3

If you continue, this may void your warranty. 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
  2 logical volume(s) in volume group "sailfish" now active
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libGLESv2.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libcutils.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libutils.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "liblog.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libEGL.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libdsyscalls.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libc++.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libc.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libm.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libbacktrace.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libGLES_trace.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libbase.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libunwind.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libprotobuf-cpp-lite.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libnetd_client.so". Will use given name.

Type your devicelock code and press [ENTER] key:
(please note that the typed numbers won't be shown for security reasons)
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libGLESv2.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libcutils.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libutils.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "liblog.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libEGL.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libdsyscalls.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libc++.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libc.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libm.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libbacktrace.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libGLES_trace.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libbase.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libunwind.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libprotobuf-cpp-lite.so". Will use given name.
readlink('/proc/self/fd/3') failed: No such file or directory [fd=3]
warning: unable to get realpath for the library "libnetd_client.so". Will use given name.
[OK] Code accepted.
lvm seems to work but there were still some complaints:

Code:
/ # lvm
lvm> lvscan
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  ACTIVE            '/dev/sailfish/root' [2.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [47.38 GiB] inherit
lvm> exit
  Exiting.
/ # resize2fs /dev/sailfish/home 11G
resize2fs 1.43.1 (08-Jun-2016)
Resizing the filesystem on /dev/sailfish/home to 2883584 (4k) blocks.
The filesystem on /dev/sailfish/home is now 2883584 (4k) blocks long.

/ # lvm
lvm> lvresize -L -4096M /dev/sailfish/home
  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
  WARNING: Reducing active logical volume to 43.38 GiB
  THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce home? [y/n]: y
  Size of logical volume sailfish/home changed from 47.38 GiB (12128 extents) to 43.38 GiB (11104 extents).
  Logical volume home successfully resized
lvm> lvresize -l +100%FREE /dev/sailfish/root
  Size of logical volume sailfish/root changed from 2.44 GiB (625 extents) to 6.44 GiB (1649 extents).
  Logical volume root successfully resized
lvm> lvscan
  ACTIVE            '/dev/sailfish/root' [6.44 GiB] inherit
  ACTIVE            '/dev/sailfish/home' [43.38 GiB] inherit
lvm> exit
  Exiting.
/ # resize2fs /dev/sailfish/home
resize2fs 1.43.1 (08-Jun-2016)
Resizing the filesystem on /dev/sailfish/home to 11370496 (4k) blocks.
The filesystem on /dev/sailfish/home is now 11370496 (4k) blocks long.

/ # resize2fs /dev/sailfish/root
resize2fs 1.43.1 (08-Jun-2016)
Filesystem at /dev/sailfish/root is mounted on /rootfs; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
The filesystem on /dev/sailfish/root is now 1688576 (4k) blocks long.
Rebooted to Sailfish, everything seems to work. Thanks, everybody!
 

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

Thread Tools

 
Forum Jump


All times are GMT. The time now is 11:32.