[ROM][UNOFFICIAL][OREO] CrDroid 4.6 for Wileyfox Swift 2/Plus/X

[nikith290]

v4.7 [27.10.2018] update
=====================
* upstream
* marmite: fix fingerprint for 3rd party apps

Скачать: ROM | Recovery | Bootloader (G.Drive)

 

[beamscotty]

Guys, as I posted in another thread, I returned the defective Swift2x, got my money back and purchased another - supposedly brand new - from Germany. Got delivery yesterday.

I unlocked the boot loader, flashed TWRP and tried to back it up. No go. TWRP was complaining that it could not mount any partition at all. Tried to wipe it. Same errors. Ignoring the errors, I flashed crDroid from here, which actually installed and booted. Very strange.

I booted in to recovery again, I got the usual "your bootloader is unlocked" message, then the white Wileyfox screen, followed by the "Your device is corrupt" screen. See picture attached. Pressing power, it continued in to TWRP. At this point I could wipe/reformat all partitions.

Proceeded to do a clean install, by first flashing the latest/recommended bootloader from here, followed by crDroid and Gapps together, as it should be done. All working fine. Restored all my apps and data from the Google cloud, finished configuration. No worries.

Question: Is there any way to get rid of the "corrupt" screen on a Swift2x? This is the 32GB model. From reading, I have seen that partition size has something to do with the device verification. Would "dm_verity enforcing" or disabling dm_verity fix it? BTW: Phone is unencrypted. Is it because the ForceEncrypt flag is set on the 2x? There is a zip one can flash which disables dm_verity and ForceEncrypt in one go here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

I am reluctant to go any further, until I get some feedback or recommendations from the devs (or anyone in the know). I certainly don't want to end up with a bricked device, or loose my IMEI's like on the previous 2x (I suspect it was the victim of some procedure before I got it. It wasn't even as described on ebay, being the 16GB model but advertised as a 32GB).

Any advise?

 

[beamscotty]

Right. Solution to the second warning screen with the red text, to anyone in doubt:

1. Turn on root for apps
2. Launch a terminal
3. su
4. reboot "dm-verity enforcing"
Done.
Can of course be done via adb or TWRP terminals.

Thanks for the help, guys!

 

[Ontanium]

Seems good but the flash light and camera doesn't work. I'm wondering what else.

 

[nikith290]

Seems good but the flash light and camera doesn't work. I'm wondering what else.

I dont think that this is a ROM issue.

Can you make a logcat and dmesg and provide it to me?

 

[Ontanium]

I dont think that this is a ROM issue.

Can you make a logcat and dmesg and provide it to me?

Maybe another time when I have more money and free time. This is kind of my primary phone so going to try Lineage 15.1 again.

If it isn't the rom, then what is it? Or what could it be?

 

[nikith290]

Maybe another time when I have more money and free time. This is kind of my primary phone so going to try Lineage 15.1 again.

If it isn't the rom, then what is it? Or what could it be?

I cant tell you what is this - thats why i need a log's

 

[beamscotty]

I can confirm that both flashlight and camera works OK on the four Swift 2 and 2x I have installed this version on.

 

[Ce Doresti]

I can confirm that both flashlight and camera works OK on the four Swift 2 and 2x I have installed this version on.

really in my version phone swift 2x 32gb no work camera. i confirm, i test all rom, and all stop work camera.

 

[Sarkie]

Latest version.

Can't rapid charge anymore.
Charging when phone is off, looks like charging but ends up at 0.
F2FS won't load if system or data is formatted (not tested before)

 

[beamscotty]

Latest version.

Can't rapid charge anymore.
Charging when phone is off, looks like charging but ends up at 0.
F2FS won't load if system or data is formatted (not tested before)

Rapid charge works fine for me on several devices. Using original orange cable and Aukey fast charger mode 3

F2FS, AFIK, you can only use F2FS on the data partition. I've tested both ext4 and F2FS on all me devices, nor problems.

I am using latest build.

 

[KevMetal]

i have downloaded this from different browsers and laptop and pc and phone and i ALWAYS get .zip corrupted error messages

*edit: i managed to flash the .zip by first wiping system partition, rebooting to recovery , then flashing the zip ..who knows why ...

Rom running like a charm , thanks . I'm very content ..xposed and su runming without even 1 fc or random crash ...

:good::victory:

great job @nikith290 ! :highfive:

 

[KevMetal]

Right. Solution to the second warning screen with the red text, to anyone in doubt:

1. Turn on root for apps
2. Launch a terminal
3. su
4. reboot "dm-verity enforcing"
Done.
Can of course be done via adb or TWRP terminals.

Thanks for the help, guys!

* I tried your "fix" for the boot warning6 screen but these commands did nothing for me ...on reboot the same splash screen appears anyway ...however.. it's not really anything to worry about ...all new phones trigger a warning or boot splash warning that bootloader has been unlocked ..

---------- Post added at 07:25 PM ---------- Previous post was at 07:20 PM ----------

everything works for me ...flashlight, camera and fast charge ...haven't checked charging when phone is off ..