Related
Hey guys,
so I thought about getting a Redmi note 3 Pro since my wileyfox swift broke.
I am a person that "needs" his phone rooted for adaway and viper audio. I also like CyanogenMod a lot.
After reading through a lot of threds here I got kind of confused and I am really sorry for the dumb questions following.
So what exactly do I have to do to get my phone unlocked rooted and maybe install CM (if it is stable enough).
And there seem to be quite many MIUI Roms out there. what is the difference between all these "global", "eu" and stable or developer versions?
Thanks in advance.
EDIT: Also I read that I can change MIUI Roms with locked bootloader. Can someone explain this?
First the firmware
Global rom is intended for worldwide use (has google play store installed, and other google apps)
China rom is for the chinese and has mostly china specific apps / china app store
Developer rom is usually the latest MIUI version so it could be buggy and is intended for testing
Stable rom is been thoroughly tested and is thought to be the most stable and reliable rom.
Vendor rom is a very stable rom given to sellers to flash for international buyers, most users would never notice, however for enthusiasts it can cause problems getting the device unlocked since it's not identified by the unlock tool, causing users to have to go through a semi-difficult process getting it back to the stable or developer firmware so we can properly unlock it.
(if you do buy one I suggest you ask them to send one with the Chinese firmware since they are easier to flash and unlock)
then there is the eu/smiui roms which are built form the official source but they are 3rd party firmwares, just compiled by someone else maybe with additional features or tweaks.
For the bootloader there is several ways to unofficially unlock it but they are risky, I won't go into that since it should be only as a last resort.
to request xiaomi to unlock your device you go to this website
http://en.miui.com/unlock/
fill out the required information, sign up for an account (you need to use a phone number you can receive sms messages on), and in a few days they usually grant permission, remember your username / email and password since you will need it later when you unlock it., then download the unlock tool, boot your phone to fast boot and then press unlock on the tool, and it should unlock (unless you have the troublesome vendor firmware), if unlocked now you can install twrp / cm13 / root / xposed ..etc
--
you can flash the official miui roms with the locked bootloader
Just to add, if you get an international version of the phone (Special Edition, codename Kate) then the bootloader unlock process does not seem to work at all. I had to resort to an unofficial unlock after trying for over a week (and I'm not new to this).
I would wait. I rely on my phone and mine stopped charging after 10 days. Followed all the silly guides about flashing this, flashing that. Only time phone is recognised is in fast boot mode but no charge. Now my phone is dead and Xiaomi support is nowhere to be seen. They said they will contact me in 24h and its been 3 days.
If you really rely on your phone then please buy a phone that has real customer support. Best case scenario you have to send phone to China and worst case scenario you have to buy a new phone.
otyg said:
Vendor rom is a very stable rom given to sellers to flash for international buyers, most users would never notice, however for enthusiasts it can cause problems getting the device unlocked since it's not identified by the unlock tool, causing users to have to go through a semi-difficult process getting it back to the stable or developer firmware so we can properly unlock it.
(if you do buy one I suggest you ask them to send one with the Chinese firmware since they are easier to flash and unlock)
....
For the bootloader there is several ways to unofficially unlock it but they are risky, I won't go into that since it should be only as a last resort.
to request xiaomi to unlock your device you go to this website
http://en.miui.com/unlock/
....
....boot your phone to fast boot and then press unlock on the tool, and it should unlock (unless you have the troublesome vendor firmware), if unlocked now you can install twrp / cm13 / root / xposed ..etc
--
you can flash the official miui roms with the locked bootloader
Click to expand...
Click to collapse
I bought for my parents 2 Redmi 3 for them to enjoy. I know vendors hinder with the Rom so I usually ask to keep the phone on its original chinese Rom when i buy for myself or for my wife.
However this time I made a mistake thinking that who needs OTA for my parents and i ordered it as it is.
Turned out all google services stops working in the next day whatever I do (reboots, resets, formats, etc...).
I tried flashing via updater app the global rom, it failed.
I tried flashing by rebooting to recovery, it didnt reboot to recovery.
I tried some other stuff which failed.
I downloaded xiaomi unlock tool, signed in, and tried to unlock the bootloader. It didn't work.
I read somehow on miui forums that it's probably a driver issue (something about disabling signature which i'm not familiar with).
Can you please help me?! What to do now? Steps or a guide would be awesome.
Thanks,
Ah safetynet, the thorn in the side of every technical android user who wants to use Android Pay.
It's even worse on a xiaomi device, because once you've been granted a bootloader unlock after waiting for days, you don't want to re-lock it for fear of locking yourself out of the device and having to wait another 30 days before you can get a new unlock permission!
There is a lot of old information around about hiding root, custom kernels, installing things in particular orders and I'm pretty sure I've tried them all - including compiling kernels from scratch with a few different versions of the unlocked bootloader hiding patch.... never getting past the dreaded CTS Mismatch
But all of a sudden I happened on a little known secret found by @kyasu that the build fingerprint is also checked : https://forum.xda-developers.com/showpost.php?p=70831797&postcount=3665
Also, conveniently, Magisk (since v9) patches the ro.boot.verifiedbootstate and related props that SafetyNet checks.
This now gives us two options to enable safetynet regardless of bootloader state.
You will need either a kernel with bootloader state hidden OR magisk, as well as a method of changing the build fingerprint.
This also assumes you've got TWRP installed and are comfortable using it.
Tested on Mi5 Lineage OS 14.1-20170206-NIGHTLY-gemini and various xiamoi.eu 7.2.X and 7.3.X versions:
NOTE: Magisk Hide on MIUI currently does not work (21st July 2017)
This has been widely reported and there are a number of open issues:
https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open miui
A fix may have been found, not ready to test however:
https://github.com/topjohnwu/Magisk/issues/298#issuecomment-316687923
Magisk:
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
From TWRP install Magisk v13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Restart and Magisk Manager app should be installed.
Hit the test safetynet button in Magisk Manager, if it passes stop here! Latest lineage roms don't need my magisk fingerprint module anymore, they just work.
Otherwise, download this magisk module on your phone: https://gitlab.com/alelec/magisk-ge...2bbf9dc8/magisk-gemini-safetynet-props-v3.zip
In Magisk Manager, go to modules and install the magisk-gemini-safetynet-props zip just downloaded. It should prompt to restart to enable module, do so.
After restart, fire up Magisk Manager and "tap to start SafetyNet check", fingers crossed it comes up Green!
Note: After each rom update you will need to reinstall Magisk in twrp, but the safetynet enabling module above should stick just fine and not need reinstall.
Custom Kernel:
I don't test this as often, as I prefer the Magisk method, however this is an option for people who don't want any kind of root on their phones.
I also don't maintain any patched kernel for miui based roms as the one's I've tried are just too buggy.
Remove any previous root, usually this can be done by simply dirty flashing your current rom in twrp.
Install gemini-safetynetpass-stable-fingerprint-20170217.zip
this package is based on gemini-safetynetpass-20170213.zip by @kyasu but only changes the build prop fingerprint, the old custom kernel has been removed:
Install a patched kernel, you can either use my autobuild of a patched latest LineageOS kernel for Mi5 (includes fingerprint fix):
https://gitlab.com/alelec/android_kernel_xiaomi_msm8996/tags (LineageOS-gemini-safetynet-kernel_XXXXXX.zip links)
or recent DragonXia kernels appear to be patched
https://forum.xda-developers.com/mi-5/development/kernel-brand-kernel-cm13-alpha-1-0-t3480663 (LineageOS)
https://forum.xda-developers.com/mi-5/development/kernel-dragonxia-kernel-v1-0-t3546619 (MIUI)
Note: Both the kernel and fingerprint zip above will need to be re-installed after each rom update.
On a related note, if you want to use Android Pay on MIUI based roms, make sure the HCE wallet configuration and permissions are set correctly.
See the following for more details: http://en.miui.com/thread-405166-1-1.html
Once you unlock it once, you can unlock it again without waiting. I just unlocked and relocked my Mi5 about 3 times in a couple days.
Sent from my MI 5 using Tapatalk
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
coronafire said:
Oh really? Wow, nothing I've read anywhere in the last few weeks has said that before, certainly simplifies things!
Do non stock kernels boot on a locked bootloader though? They didn't on my previous Sony.
Click to expand...
Click to collapse
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
I'm not sure on kernels, haven't messed with them on Xiaomi devices.
Sent from my MI 5 using Tapatalk
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
the_poolee said:
Did anyone try this patch on MIUI?
Edit: Just tried on MIUI v7.2.9 Global Dev. CTS profile and Basic Integrity check both fails.... What a bummer...
Click to expand...
Click to collapse
Drats. If basic integrity is failing that's something else triggering the issue. Before I changed the fingerprint I only had cts failing, basic was usually fine. Sometimes a replacement kernel would cause it to fail basic, but I never narrowed down exactly what the cause was.
Works on LOS. Anyway my bank doesn't support android pay yet.
Ulver said:
It does make it easy. I initially unlocked my bootloader to flash the global stable, then used mi flash to flash the ROM and relock my bootloader. I wasn't happy with the stable ROM, so I went back into the mi unlock tool, unlocked again, and flashed the dev ROM and relocked Then I see 8.2 is coming soon, so I went back to mi unlock and unlocked yet again so I can flash the new 8.2 when it comes out.
Click to expand...
Click to collapse
Looked into it some more to confirm - I'm quite sure you can't re-lock the bootloader if using anything that's not an official xiaomi rom, ie if using lineage, or even the xiaomi.eu rom, you can't lock bootloader without having a bootloop.
And yeah, I've confimed this method doesn't work on xiaomi.eu rom 7.1.20 or 7.2.16 on mi5. It gets both failed basic integritry and failed cts profile match.
I've also tried on Global Stable 8.1.4.0 with unlocked bootloader and had no luck at all, same error.
This was a clean install, factory wipe, install magisk v11.1. Initially the check couldn't work at all, I had to get google play services updated for anything to work. Then the check operates, but fails on both counts.
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Ulver said:
I passed safety net on 8.1.2.0 global stable, but failed to add a card in Android Pay. I'm hoping 8.2 works.
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
As described by @Ulver if you're on official builds, you should be able to re-lock the bootloader and avoid this issue (although without root I guess).
Aside from that, you definitely shouldn't need the zip I made for the build prop change, as you'll already have a stable build fingerprint
It turns out there's lots of versions of official rom that don't pass safetynet even when cleanly flashed with locked bootloader - xiaomi themselves keep breaking it!
A little search finds lots of references, such as this entire thread, and this post in particular: http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=273319&pid=7515203
This certainly complicates things....
Turns out you can't always re-unlock....
To test more thoroughly I decided to flashtool wipe and lock my mi5 to stable release that's reported to pass safetynet; global_images_V8.0.2.0.MAAMIDG
My plan is to verify that it passed when locked (it did), then unlock and just install magisk to see if that worked to hide.
Well, MiUnlock has told me I can't unlock, I logged back into unlock web site and it now says my unlock request is rejected (on same account as I originally unlocked on). So now I have a locked device on global stable and have to wait for re-application to unlock.
FWIW I then allowed MIUI to OTA update itself to 8.1.2.0(MAAMIDI) and then safetynet helper originally told me no, fail on both basic and cts.
Ran it a couple more times though and now it's passing. go figure... safetynet is somewhat unreliable.
tl;dr don't re-lock your phone assuming you'll be able to immediately re-unlock it, it clearly works some of the time, not always though.
Good news, I've got SafetyNet pass on xiaomi.eu (MIUI) rom with unlocked bootloader
In the end it's basically the same as the original LOS method except that as we've all seen earlier Magisk v11.1 isn't working for MIUI.
This win was achieved with Magisk v9 and phh-superuser-magisk-r266-2 with the current Magisk Manager (4.2.6)
As per the screenshot I'm running xiaomi.eu MUIU 8.3 7.2.24 in Mi5
My procedure was:
* dirty flash rom to clean up prior attempts (Install) xiaomi.eu_multi_MI5_7.2.24_v8-7.0.zip
* Install gemini-safetynetpass-stable-fingerprint-20170217.zip
* Install Magisk-v9.zip
* Install phh-superuser-magisk-r266-2.zip
* Reboot.
Simple as that, Magisk Manager shows SafetyNet passing (after asking for root privs on first launch)
I've added a new card in Android Pay, haven't tested at a terminal yet though.
If anyone's interested I previously got SafetyNet passing on MIUI with a custom kernel instead of Magisk, this gave SafetyNet green without any kind of root.
The problem with custom kernel's at this stage is the capacitive buttons (back and app switch) have reduced sensitivity / only work well when the phone is charging. AFAIK this is only really a problem on phones with LGD lcd's (what I have), the other ones might work fine.
If anyone wants to try my kernel instead let me know and I'll share it, I found it to be a bit flaky though.
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
rafix96 said:
@up:
For me not working.. SafetyNet test always have CTS false.. I tried clean install and for now it's not works.
Click to expand...
Click to collapse
Which version of which rom did you try?
coronafire said:
Which version of which rom did you try?
Click to expand...
Click to collapse
I would definitely would like to confirm this on the latest miui official global dev
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
rafix96 said:
First i try this on 7.2.24 xiaomi.eu later i updated MIUI to 7.2.3 and unfortunately it does not working too...
Click to expand...
Click to collapse
That's annoying, 7.2.24 is what works for me. It's been my daily driver since, and I've used android pay at a terminal no worries.
Do you definitely have Magisk v9 and phh-superuser-magisk-r266-2.zip ?
Magisk v11 cannot be installed else a dirty flash will be needed.
Oh, I just remembered I've also installed the 'phh's SuperUser' app from Play Store. This is probably needed
After that I opened Magisk Manager, which asked for root permissions the first time (which has to be granted).
@coronafire
Yes i tried everything but i have another one idea, when i come back to home i did MiFlash and then install eu 7.2.24 maybe will work.
Wysłane z mojego MI 5 przy użyciu Tapatalka
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
hklam0 said:
basically, if you don't need root, just flash
the latest zip in the following link (by kyasu)
https://www.androidfilehost.com/?w=files&flid=149919
will pass safetynet without locked bootloader. As they latest kernel is 2 weeks old, please consider there may be some drawback in flashing an old kernel to latest LOS build. By the way, would kyasu please update the file or let us know is there is any easy way to patch on our own?
Click to expand...
Click to collapse
Just to note, this is only for LineageOS, not MIUI.
Personally I find it easier to not need to replace the kernel and just install magisk, if root isn't wanted it can be disabled in the magisk app.
But yes it's true you can replace the kernel with a patched one, avoiding installing any kind of root.
I've experimented with this quite a bit myself, however to update it requires at a minimum applying a patch/commit to a fork of the kernel source you're starting with and compiling it.
I've got a fork of the MIUI kernel from @Shaky156 with the appropriate patch:
https://github.com/andrewleech/Mi5-...mmit/66cbe734eb15d2508a5c80157a8af38d59373535
and example build script:
https://github.com/andrewleech/Mi5-MIUI8-Nougat-Kernel/blob/master/build.sh
Or there's the original patch by @Sultanxda which usually works as well, I did test this on a LineageOS kernel but this is pretty out of date too by now, and I started from a different forked kernel anyway.
https://github.com/andrewleech/andr...mmit/f8314c10146971979ad26c881be9bd17603c1e7d
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
lixoman100 said:
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
Click to expand...
Click to collapse
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Rowdyy Ronnie said:
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Click to expand...
Click to collapse
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
lixoman100 said:
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
Click to expand...
Click to collapse
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Rowdyy Ronnie said:
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Click to expand...
Click to collapse
Thank you again for all the information :good:
Have a nice day.
I have my poco since january, but i am with BL locked until today, so i was always just reading the forums out here, but without do nothing on my device.
Today, i'm so tired of official stock that I'm going to EU stable rom. I don't want root, i don't want custom roms, nothing, just the eu rom. I used to use xiaomi.eu on my old phone.
But it seems that is more complicated to do things on poco f1, so that's my question : What i have to do exactly?
I have already the permission to unlock BL because of my old device, so i skipped this step of the website, because i use the same account. Then I activated everything i have to activate on developer options, i've sync my mi account to the BL unlock also, and downloaded everything (by everything i mean just the unlock tool, twrp from twrp.me and xiaomi.eu stable version 10.3.6) and I'm doing some backups right now, on google, mi account and local files on notebook.
After the backup, i plan to just unlock, go to bootloader, flash twrp, boot twrp, do nandroid and after the nandroid install xiaomi.eu already and boot my device.
I'm missing something or this is just all the steps?
I see that to install custom roms people flash two things more, the vendors and something called DFE,things that i never done before on custom roms world.
Is this necessary to install just the xiaomi.eu? I'm confused at this part, specially with this DFE. What these two files do to my device exactly? What happens if I flash them before install the rom, and what happens if i don't?
I know that this probably was asked before hundred times, but i'm kinda confused since i'm not doing those things in my devices since a long time ago, so sorry to ask one more time on XDA.
I hope you can help me explaining those things.
Already grateful
Cheers!
Hi, I just changed the battery on my H930 (Italy) and it's back to life. I kindly wanted to know, starting from the already unlocked Bootloader and from an LG Pie, if there is a custom rom, even if not very recent, without any bugs, which retains all the main functions (in particular Hi-Fi DAC, NFC, photos, Wi-Fi, bluetooth ,etc). Furthermore, I would need to use payments with Google Pay and therefore bypass the related checks. If someone can give me a hand of help ... eternal gratitude!
Stock Pie ROMs have been known to be poorly setup by LG. Since they have discontinued their development, these will not be fixed.
In the USA, custom ROMs don't work with VOLTE or VOWIFI... which is why I always recommend stock for USA phones to retain this capability. I don't know if Italy/Europe has any of these issues.
For these reasons, I have always recommended stock Oreo ROMs here in the USA, as these were the most stable and worked well. I have since left my V30 phone but it still has Oreo on it (and still works). For US users, I often recommend US998 ROMs as these work for most carriers (including international). So I might suggest that one to start.
As for GPay, they have gotten quite advanced with root detection. I would recommend skipping root if you can, of course. If you cannot, then I did use Magisk Hide in the past and it worked for me, but that was a few years ago, so I don't know if that works anymore. I would advise NOT using Xposed, as this was being detected as well... besides which Xposed was causing problems anyway, so I found it was not worth the hassle.
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Yes, just unlocking the bootloader can be part of the detection, even if it's not rooted. You often have to go the next step to root and then use Magisk Hide to make it "safe" from there.
Note, at least on older versions, you had to start with the TWRP install of an older version of Magisk. Once installed, then you can update it (usually) without much problem. I recall doing that myself. I believe the TWRP install required Magisk 18.x, and then I had updated to 20.x. You can check the WTF thread to see what that requires, as those instructions should still be valid.
Another option is relocking the BL, of course.
Also note, I know that at one time I had seen where once you fail the security check, you had to clear data for Google Services or something, and maybe even GPay. Otherwise, it "remembered" that you had failed, and would not recheck. By deleting data, it would force it to recheck, so you may need to do this after doing Magisk Hide. Note that you ay need to hide services as well. Again, I'm saying this based on older info... I don't know if things have changed since then.
clalos33 said:
I thank you for the valuable suggestions, I guess I will keep it a few more years with Pie and with Magisk Hide I will try to remove the root. Actually I don't remember rooting it. Is it possible that "security reasons" that don't allow me to load cards depend on unlocking the bootloader?
Click to expand...
Click to collapse
Yes, unlocking the bootloader will cause the security check to fail because you've broken the front door down. You can now do other things like root and make changes to your phone. They know this, so the assumption is if you unlocked the bootloader you are now attempting to take control of your own phone, and they don't want that.
Thank you again for your helpful suggestions. In consideration that I do not plan to use custom rom I will try to lock the Bootloader