Related
Introduction
This ROM is based on lost101's, kingkaminari's and VitaTaf's work you can find here. The main aim of my modifications is putting debloating to the extreme and getting rid of intrusive Google spying services that violate user's privacy. Before you flash this ROM read all the information below and make sure you still want to do it as some stuff you find essential might be missing and irreplaceble. Please also mind you will have to setup your device manually with ADB to unlock all of its functions.
Disclaimer
Even if everything works 100% fine for me I take no responsibility for anything that happens to anyone else's device after flashing my ROM. If you want to try it, do it on your own risk. Always backup your data.
Description
This is Identity Crisis 6 LTE v1.0a by lost101, kingkaminari and VitaTaf with the following modifications:
Version 1.2c
Changes
Version 1.0
1. build.prop
#USB debugging lock bypass
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
It is advised to remove these lines from build.prop after you're done with setup as they compromise your device's security
2. Removed from system/app:
- BasicDreams
- BookmarkProvider
- Calculator
- CalendarGoogle
- com.motorola.android.setting.diag_mdlog
- DeskClockGoogle
- Exchange3Google
- FaceLock
- FMRadioService
- GoogleContactsSyncAdapter
- HoloSpiralWallpaper
- HTMLViewer
- LatinImeGoogle
- LiveWallpapers
- LiveWallpaperPicker
- NoiseField
- PartnerBookmarksProvider
- PhaseBeam
- Piktures
- PrintSpooler
- UserDictionaryProvider
3. Removed from system/etc/permissions:
- com.google.android.maps.xml
- com.google.android.media.effects.xml
- com.google.widevine.software.drm.xml
- com.motorola.camera.xml
- com.motorola.context.xml
- com.motorola.gallery.xml
- com.motorola.software.fmradioservice.xml
- com.motorola.software.storageoptimizer.xml
4. Removed from system/framework:
- com.google.android.maps.jar
- com.google.android.media.effects.jar
- com.google.widevine.software.drm.jar
- com.motorola.android.dropboxhelper.jar
- com.motorola.gallery.jar
5. Removed from system/priv-app:
- AppDirectedSmsProxy
- atfwd
- AudioEffects
- BackupRestoreConfirmation
- CalendarProvider
- CallLogBackup
- CellBroadcastReceiver
- ConfigUpdater
- Contacts
- ContactsProvider
- CQATest
- EmaraPhoneExtensions
- GmsCore
- GoogleBackupTransport
- GoogleFeedback
- GoogleLoginService
- GoogleOneTimeInitializer
- GooglePartnerSetup
- GoogleServicesFramework
- MotCamera
- MotoOneTimeInitializer
- Phonesky
- PreloadContacts
- SetupWizard
- SetupWizardExt
- StorageOptimizer
- WallpapaerCropper
- WapPushSI
6. Removed from system/usr/srec:
- en-US folder and its files
7. Removed from system/vendor:
- pittpatt folder and its files
8. Added to system/apps:
- AnySoftKeyboard
- MiXplorer
Flashing
1. Boot into TWRP
(2. Backup)
3. Format data (Wipe>Format data>yes)
4. Transfer ROM to SD card/Local storage
5. Wipe>Factory reset
6. Install
7. Reboot
Setup (version 1.0 only)
When the installation completes you'll find there's no Setup Wizard, and some important UI components (Home button, Notifications, Quick Settings) are blocked. There's also no access to Developer's Options. Don't worry - they're normally being unlocked after you're done with Setup Wizard but since it's not there you need to do it manually:
1. Open ADB terminal on your computer
2. Connect your device
3. Execute the following commands:
Code:
adb shell
su
settings put global device_provisioned 1
settings put secure user_setup_complete 1
reboot
After reboot your device is ready to use.
Known issues
- Please refer to IDCrisis 6 LTE original thread
Life after Google
You can try using Micro GmsCore to access Play Store content, and here are some alternatives:
1. Interesting and useful apps in F-Droid store:
- Adaway (system-wide ad blocker)
- AFWall+ (very nice firewall. I use it in whitelist mode because it blocks internet access to all apps by default)
- Etar (calendar. Won't work without Google calendar service and account)
- K-9 mail (bit ugly but awesome mail client)
- Open camera (stock camera replacement)
- Wifi automatic (turns wifi off when you lock the screen which saves battery and improves security. Bugged a little and randomly disables wifi from time to time)
- SMSsecure (messaging app with encryption)
- 920 Editor (text editor)
- Document Viewer (self explanatory)
- Network Log (self explanatory)
2. Other interesting and useful apps around the web (mostly on XDA):
- ApkTrack (app updates tracker),
- Calc+ (calculator),
- CoolTool (CPU and RAM usage and other info display),
- DejaOffice (office app that looks a bit outdated, but it's the only calendar app to work without Google services I found so far),
- Disconnect.me (private web searches; the app FC right after starting it, probably due to lack of Google search services available)
- DriveDroid (turns the phone into Linux live USB),
- ES File Explorer (file explorer),
- Firefox (web browser),
- Gravity Screen (Turning screen off and on without using physical power button),
- Greenify (apps hibernator),
- KWGT (custom widget maker),
- LiveBoot (Chainfire's app that replaces boot animation with system log display),
- maps.me (open source google maps alternative),
- MiXPlorer (file explorer),
- MoboClean (permissions manager),
- Naked Browser (web browser),
- NetGuard (no-root firewall),
- NeutriNote (notes),
- Nova Launcher (launcher)
- Open Camera (same as F-Droid app),
- Parasol (community based permission manager),
- PryFi (WiFi security),
- QuickPic (gallery),
- Recently ("close all apps" button in recents window),
- Recordr (sound recording app),
- Servicely (services management. Think twice before installing and using it - developer's G+ site, developer's APKMirror downloads
- SD Maid (cleaning tool),
- Super Backup (apps, sms, call logs, etc. backup),
- Titanium Backup (data backup),
- True phone (dialer),
- VLC (media player),
- WifiKill (WiFi killer),
- Wifi Protector (WiFi security, anti-wifikill),
- Xposed
You can find more interesting apps and links on this XDA forum
3. Software that may help you secure your device - sufficientlysecure.org
4. More security software - Secure Mobile Apps
5. XDA Labs (alpha version of XDA app store)
6. Firefox browser add-on that lets you download apk files directly from google play store (without Google account connected to your device) in case you can't find desired app anywhere else.
7. Alternative app-stores, .apk mirrors, etc. - use at your own risk. So far I only tried Amazon's store - the pro is that it exists, the cons are that it requires tons of permissions, has very unfriendly interface, takes a lot of space, and the apps you download will only work as long as the store's app is installed.
Credits and thanks
Motorola for making such a good device
Google for supporting Android (but not for invading it with their intrusive services)
lost101, kingkaminari and VitaTaf - creators of original ROM
HootanParsa - creator of MIxplorer
Menny Even Danan and all creators of AnySoftKeyboard
Tesla Coil and all creators of Nova Launcher
Klaus Weidner, creator of Hacker's Keyboard
All people behind TWRP
All the developers who share useful information and solutions in the web
Please let me know if I missed someone, I'll be happy to update this list
Download
IC6_lte_v1.2c_nogoogle.zip
Identity Crisis 6 LTE v1.0a_NoGApps_mod_v.1.0_beta.zip
Version information
Status: stable
Created: 4.03.2016
Updated: 24.05.2016
reserved
reserved 2
Has anyone had success getting this working yet?
I'm having trouble getting this to work.
Yesterday when I tried to install it i got the following error:
"symlink: no of syymlinks failed = 1
Updater process ended with error: 7
Error installing zip file '/sdcard/Identity+Crisis+6+LTE+v1.0a_NoGApps_mod_v.1.0_beta.zip'
Tried again today and managed to get it to install after rebooting recovery a few times, but ended up getting into a bootloop for 40 minutes.
I tried wiping everything, ART cache, system, data, internal and cache, but still get the same, an endless bootloop.
Any ideas?
Edit: This is on an XT1039
cvamoose said:
Has anyone had success getting this working yet?
I'm having trouble getting this to work.
Yesterday when I tried to install it i got the following error:
"symlink: no of syymlinks failed = 1
Updater process ended with error: 7
Error installing zip file '/sdcard/Identity+Crisis+6+LTE+v1.0a_NoGApps_mod_v.1.0_beta.zip'
Tried again today and managed to get it to install after rebooting recovery a few times, but ended up getting into a bootloop for 40 minutes.
I tried wiping everything, ART cache, system, data, internal and cache, but still get the same, an endless bootloop.
Any ideas?
Edit: This is on an XT1039
Click to expand...
Click to collapse
The first issue is internal TWRP error that happens pretty randomly, just restart recovery and it should be gone. The second thing never really happened to me, and I have to ask if you've followed instalation instructions? They're quite strict. You must wipe data and do a factory reset prior to installation. Just try again, following all steps exactly.
I'd also consider waiting a bit for final stable version with error fixes of lost101's ROM I use as a base. It's still kind of WIP.
I'd sure want to try this out, just wondering how well Google Play and Youtube work with the Micro G framework? Those are basicly the only google apps I use.
I could use the browser for youtube, create a link directly to the homescreen maybe. And I probably could survive without the play store to, just download apk from a mirror and sideload, but it would be kind of a hassle.
Anyhow, I probablt wait a few weeks until the MM rom seems stable.
Are you going to update this with the latest MM build by lost101?
baxtex said:
Are you going to update this with the latest MM build by lost101?
Click to expand...
Click to collapse
V1.2 seems stable, so I'll try to build something on this one, but don't really have much free time atm
No worries, just wondering!
Edit: I could actually remove all this stuff myself, the setup should be identical right?
Edit: Here is a version were I removed the same things you did. But I can't get it to work, or rather, I can't setup the phone. As your description says, you need to set it up with adb. But my computer won't detect the phone. I've tried reinstalling drivers here and there but whatever I do, Windows/adb won't detect any device. I do get a beep however that it is connected, and it says something like MTP usb device. But I can't do anything with that. I've tried installing it as an adb device instead but that didn't work.
https://mega.nz/#!P4k1QYwS!fBCp3E4uyjBXy7x6x_uTLTnj3pWjoIbgpqvodzWfEuQ
So I restored my backup, and I can connect to my pc just fine. In the device manager my device is shown as: Android Device>Motorla ADB Interface.
baxtex said:
No worries, just wondering!
Edit: I could actually remove all this stuff myself, the setup should be identical right?
Edit: Here is a version were I removed the same things you did. But I can't get it to work, or rather, I can't setup the phone. As your description says, you need to set it up with adb. But my computer won't detect the phone. I've tried reinstalling drivers here and there but whatever I do, Windows/adb won't detect any device. I do get a beep however that it is connected, and it says something like MTP usb device. But I can't do anything with that. I've tried installing it as an adb device instead but that didn't work.
https://mega.nz/#!P4k1QYwS!fBCp3E4uyjBXy7x6x_uTLTnj3pWjoIbgpqvodzWfEuQ
So I restored my backup, and I can connect to my pc just fine. In the device manager my device is shown as: Android Device>Motorla ADB Interface.
Click to expand...
Click to collapse
I read through IC thread - Lost101 is still polishing it, so I'll wait for some final build. And I guess you've got problem with ADB connection, because you didn't add persistent ADB debug to build.prop, or added but with some dodgy notepad (in Windows use Notepad++) - the lines that need to be added are in the OP.
minimale_ldz said:
Disclaimer
Even if everything works 100% fine for me I take no responsibility for anything that happens to anyone else's device after flashing my ROM. If you want to try it, do it on your own risk. Always backup your data.
Known issues
- Please refer to IDCrisis 6 LTE original thread
Click to expand...
Click to collapse
I have found a bug.
I was setting a lockscreen password that contained = in it and it came up as bad bad characted (I thought it's just a bug because it wouldn't show that error on stock firmware) so I have tried to enter the same password once more and it worked. Then I have locked the phone and couldn't unlock it because I allways entered the wrong password.
I think that the same thing would happen to encrypted devices.
I have found an interesting app that lets you enter permission control settings without root, because these permission settings is hidden in most android versions that came before marshmallow. Not granual, but still better than nothing.
It's size is 7kb, it asks for no permissions, probably because it's just a shortcut to the settings.
To people who don't have Play Store:
Install BlueStacks on your pc.
Root it using King Root.
Install desired apps using Play Store.
Install ES File Explorer:
From panel select:
-Tools/Root Explorer
-Tools/Show hidden files
-Network/Cloud/+/your desired cloud provider and log in.
-Local/Device/data/app .
Select your installed apps and copy them to your drive.
From your Play Store missing device goto your cloud provider website, log in ,download and install your apps.
This method can be long, but you will have all of the apps that you downloaded on cloud so you won't have to do the same process over and over again.
@minimale_ldz since u bought new phone I have to ask - you still remember about Moto G members, right?
I'm not asking when you'll update this rom, but if you're even going to
toster88 said:
@minimale_ldz since u bought new phone I have to ask - you still remember about Moto G members, right?
I'm not asking when you'll update this rom, but if you're even going to
Click to expand...
Click to collapse
It's coming soon
@toster88 motivated me with his comment to spend some time on preparing updated version of this rom. It' based on @lost101's IC6 LTE 1.2c version and contains a few little changes:
- AnySoftKeyboard replaced with Hacker's Keyboard as ASK is a bit awkward when it comes to accesing numeric keys
- MiXplorer has been updated to the newest version (6.4.0)
- Nova Launcher added (sorry for some artifacts like empty folders or Google search box, but I have no idea how to get rid of them)
- persistent ADB debugging removed from build.prop as it's no longer needed. Init.d script deals with initial device provisionig now. /system/etc/init.d/setup can be removed after first boot if everything is working fine (quick settings, home button, developer's options, etc. are accessible).
That's about it, I hope you'll enjoy this build. Please let me know if there are any bugs specific to this rom (and not to MM or IC6 1.2c) as I'm not using XT1039 as a daily driver anymore.
Temporary Google Drive link is now live
alezardstar said:
@minimale_ldz - Can you share with us how did you manage to debloat all the ROM and purge every GApps out of it preserving its stability? Did you delete the apks by hand using your laptop before installing the zip or what did you exactly do? I'm keen to get this working on the very last release (1.5b) for Falcon.
Thanks in advance.
Click to expand...
Click to collapse
You can just unzip the rom and remove unwanted apps (with their folders) by hand in Windows file explorer and then zip it back. Or, if you wanna feel more like a propper dev you can do it with Superr Kitchen where you create custom debloat list. Both methods are confirmed to work. Removing GApps is a bit tricky as you need to remove all of them - if you leave anything it may give you FCs or black screen after boot. You will also have to choose some way to provision the device without GApps and i believe the smoothest method is by init.d script sice it's enabled in @lost101 rom and doesn't require users to do anything after installation. The script looksi like this:
Code:
#!/system/bin/sh
su -c "settings put global device_provisioned 1"
su -c "settings put secure user_setup_complete 1"
and goes in /system/etc/init.d folder
I hope that helps.
alezardstar said:
Thanks for your response. I definitely shall give it a spin with next Identity Crisis release. It happens to me I do not work on Windows, rather GNU/Linux. Do you think I can delete all the OP mentioned apks and on top of that any missed folder/apk appearing on this link using Fedora 25? As far as I could read, the link I'm passing on has Linux instructions, though being honest, I have no leisure time to read it thoroughly and that's why I'm saying I shall do it next Identity's release better. In the meantime, I want to be a hundred percent sure about what I will do when the moment comes in. Can you tell me what provision is? What does it stand for? Should I get a signature spoofer? All I want to do is Identity working as it works itself, with no GApps and supersu working as it's been working always. Although I'd say installing microG may cushion the blow since it is a FLOSS Google framework that will not make things break in a regular use. To sum it up, do I need to create a .txt file or something with the code and thereafter make it work with a init.d script application or something similar?
Thanks for all your help! Looking forward to hear from you and sorry for my late response. Real life keeps me away from my beloved hobbie: learning.
Click to expand...
Click to collapse
I guess it should work pretty much the same on Linux. Do mind I've removed much more than just GApps and today I'd left some more apps in the rom as I found them useful - eg. Calendar Provider or FM radio, but it's up to you. The bare minimum, required to get rid of GApps is:
Code:
/system/app:
- ConfigUpdater
- CalendarGoogle
- GoogleContactsSyncAdapter
/system/priv-app:
- BackupRestoreConfirmation
- GmsCore
- GoogleBackupTransport
- GoogleFeedback
- GoogleLoginService
- GoogleOneTimeInitializer
- GooglePartnerSetup
- GoogleServicesFramework
- MotoOneTimeInitializer
- Phonesky
- SetupWizard
- SetupWizardExt
The list you linked is more extensive and goes deeper into the system but it's quite similair to what I've done. You cane safely remove
Code:
system/usr/srec/en-US/
as it contains speech recognition files that Google Services use to listen to us.
I was careful with
Code:
system/lib/
because I didn't find any source describing what these libraries are actually for. Removing anything with "google" in its name seems safe. You can compare what IDCrisis has with the list and see if it can be removed safely - there's a lot of experimenting involved but the list looks like a good guide.
Code:
system/vendor/pittpatt/
contains face recognition system that I find useless with or without GApps and it can be safely removed.
Now, when you remove all GApps you'll have to provision your device. Long story short is that when you first boot your phone after flashing new rom it will start with Setup Wizard where you'll be asked for wifi password, google account details and where you accept all terms & conditions. By default you're locked in setup mode until it's finished - you can't use home button to escape it, you can't access settings, etc. If you remove GApps there's no Setup Wizard so your phone will stay in setup mode and you need to end it manually. Like I said before, the best way is to use init.d script. Use Notepad to create new file, copy the lines I posted last time, save it without any extension, I believe its permissions need to be set to 755 (rwxrxrx). Place the file in
Code:
system/etc/init.d
and that's it.
Alternatively you can use ADB or terminal emulator to execute these commands:
Code:
adb shell (only if you use ADB)
su
settings put global device_provisioned 1
settings put secure user_setup_complete 1
or you can use XDRsetup app I made to do the job (it needs root to work).
Good luck
alezardstar said:
@minimale_ldz - Apologies for my late answer. I've been busy. Thanks for your response. It is appreciated what you've done for Peregrine's users and hence for everyone who's willing to ditch GApps from @lost101 builds.
At the moment I'm stuck at a step. I'm on Fedora 25 and I want to remove a whole folder within the system /system/app/MagiskManager/ or whatever the directory is and I can not. Albeit I might delete the superuser and Magisk folders whose location is the very first thing we see as we open the .zip, I can't do the same with folders within the system and I wonder why. The other option is extracting the whole content of the ROM in a new directory and deleting files at my will. Thereafter, I can zip it back. The problem is that I do not know how to zip it back. Do you have any idea of somebody who mod on GNU/Linux?
On the other hand, I saw this apk you passed on to make the init.d script work. The simple steps that popped up on my mind were:
- Factory reset.
- Flash ROM + supersu.zip
How can I put your application within the system folders and ensure it'll work as expected? Another thing that I lack knowledge of is the permissions. How can I give a file or a folder permissions on GNU/Linux? There's nothing else I can think of other than wiping everything, flashing the ROM alongside the supersu.zip and booting up but as you told me, I'd be frozen at the first screen. It's strange for me to get ahead but I'm keen to learn and get ahold from you anytime.
Click to expand...
Click to collapse
My knowlege of Linux is pretty much none. I'm using Ubuntu for Superr's Kitchen and that's it. I don't know how different Fedora is from Ubuntu, but Ubuntu interface is very similair to Windows, so never had any problems with simple files operations like unpacking, deleting, etc, and there's always Google at hand with tons of tips and help. Extracting the rom.zip is a good first step, but I'd install the Kitchen - it really makes things esier.
BTW - beside Magisk and Superuser folders there are also apps in /system/app that need to go if you're deleting binaries. They will survive factory reset but won't work. AFAIK they are in lost101's only temporarily and he said he'll use Chainfire's SU in next version anyway.
For setting permissions, as mostly Windows user, I have two solutions - you can either set them in TWRP using its file manager or do it in Android (I'm using MiXplorer for that). You just need to root your rom first.
And you won't be frozen at the first screen if you remove all GApps and SetupWizard apks.
I got almost everything working, but I can't access the Phone via USB from my WIN7 Desktop. It works with adb/fastboot but not as MobileDevice, also it is shown in WIN-Eplorer as XT1072. It did work before I flashed this ROM.
Any advice would be highly appreciated
Thanks in advance
Solved
"Internal Storage not accessible from PC?
With Marshmallow, the default USB connection type is 'Charging only' mode. You can change USB mode to 'MTP' via the pull-down notification option"
Hey,
I tried several times to pass Safety Net so I can use Google Pay, but I get a constant CTS mismatch.
Things I tried:
-Going back to older Firmware
-Locking Bootloader
-Removing USB debugging mode
-Factory Reset (in eRecovery)
I don't know what else it could be.
Firmware I've installed right now is the CLT29 159 C432
you have busybox installed? or magisk?>
RiTCHiE007 said:
you have busybox installed? or magisk?>
Click to expand...
Click to collapse
nope and nope
like I said I already did some factory resets or flashed firmwares
Then try to install magisk and use the magisk hide feature on the system.
RiTCHiE007 said:
Then try to install magisk and use the magisk hide feature on the system.
Click to expand...
Click to collapse
I already did that. Doesn't help. It also should pass if I'm not rooted or anything. But it doesn't pass.
I also tried flashing a different boot.img because I thought it could have been not flashed but nope also doesn't help.
KennyDumah said:
I already did that. Doesn't help. It also should pass if I'm not rooted or anything. But it doesn't pass.
I also tried flashing a different boot.img because I thought it could have been not flashed but nope also doesn't help.
Click to expand...
Click to collapse
There was someone a few days ago that couldn't get google pay to work also and when he joined the play service beta then after a reboot it worked. But it sounds like there are some files on your storage that **** up the whole thing so maybe its good if you did a system format.
RiTCHiE007 said:
There was someone a few days ago that couldn't get google pay to work also and when he joined the play service beta then after a reboot it worked. But it sounds like there are some files on your storage that **** up the whole thing so maybe its good if you did a system format.
Click to expand...
Click to collapse
So I should fastboot format system / data / cache and then go to twrp or eRecovery and flash a new firmware?
Is it OK to do that in a Huawei?
Used to have nexus phones and it was way easier to do stuff
KennyDumah said:
So I should fastboot format system / data / cache and then go to twrp or eRecovery and flash a new firmware?
Is it OK to do that in a Huawei?
Used to have nexus phones and it was way easier to do stuff
Click to expand...
Click to collapse
Well, im more thinking like flashing a PIt file like on the samsung where it formats the whole memory and then flashes the firmware so that its 100% original.
RiTCHiE007 said:
Well, im more thinking like flashing a PIt file like on the samsung where it formats the whole memory and then flashes the firmware so that its 100% original.
Click to expand...
Click to collapse
Is there anything like that for Huawei?
BTW I already tried formating all partitions and reflashing. Still doesn't pass CTS.
So you said this one guy installed Google play services beta?
yea like this https://www.youtube.com/watch?v=v_RzbAhJkOk
RiTCHiE007 said:
yea like this https://www.youtube.com/watch?v=v_RzbAhJkOk
Click to expand...
Click to collapse
Tried that aswell and noticed I'm already in the beta of google play services. So thats also not my problem.
KennyDumah said:
Tried that aswell and noticed I'm already in the beta of google play services. So thats also not my problem.
Click to expand...
Click to collapse
Try this
- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot
Should fix CTS
dladz said:
Try this
- In the Magisk downloads section, download and install “MagiskHide Props Config”
- Reboot
- Download a terminal emulator from PlayStore (eg Termux)
- Open terminal emulator
- If using Termux type “su” and grant root access
- Type “props”
- Select option ‘1 edit device fingerprint’
- Select option ‘f
- pick a certified fingerprint’
- Select option ‘4
- Huawei’
- Select option ‘6
- Huawei P20 Pro (8.1.0)’
- Enter ‘Y’ for yes
- Reboot
Should fix CTS
Click to expand...
Click to collapse
Thanks will try that later at home. But shouldn't CTS pass safetynet, when I installed a new firmware without root etc?
Because that's my point. I'm not rooted or anything and flashed just a new firmware with full factory wipe.
Anyways I gonna try that as soon as I get on my pc.
KennyDumah said:
Thanks will try that later at home. But shouldn't CTS pass safetynet, when I installed a new firmware without root etc?
Because that's my point. I'm not rooted or anything and flashed just a new firmware with full factory wipe.
Anyways I gonna try that as soon as I get on my pc.
Click to expand...
Click to collapse
What else is installed?
Are all apps up to date? I had an issue a while back and it was just Google, needed an update.
Once I had and rebooted it worked.
Couldn't finish the Google pay set up, kept halting on the agreement pages.
Updated and all good.
This method worked fine for me. Thanks! I'm on 159 as well.
So I fixed it on my phone now.
I was about to try what @dladz wrote.
I installed TWRP again so I had to remove my fingerprints and screenlock.
after flashing Magisk I suddenly had the CTS passing, I dont really know if its a bug with the screenlock and fingerprints.
Hello there!
As per title I'm having a hard time installing any apk that's not coming from the Play Store.
Never happened with any other phone and googling for an hour and a half didn't help, so I've decided to post it here.
Emui10 (last build).
Play protect is disabled.
Chrome is enabled as unknown source.
Tried also third party installers with no luck.
I uploaded a little video but can't post it due to anti spam policy, in wich it shows the installation process starts, but in the end says "App not installed".
What am I missing?
Thanks in advance for any help!
A little update:
Tried to install them via ADB but that's the error I get:
[INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.vanced.android.youtube attempting to redeclare permission com.mgoogle.android.c2dm.permission.RECEIVE already owned by com.mgoogle.android.gms]
Unfortunately my knowledge ends here...
Shakin0 said:
A little update:
Tried to install them via ADB but that's the error I get:
[INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.vanced.android.youtube attempting to redeclare permission com.mgoogle.android.c2dm.permission.RECEIVE already owned by com.mgoogle.android.gms]
Unfortunately my knowledge ends here...
Click to expand...
Click to collapse
YouTube came preinstalled on P30, so you have to use adb to remove it before you try to install a new one.
Here you can find the guide to remove it: https://forum.xda-developers.com/hu...w-to-remove-huawei-bloatware-vog-ele-t4014937
zimmen said:
YouTube came preinstalled on P30, so you have to use adb to remove it before you try to install a new one.
Here you can find the guide to remove it: https://forum.xda-developers.com/hu...w-to-remove-huawei-bloatware-vog-ele-t4014937
Click to expand...
Click to collapse
Strange thing is that on my previous phone I had both YouTube (the official one), and YouTube Vanced...
Uninstalling via ADB ends in an error (can't rememeber which one as I'm afk atm). Another strange thing is that I already successfully unisntalled a lot of other processes mentioned in the guide you linked!
Now that I'm writing I guess that the phone clone process could have messed up some app/permissions, so I guess I'm doing a factory reset, clone everything but apps, try to install Vanced and Microg and then reinstall all my apps manually :good:
Shakin0 said:
Now that I'm writing I guess that the phone clone process could have messed up some app/permissions, so I guess I'm doing a factory reset, clone everything but apps, try to install Vanced and Microg and then reinstall all my apps manually :good:
Click to expand...
Click to collapse
And THAT solved the problem. :laugh:
New method that worked for me (2023/01/21) here. If the below method doesn't work, try it.
----------------------------------------------
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Steps:
0 - Some steps won't happen like you see on the video, so read carefully.
1 - Watch the whole tutorial first: The link to the tutorial: www.youtube.com/watch?v=7kGkLsf83Bk
2 - Download the app to your device and the HuaGu PC ADB to you PC.
3 - Turn off wifi and mobile data on your device, turn off the internet on your PC (this is just for security reasons, may not be really necessary. I did it)
4 - Do all the PC stuff you see on the video and also step 1 and 2 on the HuaGu app.
5 - When you reach step 3 of the HuaGu app, you may get stuck on the Restore Backup process. Let it run for a minute, go back, and if the step 3 doesn't have a check, do it again. On my 2nd try I got a check on step 3 and moved on.
6 - Turn on wifi or mobile data on your device.
7 - When doing step 4 of the HuaGu app, it should open the Google Service Assistant (that app with the purple G), gives you a error in Chinese and you won't see the same screen as in the video tutorial. Just got back to the HuaGu. It will give you a hint about not knowing if the Assistant did anything (In my case it appears that did nothing, but the whole thing worked anyway).
8 - Do steps 5, 6, 7, 8 and 9.
9 - Open Google Play Store. You'll get those annoying notifications about the not valide device / certifications / whatever. Press retry, open, close, retry and eventually Google Play Store will open normally even with all the notifications popping up.
10 - Install Google Maps. It's going to be annoying to do because of all the notifications.
11 - Open Google Maps and confirmed that you are logged in to your account. Move around the map a bit.
12 - Leave the device showing notifications for a minute or two.
13 - If you still have the annoying notifications (you probably will), go back to the HuaGu app and press on step 10.
14 - There, press step 0 and go back (I didn't register anything here. Maybe because at one time I had GMS on this device, dunno).
15 - Do all the other steps like it says.
16 - Open Google Play Store and disable automatic updates. Close it.
17 - Reboot again.
18 - Open Google Play Store, open Google Maps. If everything is working and without annoying notifications, uninstall HuaGu, Google Service Assistant and that backup restore app. Also, go to your downloads folder and there should be a bunch of APKs that were used during the tutorial. You can delete those as well. Turn off Developer Settings if you don't use them.
Congrats!!! You should have GMS on your device!! I only tested with Maps because it's the only app I really care about that needs GMS to be work so I can use all its features.
Thank you badmania98 and Average Logs!
so i have to roll back the EMUI from 12 to 10 first right?
XanaRaquel said:
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Thank you badmania98 and Average Logs!
Click to expand...
Click to collapse
Is your Google account on phone Settings\Users & accounts\Google ?
I tried about 20 times to do according to this instructions with HuaGu2.
Tried 10 times with HuaGu3.
And every time the same result: after uninstalling MicroG and installing Google Play Services, there is no Google item in Settings, no Google accounts (although there were MicroG accounts) and the Play Market asks to enter.
I have a Huawei P40 EMUI 12 Europe phone. I tried several different firmware, downgraded to EMUI 11 - the result is the same.
Have you come across such cases? What to do?
Not working for me either, same reason. When i uninstall microg, it also uninstalls my google accounts
P40 Pro, 10.1.0.176 (c432)
Any suggestions?
BestAlex said:
I tried about 20 times to do according to this instructions with HuaGu2.
Tried 10 times with HuaGu3.
And every time the same result: after uninstalling MicroG and installing Google Play Services, there is no Google item in Settings, no Google accounts (although there were MicroG accounts) and the Play Market asks to enter.
I have a Huawei P40 EMUI 12 Europe phone. I tried several different firmware, downgraded to EMUI 11 - the result is the same.
Have you come across such cases? What to do?
Click to expand...
Click to collapse
Cheecky2chops said:
Not working for me either, same reason. When i uninstall microg, it also uninstalls my google accounts
P40 Pro, 10.1.0.176 (c432)
Any suggestions?
Click to expand...
Click to collapse
A lower firmware is needed.
EMUI10.1.0.121 or 131 for P40Pro C432.
badmania98 said:
A lower firmware is needed.
EMUI10.1.0.121 or 131 for P40Pro C432.
Click to expand...
Click to collapse
Hi, I tried it 1st a few times on 10.1.0.121, exactly same outcome. The dam thing then auto updated to 176 and tried with that, again, exactly the same outcome.
Cheecky2chops said:
Hi, I tried it 1st a few times on 10.1.0.121, exactly same outcome. The dam thing then auto updated to 176 and tried with that, again, exactly the same outcome.
Click to expand...
Click to collapse
All steps are described on my (closed) thread. See my signature.
badmania98 said:
All steps are described on my (closed) thread. See my signature.
Click to expand...
Click to collapse
Yes, I was going to try that. But when I tried to downgrade via your Dload method (like i did before to get to 121) it wont let me downgrade now. It is now on 230. I've formatted memory stick, put dload folder back on it and tried again but it stays at 230. So why before it let me downgrade but not now? I dont get it.
Cheecky2chops said:
Yes, I was going to try that. But when I tried to downgrade via your Dload method (like i did before to get to 121) it wont let me downgrade now. It is now on 230. I've formatted memory stick, put dload folder back on it and tried again but it stays at 230. So why before it let me downgrade but not now? I dont get it.
Click to expand...
Click to collapse
From 11.0.0.230 to 10.1.0.121 you never ever have to use dload method. I never recommend this.
badmania98 said:
From 11.0.0.230 to 10.1.0.121 you never ever have to use dload method. I never recommend this.
Click to expand...
Click to collapse
Ohhh, sorry, i think im gettibg confused and your repky has helped me remember, thanks!
So i used dload method to get to 230. Then i must of used hisuite proxy to get to 121. Sorry mate, ill try that again later, then the method you used for gms.
XanaRaquel said:
After literally a year I have GMS on my P40 Pro again!
What worked was following a tutorial that badmania98 shared (thank youuu)
I didn't see anyone comment about this so here's what I did that actually worked.
First of: My device is a Huawei P40 Pro with EMUI 10 - 10.1.0.176 (C432E8R6P1). I don't know if it works with other EMUIs/devices. It should according with the video tutorial.
Steps:
0 - Some steps won't happen like you see on the video, so read carefully.
1 - Watch the whole tutorial first: The link to the tutorial: www.youtube.com/watch?v=7kGkLsf83Bk
2 - Download the app to your device and the HuaGu PC ADB to you PC.
3 - Turn off wifi and mobile data on your device, turn off the internet on your PC (this is just for security reasons, may not be really necessary. I did it)
4 - Do all the PC stuff you see on the video and also step 1 and 2 on the HuaGu app.
5 - When you reach step 3 of the HuaGu app, you may get stuck on the Restore Backup process. Let it run for a minute, go back, and if the step 3 doesn't have a check, do it again. On my 2nd try I got a check on step 3 and moved on.
6 - Turn on wifi or mobile data on your device.
7 - When doing step 4 of the HuaGu app, it should open the Google Service Assistant (that app with the purple G), gives you a error in Chinese and you won't see the same screen as in the video tutorial. Just got back to the HuaGu. It will give you a hint about not knowing if the Assistant did anything (In my case it appears that did nothing, but the whole thing worked anyway).
8 - Do steps 5, 6, 7, 8 and 9.
9 - Open Google Play Store. You'll get those annoying notifications about the not valide device / certifications / whatever. Press retry, open, close, retry and eventually Google Play Store will open normally even with all the notifications popping up.
10 - Install Google Maps. It's going to be annoying to do because of all the notifications.
11 - Open Google Maps and confirmed that you are logged in to your account. Move around the map a bit.
12 - Leave the device showing notifications for a minute or two.
13 - If you still have the annoying notifications (you probably will), go back to the HuaGu app and press on step 10.
14 - There, press step 0 and go back (I didn't register anything here. Maybe because at one time I had GMS on this device, dunno).
15 - Do all the other steps like it says.
16 - Open Google Play Store and disable automatic updates. Close it.
17 - Reboot again.
18 - Open Google Play Store, open Google Maps. If everything is working and without annoying notifications, uninstall HuaGu, Google Service Assistant and that backup restore app. Also, go to your downloads folder and there should be a bunch of APKs that were used during the tutorial. You can delete those as well. Turn off Developer Settings if you don't use them.
Congrats!!! You should have GMS on your device!! I only tested with Maps because it's the only app I really care about that needs GMS to be work so I can use all its features.
Thank you badmania98 and Average Logs!
Click to expand...
Click to collapse
I am unable to make a backup with Huagu pc app. And I suspect that is because I have FW10.1.0.121 and data transfer and fast charge is disabled, right?
Help much appreciated. Thx
The guide that I posted on the top doesn't work for me anymore - Device not certificated errors. It stopped working around last November. However, today I found a tutorial that works:
So new Tutorial:
Link here
WHAT I DID DIFFERENTLY:
1 - His version is 10.1.0.134 but I'm still on 10.1.0.176 (superior) and it worked.
2 - Maybe because of that, the process of Backup & Restore doesn't worked. The password isn't "icfix1net" anymore, it's "a12345678" or whatever is in the password tip. Still, couldn't restore. So I skipped opening that chinese app.
3 - Google Play Store didn't installed - said it's already installed (which isn't). I continued anyway.
4 - From this point forward I did everything like the tutorial except the parts that involve Google Play Store and the activation of syncing contacts.
5 - Uninstalled the Backup & Restore app.
6 - Done.
Notes:
- If you want to install apps just use the Aurora Store. It uses the apps from Google Play Store so it's safe. I installed Google Maps from there to do the testing.
- Google Play Store is what actually messes everything up because it updates itself and GMS. Either don't install it or block its access to the Internet (you can do that in the settings or use a firewall or whatever).
- If this doesn't work, try to follow the whole tutorial. Who knows. Like I said in the beginning, this is what worked for me.
- If you need to downgrade there are links in the video description, plus there's a lot of tutorials there on XDA for that.
Side note: If you noticed, he has a P40 Pro with unlocked bootloader. I don't know what's the point since there isn't root or custom ROMs available, but it can be done (probably paying). Mine is NOT and it doesn't make a difference in the process.
Good luck everyone !
EDIT: Late reply to everyone:
- Yes, the Google account is in the Settings.
- This new tutorial doesn't use the PC so try this.
- About all firmware questions I can't really answer. I have 10.1.0.176 and never done a downgrade. I simply never updated after that and always disabled the auto updates.
Hi guys,
new here and went through quite a few threads on Magisk before posting.
Situation is as follows:
- got my Xiaomi Mi 11 Ultra from Aliexpress a few days ago.
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
- the phone works fine, but Google Wallet would not allow me to add any of my credit/debit cards for contactless payments showing the usual "Your phone doesn't meet security requirements"
- NETFLIX wouldn't work.
- Quite a few of my banking apps work fine, including HSBC bank, Paypal, Revolut, IG Index and some others as well.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Is there any way to find out what ROM is installed and perhaps I could download the package and get the boot.img file from there? (ramdisk parameter show YES)
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
Kotofeus said:
- the seller unlocked the bootloader and instealled global ROM instead of the original Chineese ROM.
The obvious solution is to go ahead with Magisk Hide (or what's currently available instead as Hide module is phased out as far as I understand).
Now, I'm really new to all this (have rooted a couple of phones/tablets a few years back) and have a few questions:
1. I was going through the process of installing Magisk on my phone, folloing the instructions here: https://www.xda-developers.com/how-to-install-magisk/?newsletter_popup=1
So according to this, I'm supposed to find a boot.img file in the ROM archive as far as I understand, but my issue is that I don't have the installed ROM details or data as it wasn't me who installed the ROM in the first place.
Click to expand...
Click to collapse
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Kotofeus said:
2. I will be installing ADB on my computer to be able to install Magisk as per the following instructions: https://www.xda-developers.com/install-adb-windows-macos-linux/
is there anything else I'd need?
Click to expand...
Click to collapse
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
Kotofeus said:
3. Lastly, there is a bunch of good tutorials on your tube on how to use the latest Magysk + shamiko module etc. If someone knows a really good one, I would appreicate if you could post it
Click to expand...
Click to collapse
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Kotofeus said:
Would really appreciate any other feedback etc for a person who is completely new to this
Thank you very much!
Click to expand...
Click to collapse
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
simplepinoi177 said:
I'm not sure how to completely proceed as I am totally unfamiliar with Xiaomi, but I had a couple of ideas...
I imagine you can find exactly what ROM you are using in the Settings -> "About Phone" or something similar; Probably under something like "Android version" or "Build number". You can google search (most likely by build number or something similar) and find the Factory image needed to flash/install the ROM. Once you download that specific ROM installation file (most likely a .zip file), you should be able to extract it (or go inside the zipped file and extract the specific boot.img file) to be able to patch it in Magisk.
Best place to get the adb (and you'll also need fastboot.exe so you'll also get it from) is from the Platform Tools from Google's developer's site here: https://developer.android.com/studio/releases/platform-tools
I'm unsure (but I doubt) if Xiaomi Mi 11 Ultra has 2 slots (A and B), but if it does, don't download the latest version of platform tools but version r33.0.3 because any version r34.0.0 and above has a known bug that will wreck devices with 2 slots (namely Google Pixels).
Anything else you'd need is to be sure to have USB debugging enabled and the proper Google USB drivers installed on your computer (there are Windows, Mac, and Linux drivers that can be installed).
There are a number of root hide methods that hide root from Netflix and Google Wallet. One usually starts with using Magisk and Zygisk Denylist and making sure that Wallet, Netflix, Google Play Services, Google Play Store, Google Play Protect, and Google Service Framework are all "ticked" with all their sub-selections ticked as well. Also, be aware that after implementing any/all of these, usually clearing all these Google services data and cache is required & a reboot of the device is a must, but re-entering your cards will also be required as well; as well as signing back into some Google services. Then, if all that doesn't work, there's Universal SafetyNet Fix -- or even Displax's Mod branch if the official USNF isn't enough. Then also any of the further root hiding methods; Shamiko, Magisk Delta, HideMyApp, etc..
Again, I'm coming only from Pixels and have absolutely no experience with Xiaomi and I can't be sure any of these will apply since you have a "custom" ROM (sort of) so things might not be as usual. These are just general dealings with Magisk and Android OS as I know them... But you state that you are "completely new to this", so I'm just trying to cover all the bases as much as I can, even if you would be already knowledgeable of them. If anything, these can be taken as just ideas and/or pointing to a direction that might work...
Click to expand...
Click to collapse
Thank you very much for taking time and going through all my queries, really appreicate it!
I started losing hope really as looked through a number of vide tutorials involving installing magisk via custom recovery, which would mean I needed to install a custom recovery first... so this was becoming a bit of a Russian Doll thing and a never ending quest.
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
If I can't find the ROM, than the only way is to try and install custom recovery, download Magisk apk, rename it into zip, get into custom recovery mode and try to flash the zip file. Saw a few tutorials on youtube like that and it looked fairly straightforward, however not sure how easy or difficult it would be to install a custom recovery like TWRP on this phone.
I also looked through a tutorial of using Magisk with Zygisk and Denylist and again, looked pretty straightforward, but Magisk needs to be properly installed of course.
Yes, thank you - I understand that you need to clear cash and re-enter the cards once again, that would have been the least of my troubles.
Will try to search that kernel number on google once I have a moment and see if I get any luck.
Will also reasearch on how to install TWRP. If that's easier than I may go with that option instead of extracting and patching the boot.img
Kotofeus said:
Looked at "Detailed info and specs" on my phone and I have:
Baseband version
Kernel Version
I presume I can search by Kernel Version to find the ROM - will try that.
Click to expand...
Click to collapse
You can't find what MIUI version you have? That's all you basically need...
From a small bit of research, you state you are on a "global ROM" of a Xiaomi Mi 11 Ultra, which should just be a "global" version of the MIUI. You just need to find the MIUI global version and extract it (boot.ini) from the firmware update file. Once you find the version, you could search and find the firmware update file in places like here: https://xiaomirom.com/en/rom/mi-11-pro-ultra-11-ultra-star-global-fastboot-recovery-rom/ or other sites I imagine.
It's just important that you get the exact right version of the MIUI Global ROM you are currently running as patching and flashing a boot.ini of a different version could soft-brick/bootloop your device....