Database Users

[SOLVED] Stuck in TWRP Recovery after failed Update to Kitkat

So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom

tom1807 said:
So now I am little bit confused.
Downloaded the OTA update from the Google server copied it to my N7, applied the update from within TWRP 2.6.3.1.
In fact, it was running through until almost the end (I thought, wow, finally an update which works).
But then Error message:
"Error executing updater binary in zip 'sdcard/goomanager/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35'
Error flashing zip 13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35"
Reboot System brings me back to Recovery TWRP.
Somehow I have no clue what to do next.
Can give someone a hint?
Cheers
Tom
Click to expand...
Click to collapse
i am in the same boat

Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there

tom1807 said:
Not really helpful, but I found a post that TWRP could be the culprit. (maybe doesn't work in CWM also)
Found some comments here: http://www.droid-life.com/2013/11/1...krt16o-official-update-for-nexus-7-2012-wifi/
I boot now into the bootloader, try to flash from there
Click to expand...
Click to collapse
TWRP is fine. Myself and others have installed the OTA via TWRP without issue. Did you download the OTA with Goomanager? I can't think of another reason the OTA zip would be in there, but let me know otherwise.
If that is the case, download the ota http://android.clients.google.com/packages/ota/google_nakasi/13088e35942c77e4752aa1fdf51d54472509b941.signed-nakasi-KRT16O-from-JWR66Y.13088e35.zip from Google's servers, push it to /sdcard/Download/ via adb and try again.

Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk

tom1807 said:
Thanks, but I downloaded from the Google server.
During installation I get metadata_set_recursive: error
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you modified any system apps, build.prop, kernel, etc?

No, not at all. Only root and twrp
Edit:
Exact error message: set_metadata_recursive: some changes failed

Problem solved:
Followed this guide (except the bootloader-grouper-4.23.img and KitKat is booting

Nexus 7 2012 automatically boots into recovery
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.

nolan111 said:
My Nexus 7 automatically re-boots into recovery. The previous steps was not very helpful.. Please advise.
Click to expand...
Click to collapse
He flashed the 4.3 JWR66Y factory image and then installed the OTA.

comminus said:
He flashed the 4.3 JWR66Y factory image and then installed the OTA.
Click to expand...
Click to collapse
Yup that is what I had to do. I flashed the factory image with WugFresh's NRT. I accidentally deleted the OS as well from my tab. Thankfully I had saved a copy of TB on my PC. TB saves the day yet again. However, I was still not able to sideload the OTA for KitKat. I keep getting Error: Device not found error message on command prompt? I guess I'll wait for the factory image to be uploaded by Google and then flash the files.

[OBSOLETE] Root Android 7.0 Nougat after clean Install - Just use TWRP 3.0.2.1

Edit: Obsolete now. Twrp 3.0.2.1 is Out.
For now TWRP cant decrypt Android Ns vendor images so you cant flash SuperSU. So why not flash back old vendor to root the device and reflashing the NRD90M Vendor?
It works great. I root my clean install from factory image Android 7.0 NRD90M:
1. Flash the just released NRD90M via Fastboot
2. Reboot and set up your device.
3. Reboot to fastboot and flash vendor_mob30w.img by entering: fastboot flash vendor vendor_mob30w.img
4. Boot TWRP 3.0.2.0 temporary by entering: fastboot boot twrp-3.0.2-0-flounder.img
5. In TWRP copy UPDATE-SuperSU-v2.76-20160630161323.zip to your device and install it.
5.1 If you want to use adaway flash also AdAway_systemless_hosts_v2.zip.
6. Go back - back - back and reboot your device to fastboot.
7. Reflash the original vendor vendor_nrd90m.img by entering: fastboot flash vendor vendor_nrd90m.img
8. Reboot your device. Its rooted!
Extract the vendor files from the factory images or take these just extracted files from my google drive:
Download vendor_mob30w
Download vendor_nrd90m

Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.

corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
Is that one system less?

edit: nevermind this

osnapitsjoey said:
Is that one system less?
Click to expand...
Click to collapse
Yes CFAR is systemless.

If you were not a very smart man and encrypted your device during the install will this method work? Does it allow you to take monthly security updates still?

corkiejp said:
Even though TWRP can not decrypt nexus 9 nougat.
As the final release is out, TWRP will probably be updated for it soon.
You could still use it to flash supersu from OTG or sideloading the zip. Without changing vendor image.
Alternatively there is CFAR method.
Click to expand...
Click to collapse
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.

GialanG said:
I don't know if what I did was right, but without changing vendor image my N9 got boot loop at TWRP welcome screen. TWRP could only run properly after flashing old vendor image.
Click to expand...
Click to collapse
It will bootloop and eventually load. At least that is what it did on the previews. Haven't tested on final release.
You still can not modify/read encrypted data partition, hence OTG or sideloading of zips.
Edit:- Just tested and it eventually loads.

twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.

corkiejp said:
twrp-3.0.2-1-flounder.img now available supports encrypted Nexus 9.
Click to expand...
Click to collapse
Cool, thanks ! Is there also a way to decrypt the tablet ?

TheLonelyCyborg said:
Cool, thanks ! Is there also a way to decrypt the tablet ?
Click to expand...
Click to collapse
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.

corkiejp said:
Make sure you have flashed latest supersu.zip which has encryption flag disabled.
Then format your data partition.
For future updates make sure to flash supersu again before booting your tablet other wise it will re-encrypt.
---------- Post added at 01:44 PM ---------- Previous post was at 01:33 PM ----------
@Donald Nice Maybe you should update the first post, now that a working TWRP is available for encrypted Nexus 9.
Click to expand...
Click to collapse
Thanks @corkiejp it worked like a charm !

Can you please update this guide?
Sent from my Nexus 9 using Tapatalk

Twrp bootloop
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?

lawlor059 said:
I stupidly updated my nexus 9 (wi-fi) to nougat which I think is awful. I flashed it via wugfresh as it was unlocked and rooted. Flashed back to 6.0.1. Trying to install twrp 3.0.2.1. It bootloops but eventually loads. I added a pin as it was the only way I could decrypt, I get the partition decrypted and then it bootloops again. Haven't been able to root. Now running 6.0.1 no root trying to install twrp 3.0.2.1. Should I just use 3.0.2.0?
Click to expand...
Click to collapse
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.

corkiejp said:
Use 3.0.2-0 for Marshmallow! 3.02-1 is for nougat only.
Click to expand...
Click to collapse
3.0.2-1 works perfectly fine for marshmallow.

dictionary said:
3.0.2-1 works perfectly fine for marshmallow.
Click to expand...
Click to collapse
Thanks @corkiejp. @dictionary I couldn't get into the recovery with 3.0.2.1. Entering the decrypt code would just cause it to loop again. Ignoring the decrypt code I could get into the recovery but with nothing mounted it's useless. It will install successfully but nothing can be done with it.

[JAN 2018] - Pixel/Nexus full OTA and factory images

https://developers.google.com/android/images
https://developers.google.com/android/ota

Has anyone flashed this factory image yet? Does it break TWRP and/or Magisk?
Sent from my Pixel 2 using Tapatalk

I haven't yet, but expect it to break things if you flash it like that. Though if you sideload and update from a factory image it'll do a full wipe unless you edit the flash script.
Tentatively the following process should work:
- Flash factory image after removing wipe flag
- Boot TWRP image
- Flash TWRP zip
- Flash kernel
- Flash Magisk
Everything should work normally at that point.

Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Sent from my Pixel 2 using Tapatalk

Hi, update received.

Diesel_Jeremiah said:
Wouldn't the OTA not work since the system has been mounted via TWRP? Flashing the factory image should update fine and OTA shouldn't be needed (unless I'm wrong).
Click to expand...
Click to collapse
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.

Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!

guapinoy said:
Here's what I did. I uninstalled Magisk using the uninstall.zip. I flashed both stock boot.img and dtbo.img. I adb sideloaded the OTA which was walleye-ota-opm1.171019.013-5ccf0b20.zip approx 1.1 gig. I'm updated to Build OPM.171019.013 Jan 5 Patch.
I then flashed TWRP.img, installed TWRP.zip, then installed Magisk 15.2.
If anyone has an easier method. Let me know!
Click to expand...
Click to collapse
Magisk and TWRP working correctly?
Sent from my Pixel 2 using Tapatalk

Diesel_Jeremiah said:
Magisk and TWRP working correctly?
Click to expand...
Click to collapse
Yup.

Would love to see if this patches the Verizon bootloader unlock.

PuffDaddy_d said:
This was my understanding as well, but if you're side loading the full image, then it probably wipes everything and you have to nandroid backup/restore. Just a guess at this point though. We need a guinea pig.
Click to expand...
Click to collapse
Here is how I updated: [DEC 2017 to JAN 2018 Update] How I updated successfully

So far only one report of receipt via OTA? I had to sideload Dec, really hoping to just get these OTA going forward.

I've found that using old ADB tools will not flash the factory image properly. I was using a tool that an XDA member provided that had adb binaries from 2015 and kept getting errors when trying to use the flash-all.bat from the factory image. If you guys get stuck with something, update your adb and fastboot tools from the latest platform tools. It will save you a headache. If you want step by step instructions of what I did, I can provide them.

Hmm, I'm failing SafetyNet now.

Lightn1ng said:
Hmm, I'm failing SafetyNet now.
Click to expand...
Click to collapse
Did you follow Diesel's method or was this after you soft bricked your phone?

PuffDaddy_d said:
Did you follow Diesel's method or was this after you soft bricked your phone?
Click to expand...
Click to collapse
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data

Lightn1ng said:
I did the following:
- Ran flash_all from the factory image
- fastboot boot'd TWRP
- flashed the TWRP zip + magisk + FLASH kernel
- formatted /data
Click to expand...
Click to collapse
Formatting data decrypts it, that may or may not be why it's failing.

Telperion said:
Formatting data decrypts it, that may or may not be why it's failing.
Click to expand...
Click to collapse
Ooohhhhhh. How do I get it back to encrypted?

Lightn1ng said:
Ooohhhhhh. How do I get it back to encrypted?
Click to expand...
Click to collapse
Same as before, but don't format your data partition.

no OTA for me yet. I heard sideloading results in lag but who knows.
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/

Magisk on Oreo

I can't seem to install Magisk 16.0 via TWRP 3.2 on the Oreo update. It installs, but enters a bootloop. Why is that?
Also TWRP said cannot mount /data. How to fix this?
"Failed to mount '/data' (No such process)"
Also cannot format data this way
EDIT: Installed Magisk 16.4, no change. Also just realized that internal storage is inaccessible.

I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.

+)KEV1N(+ said:
I upgraded and got in a bootloop. Then I remembered I had Nougat substratum themes active. Only way I got it booting is by factory resetting it.
As for installing magisk with root access, you can try the TWRPless method. I got it working on mine. All you need is the stock boot image and a computer to use adb.
Steps on installing magisk on Oreo:
1. Put the boot image somewhere you can easily find it for later use
2. Install the latest magisk manager apk on your phone
3. Enter magisk manager and install magisk (root) using the "patch boot image" method.
4. Send the patched boot image to your computer
5. Now reboot into bootloader
6. Now on your computer install the patched boot image using fastboot flash boot "patched boot image"
7. Reboot and profit!
Hope this helped you out. Good luck
Click to expand...
Click to collapse
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...

GBry said:
Already tried. Bootloop also, probably since magisk manager used v 16.0 instead 16.4.
I noticed that 16.4 actually signed the boot image using test keys, as opposed to the 16.0 which didn't.
I'm a bit frustrated here man
EDIT: I have substratum but I don't have any of the themes active, so the first one is a go. Installing magisk however...
Click to expand...
Click to collapse
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
kekley said:
For anyone who tries the above method and has their fingerprint sensor stop working as I did, use a root file manager to remove the following directory/file:
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
and reboot.
Certain modules required me to delete those files again, and some others broke the fingerprint functionality until they were removed and I rebooted twice. I hope someone can find a complete workaround soon.
Click to expand...
Click to collapse
Did you try wiping your cache?

+)KEV1N(+ said:
So, now you're stuck in a bootloop?
Also, yes I used version 16.0 (you can never go wrong with a stable release)
---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------
Did you try wiping your cache?
Click to expand...
Click to collapse
Technically, I'm not now, since I flashed the original boot.img
But yes, if I installed magisk either via the patched boot.img or TWRP, I get a bootloop
Actually idk if bootloop or nah since I can't access logcat via adb, but it's on the bootlogo for like 5 mins (regular start time is 30-ish sec)

+)KEV1N(+ said:
Did you try wiping your cache?
Click to expand...
Click to collapse
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?

kekley said:
That was the first thing I tried, in fact. I have to use magisk 16.4 as well or else the fingerprint reader refuses to work no matter what. You haven't run into this issue at all? What's your setup if I might ask, and did you patch the boot image from the oreo update zip to install magisk?
Click to expand...
Click to collapse
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!

+)KEV1N(+ said:
I just watched a video tutorial to root it and keep stock recovery. Another thing to take note of is that I upgraded to Oreo using TWRP instead of stock recovery (yes, I didn't think it was possible on this phone).
Once I upgraded to Oreo, it reverted back to stock recovery. As you read above, I got stuck in a bootloop because I had substratum themes active, but I fixed it by using the stock recovery to factory reset it. (It's also nice to factory reset after a major OS upgrade so that you don't encounter any problems with old files)
If anyone's interested in a video, here's the one I watched:
Note: always make backups of your personal data!!!
Click to expand...
Click to collapse
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?

GBry said:
So you did a factory reset and magisk is working properly? I can boot twrp without installing, but still no go using that method. Yes, I also used TWRP to install oreo, I didn't think it was possible either, but it finished flawlessly. Except the magisk thingy.
Can you mount /data in TWRP after oreo?
Click to expand...
Click to collapse
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
How did you manage to update via twrp? I get an error when I try it.

kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.

+)KEV1N(+ said:
To answer your first question: yes, I did the basic setups, restored my apps and then installed magisk the way I explained above.
Secondly, did you try installing the latest TWRP? Because I didn't want to install TWRP until I have the stock recovery and TWRP with the latest Oreo kernels.
I saw this morning that shakalaca uploaded TWRP with the latest kernel, so I boot it through fastboot and saw that by default the following partitions were mounted: /recovery, /data, /cache. I tried /system to see if it works and it does.
I hope this answers your question and good luck!
Click to expand...
Click to collapse
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
Click to expand...
Click to collapse
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
Yes, I searched through my history and then found out that you gave me the same link, so thank you. Updated my 2nd to last post about the condition... Do I REALLY have to factory reset? Sigh...

+)KEV1N(+ said:
So, I just realized I've been sending the wrong link to everyone so far. (It sent you to the "old" folder)
Here's an updated link: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
+)KEV1N(+ said:
I don't know man. I was just running the latest release of TWRP at the time and it somehow installed it like any custom rom.
Click to expand...
Click to collapse
kekley said:
How did you manage to update via twrp? I get an error when I try it.
Click to expand...
Click to collapse
Yes, actually I just did update via TWRP, it installs flawlessly. HOWEVER, it only applies to the Oreo ROM, not the N or M ROMs. N and M needs stock recovery (the boot.img contains recovery too)

I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.

kekley said:
I was able to reflash the update via twrp by modifying the update script a bit (spat out errors about the twrp recovery having a more recent build date than the update zip) Everything seems so far so good! I haven't had issues with my fingerprint yet.
Click to expand...
Click to collapse
Did you install Magisk though?

GBry said:
Wow, that's great! Can you give me the link? I can't seem to find the one for 553kl...
EDIT: apparently it's this one, isn't it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Also tried live-booting TWRP and installing magisk (leaving stock recovery), left the boot.img unpatched
Installed the latest TWRP, the /data and internal got mounted, but after flashing magisk, bootloop again (still bootlogo after 10 minutes) even after wiping dalvik.
Cache is unwipeable somehow, is this an issue?
Click to expand...
Click to collapse
Did you try clearing it with the stock recovery?

GBry said:
Did you install Magisk though?
Click to expand...
Click to collapse
With the latest twrp, yes! :good:

OPPS28.85.16-2 October Security Patch [OTA + TWRP]

The October Security Patch for those on OPP28.85-16 has come out.
You can sideload the OTA if you're on untouched OPP28.85-16 or flash the TWRP zip if you've have TWRP.
Edit:
For the TWRP flashable zip, check this thread .
I removed it from this thread after I realized it's not OPPS28.85-16-2 but OPPS28.85-13-2
Notice that if you're on retca or reteu channel, or any other channel where you've got an Oreo version other than OPP28.85-16, then you should either wait for the OTA notification to pop up on your phone or flash the TWRP flashablr zip.
THIS OTA ZIP IS ONLY COMPATIBLE WITH OPP28.85-16. FLASHING IT OVER OPP28.85-13 OR ANY OTHER VERSION WILL HARD BRICK YOUR DEVICE
That is because this OTA patches the device's gpt table. So if you're not on OPP28.85-16 and sideload this= :crying::crying: goodbye Cedric
Downloads:
OTA : https://drive.google.com/file/d/1PHJqkdFgS-erSJ0jc54cTWvUrNRQWfZJ/view?usp=drivesdk
PS I removed the TWRP link, it's actually for OPPS28.85-13-2
Sorry for the bad edition, I'm sleepy and don't have a computer around.

Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16

Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?

merlinolillo said:
Flashed the twrp ota by Nzedpred yesterday and it's working like a charm. Previously I was on OPP28.85-16
Click to expand...
Click to collapse
Twrp Dirty flash works or i should do clean install?

the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?

can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery

iKnocks said:
Hi, i'm having some troubles to make my moto g5 identified when i'm gonna sideload the ota. how can I solve it?
Click to expand...
Click to collapse
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
If you were on stock a dirty flash works, if you were on a custom ROM you'll get lots of bugs
kare_meesner said:
the TWRP-Link shows a ...13-2, not a ...16-2, is this correct?
Click to expand...
Click to collapse
Yeah it's indeed OPPS28.85-13-2, Ill make a separate thread for it
PsyClip-R said:
can not update from ota package.
every time I check for updates, Moto Update doesn't recognize local packages. Had to apply patch via Recovery
Click to expand...
Click to collapse
No, that's not the way you do it. You have to install Motorola usb drivers, then install ADB/platform-tools, then enable usb debugging and connect the to the pc using the usb cable.
After you've done that you'll type adb devices and you should see your phone's serial number. If that shows up, type adb sideload ota-filename.zip

ahmedAZ said:
Twrp Dirty flash works or i should do clean install?
Click to expand...
Click to collapse
Yes, I made a dirty flash and it works perfectly

merlinolillo said:
Yes, I made a dirty flash and it works perfectly
Click to expand...
Click to collapse
you dont have any problems with gmail sync?

OTA Side load not working for me. Get Error 7.
Downloaded earlier that day the twrp File and installed, but then I saw that this was -13-2. Completely delete my G5 again and installed 85-16 again.
Now downloaded the OTA File, in TWRP used ADB Sideload (adb devices showed my G5) but ended with Error 7.

freeZbies said:
Have you installed the usb drivers from Motorola's website?
If you didnt, then do it, but if you've already done so and still the phone is not detected, type %tmp% on your file explorers address bar (assuming you're on windows) and and then search for .msi fules. Find the .msi correspondent to your Motorola drivers and install it mannualy.
Now it worked, thank you btw
Click to expand...
Click to collapse

woozie.2007 said:
you dont have any problems with gmail sync?
Click to expand...
Click to collapse
Not at all. Gmail sync is working fine at me

merlinolillo said:
Not at all. Gmail sync is working fine at me
Click to expand...
Click to collapse
for me doesnt, is syncing after half an hour or even one hour, but if i unlock the screen is syncing in few seconds

can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working

Street_Fighter said:
can you upload full oreo stock rom after october patch?
I need it to relock bootloader , other roms not working
Click to expand...
Click to collapse
I haven't heard of that being available out there, but u can relock using the firmware provided in this thread and apply this OTA afterwards, that way you'll have a relocked bootloader and will be in the latest security patch, although if you're not on retus/retbr/retin I recommend you to find a firmware specific to your channel (even if it's an old one) and relock your bootloader using it, and then apply the OTA's that pop up on your notifications, so as not to relock the bootloader with a firmware from another channel, which will prevent you from receiving future otas.
But if you're on one of the three quoted channels you should be fine when fastbooting this firmware.

this update fix the wifi tethering of third-party applications?