Database Develop

Android pay no longer works after MM upgrade [unlocked bootloader, but not rooted]

Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
Some of the CM-based ROMs floating around address this issue, but there is no way to use stock marshmallow with an unlocked bootloader and pass safetynet. So if you want android pay, your options are to stay on SU4TL-49 or install one of the CM-based ROMs that have implemented a workaround.
I got around this issue by using my credit card company's app instead of Android Pay. It allows me to do wireless payments everywhere Android Pay is accepted, but it only checks for root. It does not use safetynet.

Too late for you now, but recently someone in this forum updated to Marshmallow radio, but did NOT flash the Marshmallow bootloader. They were already using custom ROM. Others using that ROM who flashed Marshmallow bootloader no longer pass safetynet, but that person does. The conclusions is an unlocked Marshmallow bootloader or newer is what Safetynet looks for?
And yes, I've flashed both Marshmallow bootloader and radios over both my daily XT1225. I could only test the theory by breaking out my new-in-box third Quark, which have for emergency back-up -- and is which still probably on Kitkat.
While I previously had the older Google Wallet, Android Pay for me is not as important as controlling my own phone as I please. My phones will always be rooted. And in the Moto Quark, unlocking the bootloader is necessary for permanent root, whereas it's not necessary in some other phones -- like LG. But whatever needs to be done to root my phones, I will. And if Android Pay is not possible, so be it. I always carry my wallet when I go out somewhere. Pulling out my phone, pulling out my wallet, what's the difference?

phraxen said:
Hi all:
After upgrading my unlocked-but-still-rooted Turbo to Motorola stock Marshmallow, my Android Pay no longer works; I get the message about Android not be able to verify etc. From what I understand, SafetyNet now checks for unlocked bootloaders, not just root. Also, from what I understand, Sultanxda found a workaround by modifying the Android kernel, which they have working on the OP3.
Does anyone know if anyone is working on this for the original Turbo, and/or could someone kindly point me in the right direction?
Thanks in advance.
Workaround info: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Click to expand...
Click to collapse
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
EDIT: Here is a flashable zip that will flash the bootloader for you for those who are so inclined. Make sure to wipe cache and dalvik/art cache in TWRP afterwards: https://mega.nz/#!6logEaIQ!q8qPJw65Upt38Hxiu1JyxErmwbgL7CBzuGzzPC0C9pQ
EDIT 2: And here is the bootloader.img taken from the SU4TL-49 package if fastboot is your weapon of choice: https://mega.nz/#!iogRGIrQ!ixpZGw1cR90jLxe9r8EAt76SGNoSqVqSv1iu0v14QCc

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
Remember to wipe cache afterwards.
Click to expand...
Click to collapse
I'm confused... isn't that downgrading the bootloader?

ChazzMatt said:
I'm confused... isn't that downgrading the bootloader?
Click to expand...
Click to collapse
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
If anyone wants proof I'm on the SU4TL-49 bootloader, I can take a picture when I get home. I don't know of a way to get a picture of the bootloader screen using only my phone.

TheSt33v said:
Yes it is. And as long as your bootloader is unlocked, no harm no foul. I thought that downgrading the bootloader was the one thing that you couldn't do even if it was unlocked, but I just did it and I'm passing safetynet now, so I guess I was wrong.
Click to expand...
Click to collapse
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.

ChazzMatt said:
Learn something new everyday. Wow.
You just can't downgrade a locked bootloader, eh?
Thank you!
When I get home will try Lollipop bootloader on my XT1225.
The custom ROM guys will love this, then.
Click to expand...
Click to collapse
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!

TheSt33v said:
I seem to remember trying this a long time ago using TWRP, and TWRP was unable to flash the older bootloader. It works fine through fastboot though. I'm going to do some more investigation when I'm not at work to see if I can get TWRP to do this. That would be easier for most people.
Also, I thought the latest iSu already got around this issue. That's what BHB's command line patch thing is for. But it will certainly make things easier!
Click to expand...
Click to collapse
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.

gumbi2647 said:
I was on the latest bootloader and just flashed the .47 bootloader because of major radio issues. I flashed from TWRP and have been doing it since the .49 update.
Click to expand...
Click to collapse
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.

