Huawei Mate 20 Lite - Broken SafetyNet - Huawei Mate 20 Lite Questions & Answers

Hey,
Well, I'm after a failed attempt to root the phone.
I used Miracle Box to root my phone but in Fastboot mode it still says that the phone is Locked - but many applications built into the phone shows me the dialog box that the phone is rooted, the same shows me the Magisk app (SafetyNet test failed) and I read that it could be by some overwritten system files etc. And the question - how can I now return to the initial state? Need to reinstall system? If so, how?
Huawei Mate 20 Lite
Hisilicon Kirin 710
Android 10.0.0.286 (C432E12R1P1)

If SafetyNet attestation fails then either phone's Android got rooted or phone's bootloader got unlocked.

jwoegerbauer said:
If SafetyNet attestation fails then either phone's Android got rooted or phone's bootloader got unlocked.
Click to expand...
Click to collapse
How is this possible when Fastboot says "PHONE Locked"?
It's not my photo but it looks same on my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then what do I have to do to cheat this SafetyNet? I know I can do something like that with Magisk but for this I need TWRP which I do not have ...
Btw. To do this root I had to roll back Android 10 to Android 9 (If I remember well) and when I thought root failed I went back to Android 10 (i do that with HiSuite - I don't know if it matters)
Edit: to unlock phone in Miracle Box I went to the "Android" tab and clicked the "Unlock Bootloader" button then after a few seconds the phone reset from Fastboot back to Android (no wipe data - and as far as I know, unlocking the Bootloader involves deleting the data) And in the Miracle Box it was written that the operation was completed successfully.

Fastboot is integral part of Android OS: hence I would trust at 100% in it, and not in any 3rd-part app.

jwoegerbauer said:
Fastboot is integral part of Android OS: hence I would trust at 100% in it, and not in any 3rd-part app.
Click to expand...
Click to collapse
Okey, but:
- system apps (i mean from Huawei) shows me dialog box with text that my phone is rooted
- I can't pay with my phone (in store etc. with NFC) and banking apps shows me errors that my phone is rooted or modified (including GooglePay (i can't add my credit card because i get error that my phone is rooted))
- I can't download Netflix/Update Google Chrome from Google Play (This is the only apps I can't download so far)
And the best: It all worked before I tried to root the phone!
This is a screenshot of the game center app from Huawei (The text in English reads "Your phone is rooted. Continued use of the Game Center app may compromise security")
Magisk SafetyNet Test (big text means "Invalid certificate"):
Edit:
Yee, so it's strange - but someone wrote to me that there may be overwritten certificates, flags, etc. And because of all this it fcked up my phone and the Bootloader, Phone can still be locked
And I do not know what now - Flash ROM? Can I do so on a nonrooted phone?

You confuse things:
Whether an Android is rooted or not doesn't depend on whether a phone's bootloader is unlocked or not.
Android OS is rooted when SU-binary is present and accessible. And this easily can get detected by apps.
My recommendation:
To get rid off of the issue you have re-flash phone's Stock ROM.

jwoegerbauer said:
You confuse things:
Whether an Android is rooted or not doesn't depend on whether a phone's bootloader is unlocked or not.
Android OS is rooted when SU-binary is present and accessible. And this easily can get detected by apps.
My recommendation:
To get rid off of the issue you have re-flash phone's Stock ROM.
Click to expand...
Click to collapse
Yep, but only I have a problem with finding the ROM preferably in this version of what I have now (the latest) or somewhere around 10.0.0.286 (C432E12R1P1) for SNE-LX1 can You or someone help me with that?

Related

Android Pay - MIUI 8.2.3.0 (MAHCNDL) | Chinese Stable ROM

Seems like Android Pay does not recognise the latest system update as an official ROM, after installing Android pay and giving all the permissions:
Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards.
Click to expand...
Click to collapse
I inadvertently ran this update after purchasing the phone 2 days ago, didn't unlock the bootloader (though applied for it) and of course, haven't rooted.
I factory reset twice and still got the same. Looking forward to unlocking the bootloader so I can downgrade to the older ROM or even go on the global one (since I saw in another thread Android Pay's working on the latest global ROM V8.2.1.0.MAHMIDL, and the latest downloadable Chinese stable Rom V8.2.2.0.MAHCNDL)
Anyone updated and experience the same issue? And as I'm a newb in all of this, must I unlock the bootloader in order to downgrade?
Tried to get it to work, this time through using recovery flash (without need to unlock the bootloader and what not). Here's how I finally got Android Pay to work, and also got myself on Global Rom (lovin' it)
Prerequisite: Download the latest stable ROM file here to PC
1. Download the Chinese version of the Xiaomi Mi PC Suite and run it
2. Plug in your phone to PC and boot into recovery mode (push both volume up button + power button together until your phone reboots)
3. Allow driver to install, if you're in recovery mode, a prompt will come up. If not don't panic, read step 4. Otherwise go to Step 5.
4. If the PC Suite does nothing even if you push the big orange button on the right to connect (apparently they haven't upgraded the software to support Android 6.0 yet -_-"), click this button show below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and select the button with the words "Recovery" in it, it will prompt you to reboot your phone into recovery mode (push both volume up button + power button together until your phone reboots).
5. Select the ROM you pre-downloaded on your PC and let it run.
6. The PC Suite will look like it hits some error and on desktop the progress remains at 0% but somehow things are churning on your phone as you can see "MIUI update" and a progress bar below.
7. Let it run its course and allow the phone to reboot
8. Voilà, your phone is now in Global ROM
And Android Pay now works, hoorah!!!
Great guide, thanks a lot! I've got the sister phone to this one, the Xiaomi Mi Note 2... and my Android pay was not working with 8.3.2 global.. But now it is.. I will post a guide elsewhere as to how I had to fix it...
THIS is a DANGEROUS post, it may work - or like in my case it will start for just a moment then stop [causing a factory reset to occur] without updating. Make sure you have your mi account login and pass ready when it comes back up - or your locked out of the device setup.
Due to frustration caused by trying this post I ended up unlocking / rooting the device. It was easier than I thought it would be, flashed global fine from there and updated to 8.2.4.0 just fine OTA. Have gone on too work on other things I had decided not to due because I hadn't decided to root the device. So I guess there was a silver lining to this.

Lastest Version of Nougat For EVA-L09 UK Version

Until i looked on here today I wasnt aware there was actually an update for the huawei p9 as i the phones 'Check up update' would always tell me there was no new version. I have the P9 EVA-L09 UK version and am currently on EMUI Ver 4.1.1 and Android version 6.0. What is the latest update i can install on this phone please and will i lose all the data on my phone?
Depends on your build number. If it's C432 you should be able to update to Nougat. If not you will need to follow the debrand guide found on this forum.
My build number is EVA-L09C432B182, which is the correct version right? I just tried updating to B386 from this guide here...
http://www.stechguide.com/download-huawei-p9-b386-nougat-update/
but i get an error message saying that the update.app is the wrong version, do i need an early version of the Nougat FW??
It's a minefield. Some work some don't. I'd try an earlier build b360 or b361 maybe. You could also try using the Huawei updater guides are on here.
hmm tried version B360 and it gets to about 39% installer and then gives me a 'Software Install Failed' message. Do i need an even older version of the Nougat FW?
That's the oldest as far as I know. Did you try with 3 button or hidden update menu method.
nah i used the phone keypad code method. I have just unlocked my bootloader and installed TWRP, can i update it via TWRP safely?
Hmm well ive updated to Nougat but something doesnt seem to be right alot of the programs are missing and now im unable to get TWRP to load and just seems to load Huawei eRecovery when i press the volume up and power button on turn the system on. How do i got about getting the phone back to stock (bootloader relocked, un rooted, twrp uninstalled and back on Android Marshmellow 6.0)?? so i can start again?
Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.
wards5150 said:
Look for the b136 rom. I believe that fixes a lot of issues for people. Most of this is on the debrand guide. Have a good read of that thread.
Click to expand...
Click to collapse
Ok thanks i just posted a new thread as i now seem to be stuck on a 'this system is rebooting' screen (the warning screen you get that tles you the phone is unlocked) and the phone never actually boots anymore. Will me force flashing (Volume Up+Down+Power button) the b136 rom get me out of this predicament?
I've not had to do it myself but I have read that others have. Good luck. Shouldn't be this hard to update.
Hmm i dont even seem to be able to get the phone into the force update process (Volume UP+DOWN+Power) just hangs on the Huawei logo screen
Hmm i think the phone is bricked, im unable to get into the menu to update the Update.app file from the dload folder on the SD card, i cant even get the phone to switch off it just keeps restarting itself and freezing on the 'your device has been unlocked and cant be trusted' screen....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if i try and turn the phone of it just turns itself back on and freezes on that screen again
Im able to get to the Fastboot & recovery mode screen if i hold volume down button.......
and if i hold down both the volume and power buttons i get this screen....
and not the firmware update screen i should be getting.
It has been suggested that i need to use DC Phoenix program to fix the phone but thats a paid method and dont really want to go that route if there is another way!??
Sorry to hear that mate. Good luck fixing it. It should not be this hard to update. For some it's easy for others it's a right pain. I'm sure there will be a way to sort it the hard bit will be finding it.

Le S3 x626 bricked issue

Hi, I have checked this thread as I experienced the same issue(If confused what I'm talking about read
www chinaphonearena com/forum/Thread-Question-LeEco-Le-S3-X626-Helio-X20-Bricked ), I was able to get past the phone buttons not working and was able to flash a new firmware. But this led to another issue considering the system.
For one, I am unable to unlock my bootloader, I just receive the error : FAILED (remote: unlock operation is not allowed), and there is no way fro me to get in my android as it always stays on the LeEco POWERED BY ANDROID screen, which then shuts down and reboots.#
As well as this, the display is now very unusual: the LeEco logo is coloured green white and yellow, the display is flipped horizontally and mirrored vertically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The image above shows this.
It's VERY annoying and I hope it can be solved.
NOTE!! I can still use locked bootloader/fastboot, can't use adb and can use SP FLASH TOOL
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
damtrx_ said:
You need to power the phone and wait till boots. Enter the flipped UI enable developer mode and unlock the bootloader.
All the control are flipped so be patient.
After that enter fastboot and flash the original rom
Click to expand...
Click to collapse
Thanks for the reply, I fixed the issue the same day, I just fixed it using the second part to tickernel's red light unbrick tutorial, I completely missed it out. The rom I was using where everything was inverted was just to unbrick the phone, then after I'd have to flash the rom provided by tickernel to fix. It worked again and an advantage was that there was no more ORANGE state, I didn't have to patch to hide the message nor wait the 5 seconds, so now I can flash custom roms on my phone without the message. The method you provided wasn't the fix, before opening this thread I double checked and saw your method, but thanks anyway .
it was necessary to use a mirror. for example, in the bathroom
after brick and ressurect what write in (telephone settings) model?
Shekor said:
after brick and ressurect what write in (telephone settings) model?
Click to expand...
Click to collapse
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Kychera22 said:
it depends on which model is taken ROM. It does not play any role. Can be changed to Build.prop
Click to expand...
Click to collapse
after bad ressurects i return my device le x626. to le x620 with eui 5.8.018S (stab.) it works normal. But was some bugs with 4g on (turn phone off) and google programs don's start.
But i fixed it all, now it works great, but i think is it bad?
take the stock firmware 28. and install. why use the old version? maybe get my firmware.
to use google apps. you need to download google installer, then after installation, in the settings give permissions to all Google apps.
and correctly to do so: to install firmware, then to start system and to configure it. and then only install the google gapps.
Update on unbrick
With my phone unbricked, it now works perfectly. But now the battery drains very fast. It drops by around 25% in less than half an hour with normal use such as watching videos on youtube in "360p" with all my apps closed, but still the battery drains. I have tried flashing different roms and clearing all partitions in twrp and flashing the CUOCO AND WOLFRED x.28s custom stock roms, but still the issue persists. This is very unusual as before my phone bricked, the battery would hold up for at least an hour before falling by 10 to 20 %. Does anyone have any speculations on why or any fixes? Please help.
UPDATE: I fixed by flashing the international version system.img only if you need it send me a message and I'll put up a link.

“Kernel is not SEAndroid Enforcing” and “Custom binary blocked by FRP lock,".....Help!

Hey folks!
The phone fell a few times and now i'm getting a white screen that comes on every now and then with the message in red
“Kernel is not SEAndroid Enforcing” and “Custom binary blocked by FRP lock,”
I honestly have no idea on what to do.
Phone kind of important to me so I'm trying to preserve it,
Anyway I can get it going again without wiping everything on it ? Or is there anyway the data could be retrieved ?
Thank You!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This button was pressed to try and install idk maybe a custom recovery or a new rom, without having permission to do so, this is inherited from a google account being on the phone... either that or if you already were custom, this button was pressed to turn it off and now you get blocked from using custom code, unlock the bootloader and get rid of the frp lock and you are good, i will not help you with this procedure as it can be considered piracy and we dont do that here sorry for the wierd screenshot, it was a google result
efinityy said:
View attachment 5240391
This button was pressed to try and install idk maybe a custom recovery or a new rom, without having permission to do so, this is inherited from a google account being on the phone... either that or if you already were custom, this button was pressed to turn it off and now you get blocked from using custom code, unlock the bootloader and get rid of the frp lock and you are good, i will not help you with this procedure as it can be considered piracy and we dont do that here sorry for the wierd screenshot, it was a google result
Click to expand...
Click to collapse
I wish it where actually all that but the phone dropped to the ground. I got a screen replacement and when I tried to turn it on its been in this constant boot loop of that error message and nothing more.
I never tried to install any rom's. I'm not seeing how I would be able to out the boot loader if all it will do is constantly reset ?
Palms:09 said:
I wish it where actually all that but the phone dropped to the ground. I got a screen replacement and when I tried to turn it on its been in this constant boot loop of that error message and nothing more.
I never tried to install any rom's. I'm not seeing how I would be able to out the boot loader if all it will do is constantly reset ?
Click to expand...
Click to collapse
It's resetting because it's denying the signature on the binary of the installed firmware, that basically means a "read only" part of the phone, has been tampered with, and the "selinux not enforcing" part indicates this because many custom roms and kernels have an selinux non enforcing kernel.. and then on to frp lock, frp is Factory Reset Protection, which has been tripped, somehow, I can't say, but most oftenly this combination I've only seen on samsung's when you have unlocked the bootloader, this you need to do in order to tamper with these files, installed like rom/kernel/root, whatever the change might be, then somehow unticked the "allow OEM-Unlock" so the bootloader that is now unlocked is not allowed to be unlocked by the system itself, creating a break in the chain of trust between start and standby, and which makes you stuck in a wierd loop like this, if someone else replaced the screen for you I should really, really go talk to them. If you are the rightful owner of this phone and have no idea of anything about what I've talked about just now is and never did any of this before, someone did, and you should confront them. But I believe it's against the rules to assist with such things here and thus cannot help you any further in the matter

Question Cannot update - 3 dots missing

Hi All,
I have a Note 10 5G 4+128. It was originally on vodafone firmware and I unlocked the bootloader and installed EEA 12.0.8.0 Stable. I shortly after received an OTA update to 12.0.9.0 (RKSEUXM) so assumed everything was all good.
I have not received the 12.0.10.0 update yet and the three dots are missing on the update page for me to do it manually. If I reboot the phone and go immediately to the update page the three dots are there for a split second then disappear.
The only thing I can think that has caused this is I have removed something I thought was bloatware using the XIAOMI ADB fasttools java app on windows. I have tried reinstalling pretty much all of the "bloatware" but it does not fix the issue.
A few threads on similar things for different devices have popped up on reddit and people say to clear the data and cache from the system updater app. However I do not appear to have that app and its not in the list of things ive previously uninstalled as "bloatware". My system apps updater still works fine and reguarly updates other system apps.
Any ideas?
tap 10 time on miui logo. you will see advanced options
Thanks for your response.
I have tried this. It states the advanced options are active. My problem is that the 3 dots themselves which gives access to the update settings, which should be shown even when advanced options are off, is completely missing.
If I restart the phone and go into the update page the dots show for a split second then disappear. It almost feels like an app is crashing in the background or something.
Please see attaches screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mmm... you can try update manually with miflash tools. you know how to do?
I know how to use the miflash tools, however I believe the bootloader needs to be unlocked to use them. I have already relocked the bootloader so would need to wait a week to unlock it again, plus that would mean wiping the user storage on the device which is rather not do.
Surely there must be something else im missing here? Other people online have stated to clear the data and cache from the Updater app on other MIUI devices, however I see no way to do that.
AnUrbanPenguin said:
I know how to use the miflash tools, however I believe the bootloader needs to be unlocked to use them. I have already relocked the bootloader so would need to wait a week to unlock it again, plus that would mean wiping the user storage on the device which is rather not do.
Surely there must be something else im missing here? Other people online have stated to clear the data and cache from the Updater app on other MIUI devices, however I see no way to do that.
Click to expand...
Click to collapse
online i have found a tool very helpfull. i have remove the brand from my phone with bootloader locked. now i have the latest eu version. you can try it to update your firmware. search xiaomitool v2 by Francesco Tescari. another helpfull tool i found is xiaomiadbfastboottools.jar
The adb fastboot tools are the ones ive used to remove the bloatware on this and other phones in the past. It is excellent.
The Xiaomitool v2 is also great.
However I still feel like I am missing something. I should not have to unlock my bootloader and wipe my device every time there is an incremental MIUI update. There must be something I am missing here that is causing me not to get the OTA update or have the ability to manually update.
AnUrbanPenguin said:
The adb fastboot tools are the ones ive used to remove the bloatware on this and other phones in the past. It is excellent.
The Xiaomitool v2 is also great.
However I still feel like I am missing something. I should not have to unlock my bootloader and wipe my device every time there is an incremental MIUI update. There must be something I am missing here that is causing me not to get the OTA update or have the ability to manually update.
Click to expand...
Click to collapse
mmmm.... my advice is a clean installation of stock firmware. and the best way to do this is via miflash with bootloader unlocked. i'm not sure but i think something goes wrong during an ota update. so a sytem wipe is necessary. you could try reflash your current stock firmware via Xiaomi tool v2. i have used it to remove my brand without unlock and works fine. but if this don't solve your problem i think the only solution is a new clean installation
For mi 11 lite 5G: Go to "Settings/Apps/Manage apps" and search for app "Updater" then click on it and clear all data and cache.
Duddly said:
For mi 11 lite 5G: Go to "Settings/Apps/Manage apps" and search for app "Updater" then click on it and clear all data and cache.
Click to expand...
Click to collapse
Thank you! This really helped

Categories

Resources