Develop Bugs

Cyanogen OS system upgrade

Hi all
My friend's wife has a swift with YOG4PAS33J and he says her notifications mention a system upgrade.
Has anyone else noticed same? I ask because https://cyngn.com/support mentiones Cyanogen OS 12.1 (5.1.1) cm-12.1-YOG4PAS33J-crackling.
Thanks

Yes I have installed the upgrade YOG7DAS2FI and now running cyanogen 12.1.1.

Yep - changelog on twitter (Wileyfox).
It seems I haven't posted enough to allow me to post links.

is a ZIP file available for flashing via TWRP?

Dior DNA said:
is a ZIP file available for flashing via TWRP?
Click to expand...
Click to collapse
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver

mermigas said:
Thanks to 4PDA
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45683960
PS Never tried.
I am using CM13 Teamasek's ROM as my daily driver
Click to expand...
Click to collapse
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI

Dior DNA said:
thanks
FYI the 4PDA is YOG7DAS2BC but above was mentioned YOG7DAS2FI
Click to expand...
Click to collapse
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464

mermigas said:
Sorry. My Russian is not so good!!
http://4pda.ru/forum/index.php?s=&showtopic=694867&view=findpost&p=45707464
Click to expand...
Click to collapse
your russian seems good enough
meanwhile https://cyngn.com/support got updated

Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!

seb5049 said:
Hey, I'm new to rooting and I'm wondering how I should go about installing this update. I assume I can't just download it OTA, so what steps should I go through to install the update? Should I use the update pack from cyanogen support (can't post link)? If so, which one? cm-12.1-YOG7DAS2FI-crackling-signed-fastboot-07863145a7.zip or cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip? Sorry for my noobishness!
Click to expand...
Click to collapse
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).

Dior DNA said:
Is your firmware stock? Then OTA should announce itself and install fine (unless perhaps if your phone is encrypted).
Click to expand...
Click to collapse
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.

seb5049 said:
I've rooted my phone using a guide on this forum. I have also installed TWRP recovery.
Click to expand...
Click to collapse
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.

mermigas said:
OK . you can then download the official firmware and install it. When prompted by TWRP recovery to install SU chose NO.
Click to expand...
Click to collapse
Should I install everything in the zip? Won't that wipe all of my data?

seb5049 said:
Should I install everything in the zip? Won't that wipe all of my data?
Click to expand...
Click to collapse
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.

Dior DNA said:
The cm-12.1-YOG7DAS2FI-crackling-signed-81d046434c.zip updater-script does not seem to wipe data.
You may want to wipe dalvik and /cache first though.
Click to expand...
Click to collapse
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?

seb5049 said:
OK, one last thing: How do I flash the zip? Can I just put it on my phone and use TWRP to install it? Or do I have to use adb? And what's dalvik?
Click to expand...
Click to collapse
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success

Dior DNA said:
You flash using TWRP. The zip can be put on sdcard (internal or external).
The dalvik cache holds some sort of compiled java code. For minor upgrades one can perhaps leave it untouched. For major upgrades one typically wipes it. It does not hurt to wipe dalvik cache. After install, it is regenerated as part of the android upgrade.
Note that stock firware is probably unrooted so you may want to reinstall supersu update zip from twrp. Also, upgrade may or may not overwrite twrp with stock recovery so you may have to reflash twrp.
I have not done the upgrade myself (I will one day, I have no Swift, a friend has one).
Success
Click to expand...
Click to collapse
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.

seb5049 said:
Ok, I flashed the update, everything works fine except that every few seconds I get a box that says "Unfortunately, Google Play Services has stopped.". Super annoying!
EDIT: Allowing wakelocks for Google Play Services in Privacy Guard fixes it.
Click to expand...
Click to collapse
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated / changed during or right after upgrade.

Dior DNA said:
@seb5049
Just for my information: did you wipe dalvik-cache?
Google Play and Google Play Services typically may get updated change during or right after upgrade.
Click to expand...
Click to collapse
Yeah, I did. By the way, I disabled the permissions again, but everything's fine now.

Bugs with OxygenOS 4.0.2

I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.

Like any Android version change, you should do a clean install. If you do a factory reset your phone should be fine.

jenil1428569 said:
I just installed the 4.0.2 update, got this new Android 7.
However, upon booting somehow my device cannot detect any sim card. I went to settings, then selected SIM&Network and suddenly settings crashed. I tried selecting Data Usage / More options which also makes settings crash, while other options work fine.
Along with network related settings crashing, some of the system apps, like the new oneplus community thingy and file manager also crashes upon launching the app.
Also, whenever I boot my phone I get this 'dm-verity not started in enforcing mode' screen.
Anyone have a solution? I am seriously confused right now.
Click to expand...
Click to collapse
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/