TheSt33v said:
Interesting. I've noticed that TWRP randomly has issues with flashing things on my phone for some reason, and a reboot often fixes the issue. Maybe I just got unlucky that one time, but if that's the case, I'll have a flashable SU4TL-49 bootloader up a few minutes after I get home.
Click to expand...
Click to collapse
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
ADB is not involved. Only fastboot.
The way I did it on my phone (XT1254 unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that the BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Tried safetynet (passed), added a bunch of cards in Android Pay without issue
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.

TheSt33v said:
ADB is not involved. Only fastboot.
The way I did it on my phone (unrooted, unlocked, 100% stock MM) exactly was this:
1. Make note of BL version on bootloader screen.
2. fastboot flash motoboot bootloader.img using the SU4TL-49 bootloader.
3. Reboot bootloader
4. Confirm that that BL version has changed (it did)
5. Reboot to system.
6. Tried safetynet (failed)
7. Reboot to stock MM recovery menu
8. Wipe cache, reboot to system
9. Test safetynet (passed)
I'm assuming that wiping cache using other methods will be just as effective, but I don't know that for sure.
Click to expand...
Click to collapse
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.

gumbi2647 said:
Which version of TWRP are you using? I heard the 04 update has some issues. I have been on 03 forever.
Click to expand...
Click to collapse
04, so that could be it.

I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.

TheSt33v said:
So actually there is a way to get safetynet working again. All you have to do is flash the SU4TL-49 bootloader and wipe cache. I'll be posting the bootloader separately when I get a chance, but if you don't want to wait that long, download the full firmware package here: https://mega.nz/#!i84inDgI!IM_A_IpLlKfGpC90S2DPB6g9t8rVkhO8heE4o_WpdMI, extract bootloader.img and flash using fastboot.
fastboot flash motoboot bootloader.img
fastboot erase cache
Click to expand...
Click to collapse
Thanks for this. I'll give it a shot and let you know how it turns out.

bhb27;70506510So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
[url said:
https://www.androidfilehost.com/?fid=745425885120696423[/url]
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
Thanks! Flashing that works just fine. So now we have 2 options.

bhb27 said:
I post this around XDA, new bootloader add a new prop line
it add
[ro.boot.flash.locked]: [0]
And I patch that with this
https://www.androidfilehost.com/?fid=745425885120696423
with will change that to
[ro.boot.flash.locked]: [1]
Just use adb command
Code:
getprop | grep ro.boot.flash.locked
to check.
and then cts will not fail so is not really need to downgrade for now, There is the chance that Moto will change the boot.img so it can't boot on old bootloader, that did not happens yet on quark but others Moto device is need latest bootloader with latest ROM.
But then again may never be a update from Moto to this device.
So as long Moto did not make another patch flash this in TWRP and test with latest bootloader
https://www.androidfilehost.com/?fid=745425885120696423
of course that will not fix any other CTS fail like xposed or ROOT
So let me know if that helps if not it may be somethings else that can also be patched.
Click to expand...
Click to collapse
That worked for me. I was able to add a debit card without getting the error.
Thanks to you and TheSt33v.

ChazzMatt said:
IF you can flash through TWRP, then clearing caches is no problem in TWRP. IF we must use ADB, please include instructions to also clear caches that way, in any write-up -- if that's what you mean?
Or you do you mean flash bootloader in ADB, then immediately boot into TWRP and clear caches -- before booting back to system?
Click to expand...
Click to collapse
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk

joekitch said:
Have you tried this using TWRP and if so did everything go well
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I have not personally tried it yet. Someone else can answer if they have?

Stock Recovery To Replace Twrp!!!!!Extracted from Official Rom:)

This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me

Brick
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.

abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?

CasinovaRoyale said:
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
Click to expand...
Click to collapse
i don't think so abt hard brick
as when i was updating i simply came with error while updating that can't update
and i also tried updating after flashing custom rom [which is available online] and i was successfully updated

smokinjoe2122 said:
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
Click to expand...
Click to collapse
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.

thippu46 said:
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
Click to expand...
Click to collapse
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty

yograjfire18 said:
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
Click to expand...
Click to collapse
:angel:lol

Does someone has tried this successfully?

mabvmet said:
Does someone has tried this successfully?
Click to expand...
Click to collapse
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.

Could always just do "fastboot boot" instead of "fastboot flash". It will allow you to then boot twrp, install what you want, and not touch the stock recovery.

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
What are the steps I need to follow to install this file? (SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
---------
Edit: Solved
---------
I followed the code section steps on this post:
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
Hey! I Finally did this, I removed the twrp and the root, I Just installed this stock (?) rom through the "adb fastboot". Now when I look for OTA updates it appears a message that indicates that the latest security update is installed, it's the one of December 2017...
Why doesn't it appear the last one (april's or so)?
What I have to do in order to have or reactivate the OTA updates?
Thanks in advance!

Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.

pratham.kamath said:
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
Click to expand...
Click to collapse
How can I know what is the correct stock rom?

SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.

pratham.kamath said:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
Click to expand...
Click to collapse
My current file >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_1
This rom left me with the December security patch and no OTA updates available
This time I will download the same one, but the most recent (February, according with the web)
Next download >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip 03/02/2018 06:35
I followed this steps in code section to flash it... any suggest?
Steps >> https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018

Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.

pratham.kamath said:
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
Click to expand...
Click to collapse
Sorry, how do I run the bat file? The last time I entered the commands one by one.
My software chanel is "openmx" the sameone that I had when the phone was rooted (and with the updates available).

I need help
I need the recovery.img for the device moto g5s plus xt1806:llorando:

How to Root LG G6 H872 on Android Oreo

Hi everyone! I recently bought a LG G6 H872, which still has 10e installed. After crawling the forums for a bit, here's the sequence of things I wanted to do to it:
1.) Update to 8.0 Oreo via OTA.
2.) Unlock bootloader
3.) Root and TWRP using this: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
4.) Magisk
Is the latest Oreo update the 20a version that is mentioned in the thread or should I manually update it to something older. I saw that there was anti-rollback so I don't want to update too far. Also, if there is ever another OTA, how does one update the rooted phone?
Edit: I wrote up some steps if it helps you on this post: https://forum.xda-developers.com/showpost.php?p=77513501&postcount=4

