Hey all!
As you all know, Wileyfox has started rolling out Nougat for their devices, starting with the codenamed marmite family (Swift 2, 2 Plus and 2X models). With this new update, Wileyfox has also included a bunch of BLOATWARE I personally NEVER expected from them. I mean, I didn't request ads in my launcher, and why do I need to forcefully use Truecaller dialer instead of the cleaner, AOSP-based one? That's why I've created this Wileyfox Debloater tool, to keep the system apps as clean and stockish as possible.
App removals included:
- AndroidPay
- BasicDreams
- BookmarkProvider
- Google Books
- Chrome
- CMFileManager
- Drive
- Duo
- Gmail
- GooglePrintRecommendationService
- GoogleTTS
- Hangouts
- Keep
- Maps
- Google Music
- News and Weather
- PhotoTable
- talkback
- Google Videos
- WFChromeCustomization
- Youtube
- Contacts
- FoxHole
- Mms
- SnapdragonGallery
- TrueCaller
- All bundled-apps from /system/vendor/bundled-app
- Possibly more in the future.
(Note: All the moved Google Apps were removed for the sole reason that they can also be downloaded from the Play Store.)
App additons / other features included:
- Google Contacts, in replacement of the half-dummy, prebundled Contacts app (which was missing link with the Dialer).
- Google Dialer, in replacement of TrueCaller.
- Google Messages, in replacement of Wileyfox Mms app.
- AOSP's Launcher3, in replacement of FoxHole (Wileyfox's Launcher).
- Framework and permission files for Google Dialer to work.
- Small tweaks in the build.prop, including drop of min processors to work from 2 to 1, and rise of maximum processors to work from 4 to 8, as well as increasing the Android compiler default amount of processors from 4 to 6.
- Possibly more in the future, too.
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
(To learn how to properly upgrade your device, kindly check post [URL="https://forum.xda-developers.com/swift-2/development/debloat-wileyfox-debloater-quickly-t3587536/post72258926#post72258926"]#25[/URL])
2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Downloads:
- For the latest Wileyfox Swift 2, Swift 2 Plus and Swift 2X firmware: Wileyfox-TOS118C-Debloater--11-05-17.zip
(For version TOS089 check Wileyfox-TOS089-Debloater--10-04-17.zip)
- For more Wileyfox devices, coming soon
Installation instructions:
1. Update your device to Nougat
2. Unlock your bootloader and flash TWRP
3. Download the latest version zip
4. Boot into TWRP, make a backup if you wish (although is highly recommended), choose Install and locate and flash the ZIP.
5. Reboot and enjoy!
6. Are you missing missed calls notifications? Is the caller ID always showed as a number instead of a contact name during phone calls? Check post #16!
Uninstall instructions:
Check post #6
Enjoy, and don't forget to leave a Thanks if you loved it!
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
rivierakid said:
I'm also dissapointed that the OS is far from the pure AOSP.
But it is possible to tweak it without losing the future OTAs:
1. Install google launcher, google messenger
2. Install google phone from apk mirror - this version is working on my phone - http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
3. Deactivate truecaller, duo, news, ... - but be careful, some apps are needed for the system and remember to activate all apps before the OTA update...
Click to expand...
Click to collapse
That is also a possibility but:
1. Launcher3 conflicts with the already installed launcher, so it's impossible to get that out of the way
2. I got latest version working here using the required libraries (extracted from a Pixel), so yeah, probably both possibilities are just fine
And for the third one, just wanted to say there's no need to reactivate them (if you manage to deactivate them, ofc), and, all of the packages the script moves are stored in a safe place (/system/__bloat), so they can be restored from there
I don't remember if I had a problem with a previous OTA update for Wileyfox, but I was not able to install an update without reactivation a disabled app.
I'm not sure...
You could select a default launcher and the phone has really enough RAM, so I think it is not necessary to remove the FoxHole from the system.
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
The final solution for this is LineageOS, if they provide the source
Excellent! Thanks for providing this...such a stupid shame that Wileyfox decided to do this. I'm just hoping that they now release their sources so that we can start working on a proper release of Lineage!
*Edit: Nice! https://bitbucket.org/wileyfox/kernel-wileyfox-msm8937/commits/all*
JT
rivierakid said:
But anyway, nice work! You could provide an uninstall instructions - if it is really possible. I hope that there can be an OTA update in the future...
Click to expand...
Click to collapse
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Hello,
thanks for your effort to the community.
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
linuxct said:
Of course. The debloater doesn't delete any of your system apps, but move them to /system/__bloat. There you'll find 3 folders, the app, the priv-app and the vendor one, just cut and paste them back to /system and the deleted apps will come back. Also, don't forget to remove the framework files and permissions the debloater installs, such as /system/framework/com.google.android.dialer.support.jar and /system/etc/permissions/com.google.android.dialer.support.xml. You can also remove the the GoogleContacts, GoogleDialer, GoogleMessages and Launcher3 folders from /system/priv-app, and revert the build.prop tweaks (lines 164 and 165, change values from 1 and 8 to 2 and 4, line 196, change value from 6 to 4).
Reverting all of that, your system will go back as it came with the Nougat OTA.
Click to expand...
Click to collapse
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
MCPoppa said:
I have a question.
How do I install this? I've tried it with twrp but everytime I install twrp my device won't boot.
To repair this I flashed the newest "system.img".
But I can't replace my stock recovery.
Click to expand...
Click to collapse
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
jdtanner said:
Any chance of updating debloater to change the UI colour scheme from orange back to blue?
JT
Click to expand...
Click to collapse
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
linuxct said:
Try downloading version 3.0.2-0 from TWRP download website, and flash it via the command
Code:
fastboot flash recovery <name-of-the-file>.IMG
Replacing name of the file for the actual filename of it. To enter fastboot mode, you should see a warning when you boot up your device. Hit any volume keys, and, using them, choose the fastboot mode and select it with the power key. Now you should be able to use the fastboot commands.
I'm already working on it... But it'll surely require substratum, which probably won't work out of the box just by flashing it from the recovery. I'm looking for solutions
Click to expand...
Click to collapse
Everytime i installed twrp i got stuck in a bootloop :/
MCPoppa said:
Everytime i installed twrp i got stuck in a bootloop :/
Click to expand...
Click to collapse
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
linuxct said:
Okay, can you try doing "fastboot boot" and the name of the image instead of flashing it? It will avoid bootloops, since it just boots to the image. Keep me posted, please.
Click to expand...
Click to collapse
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
MCPoppa said:
Still doesnt let me boot up after I installed your debloat zip.
Everytime I install or boot to twrp 3.1.0 or 3.0.2 for marmite i get a boot loop and a "dm-verity .." screen.
I've tried different versions of twrp and different methods like "fastboot flash" and "fastboot boot" but everytime I flash something it gets stuck on booting up.
When I was on Marshmello I had this "dm-verity" message too but I could modify my system as I wanted and it booted up everytime, i had TWRP, your Speakermod, Magisk Mask etc installed no problem.
I think it has something todo with the update to Nougat.
How did you bring it run on your device?
Click to expand...
Click to collapse
I explained it last night here, but I also stated it in the OP:
linuxct said:
Warning:
Code:
Your device's system partition [B]IS NOW [COLOR="Red"]TAMPERED[/COLOR][/B]. This implies two things:
1. You WILL NOT BE ABLE TO INSTALL ANY NEWER OTAs ON IT.
[B]2. Your device MAY NOT BE ABLE TO BOOT UNLESS YOU DISABLE DM-VERITY.[/B]
(And to do so, the quickest way is to [B]install[/B] [B][URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk[/URL][/B].)
Click to expand...
Click to collapse
linuxct said:
I explained it last night here, but I also stated it in the OP:
Click to expand...
Click to collapse
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
MCPoppa said:
Thanks, i've installed magisk mask again and the message didn't appeared.
I've also flashed your debloater and everything works fine.
Can I now flash TWRP or do I have to boot it up via fastboot everytime?
Click to expand...
Click to collapse
Try flashing it to your recovery partition, my guess is that now that DM-verity is disabled everything should work fine
Cheers!
Quick update post after two days of usage, yesterday I noticed I didn't receive any notifications on missed calls, and that the caller ID always showed as a number although I had it added as a contact.
I realised that I didn't have any "Phone" app chosen as default in Android settings, so I was missing those notifications until I opened the Google Dialer app.
In case it happens to you, to sort it out go into Settings > Apps, then hit the gear in the top right corner and make sure you've a config similar to this one (Launcher3, Google's "Phone" and Google's "Messages" chosen as default Home, Phone and Messaging apps).
I hope this is clear for everyone, since it's not something I can fix on my side/requires the user to do the change
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Ianharding said:
I have TWRP, SuperSU, and Magisk. Marshmallow boots with no problem, but I get the dm-verity screen on boot with the message "dm-verity is not started in enforcing mode".
Does this mean dm-verity is disabled because it is not enforcing, or do I need to do something to stop the whole dm-verity screen appearing before I can successfully upgrade, debloater, and boot Nougat?
Click to expand...
Click to collapse
Firsts 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
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
digidude512 said:
If I use this to debloat my WileyFox does it mean I won't be able to use Android Pay?
Click to expand...
Click to collapse
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?
Related
Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5
version 2 out now~~~
After researching the framework info, I found out MEA G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=11050483647474827606
(version 2, replaced google apps, more debloat, more stable system)
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
3.4 install keyboard
https://androidfilehost.com/?fid=818070582850495399
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
Where is the build.prop file?
amakuramio said:
currently uploading! done in few hrs
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download ANY G8141 or G8142 ROM that is 179 version, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get force close
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. recover my system backup using twrp, for g8142 you have to follow step 4
uploading currently, isdone within 15 mins
to recover, simply make a backup of anything, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files 2, 3, 4, xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Blackghosthm said:
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Click to expand...
Click to collapse
on wifi I get 8 hrs to 8.30
on 4g, drains very fast
but newer versions are faster (after march, sony use 8.1 compiler for faster apps)
its 89% upload
its also possible that I combine system from 179 with turbo rom 75, it should be compatible and easy to do.
jianlin3062 said:
Where is the build.prop file?
Click to expand...
Click to collapse
the build.prop file is in ''root/system/build.prop'' I use notepad++ to edit it on pc then push it back to the phone
twrp file manager, copy build.prop to sd card, copy to pc, replace maple with maple_dsds and g8141 with g8142, its easy to do
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
saved-j said:
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
Click to expand...
Click to collapse
you did something completely wrong
backup your data (if you want, prefer clean) flash a 179 stock firmware erase all otherwise force close, then restore my system, then flash the 4 zips, reboot after the first one, then flash last 3 zips I posted in the link up there, then xposed, then reboot
I really have 0 problems here. I thought I kept swiftboard in it? hmm. I will make a patch zip with keyboard in it, hopefully it helps. you can also push a keyboard app in system/app/Appname/app.apk 0644 permission
https://www.apkmirror.com/apk/swift...swiftkey-beta-7-0-8-363-android-apk-download/
can you do me a favor? make a screenshot of the system app scroll down, then send me. Maybe I uploaded wrong system?
do you can xposed patch on turbo final v2 rom?
it stucked.
amakuramio said:
you did something completely wrong
Click to expand...
Click to collapse
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Also am gonna try:
-AndroPlusKernel 12 -
-Magisk 16.4 (instead of 16.0) -
-OpenGapps (instead of included) -
-Magisk-Systemless-Xposed (instead of flashing /system included) - works either way
saved-j said:
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Click to expand...
Click to collapse
pushing a keyboard into the system will also help, but that is the way to do it, yes
do you have g8141 or g8142? google play issue is related to not updating proper build prop to your device
amakuramio said:
g8142
Click to expand...
Click to collapse
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
lGIKDk said:
do you can xposed patch on turbo rom?
Click to expand...
Click to collapse
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
saved-j said:
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
Click to expand...
Click to collapse
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
https://www.apkmirror.com/apk/googl...2-8-66-090400-200774163-android-apk-download/
GmsCore.apk with permission 0644
same with phonesky
https://www.apkmirror.com/apk/googl...6-08-all-0-pr-200628961-android-apk-download/
then reboot with dalvik and cache removed (2 things only) there may be LIB compatibility issues.
Hell if google play doesnt work for g8142, I can also do nanomod! which is very light on the battery
nanomod needs xposed, but it works with xposed, so
amakuramio said:
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
Click to expand...
Click to collapse
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
amakuramio said:
Hell if google play doesnt work for g8142
Click to expand...
Click to collapse
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC too. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
*trying one more time while you're thinking*
saved-j said:
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
Click to expand...
Click to collapse
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
1. in xposed install http://repo.xposed.info/module/com.thermatk.android.xf.fakegapps (do this first, just enable it, dont reboot in recovery yet)
2.delete the following
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/GoogleAnalyticsProxy/GoogleAnalyticsProxy.apk
/system/app/GoogleExtShared/GoogleExtShared.apk
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
/system/priv-app/GmsCore/GmsCore.apk
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
/system/priv-app/GoogleExtServices/GoogleExtServices.apk
/system/priv-app/GoogleFeedback/GoogleFeedback.apk
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
/system/priv-app/Phonesky/Phonesky.apk
3. then flash nanodroid https://downloads.nanolx.org/NanoDroid/Stable/ then reboot. you might want to go options of google play then clear data afterwards.
(4. extra, see if settings folder in app is same permission as other folders, and if apk inside is also same as other apk in the different folders)
cant google login. it just black screen
amakuramio said:
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
Click to expand...
Click to collapse
The difference between them is minimal. Somehow it worked for me with OpenGapps. I'll set the phone up and leave it as it is, as it's 4:00 am already. I'm glad it worked somehow.
I'll test it during the week, though i've already found several issues, like, in Album app it doesn't allow to move from the internal memory to the folders on the SD card already existing (don't know why?? - Google Photos app does it with no problem)
lGIKDk said:
cant google login. it just black screen
Click to expand...
Click to collapse
Did you read the conversation here before posting your message? You're not alone in this problem.
Try flashing .179 again, with all the wipes, etc - following the instruction.
And flash Open Gapps right before you boot up in the system. It has JUST worked for me when I tried it in the last time, though it hadn't worked for me yesterday!
Active Screen, XZ2 Camera and some other XZ2 features, Xposed, WiFi, data, everything works just fine.
Had to spend two nights to achieve it, though.
Attaching a video of working Xposed. My device recognizes as Pixel XL because I have a Daydream Enabling magisk module.
amakuramio said:
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
Click to expand...
Click to collapse
ok. i wait.
i hope completly version
amakuramio said:
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=674106145207498283
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Blackghosthm said:
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Click to expand...
Click to collapse
though the rom is made by sony I got it from MEA version from XPERIFIRM and modified by me I did include HIS xposed fix (not directly).
What I did copy was the framework intents those are the same as his. If I modified framework myself and installed his xposed then because of mismatch the whole thing would crash so I had to force the same intents to match the signature.
UPDATE 06 OCT 2019: I will be returning to the project next week...
Apologies for my long silence over the past few months. After the initial release of this ROM I started focusing on getting the fingerprint sensor to work, which after some struggle I got it working. I then began spending time on removing non-FLOSS apps, services and providers that comes with lineageOS and replacing them with even better FLOSS alternatives. I made some good progress on this and created an automated build script for this. I also wanted to make the installation of the ROM easier, so I even created a script that automates the entire flashing procedure for you....yip...it's pretty cool On the security side I also made some good progress: I've applied several recommended hardening patches to the base system, and also patched the flawed mac-address randomization implementation that still exists in android today.
As I got close to preparing for release, google decided to stop support for maps-api V1 which is used by migrog. This completely broke all map views in apps and even started crashing the mobile browser. Because of the complexity of the android build workflow and tool-chain, I initially thought I screwed something up, but it was only after a couple of days of pulling my hair out people started reporting it on github. I had to wait for the mapbox implementation of microg to be released, and it eventually came a few weeks later.
It was shortly after the release that my personal priorities changed. I've been occupied (visa related) with that ever since but I'm happy to report that I should be able to return back to the project next week. Obviously some time has passed, so I will have to get up to speed with the latest releases of all of the repos and get that merged with my local changes, but that should only take a day. Hopefully there won't be many breaking changes, and if that is the case then I should be in a position to release V2 in about two weeks!
Cheers,
fanix (git-repo here: https://github.com/FaN11X?tab=repositories). Once you see commits you'll know I've started.
New build is available apparently.... don't know if it's the same dev..
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
I've contacted one of the mods and asked if thye could post the link. Hope they do, otherwise if someone has the ability to post links then message me and i'll PM you the download link which you can then share to the thread.
Cheers
fanix
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
mateHD said:
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
Click to expand...
Click to collapse
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
fanix-uk said:
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
Click to expand...
Click to collapse
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Is possible to have the miui camera with this rom?
mateHD said:
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Click to expand...
Click to collapse
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
perillo95 said:
Is possible to have the miui camera with this rom?
Click to expand...
Click to collapse
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
fanix-uk said:
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
Click to expand...
Click to collapse
Looking forward to it. I will probably try the current version as soon as I'm allowed to unlock my bootloader.
fanix-uk said:
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
Click to expand...
Click to collapse
With miui camera and the in-display fingerprint would be a perfect ROM, Great work
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
eerastov said:
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
Click to expand...
Click to collapse
Yes.
Whats up with the new version? Can i help somehow?
Thanks
Hi Fanix
I really appreciate what you have done for Mi8 Pro. If you did not share your work here, I think I nearly sell my phone, as the MIUI is pretty trash.
Also, thanks for your progress on adding in-display finger sensor, after you done it I feel you can create one link for donation. I really hope you can keep develop on this phone and make LOS Andorid Q available in the future.
Kind regards
One of Mi8 Pro users
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
I flashed this rom on my phone, it works really well. And I flashed a Gapps on my phone, work well as well. I did not flash the Nanadroid on my phone, is it necessary? I just worry about it becasue you said something related to SafetyNet, ahaha. I do not know if I do not have it, is my phone still safe?
Thanks a lot again.
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
hello I have tried treble version but i got MusicFX Force Close i hope you can fix this
and maybe you can port Miui Camera on this ROM thanks for your work
I found a bug :
NFC is not found in Settings and NFC Icon on status bar is error
Edit :
sometimes when opening the camera, freeze and got pop-up cannot be connected to the camera
And for musicFX is working...
Thanks
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
Current anything is good !
thanks a lot again
Any news plss
Any news?
Still others are maintaining this rom, looking forward to updating
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
bgcngm said:
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
Click to expand...
Click to collapse
Would love to be in a position to do that. However, I have just had my OnePlus 6T stolen, and now need my Mi 8 Pro as a daily driver. Would be happy to donate to get the fingerprint reader working on AOSP / GSI-Treble ROMs for the MI 8 Pro.
PART 1 of 3
Had trouble posting this in XDA, got flagged by the system so the guide is broken into 3 parts.
Attachments are in part 3.
This guide is as detailed as possible so that you won't make the same mistakes I did and won't face the same problems.
Thanks to @xd4d3v and @conbak49 for your help buddies.
[TEXT IN BLUE ARE SPECIFIC TO LG V30]
THIS IS A MUCH SAFER AND EASIER WAY TO DE-GOOGLE / DE-BLOAT ANY ANDROID ROM AND IS WRITTEN SPECIALLY FOR THE LG V30, MIGHT WORK FOR ALL PHONES
AS OF POSTING THIS, I AM ON H930DS OREO ROM BUT THIS PROCESS MIGHT BE APPLICABLE FOR ANY ANDROID ROM, ANY VERSION
YOU NEED TWRP FOR THIS TO WORK. FOR ROOTING AND TWRP PLUS MAGISK RELATED PROCESS, REFER TO OTHER GUIDES ON THE V30/SPECIFIC PHONE XDA THREAD
Preparation
CHECK THAT YOU HAVE DOWNLOADED THE FOLLOWING APPS IN A FOLDER IN YOUR PC/LAPTOP)
(side note : the folder is in your pc because sometimes the phone's internal storage is encrypted and it is best to wipe all user data. We will copy this folder to internal storage after a clean install/factory reset)
A. TITANIUM BACKUP (download v8.3.3 or above from apkmirror.com)
B. Magisk 19+zip
(NOTE: if you followed @TxanMoe and @ChazzMatt 's WTF bootloader exploit for rooting the lg v30, be aware that the magisk.zip in that post is v18, you need magisk v19 for this process, but it is okay as long as you download magisk v19 from from "https://magisk.download/" website AND put it in the folder.
[ FOR THE V30, YOU NEED THESE EXTRA FILES IN THE FOLDER:
C. Encryption Disabler(Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip OR no-verity-opt-encrypt - 6.0_1_.zip(OREO) )
D. LG ROOT CHECKER Disabler(AK3_RCTD_REMOVER.zip OR lg-rctd-disabler-1.0._1.zip(OREO) )
I am on oreo so I have the ones with red OREO, the first .zips are the latest and are probably for pie and oreo both ]
DISCLAIMER:
Although we are completely removing google apps pre-bundled in the stock rom; at the end of this process, you will have a fully functioning Aurora Store . It is the same Play Store side by side without any google trackers, and is from the open source MicroG project, so relax, you will be able to download all apps(Anonymously) including paid apps(with your login) just like you downloaded apps from the play store.
BEFORE WE BEGIN
TWRP will sometimes give a error message in red saying 'unable to mount storage/system'... This often happens if you were previously working on a different storage(OTG/SD card) and TWRP fails to switch storage. If it happens :
Go to MOUNT>STORAGE>SELECT STORAGE MEDIA>INTERNAL MEMORY and try again...it will get fixed.
WARNING:
NEVER EVER START REMOVING SYSTEM APPS WITHOUT BOOTING THE ROM/SYSTEM FOR THE FIRST TIME. SYSTEM WILL CRASH AND A BOOTLOOP WILL BE JUST AROUND THE CORNER.
STEP 1: VERY VERY VERY IMPORTANT
REMOVE YOUR GOOGLE ACCOUNT AND PHONE'S SCREEN LOCK PASSWORDS FROM SETTINGS>ACCOUNTS
DOUBLE CHECK that any google account is removed from settings.
DOUBLE CHECK that ALL FINGERPRINTS/PIN/PASSWORD LOCK METHODS HAVE BEEN REMOVED OR CANCELLED
IF YOU DON'T REMOVE YOUR GOOGLE ACCOUNT, SETUP WON'T COMPLETE WITHOUT GOOGLE APPS. YOU WILL GET ENCRYPTION ERROR AND MANY OTHER PROBLEMS (I learned it the hard way)
REBOOT [IMPORTANT]
STEP 2: IF POSSIBLE HAVE A TWRP FLASHABLE ZIP OF YOUR ROM READY IN THE PC FOLDER
if you don't have a twrp flashable zip for your system, it's ok. It's just a fail-safe method.
(Note: FOR the lgV30 you can download flashable rom zip from https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193 (at the very last of that post under UPDATE H930, US998, H930DS with latest stock firmware TWRP-flashable "ROMs" )
2.1 IF YOU HAVE A USB OTG/SD CARD
COPY THE FOLDER FROM PC TO USB OTG/SD CARD
STEP 3: back up your files from internal storage
It's getting WIPED/FORMATTED. Back up.
PART 2
STEP 4: TWRP AND FULL SYSTEM FORMAT
Disclaimer
We are going to format/factory reset your phone and delete all your data.
4.1 FROM TWRP
(Note: if you have magisk installed, to boot into TWRP simply go to 'Modules' in left plane of Magisk and in right pane inside 'Modules' there is option to 'reboot into recovery')
[ FOR THE LG V30, another method to boot into TWRP via volume down+power button is here: https://www.youtube.com/watch?v=VJF8oTGqohg
HARDWARE KEYS TO BOOT INTO TWRP:
> continue holding volume down and power button (10 sec)
>continue holding for the bootloader warning too
>as soon as LGV30 white logo appears on black background immediately unpress and repress the power button and
>continue holding both buttons
>a screen comes saying all your files will be deleted, press volume down button to YES, then press power button
>the same screen reappears again, press volume down button twice to YES, then press power button
>wait, phone reboots
>the same screen giving warning comes again
>Don't press any buttons
>After a while TWRP starts
4.1.A. PERFORM A FULL FACTORY RESET
In TWRP,
go to WIPE
SELECT ADVANCED WIPE
SELECT: DALVIK / ART CACHE
DATA
INTERNAL STORAGE
CACHE
(NOTE: don't wipe SYSTEM if you don't have flashable rom zip, there won't be any system to boot into)
(NOTE: after factory reset, Magsik must be re-flashed from TWRP, there will be Magisk icon in a firmware with previously Magisk installed, but it won't work)
(NOTE: many android roms now require a encryption disabler, make sure you have that in a flashble zip file for your rom)
SWIPE TO PERFORM ADVANCED WIPE, DON'T REBOOT.
THERE IS NOTHING IN INTERNAL MEMORY NOW
4.1.B FROM SD CARD/OTG
FLASH MAGISK 19+ ZIP
FLASH ENCRYPTION DISABLER ZIP
FLASH LG ROOT CHECK DISABLER ZIP
4.1.C IF YOU DONT HAVE SD CARD/USB OTG
follow STEP 5(not 5.1), after system starts connect phone to PC. copy the folder from PC to phone's internal memory.
COMPLETE STEP 4.1.B
While still in TWRP, go to WIPE and perform the default TWRP wipe then follow step 5 and 5.1 .
Remember this time you are not wiping your internal storage so 4.1.C users need not follow step 6. The copied folder is still there.
STEP 5: LET THE SYSTEM BOOT NORMALLY, DON'T CONNECT TO INTERNET
5.1 After booting up your system, configure settings to your like, manage display size, change your wallpapers etc.. to your liking.
THIS IS THE BASE SYSTEM WHICH WE WILL TAKE A BACKUP OF and which YOU WILL BE CONSTANTLY RESTORING VIA TWRP SHOULD ANYTHING GO WRONG.
5.2 ONLY FOR LG PHONES
LG Apps like HIFI Recorder and Smartdoctor have a Terms of use Screen before using that app for the first time. Removing google apps makes the terms of use app crash and consequently app like HIFI Recorder refuse to start. This is possible to bypass by the following method:
After step 5, open all Lg apps that you want to use like Hifi Recorder, Lg health etc and accept the terms and conditions. Once that is done; you can even remove those EULA app, Terms and conditions app...
I believe this is due to the lack of webview which gets removed along with 'Android System Webview'.
However, by the end of this post we will have a fully working, trackers and AD free Bromite webview.
STEP 6: MAKE SURE EVERYTHING IS FINE, COPY THE FOLDER FROM PC TO INTERNAL MEMORY/SD CARD/USB OTG AND REBOOT PHONE
STEP 7: BACKING UP YOUR SYSTEM IMAGE IN TWRP
After rebooting, reboot into TWRP via Magisk.
WHEN YOU START DELETING SYSTEM APPS, SYSTEM MIGHT NOT BOOT, GET STUCK IN A BOOT LOOP, HANG INFINITELY ETC. , IT TOOK ME 15+ SYSTEM RE-INSTALLS TO GET A WORKING LIST OF REMOVABLE APPS WITHOUT GETTING CAUGHT IN A BOOT LOOP.
RE-INSTALLING SYSTEM FROM A FLASHABLE ZIP IF ANYTHING GOES WRONG IS A LENGTHY, TEDIOUS PROCESS AND YOU WILL HAVE TO REPEAT EVERYTHING DONE TILL NOW.
TO MAKE RE-INSTALLING SYSTEM EASIER FOR YOU, YOU ARE GOING TO TAKE A COMPLETE SYSTEM IMAGE FROM A CLEAN INSTALL, THIS PROCESS IS IMPORTANT
In TWRP , go into BACKUP
Excluding 'SYSTEM IMAGE' back up everything to internal storage/SD, it only takes up a few minutes.
YOU NOW HAVE A COMPLETE MIRROR IMAGE OF YOUR SYSTEM. IF ANYTHING GOES WRONG AFTER REMOVING ANY APP, IT LITERALLY TAKES ONLY 2 MINUTES TO GET YOUR SYSTEM UP AND RUNNING FROM THE BACKUP.
STEP 8: REBOOT
STEP 9: INSTALL TITANIUM BACKUP,ALLOW ROOT ACCESS
STEP 10: FIND A LIST OF UN-INSTALLABLE GOOGLE APPS.
Personally, I think the easiest way is to download a FULLgapps package from 'opengapps.org' for your android version, extract it and find a file titled ' remove-gapps.txt ' . This gives you a basic idea of which packages are from google and which are not.
As a rule of thumb, packages with name like com.google.NSA_spyware are from google and packages with brand/vendor names like (here LG ELECTRONICS/lge) com.lge.hippityhoppityLGproperty are from your phone brand. Packages with name like com.android.teagoodcoffebad are core shared android apps, don't delete these.
Code:
UPDATE: DON'T USE THIS \ CAUSES BOOTLOOP thanks @cascabel for checking
HOWEVER, YOU CAN USE THIS FOR FINDING OUT GOOGLE PACAKGES YOU ARE UNSURE OF
[COLOR="Sienna"]There is this zip file specially made for removing gapps:
' [url]https://github.com/CHEF-KOCH/Remove-Gapps/releases[/url] '
but I didn't use that and it doesn't remove 'Android System Webview'
so it's upto you to find a list of removeable apps from your system.[/COLOR]
NOTE: nanoDroid/microG is a collection of open source softwares that combine the functionality of google services in a open source package. It is said that the nanoDroid installer automatically removes google packages during install. We will be installing nanoDroid later.
However, nanoDroid installer didn't remove google apps from the LG V30 OREO.
IF YOU SIMPLY WANT TO REMOVE SYSTEM AND GOOGLE APPS ON A HIT AND TRIAL BASIS, IT'S OK TOO AND THAT'S WHAT I DID BECAUSE WE HAVE A FULL SYSTEM BACKUP AND WE CAN RESTORE EVERYTHING EASILY IN 2 MINUTES.
STEP 10: IN TITANIUM BACKUP:
-----------------------------------------------
THIS PROCESS IS FOR BATCH REMOVING APPS THAT YOU ARE SURE ARE BLOATWARE\GOOGLE APPS like DRIVE,DUO,GMAIL etc
At the top right corner there are three icons: a search icon, a file with tick mark, and menu: Select the middle one.
This opens the 'Batch actions -ALL'
Swipe down to 'Un-install'
In Un-install, the last option is : 'Un-install all all user & system apps'
Select that, don't worry it just opens a page with all your apps.
Note the green tick mark at the top right corner.
Deselect all and select only the ones that you want to remove.
-----------------------------------------------
NOTE: YOU WILL FIND A LOT OF APPS WITH NAME ENDING IN OVERLAY like com.android.phone.overlay corresponding to an app com.android.phone.
They are very very small sized files and not full apps. I don't know if it is okay to leave them but by far there has been no problems leaving them alone.
Also if you remove the main app then TITANIUM BACKUP will show an error while trying to remove the overlay. JUST LEAVE OVERLAYS ALONE or REMOVE OVERLAYS BEFORE REMOVING THE MAIN CORRESPONDING APP.
-----------------------------------------------
DELETING APPS ONE-BY-ONE
ALSO: HOW TO KNOW A PACKAGE NAME IN ANDROID:
To know a package name like com.google.calculatorprebuilt from an app titled calculator so that you can be sure where the package is coming from (google/vendor/AOSP android), open TITANIUM BACKUP and in the first screen there is overview BACKUP/RESTORE Schedules; SELECT BACKUP/RESTORE and click any app. On the new window, select the button with YELLOW TEXT and find Package name.
If you are sure to remove this app, on this new window there is a option in RED titled UN-INSTALL!. Hit OK twice and uninstall the app.
Update: IN THE LG V30 removing 'Android Services Library 1' and 'Android Shared Library 1' causes bootloop and their name start with com.google.package....
-----------------------------------------------
STEP 12: AFTER REMOVING A FEW APPS RESTART YOUR SYSTEM
NOTE THE PACKAGES YOU HAVE REMOVED.
Often times, many apps inter-rely on each other and removing one app may cause other to crash.
IF THE SYSTEM BOOTS UP, FINE. CONTINUE REMOVING SYSTEM APPS.
STEP 13: BOOTLOOP AFTER REMOVING SYSTEM APPS/
SYSTEM REFUSES TO BOOT AFTER REMOVING GOOGLE APPS/
SYSTEM STUCK ON LG LOGO
This usually happens when you remove a core system app and the system fails to boot.
FOR A CONDITION LIKE THIS IS WHY WE TOOK A WHOLE SYSTEM BACKUP IN TWRP BEFORE (also called nAndroid Backup)
NO PROBLEM, FOLLOW STEP 14
STEP 14: RESTORING SYSTEM FROM A BOOTLOOP
1. BOOT INTO TWRP
2. GO TO RESTORE
3. RESTORE SYSTEM
4. DONE
PART 3/FINAL PART
STEP 15: TRY REMOVING APPS AGAIN FOLLOWING THE SAME PREVIOUS STEPS BUT CAREFULLY
STEP 16: INSTALLING microG services via NanoDroid
1. Download two zips from https://downloads.nanolx.org/NanoDroid/Stable/
First download NanoDroid-patcher-.zip
Secondly download NanoDroid-microG-.zip
2. COPY zips TO PHONE
3. IN TWRP, first flash the patcher then microG zip.
Note that the patcher takes a very long time.
4. In advanced wipe clear cache only in TWRP.
REBOOT
YOU NOW HAVE A PLAY STORE EQUIVALENT AURORA STORE AND OTHER CORE GOOGLE SERVICES IN OPEN SOURCE APPS.
PLEASE NOTE:
MOST OF YOUR APPS HAVE LOST THEIR PERMISSIONS NOW SO OPEN ALL APPS FROM LAUNCHER AND GIVE THEM PERMISSIONS. IT'S EASY. EVEN FILE MANAGER WILL ASK FOR PERMISSIONS. THIS IS DUE TO THE PATCHER PATCHING SOME SYSTEM FILES
STEP 17: INSTALLING WEBVIEW
Once Everything is done you will notice that some apps dependent on AndroidSystemWebview.apk will crash or not display properly. An example of this is the popular 'English' dictionary that can be downloaded from the play store. Instead of proprietary Webview we will now install open source webview.
IN MAGISK (Needs Internet)
1. Install Bromite Systemless Webview module(module itself needs internet and takes some time)
2. Install Xposed Framework [ UPDATE: THIS MODULE IS BROKEN AS OF NOW, DOWNLOAD XPOSED APK FROM ELSEWHERE]
IN XPOSED FRAMEWORK
1.INSTALL AnyWebView module
REBOOT
GO TO SYSTEM>Developer options
Under webview implementation option select Bromite Webview
STEP 17: AFTER REMOVING ALL APPS THAT YOU DON'T WANT, TAKE A BACKUP OF THIS BLOATWARE FREE SYSTEM IN TWRP AGAIN.
THAT WAY YOU DON'T HAVE TO GO THROUGH THESE SAME STEPS AGAIN IF YOU NEED TO FACTORY RESET YOUR DEVICE AGAIN
STEP 18: A LIST OF SAFE TO REMOVE APPS IN THE LG V30 OREO ROM
By now I am too tired to type all the apps so I just took a screenshot of all the apps I now have after installing nanoDroid and Bromite.
So you can safely remove all other apps that ARE NOT in these screenshots.
SCREENSHOTS IN ATTACHED ZIP.
Launcher: Nova Launcher
Icon Pack : Pixel Pie Icon Pack
Any Queries WELCOME.
Suggestions on other removable apps from the list HIGHLY WELCOME.
Been looking for a thread like this. Awesome!
Just a quick Q or two...
1. I might just use the zip and remove webview manually. Would that be okay? And should i uninstall libs too (g-killer has that option)?
2. I see you used nano microg - would it be fine to use the full nanodroid installer? There are some apps there that are handy afterr you have de-googled.
Again, thanks for the thread. Been trying to go microg on stock for a while now withoutuch luck (full of fc's).
Will try this asap.
cascabel said:
1. I might just use the zip and remove webview manually. Would that be okay? And should i uninstall libs too (g-killer has that option)?
2. I see you used nano microg - would it be fine to use the full nanodroid installer? There are some apps there that are handy afterr you have de-googled.
Again, thanks for the thread. Been trying to go microg on stock for a while now withoutuch luck (full of fc's).
Will try this asap.
Click to expand...
Click to collapse
Which zip are you referring to in the first point? If you mean bromite zip and if it is available, I think it would be okay to flash it. You (might) see two webviews in developer settings. I really have no idea regarding libs, I really don't have much idea of core android system but afaik the zip file from PART 2 under
There is this zip file specially made for removing gapps: ' https://github.com/CHEF-KOCH/Remove-Gapps/releases ' but I didn't use that and it doesn't remove 'Android System Webview' so it's upto you to find a list of removeable apps from your system.
Click to expand...
Click to collapse
lists many libs if you extract it and find a file delete.sh in zip>system>system.sh (shell/sh is essentially a .text file). You can try deleting those.
I might even try that zip file and see if it works or you can and update us, remember backing your system! after a fresh install.
I used the full nanoDroid package before and it came with a plethora of apps that scared me. You can download each of those apps from f-droid one by one if you just want a specific app. thanks for asking. good day!
B
tamakooo said:
Which zip are you referring to in the first point? If you mean bromite zip and if it is available, I think it would be okay to flash it. You (might) see two webviews in developer settings. I really have no idea regarding libs, I really don't have much idea of core android system but afaik the zip file from PART 2 under
lists many libs if you extract it and find a file delete.sh in zip>system>system.sh (shell/sh is essentially a .text file). You can try deleting those.
I might even try that zip file and see if it works or you can and update us, remember backing your system! after a fresh install. I think that's he zip you mentioned in your post. Not sure, though (at work and don't have time to check).
I used the full nanoDroid package before and it came with a plethora of apps that scared me. You can download each of those apps from f-droid one by one if you just want a specific app. thanks for asking. good day!
Click to expand...
Click to collapse
Oh. Sorry. My post was unclear.
I meant using g-killer to remove system apps instead of doing it manually (i don't have the time nor patience lol). I was wondering if i should delete libs using g-killer or just let them be and just remove apps. I think that's the gapps remover you linked (not sure. At work and don't have muh time besides checking here every once in a while )
About nanodroid, yeah it dies have a lot of apps. I do use the setup zip so i select which i use. Downloading on f-droid works, too.
Sorry for the questions. I'll try this tonight (maybe in 5-6 hours) and let you know what happens. :good:
Attempt 1: using the gapps uninstaller on you link gave me a bootloop. Gonna try gapps killer this tike without removing any libs.
Attempt 2: gapps killer without deleteing libs gives bootloop, too. Lol. Gonna try again but won't uninstall framework.
Attempt 3: same thing. Will try without deleting ps, play services, and framework.
Attempt 4: ok. So that worked. Still have PS and the others, though. Gonna try patching now and see if the last remnants of Google will disappear.
Ok. So i got it to work without having to clean flash. Gonna try a clean flash now and repeat. Not sure if i got all google apps deleted. Gonna try the zip again (gapps remover). If it works, I'll restore my old twrp backup and do it there. If not, I'll restore my backup and try again tomorrow. Patching takes a while...
Seems using g-apps killer zip or the gapps uninstaller zip you provided causes bootloops.
I'll try again tomorrow...
cascabel said:
Attempt 1: using the gapps uninstaller on you link gave me a bootloop. Gonna try gapps killer this tike without removing any libs.
Attempt 2: gapps killer without deleteing libs gives bootloop, too. Lol. Gonna try again but won't uninstall framework.
Attempt 3: same thing. Will try without deleting ps, play services, and framework.
Attempt 4: ok. So that worked. Still have PS and the others, though. Gonna try patching now and see if the last remnants of Google will disappear.
Ok. So i got it to work without having to clean flash. Gonna try a clean flash now and repeat. Not sure if i got all google apps deleted. Gonna try the zip again (gapps remover). If it works, I'll restore my old twrp backup and do it there. If not, I'll restore my backup and try again tomorrow. Patching takes a while...
Seems using g-apps killer zip or the gapps uninstaller zip you provided causes bootloops.
I'll try again tomorrow...
Click to expand...
Click to collapse
thanks for checking, I updated the post. Also had some other minor updates in the post.
Hey OP, thanks for writing this guide. I'm running Android 12 stock ROM + Magisk root on Zenfone 9 but I've had trouble deleting stuff in /system due to it being read-only. I am able to "freeze" goolag apps in Titanium Backup but can't seem to uninstall them with either TB or in TWRP recovery mode file browser. Seems that everything system related is mounted as read-only. Do you have any ideas on how to proceed with de-googling in such conditions? Regards
Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5EEA 13.0.3Global 13.0.1Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.
Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.
Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!
Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.
thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks
Can i update ota to 13.0.2 after rooted? Just update and root again?
Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2
How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?
thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.
vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img
kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet