[Recovery][crackling] Team Win Recovery Project for the Wileyfox Swift

1,229 posts

Thanks Meter: 4,244

By , Recognized Developer on 28th April 2016, 02:00 AM

Post Reply Email Thread

Page 1 of 2 1 2

Discussion Reviews Feature Requests Bug Reports Loading...

Team Win Recovery Project 3.0.2

Notice: This is a test build as a start to becoming an official build, I am looking for feedback right now - do not consider this stable!

I am currently looking for users to test all the features and report back with what works.
Quote the 2nd post and put a pass or fail in each of the [ ] boxes!
Please, if you can, post your recovery.log after doing the tests that fail, as well as dmesg.log

Code:

adb shell cat /tmp/recovery.log > recovery.log
adb shell dmesg > dmesg.log

WHAT IS TWRP?

Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...

Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.

DOWNLOAD

You can find the device page here:
https://idlekernel.com/twrp/crackling/ (temporary! THESE ARE TEST BUILDS!)

Find instructions on how to unlock and root your device with fastboot here:
https://twrp.idlekernel.com/devices/wileyfoxswift.html (temporary device page - do not download from here!)

CHANGES

v3.0.2-0 - See here for the changes.

FEATURES

MTP support
USB Mass Storage support
Micro SDcard support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format)
NTFS file system support (read, write)
ADB root
Full SELinux support
Built in android 6.0 tree

KNOWN ISSUES

Brightness node not set (unknown location, join #twrp to help!)
Battery status possibly unknown

CONTACT & SUPPORT

You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.

SOURCE CODE

Device tree: https://github.com/jcadduono/android...yfox_crackling
Kernel sources: https://github.com/jcadduono/android.../tree/twrp-6.0
TWRP: https://github.com/omnirom/android_bootable_recovery

CONTRIBUTIONS

Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/

XDA:DevDB Information
Team Win Recovery Project - Wileyfox Swift, Tool/Utility for the Wileyfox Swift

Contributors
jcadduono, The Team Win Recovery Project team
Source Code: https://github.com/jcadduono/android...yfox_crackling

Version Information
Status: Testing
Current Beta Version: 3.0.2-0
Beta Release Date: 2016-04-27

Created 2016-04-28
Last Updated 2016-04-29

Quick Reply Reply

The Following 3 Users Say Thank You to jcadduono For This Useful Post: [ View ]

28th April 2016, 02:00 AM |#2

OP Recognized Developer

Thunder Bay

Thanks Meter: 4,244

Donate to Me

TWRP functional checklist

Code:

Blocking checks
[ ] - Correct screen/recovery size
[ ] - Working touchscreen
[ ] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[ ] - Reboot to system
[ ] - ADB & ADB shell
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on :))
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ ] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level

Minor checks
[ ] - Reboot to bootloader
[ ] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

Quick Reply Reply

The Following User Says Thank You to jcadduono For This Useful Post: [ View ]

28th April 2016, 02:39 PM |#3

Junior Member

Thanks Meter: 1

Blocking checks
[pass] - Correct screen/recovery size
[pass] - Working touchscreen
[pass] - Backup to internal/microSD
[pass] - Restore from internal/microSD
[pass] - Reboot to system
[fail] - ADB & ADB shell
[pass] - Flash zips in Install page
[pass] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks
[ ] - Flash zip with ADB sideload
[pass] - UI colors (red/blue inversions)
[pass] - Screen goes off (and back on

)
[pass] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[pass] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[fail] - Decrypt encrypted /data
[pass] - MTP read/write
[pass] - USB Mass Storage read/write
[pass] - Set brightness level

Minor checks
[pass] - Reboot to bootloader
[pass] - Reboot to recovery
[pass] - Power Off
[pass] - Battery level
[pass] - Temperature
[fail] - Encrypted backups
[pass] - Vibration
[pass] - Screenshot

Attached Files

	recovery.log - [Click for QR Code] (18.2 KB, 24 views)
	dmesg.log - [Click for QR Code] (76.9 KB, 20 views)

Quick Reply Reply

The Following User Says Thank You to Epmak For This Useful Post: [ View ] Gift Epmak Ad-Free

28th April 2016, 11:43 PM |#4

OP Recognized Developer

Thunder Bay

Thanks Meter: 4,244

Donate to Me

Quote:

Originally Posted by Epmak

Blocking checks
[fail] - ADB & ADB shell
[fail] - Decrypt encrypted /data
[fail] - Encrypted backups

Thanks! You're sure adb isn't working? I can't find any reason it wouldn't. :S
I will try CM 13.0 decryption libs instead of CyanogenOS, maybe that will help with encryption.
For the third item, encrypted backups - you were unable to backup say...system, and use the encryption option in the options page?
(if that is so, can you get me a log trying to make an encrypted backup?)

Quick Reply Reply

29th April 2016, 12:45 AM |#5

Junior Member

Thanks Meter: 1

Quote:

Originally Posted by jcadduono

You're sure adb isn't working? I can't find any reason it wouldn't. :S

Yes, i plug phone usb cable.
adb shell
see
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

adb working in another UNOFFICIAL TWRP beroid

Quote:

Originally Posted by jcadduono

For the third item, encrypted backups - you were unable to backup say...system, and use the encryption option in the options page?
(if that is so, can you get me a log trying to make an encrypted backup?)

I use the encryption option, backup can't encrypt.
See log files.

Attached Files

	recovery_encryptbackup.log - [Click for QR Code] (332.5 KB, 8 views)
	dmesg.log - [Click for QR Code] (85.7 KB, 6 views)

Quick Reply Reply

29th April 2016, 03:16 AM |#6

OP Recognized Developer

Thunder Bay

Thanks Meter: 4,244

Donate to Me

Quote:

Originally Posted by Epmak

i don't see any error in the log for encrypted backup? it saved fine?

uploaded test3 if youre up for trying again!

Quick Reply Reply

2nd May 2016, 02:40 PM |#7

Junior Member

Thanks Meter: 0

I'm planning on giving this a run through later (possibly later in the week), but I needed to clarify something in the mean time:

Quote:

Originally Posted by jcadduono

Code:

[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)

Do the above requirements apply to the SDcard, or just the phone internal storage?

(My phone is currently encrypted, so I'm currently stuck with an older CM13 build, so have to flash anew. I haven't tested restoring from backup, and I'm hesitant to potentially lose access to a certain app right now.)

The list of mountable partitions includes a partition named "persist", unsure if this is of any relevance?
Additionally, comparing the Swift's fstab in TWRP to others, it would appear that it might be lacking in the encryption related flags on some mounts?

Also, thanks!

Quick Reply Reply

3rd May 2016, 03:29 AM |#8

OP Recognized Developer

Thunder Bay

Thanks Meter: 4,244

Donate to Me

Quote:

Originally Posted by ryzened

I'm planning on giving this a run through later (possibly later in the week), but I needed to clarify something in the mean time:

Do the above requirements apply to the SDcard, or just the phone internal storage?

(My phone is currently encrypted, so I'm currently stuck with an older CM13 build, so have to flash anew. I haven't tested restoring from backup, and I'm hesitant to potentially lose access to a certain app right now.)

The list of mountable partitions includes a partition named "persist", unsure if this is of any relevance?
Additionally, comparing the Swift's fstab in TWRP to others, it would appear that it might be lacking in the encryption related flags on some mounts?

Also, thanks!

I suppose you can ignore NTFS as the Swift doesn't support OTG storage anyways.
exFAT/vfat/f2fs would apply microSD cards.
ext4/f2fs would also apply to data, however you would need a rom with a kernel/fstab capable of taking advantage of that.

I can remove persist from the fstab, it probably shouldn't be there anyways.

Explain what you think is missing related to encryption? I believe I have everything.

When backing up data, it will be unencrypted unless you select the encrypt backup option (even if the partition is already encrypted), and when restoring a data backup, it will be whatever the partition currently is (if the filesystem is encrypted, then restoring unencrypted data backup will still keep your data partition encrypted), unless you use the [Format Data] button on the Wipe page to remove encryption from the data partition.

Quick Reply Reply

3rd May 2016, 07:16 PM |#9

Junior Member

Thanks Meter: 8

)
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ fail] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level

Minor checks
[pass ] - Reboot to bootloader
[ pass] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

Sorry couldn't test everything, cause can't mount local Storage.

Quick Reply Reply

3rd May 2016, 09:37 PM |#10

Senior Member

Thanks Meter: 111

Quote:

Originally Posted by piratoes

locking checks
[pass ] - Correct screen/recovery size
[ pass] - Working touchscreen
[ pass] - Backup to internal/microSD
[ ] - Restore from internal/microSD
[pass ] - Reboot to system
[fail ] - ADB & ADB shell
error: insufficient permissions for device
[ ] - Flash zips in Install page
[ ] - Flash boot.img/recovery.img using Flash Image in Install page

Medium checks
[ ] - Flash zip with ADB sideload
[ ] - UI colors (red/blue inversions)
[ ] - Screen goes off (and back on )
[ ] - EXT4 support (wipe/format/restore to)
[ ] - F2FS support (wipe/format/restore to)
[ ] - exFAT support (wipe/format)
[ ] - NTFS support (wipe/format)
[ ] - System, Data, Internal Storage, microSD card, and Firmware partitions listed in mount/backup choices
[ fail] - Decrypt encrypted /data
[ ] - Correct date
[ ] - MTP read/write
[ ] - USB Mass Storage read/write
[ ] - Set brightness level

Minor checks
[pass ] - Reboot to bootloader
[ pass] - Reboot to recovery
[ ] - Power Off
[ ] - Battery level
[ ] - Temperature
[ ] - Encrypted backups
[ ] - Vibration
[ ] - Screenshot
[ ] - Resize data partition

Sorry couldn't test everything, cause can't mount local Storage.

error: insufficient permissions for device

I was on linux when I saw this, the problem turned out to be the wheel group in the sudo file was hashed out ran visudo as root and un hashed it
No change, rebooted and the message disapered
Note adb still worked in windows

Quick Reply Reply

6th May 2016, 05:34 PM |#11

Junior Member

Thanks Meter: 0

Thanks for your work! I am looking forward to the Swift becoming officially supported by TWRP.

I tried the test3 build and also couldn't decrypt the data