UPDATE – 07.03.2017
This patch is no longer required to have Google Device Certification.
After install ROM B594 no further actions are required.
Thanks to "who" did this correction … and I hope somehow this thread helped to speed up solving this mismatching.
Note:
I created a new flashable zip to set original B594 local.prop in case of someone want revert the patch without install the complete ROM
_____________________________
_____________________________
WARNING: I'M NOT RESPONSIBLE FOR SCREWING UP YOUR PHONE
If you are not used to solve soft-brick don't play with this.
After installation of new stock ROM ALE-L21C432B594
- Device become uncertified
- SaftyNet status fail, due to CTS profile mismatch
How to get back device certification and CTS profile match?
- You have to change Fingerprint from B594 to B588 (at least worked to me)
- File to change => local.prop
- Location => /cust/hw/eu/prop
- See image enclosed how to change it
- After you aplied this, unroot your device, run the Safety Net test, check Play Store Settings and check if it works
- I created flashable zip in case your device is not rooted but you have TWRP installed
Thanks, it worked for me
Btw. You can root with magisk to pass SafetyNet with root.
Ok, if we don't have open bootloader, we should wait until certificated automatically? It's just the number, so it's maybe just not documented by Google, right? Hope so
If you're not rooted and do not have a custom recovery, how do you apply this?
I've extracted CUST.img from the UPDATE.APP, edited the file and rebuilt the image. Can I just use fastboot to flash it?
@proze.za
Try first without this patch. I have changed this line back and I can still pass SafetyNet. What's more my device is certified...
You need unlocked bootloader to flash cust.img and if you have unlocked bl you can just flash TWRP.
dominj97 said:
@proze.za
Try first without this patch. I have changed this line back and I can still pass SafetyNet. What's more my device is certified...
You need unlocked bootloader to flash cust.img and if you have unlocked bl you can just flash TWRP.
Click to expand...
Click to collapse
You're right. I just checked and my device is certified with B594.
proze.za said:
You're right. I just checked and my device is certified with B594.
Click to expand...
Click to collapse
So B594 it's certified? Or you did something?
Azzureux said:
So B594 it's certified? Or you did something?
Click to expand...
Click to collapse
I just installed the full B594 update (placed UPDATE.APP in dload on an sdcard, etc). And it says it is certified.
Now CTS is passed without change anything. SafetyNet-Check completly passed, but in Play Store uncertificated. No problems at all
First post updated
After full rom reflash I get no "uncertified" message
Audriuskins said:
After full rom reflash I get no "uncertified" message
Click to expand...
Click to collapse
You want tell us that we just have to update from B594 to B594 to get certificated back?
Edit: I have tried, but that isn't working. So I have to live with that.
dominj97 said:
Thanks, it worked for me
Btw. You can root with magisk to pass SafetyNet with root.
Click to expand...
Click to collapse
Thanks for the hint :good:
I tried and it works
Works, too. Closed Bootloader, no root. Uncertificated is shown on Play Store, but everything is passed since monday.
allrightlite said:
Works, too. Closed Bootloader, no root. Uncertificated is shown on Play Store, but everything is passed since monday.
Click to expand...
Click to collapse
Monday! I thought it was on Tuesday, but anyway, what was tested this time was only if SafetyNet passed on the device with root.
Like dominj97 mention on his post it works if I make root with Magisk.
I tested with SuperSU, Suhide, Superuser, but in my case only worked with Magisk.
Thread closed as per OP request.
Forum moderator,
Matt
Related
can i flash magisk using twrp and get root?
It worked for me using twrp from https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449 and magisk 16.0 on oreo firmware.
Quick answer...yes.
On Oreo (VTR-L09C432B360), I installed the 15.4 version from here... https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 (it's for the P10 Plus but works on P10's as well)
You can then update to the latest version (v16) via the Magisk Manager app.
Nougat here... https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
colthekid said:
Quick answer...yes.
On Oreo (VTR-L09C432B360), I installed the 15.4 version from here... https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 (it's for the P10 Plus but works on P10's as well)
You can then update to the latest version (v16) via the Magisk Manager app.
Nougat here... https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
Click to expand...
Click to collapse
It's doable on any p10's right like I have the dual sim version.
One more question....to get the treble ROM I have to root right?
Those have flashed successfully, did your SafetyNet pass completely? ctsProfile is the only issue I'm having right now
naeemomr said:
It's doable on any p10's right like I have the dual sim version.
One more question....to get the treble ROM I have to root right?
Click to expand...
Click to collapse
Works on all P10's as far as I'm aware. Don't know about Treble, I'm on stock.
MrDanMak said:
Those have flashed successfully, did your SafetyNet pass completely? ctsProfile is the only issue I'm having right now
Click to expand...
Click to collapse
Yes SafetyNet passes fine
colthekid said:
Works on all P10's as far as I'm aware. Don't know about Treble, I'm on stock.
Yes SafetyNet passes fine
Click to expand...
Click to collapse
Damn, didn't work for me. Just the ctsProfile: False issue I'm having. On the B360 firmware using the latest TWRP that works for the P10 as well. Know of anything else I can do to fix this perhaps?
Try Magisk in core only mode and turn on Magisk Hide, other than that I don't know I'm afraid.
-i instaled magisk manager (16)
-patched the original boot parition (you have to untrigger both options in magisk manager..."keep force encryption" "keep AVB 2.0/dm-verity)
-flashed modified boot parition with TWRP
-all OK, safetynet OK
DallasCZ said:
-i instaled magisk manager (16)
-patched the original boot parition (you have to untrigger both options in magisk manager..."keep force encryption" "keep AVB 2.0/dm-verity)
-flashed modified boot parition with TWRP
-all OK, safetynet OK
Click to expand...
Click to collapse
Hi DallasCZ,
May I ask you to be more specific?
I just ordered a P10 and I would like root it with Magisk (I alrady have a Lenovo Tab3 8Plus (TB-8703F) and successfully routed with Magisk (Safety Net check is green))
So, what are the steps? Can I use the original Magisk, or should I use a P10 specific? And how the OTA updates work with the Magisk? Eg.: Do you have to disable it before update? I hope not, since Magisk is systemless and the Oreo ROM is Treble "compatible". Oh, and could you give me a link to a working TWRP, which is compatible with the latest Oreo?
Thanks everything in advance!
So, is it not possible to flash ramdisk without unlocking bootloader?
cesedy said:
So, is it not possible to flash ramdisk without unlocking bootloader?
Click to expand...
Click to collapse
Yes you jave to unlock bootloader first.
Finally I got my phone. Now I'm testing, and getting familiar with it. But after that, I really need some help / advice ...
So my questions are the follows:
If I open the bootloader (no root, no other modifications), will I get OTA updates, and will they work?
Which TWRP is recommended? twrp 3.2.1-0 OREO or TWRP 3.2.1-0 for EMUI 8.0 or another one? What is the difference between the first two?
Can I use the official Magisc? I'm on VTR-L29 8.0.0.360(C432)
And the "really big" question: Is it possible to have OTA updates and Magisk at the same time? If yes, how?
Dexterova said:
Finally I got my phone. Now I'm testing, and getting familiar with it. But after that, I really need some help / advice ...
So my questions are the follows:
If I open the bootloader (no root, no other modifications), will I get OTA updates, and will they work?
Which TWRP is recommended? twrp 3.2.1-0 OREO or TWRP 3.2.1-0 for EMUI 8.0 or another one? What is the difference between the first two?
Can I use the official Magisc? I'm on VTR-L29 8.0.0.360(C432)
And the "really big" question: Is it possible to have OTA updates and Magisk at the same time? If yes, how?
Click to expand...
Click to collapse
Guys, don't bother with answering my question. It seems that Huawei removed the possibility to get unlock code. So, right now it seems I'll never be able to root my device
Dexterova said:
Guys, don't bother with answering my question. It seems that Huawei removed the possibility to get unlock code. So, right now it seems I'll never be able to root my device
Click to expand...
Click to collapse
Apparently you can contact customer service and receive the unlock code after a couple of days.
M1chiel said:
Apparently you can contact customer service and receive the unlock code after a couple of days.
Click to expand...
Click to collapse
Are you sure? How? Just write an e-mail to [email protected]? But why they shut down the request page / site? This does not make any sense.
Dexterova said:
Are you sure? How? Just write an e-mail to [email protected]? But why they shut down the request page / site? This does not make any sense.
Click to expand...
Click to collapse
Huawei Reddit
M1chiel said:
Huawei Reddit
Click to expand...
Click to collapse
OK, I'll give it a try...
... (other) question(s):
If I open (no root) the bootloader, will I get OTA updates?
In other words: you guys, with Magisk, how do you update your devices?
Because we do not make a list of which modules work 100% in magisk in P10, since for example xposed produces a hard brick.
Sorry my bad english
Is this still available [email protected]?
I got this error message:
The response from the remote server was:
550 5.1.1 Error: invalid recipients is found from 209.85.216.178
Since the sources are out, is there a kernel with dm-verity disabled?
I want to be able to root and keep TWRP, make some changes (hosts, restore some titaniumbackup files), unroot and still pass the checks, which normally fails due to safetynet detecting the unlocked bootloader. If I understood correctly, disabling dm-verity will allow safetynet to pass even with unlocked BL?
Or is that outdated info?
I pass safetynet with an unlocked bootloader,TWRP and root (Magisk). Just install the MagiskHide Props Config module via Magisk Manager->Modules and in a terminal type:
su
props
and apply the fix and select mate 10 as device
I'm trying to avoid using magisk to avoid losing safetynet access when an update comes. I really only need root once.
I believe you can fully uninstall magisk and pass safetynet as it was stock again
No, unfortunately not, since safetynet detects the unlocked bootloader.
Arak0n said:
No, unfortunately not, since safetynet detects the unlocked bootloader.
Click to expand...
Click to collapse
Oh sorry didn't knew that, thought maybe just using unsu.zip would do the trick
When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs
hackintosh5 said:
When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs
Click to expand...
Click to collapse
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.
kaiomatico said:
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.
Click to expand...
Click to collapse
The files are great, but, sorry to tell you, someone else already sent them to me.
However, there's good news, I got Honor Support to escalate my request to a supervisor so maybe someone will actually give me sources now! Yay.
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Note: when I and others have tried the "Local upgrade" feature with older OxygenOS international releases (e.g. 9.0.5), it would cause the T-Mobile device to brick and get stuck in the "Device mismatch" bootloop. This time it's different! Was able to re-lock bootloader after sideloading the full official 9.0.7 OTA and retain all functionality. It is likely we will even be able to take official OTA upgrades after this...if so, I consider this a full conversion
I followed @Dark Nightmares guide and did it the fastboot way and loaded TWRP, Magisk, etc and my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
TheKnux said:
I followed @Dark Nightmares guide and did it the fastboot way and loaded TWRP, Magisk, etc and my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
Click to expand...
Click to collapse
What module from Magisk did you use?
TheKnux said:
my device is certified even though I didn't do a full conversion (at least I don't think I did), I just installed a module from Magisk that let's you bypass all the junk that prevents you from having those features on Netflix, etc.
Click to expand...
Click to collapse
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
AnonymousTipster said:
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
Click to expand...
Click to collapse
Welp, count me in! This sounds great.
AnonymousTipster said:
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Click to expand...
Click to collapse
Can you please elaborate where we can find the local upgrade feature? Also, can we have the link to the ota zip ?
Thanks so much in advance!
Hmmm is this for real..?? Any way to verify??
I guess the only way to tell would be when next ota comes out if it updates without issue.
Nileshdd said:
Can you please elaborate where we can find the local upgrade feature? Also, can we have the link to the ota zip ?
Thanks so much in advance!
Click to expand...
Click to collapse
Settings->System->System updates->"Gear icon"->"Local upgrade"
Use the "full ROM" zips here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
https://forum.xda-developers.com/on...oneplus-6t-t3860953/post78026655#post78026655
OnePlus also publishes them here, but they're usually a bit delayed (still haven't posted 9.0.7 for example):
https://www.oneplus.com/support/softwareupgrade/details?code=9
AnonymousTipster said:
Settings->System->System updates->"Gear icon"->"Local upgrade"
Use the "full ROM" zips here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
https://forum.xda-developers.com/on...oneplus-6t-t3860953/post78026655#post78026655
OnePlus also publishes them here, but they're usually a bit delayed (still haven't posted 9.0.7 for example):
https://www.oneplus.com/support/softwareupgrade/details?code=9
Click to expand...
Click to collapse
Does the local upgrade factory reset the phone? I want to avoid it.
AnonymousTipster said:
Magisk will bypass SafetyNet, for now, but it's a cat-and-mouse game like I mentioned before. It's not guaranteed to keep working.
And no, Magisk does NOT bypass DRM limitations in terms of allowing you to play DRM-protected HD videos. Netflix will max out at 540p on a device with unlocked bootloader, irrespective of Magisk. You're also stuck flashing updates manually, without a full conversion.
Click to expand...
Click to collapse
Look up "liboemcrypto disabler" under Magisk downloads. Correct me if I'm wrong. Play Store said my device was not certified until I flashed this and rebooted and now it says it is certified. Besides, I'm not too worried about flashing updates manually with the way I converted, cause like you said in a few posts below, OnePlus hasn't uploaded 9.0.7 yet, it was much easier to go the route I did rather than wait for OnePlus to upload it. Anyways, thanks for this guide, I'm sure a lot of people (including myself if I decide to go this route) will find it useful.
---------- Post added at 05:49 AM ---------- Previous post was at 05:46 AM ----------
flexor224 said:
What module from Magisk did you use?
Click to expand...
Click to collapse
It's called "liboemcrypto disabler".
AnonymousTipster said:
Thanks to @Dark Nightmare's guide, flashing to an international ROM is a breeze with fastboot. However, it's still a hassle to maintain as a result of it not being a full conversion, and you're stuck with an unlocked bootloader (meaning no HD DRM-protected videos from Netflix, Hulu, or Amazon), and having to play cat-and-mouse with Magisk.
That all changes today.
Thanks to revelations by @Alec_Lightwood: once you've used the fastboot method to load an international ROM (9.0.6, 9.0.7 were tested), you can use the Local upgrade feature in the ROM to sideload the official full 9.0.7 international OTA zip to do a full flash. Once you do that, you can then:
1) Reboot back to bootloader
2) fastboot oem lock
3) Boot into OS, disable "Enable OEM unlocking"
4) Factory reset again for good measure
5) Your device is now "Certified" again, as per the Play Store, Widevine is L1, HD video playback works, dual SIM functionality still works
Click to expand...
Click to collapse
I did the local upgrade. It went just fine.
Now, will lead 2) cause a factory reset? I am trying to avoid it if possible
Nileshdd said:
I did the local upgrade. It went just fine.
Now, will lead 2) cause a factory reset? I am trying to avoid it if possible
Click to expand...
Click to collapse
relock bootloader wipes data. im doing it becuase i dont use root for anything. i only had magisk to hide the unlocked bootloader from my banking/streaming apps.
i followed op instructions and will be the guinea pig when new ota is released. will report back. thanks to oneplus backup software its not too painful to restore.
so which msmdownload tool would you use after such conversion?
headcreepz said:
so which msmdownload tool would you use after such conversion?
Click to expand...
Click to collapse
Not sure I'd assume the T-Mobile one. BUT on prior conversion before the local upgrade was possible, the fastboot oem lock wouldn't work. I was surprised when it worked when I did it last night. We'll know for sure if it's fully converted when next ota is released
After this potential conversion are the imei numbers listed differently in the settings or are they still the same?
yujikaido79 said:
After this potential conversion are the imei numbers listed differently in the settings or are they still the same?
Click to expand...
Click to collapse
Still the same
This is interesting, thank you for the info! I didn't even know we get a partial version of oxygen for T-Mobile models. Since I just received my unlock token today, my qestions are:
1. can I flash the latest oxygen os (dark nightmare guide) and if I do will that be the full version or do I have to follow your route which is 0.6? Then do the device upgrade?
2. Is there a guide to go back to stock T-Mobile rom?
3. Does flashing oxygen or any other rom retain USA bands? Because I saw a post having network problems...
Again, thanks bro!
moist_line said:
This is interesting, thank you for the info! I didn't even know we get a partial version of oxygen for T-Mobile models. Since I just received my unlock token today, my qestions are:
1. can I flash the latest oxygen os (dark nightmare guide) and if I do will that be the full version or do I have to follow your route which is 0.6? Then do the device upgrade?
2. Is there a guide to go back to stock T-Mobile rom?
3. Does flashing oxygen or any other rom retain USA bands? Because I saw a post having network problems...
Again, thanks bro!
Click to expand...
Click to collapse
U can flash using darks guide. Go to 9.0.6 then do the local upgrade to 9.0.7 for this potential full convert
Suggesting this because local upgrade may be what is doing the conversion if it actually is doing what we think it is.
There is a thread also by dark called msmdownload tool. Brings u back to full TMobile out the box stock
I have not had any issue with network. TMobile in NJ
Waiting on dark and a couple others to chime in.
Also I guess it can be tested if someone goes to 9.0
5, then local.uograde to 9.0.6, then see if ota comes in and works to 9.0.7. I should have done this last night but I went and relocked bootloader while on 9.0.7. If I'm.bored my next day off I'll do some testing.
TheKnux said:
Look up "liboemcrypto disabler" under Magisk downloads. Correct me if I'm wrong. Play Store said my device was not certified until I flashed this and rebooted and now it says it is certified. Besides, I'm not too worried about flashing updates manually with the way I converted, cause like you said in a few posts below, OnePlus hasn't uploaded 9.0.7 yet, it was much easier to go the route I did rather than wait for OnePlus to upload it. Anyways, thanks for this guide, I'm sure a lot of people (including myself if I decide to go this route) will find it useful.
---------- Post added at 05:49 AM ---------- Previous post was at 05:46 AM ----------
It's called "liboemcrypto disabler".
Click to expand...
Click to collapse
Akron huh? I am canton. This doesn't fully convert the phone. We all discovered this last update. It just allows us to use the upgrade option or flash in twrp. It still doesn't give us access to critical partitions. Whether or not flashing these OTA zips really do flash the critical partitions or not I dont know. I think it does, and it is sort of a fluke or else the ota zips would brick us still. So either way its great we dont have to use the slow strenuous fastboot method. Also, fyi, just to be sure, after one has flashed the full fastboot firmware package, you can dirty flash the whole ota via local upgrade just to be sure we are upgrading those critical partitions as well. Someone should try to do a dump before and after and compare the different partition sizes to see and verify if this does indeed update the critical partitions.ie, hyp, rpm, abl, xbl. etc.
Anyone know a secure procedure and a custom recovery compatible?
marte66 said:
Anyone know a secure procedure and a custom recovery compatible?
Click to expand...
Click to collapse
We don't have TWRP yet, it's not officially out yet for any G7 models and I don't know when ours may be.
Root your G7 with Magisk
I noticed this method without using TWRP on the G7 XDA forum but haven't tried it, and you must unlock the bootloader first. Apparently it's working for a few G7 users so it should on G7+ too if the correct boot.img is used (for G7+/'lake' not G7/'river') according to your release channel. You still wouldn't have a custom recovery but could install Adaway, Magisk modules, and gain full access to the file system.
EDIT:
If anyone tries this method please report back, and don't forget to unlock the bootloader first and use the Lake/G7 Plus firmware from lolinet. No one has reported it not working but only a handful have used it afaik. I'm on RETLA w/Dec security patch so would rather wait until OTA updated and then I might try it because it would give me everything I need from root except nandroid backups and installing ROMs (of which there aren't any yet). I have my unlock code ready to go and have the needed boot.img from my channel-specific firmware but remain fully stock.
The instructions aren't that detailed but I found you can install Magisk Manager as an apk, open it and when you tap on Install Magisk 18.1 (which isn't installed yet) it also gives the option to "patch boot.img" (which I didn't select but assume it'll let you navigate to where you put the one from firmware & not alter the currently booted partition). When finished you put/copy that altered one on your pc (preferably in your Fastboot/ABD folder) and fastboot flash it, then reboot and you should be rooted in Magisk.
EDIT #2:
Tried it, it works!
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Having done it I can say that Magisk Manager does let you navigate to the stock boot.img file after offering to patch it, then it goes through the same familiar steps as when installing in TWRP, and at the end tells you it's in your Download folder with the name patched_boot.img. After transferring to my pc I renamed it to boot.img and just manually typed in the fastboot flash boot command.
I also want to repeat that although rooted there's still no custom recovery/TWRP so you can't do nandroid backups, and now when my channel's OTA comes along I'll have to disable Magisk & flash back to my original boot.img before taking it, which I hope works but it should. It's great being rooted though on G7+ with Adaway and Youtube vanced background play, also Root Explorer to change my boot animation or debloat or whatever.
Dahenjo said:
If someone on your channel could capture their PPW29.98-66 OTA before installing, otherwise I think you'd have to wait until it appears on lolinet or Motorola's site, or we get TWRP. I realized I'd be in the same boat because my current firmware was also the only one so far on lolinet, so I decided to go ahead because I'd only get January's security patch (on Dec now) and still be a few months behind anyway.
Click to expand...
Click to collapse
Yeah, I thought so. Thanks anyway.
washoq said:
I would like to try this also, however I've already updated to PPW29.98-66 (RETEU) and there is no firmware for this version and channel on lolinet.
Any idea where I can find it or when it will be available?
Click to expand...
Click to collapse
I see there is a PPW29.98-66 RETAIL channel firmware on lolinet:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETAIL/
I'm not sure what difference the boot.img would have between them if any, and the RETAIL channel is more a 'generic' type which might be a safer choice than others of the same build version. I know the G5+ debloated ROMs by NZedPred ended up with just one version (instead of by various channels as he did originally) after finding he didn't need to bother, though I believe he did make other changes. He'd be a good one to ask though if you want to PM him.
After I get updated (revert to full stock etc) I may try the RETAIL one to re-root to see if we can use it for this purpose regardless of channel. My 'international model' from Amazon is actually just the RETLA channel since it wasn't released in the US, so I'd almost rather be on the more generic channel if it works.
EDIT:
Did some experimenting, reverted to full stock then successfully tried it again with the boot.img from the RETAIL firmware (which for my version is still PPW29.98-28), so I believe RETAIL could be used for other channels too.
This process worked for me. Moto G7 Plus, International Unlocked version.
This worked for me, XT1965-2, AT&T mexican version. Also, managed to run Substratum, just needed to compile, reboot and activate each time I changed theme.
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7pluswas shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
shaDNfro said:
Well I am on the same Page...
Also my Channel Islands reteu2, I can only find reteu...
My g7 was shipped already with a newer Version than available. Anyone tried the retail bootloader?
Alternatively, can we somehow flash the whole "retail" version on this phone?
Click to expand...
Click to collapse
I assume you have G7 Plus (not G7) with the build number you showed.
To answer your question:
I successfully fastboot flashed the full RETAIL channel PPW29.98-66 firmware a few days ago. I was on RETLA PPW29.98-28 with the December security patch and now have the January patch, and my channel is still shown as RETLA. I used the batch file posted in this thread which worked perfectly. Everything for my XT1965-2 RETLA model is working as it should on the newer RETAIL firmware, but I don't know if your RETEU2 has anything different that could cause issues.
Enforced Verity, Unlocked Bootloader, rooted Lake OPENMX Not working with Google Pay
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
vvarrior said:
"Couldn't finish setup to pay in stores
This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way."
Did I screw up by not preserving dm/verity when I patched the boot and if so, is there a way to fix it? Reflash oem rom, reinstall magisk, repatch boot, rereflash new rom with dm/verity preserved?
Click to expand...
Click to collapse
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
shaDNfro said:
I tried everything but its not working stalble for me either.
You can do delete google pay cache+data and google play services cache+data, reboot and then you can configure a payment method (e.g. add credit card). Afterwards I was able to pay exactly one time... next time it refues my card telling me I am not able to pay with that card any more...
(Bye the way, people say the issue might be connected with wifi as well, so I turned off wifi for that procedure I mentioned above)
Anyway I deleted google pay now using my banks own application, which does not detect root using magisk hide
Click to expand...
Click to collapse
There's a bunch of Google apps that need verity to be enforced I think. I think we need the stock ROM with the stock boot. Maybe the phone has to be rooted to patch the stock boot.img with verity enforced? I'm not sure but I stepped up to the G7 Plus because it finally has NFC so I can use it to pay and it was an unlocked international version that works good with Google Fi (which also needs verity enforced).
Still looking for a solution and will probably just go back to my old phone until I can get Google Fi and Pay working.
Hi,
I hope somebody can give me a hint.
I just got a used p20 pro with open bootloader but stock rom.
Unfortunately the Google security check has some "problems" with this situation and doesn't allow me to use several apps like Netflix, Google pay, etc.
So I'm looking for a way to easily fix this problem, the phone will be used by my parents.
Either lock the bootloader or "hide" it probably.
But how - I don't have the bootloader code - and I'm not too much into android rooting...
Usefull hints are appreciated.
Merry xmas
Mounty
You're on thin ice my pedigree chum..
Avoid flashing anything that would allow a block of any kind which is an absolute reality.
Having used absolutely every ROM and OS from 8.1 to 10
My advice. Flash AOSIP and then ask in thread to get safety net working.
Literally nothing else it worth your time.
Unless you're strange and like EMUI.
In such case, stuck with stock.
Just be aware you're in a position that a lot of people would kill for.
Google have done some **** stuff to make people who have unlocked bootloader a nightmare. I don't think there is a way to hide it unless you use Magisk
mounty77 said:
the phone will be used by my parents.
Click to expand...
Click to collapse
If they are not some kind of advanced users, unlocked bootloader has exactly 0 added value for them. Search the forum for flushing methods, the ones that will warn you that this method re-locks the bootloader, flush the latest stock ROM for your region and live a happy and calm life.
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Horayken said:
As a suggestion.. Use Magisk with Safety patch and you're done. You can keep the bootloader unlocked and still bypass google restrictions. (Install apps like netflix, etc.)
My phone is on 9.0.1.328 and works fine.
Click to expand...
Click to collapse
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
mounty77 said:
Hi,
Thx so far, I think I'll try the magisk thing.
Are there any downsides on this? Will Ota updates still work?
I already downloaded and installed magisk manager, but I was not able to install magisk via magisk manager.
I downloaded the zip file and tried to install it.
But I only got the attached error.
I think I have to patch something?!
Any advise?
Thx
Mounty
Click to expand...
Click to collapse
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
thx for your offer/advise. I’ll try this way - it sounds most promising to me.
Can I do this on the mobile only, or do I need a pc?
Where / How do I find the ramdisk recovery?
BL Lock
I can lock (yes, lock) your bootloader for free.
Contact me at Telegram (@AntiEngineer), you don't need to open up your device.
abyssq said:
You need to patch the ramdisk recovery file with magisk, flash it and you are good to go. It's a 5 min procedure. Let me know if you need more help with that.
This way you will hide your unlocked bootloader and you will pass safetynet.
Only downside is that if there is an ota update you will need to flash the original ramdisk recovery, do the ota and then do ramdisk recovery file patch again.
If you lock the bootloader then you won't be able to unlock it again as you won't have the code (unless you got the code from the previous owner too).
Click to expand...
Click to collapse
Hi,
unfortionatly I wasn´t sucessfull till now.
At https://openkirin.net/ is a very usefull description availaible but I´m still searching for the RAMDISK Extract. I found that database where you can donwload several versions, but mine wasn´t provided there
https://pro-teammt.ru/en/online-firmware-database/
My Version is:
CLT-L29
10.0.0.138 (C432E3R1P3log)
Anybody knows where I can download that`?
Best regards
mounty
@mounty77
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
You are on Android 10 Beta?
Root on Android 10 Beta not working for me.
Click to expand...
Click to collapse
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
mounty77 said:
No Root, just unlocked bootloader... I want to hide the unlock of the bootloader
Click to expand...
Click to collapse
Installing a "RECOVERY_RAMDIS.img" patched with Magisk is rooting the phone.
I´m fine if i have to root it to hide the open bootloader