Related
From Endgadget: https://www.engadget.com/2018/03/26/google-starts-blocking-its-apps-on-uncertified-android-devices/
If you're fond of loading custom ROMs on your Android phone, life just became complicated. Google has quietly started blocking access to its apps on uncertified devices whose firmware was built after March 16th. If you're affected, you'll get a warning that a device is "not certified" and can't sign into a Google account. This won't prevent you from loading ROMs, but you'll have to register your device IDs on a white list every time you undergo a factory reset -- when there's a 100-ID limit, you could run into problems if you're routinely wiping your phone to install new firmware.
We've asked Google for comment on the move.
The company is already quite clear about the rationale, however. Vendors officially need to get certification to load Google apps (Android's licensing model is built around this), but some of them ignore this requirement and either load the apps regardless or encourage you to download them yourself. This new block theoretically pushes those less-than-scrupulous brands to clean up their acts by either obtaining certification or sticking to an AOSP version of Android, where they'd depend on third-party apps.
The problem, of course, is that it leaves custom ROM users caught in the crossfire. They may have to be more selective about when they install ROMs and skip minor updates. It's far from the end of custom firmware, but the era of anything-goes firmware (on phones that allowed custom ROMs in the first place, that is) might be winding down.
I was just posting a thread about this aswell. My thoughts are more focused around the app store. How will we access the app store? Are we able to hack / "pirate" the app store apk or is the mod community going to have to start a separate app store? Maybe even twrp install every app we use?
Stop using wonky ass roms, if your rom passes safetynet and certifies your device, you won't need to do this. DU has been passing as certified for like a week now, even before the issue was made public. I made 2 clean flashes yesterday and haven't faced the issue. SO if rom devs fix their stuff, there won't be any need for IMEI or androidID registration.
As you can see my OnePlus 5 is listed as uncertified and I'm on stock OpenBeta 7 with no root or any other mod. Only my bootloader is unlocked that's it. BTW I flash the OpenBeta 7 clean with a erase everything and setup the phone without any issues :good:
Sent from my OnePlus 5 using XDA Labs
Is the certification check is going to be based on Bootloader lock status or ROMs????
I am confused.....
smohanv said:
Is the certification check is going to be based on Bootloader lock status or ROMs????
I am confused.....
Click to expand...
Click to collapse
If I remember me right I look at that before I unlock my bootloader and it shows me certified after the unlock it shows me uncertified, to me it seems it is based on a locked or unlocked bootloader, but I can be wrong this have to answer the gurus here :good:
Sent from my OnePlus 5 using XDA Labs
GraveDigger176 said:
If I remember me right I look at that before I unlock my bootloader and it shows me certified after the unlock it shows me uncertified, to me it seems it is based on a locked or unlocked bootloader, but I can be wrong this have to answer the gurus here :good:
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
mmmm....... so, if this is the case rooting is going to a an issue... until an exploit is found we may have to lock bootloader back and stay without rooting for a while.
Let us wait for more knowledge coming on this subject before we think of any action... at the moment my device is rooted and also I am running crDroid (Oreo 8.1) and also using magisk with Safety Net passed so that I am able to use Google Pay.
GraveDigger176 said:
As you can see my OnePlus 5 is listed as uncertified and I'm on stock OpenBeta 7 with no root or any other mod. Only my bootloader is unlocked that's it. BTW I flash the OpenBeta 7 clean with a erase everything and setup the phone without any issues :good:
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
I clean flashed OB7 on my OnePlus 5, my bootloader is set back to locked as well and my device says certified.
Maybe it's because of the unlocked bootloader that you see uncertified?
dazr87 said:
I clean flashed OB7 on my OnePlus 5, my bootloader is set back to locked as well and my device says certified.
Maybe it's because of the unlocked bootloader that you see uncertified?
Click to expand...
Click to collapse
Yeah it seems so, but i have clean flash OpenBeta 7 with erase everything and unlocked bootloader and setup the Phone without any problems, I let it as it is now until i got problems with signing in google account after a clean flash :good:
I think certified or uncertified it depends on your rom, because my device still showed me certified status, with unlocked bootloader rooted with magisk, yes it's strange but somehow I'll look after it since I'm still waiting the open beta release to stable
Ps: sorry I can't upload screenshot because my xda app keeps saying bad request
sendashano said:
I think certified or uncertified it depends on your rom, because my device still showed me certified status, with unlocked bootloader rooted with magisk, yes it's strange but somehow I'll look after it since I'm still waiting the open beta release to stable
Ps: sorry I can't upload screenshot because my xda app keeps saying bad request
Click to expand...
Click to collapse
Well then is stock OpenBeta 7 crap :laugh:
BTW then all OOS stock roms crap since I unlock the bootloader it shows me uncertified :good:
Sent from my OnePlus 5 using XDA Labs
My OP5 is running stock OB 7, with an unlocked boot loader. I'm not rooted. When I got mine used off of Swappa, I made sure to unlock the bl and then flashed the OB 5 fw. Since then I've taken the OTA's for OB 6 and 7. No issues and my device is certified in the Play Store.
Mine is stock ROM Nougat 7.1 with unlocked bootloader and root and my device is uncertified.
AEX-Rom Oreo, decrypted, rooted with Magisk shows certified.
This is no problem with stock/nonstock/root etc.
Maybe Magisk helps to be certified
Google says that will not uncertified the custom roms
I'm on ob7 unlocked bootloader with magisk installed and shows me certified
OOS 5.04, unlocked bootloader, magisk 16.0 - uncertified!!
I'm on xXx NoLimits 10.1 Stable 5.04 and rooted (Magisk 16.3) with an unlocked bootloader. No problems here.
It ws esy unlocking the bl in g5s+ , what about the z3 play, wife surprised me with this phone, im liking it already, but would like to unlock the bl and eve tually gain root/custom recovery ?
Anyone?
Depends on the model you have specifically, certain ones cant be unlocked such as amazon version. But the steps are the same as all other android phone bootloader unlocks, Steps can be found on motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
The basics consist of:
enable developer mode
enable "OEM Unlock" in developer settings
fastboot into phones bootloader and run OEM unlock commands
copy unlock code from phone that you get using oem unlocking commands into motorola website
receive email from motorola with unlock "password"
enter password into adb terminal
phone will be wiped and bootloader unlocked
Thats what i thought, i went there just to see , looks the same as for my G5S+ , ill likely do this. Is there guide somewhere on instally magisk as im outdated ( an old chainfire guy) just need some hints , doesnt look like twrp works , what about clockwork mod? Thats fine as well, , any good roms? Think 9 is comming?
Magisk root is straight forward. You can either get a working boot.img for your device from a firmware package and patch/flash it yourself. Or boot NOT flash the twrp images from the twrp website and install the magisk zip that way. The twrp for this device hasn't been compiled for flashing. It boots but flashing it to your device will boot loop it. No custom ROMs that I know of but I'm just using stock with magisk and it's fine once you have root to delete the bloat ware apps and install tweaks from magisk.
I happened to see a mate 40 pro device which is a global version but had its bootloader unlocked. Will it remain secure and operate as mentioned by the company or does it have any negatives.
Anything with an unlocked bootloader has less security compared to a device with a locked bootloader. If you plan to do confidential things with your device with an unlocked bootloader, some services will not let you use them due to an unauthorized modification of the device. An example would be applications that rely on safetynet or have services that detect an unlocked bootloader, root, and/or custom recovery. Other than that, the device should work and operate normally under any other circumstance. If you wish to get an pre-unlocked bootloader device, i recommend you to flash magisk, as that will hide root, and the unlocked bootloader status on the device so you can still do your every day things without booting you out due to an unlocked bootloader.
Thanks for your suggestions High on Linux, would help find instructions on how to flash the Magisk on Mate40 pro
Barross said:
Thanks for your suggestions High on Linux, would help find instructions on how to flash the Magisk on Mate40 pro
Click to expand...
Click to collapse
From what i have seen, there isn't an official method to flash a custom recovery or magisk yet on this device in particular. I personally don't own any huawei devices either but since this device is fairly new, you could start seeing some progress being done within the next two to three months depending if numerous developers own this phone or not.
Thank again
Barross said:
I happened to see a mate 40 pro device which is a global version but had its bootloader unlocked. Will it remain secure and operate as mentioned by the company or does it have any negatives.
Click to expand...
Click to collapse
Today rooting and android device doesn't bring any benefits.. it was used for old gen smartphones where ppl used to miss features but now you can have it without some root.. + if you have root many apps will detect it and you will encounter many many problems espec. with payment apps or bank apps etc.. making even more trouble ..
Hi all, i don't follow modding world from a while so i don't know what happened more or less into the last 3 years, so now that i need to root the device i wanted to do some questions.
I bought a realme 8 pro at the dayone and now i have the last update installed (so realme UI 4.0). I wanted to do the root but i don't know how much realme support it, if the bootloader is locked or not, ecc. ecc.
I saw in this phone thread that there is a method (the guide is written in May, 14 so it seems very recent) about unlocking bootloader (so i guess is locked?) using deeptest, i tried to read but i didn't really understand what kind of thing is that. So i wanted to ask, what is deeptest? if it is locked, if i successfuly unlock this bootloader what happens to AIO updates? (I guess there will be no updates such as other devices?). If the AIO updates stop to work, Is there a way to manually download and install updates? Can i root this device using magisk for example? I have seen there is something, but there are these things i can't understand.
Thanks in advance for replies and sorry for my bad english.
Hi, yup, the bootloader is locked.
Deeptesting is an app by realme used to request an unlock code. You can try this one https://forum.xda-developers.com/t/unlock-bootloader-help.4425415/post-86777721
Try submitting your application, if it tells you "Your model doesn't support deeptesting" you'll have to follow my guide.
Either way, after a bit of waiting, inside Deeptesting → query approve result → start Deeptesting.
Doing this allows your phone to boot into fastboot. Where you can unlock your phone using
Code:
fastboot flashing unlock
Unlocking the bootloader will wipe your data.
Hi, thanks for the reply! So there is a method to unlock the bootloader. But if i do it, i can't update anymore my device via OTA, right? How could i do that thing. In addiction, is not possible to obtain root permission without bootloader unlock? Because i need root to save whatsapp messages 'cause the application is stupid and can't do a backup by itself.
In addiction... I downloaded deeptesting and my phone does not support it. Yeah
You can get OTAs if, and only if, you didn't modify the firmware. Unlocking itself doesn't break OTAs, but rooting/custom kernels/vbmetas etc. will.
You can't get root without unlocking. As per Whatsapp, I think you can use ADB to back up data without root.
Thanks again. As i know ADB is disabled for whatsapp from a while. Ok then, thanks anyway for all informations. I guess after the bootloader unlock i can install magisk to obtain root acces.
I created this topic because I can't find a way to unlock the bootloader of my Asus Rog Phone 3. Regarding whether or not I unlocked it before, I would think not, since it was a high-end phone, when I bought it, it did not cross my mind unlock bootloader, root, install GSI roms, among others.
My Rog Phone 3 had Android 12 installed, I tried to Downgrade to Android 11, Downgrade to Android 10, and then use the Asus Original Unlock tool (using all its versions) without favorable results to unlock bootloader.
I also tried EDL Unbrick, although I don't know if there is any tool to unlock bootloader with EDL, tools, anyway, I open this question to see if there is any way today to unlock the bootloader of my Asus Rog Phone 3 (it has 12GB of RAM, It is optional, just in case.) Someone who can help me or access me, I would be very grateful, excuse my English. My goal is to unlock bootloader to root it and then install GSI roms, especially install GSI roms ..