Related
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Well it's like anything. If you don't know why you need something you probably don't need it
Sent from my HTC One using XDA Premium 4 mobile app
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
the phone never come unrooted .. you never had root installed properly
when it's flashed correctly from recovery it will not just go away
http://download.chainfire.eu/396/SuperSU
Flash that from recovery and you'll be rooted
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
bloodyniceben said:
I had SuperSU installed, everything was fine, anything I did with the phone worked. After a week it said the SU binaries were missing, and you couldn't get into SuperSU to do anything, but previously you could. If the phone was never rooted correctly like you say, i would have had this problem from the start.
Also after rooting I used a root checker which said I was rooted, but after this Su binary issue started, it said I wasn't rooted.
Still, I'm back to unrooted now, and the only reason I did it was to get Sense 6, which has since come out as an update, so I'm no worse off
Ben
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
This is a rom issue not a root issue. Could have also been an issue with the kernel. To be honest if you dont really use the root functions then there maybe no need for you to have it. To be honest most people dont really need root. They just wanna seem cool with some things they can show off on their device instead of using it for anything important or handy. I would advice to judge for yourself. Take the extra options/security risk and weigh it against remaining stock which has less options/secure.
I agree with the previous post, if you don't know what it is, you probably don't need it. As far as SuperSu disappearing, it sounds like either you didn't install it correctly or something changed. The ideal way to install SuperSu is to install via the recovery. And even so, if you reinstall your OS, you will need to reinstall SuperSu. Software does not simply disappear, something had to be done to hasten it's departure. An easy fix to your issue would have been to download the SuperSu zip package from http://download.chainfire.eu/supersu, and install it via your recovery. What I personally don't like about locking a bootloader is that now it says TAMPERED at the top of the screen.
Your issues seem to be with the restoring to stock process which HTC do make a bit convoluted, triggered by the root error not rooting itself.
Now to answer your question: My main reason for rooting is I want to take fine grained backups. Second is lots of clever people have come up with mods and improvements I like to install over the stock Sense ROM.
If you don't need anything that needs root, no need to root. Simple as that.
bloodyniceben said:
I rooted my phone a week ago, I kept with the stock Rom for a few days, then installed a Renovate sense 6 Rom which seemed to work well. I had SuperSU installed, plus a few other apps, but then all of a sudden I got an error message when trying to open SuperSU saying the binary was missing, so I downloaded a root checker which said I wasn't fully rooted! After looking on the forums to find a solution I relocked my boot loader and unrooted the phone. Trying to find a stock RUU for my phone ( unlocked Europe version ) was a bloody nightmare. Also getting it to install on my phone was a pain, but probably more to do with my computer having a slow moment.
Is it really worth all the hassle when I can all go wrong in a couple of days ?
Don't think I'll be re routing again any time soon
Sent from my HTC One
Click to expand...
Click to collapse
if you want RUU search @ htc1guru.com with firmware/software version
flash same firmware again + flash custom recovery + flash SuperSu it will resolve your problem
I rooted my phone a while back (Note 3) and have Safestrap on it. I checked with root verify and it says it is rooted.
I want to be able to do OTA updates as I don't really want to be rooted any longer or have safestrap on my phone.
Is there a EASY way to remove both/all of it so I no longer get the safestrap screen when it comes on that has the unlocked symbol at the bottom of it. And no longer have a rooted phone ?
Easy way, preferred as I stated before..
Saw this and giving it a try ! ?
http://forum.xda-developers.com/note-3-att/help/4-4-4-ota-failed-27-t2949069
Well used Super Su, it says I am no longer rooted. But safestrap still shows on start up
And after I did that I checked for a update. It shows v4.2.2 and no available updates ? WTH.... It showed a update before...
Idk either I unrooted and uninstalled safestrap and factory reset my update trys 2times both times says updated failed
is safestrap realy there. i had the same problem and installed traingle away and it removed the safestrap screen.
To Un-root your phone
You'll need to use Odin. After using Odin it will still say custom after the first boot, just re-boot and you'll be good.
I used Super SU, and unrooted. Did check and it says I am not rooted.
But I think the reason it is failing to install 4.4.4 OTA update, is that the safestrap is interfering with the installation..
So if I want to get safestrap completely off of my phone how do I do that > I have been searching the forum, and still searching,,,
Trying to find Stock Recovery Files for the SM-N900A 4.v if possible.
Then I can install via odin ?
Thanks..
Is back to full stock,but I can't update for 14 more hours.
Wish there was a way to push the update..
Spidious said:
Thanks..
Is back to full stock,but I can't update for 14 more hours.
Wish there was a way to push the update..
Click to expand...
Click to collapse
Turn your network time off and switch it to the next day and it shoukd allow you to update again
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
---------- Post added at 03:35 AM ---------- Previous post was at 03:32 AM ----------
Spidious said:
I rooted my phone a while back (Note 3) and have Safestrap on it. I checked with root verify and it says it is rooted.
I want to be able to do OTA updates as I don't really want to be rooted any longer or have safestrap on my phone.
Is there a EASY way to remove both/all of it so I no longer get the safestrap screen when it comes on that has the unlocked symbol at the bottom of it. And no longer have a rooted phone ?
Easy way, preferred as I stated before..
Click to expand...
Click to collapse
Lol you might as well not be on xda if you going to go stock with no root. 4.4.4 OTA official is like a death sentence right now. And you will be hitting your forhead wishing you didnt do that later.
But to answer your question, just uninstall safestrap from the app, and use supersu for full unroot. Or just Odin back with NC2 tar files from the threads. Odin back to NC2 should be no problems with the OTA
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Well when I had my other Samsung phone I use to install updates all the time, different roms or what ever.
But now I just want to be stock, and knew all the people on this forum do it a lot. So this is where I asked for help...
It is on 4.4.2 and says now that no update is available ? I have already tried the date change trick ! Strange I can't get a update now...Wonder why ?
Now it says I can check again in 735 hours ?
Spidious said:
Now it says I can check again in 735 hours ?
Click to expand...
Click to collapse
That is kinda weird in SuperSU did you disable OTA updates?!? But y you want stock 4.4.4 rom, as AT&T note 3 users there may not b a root or boot rom walk around for long time maybe even tell lollipop 5.0 or maybe never cause note 3 has been dead silence since 4.4.4 released almost like people stop using this device an goin to the note 4... Hopefully there will b a note 3 bootloader exploit for AT&T an verizon but idk again looks like main force is note 4
Well not sure how to fix it.
I have unrooted, removed safestrap.
Checked with root app and it says it is not rooted.
But it still won't update.
Took to AT&T tech center after on-line help from them didn't help. He was not able to update it. So I went to Bestbuys Samsung tech section. They hooked it up to their Smart update software, and it would not allow to be updated either. They said it was either rooted or had a foreign version of software on it. Or one of the software apps I had installed was messing it up.
So I again did a hard reset all the way back to stock ? And after setting up as a new phone I did a check for update 4.4.2 was on it and it said no update available......
SO WHAT IS GOING ON ? Is there a 4.4.4v that I can install with the odin, so that hopefully I can get over this bump..,, ?
Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse
ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
aeb401 said:
Since there are not too many stable ROMs available on the XT1096 that support CDMA (I am using Verizon's network). I decided I would unlock my bootloader, flash TWRP and root the stock firmware. Well, the past few days I guess I did not update my phone all the way before doing this since I just got it not even a week ago and keep getting prompts to install an OTA. This will obviously not work with TWRP and when I flashed TWRP I selected to modify the system so the stock firmware would not rewrite recovery on boot. This has become a complete pain in the ass for me. Accidently I selected to install the OTA since it is always in my notifications and when it happened it would obviously fail in TWRP but then it would boot back into the ROM and then power cycle back into TWRP. The only way to stop it was to do a factory reset which is not what I would like to do every time I accidently select to install this OTA. So my questions to you awesome people who know more about this device are. 1. is there a way I can enable the to option to where I will always have a stock recovery and then I can just fastboot boot into TWRP if needed? Or is there another way where I can just possibly stop this OTA all together even though the prompt already says it's downloaded and waiting for me to hit install. Like can I just go into rootexplorrer and delete or modify a few system files that'll stop the phone for looking for OTAs? I don't reallyl care about the OTA since it's obviously not 6.0 since VZW got boned on that one. Looks like it's just some security patches.
I'm sure this is probably a really stupid and simple question, so I apologize in advance. But thank you SO MUCH to anyone who decides to help me out. I will appreciate it GREATLY!!!
Click to expand...
Click to collapse
Try using your favorite applications manager for root and freeze MotorolaOTA. This will prevent the update from being downloaded and you won't get messages about installing the OTA update.