If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
As soon as you root any Marshmallow/Nougat phone Android Pay will not work, according to this article
I have never used Android Pay so it doesn't make any difference to me. My phone is much better now that I have debloated it. I also installed Evie Launcher and Halo Browser, both small minimalist apps and everything is really smooth.
Instead of a Debloater, could the Stock ROM not be debloated and rezipped as a custom 'Lite' version?
Thank you very much for the debloater (and the audiomodFirsts things first: After heavily modding the system like you did on Marshmallow, make sure not to update your device through the regular OTA but using a recovery image like the ones posted in this device's forum.
For magisk: are you sure you flashed it correctly? Magisk disables that dmverity message you are mentioning, so maybe you installed an old version or wasn't properly flashed.
My advice is: download everything: the recovery image, the debloater and Magisk. Boot into TWRP, wipe EVERYTHING if possible, including Data cache dalvik cache and system partitions. Once done, flash the recovery image zip, and right after that, without rebooting, flash the debloater and magisk. Reboot and everything should work perfectly
).For the installation, I was not able to install the recovey and then the debloater and magisk (error messages for the both). I needed to reboot after the recovery before installing the debloater and magisk. But all works fine (except the warning message "The dm-verity is not started in enforcing mode...").
In the system process, I've a curious thread called "ninja.bsp.setupwizard"
. Do you have it too ? I think I have to remove it, don't know where it comes from.
System image would still be tampered.
When your phone first boots up, notice the gigantic white Wileyfox logo on orange background that appears? That's ninja.bsp.setupwizard. It's the setupwizard that gets launched before the "standard" (AOSP) one, which is where we configure most of the stuff. I don't know the purpose of the other one but it definitely shouldn't be removed. You may need it if you wipe data of your device.In the system process, I've a curious thread called "ninja.bsp.setupwizard"
New version: Wileyfox-TOS118C-Debloater--11-05-17
Hi all,
A new version of the debloater tool has just been published.
It features:
- New versions for Google Dialer 9.0.155139499, Google Contacts 2.0.7 and Google Messages 2.2.068 (3961439-46.phone).
- Compatibility with newest Wileyfox's firmware: TOS118C, which you can download from here.
____________________________
If you were using a debloated system previously, and you wish to upgrade to newer versions of Wileyfox's firmware/ROM:
0. Don't try to upgrade through Wileyfox's OTA system, since the installation will fail in the recovery saying that your system partition was modified. Even if you didn't flash TWRP and you preserved AOSP's recovery.
1. Download the latest flashable recovery image available (which, in this case, you can grab from the post in link above).
2. Download latest version of flashable Magisk (if you were using it), and the latest version of the debloater tool from this thread.
3. Boot into TWRP recovery (using the Vol- + Power key combo or the OEM menu). Hit Install and locate the flashable recovery image you downloaded in step 1. Flash it.
4. Without rebooting, now flash the debloater tool and, after that, Magisk's flashable zip.
5. Reboot your device, and once it boots up, let it finish upgrading Android (you'll see a notification in your lockscreen). Once it finishes, if you installed Magisk previously, reboot into TWRP recovery like in step 3.
6. If you installed Magisk previously, hit Install and locate the Magisk flashable zip once again. Flash it. Reboot your device and profit!
I hope it's clear for everyone how to correctly upgrade a "debloated" device with the steps above
Hi all,
A new version of the debloater tool has just been published.
It features:
- New versions for Google Dialer 9.0.155139499, Google Contacts 2.0.7 and Google Messages 2.2.068 (3961439-46.phone).
- Compatibility with newest Wileyfox's firmware: TOS118C, which you can download from here.
____________________________
If you were using a debloated system previously, and you wish to upgrade to newer versions of Wileyfox's firmware/ROM:
0. Don't try to upgrade through Wileyfox's OTA system, since the installation will fail in the recovery saying that your system partition was modified. Even if you didn't flash TWRP and you preserved AOSP's recovery.
1. Download the latest flashable recovery image available (which, in this case, you can grab from the post in link above).
2. Download latest version of flashable Magisk (if you were using it), and the latest version of the debloater tool from this thread.
3. Boot into TWRP recovery (using the Vol- + Power key combo or the OEM menu). Hit Install and locate the flashable recovery image you downloaded in step 1. Flash it.
4. Without rebooting, now flash the debloater tool and, after that, Magisk's flashable zip.
5. Reboot your device, and once it boots up, let it finish upgrading Android (you'll see a notification in your lockscreen). Once it finishes, if you installed Magisk previously, reboot into TWRP recovery like in step 3.
6. If you installed Magisk previously, hit Install and locate the Magisk flashable zip once again. Flash it. Reboot your device and profit!
I hope it's clear for everyone how to correctly upgrade a "debloated" device with the steps above
After applying the patch, it is impossible to call the number 112, the phone restarts.
New Version
Hi,
I got an update TOS163B yesterday. Is there a chance to debloat a device with TOS163B installed already?
muebau
Hi,
I got an update TOS163B yesterday. Is there a chance to debloat a device with TOS163B installed already?
muebau
I can perfectly call 112 here, can't reproduce. Which screen are you trying that on?
Soon™
Using a debloated system. However, in the phone app Caller ID does not work: I don't see names for incoming calls or outgoing calls. Is this a setting I'm missing or is something else going on?
Yay!
That did the trick.
Another one: I can't find the 'Current keyboard' setting to quickly change between third party keyboards. It's just not there. I've been in contact with Wileyfox customer support about this. I wanted to send them a screenshot, but there is no option for this either. They pointed me to the 'Buttons' menu under device... but that's not there either...
Any suggestions on both 'Current keyboard' and 'Buttons'? I'm running TOS163B-N2G47H
Last edited:
That is where I looked, but 'Current keyboard' is no there. Just 'Virtual keyboard' and 'Physical keyboard'
.
Last edited:
It's not there. Just a list of the different keyboards and a 'Manage keyboards' option. With that I can toggle different keyboards on and off, but there is no option to change the current keyboard.
I would love to post some screenshots, but I can't find option either...
Maybe you mean the bottom right keyboard symbol in the navbar that appears when the keyboard is used? Not sure what your looking for.
Capture screen shots by simultaneously pressing the power and volume down button for a second.
Attachments
OK. You just solved all of my problems. Apparently with N the current keyboard setting moved. Screenshot worked as well. Apologies for being off-topic in this thread.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone