Can someone help me with the stock recovery for the august update?
I can't find the system image for nrd90m anywhere, only the ota.
Thanks
Just out of curiosity. What do you need it for?
quertiy said:
Can someone help me with the stock recovery for the august update?
I can't find the system image for nrd90m anywhere, only the ota.
Thanks
Click to expand...
Click to collapse
There's an index that lists every set of factory images:
http://forum.xda-developers.com/nexus-6p/general/index-huawei-nexus-6p-t3213583
nrd90m is not there.
I just wanted to return to complete stock for nrd90m in order to test if the ota to nrd90u works with magisk and phh's systemless root. It's official, the nrd90m recovery is nowhere to be found.
I flashed the nrd90u recovery and tried the ota but it fails with a generic "error".
Thanks.
Unless you made a clean backup of 90M I'm not sure you can. Google never released the images for 90M. If you restore MAKE SURE YOU DO NOT RESTORE YOUR EFS PARTITION. That will bork you phone into bootloops and I haven't read anywhere that it has been corrected yet.
Related
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Cryptomap said:
I decided to catch up on security patches today and, with any luck, obtain the OTA update for Android N. I performed a full unroot (SuperSU) and blew away TWRP by flashing stock recovery for my current build of 6.0.1 (MTC19X). I have also flashed everything back to stock except user data. My boot loader remains unlocked. Every time I try to get the update to 6.0.1 (MTC20F) OTA, the phone will reboot normally and try to install the update. The little android's antennae wiggle for a minute or two and then it just falls over with the familiar red exclamation mark showing up.
Anyone have any ideas?
Thanks!
Click to expand...
Click to collapse
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
ultyrunner said:
When you did have root, did you make any system changes? Perhaps installing a mod or something that's still there? OTA will fail if it detects any system changes. If you truly are back to stock, then you can also grab a zip of the OTA and install it via ADB sideload. That's what I did and it worked fine.
Click to expand...
Click to collapse
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Cryptomap said:
When I had root I ran AdAway, Helium and the XPosed framework. Do you think any of those would cause my hiccup?
EDIT: I also had SELinuxModeChanger installed.
Would my best bet be to re-root and uninstall some of those programs that could edit system files?
Click to expand...
Click to collapse
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
ultyrunner said:
You won't be able to take an OTA with Xposed for sure as it changes the system big-time. If you want to test out Nougat before they post the factory image (if ever, ugh), then follow section 14 of this guide to the letter. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
You can still flash TWRP and re-root it, but only systemless, and you can also flash a systemless Adaway. Xposed isn't available for Nougat yet, so if you must have that, you're better to wait.
Click to expand...
Click to collapse
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Cryptomap said:
Heisenberg's guides have been incredibly helpful so I'll try that route.
Thanks for the input!
Click to expand...
Click to collapse
No problem. The thanks button does that too ... Seriously though, you have to be 'completely' stock to take an OTA, thus why I await the factory images with baited breath.
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
HelpMeXDA said:
I have TWRP, but I'm still on android 6.0, security patch November 1, 2015, system version 24.11.18.clark_retus and no xposed. I have systemless root, so does full remove root in SuperSU then flashing the right recovery.img work to take all the OTA's till now? The February TWRP flashable OTA thread no longer has a live link.
Click to expand...
Click to collapse
This question is hard to answer... will it work? Maybe, we don't know. The problem is if you are rooted, you did it for a reason (or I would assume so) and you have made some changes to the /system partition over time. Doing a full unroot will not undo those changes. So if you do a full unroot, and fastboot the correct recovery image, then accept the OTA, the recovery is going start the OTA's installation script attempt to process it where it will start a checklist of items to verify, bootloader, boot image, system image, etc... the problem is we don't know what changes will cause the update to error out and which will allow it to apply.
To be honest, I don't think I have heard anyone say they have been able to successfully take this update without going back to pure stock, but ymmv.
The best thing to do would be to return to pure stock via the factory firmware images, we have a known good one of the May 2016 security update.
unrooted XT1644 (previously Magisk rooted)
bootloader unlocked
TWRP 3.1.1-0
ElementalX kernel 3.10.84
OS version: 7.0
Security patch level: June 1, 2017, firmware NPJ25.93-14.5
Baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
SafetyNet app failed "CTS profile" on unrooted Android. Oddly, my phone passed SafetyNet when I used Magisk. But after restoring my phone from a Nandroid backup taken before Magisk was flashed, it no longer passes. Might there be file directory remnants of Magisk that are affecting the SafetyNet result? Any troubleshooting steps appreciated.
There's now a September 1, 2017 OEM security OTA update waiting for me in my Notifications bar. I'm hopeful that the update will create a new system partition that'll get rid of what's causing the SafetyNet fail. Unfortunately a logo.bin TWRP flash fix made a change to my system partition settings that won't allow me to safely take an OTA update. The last time I flashed a security update was through the kindness of someone who provided a TWRP-flashable zip of the June 2017 NPJ25.93-14.5 OTA file. I'm hoping the same will eventually be provided for the September OTA update.
Same case with me too but I have model XT1643 (Indian Version), Build number: NPJS25.93.14-10.
Also, while booting up I still get bootloader unlocked warning and in Google Play Store it is showing Device Certification as Uncertified.
When I type fastboot oem lock in cmd bootloader slot count, bootloader slot suffixes and one more bootloader line all are showing not found.
And yes, in Bootloader Unlock warning it is showing 'ID: Bad key'
Other than this my device is working fine, IMEI numbers and Fingerprint sensor is working perfectly.
I followed guide by tywinlannister7: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please can anyone tell how can I correct it.
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet. I am using a XT1642, I experienced this about a year ago when I was first experimenting with custom firmware.
I downloaded the September 1, 2017 security patch update but would prefer to flash it via TWRP instead of letting the system install it. However I can't even determine where it was downloaded to and I can't access the root directory anymore. Is it safe to manually flash it on an unrooted system containing TWRP, ElementalX kernel and the logo.bin boot screen fix? I'm especially concerned about flashing it on a system that doesn't pass SafetyNet.
TCUofficial said:
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet.
Click to expand...
Click to collapse
Thank you for that essential information. I won't consider it a problem since the phone doesn't have NFC, so no Android Pay support anyway. However, I need some additional info before proceeding with the update.
Do I need to get rid of the ElementalX kernel and restore the original?
Do I need to undo the logo.bin bootloader unlock screen fix?
Do I need to get rid of TWRP before allowing the system to install the security patch?
Thanks.
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
mel2000 said:
Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
Answer is NO to both your questions. You need a STOCK boot image and a stock recovery image to “patch” (by which I think you mean upgrade via an OTA) your phone.
mel2000 said:
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
In addition to zeomal's reply, your device would also need an unmodified system partition (no root, readonly, so no TWRP modifications) else the OTA will fail too.
Furthermore, I don't think the update you've downloaded is suitable for US retail devices, and if flashed might stop you from receiving future OTA updates. If you want the stock NPJ25.93-14.5 full ROM to revert to: https://androidfilehost.com/?fid=673368273298984458
Or the NPJ25.93-14.7 stock ROM: https://androidfilehost.com/?fid=817906626617945295 Of course, either of these will reset your device to stock, erasing TWRP, root and ElementalX and most likely your data, so back up. However, they should permit you to take OTA updates. Flash only in fastboot.
If you've already installed NPJS25.93-14-10, then you won't likely get the OTA update if installed on US devices.
As for SafetyNet/ device uncertified, I recall that's likely due to an unlocked bootloader. Magisk has the ability to hide the bootloader unlocked status from Safetynet, hence why when you removed magisk, the Safetynet detection saw your unlocked bootloader and therefore trips Safetynet. An easy way to get Safetynet passed is to reflash ElementalX and magisk.
I want to thank both zeomal and echo92 for their prompt and clear responses. I will address related issues before I move on.
EDIT: Used OEM Flash.bat to reupdate to June 2017 NPJ25.93-14.5, then allowed NPJ25.93-14.7 to be installed from Moto. All went well with an unlocked bootloader. Didn't lose any apps.
- TWRP (gone)
- ElementalX (gone)
- Logo.bin fix (gone)
- SafetyNet (failed - due to unlocked bootloader)
Thanks again to all.
As mentioned in the title, I just got the Oreo update with the January patch. I'm currently running Nougat (December Patch) with just Magisk installed.
I have 2 questions :
1. If I end up installing this OTA, will it succeed?
2. If it does install, will the phone bootloop on reboot?
I don't mind doing a factory reset but I've read that has lead to people losing the OTA.
Also, I don't have TWRP installed. I just booted into TWRP to install Magisk so I can't uninstall it.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I was wondering the same thing. I've read the github link but im not sure if I should update like it is explained in there, especially since it's a new android version and not just a regular security patch. Should we follow it anyway? Im not too familiar with A/B partitions.
I have follow the GitHub way to make ota, but my uninstall magisk restore images have fail,show stock backup does not exist!what can I do now.
linwai said:
I have follow the GitHub way to make ota, but my uninstall magisk restore images have fail,show stock backup does not exist!what can I do now.
Click to expand...
Click to collapse
Did you install magisk via twrp?
After trying the A-B method (uninstall/restore image) I have an error message at second step of the Jan security patch installation. I'm not sure what's the process, don't want to go into bootloop. Cheers
Firmware Finder shows there's a new update available for my BTV-W09. It's B355 dated 06/05/18. It's a small OTA, only 190mb. Has anybody installed it? Does anybody know what's in it?
Firmware Finder provides the changelog. It has the June security patches.
No netflix hd update? ****!
How install? I don't remember. [emoji28]. Thanks in advance.
Enviat des del meu ONEPLUS A6003 usant Tapatalk
Anyone have any luck applying this update with TWRP recovery? Looks like it is going to require a flash back to stock to apply?
I was only able to install it with stock. Even then, it had to be the full install, not the OTA update. That install locks the bootloader and unroots; so I then had to re-unlock, which of course wipes the entire device, and then restore from a Google and Titanium backup. Not sure updating is worth the pain. really.
My rooted tab is now threatening to install this update when I reboot. Does anybody remember how to stop a firmware update when it wants to update on reboot?
I don't think there's much to worry about as if you're rooted with TWRP, it'll just reboot into TWRP and wait for you to manually apply it, if you can find it on the file system.
I'm currently trying to apply B356 which was recently released. This minor update contains the July 2018 Google security patches. The last time I did this from B351, this is what I did:
Via TWRP, Installed the 2 full OTA zip files for B352 downloaded with firmwarefinder. This replaced TWRP with the stock recovery but did not wipe my data.
Rebooted, and applied B353 via the normal OTA through settings. This installed the B353 full package (2.52GB).
Reinstalled TWRP with fastboot (twrp_BTV-W09_5_greatslon.img)
Booted to TWRP & installed Magisk
Re-enabled the 5GHz wifi radio
However, this doesn't seem to be working with B356 thus far. Installing the Firmwarefinder zip files failed (at least update.zip did, I didn't try the other two) so I installed the FF B352 images mentioned above. However, applying the stock OTA through settings wants to install 3 patches (B353, June 18, July 18) of size 786MB. They downloaded successfully but then it fails to apply during the reboot.
Anyone else have any luck? What did you wind up doing?
Thanks!
Every time I've applied an update, I ended up locking the bootloader and then having the phone wiped when I unlock the bootloader. I'd love to find a way to update without locking the bootloader. If you find a way to that with this update, please let post how you did it!