We have moved to a new Sailfish OS Forum. Please start new discussions there.
0

Resetting phone to factory settings in Recovery Mode? [answered]

asked 2016-01-21 22:25:51 +0300

vlad gravatar image

updated 2016-01-21 23:00:02 +0300

I tried to update to Taalojärvi with some troubles. I got a black screen now and try to resset the device to factory settings by following this

https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-do-I-use-the-Recovery-Mode-

instructions.

mkdir  -p  /mysd
mount  /dev/mmcblk1p1  /mysd
cp -f /mysd/recovery-menu  /usr/bin/recovery-menu
ls -l /usr/bin
umount /mysd
mount -t btrfs -o skip_balance /dev/mmcblk0p28 /mnt/
/usr/bin/recovery-menu

After I choise  1) Reset device to factory state

-----------------------------
     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

Wait Wait Wait...........1 min 2 min x min.... nothing happens....

Somebody an Idea?

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by JSEHV
close date 2016-02-01 17:55:44.909964

Comments

Try option 5 first! ;)

Kollin ( 2016-01-22 08:02:05 +0300 )edit

Option 5 than reboot the phone After Reboot II choise the option one and ::

rm: can't remove '/mnt/@/system/usr/keylayout/Vendor_046d_Product_c299.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/Vendor_046d_Product_c532.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/Vendor_054c_Product_0268.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/Vendor_05ac_Product_0239.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/Vendor_22b8_Product_093d.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/atmel_mxt_ts.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/cyttsp-i2c.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/gpio-keys.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/keypad_8960.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/keypad_8960_liquid.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/philips_remote_ir.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/qwerty.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/samsung_remote_ir.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout/ue_rf4ce_remote.kl': Read-only file system
rm: can't remove '/mnt/@/system/usr/keylayout': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/bmd/RFFspeed_501.bmd': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/bmd/RFFstd_501.bmd': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/bmd': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/zoneinfo/zoneinfo.dat': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/zoneinfo/zoneinfo.idx': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/zoneinfo/zoneinfo.version': Read-only file system
rm: can't remove '/mnt/@/system/usr/share/zoneinfo': Read-only file system
rm: can't remove '/mnt/@/system/usr/share': Read-only file system
rm: can't remove '/mnt/@/system/usr': Read-only file system
rm: can't remove '/mnt/@/system/vendor/firmware/libpn544_fw.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/firmware': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/drm/libdrmwvmplugin.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/drm': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/hw/power.qcom.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/hw': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/libWVStreamControlAPI_L3.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/libwvdrm_L3.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib/libwvm.so': Read-only file system
rm: can't remove '/mnt/@/system/vendor/lib': Read-only file system
rm: can't remove '/mnt/@/system/vendor': Read-only file system
rm: can't remove '/mnt/@/system/xbin/bttest': Read-only file system
rm: can't remove '/mnt/@/system/xbin/dexdump': Read-only file system
rm: can't remove '/mnt/@/system/xbin/hciconfig': Read-only file system
rm: can't remove '/mnt/@/system/xbin/hcidump': Read-only file system
rm: can't remove '/mnt/@/system/xbin/hcitool': Read-only file system
rm: can't remove '/mnt/@/system/xbin/tcpdump': Read-only file system
rm: can't remove '/mnt/@/system/xbin': Read-only file system
rm: can't remove '/mnt/@/system': Read-only file system
rm: can't remove '/mnt/@/ueventd.qcom.rc': Read-only file system
rm: can't remove '/mnt/@/ueventd.rc': Read-only file system
rm: can't remove '/mnt/@/vendor': Read-only file system
rm: can't remove '/mnt/@/tmp': Read-only file system
rm: can't remove '/mnt/@': Read-only file system
mv: can't rename '/mnt/rec-20160119_170250_@': Read-only file system
[WARNING] Could not restore rootfs subvolume!
[WARNING] Error while trying to bring the situation back to pre-recovery-process state, the older user data could not be found.
[ERROR] The secondary recovery process didn't complete successfully. 
The software will now exit.
[CLEANUP] Starting cleanup!
[CLEANUP] Umounting top volume...
[CLEANUP] Umounting /mnt

:((

It seems I have to mount the device to mnt rw? But I want try it, may be somebody has an instruction? How to mount correctly rootfs subvolume to recover the device?

vlad ( 2016-01-24 01:05:16 +0300 )edit

i have the exact same issue. Did you fix it? Or did you sent in your device???

JoTh ( 2017-02-10 12:55:50 +0300 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2016-01-26 12:28:37 +0300

vlad gravatar image

After contacting jolla support:here is the answer:

thank you for reporting this output.

If you are following the instructions in our Recovery Mode article https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-do-I-use-the-Recovery-Mode- exactly, it would start to sound like your device would need a repair.

edit flag offensive delete publish link more

Question tools

Follow
1 follower

Stats

Asked: 2016-01-21 22:25:51 +0300

Seen: 886 times

Last updated: Jan 26 '16