I do not believe there is currently a way to root the T-Mobile versions.

patruns said:
I do not believe there is currently a way to root the T-Mobile versions.
Click to expand...
Click to collapse
That is not correct, see: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518

For future people who come across this thread, here are the steps I took to root this phone:
1.) Factory reset and then update device via OTA incrementally until 20a (which is Android Oreo 8.0)
2.) unlock bootloader: https://www.youtube.com/watch?v=EpaW0-8-QKY
3.) root device: https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Note: there is a video tutorial here: https://www.youtube.com/watch?v=-z4CWLikPcI&t=821s. The first steps of flashing the laf partition are very useful to watch before attempting
4.) Factory reset in TWRP
5.) Reset after encryption error, then wipe with TWRP. May give mount error.
6.) Boot into Android Oreo. Device is not yet rooted at this point.
6.) Flash MAGISK via TWRP (SD card or ADB push) ]. Ignore the mount error. Reboot.
7.) Device is rooted! :good:

That's interesting
Without getting into an issue those steps look slightly different in order than the original process.
Or I'm a dumbass and somehow got it out of order. Seems ok now though.

Hello there!
I want to ask if it's the same to do the steps with 20e ?

Curious as well if this works with the latest update.

thendless said:
Curious as well if this works with the latest update.
Click to expand...
Click to collapse
This is an already rooted version of the latest update. I've downloaded but haven't flashed it yet, but the op is good and I've never had an issue with his work.
https://r.tapatalk.com/shareLink?ur...share_tid=3875515&share_fid=3793&share_type=t
Sent from my LG-H872 using Tapatalk

I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?

I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?

interestor said:
I am glad to see that the bootloader gets unlocked easily. @alliance1975 how did you go from Unlocked bootloader step to Twrp installed step? That is the big one I think.
There is a good TWRP available, but we can't install it because the phone lacks fastboot commands. Is there a way to install TWRP? Or is it really that the only method is the rather risky runningnak3d method?
Click to expand...
Click to collapse
I used the procedure summarized in step 3. I agree it is risky, well, the riskiest root & twrp I've ever tried. I neglected to say I only read instructions, the dev who actually came up with the plan deserves all the credit.

When I try to oem unlock nothing happens. What can I do? I have followed all other instructions.

Follow steps from this https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099

Yeah I got my bootloader unlocked

alliance1975 said:
I succeeded in completing the process.
Permanent unlock from Tom via app.
Unlocked bootloader.
Twrp installed to recovery, can boot to recovery via low volume/power button combo.
Magisk installed.
20a working nicely.
I'm getting requests from Tmo to update from 20a to 20d. Is this recommended? Will twrp, root, unlock, etc. be lost?
Click to expand...
Click to collapse
Any info on this? Will updating from 20a mess up the phone (root, etc...)?

Can't update to August SP on TA-1004

Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?

Xayar said:
Hi everyone;
I have a rooted and unlocked Nokia 8 TA-1004 (Security Patch 1 July 2018; 00WW_4_88B_SP02).
I followed the guides on this very forum on how to root and unlock (first) and then how to put TWRP (after I already had rooted and unlocked).
The problem I'm having is exactly what the title says:
I have the possibility to update to SP of August but I just can't; it gives me an installation error as soon as it finishes downloading.
I already tried to Factory Reset the phone and when that didn't solve anything I tried (and succeded) putting TWRP hoping it would solve (hope never dies) the problem but it didn't.
I'm at a loss here, can anyone help me?
Click to expand...
Click to collapse
This "problem" happens because the Android OS only updates the other partition set (A/B) when it's all stock and to achieve root thru Magisk we must patch the bootloader, making it unsuitable for the process.
You need to revert back to the official bootloader and then you'll be able to get it updated. After that just apply the patched bootloader to regain root/twrp and unfortunately that's what you gotta do on every update.

So uhhh how and where do I get the stock bootloader?
If I flash the magisk uninstaller I should get the stock boot image back because Magisk backs it up but I don't thing that alone does the trick.
What else do I need and where do I get it?

That's not an issue related to bootloader but rather to the patched boot.img existing on both paritions A/B. You'll have to restore Magisk backup image or reflash official June OTA and start updating the system without Magisk.

So if I just flash the Magisk uninstaller I will regain the ability to update?

Xayar said:
So if I just flash the Magisk uninstaller I will regain the ability to update?
Click to expand...
Click to collapse
Either you'll have ability to update or soft brick 50/50 odds

I don't like those odds ?
I tried restoring the boot image using Magisk's tool (since the version 17 there's the option of restoring the boot.img without actually uninstalling everything but it says it doesn't have any boot.img backed up...
I guess I'm back to square one and need to downgrade to the June update... Can I just flash it?

Unable to install OTA

I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image

I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!

I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.

FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.

e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?

FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.