has anyone managed to rebrand to a different version? i tried funkyhuwei and managed to get halfway thru the process, but was stuck at the firmware install thru their version of huiste and needed to unbrick it using erecovery. I was hoping to upgrade to 9.0 after rebranding.
for anyone looking to do this, i gave up on my own. i paid $30 to Ministry Of Solutions. He rebranded it to C432 i am now on emui 9.1
tensux said:
for anyone looking to do this, i gave up on my own. i paid $30 to Ministry Of Solutions. He rebranded it to C432 i am now on emui 9.1
Click to expand...
Click to collapse
After the rebranding and update to 9.1, do you have Widevine L1 for Netflix in 1080p HD or do you have L3 (SD)? I was thinking about rebranding my Mediapad M5 through the same service but if I don't keep Widevine L1 it may not be worth it
i wouldn't know how to check that. i am only getting 960x540 on all episodes of test patterns in netflix. i do get 1920x1080 on other tablets i own
tensux said:
i wouldn't know how to check that. i am only getting 960x540 on all episodes of test patterns in netflix. i do get 1920x1080 on other tablets i own
Click to expand...
Click to collapse
You can check by downloading "DRM Info" from the Play store. If you open it and look at the Widevine CDM section, you'll see what it shows for Security Level, L1 or L3
DRM Info - Apps on Google Play
Shows DRM information (Widevine, PlayReady, etc) from Android DRM Framework
play.google.com
yada-yada said:
You can check by downloading "DRM Info" from the Play store. If you open it and look at the Widevine CDM section, you'll see what it shows for Security Level, L1 or L3
DRM Info - Apps on Google Play
Shows DRM information (Widevine, PlayReady, etc) from Android DRM Framework
play.google.com
Click to expand...
Click to collapse
ok getting security level L3
tensux said:
ok getting security level L3
Click to expand...
Click to collapse
Darn ☹ thats disappointing. I would love to be on EMUI 9.1 but I don't think I can give up HD video to do it. Thanks for checking
Well, I just checked on my device (M5, 8,4", C437, stock rooted EMUI 9.1, security patch September 2020) and I do get security level L1 in Widevine CDM section
@tensux is your SafetyNet - check green?
AndDiSa said:
Well, I just checked on my device (M5, 8,4", C437, stock rooted EMUI 9.1, security patch September 2020) and I do get security level L1 in Widevine CDM section
@tensux is your SafetyNet - check green?
Click to expand...
Click to collapse
@AndDiSa Was your M5, 8,4", C437 rebranded from a different version or is it still the stock region, just rooted? The US C567 has L1 on the stock EMUI 8, so it sounds like @tensux may have lost that when he rebanded. Or would just using Magisk maybe bring it back?
It's still stock, not rebranded, but trying to root with Magisk may be a solution as Magisk is able to bring back passing SafetyNet on unlocked devices. Probably in his case it's working, too ...
AndDiSa said:
Well, I just checked on my device (M5, 8,4", C437, stock rooted EMUI 9.1, security patch September 2020) and I do get security level L1 in Widevine CDM section
@tensux is your SafetyNet - check green?
Click to expand...
Click to collapse
yes it does pass safetynet. I am not rooted. i had him rebrand from a usa version to a european one so that it could be updated to android 9
ok i rooted with magisk. still showing L3
Do you still pass SafetyNet? If yes, the only idea what comes into my mind is: rebranding is installing a new OS and all of its dependencies but leaves certificates and keys alone. In that case, the device the keys used to identify in relation to widevine are still the ones from the C567 device and so it's still identified as a L3 device ...
AndDiSa said:
Do you still pass SafetyNet? If yes, the only idea what comes into my mind is: rebranding is installing a new OS and all of its dependencies but leaves certificates and keys alone. In that case, the device the keys used to identify in relation to widevine are still the ones from the C567 device and so it's still identified as a L3 device ...
Click to expand...
Click to collapse
yes it does pass safetynet
Related
Hopefully the phones we have will survive long enough to have another update next year. https://blog.motorola.com/2018/08/15/baked-android-pie-coming-motorola/
Yey. Let's wait till end q1 of 2019 when Google starts to test Android Q for Motorola to get P ready for it's last year's phone's. Or do I have to remind you that Oreo was released end April/early May to the original Z play?
Artim_96 said:
Yey. Let's wait till end q1 of 2019 when Google starts to test Android Q for Motorola to get P ready for it's last year's phone's. Or do I have to remind you that Oreo was released end April/early May to the original Z play?
Click to expand...
Click to collapse
And it hasn't even been released in some regions ??*
OTBOPKOTO said:
Hopefully the phones we have will survive long enough to have another update next year. https://blog.motorola.com/2018/08/15/baked-android-pie-coming-motorola/
Click to expand...
Click to collapse
You might have misunderstood something.
The article says "Android Pie will be served up on the below Motorola smartphones starting this fall:"
wsemi said:
You might have misunderstood something.
The article says "Android Pie will be served up on the below Motorola smartphones starting this fall:"
Click to expand...
Click to collapse
Yes, starting with the 2018 models, or maybe only with the Z3 since it's the most expensive ones. Or do you really believe that our one year old phone will get updates that quick? They are not Pixels and knowing the update strategy of Lenovo for the past couple of years and without treble we can be lucky if we even get it this year. or have you forgotten the Oreo update? And it wasn't even to 8.1, just 8.0
I am still on 7.1.1 Nougut. According to support, I am on the latest update. But on 08/31 they claimed they are behind, but it is coming soon.
Shouldn't the all be the same regardless of software channel, build number, SKU, Version, etc.? They are all Moto Z2 Play. Mine is even unlocked so I would think that would be a benefit.
Here are the specs from the "about phone":
- Moto Z2 Play - UNLOCKED version (carrier independent)
- Software Channel = "retla"
- Build Number = NPSS26.118-19-1-16
- SKU = XT1710-06
- Version = PVT1
- Baseband version = M8953P_23.33.07.34.01RALBUS_LATAMDSDS_CUST
- Security patch = February 1, 2018
- Android 7.1.1. (Nougut)
Murf. said:
I am still on 7.1.1 Nougut. According to support, I am on the latest update. But on 08/31 they claimed they are behind, but it is coming soon.
Shouldn't the all be the same regardless of software channel, build number, SKU, Version, etc.? They are all Moto Z2 Play. Mine is even unlocked so I would think that would be a benefit.
Here are the specs from the "about phone":
- Moto Z2 Play - UNLOCKED version (carrier independent)
- Software Channel = "retla"
- Build Number = NPSS26.118-19-1-16
- SKU = XT1710-06
- Version = PVT1
- Baseband version = M8953P_23.33.07.34.01RALBUS_LATAMDSDS_CUST
- Security patch = February 1, 2018
- Android 7.1.1. (Nougut)
Click to expand...
Click to collapse
I had the update like in mid July, but it didn't take. It got all messed up and went back to 7.1.1
So I installed Oreo on the side and put Custom Rom on top of it.
Android 9 confirmed... but im still on 7.1.1... i cant understand why my phone never got Oreo
Emacordoba said:
Android 9 confirmed... but im still on 7.1.1... i cant understand why my phone never got Oreo
Click to expand...
Click to collapse
Same here. I have no idea why my phone won't update. I have it unlocked and rooted with Magisk, but won't it still detect the update and try to download it? I just need to unroot first and flash it and it should be just fine I thought. But nope, still on 7.1.1 with the February 2018 security patch. I'm on software channel retus. Right now I'm not really too concerned with getting a new version of Android on this phone since everything is stable but I'd like to know why my phone never got the 8.0/8.1 update.
Johmama said:
Same here. I have no idea why my phone won't update. I have it unlocked and rooted with Magisk, but won't it still detect the update and try to download it? I just need to unroot first and flash it and it should be just fine I thought. But nope, still on 7.1.1 with the February 2018 security patch. I'm on software channel retus. Right now I'm not really too concerned with getting a new version of Android on this phone since everything is stable but I'd like to know why my phone never got the 8.0/8.1 update.
Click to expand...
Click to collapse
i have mine without root and locked like the first day... no mods, only basic soft and games.... still on february patch
Emacordoba said:
i have mine without root and locked like the first day... no mods, only basic soft and games.... still on february patch
Click to expand...
Click to collapse
It depends on carrier. Although, if you ask them, carrier will say it depends on Moto; but truth is, it isn't. As far as I know, AT&T Latin America released (or it was Moto?) 8.0 Oreo in August, which has been already updated up to September, 2018. Next should be 9, but... Yes, 8.0 was released same time as 9 for Pixels, a full year after Z2 device landed. So, statistically, 9's OTA should be inside AT&T's Z2 devices, late in 2019. That would be another year, probably along with 10's appearance! but... Maybe not. Who knows what's in their heads. Point seems to be keeping OTA fans (don't count me in) eager as hell.
Sent from my Moto Z2 Play using XDA Labs
I've just received October's security patch
Build No. : OPSS27.76-12-25-11View attachment 4630311
Sent from my Moto Z2 Play using Tapatalk
Is pie update coming or not? Or are there a custom pie ROM available? Would you recommend flashing ROM? I mean will it reduce battery or performance? Thanks in advance.
The Android Pie 9.0 update we get for Moto Z2 Play will be still on 32bit architecture?
g0u1ham said:
The Android Pie 9.0 update we get for Moto Z2 Play will be still on 32bit architecture?
Click to expand...
Click to collapse
Yes, 100%.
Cupcake 1.5 said:
Yes, 100%.
Click to expand...
Click to collapse
So did they mean this Fall as in NOW? Coz I'm still on 8.0.0 as "latest" and seriously peeved considering these Z²s are pretty much vanilla Android to begin with
Mi A1 received Android 9 pie update and now it supports dual 4G + volte. Really shocked to see Snapdragon 625 supporting dual 4G and that too enabled with an update. And Moto doesn't even update their os to 64 bit.
signation said:
Mi A1 received Android 9 pie update and now it supports dual 4G + volte. Really shocked to see Snapdragon 625 supporting dual 4G and that too enabled with an update. And Moto doesn't even update their os to 64 bit.
Click to expand...
Click to collapse
For this device to be updated to 64bit, it would require formatting, users would lose all their stored data. How well do you think that would go over with the general public?
kewlzter said:
For this device to be updated to 64bit, it would require formatting, users would lose all their stored data. How well do you think that would go over with the general public?
Click to expand...
Click to collapse
That is a fair point. Although it's fairly easy to backup data on a phone with SD card, not everyone will like it. I had Asus zenfone 3 which came with 64bit OS despite 3GB of RAM and camera 2 API was enabled so the Gcam and hdr+ worked without root. Thought Z2 play with 4GB RAM, better camera sensor and stock Android will be even better. I was wrong.
I have the 10" Wifi M5 (Chinese version c00), and finally realized that it will never get widevine L1 so I decided to unlock the bootloader and install a custom ROm. I've tried Resurrection Remix beta 3.1 and the lastest OmniRom which should have widevine L1, but unfortunately i still can't get it.
So my next step is installing Magisk to try and see I can pass safetynet. Just wanted to know if anyone has installed it on an OpenKirin Rom before I try it?
Thanks.
ChildishGambino3005 said:
I have the 10" Wifi M5 (Chinese version c00), and finally realized that it will never get widevine L1 so I decided to unlock the bootloader and install a custom ROm. I've tried Resurrection Remix beta 3.1 and the lastest OmniRom which should have widevine L1, but unfortunately i still can't get it.
So my next step is installing Magisk to try and see I can pass safetynet. Just wanted to know if anyone has installed it on an OpenKirin Rom before I try it?
Thanks.
Click to expand...
Click to collapse
I was just realizing that actually as well, i have a Chinese one too and noticed no L1. If you didn’t have L1 on stock, then you won’t get it under OpenKirin either, as the keys need to be baked into the hardware. I think Huawei only did that or enabled those for the Euro C423 models, but not on Chinese C00.
What stock ROM version were you on when you decided to unlock the bootloader?
konradsa said:
I was just realizing that actually as well, i have a Chinese one too and noticed no L1. If you didn’t have L1 on stock, then you won’t get it under OpenKirin either, as the keys need to be baked into the hardware. I think Huawei only did that or enabled those for the Euro C423 models, but not on Chinese C00.
What stock ROM version were you on when you decided to unlock the bootloader?
Click to expand...
Click to collapse
I'm on 171. Is there a way to rebrand the m5 to another region? C423 seems to be the only good version. The US variant doesn't seem to have 5ghz wifi.
ChildishGambino3005 said:
I have the 10" Wifi M5 (Chinese version c00), and finally realized that it will never get widevine L1 so I decided to unlock the bootloader and install a custom ROm. I've tried Resurrection Remix beta 3.1 and the lastest OmniRom which should have widevine L1, but unfortunately i still can't get it.
So my next step is installing Magisk to try and see I can pass safetynet. Just wanted to know if anyone has installed it on an OpenKirin Rom before I try it?
Thanks.
Click to expand...
Click to collapse
ChildishGambino3005 said:
I'm on 171. Is there a way to rebrand the m5 to another region? C423 seems to be the only good version. The US variant doesn't seem to have 5ghz wifi.
Click to expand...
Click to collapse
Not afaik. Didn’t see any success stories of people successfully doing that.
hello,
since the Honor 9 isnt getting any security fixes anymore what can we do
about the BlueFrag security hole?
https://www.andreafortuna.org/2020/...-critical-bluetooth-vulnerability-in-android/
It seems right now the only chance would be phussons android 10 GSI
https://forum.xda-developers.com/honor-9/how-to/android-10-t3993461
since there are no Custom Android 9 or 10 ROMS with latest Google Security Fixes - correct?
If someone figures out how to bypass the bootloader that huawei put, then we can start doing this roms thing, until then, unfortunate people like me are stuck at a locked bootloader.
Well i can technically do the whole process of flashing my board again using dc unlocker and then unlocking my bootloader while I'm at it, but that's too much hassle, man, plus you need some money to spare. It's not worth it anymore unless you absolutely have to, I'm just happy with a working phone lol
thanks for answering - i'm also stuck at EMUI 9.1
and with this method?
wouldnt it be free?
https://forum.xda-developers.com/honor-9/how-to/downgrade-unbrick-honor-9-imei-fix-t3934363
then we could try some of theses ROMS out
https://openkirin.net/download/
andPS2 said:
thanks for answering - i'm also stuck at EMUI 9.1
and with this method?
wouldnt it be free?
https://forum.xda-developers.com/honor-9/how-to/downgrade-unbrick-honor-9-imei-fix-t3934363
then we could try some of theses ROMS out
https://openkirin.net/download/
Click to expand...
Click to collapse
Nope, u have to pay for it, and yeah, i'm waiting for them to find an exploit on the security that huawei put in their gpu turbo update, bec. that's the root of our problem, i heard that if you downgrade to a non-turbo firmware, it's gonna brick your device, so might as well be patient until the guys at dc phoenix figures out how to read bootloader codes on emui9.
Also I saw that openkirin has hw buttons fixed, i think it's the capacitive buttons fix that people often lose bec. of installing twrp, so i'm excited for that day that we can install openkirin roms
scarlet_venom said:
Nope, u have to pay for it, and yeah, i'm waiting for them to find an exploit on the security that huawei put in their gpu turbo update, bec. that's the root of our problem, i heard that if you downgrade to a non-turbo firmware, it's gonna brick your device, so might as well be patient until the guys at dc phoenix figures out how to read bootloader codes on emui9.
Also I saw that openkirin has hw buttons fixed, i think it's the capacitive buttons fix that people often lose bec. of installing twrp, so i'm excited for that day that we can install openkirin roms
Click to expand...
Click to collapse
to unlock bootloader, try the potatonv method. I commented it here:
Using Honor 9 after EOL / Unlock bootloader / Flash custom rom
Hi everyone, since Huawei apparently dropped support for the Honor 9 a while ago, I'm getting concerned of my phone being a security risk as the Android security patch is of july 2019. As my 3-year-old phone is still working totally fine, I was...
forum.xda-developers.com
Hi,
I just noticed that on my rooted (Magisk 23) and therefore bootloader-unlocked device Widevine L1 seems to be active according to DRM Info.
I always thought this to be impossible. OOS 11.0.2.1 fixed some Widevine issues. Is it possible they fixed too much?
TheColin21 said:
Hi,
I just noticed that on my rooted (Magisk 23) and therefore bootloader-unlocked device Widevine L1 seems to be active according to DRM Info.
I always thought this to be impossible. OOS 11.0.2.1 fixed some Widevine issues. Is it possible they fixed too much?
Click to expand...
Click to collapse
I'm not sure about updating to the latest 11.0.2.1 from an older version in an B/L unlocked state (as i haven't tried on my device), but I do know that some people (with locked bootloaders) Lost L1 after updating to 11.0.2.1
I know with the previous versions of OOS11(other than 11.0.2.1), I had to keep the bootloader locked for upgrading from A10 to A11, then I could unlock bootloader and still keep L1. It's nice to know that I may not have to repeat this process if/when I decide to upgrade to A11.
Hw4ng3r said:
They were suppose to have fixed this issue with the first version of A11/OOS11, but it was problematic for some and not others. I'm not sure about updating to the latest 11.0.2.1 from an older version in an B/L unlocked state, but I do know that some people (with locked bootloaders) Lost L1 after updating to 11.0.2.1
I know with the previous versions of OOS11(other than 11.0.2.1), I had to keep the bootloader locked for upgrading from A10 to A11, then I could unlock bootloader and still keep L1. It's nice to know that I may not have to repeat this process if/when I decide to upgrade to A11.
Click to expand...
Click to collapse
So you mean they should have fixed the error of not licensed devices getting L1 or an error where legit L1 devices were downgraded to L3?
TheColin21 said:
So you mean they should have fixed the error of not licensed devices getting L1 or an error where legit L1 devices were downgraded to L3?
Click to expand...
Click to collapse
I have seen a lot of users (I think it's mostly 7T devices) that have actually lost L1 with the latest update, even with locked bootloaders.
OnePlus recently stated that their next update is suppose to fix the L1 loss on locked devices, but I would take that with a grain of salt. They've been messing up hard with OOS11 on 7/T/Pro devices.
Aren't unlocked devices supposed to be bound to L3?
TheColin21 said:
Aren't unlocked devices supposed to be bound to L3?
Click to expand...
Click to collapse
You would think yes, but not on OOS11. L1 sticks regardless of the bootloader state.
Do you have any source for that?
TheColin21 said:
Do you have any source for that?
Click to expand...
Click to collapse
Sorry I should probably correct my posts. I don't know if OnePlus ever stated that you will get L1 with an unlocked B/L on OOS11 (I don't think they ever would). As you have stumbled across it with your device, and I know it works with my device as well (and many other 7T/Pro's) since the very fist release of OOS 11, we are somehow able to keep L1 with the B/L in an unlocked state.
Has anyone been able to restore widevine l1 certification ocne you unlocked your bootloader? Currently running the latest .128 USA rom on an xc62 with the latest kirishima rom. My device is currently spoofed as a nexus 6p. Google play is certified. Google wallet works. Magisk is hidden and renamed. Netflix and anything Google shouldn't see it but I'm still at l3 certification. Anyone have a fix?
There is no fix for L1 because you unlocked your bl so the drm keys are gone and that gives you L3 widevine.