I tried the searches, i tried the restore to stock, i tried windroid, i tried everything.
i have a moto x pure with originally 6.0.1 but it was with a unlocked bootloader. now i want to restore it back. i tried everything i could find to relock it and now i am trying the system images from motorola but i keep getting this ******* response
tail_XT1575_MPH24.49-18_18\CLARK_RETUS_MPH24.49-18_18_retus_US>fastboot flash
rtition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.003s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.354s
can someone please help me. the bat all files are not working and now manually isnt working either. step by step instructions would be appriciated. ive been trying at this for 5 hours now
You cannot lock the bootloader again. Once it's unlocked it's a done deal. Warranty wise
Sent from my XT1575 using Tapatalk
You can relock... But there is no reason to. If it is not locking you are not 100% stock. I think there was discussion on this in the firmware thread.
Problem with 'gpt.bin' not flashing is you are trying to downgrade, regardless of an unlocked bootloader or not, you cannot downgrade the partition table (gpt.bin is the partition table). If you want to relock you need to factory default in recovery, flash the stock ROM that is the same or newer version than you have installed (you cannot downgrade), and you must use the 'fastboot oem lock begin" commands to start and 'fastboot oem lock' to end the flashing sequence.
Although this process works, it isn't really relavent and means nothing because Moto will always know it was unlocked (the generation of the unlock token voided your warranty, whether unlocked or not), your bootloader status will never return to 0 and your software status will always show modified.
Be aware that we have seen a few Moto G 2015 devices get bricked by this, if somehow the bootloader version doesn't match the ROM (can happen... we have seen it more than once) due to flashing multiple stock images or failed/improper OTA flash, and the bootloader gets locked it becomes insta-brick and won't go past the bootloader and won't unlock again. It seems the only way out is to flash a newer official stock image if/when one becomes available.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my 0PJA2 using Tapatalk
So you either haven't flashed anything, or you returned to stock and took an OTA and it went official again (lucky you, it's inconsistent).
Bootloader status can never be returned to 0.
Sent from my Motorola XT1575 using XDA Labs
Jessooca said:
I have the latest July update (minor sec update) my phone is stock and I have the latest firmware, spoke to Tom (rootjunky) and he was stumped as well. I have the same issue and I'm not downgrading anything, nor flashing an older firmware, yet still have your same issue. Unlocked the bootloader and that didn't help either.
Probably have rootjunky remotely look at my XT1575 and see if he can figure it out..... I will let you know the issue when we know.
Curious.... Does your phone always startup and go into that bootloader/fastboot screen??
Click to expand...
Click to collapse
It did for a bit not but anymore. It was doing bootloops but when I put back twrp and reflashed a ROM on XDA it stopped doing it
Sent from my 0PJA2 using Tapatalk
ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.
Jonathanlc2005 said:
ok an update.
so i downloaded from here http://www.gammerson.com/2015/09/restore-stock-firmware-rom-in-moto-x-style-pure-2015.html which is the same as a link from XDA and already had the download.
so i flashed it three times to assure it was flash entirely.
1) first time it just flashed the software
2)second time the radios started to work
3) third time was just to make sure it worked properly
it started to change the bootloader date and returned the unlocked bootloader message. after i did that, everything worked the way it was supposed to minus the bootloader lock.
it gave me a notification that there is an update available for marshmallow, downloaded and flashed automatically so i think im in good hands so far. i guess everything is ok now and after nougat, ill just root it back again.
Click to expand...
Click to collapse
Try windroid tool kit it works except for root but it does have a bootloader relock to it.
Related
GO GO GO!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
YOU NEED YOUR BOOTLOADER UNLOCKED TO CARRY OUT THIS PROCESS. It's easy using fastboot, which is included in the download below. The instructions on the Motorola site are very straightforward - visit this page to get started. Unlocking the bootloader will wipe your device.
This Superboot installs SuperSU version 1.80. Note that rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Click to expand...
Click to collapse
Full Guide
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/ (Thanks to helinhof)
http://t.co/7icWLuTwSW (Thanks to munchy_cool)
"PaulOBrien 3h
Nobody has rooted the Moto G yet? Well that won't do will it. Superboot uploading now... pic.twitter.com/6B9qcA6kfs"
"Moto G root tool online soon. It's my usual process, a Superboot image..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/PaulOBrien
Greaatt.. wainting for this..
bgochoa said:
Greaatt.. wainting for this..
Click to expand...
Click to collapse
We are two!
Moto G - Rooted
Here we go guys!
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
its a go http://t.co/7icWLuTwSW
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
Nice one...I´ve been waiting for this...the process took less than 10secs. Thanks!
Does it works in the german version?
FighterFX said:
Does it works in the german version?
Click to expand...
Click to collapse
It worked for me on my German Retail Moto G.
alex1301 said:
It worked for me on my German Retail Moto G.
Click to expand...
Click to collapse
Mine too, 14.71.8.Retail.en.DE
has anyone got this to work with the tesco version?
so how much space is there for system and for the apps
on 8 gb version
Props and thanks to [email protected], i can now consider buying this phone
i have a problem .... mmy cel is unblock but no rooting u.u
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
can confirm that this is working, done in under a minute
burma said:
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
Click to expand...
Click to collapse
I was able to get it working only after reflashing stock http://forum.xda-developers.com/showthread.php?t=2542219&page=3 then encrypting and then reflashing superboot.
So maybe it is worth updating instructions:
1) Unlock bootloader (wiping all data)
2) Encrypt your phone
3) Flash superboot
Thanks! only a question... If i unlock the bootloader and root the moto g, will I still receive the kitkat OTA update?
still not rooting
unlocked the boot loader, tried to root with super boot, but didnt work, flashed to generic uk, tried to root again and it still wont say rooted or show the su app, please can someone help?!
Rooted...wireless tether working with wifi router app. However, I got notified of 4.4 update today and it downloads, starts install, then fails.
I did an OTA update, and SMS stopped working and also my screen wouldn't shut off automatically (nor when I hit the button).
So I tried flashing back to the 4.4.2 version from sbf.droid-developers but I got an error.
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Now I'm stuck in AP Fastboot. It says Battery Low, but I can get it to say Battery OK by plugging it into the wall and then rebooting it or something weird like that. It's hard to get it to do it but it's possible.
Anyway, it doesn't matter what version I try to flash now, boot and system give me errors when trying to flash.
Partition (boot) Security Version Downgraded
It seems like I need to be unlocked in order to downgrade, but to unlock I have to get out of fastboot. Am I perma bricked?
Not sure how I fixed it to be honest, but I'll try to recall some things that might help others.
At the end of a long road of reinstalling drivers, fighting with the low battery, trying various versions of the firmwares, and trying multiple scripts/tools, I got it to work.
I ended up using (not sure how much of this is relevant);
Motorola Drivers from the Motorola Device Manager
RSD lite, v6.1.4
The newest 4.4.2 firmware
eulogy1337 said:
Not sure how I fixed it to be honest, but I'll try to recall some things that might help others.
At the end of a long road of reinstalling drivers, fighting with the low battery, trying various versions of the firmwares, and trying multiple scripts/tools, I got it to work.
I ended up using (not sure how much of this is relevant);
Motorola Drivers from the Motorola Device Manager
RSD lite, v6.1.4
The newest 4.4.2 firmware
Click to expand...
Click to collapse
The only part of that which would be relevant is if you did in fact use the newest 4.4.2 firmware. This would be 18X.46.15. The reasons that is relevant is because (1) you titled your original post that you were attempting to un-do the most recent update (which you have now successfully installed again) and (2) If you are on the .15 firmware and not .10, you will not be able to unlock your bootloader now. You may or may not be aware of that already. Otherwise, you did exactly what was needed to make your phone operable. :good:
netizenmt said:
The only part of that which would be relevant is if you did in fact use the newest 4.4.2 firmware. This would be 18X.46.15. The reasons that is relevant is because (1) you titled your original post that you were attempting to un-do the most recent update (which you have now successfully installed again) and (2) If you are on the .15 firmware and not .10, you will not be able to unlock your bootloader now. You may or may not be aware of that already. Otherwise, you did exactly what was needed to make your phone operable. :good:
Click to expand...
Click to collapse
I used the newest 4.4.2 on that site (which is .10). I was getting errors before and the only glaring difference is the version of RSD lite. I dunno why it worked then and not before.
eulogy1337 said:
I used the newest 4.4.2 on that site (which is .10). I was getting errors before and the only glaring difference is the version of RSD lite. I dunno why it worked then and not before.
Click to expand...
Click to collapse
Well, now that you mention is, I suppose an older version of RSD Lite might generate that error. .10 is the money version of 4.4.2 - if you have .10, you can still unlock your BL by following the tutorials for KitKat to do so. .15 is the -newest- version, but primarily, it's an update to fix the exploits that allow .10 to be unlocked and rooted, so don't do it before you unlock. Once you are unlocked, .15 is fine - you will still be able to install a custom recovery, root, etc. I would install the recovery before you update as well, personally. Good luck!
netizenmt said:
Well, now that you mention is, I suppose an older version of RSD Lite might generate that error. .10 is the money version of 4.4.2 - if you have .10, you can still unlock your BL by following the tutorials for KitKat to do so. .15 is the -newest- version, but primarily, it's an update to fix the exploits that allow .10 to be unlocked and rooted, so don't do it before you unlock. Once you are unlocked, .15 is fine - you will still be able to install a custom recovery, root, etc. I would install the recovery before you update as well, personally. Good luck!
Click to expand...
Click to collapse
I'm still having most of the issues that made me try to un-do the update anyway.
Texts take ~20 mins to send out. Phone calls seem okay. Google Play Store freezes non-stop (downloading/installing new apps takes forever, usually gets stuck downloading around 75% regardless of the size of the app). If I go to Developer Options, the Settings app locks up until I close it (I wanted to see if I could switch to/from ART). Battery might be draining faster too.
I'm afraid to get stuck back at the fastboot. What should I do?
What can I do with this? I installed the update and I wasn't able to root my xt907.
As stupid as I could be, I went inmediately to RSD with the same ROM I flashed just a couple of hours ago (want don't have the most recent update, I think).
Stuck at Fastboot. Fastboot Reason: Flash Failure
When I try to re-flah, it says:
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed from GPT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to fix the Brick of RSD (at least this worked for me)
A collab I want to do... This solved me right now my problem
In the xml file (assuming you removed any lines which contains “GetVar”, “var” or “oem”), delete the following lines:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="5B3FD782141145E4BD1C9270D954AFF1" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="8514ED883150B7A0579F9431CD872B39" />
Click to expand...
Click to collapse
I don't know what are these files, but my phone came back from death :fingers-crossed: :laugh:
If this helps anyone, just... Yay!
Attatched, how it goes the XML file
I had a similar issue, and now i believe i need the 46.15 firmware to get back up and running. But it doesn't seem to be something i can find online.
There is a thread with the .15 FW in the general section.
Sent from my HTC6525LVW using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seems like our bootloader can be unlocked now via developer options. Do y'all think we can get root soon?
Thats in the 5.0.2 dev options as well, still doesnt allow
wait, so the verizon model does NOT have a root option? crap. guess i'll be returning mine for another carrier
does any other phone carrier have this problem? or is it just verizon? cause im just mostly getting the phone to use as a media player device but I prefer to still have root.
Get the Boost variant, it has root.
Sent from my XT1528
Will boost version work with a Verizon SIM and Verizon LTE?
wpbear said:
Will boost version work with a Verizon SIM and Verizon LTE?
Click to expand...
Click to collapse
No, it will not. It will also not work with domestic GSM networks.
does anyone know if the Sprint version has root? It seems the only colour boost has is white and i really dont want a white phone
it's unlocked going to try an root ill post back with result after you take the update immediatley go into dev hit oem unlock then go into fastboot an it will be unlocked i messed up an rebooted it an it factory locked itself so
So were you able to root it?
It didn't have the device lock on it so I'm assuming but I couldn't do it due to reboot n relocking bootloader is my presumption
Sent from my XT1528 using XDA Free mobile app
So the method you are suggesting is to download and take the 5.1 update. After it updates and boots up go to developer mode and check OEM Unlock. Then fastboot and it should show that the boatloader is unlock? Is that correct? Then in fastboot flash recovery.img (TWRP) and then using TWRP flash SuperSU, right?
---------- Post added at 01:08 AM ---------- Previous post was at 12:56 AM ----------
@Soldier1184 - I guess my unit was up for two updates. One to update to the latest 5.0.2 and then another to 5.1. Before I updated to the latest 5.0.2 I had checked off on the OEM Unlock box then took the 5.0.2 update. After the update and the next boot up I checked OEM Unlock and it was still checked. I then went into fastboot but it still says that it was locked. So I have a few questions. 1) Should I not let it boot up after the update and go into fastboot first? 2)Or the method you are suggesting only works after the 5.1 update? I know you don't have a definitive answer to those but I was just wondering what you think and since I haven't updated to 5.1 yet I can give a test.
When I did it it was unchecked then I updated after that immediately checked oem unlock my fastboot didn't state locked or unlocked it wasn't even there then I rebooted again after I unchecked it it stated locked so I switched oem on again in dev menu still no go so since I can't test it again take the update do the steps n pm back with results if it doesn't say device locked in-between charging n USB thing then reboot leave oem checked n fastboot again n post back
Sent from my XT1528 using XDA Free mobile app
No go...I install the update...upon rebooting I hurry and got it go into fastboot but it already says "Locked"....I reboot then got into developer tools and rechecked OEM Unlock...reboot into fastboot...still says "Locked"...oh well...guess I'll have to wait. The worst thing is that I just cracked my RAZR Maxx's screen and now I have no way to tether....
I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!
deleted
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems
I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.
I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!
scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
TLDR: OTA to Nougat refuses to install on XT1625...because Consumer Celluar?
So here's the long version... Bought a refurbished Moto G4 XT1625 (not amazon) with the intention of using it as a learning aid for unlocking, rooting, etc.
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it. However, I captured the file, pulled up the stock ROM download from the official Moto website after checking that the build numbers matched, and proceeded to unroot and reflash that stock ROM (except for bootloader and gpt files). I booted back up, got the notification again, and hit OK. Fail. So I booted into recovery and tried to sideload OTA (using "Blur_Version.24.31.65.athene.retail.en.US.zip" pulled from "com.motorola.ccc.ota-20171028-062630.tar.gz"). Fail.
Maybe somehow I misread the multiple how-tos out there, and I'm screwing something up in the process here?
After numerous rinse and repeats of the above steps, I cannot for the life of me get past this damn error which (assuming my inexperienced eyes are reading it properly) seems to say that the current CCMyConsumer.apk on my phone is somehow wrong (corrupted/incorrect/missing?), and so the OTA's response to me is a big FU.
Verifying current system...
E3005: "/oem/app/CCMyConsumer/CCMyConsumer.apk" has unexpected contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This seems.......weird to me? If I have both the stock ROM and am using the actual OTA, why would a random provider's app be screwed up, much less screwing up the update.
Also, if it matters at all, here's that particular directory tree in a file manager...an apk file doesn't appear to even be there?
Could a lack of existence be the "unexpected contents?"
So, the question as in the TLDR, any ideas on what the cause or solution to this error or overall OTA issue could be? I'm at a loss.
The only other item I noticed is that my "Settings" now crashes if I attempt to navigate into "Apps" within its menu. However, if I navigate directly into an App's info page via the app drawer, I can access those. Not saying this is related, I have no idea, but being the only other oddity, and since it persists through flashes, I figured I'd mention it (even if unrelated, I am still curious what could be going on there too...).
Thanks in advance for any help, education, or peace of mind. =P
NobodyByChoice said:
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it.
Click to expand...
Click to collapse
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
lmacmil said:
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
Click to expand...
Click to collapse
Thanks for the advice, sorry for the late reply as I was out of the country. I do understand the need to get rid of TWRP first, but I'll read through your recommended threads and see what happens!