dbabaev21 said:
Check this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757/
Click to expand...
Click to collapse
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.

jenil1428569 said:
I did the hard reset thingy and factory reset whatsoever, and some system apps not launching have been dealt with. However, my sim card is still not being detected and thos horrendous lag is still present.
Click to expand...
Click to collapse
Ok, good.
Now sideload the OOS v4.0.2. So, everything will go back to normal.

How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?

Kris Chen said:
How did you upgrade to OOS 4.0.2 ? from OOS 4.0.1 ? Or OOS 3.5.4 ? So did you upgrade from stock recovery or TWRP ?
Click to expand...
Click to collapse
I upgraded it from OOS 3.2.8 through TWRP.

OK, May I ask you which one of TWRP version do you use ?
jenil1428569 said:
I upgraded it from OOS 3.2.8 through TWRP.
Click to expand...
Click to collapse

Kris Chen said:
OK, May I ask you which one of TWRP version do you use ?
Click to expand...
Click to collapse
3.0.3_0

The dm-verity problem usually comes if you flash the update and don't flash SuperSU without rebooting, and with the problem with your sim, I would try to insert a different sim and see if the problem persist.
Un saludo.

Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
jenil1428569 said:
3.0.3_0
Click to expand...
Click to collapse

Kris Chen said:
Thanks!
Let me summarize how to flash OOS 4.0.2: You use TWRP 3.0.3-0 to upgrade your OP3 from OOS 3.5.2 to OOS 4.0.2
Well, I would recommend you do so:
(1)Please use Titanium to backup all your files and then copy to your computer.
(2)Upgrade your TWRP 3.0.3-0 to TWRP 3.0.3-1. TWRP 3.0.3-1 can be downloaded from TWRP official site.
(3)Then download complete OOS 4.0.2 to your computer HDD.
(4)Wipe all partition
(5)Copy OOS 4.0.2 to your phone, including of your Titanium App backup files.
(6)Flashing OOS 4.0.2. Then SuperSU 2.79 and google play store.
(7)Reboot to system and complete all necessary settings.
(8)After that, going to google play store and install Taitanium backup. Then restore all your backup files.
(9)Reboot again. Done
God bless !
Click to expand...
Click to collapse
Can I ask why you recommend flashing google play store, when it's included in the complete OOS 4.0.2 ? Seems redundant...

Downgrading to OOS 4.0.2

Sup guys,
I have been using the rooted original roms for a while now with the APT-x codec installed though since 4.0.3 this doesn't work any more. So I would like to downgrade to 4.0.2 for the time being. How would I go about doing this ?

Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
http://downloads.oneplus.net/devices/oneplus-3/

Anova's Origin said:
Select the version of OOS you want, download it from OnePlus's site and flash it through either the stock or custom recovery.
Click to expand...
Click to collapse
Same way as upgrading to a new version? to keep root I would have to flash Supersu ?

Yep.

Can I just use the current twrp and supersu or would I need to download a older version of either?

tdmike said:
Can I just use the current twrp and supersu or would I need to download a older version of either?
Click to expand...
Click to collapse
Yes, you can.
AptX is working good on 4.0.3 with magisk module.
I'm using it at the moment.
But it's broken since 4.1.

So I just had to restore to the current version. My launcher and keyboard kept crashing and I wasn't able to install apps. Seems something went wrong. Anyone any clues?
What I did: take a nandroid, wipe dalvik cache, install 4.0.3, install most recent SuperSU. Wipe dalvik again and reboot.

Rooting success but no root on a7 (2017)

When u was rooting my a7 2017 (nougat) using odin, it said it was a success. So when i turned on the phone, it said that my phones verification has failed and i had to reset to factory defaults. So i did, and when i downloaded an app to check if i have root, it said no. The devices is official and i cant use some of my apps due to rooting. What can u do to fix this issue?

By doing a factory reset it deletes everything, including data and files. Root would have been deleted by doing this.
I think you're at least on December 2017 security patch, that's why root didn't work. There's a guide on how to root if you're on December/January security patch. Good luck!
Check @PMFRTT answer below

I want to know how you can reset the knox counter so i can use like samsung secure folder ir fitness etc

I wish I could help you, but I haven't rooted this phone and haven't tried to reset Knox on my previous devices.

