Hello, I did Rooted my OnePlus 7pro last month after the latest update & security patch.
I did unlocked bootloader and did the patched image with fastboot. Installed magisk and did something based on search result from xdaforum to fix missing Waveline L1 issue,
But now yesterday I found that none of streaming service is able to play hd content with "DRM_SCHEME_NOT_SUPPORTED" error in all downloaded files. I've been trying to fix the issue without wiping the whole device with no success. If anyone able to fix it without reflashing/wiping please help
Unlocking the bootloader will end in getting widevine L3, but with any Open Beta or the lastest stable from OOS11 we get widevine L1 with unlocked bootloader and root, also we can get it in custom roms using the mentioned stock roms as base.
RokCruz said:
Unlocking the bootloader will end in getting widevine L3, but with any Open Beta or the lastest stable from OOS11 we get widevine L1 with unlocked bootloader and root, also we can get it in custom roms using the mentioned stock roms as base.
Click to expand...
Click to collapse
Ah... Thanks, today I recieved notification for the update 11.0.2.1, can I update to it without doing any unroot process, btw I have rooted by flashing patched image by adb.
Will updating the device brick it. I use oxygen updater for updates
bullooka said:
Ah... Thanks, today I recieved notification for the update 11.0.2.1, can I update to it without doing any unroot process, btw I have rooted by flashing patched image by adb.
Will updating the device brick it. I use oxygen updater for updates
Click to expand...
Click to collapse
The method to get root doesn't matter, and you don't need to worry about getting your device bricked for installing any update just keep in mind that for rooted devices is mandatory to install full OTA and not the incremental OTA.
After installing the update don't reboot and go to magisk and select install>install to the inactive slot to keep root
RokCruz said:
The method to get root doesn't matter, and you don't need to worry about getting your device bricked for installing any update just keep in mind that for rooted devices is mandatory to install full OTA and not the incremental OTA.
After installing the update don't reboot and go to magisk and select install>install to the inactive slot to keep root
Click to expand...
Click to collapse
Thanks. I'll avoid the root for now. Loosing L1 cirtification was a big headache for me.will avoid any chance.
bullooka said:
Thanks. I'll avoid the root for now. Loosing L1 cirtification was a big headache for me.will avoid any chance.
Click to expand...
Click to collapse
Related
I'm currently on NXT-29C185B190 and I received update with NXT-29C185B1200, my phone is unlocked and rooted, I have flash fire installed and it recognized that update was downloaded.
My question is flash fire have big red huawei device warning, saying Huawei device is very easy to hard brick (also my mate 8 is my first locked bootloader phone) so is it safe to use flash fire ? or install update throught huawei system without losing root ?
MegaMedo said:
I received update with NXT-29C185B1200
Click to expand...
Click to collapse
Is this an EMUI update through the standard update menu in settings - updater?
The version seems a bit odd to me, the last update for C185 was B320, I wouldn't expect an official update to jump as high as that. Mind uploading a screenshot?
Anyway, as for actually updating, as long as you are running stock recovery (not TWRP) then it shouldn't be an issue. Just know that you WILL lose root after updating. And I'd strongly suggest making a data backup before the update.
MuPp3t33r said:
Is this an EMUI update through the standard update menu in settings - updater?
The version seems a bit odd to me, the last update for C185 was B320, I wouldn't expect an official update to jump as high as that. Mind uploading a screenshot?
Anyway, as for actually updating, as long as you are running stock recovery (not TWRP) then it shouldn't be an issue. Just know that you WILL lose root after updating. And I'd strongly suggest making a data backup before the update.
Click to expand...
Click to collapse
Thanks for the help, I tried to user flash fire to keep my root but it failed to update, now I really think rooting huawei phone is more trouble than it worth as for what you said is version is typo
I'm currently on B190 and I got update to B200.
and yes the update is standard update from system updater
I have twrp installed so that means I can't update at all ?
Plz i want to know how to return to the normal situation after root and unlock bootloader in order to receibe update without problem
Prof1977 said:
Plz i want to know how to return to the normal situation after root and unlock bootloader in order to receibe update without problem
Click to expand...
Click to collapse
Well if you unlocked bootlader and rooted, it safe to say that you have TWRP installed, fire up SRKToolHuawei choose (2)install recovery then install stock recovery after that it reboots and then update using system updater from huawei.
PS: You will lose your root access and new to install TWRP then root again.
MegaMedo said:
Well if you unlocked bootlader and rooted, it safe to say that you have TWRP installed, fire up SRKToolHuawei choose (2)install recovery then install stock recovery after that it reboots and then update using system updater from huawei.
PS: You will lose your root access and new to install TWRP then root again.
Click to expand...
Click to collapse
Thinks a lot were can fond recovery?sorry
Prof1977 said:
Thinks a lot were can fond recovery?sorry
Click to expand...
Click to collapse
download SRKToolHuawei-Lod-Chong-V2.0-20161002 or whatever version you used to unlock bootloader and choose option 2 (Install recevory) and that it.
Thinks very much
Hello.
Just got the news about 7.0 being released for this phone, and thought I would give it a shot. However, I have a few questions before I update . These are not in any particular order and I would love any help people can provide, even if you can't answer all the questions.
Since I got this phone, I unlocked the bootloader (I bought the unlocked version) and got TWRP, then installed SuperSU binary in order to use a few root apps on my phone. Then along came an OTA update. When I went to install it, I got a message informing me that the update couldn't be installed due to my system being modified, which was fair enough as I had installed SuperSU. I stopped bothering with OTA updates.
Now it's been a while and the Nougat update is out and apparently available over OTA. Is there a way for me to return to normal system and get this OTA without losing all of my personal data already on the phone? I understand that I'd probably have to get TWRP again, and what is recommended for root now? Can I "re-lock" my bootloader in order to get the OTA?
Basically: How can I get Nougat without losing my data?
Cheers, and thanks for reading! Quick answers would be appreciated.
DuoDex said:
Basically: How can I get Nougat without losing my data?
Click to expand...
Click to collapse
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
alray said:
backup your data and then flash a ruu, either the nougat version if its available for your version or flash the marshmallow ruu then take the ota update.
What is your "fastboot getvar all" ?
Click to expand...
Click to collapse
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
DuoDex said:
I was able to get it by poking around in the forums, first got the RUU for 1.57, relocked bootloader, and am now OTAing the Nougat version (fingers crossed it all works). Thank you so much for replying!
Question: If I install TWRP (like I had before) and then Magisk, will I continue to be able to receive OTA updates? Backing up and reinstalling is such a pain and I'm afraid I will break something. Some people say you need to mount system read-only - how is this accomplished via TWRP exactly?
Thanks again!
Click to expand...
Click to collapse
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
txag2011 said:
I just went thru the process or putting magisk on nougat. You'll want to use twrp 3.0.3-4 for it. From what I understood from the user who clued me into it, magisk will let you take OTA's and use android pay since it won't mess with dm-verity, SELinux or safetyNet. I can definately confirm the Android pay part at least. I did notice however i had to turn on magisk hide in the settings to get it to pass the safetynet check.
as for mounting the system as read only, the first time i booted into twrp it asked me to either slide the lock to modify /system or check a box to mount it as read only and that was it.
Click to expand...
Click to collapse
I was mistaken, Magisk now patches dm-verity and forced encryption. You should be able to take an OTA by flashing the stock recovery though, and failing that by also restoring the system image backup you make in TWRP before modifying or mounting system.
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
br54 said:
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
Click to expand...
Click to collapse
Since when do you need to relock to install updates?
br54 said:
You have to remove majisk
Relock boot
Then you will receive official update
Then unlock and reinstall majisk
Click to expand...
Click to collapse
freeza said:
Since when do you need to relock to install updates?
Click to expand...
Click to collapse
There is no need to relock.
I didnt whe 110 came out and it still updated... rooted with Magisk as well
@any_thing
Check the ROMs/Kernels/Recoveries section, there's a modified stock recovery that allows for updating w/o relocking the Bootloader.*
Once complete, put TWRP back & root, you will not lose any data/apps/etc...... as you would by simply relocking your Bootloader....
* YMMV,this modified recovery may not be compatible w/your model.
https://forum.xda-developers.com/ho.../recovery-bkl-nocheck-recovery-flash-t3778085
Sent from my HUAWEI BKL-L04 using XDA Labs
Good luck then.... Personally I don't care.. Mine works fine
any_thing said:
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
Click to expand...
Click to collapse
I have the BKL-L04 model & got an update notice earlier today:
While on stock rooted with TWRP & Magisk,the update downloaded & attempted to install,but,it failed.
So,just flash the stock recovery for your model & take the update w/o relocking your bootloader.
You will not lose any data from switching recoveries,at least on this phone.
(If you want to unroot 1st,that's fine,but,not necessary,flashing the modified stock recovery image unroots your phone anyway.)
After taking the update,flash the TWRP & Magisk (& Magisk Manager App,if it disappeared) as you did previously.
Just posting what worked for me,& in no way are my experiences/usage intended to contradict posts/suggestions from others,especially if they have the exact same model of phone as yours.
Hope this helps. :good:
any_thing said:
Guys, i am unable to update to latest .161. I have unlocked bootloader, twrp and installed magisk.
Update manager download the update but it fails to update in twrp recovery.
Please suggest. I don't want to lose data.
Can someone provide zip update package so that i can update in twrp??
Click to expand...
Click to collapse
Just install stock ram disk...
It would automatically remove twrp and root.. And u will b able to install update once updated just reflash twrp ram disk and install magisk zip to get root back..
That's how I did it on c675
(--light--) said:
Just install stock ram disk...
It would automatically remove twrp and root.. And u will b able to install update once updated just reflash twrp ram disk and install magisk zip to get root back..
That's how I did it on c675
Click to expand...
Click to collapse
will i lose my data?
any_thing said:
will i lose my data?
Click to expand...
Click to collapse
No not at all... Ramdisk is a different partation
I had rooted phone with magisk installed, I received 2 updates like that - automatically lost root privileges, but I didn't receive .161 update (EIS update still not available for me?) any way to get this update?
PS my bootloader is unlocked... do I need lock it to get an update? and how to lock it?
I started off by unlocking bootloader (and losing my DRM). I needed to root. Everything was perfect. Then, I saw the VoLTE ROMs. I went for Bliss. It installed OK but I started to get SIM1 issues and than I was not able to get a all-clear on the Magisk security test. Also, my corporate apps failed to install because device was not getting encrypted. I reinstalled but same effect. Then I went to crDroid. Its Android 9. Exact same issues except SIM1 was okay now. Right now, I used XperiFirm to get the official ROM and install it but keep TWRP + Magisk and I'm still facing the issue with encryption, Magisk security test failing, & no rooting.
How should I reinstall official ROM but keep bootloader unlocked + Magisk + root? Am I to do a more through formatting?
me too other person can't hear me what i say. (Bliss rom 12.12 latest ver.)
Doomer D. Great said:
I started off by unlocking bootloader (and losing my DRM). I needed to root. Everything was perfect. Then, I saw the VoLTE ROMs. I went for Bliss. It installed OK but I started to get SIM1 issues and than I was not able to get a all-clear on the Magisk security test. Also, my corporate apps failed to install because device was not getting encrypted. I reinstalled but same effect. Then I went to crDroid. Its Android 9. Exact same issues except SIM1 was okay now. Right now, I used XperiFirm to get the official ROM and install it but keep TWRP + Magisk and I'm still facing the issue with encryption, Magisk security test failing, & no rooting.
How should I reinstall official ROM but keep bootloader unlocked + Magisk + root? Am I to do a more through formatting?
Click to expand...
Click to collapse
if you go to reinstall official rom you will not having any facing problems only root will gone, and i use Emma software
I'm not used to Emma. But from what I gathered, I'll be back on a non-root device. I do not want that. We are already facing issues with Android 10 Roms and device encryption. I need to reinstall with XperiFirm but need to know what *ta files I need to delete before flashing and also, what do I have to format and wipe as well. Need to retain boot loader as unlocked.
No need to delete any *ta just flash with newflasher
Toni Mahmud said:
No need to delete any *ta just flash with newflasher
Click to expand...
Click to collapse
HI. Keeping all TA files means I'll loose unlock bootloader too? Say I'm more in favor of having a working phone, what do I need to format or wipe before flashing or I just flash and everything is set? Since I have bootloader already unlocked do I need to say y/n to the new flasher questions?
give only for all and put ENTER don't worry