Page 23 of 36 « First 132122 23 242533 Last »
Reply
Thread Tools
deprecated is offline deprecated
2017-10-10 , 03:28
Posts: 300 | Thanked: 962 times | Joined on Jun 2010 @ USA
#221
Originally Posted by oenone View Post
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!
Sorry, I wasn't around earlier. Yeah, it's safe to ignore the errors. I've done it a few times as a test procedure on mine, always with the same errors. Glad to see you got it up and running!

FYI, you can flash that recovery image to the phone itself with

Code:
fastboot flash recovery hybris-recovery.img
That way, you can enter recovery whenever you need by powering the phone on while holding Vol. down. No more need to use fastboot on your computer each time.
__________________
Sony Xperia XA2 Ultra SFOS 3 + Sony Xperia X SFOS 3, Nokia N810
 

The Following 5 Users Say Thank You to deprecated For This Useful Post:
meemorph is offline meemorph
2017-10-10 , 13:49
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#222
@oenone: Congrats, you did it. Your phone has a nice huge home partition, is it a 64GB model?

You should flash it to the recovery partition, as @deprecated told you. If your phone has troble you can use it as described.

Have fun!
 

The Following User Says Thank You to meemorph For This Useful Post:
mariusmssj is offline mariusmssj
2017-10-10 , 15:31
Posts: 951 | Thanked: 2,344 times | Joined on Jan 2012 @ UK
#223
From the Hardware Adaptation sources and instructions

ChangeLog

2017-10-10: Switching to blobless builds, you no longer have to download SW binaries to build things, will only need them to flash the image
__________________
N9/N950 Kernel update project
VLC remote for Sailfish
 

The Following 4 Users Say Thank You to mariusmssj For This Useful Post:
m4r0v3r is offline m4r0v3r
2017-10-10 , 17:59
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#224
Ill get a new image up in a few days, i dont have access to my build machine atm so can ya do :P
 

The Following 7 Users Say Thank You to m4r0v3r For This Useful Post:
mousse04 is offline mousse04
2017-10-10 , 18:23
Posts: 443 | Thanked: 282 times | Joined on Oct 2011 @ Grenoble, France
#225
Originally Posted by mariusmssj View Post
From the Hardware Adaptation sources and instructions
These instructions are strange to me : I had in mind that now, flashing will no more touch the blobs partition? So, why it could be needed to flash ... ?
 

The Following User Says Thank You to mousse04 For This Useful Post:
oenone is offline oenone
2017-10-11 , 01:39
Posts: 84 | Thanked: 146 times | Joined on Feb 2015
#226
Originally Posted by meemorph View Post
@oenone: Congrats, you did it. Your phone has a nice huge home partition, is it a 64GB model?
Yes, it is the dual-sim 64GB model. Was cheaper than the regular version.

Originally Posted by meemorph View Post
You should flash it to the recovery partition, as @deprecated told you. If your phone has trouble you can use it as described.
Originally Posted by deprecated View Post
Sorry, I wasn't around earlier. Yeah, it's safe to ignore the errors. I've done it a few times as a test procedure on mine, always with the same errors. Glad to see you got it up and running!

FYI, you can flash that recovery image to the phone itself with

Code:
fastboot flash recovery hybris-recovery.img
That way, you can enter recovery whenever you need by powering the phone on while holding Vol. down. No more need to use fastboot on your computer each time.
Thank you meemorph and thank you depreciated.

Are there any negatives to flashing Jolla Recovery if one plans to forget about Android? It certainly does have a much more "wholesome" (maybe the word I am looking for is "powerful"?) shell than TWRP.

My initial reluctance stems from typing on a small touch screen to be such a drag I would almost rather wait until I can fastboot via a computer to fix an issue via a keyboard rather than trying to get that sorted out on the device itself.
 

The Following 2 Users Say Thank You to oenone For This Useful Post:
nieldk is offline nieldk
2017-10-11 , 04:29
Posts: 1,293 | Thanked: 4,319 times | Joined on Oct 2014
#227
Originally Posted by oenone View Post
Are there any negatives to flashing Jolla Recovery if one plans to forget about Android? It certainly does have a much more "wholesome" (maybe the word I am looking for is "powerful"?) shell than TWRP..
No, and if you for some reason needs TWRP, you can either flash it back, or just boot it.

fastboot boot TWRP. Img
__________________
You can still support my work by donation - click here
 

The Following 4 Users Say Thank You to nieldk For This Useful Post:
suicidal_orange is offline suicidal_orange
2017-10-11 , 06:49
Posts: 177 | Thanked: 427 times | Joined on Sep 2017
#228
Is there any news on the compact port of this? All I can find are a couple of encouraging looking snippets on gitlab and comments on the announcements and official questions which get officially answered 'no', but so do questions about Linux flashing. Supported and working are not the same thing...

Ideally I'd like a compact with predictive text but if it's different enough that no-one's got it working yet I'm guessing there's no hope the official build will work and I should pick up a full size X?

I can't last much longer on this Z3C with intermittent vibration and an SD card that pops out even if AOSP with no apps was lovely, which it isn't!
 

The Following 2 Users Say Thank You to suicidal_orange For This Useful Post:
meemorph is offline meemorph
2017-10-11 , 08:23
Posts: 204 | Thanked: 443 times | Joined on Jul 2012 @ Germany - Potsdam
#229
Originally Posted by nieldk View Post
No, and if you for some reason needs TWRP, you can either flash it back, or just boot it.

fastboot boot TWRP. Img
The last twrp-3.1.1-suzu-2017.08.22.img did not work correctly on my Xpera X f5121. It looks good, but cannot access all partitions. The hybris-recovery is atm the better choice, you need terminal and linux skills.
 

The Following User Says Thank You to meemorph For This Useful Post:
acrux is offline acrux
2017-10-11 , 11:04
Posts: 287 | Thanked: 618 times | Joined on Jan 2011 @ Estonia
#230
Status update(if changed) after upgrade to 2.1.3.3
Originally Posted by acrux View Post
2. Only 3 Ambiences are selectable.
Seems to be fixed after last weekend updates.

3. Doubletap wake does not work all time at the first try. Usually there are several attempts needed.
Next time, before reporting, remove the protective film

5. During the call the volume is very low even at maximum level. Not usable at street noise level...
The same - next time, before reporting, remove the protective film

5. No internet connection sharing (actually a showstopper here)
Still the same

7. Not possible to install any openrepos.net client (warehouse, storeman)
Seems to be OK now.

Addition: Hardware camera button does not work yet
Last edited by acrux; 2017-10-11 at 12:18. Reason: Addition
 

The Following 2 Users Say Thank You to acrux For This Useful Post:
Reply
Page 23 of 36 « First 132122 23 242533 Last »

« Previous Thread | Next Thread »
Thread Tools

 
Forum Jump


All times are GMT. The time now is 01:51.

Contact Us - Home - Archive - Top