rashisp said:
By doing a factory reset it deletes everything, including data and files. Root would have been deleted by doing this.
I think you're at least on December 2017 security patch, that's why root didn't work. There's a guide on how to root if you're on December/January security patch. Good luck!
Click to expand...
Click to collapse
The ROOT files are located inside the system partition, so a factory reset would not have deleted those. A Factory reset usually wipes the data, cache and dalvik cache partitions.
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
[/COLOR]
SlewedThread444 said:
When u was rooting my a7 2017 (nougat) using odin, it said it was a success. So when i turned on the phone, it said that my phones verification has failed and i had to reset to factory defaults. So i did, and when i downloaded an app to check if i have root, it said no. The devices is official and i cant use some of my apps due to rooting. What can u do to fix this issue?
Click to expand...
Click to collapse
If you could let me know what version of android you are using, what recovery and which file u used to root i might be able to help you

PMFRTT said:
The ROOT files are located inside the system partition, so a factory reset would not have deleted those. A Factory reset usually wipes the data, cache and dalvik cache partitions.
Click to expand...
Click to collapse
You're right, I will update my answer pointing to yours.

My phone was on nougat (7.0), and i used twrp. After it said my phones verification had failed, twrp said that my storage was not mounted

SlewedThread444 said:
My phone was on nougat (7.0), and i used twrp. After it said my phones verification had failed, twrp said that my storage was not mounted
Click to expand...
Click to collapse
Did you flash this boot image patch: https://androidfilehost.com/?fid=24591000424951049 after installing twrp?
That should fix the not mounted problem.
Then try reflashing supersu.

It keeps leading me to "the integrity verification of this device has failed, please do a facotry reset"

Hm for me flashing that file after installing twrp worked

no verity crypt helps
PMFRTT said:
Hm for me flashing that file after installing twrp worked
Click to expand...
Click to collapse
yes, it did the trick for me as well
but I still have no camera
it just keeps stopping

PMFRTT said:
The ROOT files are located inside the system partition, so a factory reset would not have deleted those. A Factory reset usually wipes the data, cache and dalvik cache partitions.
Click to expand...
Click to collapse
Nope, anything Marshmallow and onwards is systemless root. Doesn't touch the SYSTEM partition at all unless system root is forced.
The previous poster was correct. Formatting DATA removes root.
---------- Post added at 09:45 PM ---------- Previous post was at 09:43 PM ----------
basile said:
yes, it did the trick for me as well
but I still have no camera
it just keeps stopping
Click to expand...
Click to collapse
I suggest to use Magisk, development has ceased for SuperSU and its unlikely the issues will be sorted out any time soon.

ashyx said:
Nope, anything Marshmallow and onwards is systemless root. Doesn't touch the SYSTEM partition at all unless system root is forced.
The previous poster was correct. Formatting DATA removes root.
Click to expand...
Click to collapse
Oh, i didn't know that, thanks! Might aswell go ahead and delete my post, to not confuse anyone

What u want to know is how to use stuff like secure folder or samsung fitness since i dont hsve root but it says i have root.

SlewedThread444 said:
What u want to know is how to use stuff like secure folder or samsung fitness since i dont hsve root but it says i have root.
Click to expand...
Click to collapse
As previously advised you are removing root by factory resetting the device.
The integrity check is failing because you have made modifications to the device.
I'm guessing the root method you are using is cf_autoroot?
My advice is to flash supersu with twrp.
It's important to format the data partition then apply the dmverity/encryption patch when rooting with supersu or you can simply FORMAT data then flash Magisk which will do it all for you.

SlewedThread444 said:
What u want to know is how to use stuff like secure folder or samsung fitness since i dont hsve root but it says i have root.
Click to expand...
Click to collapse
So how do i root a7 2017 with magisk then

SlewedThread444 said:
So how do i root a7 2017 with magisk then
Click to expand...
Click to collapse
Flash Magisk 16.0 with TWRP

So how do i flash twrp to the point where there wont be any verification failures.

SlewedThread444 said:
So how do i flash twrp to the point where there wont be any verification failures.
Click to expand...
Click to collapse
Just go to the relevant thread as advised.

SlewedThread444 said:
When u was rooting my a7 2017 (nougat) using odin, it said it was a success. So when i turned on the phone, it said that my phones verification has failed and i had to reset to factory defaults. So i did, and when i downloaded an app to check if i have root, it said no. The devices is official and i cant use some of my apps due to rooting. What can u do to fix this issue?
Click to expand...
Click to collapse
Bro i have the same problem. I update my phone today. And i try to root with cf-autoroot amd later of flash with odin the phone said phones verification has failed.
How do you slove this?? You have root ypur phone?

Substratum, Andromeda, & PitchBlack theme on Android Pie official release

