Ask / Submit
11

Rescue your phone. What to do if btrfs not mounting in write mode.

asked 2016-12-19 10:58:47 +0300

creep82 gravatar image

updated 2016-12-19 13:13:06 +0300

So, i got the problem after new update... Reset to factory defaults does not works in my case,'cause file system has only 1G free space. After entering in rescue mode using telnet 10.42.66.66, i booting a shell (case 4). I tried a lot of option for mounting /dev/mmcblk0p28 in write mode, but i has failed. But i solved it in very simple way)

  1. Go to the rescue mode (eject battery and any cable, push vol down button,hold when plug battery back and push power.) Insert cable.

  2. Connecting via telnet to 10.42.66.66. Choose case 4, etc..

  3. Good bless the netcat,cat and dd) We need copy block device file to our system (my system is linux). Prepare our system for coping - check your ip after plug in cable- my is 10.42.66.67

This for receive side nc -l 1000 > jolla

and for sender side in sailfish shell:

cat /dev/mmcblk0p28 | nc 10.42.66.67 1000

After a few minutes we will get a 14G file with root system. Jolla use BTRFS file system, it support subvolumes so we need to mount it in right way :

mount -o subvolid=0 /home/username /mnt/cf (i have a cf directory for my cf card early so i decide to use it).

Now just use MC - go to the /mnt/cf/@home/nemo and clean for some space (l del all my vids,but i dont care cause i have backup now))))

Then - umount /mnt/cf

4.And we just need to send this file (/home/username/jolla) back as block device mmcblk0p28. On jolla side nc -l -p 1000 | dd of=/dev/mmcblk0p28

on sender side

dd if=/home/username/jolla_test | nc 10.42.66.66 1000

this operation need something about 8000 sec.

So it done... exit from jolla shell and power on your phone.

edit retag flag offensive close delete

Comments

Thats, i think, exactly, what happend to my sisters jolla. Ill try that when ill arrive home!

Huholoman ( 2016-12-20 13:41:16 +0300 )edit
1

Any time, If you need some help just let me know! )

creep82 ( 2016-12-20 15:10:27 +0300 )edit

Thanks, that solution fixed my Jolla too!

JimH ( 2016-12-22 12:17:34 +0300 )edit
1

I din'd have so much space to update, but just prepared the proces with the button, to start the mobile preparation to firmware update, like I usually did always to flush memory and prepare the mobile. Then mobile rebootted and nothing has helped anymore, even the formatting like can see from this telnet session ...


Jolla Recovery v0.3.1

Welcome to the recovery tool! The available options are: 1) Reset device to factory state 2) Reboot device 3) Bootloader unlock [Current state: locked] 4) Shell 5) Try btrfs recovery if your device is in bootloop 6) Exit Type the number of the desired action and press [Enter]: 1

ALL DATA WILL BE ERASED! Clears everything from the device and reverts the software back to factory state. This means LOSING EVERYTHING you have added to the device (e.g. updates, apps, accounts, contacts, photos and other media). Are you really SURE? [y/N] y[CLEANUP] Starting cleanup! [CLEANUP] Umounting top volume... [CLEANUP] Deleting /mnt [CLEANUP] Cleanup done. Mounting /dev/mmcblk0p28 on /mnt sh: unlock: unknown operand

Type your devicelock code and press [ENTER] key: (please note that the typed numbers won't be shown for security reasons) [OK] Code accepted. sh: unlock: unknown operand sh: shell: unknown operand [OK] Factory snapshots found. Resetting procedure started! Backing up current root and home subvolumes. If the backup fails, the old data will be deleted to let the recovery process continue. mv: can't rename '/mnt/@': Read-only file system [WARNING] Couldn't backup rootfs, maybe the filesystem is corruped. The rootfs subvolume will now be deleted to let the recovery process continue. Transaction commit: none (default) Delete subvolume '/mnt/@' ERROR: cannot delete '/mnt/@' - Read-only file system [ERROR] While deleting old user data! [CRITICAL] The current system subvolumes could not be moved or deleted! The recovery process cannot continue! [CLEANUP] Starting cleanup! [CLEANUP] Umounting top volume... [CLEANUP] Umounting /mnt

Please help me!!! I have not development open and not rooted, just normal procedure :( Firmware version Aurajoki V. 2.0.2.51 and I was trying to upgrade to Haapajoki V. 2.0.5.6

PC75 ( 2017-01-04 19:14:58 +0300 )edit
1

I think it's the same problem that i had... Just use this article. Connect again via telnet,and backup your block device with nc. Mount it in your host system,clear something and rewrite it in to your phone again.

creep82 ( 2017-01-08 17:59:27 +0300 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2016-12-26 22:52:32 +0300

Huholoman gravatar image

updated 2016-12-26 23:14:08 +0300

When I was running nc i had to run it this way

nc -lp 1000 > jolla

otherwise it ignored that 1000 as a port and when i used netstat and i used the port shown there it didnt work neither.

Btw. I run Debian testing.

edit flag offensive delete publish link more

Comments

i think nc work a little bit different in some distro's. Which Debian do you use?

creep82 ( 2016-12-26 23:22:11 +0300 )edit

Debian testing, codename Stratch.

Huholoman ( 2016-12-27 10:10:34 +0300 )edit

So, i test it on a Stratch Alpha 8, and after nc -lp 1000 > jolla , i see my 1000 port is open... Show please me your netstat -nlt

creep82 ( 2016-12-27 15:39:41 +0300 )edit

tcp 0 0 127.0.0.1:631 0.0.0.0:* NASLOUCHÁ tcp 0 0 127.0.0.1:25 0.0.0.0:* NASLOUCHÁ tcp 0 0 127.0.0.1:3306 0.0.0.0:* NASLOUCHÁ tcp6 0 0 :::80 :::* NASLOUCHÁ tcp6 0 0 ::1:631 :::* NASLOUCHÁ tcp6 0 0 ::1:25 :::* NASLOUCHÁ tcp6 0 0 :::443 :::* NASLOUCHÁ

Huholoman ( 2017-03-08 20:30:03 +0300 )edit
0

answered 2016-12-22 14:18:40 +0300

jovirkku gravatar image

updated 2016-12-22 14:22:24 +0300

Following the guidelines in the two help articles below on regular basis may help you avoiding the need to use the rescue approach of this post in the future:

edit flag offensive delete publish link more

Comments

That's not true, I've never let my device memory going beyond 9GB and I recently had very big troubles with BTRFS, due to the lack of frequent updates (and their "Optimization process") in 2016.

Sthocs ( 2016-12-28 11:50:31 +0300 )edit
Login/Signup to Answer

Question tools

Follow
6 followers

Stats

Asked: 2016-12-19 10:58:47 +0300

Seen: 605 times

Last updated: Dec 26 '16