Related
Hi all, currently running my pixel 2 on latest Dec security patch. 8.1. However due to bug in bootloader (66) unable to unlock the device. I can RMA but still want to know is there any way to revert back OTA update ?
I tried using OTA side load from Recovery but its giving me error saying current timestamp is newer than OTA so failing.
Any tweak to downgrade ?
rohanhole said:
Hi all, currently running my pixel 2 on latest Dec security patch. 8.1. However due to bug in bootloader (66) unable to unlock the device. I can RMA but still want to know is there any way to revert back OTA update ?
I tried using OTA side load from Recovery but its giving me error saying current timestamp is newer than OTA so failing.
Any tweak to downgrade ?
Click to expand...
Click to collapse
As far as i know u cant downgrade. Regarding the bug in bootloader unlocking, that has been solved. Restore factory your device and you should be able to unlock bootloader.
infamousvincci said:
As far as i know u cant downgrade. Regarding the bug in bootloader unlocking, that has been solved. Restore factory your device and you should be able to unlock bootloader.
Click to expand...
Click to collapse
I tried but facing issue. Its toggling but at the time of flashing fastboot command its saying locked.
I doubt something broke in 66 version of bootloader. That's why wanted to be on previous version to check the solution
rohanhole said:
I tried but facing issue. Its toggling but at the time of flashing fastboot command its saying locked.
I doubt something broke in 66 version of bootloader. That's why wanted to be on previous version to check the solution
Click to expand...
Click to collapse
What command are u running? And what is the error that shows
infamousvincci said:
What command are u running? And what is the error that shows
Click to expand...
Click to collapse
Described in https://issuetracker.google.com/issues/68897739#comment119
Read last comments ! You will realise.
rohanhole said:
Described in https://issuetracker.google.com/issues/68897739#comment119
Read last comments ! You will realise.
Click to expand...
Click to collapse
Prolly yeah. But i was able to unlock bootloader on 2 pixel 2 phones running 8.1. mine and my fiance. Prolly weird and rare bug
Currently I am on stock OOS with a locked bootloader and I heard that when you unlock the bootloader the DRM gets downgraded to L3.
Is this correct and does it go back to L1 if you relock the bootloader?
Also, is there a hack of some sort that allows the device to continue using L1 DRM with an unlocked bootloader?
L1 not working
I unlocked bootloader and then relocked it again but it is still showing L3 what should i do
Hey check this -> https://forums.oneplus.com/threads/closed-widevine-drm-on-op6.815683/page-2#post-18476836
You can try to flash magisk to pass the saftynet and hide netflix/amazon prime video to try HD content
edit:
My OnePlus 6 with unlocked bootloader and I have DRM lvl 3
Pundy said:
Hey check this -> https://forums.oneplus.com/threads/closed-widevine-drm-on-op6.815683/page-2#post-18476836
You can try to flash magisk to pass the saftynet and hide netflix/amazon prime video to try HD content
edit:
My OnePlus 6 with unlocked bootloader and I have DRM lvl 3
Click to expand...
Click to collapse
Ok so it is reversible
But there is no way to get L1 with an unlocked bootloader?
ThePiGuy said:
Ok so it is reversible
But there is no way to get L1 with an unlocked bootloader?
Click to expand...
Click to collapse
What I've seen by now, no it's not possible.
Pundy said:
What I've seen by now, no it's not possible.
Click to expand...
Click to collapse
Ah ok that's unfortunate
I'll probably stay with official OOS for the moment anyway, but thanks for the info
So, has anyone tried OOS 5.1.6 and the fastboot locked bootloader bug to backup and restore the DRM keys while locked or to use Magisk root while on 5.1.6 locked bootloader and see if L1 keys are retained?
driverdis said:
So, has anyone tried OOS 5.1.6 and the fastboot locked bootloader bug to backup and restore the DRM keys while locked or to use Magisk root while on 5.1.6 locked bootloader and see if L1 keys are retained?
Click to expand...
Click to collapse
There's another thread in this forum that poses that exact question. No one to date has succeeded and I'm not sure it's even possible using the 5.6 boot exploit because Widevine calls home every time it proxies protected content.
I suggested chipping in on a bounty that would go to whomever can find a way to get L1 on a OP6 with its' bootloader unlocked using a method that would be successful with ROMs based on OOS, LOS and AOSP. I figured a little financial incentive could provide some motivation, but nobody else seemed willing to contribute. ?
TuxRuffian said:
There's another thread in this forum that poses that exact question. No one to date has succeeded and I'm not sure it's even possible using the 5.6 boot exploit because Widevine calls home every time it proxies protected content.
I suggested chipping in on a bounty that would go to whomever can find a way to get L1 on a OP6 with its' bootloader unlocked using a method that would be successful with ROMs based on OOS, LOS and AOSP. I figured a little financial incentive could provide some motivation, but nobody else seemed willing to contribute.
Click to expand...
Click to collapse
Since I need L1 on an unlocked bootloader, I ended up getting a Moto Z3 Play despite it being slower since Widevine L1 stays regardless of bootloader state or Magisk being installed.
Today I did a stupid thing, I unlocked the bootloader, and only then found out that because of this I can not watch Netflix in HD, so I blocked the bootloader again, but Widevine still indicates L3, am I doing something wrong?
Is the device rooted?
CurlyApple said:
Is the device rooted?
Click to expand...
Click to collapse
No, now it's full stock with locked bootloader.
Edit #1
I just tried flashing the system via Msm Tool, it didn't change anything, it's still Widevine L3
Sounds strange. I've unlocked and relocked the bootloader a couple of times and it always restored DRM L1 ?
Is it possible that I can't go back to L1 because of flashed persist.img in fastboot?
yeah, just reflash the original one or use mdm download tool
matze19999 said:
yeah, just reflash the original one or use mdm download tool
Click to expand...
Click to collapse
That's the problem, I don't have the original persist.img from my phone.
I also tried to unlock the bootloader and use the MsmDownload Tool, but it did nothing, I made a mistake after unlocking the bootloader, I did not know how to go back to stock and how to use msm download tool, so I used the fastboot package in which it was persist.img, I don't know what to do, I have blocked bootloader and Widevine L3
Rayekk said:
That's the problem, I don't have the original persist.img from my phone.
I also tried to unlock the bootloader and use the MsmDownload Tool, but it did nothing, I made a mistake after unlocking the bootloader, I did not know how to go back to stock and how to use msm download tool, so I used the fastboot package in which it was persist.img, I don't know what to do, I have blocked bootloader and Widevine L3
Click to expand...
Click to collapse
I Also Unlocked & Relocked BL of my 7 Pro many times (used MSM Tool for reverting), It simply reverts back to L1, without any issues
aaryan45 said:
I Also Unlocked & Relocked BL of my 7 Pro many times (used MSM Tool for reverting), It simply reverts back to L1, without any issues
Click to expand...
Click to collapse
Maybe, but in my case it doesn't work that way, I don't know why, maybe it's because I flashed persist.img that doesn't come from my phone
I wrote to support about my problem, they told me to send the phone back to the repair service, so I did, the phone came back to me after a week with a flashing system again, but Widevine still indicates L3, what should I do now? please help
I have the same problem as well
Kshysiek said:
I have the same problem as well
Click to expand...
Click to collapse
Reflashed phone several times after rooting with msm and it predictably restored l1 everytime
misterSTV said:
Reflashed phone several times after rooting with msm and it predictably restored l1 everytime
Click to expand...
Click to collapse
My current OnePlus works exactly like that, but the previous model I wrote about in this thread had an incorrect persist partition, for my fault of course, I unnecessarily flashed it through fastboot, I didn't know about MSM at the time. I learned that the persist partition is responsible for DRM keys, when it is changed or damaged the phone irretrievably loses widevine L1.
Rayekk said:
My current OnePlus works exactly like that, but the previous model I wrote about in this thread had an incorrect persist partition, for my fault of course, I unnecessarily flashed it through fastboot, I didn't know about MSM at the time. I learned that the persist partition is responsible for DRM keys, when it is changed or damaged the phone irretrievably loses widevine L1.
Click to expand...
Click to collapse
I have same issue help plzzz
Rayekk said:
Today I did a stupid thing, I unlocked the bootloader, and only then found out that because of this I can not watch Netflix in HD, so I blocked the bootloader again, but Widevine still indicates L3, am I doing something wrong?
Click to expand...
Click to collapse
Hi bro, have you fixed it ? I have the same problem with my 8T
Hello just a few minutes ago I manually searched for updates from the system setting (have auto update off) and realized I had an update so I took it. I've taken updates OTA before with no issues however this time it basically completely factory data reset my phone and also what's more bizarre is it removed my bootloader unlock that I had gotten way back when the phone was first released. I have never installed custom firmware or even rooted the device but I did get my bootloader unlocked using a paid service that I found about here. I have a snapdragon model note 20 ultra 5g. I am so confused why this time around the OTA affected these things. I have included a screenshot of the OTA I took. Can anyone tell me what happened to my bootloader unlock I've had for like 6 months ?
Do you have a U or a UI device? If so I think Samsung changed the bootloader from version 1 to version 2 and that might be why you lost it. Checkout the last 2 pages of this thread here where you might be able to get more clarification.
Whenever you lock or unlock your bootloader, you device will factory reset.
When you took the update, it updated the bootloader to version 2.
Since your unlock was not an official one, it relocked your bootloader in the process.
This is what caused the wipe.
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
coilbio said:
Yup. You're not supposed to take ota updates with unofficial unlocked bootloader.
Not even sim unlock.
Click to expand...
Click to collapse
Is there such a thing as an official bootloader unlock?
shpotik said:
Is there such a thing as an official bootloader unlock?
Click to expand...
Click to collapse
Nope. Not for US versions.
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
*Detection* said:
Why did you unlock the bootloader if you haven't ever rooted or flashed custom?
Click to expand...
Click to collapse
It sounded like a good idea at the time.
I've successfully reverted back to stock rom using the rescue software but couldn't figure out how to relock the bootloader. Could anyone post a tutorial on it?
raiprasant62 said:
I've successfully reverted back to stock rom using the rescue software but couldn't figure out how to relock the bootloader. Could anyone post a tutorial on it?
Click to expand...
Click to collapse
Fastboot mode => fastboot flashing lock
Will I get widevine L1 support back if I relock bootloader? And will I be able to unlock it again?
raiprasant62 said:
Will I get widevine L1 support back if I relock bootloader?
Click to expand...
Click to collapse
I don't know
raiprasant62 said:
And will I be able to unlock it again?
Click to expand...
Click to collapse
yes
@raiprasant62 it is VERY CRITICAL that you have the correct stock ROM variant for your model installed before relocking bootloader or it'll lock and give a corrupt device warning and fail to boot!!!!
The ONLY safe way to relock bootloader is to use Motorola Rescue and Smart Assistant tool and then boot into the ROM and then attempt relocking
Has anyone successfully relocked the phone and checked Widevine L1 status after relock?
I read somewhere here that once unlocked.. this phone can never get L1 back and is stuck on L3 forever. But I can't find where. I wonder if it's speculation or has anyone actually tried it?
JonW434 said:
Has anyone successfully relocked the phone and checked Widevine L1 status after relock?
I read somewhere here that once unlocked.. this phone can never get L1 back and is stuck on L3 forever. But I can't find where. I wonder if it's speculation or has anyone actually tried it?
Click to expand...
Click to collapse
is there a fully working TWRP build available for this device which can backup /data? if yes then backup your data -> relock the bootloader -> boot into system and see what will happen.
As far as I know, there's no working TWRP currently, but I will keep looking. I haven't seen anyone talk about using it.
I did find this, from here, but I haven't found anyone talk about the pros and cons or if it worked or not. My phone hasn't been unlocked yet, because I'm unsure if I will get L1 back if I ever relock it. If I unlock it, I'll test a few of the ROMS on here out and see what happens.
JonW434 said:
I did find this, from here, but
Click to expand...
Click to collapse
that's all I could find, too. but it's unclear if it's able to decrypt & backup /data.
I assume it would be possible to bring back L1 since it depends on your verified boot state. it's like the Play Store certification I think.
@JonW434 I have heard users on Telegram saying that yes relocking bootloader that WV L1 does come back on Motorola devices
ThE_MarD said:
@JonW434 I have heard users on Telegram saying that yes relocking bootloader that WV L1 does come back on Motorola devices
Click to expand...
Click to collapse
Yeah it seems so.
Like you said in post #5, it seems the most important thing is to make sure to have correct version of stock rom installed for correct model. Outside of that, it just seems there aren't many people relocking in order to confirm it. But it seems like it should work like with any other phones. I've seen other Motorola users (for other models) that it relocks fine. I'm not sure where it came from that this phone can't do that, maybe it was a misunderstanding.
JonW434 said:
I'm not sure where it came from that this phone can't do that, maybe it was a misunderstanding.
Click to expand...
Click to collapse
some Moto's will never get back the state of "oem_locked" once they were unlocked. maybe that's the reason. but it doesn't effect the verfied boot state.
WoKoschekk said:
some Moto's will never get back the state of "oem_locked" once they were unlocked. maybe that's the reason. but it doesn't effect the verfied boot state.
Click to expand...
Click to collapse
Interesting. I've been outside the world of Android stuff for a few years and have been relearning everything, or some new things that have changed.
Is there a way to check the state of these things via an app or rooted file explorer or are this things inaccessible to us, in terms of modifying or viewing them?
JonW434 said:
Interesting. I've been outside the world of Android stuff for a few years and have been relearning everything, or some new things that have changed.
Is there a way to check the state of these things via an app or rooted file explorer or are this things inaccessible to us, in terms of modifying or viewing them?
Click to expand...
Click to collapse
on your fastboot screen bottom left: oem_locked, flashing_unlocked or flashing_locked
JonW434 said:
Has anyone successfully relocked the phone and checked Widevine L1 status after relock?
I read somewhere here that once unlocked.. this phone can never get L1 back and is stuck on L3 forever. But I can't find where. I wonder if it's speculation or has anyone actually tried it?
Click to expand...
Click to collapse
I don't know how to check that but after relock I was able to use Google wallet without any hacks. Also unlock again was not a problem. Now I am on stock 13 ROM rooted. That works good for me.