So I just updated to the official release of Android Pie and I am trying to get the PitchBlack theme to work. I am using Substratum V. 999 and newest version of PitchBlack. Has anyone gotten this to work? My phone is rooted and it grants permissions but I get the error "substratum cannot connect to andromeda backend". Is Andromeda still needed? I tried uninstalling and re-installing (all 3), rebooting, following the instructions and using Substratum CI. Nothing seems to work. I can build and enable the overlays but when I reboot, there is nothing in the overlay manager to enable. Any help would be appreciated. Thanks

kj13569 said:
So I just updated to the official release of Android Pie and I am trying to get the PitchBlack theme to work. I am using Substratum V. 999 and newest version of PitchBlack. Has anyone gotten this to work? My phone is rooted and it grants permissions but I get the error "substratum cannot connect to andromeda backend". Is Andromeda still needed? I tried uninstalling and re-installing (all 3), rebooting, following the instructions and using Substratum CI. Nothing seems to work. I can build and enable the overlays but when I reboot, there is nothing in the overlay manager to enable. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Well known issue my friend. First, clear substratum app cache/data and uninstall it. After you reboot use this version. https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
It's the 998 version. When you build your overlays, select "build and update" Then reboot, go to substratum manage and enable them :good:
And since your rooted, get rid of Andromeda :good:

Badger50 said:
Well known issue my friend. First, clear substratum app cache/data and uninstall it. After you reboot use this version. https://drive.google.com/file/d/1S_2XmrGn8l5-zjnE24fvwPt8FiKnnt-b/view?usp=drivesdk
It's the 998 version. When you build your overlays, select "build and update" Then reboot, go to substratum manage and enable them :good:
And since your rooted, get rid of Andromeda :good:
Click to expand...
Click to collapse
That worked! Thanks!

This workaround isn't working for me. I'm using version 998 and I keep getting the "please compile this overlay before applying"
Steps:
1) I was previously using 999. Killed app, cleared cache, uninstall.
2) I installed 998 as mentioned here.
3) Restarted, "build and update" on PitchBlack. Restart
4) Tried change overlay states for that theme. I get the message that you need to compile first.
5 )Cleared cache and killed app once again.
6) Uninstalled all substratum themes.
7) Reinstall pitchblack and restart.
8) Perform build and update step for pitchblack
9) Restart and again tried applying it . Same compilation message
I noticed when I perform "build and update," it zooms through the steps super fast (takes like a second and a half) and gives compilation errors.
Any ideas?

davidisflash said:
This workaround isn't working for me. I'm using version 998 and I keep getting the "please compile this overlay before applying"
Steps:
1) I was previously using 999. Killed app, cleared cache, uninstall.
2) I installed 998 as mentioned here.
3) Restarted, "build and update" on PitchBlack. Restart
4) Tried change overlay states for that theme. I get the message that you need to compile first.
5 )Cleared cache and killed app once again.
6) Uninstalled all substratum themes.
7) Reinstall pitchblack and restart.
8) Perform build and update step for pitchblack
9) Restart and again tried applying it . Same compilation message
I noticed when I perform "build and update," it zooms through the steps super fast (takes like a second and a half) and gives compilation errors.
Any ideas?
Click to expand...
Click to collapse
I had problems with pitchblack using the latest updated substratum. I went back to 998 and that version worked for me. Not sure what's going on with yours.
Are you on a clean install of Android pie or did you dirty flash?
I am on a clean flash and pitchblack works fine with 998.

Clean but forgot I installed some mods in twrp using Tulsa aroma mod for themes

I'm new to using substatum, is this pitch black theme found in play store or elsewhere?

Fe Mike said:
I'm new to using substatum, is this pitch black theme found in play store or elsewhere?
Click to expand...
Click to collapse
You can buy it from play store
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
You can buy it from play store
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thank you much

I found ethereal theme works great for Android pie. I have had issues with other overlays blanking out notifications or not showing them at all. Ethereal all notifications are readable.

I've tried to get pitch black to work but to no success. I have 998 subsrtatum from previous poster. If I select all and pick the settings I want, it compiles but with errors. Lot of errors with dialer. If I just do the system only it will compile successfully but upon reboot it's not in the manager. I'm on stock pie, with ElementalX and magisk.

Same here
---------- Post added at 01:30 AM ---------- Previous post was at 01:17 AM ----------
Uninstalling Andromeda fixed it

kronikings said:
Same here
---------- Post added at 01:30 AM ---------- Previous post was at 01:17 AM ----------
Uninstalling Andromeda fixed it
Click to expand...
Click to collapse
Andromeda is used when your not rooted though, correct? I've never used it.

Fe Mike said:
Andromeda is used when your not rooted though, correct? I've never used it.
Click to expand...
Click to collapse
Yeah I had it installed from before I was rooted and didn't realize it but once I removed it I was able to see my installed themes in the manager...

Yeah Andromeda won't work for P